Sensing network function (NF) repository and exposure function
The introduction of SEF, SEDF, and SRF NFs addresses registration and discovery inefficiencies in wireless communication standards, optimizing signaling and enabling efficient streaming of sensing data to external clients, enhancing NEF capabilities.
Patent Information
- Application Number
- PCT/IB2026/054603
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-08-15
- Filing Date
- 2026-05-08
- Publication Date
- 2026-11-12
AI Technical Summary
Current wireless communication standards lack detailed descriptions on how Sensing Core NFs register and discover each other in a self-organizing manner, leading to potential heavy signaling and inefficiencies in streaming data results to external sensing clients, with the NEF not suited for streaming data handling.
Introduce new Sensing Core NFs such as SEF, SEDF, and SRF to optimize signaling flows and enable efficient discovery and streaming of sensing data, with the option to enhance the NEF or connect directly to a future data plane for broader data support.
Facilitates efficient registration and discovery of Sensing Core NFs, optimizing signaling and enabling seamless streaming of sensing data to external clients, enhancing the NEF's capability to handle both control plane and data transmission.
Smart Images

Figure IB2026054603_12112026_PF_FP_ABST
Abstract
Description
[0001] SENSING NETWORK FUNCTION (NF) REPOSITORY AND EXPOSURE FUNCTION
[0002] FIELD
[0003] The present disclosure relates to wireless communications, and in particular, to a network functions related to sensing.
[0004] BACKGROUND
[0005] The Third Generation Partnership Project (3GPP) has developed and is developing standards for Fourth Generation (4G) (also referred to as Long Term Evolution (LTE)) and Fifth Generation (5G) (also referred to as New Radio (NR)) wireless communication systems. Such systems provide, among other features, broadband communication between network nodes, such as base stations, and mobile user equipments (UE), as well as communication between network nodes and between UEs. The 3GPP is also developing standards for Sixth Generation (6G) wireless communication networks.
[0006] In particular, 3GPP may describe sensing definitions and categories of use cases for ISAC. Integrated Sensing and Communication (ISAC) enables the spatial location of objects by integrating sensing with communication capabilities in mobile networks.
[0007] FIG. 1 is a diagram of one or more use cases for 3GPP. FIG. 2 is a list of example 3GPP use cases in 3GPP TS 22.837.
[0008] FIG. 3 is a diagram of sensing topologies. The left portion of FIG. 3 relates to a monostatic sensing topology. The traditional radar topology is monostatic where the same node is used as transmitter and receiver. Depending on the distance (delay) to the target, the sensing signal transmission might still be ongoing when the earliest echo arrives. The middle portion of FIG. 3 shows a bistatic sensing system that avoids self-interference by using different nodes as transmitters and receivers. Multistatic sensing is an extension to bistatic sensing, which combines multiple bistatic sensing links, see the right side of FIG.
[0009] 3.
[0010] FIG. 4 is a diagram of a summary of use cases.
[0011] FIG. 5 is a diagram of an external exposure application programming interface (API).
[0012] Sensing Area Topology managementSensing Unit (SU) Area: The area where an SU can be used for sensing measurement, i.e., the area a certain SU “covers”. This area may be a 2D or 3D representation.
[0013] Sensing Unit Coordinator (SUC) Area: The area controlled by a certain SUC, i.e., the area in which the SUC is in direct control of one or more SUs.
[0014] Serving Sensing Area: The area for which a certain sensing request handler (SRH) can handle a sensing job / task. The area may be described as a geographical area (in 2D or 3D) or even be represented by a geographical point representing, e.g., its deployment location or a point in the area where it can handle a sensing job / task.
[0015] Target Sensing Area: The area targeted for a certain sensing measurement.
[0016] Typically used between the sensing workflow manager (SRH) and the sensing unit coordinator (SUC).
[0017] Exposed Serving Sensing Area: A pre-determined area used in the exposure interface with external sensing clients, e.g., to be used in SLAs with sensing clients. This area may or may not be based on the network-internal Serving Sensing Areas.
[0018] The result of above “procedure” is shown in FIG. 6. The NRF requires new sensing specific functionality compared to the Network Repository Function (NRF) specified in 3GPP TS 29.510. 3GPP may decide to include the sensing specific functionality into the already specified NRF or to specify a new sensing specific repository function.
[0019] This sensing request is normally received (possibly via aggregators) to the API GW inside the CSP domain. The API GW (possibly with the help of other network functions (NFs)) may authenticate the AF before it forwards the sensing job initiation (including the Area in which the job is requested) to the rest of the network. The rest of the network can be, e.g., a NEF, Network Exposure Function, (or similar function).
[0020] The NEF (or any other exposure handling function, if not the NEF) maps the area input from an application function (AF), i.e., in which the job is requested to the CSP internal Sensing Area(s) in order to send the sensing job request to the correct Core SRH instance.
[0021] Currently, there are no details on how the different Sensing Core NFs are registering and discovering each other in a self-organizing way, using a repository function, nor are there any descriptions on the identifiers needed to make the solution work end-to-end.Background: Static configuration of SUC on SCC, SUC registration in SCC: Pl 13408, Pl 12409
[0022] A solution may have a risk of causing heavy signaling which could be mitigated by specifying the new Sensing dedicated NFs, as collapsed functions, and not reusing the existing 5GC NFs.
[0023] A solution might not cope with streaming results towards an external sensing Client (via the exposure function or otherwise), as traditional exposure solutions have primarily been about request-response style designs.
[0024] For the same reason, the NEF in 5GC is possibly not suited to cater for Streaming data results but only for control plane traffic.
[0025] SUMMARY
[0026] Some embodiments advantageously provide methods, systems, and apparatuses for network functions related to sensing.
[0027] One or more embodiments introduce new sensing core function NFs:
[0028] • SEF, Sensing Exposure Function
[0029] • SEDF, Sensing Exposure Data Function
[0030] • SRF, Sensing Repository Function
[0031] One or more embodiments introduce call flows that
[0032] • Registers NFs, making them discoverable
[0033] • Discovers NFs and sets up a sensing job from a to z.
[0034] One or more embodiments introduce options on how to optimize signaling flows. Introduces an identity framework making it possible to steer results in a way that depends on the sensing tasks / processing needed
[0035] If no new NFs are introduced then the NEF may have to be enhanced to support one Control Plane NF and one Data Transmission NF, like SEF and SEDF as described herein. This new “Exposure Data” NF doesn’t have to be limited to Sensing only if the legacy 5GC NEF is enhanced but any streaming data could be supported. Alternatively, the new “Exposure Data” NF could connect directly to a future data plane (which is not further described herein).
[0036] According to one aspect of the present disclosure, a method implemented by a sensing core node that is configured to communicate with a Radio Access Network, RAN, node is provided. The sensing core node includes a first sensing request handler, SRH, that supports at least one sensing area supported by the RAN node. At least one sensing-basedfunction is provided to a client node, using the first SRH. At least one function associated with at least one sensing-based function is performed.
[0037] According to one or more embodiments of this aspect, a registration message is received; and a registration response is transmitted where the registration response indicates that the RAN node has been: accepted by the sensing core node as a sensing RAN node for one or both of performing sensing measurements and obtaining sensing data; and registered in the sensing core node.
[0038] According to one or more embodiments of this aspect, the registration message comprises at least one parameter, where the at least one parameter includes one or more of: an identity of the RAN node; a sensing coverage area of the RAN node; a communication address of the RAN node; capability information of the RAN node; and a secondary sensing unit coordinator associated with the RAN node.
[0039] According to one or more embodiments of this aspect, an update procedure is performed based on a change to at least one of the at least one parameter; and the update procedure results in a second SRH being used to provide at least one sensing-based function to the client node.
[0040] According to one or more embodiments of this aspect, the registration response comprises one or more of: an identity of the first SRH; indication of a backup SRH; numerical weight associated with the first SRH; and capabilities of the first SRH.
[0041] According to one or more embodiments of this aspect, the sensing core node comprises a Sensing Exposure Function, SEF; and a Sensing Core Function, SCF, is selected at the SEF for discovery of a sensing entity to service a sensing request from an Application Function, AF.
[0042] According to one or more embodiments of this aspect, the RAN node is determined, at the SCF, to be capable of performing sensing associated with the sensing request; the sensing request is transmitted, via the first SRH, to the RAN node; in response to the sensing request, sensing data is received from the RAN node; and the sensing data satisfying the sensing request.
[0043] According to one or more embodiments of this aspect, the sensing request is associated with one of: environment monitoring; motion monitoring; object detection; and object tracking.
[0044] According to one or more embodiments of this aspect, the sensing core node further comprises a Sensing Exposure Data Function, SEDF. An external sensing data session point of interconnect is provided to an Application Function, AF, or NetworkExposure Function, NEF using the SEDF. Sensing data received from a plurality of sensing processing functions is merged at the SEDF. The sensing data is processed at the SEDF so that privacy-friendly data remains for exposure to the AF or NEF.
[0045] According to one or more embodiments of this aspect, the sensing core node further comprises a Sensing Repository Function, SRF,
[0046] A lookup request for a sensing request handler or a sensing processing function is received at the SRF.
[0047] One or more sensing request handlers or sensing processing functions that match the lookup request are determined at the SRF based on stored network function profiles.
[0048] Eookup response information is provided from the SRF where the lookup response information comprises one or more of an identity, a serving sensing area, a URI, a load indication, and a backup indication associated with the one or more sensing request handlers or sensing processing functions.
[0049] According to one or more embodiments of this aspect, the at least one function includes one or more of: optimizing signaling flows; and performing a sensing task.
[0050] According to another aspect of the present disclosure, a sensing core node configured to communicate with a Radio Access Network, RAN, node is provided. The sensing core node includes a first sensing request handler, SRH, that supports at least one sensing area supported by the RAN node. The sensing core node is configured to: provide, using the first SRH, at least one sensing-based function to a client node; and perform at least one function associated with at least one sensing-based function.
[0051] According to one or more embodiments of this aspect, the sensing core node is further configured to: receive a registration message; and transmit a registration response indicating that the RAN node has been: accepted by the sensing core node as a sensing RAN node for one or both of performing sensing measurements and obtaining sensing data; and registered in the sensing core node.
[0052] According to one or more embodiments of this aspect, the registration message comprises at least one parameter, where the at least one parameter includes one or more of: an identity of the RAN node; a sensing coverage area of the RAN node; a communication address of the RAN node; capability information of the RAN node; and a secondary sensing unit coordinator associated with the RAN node.
[0053] According to one or more embodiments of this aspect, the sensing core node is further configured to perform an update procedure based on a change to at least one of theat least one parameter; and the update procedure results in a second SRH being used to provide at least one sensing-based function to the client node.
[0054] According to one or more embodiments of this aspect, the registration response comprises one or more of: an identity of the first SRH; indication of a backup SRH; numerical weight associated with the first SRH; and capabilities of the first SRH.
[0055] According to one or more embodiments of this aspect, the sensing core node comprises a Sensing Exposure Function, SEF, that is configured to select a Sensing Core Function, SCF, for discovery of a sensing entity to service a sensing request from an Application Function, AF.
[0056] According to one or more embodiments of this aspect, the SCF is configured to: determine that the RAN node is capable of performing sensing associated with the sensing request; transmit, via the first SRH, the sensing request to the RAN node; in response to the sensing request, receive sensing data from the RAN node; and the sensing data satisfying the sensing request.
[0057] According to one or more embodiments of this aspect, the sensing request is associated with one of: environment monitoring; motion monitoring; object detection; and object tracking.
[0058] According to one or more embodiments of this aspect, the sensing core node further comprises a Sensing Exposure Data Function, SEDF; and the sensing core node is configured to: provide, using the SEDF, an external sensing data session point of interconnect to an Application Function, AF, or Network Exposure Function, NEF; merge, at the SEDF, sensing data received from a plurality of sensing processing functions; and process, at the SEDF, the sensing data so that privacy-friendly data remains for exposure to the AF or NEF.
[0059] According to one or more embodiments of this aspect, the sensing core node further comprises a Sensing Repository Function, SRF; and the sensing core node is further configured to: receive, at the SRF, a lookup request for a sensing request handler or a sensing processing function; determine, at the SRF based on stored network function profiles, one or more sensing request handlers or sensing processing functions that match the lookup request; and provide, from the SRF, lookup response information comprising one or more of an identity, a serving sensing area, a URI, a load indication, and a backup indication associated with the one or more sensing request handlers or sensing processing functions.According to one or more embodiments of this aspect, the at least one function includes one or more of: optimizing signaling flows; and performing a sensing task.
[0060] According to another aspect of the present disclosure, a method implemented by a Radio Access Network, RAN, node that is configured to communicate with a sensing core node is provided. A first sensing request handler, SRH of the sensing core node is discovered. A registration message is transmitted to the first SRH. A registration response is received where the registration response indicates that the RAN node has been: accepted by the sensing core node as a sensing network node for one or both of performing sensing measurements and obtaining sensing data; and registered in the sensing core node.
[0061] According to one or more embodiments of this aspect, the registration message comprises at least one parameter, the at least one parameter including one or more of: an identity of the RAN node; a sensing coverage area of the RAN node; a communication address of the RAN node; capability information of the RAN node; and a secondary sensing unit coordinator associated with the RAN node.
[0062] According to one or more embodiments of this aspect, the update procedure is performed based on a change to at least one of the at least one parameter; and the update procedure is configured to cause the RAN node to discover a second SRH.
[0063] According to one or more embodiments of this aspect, the registration response comprises one or more of: an identity of the first SRH; indication of a backup SRH; numerical weight associated with the first SRH; and capabilities of the first SRH.
[0064] According to one or more embodiments of this aspect, the discovery of the first SRH includes discovering at least one SRH that supports at least one sensing area of the RAN node.
[0065] According to one or more embodiments of this aspect, a sensing request is received from the SRH; in response to the sensing request, one or both of sensing measurements and obtaining sensing data is performed to satisfy the sensing request; and the one or both of the sensing measurements and sensing data are indicated to the first SRH.
[0066] According to one or more embodiments of this aspect, the sensing request is associated with one of: environment monitoring; motion monitoring; object detection; and object tracking.
[0067] According to another aspect of the present disclosure, a Radio Access Network, RAN, node is configured to communicate with a sensing core node. The RAN node is configured to: discover a first sensing request handler, SRH of the sensing core node;cause transmission of a registration message to the first SRH; and receive a registration response indicating that the RAN node has been: accepted by the sensing core node as a sensing network node for one or both of performing sensing measurements and obtaining sensing data; and registered in the sensing core node.
[0068] According to one or more embodiments of this aspect, the registration message comprises at least one parameter, where the at least one parameter includes one or more of: an identity of the RAN node; a sensing coverage area of the RAN node; a communication address of the RAN node; capability information of the RAN node; and a secondary sensing unit coordinator associated with the RAN node.
[0069] According to one or more embodiments of this aspect, the RAN node is further configured to perform an update procedure based on a change to at least one of the at least one parameter; and the update procedure is configured to cause the RAN node to discover a second SRH.
[0070] According to one or more embodiments of this aspect, the registration response comprises one or more of: an identity of the first SRH; indication of a backup SRH; numerical weight associated with the first SRH; and capabilities of the first SRH.
[0071] According to one or more embodiments of this aspect, the discovery of the first SRH includes discovering at least one SRH that supports at least one sensing area of the RAN node.
[0072] According to one or more embodiments of this aspect, the RAN node is further configured to: receive a sensing request from the SRH; in response to the sensing request, one or both of perform sensing measurements and obtain sensing data to satisfy the sensing request; and indicate the one or both of the sensing measurements and sensing data to the first SRH.
[0073] According to one or more embodiments of this aspect, the sensing request is associated with one of: environment monitoring; motion monitoring; object detection; and object tracking.
[0074] BRIEF DESCRIPTION OF THE DRAWINGS
[0075] A more complete understanding of the present embodiments, and the attendant advantages and features thereof, will be more readily understood by reference to the following detailed description when considered in conjunction with the accompanying drawings wherein:
[0076] FIG. 1 is a diagram of one or more use cases for 3GPP;FIG. 2 is a list of 3GPP use Case in 3GPP TS 22.837;
[0077] FIG. 3 is a diagram of sensing topologies;
[0078] FIG. 4 is a diagram of a summary of use cases;
[0079] FIG. 5 is a diagram of an external exposure API;
[0080] FIG. 6 is a diagram of a result of a procedure associated with an exposed serving sensing area;
[0081] FIG. 7 is a schematic diagram of an example network architecture illustrating a communication system according to principles disclosed herein;
[0082] FIG. 8 is a block diagram of a network node in communication with a user equipment over a wireless connection according to some embodiments of the present disclosure;
[0083] FIG. 9 is a schematic diagram of another example network architecture illustrating a communication system according to principles disclosed herein;
[0084] FIG. 10 is a flowchart of an example process in a network node according to some embodiments of the present disclosure;
[0085] FIG. 11 is a flowchart of an example process in a RAN node according to some embodiments of the present disclosure;
[0086] FIG. 12 is a flowchart of an example process in a core network node according to some embodiments of the present disclosure;
[0087] FIG. 13 is a flowchart of an example process in a sensing core node according to some embodiments of the present disclosure;
[0088] FIG. 14 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments may be virtualized;
[0089] FIG. 15 is a signaling diagram of a sensing call flow setup-DNS-CSP according to one or more embodiments of the present disclosure;
[0090] FIG. 16 is a signaling diagram of a sensing call flow setup-CSP-sensing Core according to one or more embodiments of the present disclosure;
[0091] FIG. 17 is a diagram of a sensing call flow - CSP-Sensing Core (1 of 3) according to one or more embodiments of the present disclosure;
[0092] FIG. 18 is a signaling diagram of a sensing call flow-CSP-Sensing Core (2 of 3) according to one or more embodiments of the present disclosure;
[0093] FIG. 19 is a signaling diagram of sensing call flow-CSP-sensing core (3 of 3) according to one or more embodiments of the present disclosure;FIG. 20 is a sensing call flow (collapsed SRF+SEF) according to one or more embodiments of the present disclosure;
[0094] FIG. 21 is a sensing call flow (Collapsed SRF+SEF+SEDF) according to one or more embodiments of the present disclosure;
[0095] FIG. 22 is a sequence drawing of a procedure for a requested sensing service authorization according to one or more embodiments of the present disclosure; and FIG. 23 is a signaling diagram of a procedure of sensing result exposure to an AF, where several steps are described below.
[0096] DETAILED DESCRIPTION
[0097] One or more embodiments described herein focus on the Sensing Core functionalities, Service Exposure and the RAN / CN interface. In particular, one or more embodiments, make the sensing solution work end-to-end including exposure of data transmission, from an external exposure perspective, in an efficient way.
[0098] Before describing in detail exemplary embodiments, it is noted that the embodiments reside primarily in combinations of apparatus components and processing steps related to network functions related to sensing. Accordingly, components have been represented where appropriate by conventional symbols in the drawings, showing only those specific details that are pertinent to understanding the embodiments so as not to obscure the disclosure with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein.
[0099] As used herein, relational terms, such as “first” and “second,” “top” and “bottom,” and the like, may be used solely to distinguish one entity or element from another entity or element without necessarily requiring or implying any physical or logical relationship or order between such entities or elements. The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the concepts described herein. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises,” “comprising,” “includes” and / or “including” when used herein, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.In embodiments described herein, the joining term, “in communication with” and the like, may be used to indicate electrical or data communication, which may be accomplished by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling or optical signaling, for example. One having ordinary skill in the art will appreciate that multiple components may interoperate and modifications and variations are possible of achieving the electrical and data communication.
[0100] In some embodiments described herein, the term “coupled,” “connected,” and the like, may be used herein to indicate a connection, although not necessarily directly, and may include wired and / or wireless connections.
[0101] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the concepts described herein. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises,” “comprising,” “includes” and / or “including” when used herein, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.
[0102] The term “network node” used herein can be any kind of network node comprised in a radio network which may further comprise any of base station (BS), radio base station, base transceiver station (BTS), base station controller (BSC), radio network controller (RNC), g Node B (gNB), evolved Node B (eNB or eNodeB), Node B, multistandard radio (MSR) radio node such as MSR BS, multi-cell / multicast coordination entity (MCE), relay node, donor node controlling relay, radio access point (AP), transmission points, transmission nodes, Remote Radio Unit (RRU) Remote Radio Head (RRH), a core network node (e.g., mobile management entity (MME), self-organizing network (SON) node, a coordinating node, positioning node, MDT node, etc.), an external node (e.g., 3rd party node, a node external to the current network), nodes in distributed antenna system (DAS), a spectrum access system (SAS) node, an element management system (EMS), etc. The network node may also comprise test equipment. The term “radio node” used herein may be used to also denote a user equipment (UE) such as a wireless device (WD) or a radio network node.
[0103] In some embodiments, the non-limiting terms wireless device (WD) or a user equipment (UE) are used interchangeably. The UE herein can be any type of user equipment capable of communicating with a network node or another UE over radiosignals, such as a wireless device (WD). The UE may also be a radio communication device, target device, device to device (D2D) UE, machine type UE or UE capable of machine to machine communication (M2M), low-cost and / or low-complexity UE, a sensor equipped with UE, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, Customer Premises Equipment (CPE), an Internet of Things (loT) device, or a Narrowband loT (NB-IOT) device etc.
[0104] Also, in some embodiments the generic term “radio network node” is used. It can be any kind of a radio network node which may comprise any of base station, radio base station, base transceiver station, base station controller, network controller, RNC, evolved Node B (eNB), Node B, gNB, Multi-cell / multicast Coordination Entity (MCE), relay node, access point, radio access point, Remote Radio Unit (RRU) Remote Radio Head (RRH).
[0105] Note that although terminology from one particular wireless system, such as, for example, 3GPP LTE and / or New Radio (NR) and / or 6G, may be used in this disclosure, this should not be seen as limiting the scope of the disclosure to only the aforementioned system. It is contemplated that other 3GPP systems may make use of the concepts and arrangements disclosed herein. For example, a disclosure relating to NR may also be implementable in a 6G system and / or an LTE system, a disclosure relating to 6G may also be implementable in a NR and / or LTE system, and a disclosure relating to LTE may also be implementable in a NR and / or 6G system. Other wireless systems, including without limitation Wide Band Code Division Multiple Access (WCDMA), Worldwide Interoperability for Microwave Access (WiMax), Ultra Mobile Broadband (UMB) and Global System for Mobile Communications (GSM), may also benefit from exploiting the ideas covered within this disclosure.
[0106] Note further, that functions described herein as being performed by a user equipment or a network node may be distributed over a plurality of user equipments and / or network nodes. In other words, it is contemplated that the functions of the network node and user equipment described herein are not limited to performance by a single physical device and, in fact, can be distributed among several physical devices.
[0107] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs. It will be further understood that terms used herein should be interpreted as having a meaning that is consistent with their meaning in the context of this specification and the relevant art and will not be interpreted in an idealizedor overly formal sense unless expressly so defined herein.
[0108] Some embodiments are directed to network functions related to sensing.
[0109] Referring again to the drawing figures, in which like elements are referred to by like reference numerals, there is shown in FIG. 7 a schematic diagram of a communication system 10, according to an embodiment, such as a 3GPP-type cellular network that may support standards such as LTE and / or NR (5G) and / or 6G, which comprises an access network 12, such as a radio access network, and a core network 14. The core network 14 includes one or more core network nodes 15 such as sensing core node 15. In some embodiments, core network node 15 includes SRH unit 17 for performing core network node 15 (e.g., sensing core node) functions that are described herein. The access network 12 comprises a plurality of network nodes 16a, 16b, 16c (referred to collectively as network nodes 16), such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 18a, 18b, 18c (referred to collectively as coverage areas 18). Each network node 16a, 16b, 16c is connectable to the core network 14 over a wired or wireless connection 20. A first user equipment (UE) 22a located in coverage area 18a is configured to wirelessly connect to, or be paged by, the corresponding network node 16a. A second UE 22b in coverage area 18b is wirelessly connectable to the corresponding network node 16b. While a plurality of UEs 22a, 22b (collectively referred to as user equipments 22) are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding network node 16. Note that although only two UEs 22 and three network nodes 16 are shown for convenience, the communication system may include many more UEs 22 and network nodes 16.
[0110] As one example, in certain embodiments, access network 12 may contain some access network nodes 16 that support 3GPP radio access technologies (RAT), such as LTE or NR, while other access network nodes 16 support (or the same access network nodes 16 additionally support) non-3GPP RATs, such as Wi-Fi or a proprietary RAT. As another example, communication system 10 may support multiple generations of related communication standards (e.g., 4G, 5G and 6G 3GPP communication standards) and, as a result, may include an access network 12 and / or a core network 14 that supports multiple different standard generations or may include multiple access networks 12 and / or multiple core networks 14 with individual networks supporting different standards generations.
[0111] Also, it is contemplated that a UE 22 can be in simultaneous communicationand / or configured to separately communicate with more than one network node 16 and more than one type of network node 16. For example, a UE 22 can have dual connectivity with a network node 16 that supports LTE and the same or a different network node 16 that supports NR. As an example, UE 22 can be in communication with an eNB for LTE / E-UTRAN, a gNB for NR / NG-RAN (i.e., being configured for multiradio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC) and / or Wi-Fi.
[0112] A network node 16 (eNB or gNB) is configured to include a sensing unit 24 which is configured to perform one or more network node 16 functions that are described herein. A core network node 15 is configured to include a SRH unit 17 which is configured to perform one or more SRH unit 17 functions that are described herein.
[0113] Example implementations, in accordance with an embodiment, of the UE 22 and network node 16 discussed in the preceding paragraphs will now be described with reference to FIG. 8.
[0114] The communication system 10 includes a network node 16 provided in a communication system 10 and including hardware 28 enabling it to communicate with the UE 22. The hardware 28 may include a communication interface 29 comprising a radio interface 30 for setting up and maintaining at least a wireless connection 32 with a UE 22 located in a coverage area 18 served by the network node 16. The radio interface 30 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers. The radio interface 30 includes an array of antennas 34 to radiate and receive signal(s) carrying electromagnetic waves.
[0115] In the embodiment shown, the hardware 28 of the network node 16 further includes processing circuitry 36. The processing circuitry 36 may include a processor 38 and a memory 40. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 36 may comprise integrated circuitry for processing and / or control, e.g., one or more processors and / or processor cores and / or FPGAs (Field Programmable Gate Array) and / or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 38 may be configured to access (e.g., write to and / or read from) the memory 40, which may comprise any kind of volatile and / or nonvolatile memory, e.g., cache and / or buffer memory and / or RAM (Random Access Memory) and / or ROM (Read-Only Memory) and / or optical memory and / or EPROM (Erasable Programmable Read-Only Memory).
[0116] Thus, the network node 16 further has software 42 stored internally in, forexample, memory 40, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the network node 16 via an external connection. The software 42 may be executable by the processing circuitry 36. The processing circuitry 36 may be configured to control any of the methods and / or processes described herein and / or to cause such methods, and / or processes to be performed, e.g., by network node 16.
[0117] Processor 38 corresponds to one or more processors 38 for performing network node 16 functions described herein. The memory 40 is configured to store data, programmatic software code and / or other information described herein. In some embodiments, the software 42 may include instructions that, when executed by the processor 38 and / or processing circuitry 36, causes the processor 38 and / or processing circuitry 36 to perform the processes described herein with respect to network node 16. For example, processing circuitry 36 of the network node 16 may include sensing unit 24 which is configured to perform one or more network node 16 functions that are described herein.
[0118] The network node 16 may be composed of multiple distinct network entities (e.g., a NodeB entity and a RNC entity, or a BTS entity and a BSC entity, etc.), which may each have or utilize their own respective physical components. In certain scenarios in which the network node 16 comprises multiple such entities (e.g., BTS and BSC), one or more of the separate entities may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 16 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memories 40 or portions of memory 40 for different RATs) and some components may be reused (e.g., a same antenna may be shared by different RATs). The network node 16 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 16, for example GSM, WCDMA, LTE, NR, Wi-Fi (e.g., according to an IEEE 802.11 family standard), Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 16.
[0119] In certain alternative embodiments, network node 16 may be capable of wireless communication but does not include separate radio front-end circuitry, instead, the processing circuitry 36 includes radio front-end circuitry and is connected to the antenna 34. Similarly, in some embodiments, all or some of the RF receivers, transmitters and / ortransceivers are part of the radio interface 30. In still other embodiments, the communication interface 29 includes one or more ports or terminals, the radio interface 30, and the RF receiver, transmitter and / or transceiver, and the communication interface 31 communicates with baseband processing circuitry, which is part of a digital unit (not shown).
[0120] The antenna 34 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 34 may be coupled to the radio front-end circuitry in radio interface 30 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 34 is separate from the network node 16 and connectable to the network node 16 through one or more interfaces or ports.
[0121] Core network node 15 includes hardware 70 enabling it to communicate with the network node 16, among other entities in system 10. For example, core network node 15 can communicate wirelessly or via a wired connection with network nodes 16 via communication link 59. The hardware 70 may include a communication interface 72 for communicating with one or more entities in system 10. In some embodiments, communication interface 72 includes a radio interface for setting up and maintaining at least a wireless connection. The radio interface may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers. The radio interface includes an array of antennas to radiate and receive signal(s) carrying electromagnetic waves.
[0122] In the embodiment shown, the hardware 70 of the core network node 15 further includes processing circuitry 74. The processing circuitry 74 may include a processor 76 and a memory 78. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 74 may comprise integrated circuitry for processing and / or control, e.g., one or more processors and / or processor cores and / or FPGAs (Field Programmable Gate Array) and / or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 76 may be configured to access (e.g., write to and / or read from) the memory 78, which may comprise any kind of volatile and / or nonvolatile memory, e.g., cache and / or buffer memory and / or RAM (Random Access Memory) and / or ROM (Read-Only Memory) and / or optical memory and / or EPROM (Erasable Programmable Read-Only Memory).
[0123] Thus, the core network node 15 further has software 80 stored internally in, for example, memory 78, or stored in external memory (e.g., database, storage array, networkstorage device, etc.) accessible by the core network node 15 via an external connection. The software 80 may be executable by the processing circuitry 74. The processing circuitry 74 may be configured to control any of the methods and / or processes described herein and / or to cause such methods, and / or processes to be performed, e.g., by core network node 15. Processor 76 corresponds to one or more processors 76 for performing core network node 15 functions described herein. The memory 78 is configured to store data, programmatic software code and / or other information described herein. In some embodiments, the software 80 may include instructions that, when executed by the processor 76 and / or processing circuitry 74, causes the processor 76 and / or processing circuitry 74 to perform the processes described herein with respect to core network node 15. For example, processing circuitry 74 of the core network node 15 may include sensing unit 24 which is configured to perform one or more network node 16 functions that are described herein.
[0124] The communication system 10 further includes the UE 22 already referred to. The UE 22 may have hardware 44 that may include a radio interface 46 configured to set up and maintain a wireless connection 32 with a network node 16 serving a coverage area 18 in which the UE 22 is currently located. The radio interface 46 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers. The radio interface 46 includes an array of antennas 48 to radiate and receive signal(s) carrying electromagnetic waves.
[0125] Communication functions of the radio interface 46 may include cellular communication, Wi-Fi communication (e.g., according to an IEEE 802.11 family standard), LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / internet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.
[0126] The hardware 44 of the UE 22 further includes processing circuitry 50. Theprocessing circuitry 50 may include a processor 52 and memory 54. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 50 may comprise integrated circuitry for processing and / or control, e.g., one or more processors and / or processor cores and / or FPGAs (Field Programmable Gate Array) and / or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 52 may be configured to access (e.g., write to and / or read from) memory 54, which may comprise any kind of volatile and / or nonvolatile memory, e.g., cache and / or buffer memory and / or RAM (Random Access Memory) and / or ROM (Read-Only Memory) and / or optical memory and / or EPROM (Erasable Programmable Read-Only Memory).
[0127] Thus, the UE 22 may further comprise software 56, which is stored in, for example, memory 54 at the UE 22, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the UE 22. The software 56 may be executable by the processing circuitry 50. The software 56 may include a client application 58. The client application 58 may be operable to provide a service to a human or non-human user via the UE 22.
[0128] The processing circuitry 50 may be configured to control any of the methods and / or processes described herein and / or to cause such methods, and / or processes to be performed, e.g., by UE 22. The processor 52 corresponds to one or more processors 52 for performing UE 22 functions described herein. The UE 22 includes memory 54 that is configured to store data, programmatic software code and / or other information described herein. In some embodiments, the software 56 and / or the client application 58 may include instructions that, when executed by the processor 52 and / or processing circuitry 50, causes the processor 52 and / or processing circuitry 50 to perform the processes described herein with respect to UE 22.
[0129] In some embodiments, the inner workings of the network node 16 and UE 22 may be as shown in FIG. 8 and independently, the surrounding network topology may be that of FIG. 7.
[0130] The wireless connection 32 between the UE 22 and the network node 16 is in accordance with the teachings of the embodiments described throughout this disclosure. More precisely, the teachings of some of these embodiments may improve the data rate, latency, and / or power consumption and thereby provide benefits such as reduced user waiting time, relaxed restriction on file size, better responsiveness, extended battery lifetime, etc. In some embodiments, a measurement procedure may be provided for thepurpose of monitoring data rate, latency and other factors on which the one or more embodiments improve.
[0131] Although FIGS. 7 and 8 show various “units” such as sensing unit 24 and SRH unit 17 as being within a respective processor, it is contemplated that these units may be implemented such that a portion of the unit is stored in a corresponding memory within the processing circuitry. In other words, the units may be implemented in hardware or in a combination of hardware and software within the processing circuitry.
[0132] FIG. 9 is another example of a communication system 10 according to some embodiments. As used herein, the communication system 10 of FIG. 9 includes multiple access points (APs) 60 (with four example APs 60a, 60b, 60c, and 60d being depicted) and multiple wireless devices, referred to in the context of communication system 10 of FIG. 9 as stations (STAs) 62 (referred to individually as STA 62a, STA 62b, STA 62c, STA 62d, and STA 62e). STA 62a is served by AP 60a in a first basic service set (BSS) 64a. STA 62b and STA 62c are served by AP 60b in a second BSS, BSS 64b. STA 62d is served by AP 60c in a third BSS, BSS 64c. STA 62e is served by AP 60d in a fourth BSS, BSS 64d. Stations 62 may be non-AP STAs and correspond to various kinds of wireless devices, for example, user terminals, such as mobile or stationary computing devices like smartphones, laptop computers, desktop computers, tablet computers, gaming devices, head-mounted displays (HMDs) for Augmented Reality (AR) or Virtual Reality (VR), or the like, including UEs 22 that are shown and described with respect to FIGS. 7 and 8. In other words, in some embodiment, STA 62 is a UE 22. Further, stations 62 could, for example, correspond to other kinds of equipment like smart home devices, printers, multimedia devices, data storage devices, or the like.
[0133] Each of STAs 62 may connect through a radio link to one of APs 60. For example, depending on location or channel conditions experienced by a given STA 62, the STA may select an appropriate AP and BSS for establishing the radio link. The radio link may be based on one or more orthogonal frequency-division multiplexing (OFDM) carriers from a frequency spectrum that is shared on the basis of a contention-based mechanism, e.g., an unlicensed or license exempt band like 2.4 GHz Industrial, Scientific, and Medical (ISM) band, the 5 GHz band, the 6 GHz band, or the 60 GHz band.
[0134] Each AP 60 may provide data connectivity to STAs 62 connected to a particular AP 60. As illustrated, APs 60 may be connected to a data network 66. In this way, APs 60 may also provide data connectivity between STAs 62 and other entities, e.g., to one or more servers, service providers, data sources, data sinks, user terminals, or the like.Accordingly, the radio link established between a given STA 62 and its serving AP 60 may be used for providing various kinds of services to STA 62, e.g., a voice service, a multimedia service, or other data service. Such services may be based on applications that are executed on STA 62 and / or on a device linked to STA 62. By way of example, FIG. 9 illustrates an application service platform 68 provided in data network 66. The application(s) executed on STA 62 and / or on one or more other devices linked to STA 62 may use the radio link for data communication with one or more other STA 62 and / or the application service platform 68, thereby enabling utilization of the corresponding service(s) at STA 62.
[0135] FIG. 10 is a flowchart of an example process in a network node 16 according to one or more embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of network node 16 such as by one or more of processing circuitry 36 (including the Sensing Unit 24), processor 38, and / or radio interface 30. Network node 16 is configured to discover (Block S100) a sensing request handler, SRH of a sensing core node 15 (e.g., core network node 15), as described herein. Network node 16 is configured to transmit (Block S102) a registration message to the SRH, as described herein. Network node 16 is configured to receive (Block S104) a registration response indicating that the network node 16 has been: accepted by the sensing core node 15 as a sensing network node 16; and registered in the sensing core node 15.
[0136] According to one or more embodiments, the registration message comprises at least one parameter, where the at least one parameter includes one or more of: an identity of the network node 16; a sensing coverage area of the network node 16; a communication address of the network node 16; capability information of the network node 16; and a secondary sensing unit coordinator associated with the network node 16.
[0137] According to one or more embodiments, the network node 16 is further configured to perform an update procedure based on a change to at least one of the at least one parameter.
[0138] According to one or more embodiments, the response message comprising one or more of: an identity of the SRH; indication of a backup SRH; weight associated with the SRH; and capabilities of the SRH.
[0139] According to one or more embodiments, the discovery of the SRH includes discovering at least one SRH that support at least one sensing area of the network node.
[0140] According to one or more embodiments, the network node 16 is further configuredto: receive a sensing request from the SRH; select at least one sensing entity to satisfy the sensing request; and indicate sensing data associated with the at least one sensing entity.
[0141] FIG. 11 is a flowchart of an example process in a RAN node 16 (e.g., network node 16) according to one or more embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of RAN node 16 such as by one or more of processing circuitry 36 (including the Sensing Unit 24), processor 38, and / or radio interface 30. RAN node 16 is configured to discover (Block S106) a first sensing request handler, SRH of the sensing core node 15, as described herein. RAN node 16 is configured to cause (Block S108) transmission of a registration message to the first SRH, as described herein. RAN node 16 is configured to receive (Block SI 10) a registration response indicating that the RAN node 16 has been: accepted by the sensing core node 15 as a sensing RAN node for one or both of performing sensing measurements and obtaining sensing data; and registered in the sensing core node 15.
[0142] According to one or more embodiments, the registration message comprises at least one parameter, where the at least one parameter includes one or more of: an identity of the RAN node 16; a sensing coverage area of the RAN node 16; a communication address of the RAN node 16; capability information of the RAN node 16; and a secondary sensing unit coordinator associated with the RAN node 16.
[0143] According to one or more embodiments, the RAN node 16 is further configured to perform an update procedure based on a change to at least one of the at least one parameter; and the update procedure is configured to cause the RAN node 16 to discover a second SRH.
[0144] According to one or more embodiments, the registration response comprises one or more of: an identity of the first SRH; indication of a backup SRH; numerical weight associated with the first SRH; and capabilities of the first SRH.
[0145] According to one or more embodiments, the discovery of the first SRH includes discovering at least one SRH that supports at least one sensing area of the RAN node 16.
[0146] According to one or more embodiments, the RAN node 16 is further configured to: receive a sensing request from the first SRH; in response to the sensing request, one or both of perform sensing measurements and obtain sensing data to satisfy the sensing request; and indicate the one or both of the sensing measurements and sensing data to the first SRH.
[0147] According to one or more embodiments, the sensing request is associated with one of: environment monitoring; motion monitoring; object detection; and object tracking.FIG. 12 is a flowchart of an example process in a sensing core node 15 (e.g., core network node 15) according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of sensing core node 15 such as by one or more of processing circuitry 74 (including the SRH unit 17), processor 76, and / or communication interface 72. The sensing core node 15 is configured to provide (Block SI 12), using the SRH, at least one sensing-based function to a network 12 as described herein. The sensing core node 15 is configured to perform (Block SI 14) at least one function associated with the at least one sensing-based function as described herein.
[0148] According to one or more embodiments, the sensing core node 15 is further configured to receive a registration message; and transmit a registration response indicating that the network node 16 has been: accepted by the sensing core node 15 as a sensing network node 16; and registered in the sensing core node 15.
[0149] According to one or more embodiments, the registration message comprises at least one parameter, the at least one parameter including one or more of: an identity of the network node 16; a sensing coverage area of the network node 16; a communication address of the network node 16; capability information of the network node 16; and a secondary sensing unit coordinator associated with the network node 16.
[0150] According to one or more embodiments, the sensing core node 15 is further configured to perform an update procedure based on a change to at least one of the at least one parameter.
[0151] According to one or more embodiments, the response message comprising one or more of: an identity of the SRH; indication of a backup SRH; weight associated with the SRH; and capabilities of the SRH.
[0152] According to one or more embodiments, the sensing core node 15 is further configured to: transmit, via the SRH, a sensing request from the SRH; and receive sensing data associated with at least one sensing entity, the sensing data satisfying the request.
[0153] According to one or more embodiments, the at least one function includes one or more of: optimizing signaling flows; and performing a sensing task.
[0154] FIG. 13 is a flowchart of another example process in a sensing core node 15 (e.g., core network node 15) according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of sensing core node 15 such as by one or more of processing circuitry 74 (including the SRH unit 17), processor 76, and / or communication interface 72. The sensing core node 15 includes afirst SRH that supports at least one sensing area supported by the RAN node 16. The sensing core node 15 is configured to provide (Block SI 16), using the first SRH, at least one sensing-based function to a client node, as described herein. The sensing node 15 is configured to perform (Block SI 18) at least one function associated with at least one sensing-based function, as described herein.
[0155] According to one or more embodiments, the sensing core node 15 is further configured to: receive a registration message; and transmit a registration response indicating that the RAN node has been: accepted by the sensing core node as a sensing network node for one or both of performing sensing measurements and obtaining sensing data; and registered in the sensing core node 15.
[0156] According to one or more embodiments, the registration message comprises at least one parameter, where the at least one parameter including one or more of: an identity of the RAN node 16; a sensing coverage area of the RAN node 16; a communication address of the RAN node 16; capability information of the RAN node 16; and a secondary sensing unit coordinator associated with the RAN node 16.
[0157] According to one or more embodiments, the sensing core node 15 is further configured to perform an update procedure based on a change to at least one of the at least one parameter; and the update procedure results in a second SRH being used to provide at least one sensing-based function to the client node.
[0158] According to one or more embodiments, the registration response comprises one or more of: an identity of the first SRH; indication of a backup SRH; numerical weight associated with the first SRH; and capabilities of the first SRH.
[0159] According to one or more embodiments, the sensing core node 15 comprises a Sensing Exposure Function, SEF, that is configured to select a Sensing Core Function, SCF, for discovery of a sensing entity to service a sensing request from an Application Function, AF.
[0160] According to one or more embodiments, the SCF is configured to: determine that the RAN node 16 is capable of performing sensing associated with the sensing request; transmit, via the first SRH, the sensing request to the RAN node 16; in response to the sensing request, receive sensing data from the RAN node 16; and the sensing data satisfying the sensing request.
[0161] According to one or more embodiments, the sensing request is associated with one of: environment monitoring; motion monitoring; object detection; and object tracking.According to one or more embodiments, the sensing core node further comprises a Sensing Exposure Data Function, SEDF, and the sensor core node is further configured to provide, using the SEDF, an external sensing data session point of interconnect to an Application Function, AF, or Network Exposure Function, NEF; merge, at the SEDF, sensing data received from a plurality of sensing processing functions; and process, at the SEDF, the sensing data so that privacy- friendly data remains for exposure to the AF or NEF.
[0162] According to one or more embodiments, the sensing core node further comprises a Sensing Repository Function, SRF, and where the sensing core node is configured to receive, at the SRF, a lookup request for a sensing request handler or a sensing processing function; determine, at the SRF based on stored network function profiles, one or more sensing request handlers or sensing processing functions that match the lookup request; and provide, from the SRF, lookup response information comprising one or more of an identity, a serving sensing area, a URI, a load indication, and a backup indication associated with the one or more sensing request handlers or sensing processing functions.
[0163] According to one or more embodiments, the at least one function includes one or more of: optimizing signaling flows; and performing a sensing task.
[0164] Another example process in a sensing core node 15 (e.g., core network node 15) according to some embodiments of the present disclosure is now described. One or more blocks described herein may be performed by one or more elements of sensing core node 15 such as by one or more of processing circuitry 74 (including the SRH unit 17), processor 76, and / or communication interface 72. The sensing core node 15 includes a first SRH that supports at least one sensing area supported by the RAN node 16. The sensing core node 15 is configured to receive a registration message; and transmitting a registration response indicating that the RAN node has been: accepted by the sensing core node as a sensing RAN node for one or both of performing sensing measurements and obtaining sensing data; and registered in the sensing core node.
[0165] For example, in some embodiments, the telecommunication system 10 includes one or more Open-RAN (ORAN) network nodes 16. An ORAN network node 16 is a node in the telecommunication system 10 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other nodes to implement one or more functionalities of any node in the telecommunication system 10, including one or more network nodes 16 in the access network 12 and / or core network nodes 15.Examples of an ORAN network node 16 include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O-CU-CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). The network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an Al, Fl, Wl, El, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN access node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an 0-2 interface defined by the O-RAN Alliance or comparable technologies. The network nodes 16 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 22a, 22b, 22c, and 22d (one or more of which may be generally referred to as UEs 22) to the core network 14 over one or more wireless connections.
[0166] FIG. 14 is a block diagram illustrating a virtualization environment 94 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 94 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment 94 includes components defined by the 0-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an 0-2 interface.
[0167] Applications 96 (which may alternatively be called software instances, virtualappliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment 94 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.
[0168] Hardware 98 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth.
[0169] Software may be executed by the processing circuitry to instantiate one or more virtualization layers 100 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 102a and 102b (one or more of which may be generally referred to as VMs 102), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 100 may present a virtual operating platform that appears like networking hardware to the VMs 102.
[0170] The VMs 102 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 100. Different embodiments of the instance of a virtual appliance 96 may be implemented on one or more of VMs 102, and the implementations may be made in different ways.
[0171] Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.
[0172] In the context of NFV, a VM 102 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non- virtualized machine. Each of the VMs 102, and that part of hardware 98 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs 102 on top of the hardware 98 and corresponds to the application 96.
[0173] Hardware 98 may be implemented in a standalone network node with generic or specific components. Hardware 98 may implement some functions via virtualization. Alternatively, hardware 98 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 104, which, among others, oversees lifecycle management of applications 96. In some embodiments, hardware 98 is coupled to one or more radiounits that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system 106 which may alternatively be used for communication between hardware nodes and radio units.
[0174] Having described the general process flow of arrangements of the disclosure and having provided examples of hardware and software arrangements for implementing the processes and functions of the disclosure, the sections below provide details and examples of arrangements for network functions related to sensing.
[0175] Some embodiments provide network functions related to sensing. One or more network node 16 (e.g., RAN or RAN node) functions described below may be performed by one or more of processing circuitry 36, processor 38, sensing unit 24, communication interface 29, etc. One or more core network node 15 (e.g., sensing core node 15) functions described below may be performed by one or more of processing circuitry 74, processor 76, SRH unit 17, communication interface 72, etc. In one or more embodiments, SRH 17 performs the functions of SRH unit 17.
[0176] NF Registration and Update, RAN
[0177] FIG. 15 is a signaling diagram of an example sensing call flow setup-DNS-CSP according to one or more embodiments of the present disclosure. The steps in FIG. 15 are as follows:
[0178] 1. RAN performs a Sensing Request Handler (SRH 17) discovery, SRH Lookup Request, to find which SRHs 17 to contact upon start
[0179] 2. RAN sends a registration message to the SRH 17 including its own
[0180] 1. Identity
[0181] 2. Sensing coverage area
[0182] 3. Address used for later communication
[0183] 4. Capabilities (optional)
[0184] 5. Secondary SUC (optional)
[0185] 3. The SRH 17 will respond with an acceptance that the new sensing RAN node 16 has been registered in the Sensing Core, SRH 17 including it’s own
[0186] 1. Identity
[0187] 2. Backup SRH (optional)3. Weight (optional), only valid in case of multiple SRHs 17
[0188] 4. Capabilities (optional)
[0189] 4. Both RAN and Core can use the Update procedure if any parameters change, e.g., SUC coverage Area, SRH weight, etc...
[0190] In step 1 RAN discovers the relevant SRH(s) 17 by:
[0191] • pre-configured IP address(s) / FQDN(s)
[0192] • look-up using supported sensing areas, i.e., discovering SRH(s) 17 supporting sensing area(s) supported by the RAN node 16.
[0193] • by finding the nearest SRH(s) 17 where then the SRH(s) 17 gets configured with supported sensing areas through the RAN registration, i.e., SRH(s) 17 will be configured with the sensing areas registered by RAN nodes 16.
[0194] One alternative, is to configure the RAN node manually on the SRH 17 and have that contact each RAN node 16 to subscribe to any area changes.
[0195] One or more embodiments of the proposed solution may be similar to the NG Setup procedure that can be found in 3GPP TS 38.413 but configured for the sensing instead of communication services.
[0196] The Sensing Request Handler 17 would have a similar role in that procedure as the AMF and the RAN node 16 (SUC, Sensing Unit Controller) will have a similar role as the gNB.
[0197] One or more parameters included in step 2 and step 4 are:
[0198] • SUC Area
[0199] • SUC Address (e.g., global RAN node identity)
[0200] • Secondary SUC to use (Optional)
[0201] NF Registration and Update, Core
[0202] FIG. 16 is a signaling diagram of an example sensing call flow setup-CSP-sensing Core according to one or more embodiments of the present disclosure.
[0203] This is similar to the NF Registration, NF Update and NF Discovery procedures in 3GPP TS 29.510 but configured for the sensing instead of communication services. It is more lightweight compared to the communication services with less parameters; one or more example parameters for the SRH, Sensing Request Handler 17 are:
[0204] • SRH Identity
[0205] • Serving Sensing Area
[0206] • SRH URI (FQDN / IP Address)
[0207] • Load• Backup SRH (Optional)
[0208] For the CN UC SPF, Core Network Use Case Sensing Process Function, the similar type of parameters as above are also applicable, but for the SPF, e.g.,
[0209] • SPF Identity
[0210] • Location
[0211] • SPF URI (FQDN / IP Address)
[0212] • Load
[0213] • Capabilities e.g., GPU availability (Optional)
[0214] • Backup SPF (Optional)
[0215] Note: In FIG. 16, the Backup SRH and Backup SPF are called “secondary” SRH / SPF but due to time constraint the use of “secondary” may not be appropriate and instead may must be considered “SRH / SPF” or backup SPF, etc..
[0216] There is the possibility to collapse the Repository and the Exposure functions, as described below.
[0217] Exposure Call flow end-to-end
[0218] FIGS. 17-19 are an example of a sensing call flow.
[0219] FIG. 17 is a diagram of an example sensing call flow - CSP-Sensing Core (part 1 of 3) according to one or more embodiments of the present disclosure. One or more of FIGs. 17-19 may relate to one call flow or process.
[0220] Step 1 may additionally include an end-to-end data stream for the sensing data. For instance, a “Sensing Client Data Result URI” may be included in Step 1 for the case when the CU UC SPF sends the Sensing result directly to the Sensing Client, thus bypassing the SEF, in the Sensing Call Flow (3 of 3)(i.e., FIG. 19 described below) after step 6. These could also be used by a future Data Plane solution. Alternatively, the client could be provided (in the acknowledgement to step 1 or in a later notification) with the “result URI” indicating where to fetch the result.
[0221] Step 3 typically includes the following parameters per SRH instance:
[0222] • SRH Identity
[0223] • Serving Sensing Area
[0224] • SRH URI (FQDN / IP Address)
[0225] • Load
[0226] • Backup SRH 17 (Optional)
[0227] Additionally, in step 3, the SRH 17 receives the SEF DATA URI or the SEDF Data URI so that it can provide them to the CN UC SPF to be used by the CN UC SPFwhen providing results to either the SEF or the SEDF, depending on the reporting alternative which may be selected based on the Sensing Job requested, e.g., if streaming data requested then SEF selects to use the SEDF URL
[0228] Step 5 typically includes the following parameters per SPF instance:
[0229] • SPF Identity
[0230] • Location
[0231] • SPF URI (FQDN / IP Address)
[0232] • Load
[0233] • Capabilities e.g., GPU availability (Optional)
[0234] • Backup SPF (Optional)
[0235] The functional description of the SRF, Sensing Repository Function, may be, for example, as follows:
[0236] • Supports service discovery function. Receive NF Discovery Request from NF instance and provides the information of the discovered NF instances (be discovered) to the NF instance
[0237] • Maintains the NF profile of available NF instances and their supported services.
[0238] • Maintains the health status of NFs.
[0239] The functional description of the SEF, Sensing Exposure Function, may be, for example, as follows:
[0240] • Sensing capabilities and events may be securely exposed by SEF for, e.g., 3rd party, Application Functions.
[0241] • Translation of internal-external information:
[0242] o It translates between information exchanged with the AF and information exchanged with the internal network function. For example, it translates between external Transaction Identifiers and Internal Transaction Identifiers.
[0243] o In particular, SEF handles masking of network and user sensitive information to external AF's according to the network policy, e.g., Target Sensing Areas.
[0244] • Invoking a specific streaming data exposure function and redirecting the internally processed sensing data towards said function.
[0245] FIG. 18 is a signaling diagram of an example sensing call flow-CSP-Sensing Core (part 2 of 3) according to one or more embodiments of the present disclosure.
[0246] The functional description of the SEDF, Sensing Exposure Data Function, may be,for example, as described below:
[0247] • External Sensing Data Session point of interconnect to AF.
[0248] • Merging of data received from several CN UC SPF.
[0249] • Consent management for streaming data i.e., filtering of information for which the consent has changed during the sensing job.
[0250] • Process the data so that only privacy-friendly data remains, e.g., remove humans or at least identifiable humans from a radar image, based on network policies.
[0251] FIG. 19 is a signaling diagram of sensing call flow-CSP-sensing core (3 of 3) according to one or more embodiments of the present disclosure.
[0252] Collapsing the Exposure and Repository Functions
[0253] FIG. 20 is a sensing call flow (collapsed SRF+SEF) according to one or more embodiments of the present disclosure.
[0254] Collapsing the Exposure, Exposure Data and Repository Functions FIG. 21 is a sensing call flow (Collapsed SRF+SEF+SEDF) according to one or more embodiments of the present disclosure.
[0255] Note: further collapsing could exist by sending the Sensing Result Data directly from the CN UC SPF to the Sensing Client (Ref Sensing Call Flow (1 of 3), step 1) thus bypassing the SEDF.
[0256] As an alternative, the SEF could be constructed in the same fashion as the old SGSN (or PGW before splitting into PGW-C and PGW-U), one Control plane part and an additional User plane part. The SEF and SEDF functionalities would thus be combined into a single network function (SEF / SEDF) (also in the repository) and hide its existence by using external stream / data addresses to direct the data to the wanted part of the SEF.
[0257] Authorization of Sensing Service Consumer
[0258] In the following table the entities used in the latest pCR draft (Appendix D) are listed together with the naming used in the previous pCR draft, and entity names used earlier in this document.
[0259] Mapping of entity names
[0260] Sensing Service Consumer Sensing Client
[0261] SnCF(Sensing Core Function) SCF (Sensing Core Function)
[0262] Sensing Request Handler
[0263]
[0264] Sensing Repository Function
[0265] CN UC Sensing Processing Function NEF SEF (Sensing Exposure Function)
[0266] Sensing Exposure Data Function
[0267]
[0268] FIG. 22 is a sequence drawing of a procedure for a requested sensing service authorization according to one or more embodiments of the present disclosure.
[0269] At step 1, a sensing service consumer, e.g. AF, invokes a sensing service request to a NEF. In some implementations, inside the request the sensing service consumer includes the following parameters:
[0270] • AF Identifier (in case a sensing service consumer is an AF), External Target Sensing Area information (e.g., geographical area information and, optionally, altitude information), Type of sensing to perform (e.g., SensingEventType = “Object Detection”, “Object Tracking”), sensing result detail level (e.g., an indication about the detected object, parameter determined, as well as time and / or spatial resolution of the sensing data).
[0271] Some additional (optional) parameters can include:
[0272] • event reporting mode (e.g., one-time, event-triggered or periodic reporting), sensing data exposure parameters (e.g., type of streaming and transport mechanism to be applied in case the streaming of the obtained sensing data is being requested). Other parameters for a sensing service request can be considered and added during the later phases.
[0273] At step 2, the NEF determines whether the sensing service consumer (e.g., AF) is authorized to request sensing services from the network, i.e., to invoke sensing servicespecific APIs.
[0274] At step 3, if the authorization is not granted, the NEF sends the response to the sensing service consumer (e.g., AF) with a Result value indicating that the authorization has failed, and all further steps are skipped.
[0275] At step 4, if the authorization is granted, the NEF sends the sensing service request to the SnCF and includes parameters from the sensing service consumer; if required, the NEF maps them to 3GPP internal parameters.
[0276] At step 5, the SnCF performs a sensing request specific authorization in the implementation specific way, considering, for instance, sensing service consumer NF type, event reporting mode, sensing data exposure parameters, and other parameters from thesensing service request.
[0277] Note that in case a sensing service request is invoked by an NF / AF within the operator’s trust domain, the existing NF discovery and authorization procedures apply.
[0278] At steps 6-7, if the SnCF does not grant the authorization for the requested sensing service operation, the SnCF rejects the request and responds (via NEF) to the sensing service consumer with a Result value indicating that the authorization has failed, and all further steps are skipped.
[0279] At step 8, if the authorization is granted, the sensing service continues to provide the requested sensing result.
[0280] In some implementations, the authorization is performed in two steps:
[0281] • First the NEF authorizes the Sensing Service Consumer (e.g., AF) to ensure the consumer is authorized to access the sensing service-specific APIs from the network.
[0282] • If authorized, the SnCF will proceed with the authorization to ensure the sensing request can be authorized on an operational level. For this, the SnCF authorization is implementation specific, and may consider, for instance, sensing service consumer NF type, event reporting mode, sensing data exposure parameters, and other parameters from the sensing service request (in step 1). In some implementations, these parameters from the sensing service request include: o AF Identifier (in case a sensing service consumer is an AF), External Target Sensing Area information (e.g., geographical area information and, optionally, altitude information), Type of sensing to perform (e.g., SensingEventType = “Object Detection”, “Object Tracking”), sensing result detail level (e.g., an indication about the detected object, parameter determined, as well as time and / or spatial resolution of the sensing data); o Some additional (optional) parameters can include: event reporting mode (e.g., one-time, event-triggered or periodic reporting), sensing data exposure parameters (e.g., type of streaming and transport mechanism to be applied in case the streaming of the obtained sensing data is being requested) which may include IP address, transport protocols etc.
[0283] Accordingly, one or more embodiments described herein provide one or more of the following advantages:
[0284] self-organizing-based solution, i.e., minimum of OPEX required compared to manually configure the solution;saves signaling by assembling / merging the NFs in a logical way for sensing; and
[0285] makes it possible to stream sensing results to an external sensing client. Some Examples
[0286] Example Al. A sensing core node configured to communicate with a network node, the sensing core node including a sensing request handler, SRH, the sensing core node configured to, and / or comprising a radio interface and / or processing circuitry configured to:
[0287] provide, using the SRH, at least one sensing-based function to a network; and perform at least one function associated with the at least one sensing-based function.
[0288] Example A2. The sensing core node of Example Al, wherein the sensing core node is further configured to:
[0289] receive a registration message; and
[0290] transmit a registration response indicating that the network node has been:
[0291] accepted by the sensing core node as a sensing network node; and registered in the sensing core node.
[0292] Example A3. The sensing core node of Example A2, wherein the registration message comprises at least one parameter, the at least one parameter including one or more of:
[0293] an identity of the network node;
[0294] a sensing coverage area of the network node;
[0295] a communication address of the network node;
[0296] capability information of the network node; and
[0297] a secondary sensing unit coordinator associated with the network node.
[0298] Example A4. The sensing core node of Example A3, wherein the sensing core node is further configured to perform an update procedure based on a change to at least one of the at least one parameter.
[0299] Example A5. The sensing core node of any one of Examples A2-A4, wherein the response message comprising one or more of:
[0300] an identity of the SRH;
[0301] indication of a backup SRH;
[0302] weight associated with the SRH; and
[0303] capabilities of the SRH.Example A6. The sensing core node of any one of Examples A1-A5, wherein the sensing core node is further configured to:
[0304] transmit, via the SRH, a sensing request from the SRH; and
[0305] receive sensing data associated with at least one sensing entity, the sensing data satisfying the request.
[0306] Example A7. The sensing core node of any one of Examples A1-A6, wherein the at least one function includes one or more of:
[0307] optimizing signaling flows; and
[0308] performing a sensing task.
[0309] Example Bl. A method implemented by a sensing core node that is configured to communicate with a network node, the sensing core node including a sensing request handler, SRH, the method comprising:
[0310] providing, using the SRH, at least one sensing-based function to a network; and performing at least one function associated with the at least one sensing-based function.
[0311] Example B2. The method of Example Bl, further comprising:
[0312] receiving a registration message; and
[0313] transmitting a registration response indicating that the network node has been: accepted by the sensing core node as a sensing network node; and registered in the sensing core node.
[0314] Example B3. The method of Example B2, wherein the registration message comprises at least one parameter, the at least one parameter including one or more of: an identity of the network node;
[0315] a sensing coverage area of the network node;
[0316] a communication address of the network node;
[0317] capability information of the network node; and
[0318] a secondary sensing unit coordinator associated with the network node.
[0319] Example B4. The method of Example B3, further comprising performing an update procedure based on a change to at least one of the at least one parameter.
[0320] Example B5. The method of any one of Examples B2-B4, wherein the response message comprising one or more of:
[0321] an identity of the SRH;
[0322] indication of a backup SRH;
[0323] weight associated with the SRH; andcapabilities of the SRH.
[0324] Example B6. The method of any one of Examples B1-B5, further comprising: transmitting, via the SRH, a sensing request from the SRH; and
[0325] receiving sensing data associated with at least one sensing entity, the sensing data satisfying the request.
[0326] Example B7. The method of any one of Examples B1-B6, wherein the at least one function includes one or more of:
[0327] optimizing signaling flows; and
[0328] performing a sensing task.
[0329] Example Cl. A network node configured to communicate with a sensing core node, the network node configured to, and / or comprising a radio interface and / or comprising processing circuitry configured to:
[0330] discover a sensing request handler, SRH of a core node;
[0331] cause transmission of a registration message to the SRH; and
[0332] receive a registration response indicating that the network node has been:
[0333] accepted by the sensing core node as a sensing network node; and registered in the sensing core node.
[0334] Example C2. The network node of Example Cl, wherein the registration message comprises at least one parameter, the at least one parameter including one or more of: an identity of the network node;
[0335] a sensing coverage area of the network node;
[0336] a communication address of the network node;
[0337] capability information of the network node; and
[0338] a secondary sensing unit coordinator associated with the network node.
[0339] Example C3. The network node of any one of Examples C1-C2, wherein the network node is further configured to perform an update procedure based on a change to at least one of the at least one parameter.
[0340] Example C4. The network node of any one of Examples C1-C3, wherein the response message comprising one or more of:
[0341] an identity of the SRH;
[0342] indication of a backup SRH;
[0343] weight associated with the SRH; and
[0344] capabilities of the SRH.Example C5. The network node of any one of Examples C1-C4, wherein the discovery of the SRH includes discovering at least one SRH that support at least one sensing area of the network node.
[0345] Example C6. The network node of any one of Examples C1-C5, wherein the network node is further configured to:
[0346] receive a sensing request from the SRH;
[0347] select at least one sensing entity to satisfy the sensing request; and
[0348] indicate sensing data associated with the at least one sensing entity.
[0349] Example DI. A method implemented by a network node that is configured to communicate with a sensing core node, the method comprising:
[0350] discovering a sensing request handler, SRH of a core node;
[0351] transmitting of a registration message to the SRH; and
[0352] receiving a registration response indicating that the network node has been:
[0353] accepted by the sensing core node as a sensing network node; and registered in the sensing core node.
[0354] Example D2. The method of Example DI , wherein the registration message comprises at least one parameter, the at least one parameter including one or more of: an identity of the network node;
[0355] a sensing coverage area of the network node;
[0356] a communication address of the network node;
[0357] capability information of the network node; and
[0358] a secondary sensing unit coordinator associated with the network node.
[0359] Example D3. The method of any one of Examples D1-D2, further comprising performing an update procedure based on a change to at least one of the at least one parameter.
[0360] Example D4. The method of any one of Examples D1-D3, wherein the response message comprising one or more of:
[0361] an identity of the SRH;
[0362] indication of a backup SRH;
[0363] weight associated with the SRH; and
[0364] capabilities of the SRH.
[0365] Example D5. The method of any one of Examples D1-D4, wherein the discovery of the SRH includes discovering at least one SRH that support at least one sensing area of the network node.Example D6. The method of any one of Examples D1-D5, further comprising: receiving a sensing request from the SRH;
[0366] selecting at least one sensing entity to satisfy the sensing request; and indicating sensing data associated with the at least one sensing entity.
[0367] Embodiment El. A method implemented by a sensing core node that is configured to communicate with a network exposure node, the method comprising:
[0368] receiving, from the network exposure node, a sensing service request conditionally based on the sensing service request being first authorized by the network exposure node for consumer access;
[0369] performing second authorization for the sensing service request on an operational level; and
[0370] executing the sensing service conditionally based on the second authorization by the sensing core node being successful.
[0371] Embodiment E2. A method of Embodiment El , wherein performing the second authorization comprises considering one or more of sensing service consumer NF type, event reporting mode, sensing data exposure parameters, and other parameters from the sensing service request.
[0372] Embodiment E3. A method of Embodiment El or E2, wherein performing the second authorization comprises considering one or more of AF Identifier (in case a sensing service consumer is an AF), External Target Sensing Area information (e.g., geographical area information and, optionally, altitude information), Type of sensing to perform (e.g., SensingEventType = “Object Detection”, “Object Tracking”), sensing result detail level (e.g., an indication about the detected object, parameter determined, as well as time and / or spatial resolution of the sensing data).
[0373] Embodiment E4. A method of any of Embodiments El to E3, wherein performing the second authorization comprises considering one or more of event reporting mode (e.g., one-time, event-triggered or periodic reporting), sensing data exposure parameters (e.g., type of streaming and transport mechanism to be applied in case the streaming of the obtained sensing data is being requested) which may include IP address, transport protocols etc.
[0374] Embodiment E5. A sensing core node, comprising:
[0375] a network interface configured to communicate with other network nodes; and processing circuitry coupled to the network interface, wherein the processing circuitry is configured to implement a method according to any of Embodiments El to E4.STANDARDIZING THE PROPOSED SOLUTIONS
[0376] Below are provide non-limiting examples of how certain aspects of the proposed solutions could be implemented within the framework of a specific communication standard. In particular, one or more embodiments described below provides non-limiting examples of how the proposed solutions could be implemented within the framework of a 3GPP TSG RAN standard. The changes described below are merely intended to illustrate how certain aspects of the proposed solutions could be implemented in a particular standard. However, the proposed solutions could also be implemented in other suitable manners, both in the 3GPP Specification and in other specifications or standards.
[0377] KI#3, a new solution: Discovery and selection of NFs for the AF-requested sensing service
[0378] This contribution proposes a new solution for KI#3 that introduces aspects on how to discover and select network functions for the AF-requested sensing service.
[0379] 1. Discussion
[0380] This contribution proposes a new solution for KI#3 that introduces aspects on how to discover and select network functions for the AF-requested sensing service.
[0381] 2. Text Proposal
[0382] It is proposed to agree the following solution to 3GPP TR 23.700-14.
[0383] »» Start of Changes ««
[0384] 6.0 Mapping of Solutions to Key Issues
[0385] Table 6.0-1: Mapping of Solutions to Key Issues
[0386] Key Issues
[0387] Solutions #1 #2 #3 #4 #5 #6 #Y X
[0388] #2
[0389]
[0390] »» Next Change (all new text)««
[0391] 6.Z Solution #Z: Selecting NFs for the AF-requested sensing service
[0392] 6.Z.1 High-level solution principles
[0393] The solution is based on following principles:
[0394] To be added once the solution is stable.
[0395] 6.Z.2 Functional DescriptionThe solution is built upon the KI#5 solution on Exposing Sensing Results to an AF (see S2-250xxxxx for details) and includes the following aspects applied to discover and select network functions for handling an AF-request sensing services:
[0396] Sensing Exposure Function (SEF) may discover a Sensing Core Function (SCF) by invoking the service from the network repository function for which (External) Target Sensing Area information from the AF request can be used.
[0397] Alternatively, SCF information may be available to the SEF by other means, e.g., locally configured at the SEF. A network can also be configured with only one SCF if that is a choice of the deployment.
[0398] SCF discovers and selects NG-RAN node(s) capable of performing the authorized type of sensing and relevant to the Target Sensing Area based on the information from 0AM on NG-RAN supported sensing capabilities, supported area for sensing etc.
[0399] 6.Z.3 Procedures
[0400] Additional steps are added to the procedure in clause 6.X.4 (reflecting the solution for KI#5 on “Exposing Sensing Results to an AF”) to include aspects related to the discovery and selection of NFs for handling a sensing service request in the network:
[0401] Step 2: The Sensing Core Function (SCF) discovery and selection functionality is supported by the Sensing Exposure Function (SEF) to determine an SCF to handle the requested sensing service in the network.
[0402] To perform SCF discovery and selection, the SEF may utilize a repository function with the (External) Target Sensing Area information as an input for discovering an SCF.
[0403] NOTE Z1 : Information about External Target Sensing Area can be included by the AF inside the request for a sensing service to the network and mapped by the SEF in to 3GPP internal Target Sensing Area information.
[0404] Alternatively, SCF information may be available by other means, e.g., locally configured at the SEF. The SEF selects the SCF instance(s) based on the available SCF instance(s) or from the locally configured SCF instance(s).
[0405] NOTE Z2: The locally configured SCF instance(s) at the SEF can be used, for instance, to select a specific SCF instance for the sensing request from the AF invoking the sensing service.
[0406] NOTE Z3: As the deployment choice the network can be configured with one SCF.Step 4: The SCF obtains the NG-RAN information (e.g., supported sensing capabilities, supported area for sensing) via OAM. Once the SCF receives a sensing service request from the SEF, the SCF selects the NG-RAN node based on the received Target Sensing Area information from the SEF, other information in the AF request (e.g., type of sensing event, start and destination points for the object tracking) and the NG-RAN information configured by OAM (e.g., supported sensing capabilities, supported area for sensing).
[0407] NOTE Z4: Target Sensing Area can span the supported sensing area of one or multiple NG-RAN node(s) or can be a fraction of a supported sensing area of a single NG-RAN node.
[0408] 6.Z.4 Impacts on existing services, entities and interfaces
[0409] NEF:
[0410] NOTE Z5: Impacts on NEF depend on KI#1 outcome and whether SEF will be a part of NEF in particular.
[0411] Sensing Exposure Function (SEF):
[0412] discovers and selects a Sensing Core Function (SCF) for handling the sensing service in the core network;
[0413] SCF information may be locally configured at the SEF.
[0414] Sensing Core Function (SCF):
[0415] discovers and selects an NG-RAN node based on the pre-configured information and the information in the sensing service request from the AF.
[0416] »» End of Changes ««
[0417] KI#2, a new solution: AF-requested sensing service authorization by the network This contribution proposes a new solution for KI#2 that introduces aspects of the AF-requested sensing service authorization by the network.
[0418] 1. Discussion
[0419] This document proposes a new solution for KI#2 that introduces aspects of the AF-requested sensing service authorization by the network.
[0420] 2. Text Proposal
[0421] It is proposed to agree the following solution to 3GPP TR 23.700-14.
[0422] »» Start of Changes ««
[0423] 6.0 Mapping of Solutions to Key Issues
[0424] Table 6.0-1: Mapping of Solutions to Key Issues
[0425] Key Issues
[0426]
[0427] Solutions #1 #2 #3 #4 #5 #6 #Y X
[0428] #2
[0429]
[0430] »» Next Change (all new text)««
[0431] 6. Y Solution #XY : AF-requested sensing service authorization by the network 6. Y.1 High-level solution principles
[0432] The solution is based on following principles:
[0433] To be added once the solution is stable.
[0434] 6.Y.2 Functional Description
[0435] The solution is built upon the KI#5 solution on Exposing Sensing Results to an AF (see S2-250xxxxx for details) and includes the following authorization aspects:
[0436] AF Authorization Data is introduced and used by the Sensing Exposure Function (SEF) to perform the authorization outcome. The AF authorization Data contain an AF ID, description of an allowed area for sensing, type of sensing the AF is allowed to request, and level of details the sensing result and data can be provided to the AF.
[0437] 6.Y.3 Procedures
[0438] Additional steps are added to the procedure in clause 6.X.4 (reflecting the solution for KI#5 on “Exposing Sensing Results to an AF”) to include the AF request authorization aspects:
[0439] Step 2: Sensing Exposure Function (SEF) performs the AF request authorization based on a service level agreement (SLA) between the 3rd party AF that invokes the sensing service request and the 5GS of the mobile network operator, the operator policy and local configuration.
[0440] Editor's note: The AF authorization needs to be coordinated and confirmed with SA WG3.
[0441] The information needed to support the authorization of the AF for performing the sensing service is given in Table 6.Y.3-1. This information (i.e., AF Authorization Data) are either retrieved from the network or configured locally at the SEF. When the SCF retrieves the AF Authorization Data from the network (e.g., one of the 5GC NFs), the SEF also subscribes to the changes of the AF Authorization Data.
[0442] Table 6.Y.3-1: AF Authorization Data for sensing services
[0443] AF Authorization Data Description
[0444] AF ID Identifier used to identify the AF.
[0445]
[0446] Allowed sensing area Indicate the allowed area for the indicated AF to perform the sensing services operations.
[0447] Allowed sensing service Indicate the allowed service operation (s) operations for the indicated AF, e.g. environment monitoring, motion monitoring, object detection, object tracking.
[0448] Allowed sensing result Indicate whether the AF is authorized to detail level request sensing result in the form of notifications about sensing event and / or more detailed sensing result in terms of obtained sensing data is also allowed.
[0449]
[0450] NOTE Yl: Other information that can be used for authorization of the AF requesting a sensing service can be determined during the normative phase.
[0451] Editor's note: Where the network stores AF Authorization Data is FFS.
[0452] Editor's note: Whether other NFs need to perform any type of authorization can be further considered and is FFS.
[0453] 6.X.4 Impacts on existing services, entities and interfaces
[0454] NEF:
[0455] NOTE Y2: Impacts on NEF depend on KI#1 outcome and whether SEF will be a part of NEF in particular.
[0456] Sensing Exposure Function (SEF):
[0457] performs AF authorization for the sensing service;
[0458] retrieves AF Authorization Data from the network entity (if applicable) or has them stored locally
[0459] »» End of Changes ««
[0460] KI#5, a new solution: Baseline for exposing sensing results to an AF
[0461] This contribution proposes a new solution for KI#5 that aims at providing a baseline for exposing sensing results to an AF.
[0462] 1. Discussion
[0463] This document proposes a new solution for KI#5 that aims at providing a baseline for exposing sensing results to an AF.
[0464] 2. Text ProposalIt is proposed to agree the following solution to 3GPP TR 23.700-14.
[0465] »» Start of Changes ««
[0466] 6.0 Mapping of Solutions to Key Issues
[0467] Table 6.0-1: Mapping of Solutions to Key Issues
[0468] Key Issues
[0469] Solutions #1 #2 #3 #4 #5 #6 #X X
[0470] #2
[0471]
[0472] »» Next Change (all new text)««
[0473] 6.X Solution #XY : Exposing Sensing Results to an AF
[0474] 6.X.1 High-level solution principles
[0475] The solution is based on following principles:
[0476] AF invokes a sensing service request to a Sensing Exposure Function (SEF) - a new entity in the core network. The SEF authorizes the AF request and, if authorized, discovers and selects a Sensing Core Function (SCF). The SCF is a new CN NF that handles the sensing service request in the core network.
[0477] The SCF discovers and selects NG-RAN node(s) capable of performing the authorized type of sensing and relevant to the Target Sensing Area. The SCF instructs the selected NG-RAN to obtain the sensing data.
[0478] The NG-RAN provides the obtained sensing data to the SCF for sensing result determination and / or for further exposure to the SEF and the AF.
[0479] 6.X.2 Impacts on the Key Issues
[0480] This solution addresses KI#5 aspect related to how the core network exposes sensing results to the sensing service consumer. However, the solution impacts also other key issue, and the impact could be the following:
[0481] KI#1: New core network functions are being considered - Sensing Core Function (SCF) that handles sensing request in the core network and Sensing Exposure Function (SEF) that can be used to expose the obtained sensing result to the sensing service consumer (i.e., AF that invoked the sensing service request)
[0482] KI#2: AF authorization is performed by SEF.
[0483] KI#3: SCF selection is performed by the SEF; the SCF selects an NG-RAN node to perform sensing data collection.KI#4: NG-RAN obtained sensing data are transferred to the SCF for sensing result determination and, if applicable, to the SEF for the exposure to the AF.
[0484] KI#6: SCF includes the sensing operation specific parameters as inputs inside a sensing request to the selected NG-RAN node(s).
[0485] 6.X.3. Functional Description
[0486] The following scenario is considered for this solution. An application function (AF) invokes a sensing service to request the network to perform either (i) environment monitoring, (ii) motion monitoring, (Hi) object detection, or (iv) object detection and tracking. The AF also may request a sensing result detail level to be exposed, i.e. sensing outcome (e.g., indication whether the object has been detected or not) or a more detailed description of what has been sensed by the 5GS (e.g. sensing data is a certain form). In this case, the AF acts as a sensing service consumer and a sensing service requester. The AF request is sent to a new NF - Sensing Exposure Function (SEF) that performs authorization of the AF requested sensing service.
[0487] If the AF request is authorized, the SEF selects a Sensing Core Function (SCF) that handles the sensing service request and the invokes the corresponding sensing service operation to the selected SCF. The SCF discovers and selects a NG-RAN node(s) to handle the core network-requested sensing service (e.g., object tracking in a certain area). The NG-RAN node may take a role of a Sensing Entity, perform sensing measurements, and obtain sensing data. The NG-RAN node provides the obtained sensing data to the SCF for sensing result determination and / or sensing data exposure, if applicable, to the AF via the SEF.
[0488] NOTE XI: Roles and functionalities of the involved NFs (e.g. SEF, SCF and NG-RAN) can change depending on the resolution of the ENs in the procedure, see clause 6.X.4.
[0489] 6.X.4 Procedures
[0490] Procedures for sensing result exposure in cases when an AF invokes the sensing service towards a core network in shown in FIG. 23.
[0491] FIG. 23 is a signaling diagram of a procedure of sensing result exposure to an AF, where several steps are described below.
[0492] 1. The Sensing service consumer (e.g. AF) invokes a sensing service request (e.g., Nsef_SensingEvent_Subscribe) to the SEF. Inside the request the AF include the following mandatory and optional parameters:
[0493] Editor's note: Whether the SEF can be a part of NEF is FFS and outcome of KI#1.mandatory, AF Identifier;
[0494] mandatory, External Target Sensing Area information (e.g., geographical area information and, optionally, altitude information);
[0495] mandatory, Type of sensing to perform (e.g., SensingEventType = “Environment Monitoring”, “Motion Monitoring”, “Object Detection”, “Object Tracking”);
[0496] mandatory, sensing result detail level to report (e.g., notifications with, for example, an indication about the determined sensing result (“Object detected”, “Parameter estimated”) or a more detailed description of sensing data that can be used for the sensing result determination);
[0497] optionally, sensing periodicity (e.g., one-time reporting, periodic or event-triggered sensing;
[0498] optionally, sensing data exposure parameters (e.g., time and / or spatial resolution of the sensing data, type of streaming and transport mechanism to be applied in case the streaming of the obtained sensing data is being requested, etc.)
[0499] NOTE X2: Other parameters that AF can include in a sensing service request can be added during the study phase or later during the normative phase.
[0500] NOTE X3: The exact names of service operations and semantics can be determined during the normative phase.
[0501] 2. The SEF performs the AF-requested sensing service authorization.
[0502] NOTE X4: Data used for the AF-requested sensing service authorization and other details on how SEF authorizes the AF request is outcome of KI#2.
[0503] Editor's note: Whether the SEF performs the consent check per AF identity is FFS and needs coordination with SA WG3.
[0504] If the AF request for sensing service is authorized, the SEF maps the External Target Sensing Area information in the AF request to a 3GPP-internal Target Sensing Area information and then discovers and selects a SCF to handle the sensing service request. NOTE X5: How a SCF is discovered and selected is outcome of KI#3.
[0505] Editor's note: How Target Sensing Area information to be described is FFS and needs to be coordinated with RAN WGs.
[0506] 3. The SEF invokes the corresponding sensing service request (e.g.
[0507] Nscf_SensingEvent_Subscribe) to the selected SCF and provides the relevant sensing service parameters from Step 1.4. The SCF discovers and selects NG-RAN node(s) capable of performing the authorized type of sensing and relevant to the Target Sensing Area of the authorized sensing service.
[0508] NOTE 6: How the SCF discovers and selects NG-RAN node(s) to handle the AF-requested sensing service is covered by solutions for KI#3 of this study.
[0509] Editor's note: Whether the SCF needs to perform authorization of sensing operations is FFS and depends on type of sensing operations, sensing entities involved, and outcome of KI#2.
[0510] 5. The SCF sends the sensing service request to the selected NG-RAN node. Inside the request, the SCF includes, for instance, Target Sensing Area information, type of sensing to perform, relevant parameters from the AF request in Step 1 , and other relevant parameters derived by the SCF for the authorized sensing service.
[0511] 6. Based on the received sensing service request from the SCF, the NG-RAN starts obtaining sensing data with / without taking a role of a Sensing Entity.
[0512] Editor's note: How sensing measurements are performed and how the NG-RAN obtained the sensing data are RAN WGs decisions and are FFS.
[0513] Editor's note: Whether the NG-RAN can also perform determination of the sensing result depends on further clarification of the scope of this study and RAN WGs decision.
[0514] 7. The NG-RAN provides the sensing data to the SCF for sensing result determination, sensing result and / or sensing data exposure if applicable.
[0515] NOTE X7: How the NG-RAN provides the obtained sensing data to the SCF is covered by KI#4 of this study.
[0516] 8a. The SCF may determine the sensing result considering the sensing result detail level included in the request.
[0517] NOTE X8: How the SCF uses the sensing data to determine a sensing result is up to implementation.
[0518] 9a. The SCF may notify the SEF using the Nscf_SensingEvent_Notify service operation about the determined sensing result.
[0519] 10a. The SEF forwards the received notification from the SCF to the AF using the Nsef_SensingEvent_Notify service operation.
[0520] 8b. The SCF may process the received sensing data considering the sensing result detail level from the AF request in Step 1 , and then the SCF may provide the processed sensing data to the SEF for the exposure.NOTE X9: How the SCF process the sensing data considering the sensing result detail level is up to implementation.
[0521] NOTE X10: How the SCF provides the received / processed sensing data to the SEF is covered by KI#4 of this study.
[0522] 9b. The SEF may store the provided sensing data and prepare the sensing data for exposure using the parameters for sensing data exposure from the AF request in Step 1.
[0523] 10b. The SEF may expose the sensing data to the AF according to the sensing result detail level and sensing data exposure parameters authorized for the AF request. 6.X.5 Impacts on existing services, entities and interfaces
[0524] AF:
[0525] acts as a Sensing Service Consumer by sending a sensing service request to the core network and consuming the sensing result and sensing data (if applicable).
[0526] NEF:
[0527] NOTE XI 1 : Impacts on NEF depend on KI#1 outcome and whether SEF will be a part of NEF in particular.
[0528] Sensing Exposure Function (SEF):
[0529] performs AF request authorization for the sensing service;
[0530] discovers and selects a Sensing Core Function (SCF) for handling the sensing service in the core network;
[0531] maps an Externals Target Sensing area information to an internal Target Area Sensing Area information;
[0532] exposes the determined sensing result and / or sensing data, if applicable, to a sensing service consumer (i.e., AF).
[0533] Sensing Core Function (SCF):
[0534] discovers and selects an NG-RAN node capable of sensing for a specific service;
[0535] may collect the obtained sensing data from the NG-RAN for determination of a sensing result;
[0536] may determine a sensing result based on the collected sensing data; may process and provide the received sensing data to the SEF for storage and / or exposure to the AF.
[0537] may notify the AF (via SEF) about the sensing result.
[0538] NG-RAN:may take a role of a Sensing Entity for the requested sensing service from the SCF;
[0539] may obtain sensing data based on the sensing service request from the SCF; may provide the collected sensing data to the SCF.
[0540] »» End of Changes ««
[0541] 6.X Solution #X: Exposing Sensing Results to an AF
[0542] 6.X.1 High-level solution principles
[0543] The solution is based on following principles:
[0544] - AF invokes a sensing service request to an NEF. The NEF authorizes the AF, and, if authorized, selects a Sensing Core Function (SnCF). The SnCF is a new CN NF that handles the sensing service request in the core network.
[0545] - The SnCF selects NG-RAN node(s) for the relevant Target Sensing Area of the authorized sensing service. The SnCF requests the selected NG-RAN node(s) to obtain the sensing data.
[0546] - The NG-RAN node(s) provide sensing data to the SnCF for sensing result determination, if applicable, and / or for further exposure towards the AF.
[0547] 6.X.2 Impacts on the Key Issues
[0548] This solution addresses KI#5 aspect related to how the core network exposes sensing data and / or sensing results to the sensing service consumer. However, the solution impacts also other key issue, and the impact could be the following:
[0549] - KI#1: New core network functions are being considered - Sensing Core Function (SnCF) that handles sensing request in the core network, and NEF is used to expose the obtained sensing data and / or sensing results.
[0550] - KI#2: AF authorization is performed by the NEF.
[0551] - KI#3: NEF selects an SnCF, the SnCF selects NG-RAN node(s) to perform sensing data collection.
[0552] - KI#4: NG-RAN node(s) determine the sensing result or transfer the sensing data to the SnCF for sensing result determination.
[0553] - KI#6: SnCF includes the sensing operation specific parameters as inputs inside a sensing request to the selected NG-RAN node(s).
[0554] 6.X.3. Functional Description
[0555] The following scenario is considered for this solution. An application function (AF) invokes a sensing service to request the network to perform (i) object detection or (ii) object detection and tracking. The AF also may request a sensing result detail level to beexposed, i.e. sensing outcome (e.g., indication whether the object has been detected or not) or a more detailed description of what has been sensed by the 5GS (e.g. sensing data is a certain form). In this case, the AF acts as a sensing service consumer and a sensing service requester. The AF request is sent to the NEF.
[0556] The NEF selects a Sensing Core Function (SnCF) that will handle the sensing service request. The NEF invokes the corresponding sensing service operation to the selected SnCF. The SnCF selects a NG- RAN node(s) for the core network-requested sensing service and invokes the corresponding sensing service request(s).
[0557] The NG-RAN node(s) collects sensing data, determines the sensing result, if applicable, or provides the obtained sensing data to the SnCF for further sensing result determination and / or sensing data exposure.
[0558] NOTE XI: Roles and functionalities of the involved NFs (e.g. NEF, SnCF and NG- RAN) can change depending on the resolution of the ENs in the procedure, see clause 6.X.4.
[0559] 6.X.4 Procedures
[0560] Procedure for sensing result exposure in cases when a sensing service consumer (e.g., AF) invokes the sensing service towards a core network is shown in FIG 22.
[0561] FIG. 23 is a signaling diagram of a procedure of sensing result exposure to an AF, where several steps are described below.
[0562] 1. The Sensing service consumer (e.g., AF) invokes a sensing service request (e.g., Nnef_SensingEvent_Subscribe) to the NEF. Inside the request the AF includes the following mandatory and optional parameters:
[0563] - mandatory: AF Identifier, External Target Sensing Area information (e.g., geographical area information and, optionally, altitude information), Type of sensing to perform (e.g., SensingEventType = “Object Detection”, “Object Tracking”), sensing result detail level (e.g., an indication about the detected object, parameter determined, and / or time and / or spatial resolution of the sensing data);
[0564] - optional: event reporting mode (e.g., one-time, event-triggered or periodic reporting), sensing data exposure parameters (e.g., type of streaming and transport mechanism to be applied in case the streaming of the obtained sensing data is being requested).
[0565] NOTE X3: Other parameters that AF can include in a sensing service request can be added during the later phases.NOTE X4: The exact names of service operations and semantics can be determined in the later phase.
[0566] 2. The NEF performs the authorization of the AF for the sensing service.
[0567] NOTE X5: Data used for the AF-requested sensing service authorization and other details on how the NEF authorizes the AF request is outcome of KI#2.
[0568] Editor's note: Whether the NEF performs the consent check per AF identity is FFS and needs coordination with SA WG3.
[0569] If the AF request for sensing service is authorized, the NEF maps the External Target Sensing Area information in the AF request to a 3GPP-internal Target Sensing Area information and then discovers and selects an SnCF to handle the sensing service request.
[0570] NOTE X6: How the NEF selects an SnCF is outcome of KI#3.
[0571] Editor's note: How Target Sensing Area information needs to be described is FFS and requires coordination with RAN WGs.
[0572] 3. The NEF invokes the corresponding sensing service request (e.g.
[0573] Nsncf_SensingEvent_Subscribe) to the selected SnCF and provides the relevant sensing service parameters from the AF request in Step 1.
[0574] 4. The SnCF selects NG-RAN node(s) for the relevant Target Sensing Area of the authorized sensing service.
[0575] NOTE X7: How the SnCF selects NG-RAN node(s) to handle the AF-requested sensing service is covered by solutions for KI#3 of this study.
[0576] NOTE X8: How the SnCF authorizes the sensing service operation, if applicable, is the outcome of KI#2 of this study.
[0577] 5. The SnCF sends the sensing service request to the selected NG-RAN node(s). Inside the request, the SnCF includes, for instance, Target Sensing Area information, type of sensing to perform, relevant parameters from the AF request in Step 1 , and other parameters derived by the SnCF for the authorized sensing service.
[0578] 6. Based on the received sensing service request from the SnCF, the NG-RAN node(s) starts obtaining sensing data.
[0579] NOTE X9: How sensing measurements are performed and how the NG-RAN node(s) obtain the sensing data are RAN WGs decisions.
[0580] 7. The NG-RAN node(s) may perform determination of a sensing result.
[0581] Editor’s note: Whether NG-RAN nodes can perform determination of a sensing result is FFS and needs to be coordinated with RAN WGs.8. The NG-RAN node(s) provides the sensing result / data to the SnCF.
[0582] NOTE X10: How the NG-RAN node(s) provides the obtained sensing result / data to the SnCF is covered by KI#4 of this study.
[0583] 9a. The SnCF may determine the sensing result considering the sensing result detail level included in the AF request in Step 1.
[0584] NOTE XI 1 : How the SnCF uses the sensing data to determine a sensing result is up to implementation.
[0585] 10a. The SnCF may notify the NEF using the Nsncf_SensingEvent_Notify service operation about the determined sensing result.
[0586] lla. The NEF forwards the received notification from the SnCF to the AF using the Nnef_SensingEvent_Notify service operation.
[0587] 9b. The SnCF may process the received sensing data considering the sensing result detail level from the AF request in Step 1 ,
[0588] 10b. The SnCF may provide the processed sensing data to the NEF for the exposure. NOTE X12: How the SnCF processes the sensing data considering the sensing result detail level is up to implementation.
[0589] NOTE XI 3: How the SnCF provides the sensing data to the NEF is covered by KI#4 of this study.
[0590] llb. The NEF may cache the provided sensing data and prepare the sensing data for exposure using the parameters for sensing data exposure from the AF request in Step 1.
[0591] 12b. The NEF may expose the sensing data to the AF according to the sensing result detail level and sensing data exposure parameters authorized for the AF request. 6.X.5 Impacts on existing services, entities and interfaces
[0592] AF:
[0593] - acts as a Sensing Service Consumer by sending a sensing service request to the core network and consuming the sensing result and sensing data (if applicable).
[0594] Network Exposure Function (NEF):
[0595] - performs sensing service consumer (e.g., AF) authorization;
[0596] - selects a Sensing Core Function (SnCF) for handling the sensing service in the core network;
[0597] - maps an External Target Sensing area information to an internal Target Sensing Area information;- may cache and expose the determined sensing result and / or sensing data, if applicable, to a sensing service consumer (e.g., AF).
[0598] Sensing Core Function (SnCF):
[0599] - selects NG-RAN node(s) capable of sensing for a specific service;
[0600] - may collect the obtained sensing data from the NG-RAN node(s) for determination of a sensing result;
[0601] - may determine a sensing result based on the collected sensing data;
[0602] - may process and provide the received sensing data to the NEF for exposure to the AF; - may notify (via NEF) the sensing service consumer (e.g., AF) about the sensing result. NG-RAN:
[0603] - may obtain sensing data based on the sensing service request from the SnCF;
[0604] - may provide the collected sensing data to the SnCF;
[0605] - may determine a sensing result.
[0606] As will be appreciated by one of skill in the art, the concepts described herein may be embodied as a method, data processing system, computer program product and / or computer storage media storing an executable computer program. Accordingly, the concepts described herein may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects all generally referred to herein as a “circuit” or “module.” Any process, step, action and / or functionality described herein may be performed by, and / or associated to, a corresponding module, which may be implemented in software and / or firmware and / or hardware. Furthermore, the disclosure may take the form of a computer program product on a tangible computer usable storage medium having computer program code embodied in the medium that can be executed by a computer. Any suitable tangible computer readable medium may be utilized including hard disks, CD-ROMs, electronic storage devices, optical storage devices, or magnetic storage devices.
[0607] Some embodiments are described herein with reference to flowchart illustrations and / or block diagrams of methods, systems and computer program products. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer (to thereby create a special purpose computer), special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processorof the computer or other programmable data processing apparatus, create means for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks.
[0608] These computer program instructions may also be stored in a computer readable memory or storage medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture including instruction means which implement the function / act specified in the flowchart and / or block diagram block or blocks.
[0609] The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks.
[0610] It is to be understood that the functions / acts noted in the blocks may occur out of the order noted in the operational illustrations. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality / acts involved. Although some of the diagrams include arrows on communication paths to show a primary direction of communication, it is to be understood that communication may occur in the opposite direction to the depicted arrows.
[0611] Computer program code for carrying out operations of the concepts described herein may be written in an object oriented programming language such as Python, Java® or C++. However, the computer program code for carrying out operations of the disclosure may also be written in conventional procedural programming languages, such as the "C" programming language. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer. In the latter scenario, the remote computer may be connected to the user's computer through a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).Many different embodiments have been disclosed herein, in connection with the above description and the drawings. It will be understood that it would be unduly repetitious and obfuscating to literally describe and illustrate every combination and subcombination of these embodiments. Accordingly, all embodiments can be combined in any way and / or combination, and the present specification, including the drawings, shall be construed to constitute a complete written description of all combinations and subcombinations of the embodiments described herein, and of the manner and process of making and using them, and shall support claims to any such combination or subcombination.
[0612] It will be appreciated by persons skilled in the art that the embodiments described herein are not limited to what has been particularly shown and described herein above. In addition, unless mention was made above to the contrary, it should be noted that all of the accompanying drawings are not to scale. A variety of modifications and variations are possible in light of the above teachings without departing from the scope of the following claims.
Claims
CLAIMS:
1. A method implemented by a sensing core node (15) that is configured to communicate with a Radio Access Network, RAN, node (16), the sensing core node (15) including a first sensing request handler, SRH (17), that supports at least one sensing area supported by the RAN node (16), the method comprising:providing (SI 16), using the first SRH (17), at least one sensing-based function to a client node; andperforming (SI 18) at least one function associated with at least one sensing-based function.
2. The method of Claim 1, further comprising:receiving a registration message; andtransmitting a registration response indicating that the RAN node (16) has been:accepted by the sensing core node as a sensing RAN node (16) for one or both of performing sensing measurements and obtaining sensing data; andregistered in the sensing core node (15).
3. The method of Claim 2, wherein the registration message comprises at least one parameter, the at least one parameter including one or more of:an identity of the RAN node (16);a sensing coverage area of the RAN node (16);a communication address of the RAN node (16);capability information of the RAN node (16); anda secondary sensing unit coordinator associated with the RAN node (16).
4. The method of Claim 3, further comprising performing an update procedure based on a change to at least one of the at least one parameter; andthe update procedure results in a second SRH (17) being used to provide at least one sensing-based function to the client node.
5. The method of any one of Claims 2-4, wherein the registration response comprises one or more of:an identity of the first SRH (17);indication of a backup SRH (17);numerical weight associated with the first SRH (17); andcapabilities of the first SRH (17).
6. The method of any one of Claims 1-5, wherein the sensing core node (15) comprises a Sensing Exposure Function, SEF, and wherein the method further comprises:selecting, at the SEF, a Sensing Core Function, SCF, for discovery of a sensing entity to service a sensing request from an Application Function, AF.
7. The method of Claim 6, further comprising:determining, at the SCF, that the RAN node (16) is capable of performing sensing associated with the sensing request;transmitting, via the first SRH (17), the sensing request to the RAN node (16); in response to the sensing request, receiving sensing data from the RAN node (16); andthe sensing data satisfying the sensing request.
8. The method of any one of Claims 6-7, wherein the sensing request is associated with one of:environment monitoring;motion monitoring;object detection; andobject tracking.
9. The method of any one of Claims 1-8, wherein the sensing core node (15) further comprises a Sensing Exposure Data Function, SEDF, and wherein the method further comprises:providing, using the SEDF, an external sensing data session point of interconnect to an Application Function, AF, or Network Exposure Function, NEF;merging, at the SEDF, sensing data received from a plurality of sensing processing functions; andprocessing, at the SEDF, the sensing data so that privacy-friendly data remains for exposure to the AF or NEF.
10. The method of any one of Claims 1-9, wherein the sensing core node (15) further comprises a Sensing Repository Function, SRF, and wherein the method further comprises:receiving, at the SRF, a lookup request for a sensing request handler or a sensing processing function;determining, at the SRF based on stored network function profiles, one or more sensing request handlers or sensing processing functions that match the lookup request; andproviding, from the SRF, lookup response information comprising one or more of an identity, a serving sensing area, a URI, a load indication, and a backup indication associated with the one or more sensing request handlers or sensing processing functions.
11. The method of any one of Claims 1-10, wherein the at least one function includes one or more of:optimizing signaling flows; andperforming a sensing task.
12. A sensing core node (15) configured to communicate with a Radio Access Network, RAN, node (16), the sensing core node (15) including a first sensing request handler, SRH, that supports at least one sensing area supported by the RAN node (16), the sensing core node (15) configured to:provide, using the first SRH (17), at least one sensing-based function to a client node; andperform at least one function associated with at least one sensing-based function.
13. The sensing core node (15) of Claim 12, wherein the sensing core node (15) is further configured to:receive a registration message; andtransmit a registration response indicating that the RAN node (16) has been: accepted by the sensing core node as a sensing RAN node (16) for one or both of performing sensing measurements and obtaining sensing data; andregistered in the sensing core node (15).
14. The sensing core node (15) of Claim 13, wherein the registration message comprises at least one parameter, the at least one parameter including one or more of: an identity of the RAN node (16);a sensing coverage area of the RAN node (16);a communication address of the RAN node (16);capability information of the RAN node (16); anda secondary sensing unit coordinator associated with the RAN node (16).
15. The sensing core node (15) of Claim 14, wherein the sensing core node (15) is further configured to perform an update procedure based on a change to at least one of the at least one parameter; andthe update procedure results in a second SRH (17) being used to provide at least one sensing-based function to the client node.
16. The sensing core node (15) of any one of Claims 13-15, wherein the registration response comprises one or more of:an identity of the first SRH (17);indication of a backup SRH (17);numerical weight associated with the first SRH (17); andcapabilities of the first SRH (17).
17. The sensing core node (15) of any one of Claims 12-16, wherein the sensing core node (15) comprises a Sensing Exposure Function, SEF, that is configured to select a Sensing Core Function, SCF, for discovery of a sensing entity to service a sensing request from an Application Function, AF.
18. The sensing core node (15) of Claim 17, wherein the SCF is configured to: determine that the RAN node (16) is capable of performing sensing associated with the sensing request;transmit, via the first SRH (17), the sensing request to the RAN node (16);in response to the sensing request, receive sensing data from the RAN node (16); andthe sensing data satisfying the sensing request.
19. The sensing core node (15) of any one of Claims 17-18, wherein the sensing request is associated with one of:environment monitoring;motion monitoring;object detection; andobject tracking.
20. The sensing core node (15) of any one of Claims 12-19, wherein the sensing core node (15) further comprises a Sensing Exposure Data Function, SEDF; and the sensing core node (15) is configured to:provide, using the SEDF, an external sensing data session point of interconnect to an Application Function, AF, or Network Exposure Function, NEF;merge, at the SEDF, sensing data received from a plurality of sensing processing functions; andprocess, at the SEDF, the sensing data so that privacy-friendly data remains for exposure to the AF or NEF.
21. The sensing core node (15) of any one of Claims 12-20, wherein the sensing core node (15) further comprises a Sensing Repository Function, SRF; and the sensing core node (15) is further configured to:receive, at the SRF, a lookup request for a sensing request handler or a sensing processing function;determine, at the SRF based on stored network function profiles, one or more sensing request handlers or sensing processing functions that match the lookup request; andprovide, from the SRF, lookup response information comprising one or more of an identity, a serving sensing area, a URI, a load indication, and a backup indication associated with the one or more sensing request handlers or sensing processing functions.
22. The sensing core node (15) of any one of Claims 12-21, wherein the at least one function includes one or more of:optimizing signaling flows; andperforming a sensing task.
23. A method implemented by a Radio Access Network, RAN, node (16) that is configured to communicate with a sensing core node (15), the method comprising: discovering (S106) a first sensing request handler, SRH (17), of the sensing core node;causing (S108) transmission of a registration message to the first SRH (17); and receiving (SI 10) a registration response indicating that the RAN node (16) has been:accepted by the sensing core node (15) as a sensing network node (16) for one or both of performing sensing measurements and obtaining sensing data; and registered in the sensing core node (15).
24. The method of Claim 23, wherein the registration message comprises at least one parameter, the at least one parameter including one or more of:an identity of the RAN node (16);a sensing coverage area of the RAN node (16);a communication address of the RAN node (16);capability information of the RAN node (16); anda secondary sensing unit coordinator associated with the RAN node (16).
25. The method of any one of Claims 23-24, further comprising performing an update procedure based on a change to at least one of the at least one parameter; and the update procedure is configured to cause the RAN node (16) to discover a second SRH.
26. The method of any one of Claims 23-25, wherein the registration response comprises one or more of:an identity of the first SRH (17);indication of a backup SRH (17);numerical weight associated with the first SRH (17); andcapabilities of the first SRH (17).
27. The method of any one of Claims 23-26, wherein the discovery of the first SRH (17) includes discovering at least one SRH (17) that supports at least one sensing area of the RAN node (16).
28. The method of any one of Claims 23-27, further comprising: receiving a sensing request from the SRH (17);in response to the sensing request, one or both of performing sensing measurements and obtaining sensing data to satisfy the sensing request; and indicating the one or both of the sensing measurements and sensing data to the first SRH (17).
29. The method of any one of Claims 23-28, wherein the sensing request is associated with one of:environment monitoring;motion monitoring;object detection; andobject tracking.
30. A Radio Access Network, RAN, node (16) configured to communicate with a sensing core node (15), the RAN node (16) configured to:discover a first sensing request handler, SRH (17), of the sensing core node (15); cause transmission of a registration message to the first SRH (17); and receive a registration response indicating that the RAN node (16) has been:accepted by the sensing core node (15) as a sensing network node (16) for one or both of performing sensing measurements and obtaining sensing data; and registered in the sensing core node (15).
31. The RAN node (16) of Claim 30, wherein the registration message comprises at least one parameter, the at least one parameter including one or more of: an identity of the RAN node (16);a sensing coverage area of the RAN node (16);a communication address of the RAN node (16);capability information of the RAN node (16); anda secondary sensing unit coordinator associated with the RAN node (16).
32. The RAN node (16) of any one of Claims 30-31, wherein the RAN node (16) is further configured to perform an update procedure based on a change to at least one of the at least one parameter; andthe update procedure is configured to cause the RAN node (16) to discover a second SRH (17).
33. The RAN node (16) of any one of Claims 30-32, wherein the registration response comprises one or more of:an identity of the first SRH (17);indication of a backup SRH (17);numerical weight associated with the first SRH (17); andcapabilities of the first SRH (17).
34. The RAN node (16) of any one of Claims 30-33, wherein the discovery of the first SRH (17) includes discovering at least one SRH (17) that supports at least one sensing area of the RAN node (16).
35. The RAN node (16) of any one of Claims 30-34, wherein the RAN node (16) is further configured to:receive a sensing request from the SRH (17);in response to the sensing request, one or both of perform sensing measurements and obtain sensing data to satisfy the sensing request; andindicate the one or both of the sensing measurements and sensing data to the first SRH (17).
36. The RAN node (16) of any one of Claims 30-35, wherein the sensing request is associated with one of:environment monitoring;motion monitoring;object detection; andobject tracking.
