System and methods for sensing function registration, discovery, and selection

Abstract

In accordance with implementations, an NRF network entity receives from a sensing function network entity a sensing function profile registration request indicating at least one parameter. The at least one parameter indicates at least one sensing service area of interest. The NRF network entity sends to the sensing function network entity a sensing function profile registration response.

Description

SYSTEM AND METHODS FOR SENSING FUNC ION REGISTRATION, DISCOVERY, AND SELECTIONCROSS-REFERENCE TO RELATED APPLICATION

[0001] This patent application claims the benefit of U.S. Provisional Application No.63 / 802,238, filed on May 8, 2025, and entitled “System and Methods for Sensing Function Registration, Discovery and Selection,” application of which is hereby incorporated by reference herein as if reproduced in its entirety.TECHNICAL FIELD

[0002] The present disclosure relates generally to wireless communications, and, in particular implementations, to systems and methods for sensing function.BACKGROUND

[0003] Next generation waveform technologies have inched mobile access networks closer to a true realization of integrated sensing and communications (ISAC). Thus far, sensing has been a functionality exclusively reserved for radar sensing systems due to legacy waveform technology limitations. However, because high frequency bands are expected to be utilized by 6th generation (6G) networks, the corresponding waveform technologies will bear strong resemblances to those of sensing platforms. Hence, it is anticipated that mobile networks will conduct both sensing and communications in an integrated manner, hence, ISAC.

[0004] The added dimension of sensing in mobile networks has the potential to enhance localization methods, map the physical world for the network to “see,” enhance target identification and tracking, and improve beamforming and interference mitigation.

[0005] To this end, 3GPP has started studying different aspects of ISAC in different RAN and SA working groups. Functional requirements and performance requirements of integrated sensing and communication services that have architectural impacts have been studied in Working Group 1 in the Service and System Aspects (SAi). The SAi study has also identified the service requirements on sensing configuration, 5th generation (5G) wireless sensing service, exposure, security and charging. Moreover, Working Group 2 in the Service and System Aspects (SA2) has started a 5G-Advanced (5G-A) study in Release 20 to address the SAi requirements. The SA2 study is expected to be continued in 6G.FW 6000761PCT02 1[ooo6] Some of the ISAC terms defined as part of the SA1 / SA2 studies (TR 23.700-14 and TR 22.837) include the following:Sensing Measurement Data: data collected about radio / wireless signals impacted (e.g. reflected, refracted, diffracted) by an object or environment of interest for sensing purposes;Sensing Measurement Process: process of collecting sensing measurement data; Sensing Result: the information derived from processing sensing measurement data;Sensing Service Area Location: an area location, with or without obstacle, the 5G system can provide sensing service with certain quality;Transparent Sensing: sensing measurements are communicated such that they can be discerned and interpreted by the 5GS, e.g., the data is communicated using a standard protocol to an interface defined by the 5GS;Sensing Service Consumer: the entity that may consume the Sensing Result. The Sensing Service Consumer may also request the Sensing Result;Sensing Entity: the Sensing Entity referring to a Sensing Transmitter or to a Sensing Receiver;Sensing Function: indicating the logical function which is involved in supporting Sensing Service; andSensing Service: capability to collect and provide information about object and / or characteristics of the environment using radio signals.SUMMARY

[0007] Technical advantages are generally achieved, by implementations of this disclosure which describe methods, apparatus, and systems.

[0008] In accordance with implementations, an NRF network entity receives from a sensing function network entity a sensing function profile registration request indicating at least one parameter. The at least one parameter indicates at least one sensing service area of interest. The NRF network entity sends to the sensing function network entity a sensing function profile registration response.

[0009] In some implementations, the at least one parameter may further indicate at least one of a network function (NF) type, at least one supported sensing mode, or at least one supported sensing type.

[0010] In some implementations, the at least one sensing service area of interest may include one or more areas in which the sensing function network entity has sensing result or sensing data. The NF type may be a sensing function type. The at least one supported sensing mode may include one or more sensing modes for which the sensingFW 6000761PCT02 2function network entity has the sensing result or the sensing data. The at least one supported sensing type may include at least one of tracking or detection.[oon] In some implementations, the NRF network entity may store the at least one parameter as a sensing function profile corresponding to the sensing function network entity.

[0012] In some implementations, the NRF network entity may receive a discovery request for a sensing service. The NRF network entity may send a discovery response for sensing function selection.

[0013] In some implementations, the discovery request may be received from a trusted application function (AF). The discovery response may be sent to the trusted AF. The trusted AF may select the sensing function network entity based on the at least one sensing service area of interest of the sensing function profile after the trusted AF receives the discovery response.

[0014] In some implementations, the discovery request may be received from a network exposure functionality (NEF) network entity between the NRF network entity and an untrusted AF. The discovery response is sent to the NEF network entity.

[0015] In some implementations, before the NEF network entity sends the discovery request, the NEF network entity may receive from the untrusted AF a sensing service request for the sensing service. The sensing service request may indicate selection criteria. The selection criteria may include at least one of a sensing service area of interest or a sensing service time period of interest. The NEF network entity may determine, based on configured policies, whether the untrusted AF is entitled to request the sensing service. The NEF network entity may send the discovery request on behalf of the untrusted AF using the selection criteria.

[0016] In some implementations, after the NEF network entity receives the discovery response, the NEF network entity may select the sensing function network entity. The NEF network entity may assign a sensing coordination identifier (ID) corresponding to the sensing function network entity. The NEF network entity may send to the untrusted AF a sensing sendee response. The sensing service response may include the sensing coordination ID. The untrusted AF may store the sensing coordination ID and use the sensing coordination ID in subsequent interactions with the NEF network entity for the sensing service.

[0017] In some implementations, the sensing service response may further include information about how the sensing coordination ID relates to the selection criteria.

[0018] In some implementations, the untrusted AF may be outside a trusted domain corresponding to an operator of the sensing function network entity.FW 6000761PCT02 3

[0019] In accordance with implementations, a sensing function network entity sends to a network repository function (NRF) network entity a sensing function profile registration request indicating at least one parameter. The at least one parameter indicates at least one sensing service area of interest. The sensing function network entity receives from the NRF network entity a sensing function profile registration response.

[0020] In some implementations, the at least one parameter may further indicate at least one of a network function (NF) type, at least one supported sensing mode, or at least one supported sensing type.

[0021] In some implementations, the at least one sensing service area of interest may include one or more areas in which the sensing function network entity has sensing result or sensing data. The NF type may be a sensing function type. The at least one supported sensing mode may include one or more sensing modes for which the sensing function network entity has the sensing result or the sensing data. The at least one supported sensing type may include at least one of tracking or detection.

[0022] In accordance with implementations, a trusted AF sends to a network repository function (NRF) network entity a discovery request for a sensing service. The trusted AF receives from the NRF network entity a discovery response. The trusted AF selects a sensing function network entity based on at least one parameter of a sensing function profile. The at least one parameter indicates at least one sensing service area of interest.

[0023] In some implementations, the at least one parameter may further indicate at least one of a network function (NF) type, at least one supported sensing mode, or at least one supported sensing type.

[0024] In some implementations, the at least one sensing service area of interest may include one or more areas in which the sensing function network entity has sensing result or sensing data. The NF type may be a sensing function type. The at least one supported sensing mode may include one or more sensing modes for which the sensing function network entity has the sensing result or the sensing data. The at least one supported sensing type may include at least one of tracking or detection.

[0025] In accordance with implementations, an untrusted AF sends to a network exposure functionality (NEF) network entity a sensing service request for a sensing service. The sensing service request may indicate selection criteria. The selection criteria may include at least one of a sensing service area of interest or a sensing service time period of interest. The untrusted AF receives from the NEF network entity a sensing service response. The sensing service response includes a sensing coordination identifier (ID) corresponding to a sensing function network entity selected by the NEF network entity.FW 6000761PCT02 4

[0026] In some implementations, the untrusted AF may store the sensing coordination ID. The untrusted AF may use the sensing coordination ID for interactions with the NEF network entity for the sensing service.

[0027] In some implementations, the sensing service response may further include information about how the sensing coordination ID relates to the selection criteria.

[0028] In some implementations, the untrusted AF may be outside a trusted domain corresponding to an operator of the NEF network entity.

[0029] In accordance with implementations, an NEF network entity receives from an untrusted application function (AF) a sensing service request for a sensing service. The sensing service request indicates selection criteria. The selection criteria include at least one of a sensing service area of interest or a sensing service time period of interest. The NEF network entity determines based on configured policies that the untrusted AF is entitled to request the sensing service. In response to the determining, the NEF network entity sends to a network repository function (NRF) network entity a discovery request for the sensing service. The NEF network entity receives from the NRF network entity a discovery response for sensing function selection. The NEF network entity selects a sensing function network entity. The NEF network entity assigns a sensing coordination identifier (ID) corresponding to the sensing function network entity. The NEF network entity sends to the untrusted AF, a sensing service response. The sensing service response includes the sensing coordination ID.

[0030] In some implementations, the sensing service response may further include information about how the sensing coordination ID relates to the selection criteria.

[0031] The disclosed techniques provide a structured mechanism for sensing function registration, discovery, and selection in wireless core networks. By introducing sensing-specific parameters (e.g., including service area) into the NRF sensing function profile, service consumers can efficiently identity and select the most suitable sensing function. For trusted AFs, direct NRF discovery enables self-directed selection. For untrusted AFs, the NEF can act as a secure intermediary, performing discovery and selection on the untrusted AF’s behalf and returning a sensing coordination ID that shields internal network details while enabling subsequent service interactions.Together, these mechanisms address a key gap in the current solutions by providing a complete, security-conscious procedure for sensing function discovery and selection across both trusted and untrusted service consumers.FW 6000761PCT02 5BRIEF DESCRIPTION OF THE DRAWINGS

[0032] For a more complete understanding of the present disclosure, and the advantages thereof, reference is now made to the following descriptions taken in conjunction with the accompanying drawings, in which:

[0033] FIG. 1 illustrates an example network architecture for sensing function deployment in the 5G core, in accordance with some implementations;

[0034] FIG. 2 shows an example procedure for sensing function registration, discovery, and selection when a sensing service is requested by a trusted AF, in accordance with some implementations;

[0035] FIG. 3 shows an example procedure for sensing function registration, discovery, and selection when two sensing functions supporting different sensing capabilities register with the NRF, in accordance with some implementations;

[0036] FIG. 4 shows an example procedure for sensing function registration, discovery, and selection when a sensing service is requested by an untrusted AF, in accordance with some implementations;

[0037] FIG.5 shows an example procedure for sensing function registration, discovery, and selection when two sensing functions A and B supporting different sensing capabilities register with the NRF, in accordance with some implementations;

[0038] FIG. 6A illustrates an example flowchart of operations performed by an NRF network entity, in accordance with some implementations;

[0039] FIG. 6B illustrates an example flowchart of operations performed by a sensing function network entity, in accordance with some implementations;

[0040] FIG. 6C illustrates an example flowchart of operations performed by a trusted AF, in accordance with some implementations;

[0041] FIG. 6D illustrates an example flowchart of operations performed by an untrusted AF, in accordance with some implementations;

[0042] FIG. 6E illustrates an example flowchart of operations performed by an NEF network entity, in accordance with some implementations;

[0043] FIG. 7 illustrates an example communications system, in accordance with some implementations;

[0044] FIG. 8 illustrates an example communications system, in accordance with some implementations;FW 6000761PCT02 6

[0045] FIGs. 9A and 9B illustrate example devices that may implement the methods and teachings according to this disclosure, in accordance with some implementations; and

[0046] FIG. 10 is a block diagram of a computing system that may be used for implementing the devices and methods disclosed herein, in accordance with some implementations.

[0047] Corresponding numerals and symbols in the different figures generally refer to corresponding parts unless otherwise indicated. The figures are drawn to clearly illustrate the relevant aspects of the implementations and are not necessarily drawn to scale.DETAILED DESCRIPTIONS

[0048] As part of the network architecture and functional enhancements to support ISAC in the mobile core (5G core and 6G core), a new network functionality, i.e., sensing function (or sensing management function), could be added to mobile core. For example, FIG. 1 shows that the sensing function 102 is added to the 5G core too, in accordance with some implementations. The sensing function is defined by 3GPP SA2 as a logical function which is involved in supporting sensing service including collecting sensing measurement data, calculating the sensing result, and exposing the sensing result to a sensing service consumer.

[0049] A sensing service request can be initiated by an application function (AF) (sensing service consumer) which is either located inside mobile network (e.g., trusted AF 104 owned / controlled by the mobile operator) or outside mobile network (e.g., untrusted AF 106 owned / controlled by the third party). When a sensing service request is initiated by the trusted / untrusted AF 104 / 106, it may be determined which sensing function in the network can serve this request (i.e., sensing function discovery and selection). To enable sensing function discovery and selection, the sensing function profile including sensing capability information should be registered in the network repository function (NRF) 108. To this end, the SA2 study in Release 20 has identified a specific issue to study the above problem of sensing function registration, discovery, and selection, that may be referred to as key issue (KI), Sensing Entity and Sensing Function Discovery and (Re-)Selection. In the description of this KI, it is specified that when required, for the discovery and (re-) selection of the Sensing Function(s), the study may need to address the following aspects:which entity (ies) performs the discovery and (re-)selection of sensing function(s);FW 6000761PCT02 7what information and / or criteria are taken into account for the discovery and (re-)selection of sensing function(s); andthe procedure(s) for the discovery and (re-)selection of the sensing function(s).

[0050] This sensing function is a control plane (CP) function that is added to the service-based architecture of core network control plane and interfaces to other core control plane network functions (NFs) on the service bus. New or enhanced service operations on the existing service bus interfaces can be introduced to carry the information that the new sensing function could exchange with other existing NFs. In terms of the functionality, a sensing function adds new capabilities to the network as compared to, for example, the location management function (LMF), such as the following.

[0051] The sensing function supports different sensing modes depending on the transmitter / receiver configuration and the involvement of the UE or gNBs, unlike LMF which only provides location service. Also, the sensing function provides different types of services such as tracking and detection. Further, the sensing function can support non-3GPP sensing data integration.

[0052] Therefore, the information about these new capabilities could be taken into consideration when the sensing function registration, discovery, and selection procedure is performed.

[0053] ISAC is a new study in 3GPP started in Release 20. Currently, there is no solution for a procedure for sensing function registration that includes enhancements on NRF service operations by defining sensing function profile that includes introducing sensing capability information that should be registered in NRF (e.g., 108). Further, there is no solution for separate detailed procedures for sensing function discovery and selection, which are triggered by receiving a sensing service request from a trusted and / or untrusted AF (e.g., 104 and / or 106), and defining a new service operation between the AF and the network exposure functionality (NEF) (e.g., 110) to include sensing service selection criteria parameters.

[0054] Some current solutions introduce a sensing entity (sensing transmitter / receiver) selection mechanism which does not cover sensing function discovery and selection. The current solutions may focus on sensing service authorization procedures that include sensing service creation, modification, termination, and suspension and require interactions between sensing clients and sensing authorization function. The focus of this disclosure is on registering, discovering, and selecting a sensing function that can serve an authorized service request and requires interactions between the sensing function (e.g., 102), the NRF (e.g., 108), the NEF (e.g., 110), and the AF (e.g., 104 and / or 106). While similar parameters may be used during a sensing service FW 6000761PCT02 8authorization decision and a sensing function discovery and selection, the described implementations cover how and via which service operations these parameters can be exchanged between the involved network entities including the sensing function (e.g., 102), the NRF (e.g., 108), the AF (e.g., 104 and / or 106), and the NEF (e.g., no).

[0055] The example implementations in this disclosure describe a new technical solution for sensing function registration, discovery, and selection. The main objectives of the proposed solution include the following.

[0056] Two separate sensing function registration, discovery, and selection procedures are described in this disclosure to cover both cases when a sensing service request is triggered by a trusted AF and / or an untrusted AF.[OO57] The described procedures include operations for sensing function registration via enhancing NRF service operations for network function (NF) registration while introducing new parameters as part of sensing function profile.

[0058] The described procedures include operations for sensing function discovery and selection while adding sensing service selection criteria parameters.

[0059] This disclosure describes a new service operation for interaction between AF and NEF to enable sensing function discovery and selection by NEF for an untrusted AF.Sensing Function Registration, Discovery, and Selection when Sensing Service Is Requested by a Trusted AF

[0060] FIG. 2 illustrates an example of sensing function registration, discovery, and selection when sensing service is requested by a trusted AF, in accordance with some implementations.

[0061] At the operation 201, the sensing function 102 may register to the NRF 108, by invoking the Nnrf_NFManagement_NFRegister request service operation, with the sensing function 102’s NF profile, which includes the NF type (e.g., sensing function type), the supported sensing service area (serving areas for which sensing function has the sensing result / data), the supported sensing modes (sensing modes for which sensing function has the sensing result / data), supported sensing entity identifiers (IDs) (IDs of the sensing transmitters / receivers located within supported sensing service area), and / or supported sensing service types (e.g., tracking, detection), supported security information, sensing privacy information, supported sensing key performance indicator(s) (KPI), supported sensing mobility capability, and / or supported non-3GPP sensing data capability.

[0062] At the operation 202, the NRF 108 may receive the registration request from the sensing function 102 and store the NF profile of the sensing function 102.FW 6000761PCT02 9

[0063] At the operation 203, the NRF 108 may send a registration response to the sensing function 102 by invoking, for example, the Nnrf_NFManagement_NFRegister response.

[0064] The existing 3GPP specified Nnrf_NFManagement_NFRegister service operations (TS 23.502) maybe enhanced for interactions between the sensing function 102 and the NRF 108 to include the sensing function profile information. Examples of these enhancements are listed below. The NRF 108 may store all the parameters provided as input parameters of each sensing function registration request under the sensing function profile of that sensing function.

[0065] For example, when the sensing function A provides sensing areas 1, 2, and 3 as its supported sensing service areas, this information is stored in the profile of the sensing function A. As another example, the sensing function B may provide tracking and detection as its supported sensing types, and the NRF may store these sensing types of information in the profile of the sensing function B.Service operation name: Nnrf_NFManagement_NFRegister.Description: registering the consumer NF in the NRF by providing the NF profile of the consumer NF to NRF and NRF marks the consumer NF available.Inputs that may be required: NF type, NF instance ID, fully qualified domain name (FQDN) or IP address of NF, names of supported NF services (if applicable) and public land mobile network (PLMN) ID (e.g., if NF needs to be discovered by other PLMNs / stand-alone non-public networks (SNPNs).Inputs that can be optional:supported sensing service area (serving areas for which the sensing function has the sensing result / data);supported sensing operation modes (sensing modes for which the sensing function has the sensing result / data: i.e., Monostatic, Bistatic);supported sensing entity IDs (IDs of the sensing transmitters / receivers located within the supported sensing service area);supported sensing service types (e.g., tracking, detection);supported security information (e.g., security level, security domain information, security protection capability);supported privacy information (e.g., privacy protect level, privacy domain information, privacy protection capability);supported sensing KPI (e.g., sensing service category, sensing resolution);FW 6000761PCT02 10supported sensing mobility capability (e.g., support sensing service continuity across different sensing service areas which may or may not be associated with this sensing function);supported non-3GPP sensing data capability (e.g., support integrating other non- 3GPP sensing data).Outputs that may be required: result indication.Outputs that could be optional: none.

[0066] The trusted AF 104 may discover sensing function(s) from the NRF by invoking, for example, the Nnrf_NFDiscovery_Request at the operation 204 and receiving, for example, the Nnrf_NFDiscovery_Response from the NRF 108 at the operation 205.

[0067] The existing 3GPP specified Nnrf_NFDiscovery_Request service operations (TS 23.502) maybe enhanced for interactions between the trusted AF 104 and NRF 108 to include the sensing function profile information. Examples of these enhancements are listed below. The NRF 108 may use the parameters provided in the input of the discovery requests to determine what information from the sensing function profile is needed by the trusted AF 104. For example, when the trusted AF 104 asks for sensing service areas as an input parameter, the NRF 108 could provide the supported service area of each registered sensing function in the NRF 108 alongside other input parameters provided in the AF request. As another example, the trusted AF 104 may ask sensing operation modes as an input parameter, and the NRF 108 may provide a list of supported sensing operation modes of each registered sensing function as output parameters of discovery request service operations.Service operation name: Nnrf_NFDiscovery_RequestDescription: providing the IP address or FQDN of the expected NF instance(s) and if present in NF profile, the endpoint address(es) of NF service instan ce(s) to the NF service consumer or SCP.Inputs that may be required: one or more target NF service name(s), NF type of the target NF, NF type of the NF service consumer.Inputs that can be optional:sensing service areas (serving areas for which the sensing function has the sensing result / data);sensing operation modes (sensing modes for which the sensing function has the sensing result / data);sensing entity IDs (IDs of the sensing transmitters / receivers located within the supported sensing service area);FW 6000761PCT02 11sensing service types (e.g., tracking, detection);security information (e.g., security level, security domain information, security protection capability);privacy information (e.g., privacy protect level, privacy domain information, privacy protection capability);sensing KPI (e.g., sensing service category, sensing resolution);sensing mobility capability (e.g., support sensing service continuity across different sensing service areas which may or may not associated with this sensing function);non-3GPP sensing data capability (e.g., support integrating other non-3GPP sensing data).Outputs that may be required: one of the following:a set of NF instance profiles; oran indication that “indirect communication with delegated discovery with NF selection at target domain is requested”; oran indication that “indirect communication without delegated discovery with NF selection at target domain is requested” together with a set of NF instance profiles; anda validity period for the discovery result.

[0068] The set of NF instance profiles could contain per NF instance: NF type, NF instance ID, FQDN or IP address(es) of the NF instance, and if applicable, a list of services instances, where each service instance has a service name, an NF service instance ID, and optionally endpoint address(es)

[0069] Endpoint address(es) may be a list of IP addresses or an FQDN for the NF service instance.

[0070] Outputs that can be optional: per NF instance, information in the NF profile listed related to the NF instance as specified in TS 23.502 and TS 23.501:supported sensing service area (serving areas for which the sensing function has the sensing result / data);supported sensing operation modes (sensing modes for which sensing function has the sensing result / data);supported sensing entity IDs (IDs of the sensing transmitters / receivers located within the supported sensing service area);supported sensing service types (e.g., tracking, detection);supported security information (e.g., security level, security domain information, security protection capability);FW 6000761PCT02 12supported privacy information (e.g., privacy protect level, privacy domain information, privacy protection capability);supported sensing KPI (e.g., sensing service category, sensing resolution); supported sensing mobility capability (e.g., support sensing service continuity across different sensing service areas which may or may not associated with this sensing function);supported non-3GPP sensing data capability (e.g., support integrating other non- 3GPP sensing data);validity time of sensing data.

[0071] At the operation 206, the trusted AF 104 may select sensing function(s), for example, by matching sensing function’s profile to the trusted AF 104’s selection criteria such as sensing service areas of interest, sensing service time period of interest (time duration in which the AF may require sensing service), sensing modes of interest, sensing entities of interest, and / or sensing types of interest.

[0072] FIG. 3 shows an example that there may be at least two sensing functions: the sensing function A 102a supporting sensing service area 1 and the sensing function B 102b supporting sensing service area 2 discovered from the NRF 108, in accordance with some implementations. The operations 301 to 306 are similar to the operations 201 to 206 described with respect to FIG. 2, respectively. The trusted AF 104 maybe interested only in sensing service area 1. At the operation 301, the sensing function A 102a and the sensing function B 102b may register to the NRF 108, by invoking their respective Nnrf_NFManagement_NFRegister request service operations. Each Nnrf_NFManagement_NFRegister request service operation is similar to the Nnrf_NFManagement_NFRegister request service operation described with respect to the operation 201 shown in FIG. 2. At the operation 302, the NRF 108 may receive the registration requests from the sensing function A 102a and the sensing function B 102b, and the NRF 108 may store the NF profiles of the sensing functions 102a and 102b. At the operation 303, the NRF 108 may send the respective registration responses to the sensing function A 102a and the sensing function B 102b by invoking, for example, the respective Nnrf_NFManagement_NFRegister responses. The operations 304 and 305 are similar to the operations 204 and 205 described with respect to FIG. 2, respectively. At the operation 306, the trusted AF 104 may select sensing function A 102a whose capability matches its selection criteria of sensing service area 1.FW 6000761PCT02 13Sensing Function Registration, Discovery, and Selection When Sensing Service Is Requested by an Untrusted AF

[0073] FIG. 4 shows an example procedure for sensing function registration, discovery, and selection when a sensing service is requested by an untrusted AF, in accordance with some implementations. At the operation 401, the sensing function 102 may register to the NRF 108, by invoking the Nnrf_NFManagement_NFRegister request service operation, with its NF profile, which includes the NF Type (i.e., sensing function type), supported sensing service area (serving areas for which sensing function has the sensing result / data), supported sensing modes (sensing modes for which sensing function has the sensing result / data), supported sensing entity IDs (IDs of the sensing transmitters / receivers located within supported sensing service area) and / or supported sensing service types (e.g., tracking, detection), supported security information, sensing privacy information, supported sensing KPI, supported sensing mobility capability, and / or supported non-3GPP sensing data capability.

[0074] Existing 3GPP specified Nnrf_NFManagement_NFRegister service operations (TS 23.502) may be enhanced for interactions between the sensing function and the NRF to include sensing function profile information. These enhancements are described above with respect to the operation 201 in FIG. 2.

[0075] The operation 402 is similar to the operation 202 in FIG. 2. At the operation 402, the NRF 108 may receive the registration request from the sensing function 102 and store its NF profile.

[0076] The operation 403 is similar to the operation 203 in FIG. 2. At the operation 403, the NRF 108 may send a registration response to the sensing function 102 by invoking, for example, the Nnrf_NFManagement_NFRegister response.

[0077] At the operation 404, the untrusted AF 106 may send a sensing service request to the NEF 110 including some selection criteria such as sensing service areas of interest, sensing service time periods of interest (time duration in which the AF may require sensing service), sensing operation modes of interest, sensing entities of interest, sensing types of interest, security levels of interest, privacy levels of interest, sensing KPIs of interest, sensing mobility capability of interest, and / or non-3GPP data of interest.

[0078] A new service operation may be introduced for interactions between the NEF 110 and the untrusted AF 106 to support sensing service requests. An example of this new service operation is listed below.Service operation name: Nnef_AF_request_for_SensingDescription: the AF requesting the NEF to perform sensing function discovery.FW 6000761PCT02 14Inputs that may be required: AF identifier.Inputs that can be optional:sensing service area of interest;sensing service time period of interest (time duration in which the AF may require sensing service);sensing operation modes of interest;sensing entities of interest;sensing types of interest;security levels of interest;privacy levels of interest;sensing KPIs of interest;sensing mobility capability of interest;non~3GPP sensing data of interest.Outputs that may be required: transaction reference ID, result.Output that can be optional: none.

[0079] The NEF 110 may use information provided as input parameters in the sensing service request of the untrusted AF 106 as the parameters required during the sensing function discovery. For example, when the untrusted AF 106 provides a sensing service area of interest as an input parameter in its sensing service request, the NEF no may ask the NRF 108 to provide supported areas of each registered sensing function.

[0080] At the operation 405, the NEF no may check based on configured policies whether the untrusted AF 106 is entitled to request a sensing service.

[0081] The NEF no may discover sensing function(s) on behalf of the untrusted AF 106 from the NRF 108 by invoking, for example, the Nnrf_NFDiscovery_Request at the operation 406 (using the selection criteria provided by the untrusted AF 106 as defined at the operation 404 above) and receiving, for example, the Nnrf_NFDiscovery_Response from the NRF 108 at the operation 407.

[0082] Existing 3GPP specified Nnrf_NFDiscovery_Request service operations (TS 23.502) may be enhanced for interactions between the NEF no and the NRF 108 to include sensing function profile information. The example of this enhancement is described above with respect the operations 204 and 205 in FIG. 2. The NEF no may use information provided as input parameters in the sensing service request of the untrusted AF 106 as the parameters required during the sensing function discovery.

[0083] The NRF 108 may also use the parameters provided in the input of the discovery requests to determine what information from the sensing function profile is needed by the NEF no. For example, when the NEF no asks for sensing service areas as FW 6000761PCT02 15an input parameter, the NRF 108 could provide the supported service area of each registered sensing function stored in the NRF 108 along with other input parameters provided in the NEF no’s request. As another example, the NEF no may ask for sensing operation modes as an input parameter, and the NRF 108 may provide a list of supported sensing operation modes of each registered sensing function as output parameters of discovery request service operations.

[0084] At the operation 408, the NEF 110 may select sensing function(s), e.g., by matching corresponding sensing function(s) profile(s) to the selection criteria received from the untrusted AF 106. In this step, the NEF 110 may assign a sensing coordination ID to each AF sensing request. The NEF 110 may also store the sensing coordination ID(s). For example, as shown in FIG. 5, there maybe two sensing functions: the sensing function A 102a supporting sensing service area 1 and the sensing function B 102b supporting sensing service area 2 discovered from the NRF 108 while the untrusted AF 106 may be interested only in sensing service area 1. In this case, the NEF no may select the sensing function A 102a whose capability matches the untrusted AF 106’s selection criteria of sensing service area 1.

[0085] At the operation 409, the NEF no may send the sensing service response only including the sensing coordination ID(s) as assigned in the operation 408 above and information on how they relate to corresponding selection criteria provided by the untrusted AF 106.

[0086] At the operation 410, the untrusted AF 106 may store the sensing coordination ID(s) and use it in subsequent interactions with the NEF 110 for the requested sensing service.

[0087] Like request / response service operations, a subscribe / notify service operation with the same input parameters as the selection criteria may also be used for interactions between the NEF 110 and the untrusted AF 106. In this case, the NEF 110 may perform a new sensing function discovery and, accordingly, may re-select sensing function(s) upon receiving notification from the untrusted AF 106 on sensing service selection criteria updates.

[0088] FIG. 5 shows an example procedure for sensing function registration, discovery, and selection when two sensing functions A and B supporting different sensing capabilities register in the NRF, in accordance with some implementations. The operations 501 to 503 are similar to the operations 301 to 303 described above with respect to FIG.3, respectively. The operations 504 to 510 are similar to the operations 404 to 410 described above with respect to FIG. 4, respectively.

[0089] FIG. 6A illustrates an example of a flowchart of a method 600 performed by an NRF network entity, in accordance with some implementations. The NRF networkFW 6000761PCT02 16entity may include computer-readable code or instructions executing on one or more processors of the NRF network entity. Coding of the software for carrying out or performing the method 600 is well within the scope of a person of ordinary skill in the art having regard to the present disclosure. The method 600 may include additional or fewer operations than those shown and described and may be carried out or performed in a different order. Computer-readable code or instructions of the software executable by the one or more processors may be stored on at least one non-transitory computer-readable medium, such as for example, at least one memory of the NRF network entity. In some implementations, the method 600 may be performed by one or more units or modules (e.g., an integrated circuit) of the NRF network entity, such as field programmable gate arrays (FPGAs) or application-specific integrated circuits (ASICs).

[0090] The method 600 starts at the operation 602, where the NRF network entity receives from a sensing function network entity a sensing function profile registration request indicating at least one parameter. The at least one parameter indicates at least one sensing service area of interest. At the operation 604, the NRF network entity sends to the sensing function network entity a sensing function profile registration response.

[0091] In some implementations, the at least one parameter may further indicate at least one of a network function (NF) type, at least one supported sensing mode, or at least one supported sensing type.

[0092] In some implementations, the at least one sensing service area of interest may include one or more areas in which the sensing function network entity has sensing result or sensing data. The NF type may be a sensing function type. The at least one supported sensing mode may include one or more sensing modes for which the sensing function network entity has the sensing result or the sensing data. The at least one supported sensing type may include at least one of tracking or detection.

[0093] In some implementations, the NRF network entity may store the at least one parameter as a sensing function profile corresponding to the sensing function network entity.

[0094] In some implementations, the NRF network entity may receive a discovery request for a sensing service. The NRF network entity may send a discovery response for sensing function selection.

[0095] In some implementations, the discovery request may be received from a trusted application function (AF). The discovery response may be sent to the trusted AF. The trusted AF may select the sensing function network entity based on the at least one sensing service area of interest of the sensing function profile after the trusted AF receives the discovery response.FW 6000761PCT02 17

[0096] In some implementations, the discovery request may be received from a network exposure functionality (NEF) network entity between the NRF network entity and an untrusted AF. The discovery response is sent to the NEF network entity.

[0097] In some implementations, before the NEF network entity sends the discovery request, the NEF network entity may receive from the untrusted AF a sensing service request for the sensing service. The sensing service request may indicate selection criteria. The selection criteria may include at least one of a sensing service area of interest or a sensing service time period of interest. The NEF network entity may determine, based on configured policies, whether the untrusted AF is entitled to request the sensing service. The NEF network entity may send the discovery request on behalf of the untrusted AF using the selection criteria.

[0098] In some implementations, after the NEF network entity receives the discovery response, the NEF network entity may select the sensing function network entity. The NEF network entity may assign a sensing coordination identifier (ID) corresponding to the sensing function network entity. The NEF network entity may send to the untrusted AF a sensing service response. The sensing service response may include the sensing coordination ID. The untrusted AF may store the sensing coordination ID and use the sensing coordination ID in subsequent interactions with the NEF network entity for the sensing service.

[0099] In some implementations, the sensing service response may further include information about how the sensing coordination ID relates to the selection criteria.

[0100] In some implementations, the untrusted AF may be outside a trusted domain corresponding to an operator of the sensing function network entity.

[0101] FIG. 6B illustrates an example of a flowchart of a method 610 performed by a sensing function network entity, in accordance with some implementations. The sensing function network entity may include computer-readable code or instructions executing on one or more processors of the sensing function network entity. Coding of the software for carrying out or performing the method 610 is well within the scope of a person of ordinary skill in the art having regard to the present disclosure. The method 610 may include additional or fewer operations than those shown and described and may be carried out or performed in a different order. Computer-readable code or instructions of the software executable by the one or more processors may be stored on at least one non-transitory computer-readable medium, such as for example, at least one memory of the sensing function network entity. In some implementations, the method 610 may be performed by one or more units or modules (e.g., an integrated circuit) of the sensing function network entity, such as field programmable gate arrays (FPGAs) or applicationspecific integrated circuits (ASICs).FW 6000761PCT02 18

[0102] The method 610 starts at the operation 612, where the sensing function network entity sends to a network repository function (NRF) network entity a sensing function profile registration request indicating at least one parameter. The at least one parameter indicates at least one sensing service area of interest. At the operation 614, the sensing function network entity receives from the NRF network entity a sensing function profile registration response.

[0103] In some implementations, the at least one parameter may further indicate at least one of a network function (NF) type, at least one supported sensing mode, or at least one supported sensing type.

[0104] In some implementations, the at least one sensing service area of interest may include one or more areas in which the sensing function network entity has sensing result or sensing data. The NF type may be a sensing function type. The at least one supported sensing mode may include one or more sensing modes for which the sensing function network entity has the sensing result or the sensing data. The at least one supported sensing type may include at least one of tracking or detection.

[0105] FIG. 6C illustrates an example of a flowchart of a method 620 performed by a trusted application function (AF), in accordance with some implementations. The trusted AF may include computer-readable code or instructions executing on one or more processors of the trusted AF. Coding of the software for carrying out or performing the method 620 is well within the scope of a person of ordinary skill in the art having regard to the present disclosure. The method 620 may include additional or fewer operations than those shown and described and may be carried out or performed in a different order. Computer-readable code or instructions of the software executable by the one or more processors may be stored on at least one non-transitory computer-readable medium, such as for example, at least one memory of the trusted AF. In some implementations, the method 620 may be performed by one or more units or modules (e.g., an integrated circuit) of the trusted AF, such as field programmable gate arrays (FPGAs) or application-specific integrated circuits (ASICs).

[0106] The method 620 starts at the operation 622, where the trusted AF sends to a network repository function (NRF) network entity a discovery request for a sensing service. At the operation 624, the trusted AF receives from the NRF network entity a discovery response. At the operation 626, the trusted AF selects a sensing function network entity based on at least one parameter of a sensing function profile. The at least one parameter indicates at least one sensing service area of interest.

[0107] In some implementations, the at least one parameter may further indicate at least one of a network function (NF) type, at least one supported sensing mode, or at least one supported sensing type.FW 6000761PCT02 19[oio8] In some implementations, the at least one sensing service area of interest may include one or more areas in which the sensing function network entity has sensing result or sensing data. The NF type may be a sensing function type. The at least one supported sensing mode may include one or more sensing modes for which the sensing function network entity has the sensing result or the sensing data. The at least one supported sensing type may include at least one of tracking or detection.

[0109] FIG. 6D illustrates an example of a flowchart of a method 630 performed by a trusted application function (AF), in accordance with some implementations. The untrusted AF may include computer-readable code or instructions executing on one or more processors of the untrusted AF. Coding of the software for carrying out or performing the method 630 is well within the scope of a person of ordinary skill in the art having regard to the present disclosure. The method 630 may include additional or fewer operations than those shown and described and may be carried out or performed in a different order. Computer-readable code or instructions of the software executable by the one or more processors may be stored on at least one non-transitory computer-readable medium, such as for example, at least one memory of the untrusted AF. In some implementations, the method 630 may be performed by one or more units or modules (e.g., an integrated circuit) of the untrusted AF, such as field programmable gate arrays (FPGAs) or application-specific integrated circuits (ASICs).

[0110] The method 630 starts at the operation 632, where the untrusted AF sends to a network exposure functionality (NEF) network entity a sensing service request for a sensing service. The sensing sendee request may indicate selection criteria. The selection criteria may include at least one of a sensing service area of interest or a sensing service time period of interest. At the operation 634, the untrusted AF receives from the NEF network entity a sensing service response. The sensing service response includes a sensing coordination identifier (ID) corresponding to a sensing function network entity selected by the NEF network entity.

[0111] In some implementations, the untrusted AF may store the sensing coordination ID. The untrusted AF may use the sensing coordination ID for interactions with the NEF network entity for the sensing service.

[0112] In some implementations, the sensing service response may further include information about how the sensing coordination ID relates to the selection criteria.

[0113] In some implementations, the untrusted AF may be outside a trusted domain corresponding to an operator of the NEF network entity.

[0114] FIG. 6E illustrates an example of a flowchart of a method 640 performed by a network exposure functionality (NEF) network entity, in accordance with some implementations. The NEF network entity may include computer-readable code orFW 6000761PCT02 20instructions executing on one or more processors of the NEF network entity. Coding of the software for carrying out or performing the method 640 is well within the scope of a person of ordinary skill in the art having regard to the present disclosure. The method 640 may include additional or fewer operations than those shown and described and may be carried out or performed in a different order. Computer-readable code or instructions of the software executable by the one or more processors may be stored on at least one non -transitory computer-readable medium, such as for example, at least one memory of the NEF network entity. In some implementations, the method 640 may be performed by one or more units or modules (e.g., an integrated circuit) of the NEF network entity, such as field programmable gate arrays (FPGAs) or application-specific integrated circuits (ASICs).

[0115] The method 640 starts at the operation 642, where the NEF network entity receives from an untrusted application function (AF) a sensing service request for a sensing service. The sensing service request indicates selection criteria. The selection criteria include at least one of a sensing service area of interest or a sensing service time period of interest. At the operation 644, the NEF network entity determines based on configured policies that the untrusted AF is entitled to request the sensing service. At the operation 646, in response to the determining, the NEF network entity sends to a network repository function (NRF) network entity a discovery request for the sensing service. At the operation 648, the NEF network entity receives from the NRF network entity a discovery response for sensing function selection. At the operation 650, the NEF network entity selects a sensing function network entity. At the operation 652, the NEF network entity assigns a sensing coordination identifier (ID) corresponding to the sensing function network entity. At the operation 654, the NEF network entity sends to the untrusted AF, a sensing service response. The sensing service response includes the sensing coordination ID.

[0116] In some implementations, the sensing service response may further include information about how the sensing coordination ID relates to the selection criteria.

[0117] FIG. 7 illustrates an example communications system 700. Communications system 700 includes an access node 710 serving user equipments (UEs) with coverage 701, such as UEs 720. In a first operating mode, communications to and from a UE passes through access node 710 with the coverage area 701. The access node 710 is connected to a backhaul network 715 for connecting to the internet, operations and management, and so forth. In a second operating mode, communications to and from a UE do not pass through access node 710, however, the access node 710 typically allocates resources used by the UE to communicate when specific conditions are met.Communications between a pair of UEs 720 can use a sidelink connection (shown as twoFW 6000761PCT02 21separate one-way connections 725). In FIG. 7, the sidelink communication is occurring between two UEs operating inside of coverage area 701. However, sidelink communications, in general, can occur when UEs 720 are both outside coverage area 701, both inside coverage area 701, or one inside and the other outside coverage area 701. Communication between a UE and access node pair occur over uni-directional communication links, where the communication links between the UE and the access node are referred to as uplinks 730, and the communication links between the access node and UE are referred to as downlinks 735.

[0118] Access nodes may also be commonly referred to as Node Bs, evolved Node Bs (eNBs), next generation (NG) Node Bs (gNBs), master eNBs (MeNBs), secondary eNBs (SeNBs), master gNBs (MgNBs), secondary gNBs (SgNBs), network controllers, control nodes, base stations, access points, transmission points (TPs), transmission-reception points (TRPs), cells, carriers, macro cells, femtocells, pico cells, and so on, while UEs may also be commonly referred to as mobile stations, mobiles, terminals, users, subscribers, stations, and the like. Access nodes may provide wireless access in accordance with one or more wireless communication protocols, e.g., the Third Generation Partnership Project (3GPP) long term evolution (LTE), LTE advanced (LTE-A), 5G, 5G LTE, 5G NR, sixth generation (6G), High Speed Packet Access (HSPA), the IEEE 802.11 family of standards, such as 802.na / b / g / n / ac / ad / ax / ay / be, etc. While it is understood that communications systems may employ multiple access nodes capable of communicating with a number of UEs, only one access node and two UEs are illustrated for simplicity.

[0119] FIG. 8 illustrates an example communication system 800. In general, the system 800 enables multiple wireless or wired users to transmit and receive data and other content. The system 800 may implement one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single-carrier FDMA (SC-FDMA), or non-orthogonal multiple access (NOMA).

[0120] In this example, the communication system 800 includes electronic devices (ED) 8ioa-8ioc, radio access networks (RANs) 82oa-82ob, a core network 830, a public switched telephone network (PSTN) 840, the Internet 850, and other networks 860. While certain numbers of these components or elements are shown in FIG. 8, any number of these components or elements may be included in the system 800.

[0121] The EDs 8ioa-8ioc are configured to operate or communicate in the system 800. For example, the EDs 8ioa-8ioc are configured to transmit or receive via wireless or wired communication channels. Each ED 8ioa-8ioc represents any suitable end user device and may include such devices (or may be referred to) as a user equipment orFW 6000761PCT02 22device (UE), wireless transmit or receive unit (WTRU), mobile station, fixed or mobile subscriber unit, cellular telephone, personal digital assistant (PDA), smartphone, laptop, computer, touchpad, wireless sensor, AIoT device (e.g., for asset management), or consumer electronics device.

[0122] The RANs 82oa-82ob here include base stations 8yoa-8yob, respectively. Each base station 8yoa-8yob is configured to wirelessly interface with one or more of the EDs 8ioa-8ioc to enable access to the core network 830, the PSTN 840, the Internet 850, or the other networks 860. For example, the base stations 8yoa-8yob may include (or be) one or more of several well-known devices, such as a base transceiver station (BTS), a Node-B (NodeB), an evolved NodeB (eNB), a Next Generation (NG) NodeB (gNB), a gNB centralized unit (gNB-CU), a gNB distributed unit (gNB-DU), a Home NodeB, a Home eNodeB, a site controller, an access point (AP), or a wireless router. The EDs 8ioa-8ioc are configured to interface and communicate with the Internet 850 and may access the core network 830, the PSTN 840, or the other networks 860.

[0123] In the embodiment shown in FIG. 8, the base station 8yoa forms part of the RAN 820a, which may include other base stations, elements, or devices. Also, the base station 8yob forms part of the RAN 820b, which may include other base stations, elements, or devices. Each base station 8yoa-8yob operates to transmit or receive wireless signals within a particular geographic region or area, sometimes referred to as a “cell.” In some embodiments, multiple-input multiple-output (MIMO) technology may be employed having multiple transceivers for each cell.

[0124] The base stations 8yoa-8yob communicate with one or more of the EDs 810a-810c over one or more air interfaces 890 using wireless communication links. The air interfaces 890 may utilize any suitable radio access technology.

[0125] It is contemplated that the system 800 may use multiple channel access functionality, including such schemes as described above. In particular implementations, the base stations and EDs implement 5G New Radio (NR), LTE, LTE-A, or LTE-B. Of course, other multiple access schemes and wireless protocols may be utilized.

[0126] The RANs 82oa-82ob are in communication with the core network 830 to provide the EDs 8ioa-8ioc with voice, data, application, Voice over Internet Protocol (VoIP), or other services. Understandably, the RANs 82oa-82ob or the core network 830 may be in direct or indirect communication with one or more other RANs (not shown). The core network 830 may also serve as a gateway access for other networks (such as the PSTN 840, the Internet 850, and the other networks 860). In addition, some or all of the EDs 8ioa-8ioc may include functionality for communicating with different wireless networks over different wireless links using different wireless technologies or protocols. Instead of wireless communication (or in addition thereto), the EDs may communicateFW 6oooy6iPCTo2 23via wired communication channels to a service provider or switch (not shown), and to the Internet 850.

[0127] Although FIG. 8 illustrates one example of a communication system, various changes maybe made to FIG. 8. For example, the communication system 800 could include any number of EDs, base stations, networks, or other components in any suitable configuration.

[0128] FIGs. 9A and 9B illustrate example devices that may implement the methods and teachings according to this disclosure. In particular, FIG. 9A illustrates an example ED 910, and FIG. 9B illustrates an example base station 970. The ED 910 and the base station 970 may communicate over the air interface 990. These components could be used in the system 800 or in any other suitable system.

[0129] As shown in FIG. 9A, the ED 910 includes at least one processing unit 900. The processing unit 900 implements various processing operations of the ED 910. For example, the processing unit 900 could perform signal coding, data processing, power control, input / output processing, or any other functionality enabling the ED 910 to operate in the system 800. The processing unit 900 also supports the methods and teachings described in more detail above. Each processing unit 900 includes any suitable processing or computing device configured to perform one or more operations. Each processing unit 900 could, for example, include a microprocessor, microcontroller, digital signal processor, field programmable gate array, or application specific integrated circuit.

[0130] The ED 910 also includes at least one transceiver 902. The transceiver 902 is configured to modulate data or other content for transmission by at least one antenna or NIC (Network Interface Controller) 904. The transceiver 902 is also configured to demodulate data or other content received by the at least one antenna 904. Each transceiver 902 includes any suitable structure for generating signals for wireless or wired transmission or processing signals received wirelessly or by wire. Each antenna 904 includes any suitable structure for transmitting or receiving wireless or wired signals. One or multiple transceivers 902 could be used in the ED 910, and one or multiple antennas 904 could be used in the ED 910. Although shown as a single functional unit, a transceiver 902 could also be implemented using at least one transmitter and at least one separate receiver.

[0131] The ED 910 further includes one or more input / output devices 906 or interfaces (such as a wired interface to the Internet 850). The input / output devices 906 facilitate interaction with a user or other devices (network communications) in the network. Each input / output device 906 includes any suitable structure for providingFW 6000761PCT02 24information to or receiving information from a user, such as a speaker, microphone, keypad, keyboard, display, or touch screen, including network interface communications.

[0132] In addition, the ED 910 includes at least one memory 908. The memory 908 stores instructions and data used, generated, or collected by the ED 910. For example, the memory 908 could store software or firmware instructions executed by the processing unit(s) 900 and data used to reduce or eliminate interference in incoming signals. Each memory 908 includes any suitable volatile or non-volatile storage and retrieval device(s). Any suitable type of memory may be used, such as random access memory (RAM), read only memory (ROM), hard disk, optical disc, subscriber identity module (SIM) card, memory stick, secure digital (SD) memory card, and the like.

[0133] As shown in FIG. 9B, the base station 970 includes at least one processing unit 950, at least one transceiver 952, which includes functionality for a transmitter and a receiver, one or more antennas 956, at least one memory 958, and one or more input / output devices or interfaces 966. A scheduler, which would be understood by one skilled in the art, is coupled to the processing unit 950. The scheduler could be included within or operated separately from the base station 970. The processing unit 950 implements various processing operations of the base station 970, such as signal coding, data processing, power control, input / output processing, or any other functionality. The processing unit 950 can also support the methods and teachings described in more detail above. Each processing unit 950 includes any suitable processing or computing device configured to perform one or more operations. Each processing unit 950 could, for example, include a microprocessor, microcontroller, digital signal processor, field programmable gate array, or application specific integrated circuit.

[0134] Each transceiver 952 includes any suitable structure for generating signals for wireless or wired transmission to one or more EDs or other devices. Each transceiver 952 further includes any suitable structure for processing signals received wirelessly or by wire from one or more EDs or other devices. Although shown combined as a transceiver 952, a transmitter and a receiver could be separate components. Each antenna 956 includes any suitable structure for transmitting or receiving wireless or wired signals. While a common antenna 956 is shown here as being coupled to the transceiver 952, one or more antennas 956 could be coupled to the transceiver(s) 952, allowing separate antennas 956 to be coupled to the transmitter and the receiver if equipped as separate components. Each memory 958 includes any suitable volatile or non-volatile storage and retrieval device(s). Each input / output device 966 facilitates interaction with a user or other devices (network communications) in the network. Each input / output device 966 includes any suitable structure for providing information to or receiving / providing information from a user, including network interface communications.FW 6000761PCT02 25

[0135] FIG. 10 is a block diagram of a computing system woo that may be used for implementing the devices and methods disclosed herein. For example, the computing system can be any entity of UE, access network (AN), mobility management (MM), session management (SM), user plane gateway (UPGW), or access stratum (AS). Specific devices may utilize all of the components shown or only a subset of the components, and levels of integration may vary from device to device. Furthermore, a device may contain multiple instances of a component, such as multiple processing units, processors, memories, transmitters, receivers, etc. The computing system 1000 includes a processing unit 1002. The processing unit includes a central processing unit (CPU) 1014, memory 1008, and may further include a mass storage device 1004, a video adapter 1010, and an I / O interface 1012 connected to a bus 1020.

[0136] The bus 1020 may be one or more of any type of several bus architectures including a memory bus or memory controller, a peripheral bus, or a video bus. The CPU 1014 may comprise any type of electronic data processor. The memory 1008 may comprise any type of non-transitory system memory such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous DRAM (SDRAM), read-only memory (ROM), or a combination thereof. In an embodiment, the memory 1008 may include ROM for use at boot-up, and DRAM for program and data storage for use while executing programs.

[0137] The mass storage 1004 may comprise any type of non-transitory storage device configured to store data, programs, and other information and to make the data, programs, and other information accessible via the bus 1020. The mass storage 1004 may comprise, for example, one or more of a solid state drive, hard disk drive, a magnetic disk drive, or an optical disk drive.

[0138] The video adapter 1010 and the I / O interface 1012 provide interfaces to couple external input and output devices to the processing unit 1002. As illustrated, examples of input and output devices include a display 1018 coupled to the video adapter 1010 and a mouse, keyboard, or printer 1016 coupled to the I / O interface 1012. Other devices may be coupled to the processing unit 1002, and additional or fewer interface cards maybe utilized. For example, a serial interface such as Universal Serial Bus (USB) (not shown) may be used to provide an interface for an external device.

[0139] The processing unit 1002 also includes one or more network interfaces 1006, which may comprise wired links, such as an Ethernet cable, or wireless links to access nodes or different networks. The network interfaces 1006 allow the processing unit 1002 to communicate with remote units via the networks. For example, the network interfaces 1006 may provide wireless communication via one or more transmitters / transmit antennas and one or more receivers / receive antennas. In an embodiment, the processingFW 6000761PCT02 26unit 1002 is coupled to a local-area network 1022 or a wide-area network for data processing and communications with remote devices, such as other processing units, the Internet, or remote storage facilities.

[0140] It should be appreciated that not all components in the devices described in FIGs. 7-10 are required. In a non-limiting example, the ED 910 may be implemented as an AIoT device 910. But, the AIoT device 910 may not include the input / output devices 906 for providing information to or receiving information from a user, such as a speaker, microphone, keypad, keyboard, display, or touch screen. The transceiver 902 of the AIoT device 910 may be capable of transmitting by backscattering a radio wave received, instead of by generating the radio wave, for wireless communication purpose. In another non-limiting example, the system 1000 may be implemented as an AIoT device 1000 that does not include or use the mass storage device 1004, the video adapter 1010, the mouse, keyboard, or printer 1016, or the display 1018.

[0141] It should be appreciated that one or more steps of the embodiment methods provided herein maybe performed by corresponding units or modules. For example, a signal may be transmitted by a transmitting unit or a transmitting module. A signal may be received by a receiving unit or a receiving module. A signal may be processed by a processing unit or a processing module. Other steps may be performed by a performing unit or module, a generating unit or module, an obtaining unit or module, a setting unit or module, an adjusting unit or module, an increasing unit or module, a decreasing unit or module, a determining unit or module, a modifying unit or module, a reducing unit or module, a removing unit or module, or a selecting unit or module. The respective units or modules may be hardware, software, or a combination thereof. For instance, one or more of the units or modules may be an integrated circuit, such as field programmable gate arrays (FPGAs) or application-specific integrated circuits (ASICs).

[0142] Although the disclosure has been described in detail, it should be understood that various changes, substitutions and alterations can be made without departing from the spirit and scope of this disclosure as defined by the appended claims. Moreover, the scope of the disclosure is not intended to be limited to the particular implementations described herein, as one of ordinary skill in the art will readily appreciate from this disclosure that processes, machines, manufacture, compositions of matter, means, methods, or steps, presently existing or later to be developed, may perform substantially the same function or achieve substantially the same result as the corresponding implementations described herein. Accordingly, the appended claims are intended to include within their scope such processes, machines, manufacture, compositions of matter, means, methods, or steps.FW 6000761PCT02 27

Claims

WHAT IS CLAIMED IS:

1. A method comprising:receiving, by a network repository function (NRF) network entity from a sensing function network entity, a sensing function profile registration request indicating at least one parameter, the at least one parameter indicating at least one sensing service area of interest; andsending, by the NRF network entity to the sensing function network entity, a sensing function profile registration response.

2. The method of claim 1, the at least one parameter further indicating at least one of a network function (NF) type, at least one supported sensing mode, or at least one supported sensing type.

3. The method of claim 2, the at least one sensing service area of interest including one or more areas in which the sensing function network entity has sensing result or sensing data, the NF type being a sensing function type, the at least one supported sensing mode including one or more sensing modes for which the sensing function network entity has the sensing result or the sensing data, the at least one supported sensing type including at least one of tracking or detection.

4. The method of any of claims 1-3, further comprising:storing, by the NRF network entity, the at least one parameter as a sensing function profile corresponding to the sensing function network entity.

5. The method of claim 4, further comprising:receiving, by the NRF network entity, a discovery request for a sensing service; andsending, by the NRF network entity, a discovery response for sensing function selection.

6. The method of claim 5, wherein the discovery request is received from a trusted application function (AF), the discovery response is sent to the trusted AF, and the trusted AF selects the sensing function network entity based on the at least one sensing service area of interest of the sensing function profile after the trusted AF receives the discovery response.

7. The method of claim 5, wherein the discovery request is received from a network exposure functionality (NEF) network entity between the NRF network entity and an untrusted AF, and the discovery response is sent to the NEF network entity.FW 6000761PCT02 288. The method of claim 7, wherein, before the NEF network entity sends the discovery request, the NEF network entity performs:receiving, from the untrusted AF, a sensing service request for the sensing service, the sensing service request indicating selection criteria, the selection criteria including at least one of a sensing service area of interest or a sensing service time period of interest; anddetermining, based on configured policies, whether the untrusted AF is entitled to request the sensing service,wherein the NEF network entity sends the discovery request on behalf of the untrusted AF using the selection criteria.

9. The method of claim 8, wherein, after the NEF network entity receives the discovery response, the NEF network entity performs:selecting the sensing function network entity;assigning a sensing coordination identifier (ID) corresponding to the sensing function network entity; andsending, to the untrusted AF, a sensing service response, the sensing service response including the sensing coordination ID,wherein the untrusted AF stores the sensing coordination ID and uses the sensing coordination ID in subsequent interactions with the NEF network entity for the sensing service.

10. The method of claim 9, the sensing service response further including information about how the sensing coordination ID relates to the selection criteria.

11. The method of claim 7, wherein the untrusted AF is outside a trusted domain corresponding to an operator of the sensing function network entity.

12. A method comprising:sending, by a sensing function network entity to a network repository function (NRF) network entity, a sensing function profile registration request indicating at least one parameter, the at least one parameter indicating at least one sensing service area of interest; andreceiving, by the sensing function network entity from the NRF network entity, a sensing function profile registration response.

13. The method of claim 12, the at least one parameter further indicating at least one of a network function (NF) type, at least one supported sensing mode, or at least one supported sensing type.FW 6000761PCT02 2914- The method of claim 13, the at least one sensing service area of interest including one or more areas in which the sensing function network entity has sensing result or sensing data, the NF type being a sensing function type, the at least one supported sensing mode including one or more sensing modes for which the sensing function network entity has the sensing result or the sensing data, the at least one supported sensing type including at least one of tracking or detection.

15. A method comprising:sending, by a trusted application function (AF) to a network repository function (NRF) network entity, a discovery request for a sensing service;receiving, by the trusted AF from the NRF network entity, a discover}" response; andselecting, by the trusted AF, a sensing function network entity based on at least one parameter of a sensing function profile, the at least one parameter indicating at least one sensing service area of interest.

16. The method of claim 15, the at least one parameter further indicating at least one of a network function (NF) type, at least one supported sensing mode, or at least one supported sensing type.

17. The method of claim 16, the at least one sensing service area of interest including one or more areas in which the sensing function network entity has sensing result or sensing data, the NF type being a sensing function type, the at least one supported sensing mode including one or more sensing modes for which the sensing function network entity has the sensing result or the sensing data, the at least one supported sensing type including at least one of tracking or detection.

18. A method comprising:sending, by an untrusted application function (AF) to a network exposure functionality (NEF) network entity, a sensing service request for a sensing service, the sensing service request indicating selection criteria, the selection criteria including at least one of a sensing service area of interest or a sensing service time period of interest; andreceiving, by the untrusted AF from the NEF network entity, a sensing service response, the sensing service response including a sensing coordination identifier (ID) corresponding to a sensing function network entity selected by the NEF network entity.

19. The method of claim 18, further comprising:storing, by the untrusted AF, the sensing coordination ID; andFW 6000761PCT02 30using, by the untrusted AF, the sensing coordination ID for interactions with the NEF network entity for the sensing service.

20. The method of any of claims 18-19, the sensing service response further including information about how the sensing coordination ID relates to the selection criteria.

21. The method of any of claims 18-20, wherein the untrusted AF is outside a trusted domain corresponding to an operator of the NEF network entity.

22. A method comprising:receiving, by a network exposure functionality (NEF) network entity from an untrusted application function (AF), a sensing service request for a sensing service, the sensing service request indicating selection criteria, the selection criteria including at least one of a sensing service area of interest or a sensing service time period of interest;determining, by the NEF network entity based on configured policies, that the untrusted AF is entitled to request the sensing service;in response to the determining, sending, by the NEF network entity to a network repository function (NRF) network entity, a discovery request for the sensing service;receiving, by the NEF network entity from the NRF network entity, a discovery response for sensing function selection;selecting, by the NEF network entity, a sensing function network entity; assigning, by the NEF network entity, a sensing coordination identifier (ID) corresponding to the sensing function network entity; andsending, by the NEF network entity to the untrusted AF, a sensing service response, the sensing service response including the sensing coordination ID.

23. The method of claim 22, the sensing service response further including information about how the sensing coordination ID relates to the selection criteria.

24. A network repository function (NRF) network entity comprising:at least one processor; anda non-transitory computer readable storage medium storing programming, the programming including instructions that, when executed by the at least one processor, cause the NRF network entity to perform a method according to any of claims 1-11.

25. A sensing function network entity comprising:at least one processor; anda non-transitory computer readable storage medium storing programming, the programming including instructions that, when executed by the at least one processor,FW 6000761PCT02 31cause the sensing function network entity to perform a method according to any of claims 12-14.

26. A trusted application function (AF) comprising:at least one processor; anda non-transitory computer readable storage medium storing programming, the programming including instructions that, when executed by the at least one processor, cause the trusted AF to perform a method according to any of claims 15-17.

27. An untrusted application function (AF) comprising:at least one processor; anda non-transitory computer readable storage medium storing programming, the programming including instructions that, when executed by the at least one processor, cause the untrusted AF to perform a method according to any of claims 18-21.

28. A network exposure functionality (NEF) network entity comprising:at least one processor; anda non-transitory computer readable storage medium storing programming, the programming including instructions that, when executed by the at least one processor, cause the NEF network entity to perform a method according to any of claims 22-23.

29. A non-transitory computer-readable medium having instructions stored thereon that, when executed by a network repository function (NRF) network entity, cause the NRF network entity to perform a method according to any of claims 1-11.

30. A non-transitory computer-readable medium having instructions stored thereon that, when executed by a sensing function network entity, cause the sensing function network entity to perform a method according to any of claims 12-14.

31. A non-transitory computer-readable medium having instructions stored thereon that, when executed by a trusted application function (AF), cause the trusted AF to perform a method according to any of claims 15-17.

32. A non-transitory computer-readable medium having instructions stored thereon that, when executed by an untrusted application function (AF), cause the untrusted AF to perform a method according to any of claims 18-21.

33. A non-transitory computer-readable medium having instructions stored thereon that, when executed by a network exposure functionality (NEF) network entity, cause the NEF network entity to perform a method according to any of claims 22-23.FW 6000761PCT02 32

Images