Approaches for supporting sensing function and sensing entity registration, discovery, and selection

The proposed method and network architecture address the challenges of registering, discovering, and selecting sensing entities and functions in 5G systems, enhancing the efficiency and effectiveness of sensing services for diverse applications.

WO2026235386A1PCT designated stage Publication Date: 2026-11-12SAMSUNG ELECTRONICS CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/KR2026/005968
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2026-03-23
Filing Date
2026-05-11
Publication Date
2026-11-12

AI Technical Summary

Technical Problem

Existing 5G mobile communication systems face challenges in efficiently managing the registration, discovery, and selection of sensing entities and functions, particularly in supporting diverse sensing services and use cases such as object detection and tracking, which are essential for enhanced functionalities like AR, VR, and drone communication.

Method used

A method and network architecture that includes a sensing function (SF), network repository function (NRF), and access and mobility management function (AMF) to facilitate the discovery and selection of sensing services and entities, enabling efficient registration and selection processes through network interactions.

Benefits of technology

Enhances the ability of 5G networks to support diverse sensing services by optimizing the registration, discovery, and selection of sensing entities, improving the efficiency and effectiveness of sensing operations.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure KR2026005968_12112026_PF_FP_ABST
    Figure KR2026005968_12112026_PF_FP_ABST
Patent Text Reader

Abstract

The disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. A method for sensing function (SF) discovery and selection in a mobile communications network, the method comprising: transmitting, from a sensing service consumer to a network repository function (NRF), a discovery request corresponding to a sensing service; determining, by the NRF, one or more sensing functions (SF) based on the discovery request; transmitting, from the NRF to the sensing service consumer, an indication of the one or more SFs; and selecting, by the sensing service consumer, a SF from the one or more SFs to provide the sensing service.
Need to check novelty before this filing date? Find Prior Art

Description

APPROACHES FOR SUPPORTING SENSING FUNCTION AND SENSING ENTITY REGISTRATION, DISCOVERY, AND SELECTION

[0001] Certain examples of the present disclosure provide methods and apparatus for supporting sensing function and sensing entity registration, discovery, and selection.

[0002] 5G mobile communication technologies define broad frequency bands such that high transmission rates and new services are possible, and can be implemented not only in "Sub 6GHz" bands such as 3.5GHz, but also in "Above 6GHz" bands referred to as mmWave including 28GHz and 39GHz. In addition, it has been considered to implement 6G mobile communication technologies (referred to as Beyond 5G systems) in terahertz bands (for example, 95GHz to 3THz bands) in order to accomplish transmission rates fifty times faster than 5G mobile communication technologies and ultra-low latencies one-tenth of 5G mobile communication technologies.

[0003] At the beginning of the development of 5G mobile communication technologies, in order to support services and to satisfy performance requirements in connection with enhanced Mobile BroadBand (eMBB), Ultra Reliable Low Latency Communications (URLLC), and massive Machine-Type Communications (mMTC), there has been ongoing standardization regarding beamforming and massive MIMO for mitigating radio-wave path loss and increasing radio-wave transmission distances in mmWave, supporting numerologies (for example, operating multiple subcarrier spacings) for efficiently utilizing mmWave resources and dynamic operation of slot formats, initial access technologies for supporting multi-beam transmission and broadbands, definition and operation of BWP (BandWidth Part), new channel coding methods such as a LDPC (Low Density Parity Check) code for large amount of data transmission and a polar code for highly reliable transmission of control information, L2 pre-processing, and network slicing for providing a dedicated network specialized to a specific service.

[0004] Currently, there are ongoing discussions regarding improvement and performance enhancement of initial 5G mobile communication technologies in view of services to be supported by 5G mobile communication technologies, and there has been physical layer standardization regarding technologies such as V2X (Vehicle-to-everything) for aiding driving determination by autonomous vehicles based on information regarding positions and states of vehicles transmitted by the vehicles and for enhancing user convenience, NR-U (New Radio Unlicensed) aimed at system operations conforming to various regulation-related requirements in unlicensed bands, NR UE Power Saving, Non-Terrestrial Network (NTN) which is UE-satellite direct communication for providing coverage in an area in which communication with terrestrial networks is unavailable, and positioning.

[0005] Moreover, there has been ongoing standardization in air interface architecture / protocol regarding technologies such as Industrial Internet of Things (IIoT) for supporting new services through interworking and convergence with other industries, IAB (Integrated Access and Backhaul) for providing a node for network service area expansion by supporting a wireless backhaul link and an access link in an integrated manner, mobility enhancement including conditional handover and DAPS (Dual Active Protocol Stack) handover, and two-step random access for simplifying random access procedures (2-step RACH for NR). There also has been ongoing standardization in system architecture / service regarding a 5G baseline architecture (for example, service based architecture or service based interface) for combining Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC) for receiving services based on UE positions.

[0006] As 5G mobile communication systems are commercialized, connected devices that have been exponentially increasing will be connected to communication networks, and it is accordingly expected that enhanced functions and performances of 5G mobile communication systems and integrated operations of connected devices will be necessary. To this end, new research is scheduled in connection with eXtended Reality (XR) for efficiently supporting AR (Augmented Reality), VR (Virtual Reality), MR (Mixed Reality) and the like, 5G performance improvement and complexity reduction by utilizing Artificial Intelligence (AI) and Machine Learning (ML), AI service support, metaverse service support, and drone communication.

[0007] Furthermore, such development of 5G mobile communication systems will serve as a basis for developing not only new waveforms for providing coverage in terahertz bands of 6G mobile communication technologies, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), array antennas and large-scale antennas, metamaterial-based lenses and antennas for improving coverage of terahertz band signals, high-dimensional space multiplexing technology using OAM (Orbital Angular Momentum), and RIS (Reconfigurable Intelligent Surface), but also full-duplex technology for increasing frequency efficiency of 6G mobile communication technologies and improving system networks, AI-based communication technology for implementing system optimization by utilizing satellites and AI (Artificial Intelligence) from the design stage and internalizing end-to-end AI support functions, and next-generation distributed computing technology for implementing services at levels of complexity exceeding the limit of UE operation capability by utilizing ultra-high-performance communication and computing resources.

[0008] Embodiments of the present disclosure may provide a network entity, methods performed by sensing function and methods performed by access and mobility management function.

[0009] It is an aim of certain examples of the present disclosure to address, solve and / or mitigate, at least partly, at least one of the problems and / or disadvantages associated with the related art, for example at least one of the problems and / or disadvantages described herein. It is an aim of certain examples of the present disclosure to provide at least one advantage over the related art, for example at least one of the advantages described herein.

[0010] In accordance with a first aspect of the present disclosure, there is provided a method for sensing function (SF) discovery and selection in a mobile communications network, the method comprising: transmitting, from a sensing service consumer to a network repository function (NRF), a discovery request corresponding to a sensing service; determining, by the NRF, one or more sensing functions (SF) based on the discovery request; transmitting, from the NRF to the sensing service consumer, an indication of the one or more SFs; and selecting, by the sensing service consumer, a SF from the one or more SFs to provide the sensing service.

[0011] In an example, the discovery request includes information on network function type and a sensing service area, and the one or more SFs are SFs that match the information of the discovery request, wherein the network function type is a network function that supports the sensing service.

[0012] In an example, the discovery request is transmitted to the NRF from the sensing service consumer via a network exposure function (NEF) and the indication of the one or more SFs is transmitted from the NRF to the sensing service consumer via the NEF.

[0013] In an example, the method further comprises transmitting, from each of the one or more SFs to the NRF, a registration request including a network function (NF) profile of the respective SF; registering, by the NRF, the NF profiles of the one or more SFs; and transmitting, from the NRF to each of the SFs, a respective registration response.

[0014] In an example, the NF profile of a SF includes information on a type of sensing supported by the SF and SF location information.

[0015] In an example, a type of sensing includes one or more of user equipment (UE)-based, network-based, device-based, device-free, object detection, object movement detection, and detection of certain types of object.

[0016] In an example, the method further comprises transmitting, from the sensing service consumer to the SF, a sensing service request; and selecting, by the SF, one or more sensing entities from a plurality of sensing entities based on the sensing service request for the sensing service.

[0017] In an example, the method further comprises transmitting, from the SF to a NF, in response to the sensing service request, a request for sensing entity information; transmitting, from the NF to the SF, information on the plurality of sensing entities.

[0018] In an example, the request for sensing entity information includes an area of interest and / or a list of sensing entities, and the plurality of sensing entities are sensing entities included in the area of interest and / or the list of sensing entities.

[0019] In an example, the method further comprises determining, by the NF, the plurality of sensing entities based on the area of interest and the list of sensing entities.

[0020] In an example, the NF transmits to the SF, information on the sensing entities included in the list.

[0021] In an example, the NF is an access and mobility management function (AMF), or an Operations, Administration, and Maintenance (OAM) entity.

[0022] In an example, the selecting, by the SF, is based on an area of interest included in the sensing service request.

[0023] In an example, the area of interest is a target sensing area.

[0024] In an example, the method further comprises reselecting one or more sensing entities based on the sensing service request for an ongoing sensing service corresponding to the sensing service request.

[0025] In an example, the plurality of sensing entities includes one or more of a user equipment (UE) and a gNB.

[0026] In an example, the method further comprises transmitting, from the SF to the selected one or more sensing entities, a notification of selection for a sensing service.

[0027] In an example, the method further comprises transmitting, from each of the plurality of sensing entities to the NF, a registration request including sensing-related information of the respective sensing entity, wherein the information on the plurality of sensing entities includes the sensing-related information.

[0028] In an example, the sensing-related information includes capability information of the respective sensing entity.

[0029] In an example, the method further comprises transmitting, from the NF to the plurality of sensing entities, a registration response in response to the registration request.

[0030] In an example, each of the plurality of sensing entities is authorised by the network to perform as a sensing transmitter and / or a sensing receiver.

[0031] In an example, the method further comprises authorising, by the SF, the sensing service consumer to request a sensing service.

[0032] In an example, the mobile communications network is a 3GPP-compliant mobile communications network.

[0033] In accordance with a second aspect of the present disclosure, there is provided a mobile communications network comprising a sensing function (NF), a network repository function (NRF), a network function, and access and mobility management function (AMF), an Operations, Administration, and Maintenance (OAM) entity, and a plurality of sensing entities, where the mobile communications network is configured to implement the method of any preceding aspect and example.

[0034] In accordance with a third aspect of the present disclosure, there is provided a method of a sensing function (SF) for use in a mobile communications network, the method comprising: transmitting, from the SF to an network repository function (NRF), a registration request including a network function (NF) profile of the SF; receiving, at the SF from the NRF, a registration response; receiving, from a sensing service consumer, a sensing service request; and selecting, by the SF, one or more sensing entities from a plurality of sensing entities based on the sensing service request for the sensing service.

[0035] In accordance with a fourth aspect of the present disclosure, there is provided a sensing function (SF) for use in a mobile communications network, wherein the SF is configured to implement the above method of a sensing function.

[0036] In accordance with a fifth aspect of the present disclosure, there is provided a method of a sensing entity for use in a mobile communications network, the method comprising: transmitting, to a network function (NF), a registration request including sensing-related information of the sensing entity; receiving, from a sensing function (SF), a notification of selection of the sensing entity for a sensing service; and transmitting, from the sensing entity to the SF, a response accepting the selection.

[0037] In accordance with a sixth aspect of the present disclosure, there is provided a sensing entity for use in a mobile communications network, wherein the sensing entity is configured to implement the above method of the sensing entity.

[0038] In accordance with a seventh aspect of the present disclosure, there is provided a method of a network repository function (NRF) for use in a mobile communications network, the method comprising: receiving, from each of one or more sensing functions (SFs), a registration request including a network function (NF) profile of the respective SF; registering the NF profiles of the one or more SFs; receiving, from a sensing service consumer, a discovery request corresponding to a sensing service; determining one or more SFs based on the discovery request and the registered NF profiles; and transmitting, to the sensing service consumer, an indication of the determined one or more SFs.

[0039] In accordance with a eighth aspect of the present disclosure, there is provided a network repository function (NRF) for use in a mobile communications network, wherein the NRF is configured to implement the above method of a network repository function.

[0040] Other aspects, advantages, and salient features of the disclosure will become apparent to those skilled in the art from the following detailed description taken in conjunction with the accompanying drawings.

[0041] Embodiments of the present disclosure may provide a network entity, methods performed by sensing function and methods performed by access and mobility management function.

[0042] Embodiments / examples of the present disclosure are further described hereinafter with reference to the accompanying drawings, in which:

[0043] Figure 1 provides an example of sensing with co-located sensing receiver and sensing transmitter;

[0044] Figure 2 provides an example of sensing with separated sensing receiver and sensing transmitter;

[0045] Figure 3 provides an example procedure for the registration of sensing related information and / or sensing entities in accordance with the present disclosure;

[0046] Figure 4 provides an example procedure for sensing function discovery in accordance with the present disclosure;

[0047] Figure 5 provides an example procedure for sensing entity discover and (re-) selection in accordance with the present disclosure; and

[0048] Figure 6 provides a block diagram of an exemplary network entity / function that may be used in certain examples of the present disclosure.

[0049]

[0050] The content of the following documents is referred to below and / or their content provides background information and context that the following disclosure should be considered in view of:

[0051] 3GPP TS 22.137 v19.1.0 April 2024

[0052] 3GPP TR 22.837 v19.4.0 June 2024

[0053] 3GPP TS 38.901 v18.0.0 April 2024

[0054] 3GPP TR 23.700-14 v0.1.0 April 2025

[0055] 3GPP TS 23.502 v19.3.0 March 2025

[0056] S2-2502780, 3GPP TSG WG-2 Meeting #167, 17 - 21 February 2025

[0057] SP-250067, 3GPP TSG SA Meeting #107, 12 - 14 March, 2025

[0058] (Note: the example versions shown for each TS are non-limiting, other versions of the TS may be considered also)

[0059] Wireless or mobile (cellular) communications networks in which a mobile terminal (e.g., user equipment (UE), such as a mobile handset) communicates via a radio link with a network of base stations, or other wireless access points or nodes, have undergone rapid development through a number of generations. The 3rdGeneration Partnership Project (3GPP) design, specify and standardise technologies for mobile wireless communication networks. Fourth Generation (4G) and Fifth Generation (5G) systems are now widely deployed, and development of Sixth Generation (6G) Systems is in progress.

[0060] 3GPP standards for 4G systems include an Evolved Packet Core (EPC) and an Enhanced-UTRAN (E-UTRAN: an Enhanced Universal Terrestrial Radio Access Network). The E-UTRAN uses Long Term Evolution (LTE) radio technology. LTE is commonly used to refer to the whole system including both the EPC and the E-UTRAN, and LTE is used in this sense in the remainder of this document. LTE should also be taken to include LTE enhancements such as LTE Advanced and LTE Pro, which offer enhanced data rates compared to LTE.

[0061] In 5G systems a new air interface has been developed, which may be referred to as 5G New Radio (5G NR) or simply NR. NR is designed to support the wide variety of services and use case scenarios envisaged for 5G networks, though builds upon established LTE technologies. New frameworks and architectures are also being developed as part of 5G networks in order to increase the range of functionality and use cases available through 5G networks.

[0062] In addition to conventional communication applications of such networks, approaches for sensing have been and continue to be developed for existing and future systems.

[0063] 3GPP SA1 work on Integrated Sensing and Communication

[0064] As documented in TR 22.837, there are various use cases requires the support of 3GPP sensing. Some of the use cases may require the 3GPP sensing and non-3GPP sensing work jointly. For example, the integrated sensing could be used to detect of different type of objects / intruders of smart home, in smart factory, on road, around railway. It is also useful for UAV operation to avoid collisions between UAVs and between UAV and other objects. And other various use cases, e.g. to detect rainfall and flood, management of traffic flow and parking control, health and sleep monitoring at home, etc.

[0065] As documented in TS 22.137:

[0066] 5G wireless sensing is a technology enabler to acquire information about characteristics of the environment and / or objects within the environment, that uses radio frequency to determine the distance (range), angle, or instantaneous linear velocity of objects, etc.

[0067] Radio frequency sensing functionality provides services for device-free object localization as there is lack of need for the object to be connected via a device in the network. The estimation of parameters such as signal strength, delay, doppler and angle spectrum information is obtained from scattered and / or reflected radio frequency signals transmitted and received by RAN nodes or UEs by using NR radio frequency signals and, in some cases, previously defined information available in EPC and / or E-UTRAN, without leading to impacts on EPC and E-UTRAN. By processing these radio frequency signals, features such as the location, velocity, geometric information of the objects can be extracted and further exposed together with contextual information towards different applications.

[0068] The capabilities to obtain range, velocity, and angle information from the radio frequency signals can provide a broad range of new functionality, such as various objects detection, object recognition (e.g., vehicle, human, animal, UAV) and high accuracy localization, tracking and activity recognition.

[0069] This technical specification describes the sensing technology as part of the 5G system for enabling new services and use cases. 5G wireless sensing service provides new possibilities for enhanced usage of the telecommunication infrastructure. It provides input to different verticals (e.g., UAVs, smart home, V2X, factories, railways, public safety, etc) enabling applications offering e.g., intruder detection, assisted automotive maneuvering and navigation, trajectory tracing, collision avoidance, traffic management, health and activity monitoring.

[0070] In some cases, 5G wireless sensing can also use non-3GPP type sensors (e.g., Radar, camera) to further support the 3GPP-based sensing.

[0071] SA1 consolidated the functional requirement to support integrated sensing by 3GPP. As documented in clause 7.1 of TR 22.837, the functional requirements include the following tables.

[0072] Table 1: Table 7.1.1-1 of TR 22.837 General Consolidated Requirements

[0073]

[0074]

[0075]

[0076]

[0077] Table 2: Table 7.1.2-1 of TR 22.837 Configuration and authorization Consolidated

[0078] Requirements

[0079]

[0080]

[0081] Table 3: Table 7.1.3-1 of TR 22.837 Network exposure Consolidated Requirements

[0082]

[0083]

[0084]

[0085] Table 4: Table 7.1.4-1 of TR 22.837 Security Consolidated Requirements

[0086]

[0087]

[0088] Table 5: Table 7.1.5-1 of TR 22.837 Charging Consolidated Requirements

[0089]

[0090] Sensing Operations Defined by 3GPP

[0091] As documented in clause 4.2 of TS 22.137:

[0092] The operation of the 5G wireless sensing service, a.k.a. sensing operation, relies on processing the transmissions, reflections, and scattering of wireless sensing signals.

[0093] 5G wireless sensing, therefore, has the opportunity to enhance the 5G system from a communication network to a wireless communication and sensing network, where it uses 5G entities to sense objects and the environment in its surroundings.

[0094] Sensing operation can be implemented in a couple of different ways, from radar like sensing where the sensing transmitter and sensing receiver are co-located in the same entity (figure 4.2-1), called Monostatic sensing, to have the sensing receiver and sensing transmitter in different entities (figure 4.2-2), also called Bistatic sensing. A more advanced scenario with multiple sensing transmitters and receivers is also possible, called Multistatic sensing. The reflections of the sensing signal sent from the sensing transmitter are received by the sensing receiver and processed to obtain characteristics of the sensed object and its environment (e.g., location). Below figure 4.2-1 and figure 4.2-2 show examples of the sensing operation and the nomenclature used in this specification.

[0095] Non-3GPP based sensing is when information from non-3GPP sensors is used to determine characteristics of objects and their environment. These non-3GPP sensors could include radar camera or Wi-Fi sensing. While the mechanism of these types of sensing is not considered in this specification, non-3GPP sensing data from these non-3GPP sensors, if available, can be used in 5G wireless sensing to achieve improved sensing result, or in any other way to enhance the sensing service.

[0096] The 5G wireless sensing service could be consumed by either the 3GPP system or trusted third-party.

[0097] It is expected that the 5G wireless sensing service will work independently of positioning service.

[0098] There are some factors affecting the performance that the 5G wireless sensing service can achieve e.g.,

[0099] - Operating frequencies and used bandwidth.

[0100] - The propagation environment also plays an important role. Environments with many objects that can block radio signals, leading to interruption of the Line of Sight (LOS) path and reflections / scattering can increase the number of interfering signal paths, as well as clutter and thus make it harder to reach higher resolutions.

[0101] Sensing operations, such as authorization, and parameters such as sensing area, sensing operation period and sensing operation time window etc., could be configured and adjusted for efficient use of all kinds of resources, such as energy and radio spectrum, etc.

[0102]

[0103] There are two major types of sensing operations: Monostatic and Bistatic sensing. There is also a more advanced scenario - Multistatic sensing.

[0104] Monostatic sensing: the sensing transmitter and sensing receiver are co-located in the same entity, as shown in Figure 1, which shows an example of sensing with co-located sensing receiver and sensing transmitter as defined in TS 22.137.

[0105] Bistatic sensing: have the sensing receiver and sensing transmitter in different entities, as shown in Figure 2, which shows an example of sensing with separated sensing receiver and sensing transmitter of as defined in TS 22.137.

[0106] 5G Wireless Sensing Performance Requirements

[0107] As documented in clause 6 of TS 22.137:

[0108] 5G wireless Sensing service is required to fulfil different performance requirement (e.g., accuracy, resolution, latency, etc.) based on the characteristics of one or multiple target object(s) and / or the environment to be sensed in a target sensing service area. The following set of key performance requirements is used:

[0109] - Accuracy of positioning estimate describes the closeness of the measured sensing result (i.e., position) of the target object to its true position value. It can be further derived into a horizontal sensing accuracy - referring to the sensing result error in a 2D reference or horizontal plane, and into a vertical sensing accuracy - referring to the sensing result error on the vertical axis or altitude.

[0110] - Accuracy of velocity estimate describes the closeness of the measured sensing result (i.e., velocity) of the target object to its true velocity.

[0111] - Confidence level describes the percentage of all the possible measured sensing results that can be expected to include the true sensing result considering the accuracy.

[0112] - Sensing Resolution describes the minimum difference in the measured magnitude of target objects (e.g., range, velocity) to be allowed to detect objects in different magnitude.

[0113] - Missed detection probability describes the conditional probability of not detecting the presence of target object / environment when the target object / environment is present. This probability is denoted by the ratio of the number of events falsely identified as negative, over the total number of events with a positive state. It applies only to binary sensing results.

[0114] - False alarm probability describes the conditional probability of falsely detecting the presence of target object / environment when the target object / environment is not present. This probability is denoted by the ratio of the number of events falsely identified as being positive, over the total number of events with a negative state. It applies only to binary sensing results.

[0115] - Max sensing service latency: time elapsed between the event triggering the determination of the sensing result and the availability of the sensing result at the sensing system interface.

[0116] - Refreshing rate: rate at which the sensing result is generated by the sensing system. It is the inverse of the time elapsed between two successive sensing results.

[0117] 5G wireless sensing performance requirements are applied to 3GPP sensing data and sensing results.

[0118]

[0119] The performance requirements for 5G Wireless sensing are detailed in Table 6.2-1 of TS 22.137 shown below.

[0120] Table 6: Table 6.2-1 of TS 22.137 Performance requirements for 5G Wireless sensing

[0121]

[0122]

[0123]

[0124] 3GPP RAN1 Work on Study on Channel Modelling for Integrated Sensing and Communication (ISAC) for NR

[0125] 3GPP RAN1 working group studied channel modelling for integrated sensing and communication for NR for the objectives documented in SID RP-242348, including:

[0126] The focus of the study is to define channel modelling aspects to support object detection and / or tracking (as per the SA1 meaning in TS 22.137). The study should aim at a common modelling framework capable of detecting and / or tracking the following example objects and to enable them to be distinguished from unintended objects:

[0127] * UAVs

[0128] * Humans indoors and outdoors

[0129] * Automotive vehicles (at least outdoors)

[0130] * Automated guided vehicles (e.g. in indoor factories)

[0131] * Objects creating hazards on roads / railways, with a minimum size dependent on frequency

[0132]

[0133] All six sensing modes should be considered (i.e. TRP-TRP bistatic, TRP monostatic, TRP-UE bistatic, UE-TRP bistatic, UE-UE bistatic, UE monostatic).

[0134] Frequencies from 0.5 to 52.6 GHz are the primary focus, with the assumption that the modelling approach should scale to 100 GHz. (If significant problems are identified with scaling above 52.6 GHz, the range above 52.6 GHz can be deprioritized.)

[0135] For the above use cases, sensing modes and frequencies:

[0136] * Identify details of the deployment scenarios corresponding to the above use cases.

[0137] * Define channel modelling details for sensing using 38.901 as a starting point, and taking into account relevant measurements, including:

[0138] ** modelling of sensing targets and background environment, including, for example (if needed by the above use cases), radar cross-section (RCS), mobility and clutter / scattering patterns;

[0139] ** spatial consistency.

[0140]

[0141] TRP is the Transmission and Reception Point.

[0142] The outcome of the study item is documented in TR 38.901. SA1 identified the major parameters of channel modelling for different sensing operation scenarios by considering the transmitter and receiver entities, including TRP-TRP, TRP-terrestrial UE, TRP-vehicle UE, TRP-aerial UE, terrestrial UE- terrestrial UE, terrestrial UE - vehicle UE, terrestrial UE-aerial UE, vehicle UE - vehicle UE, aerial UE - aerial UE.

[0143] Standards Background of ISAC in 3GPP SA2 Working Group

[0144] 3GPP SA2 New SID on Study on Architecture Enhancement to support Integrated Sensing and Communication (ISAC) was approved in Feb 2025 during SA2#167 S2-2502780. Then the SID was further modified and approved during SA#107 meeting in March 2025 in SP-250067. The following aspects will be studied:

[0145] WT-1: Architecture and function enhancements to support sensing.

[0146] - WT-2: Service authorization and revocation. This includes investigating mechanisms for authorization and revocation sensing service requests from the service consumer.

[0147] - WT-3: Discovery and selection of sensing entities based on service requirements triggered by the service request and capability of the sensing entities.

[0148] - WT-4: Sensing data and the associated information collection and transport mechanisms for result calculation.

[0149] - WT-5: Mechanisms for providing sensing associated information and result (including sensing result and contextual information) exposure, for one time, periodic or event based reporting.

[0150] - WT-6: Configuration parameters / policy provisioning for the support of ISAC services.

[0151]

[0152] The Key Issue (KI) description of the above WTs (work tasks) were discussed and agreed during SA2#168 meeting in Feb 2025. The agreed KI descriptions were documented in clause 5 of TR 23.700-14, including:

[0153] 5.1 Key Issue #1: System Architecture to Support Sensing

[0154] This key issue will address the general system architecture and function enhancements required to provide end-to-end support for sensing. The general architecture aspects that need to be studied include any new and / or existing functions in the Core Network and their interactions that should be involved in providing support for sensing. Potential privacy requirements if identified will be considered for this key issue.

[0155] NOTE: Solutions for other key issues may also impact general architecture aspects covered by this key issue.

[0156] 5.2 Key Issue #2: Authorization and Revocation to Support Sensing Service

[0157] The key issue is to address the authorization and revocation for a particular sensing service, specifically:

[0158] - authorization of sensing service requests and revocation of an on-going sensing service; and

[0159] - authorization and revocation for the sensing entities if applicable.

[0160] For the authorization of the sensing service request, and the revocation of an on-going sensing service, the study needs to address the following aspects:

[0161] - whether and how to perform sensing service request authorization if required, and the criteria for the sensing service request authorization, based on the requirements from TS 22.137 [2];

[0162] - whether and how to perform sensing service revocation if required, and the criteria for the revocation, based on the requirements from TS 22.137 [2];

[0163] - whether, how and which entity( / entities) performs the sensing service request authorization and sensing service revocation if required;

[0164] - whether and where to store the sensing service request authorization information and sensing service revocation information, and when and how to update the authorization and revocation information if required.

[0165] For the authorization and revocation for the sensing entities if applicable, the study needs to address the following aspects:

[0166] - whether, when and which entity performs the authorization and revocation of the sensing entity( / entities);

[0167] - if needed, the granularity of the sensing entity authorization, e.g. based on TS 22.137 [2];

[0168] - if needed, storage and management of the authorization information for the sensing entities.

[0169] NOTE: The authorization and revocation for the sensing entities can be related to the key issue #3 on sensing entities discovery and selection.

[0170] 5.3 Key Issue #3: Sensing Entity and Sensing Function Discovery and (Re-)Selection

[0171] This key issue aims to study how to perform the Sensing entity(ies) and Sensing Function(s) discovery and (re-)selection, in particular:

[0172] - When required, for the discovery and (re-)selection of the Sensing entity(ies), the study needs to address the following aspects:

[0173] - Which entity(ies) performs the discovery and (re-)selection of the Sensing entity(ies);

[0174] - What the information and / or criteria are taken into account for the discovery and (re-)selection of the Sensing entity(ies); and

[0175] - The procedure(s) for the discovery and (re-)selection of the Sensing entity(ies).

[0176] - When required, for the discovery and (re-)selection of the Sensing Function(s), the study needs to address the following aspects:

[0177] - Which entity(ies) performs the discovery and (re-)selection of Sensing Function(s);

[0178] - What the information and / or criteria are taken into account for the discovery and (re-)selection of Sensing Function(s); and

[0179] - The procedure(s) for the discovery and (re-)selection of the Sensing Function(s).

[0180] 5.4 Key Issue #4: Sensing Data and the Associated Information Collection and Transport

[0181] Integration of sensing and communication requires 3GPP network to collect and transfer sensing data and the associated information to a Sensing Function.

[0182] This Key Issue aims to study:

[0183] - How to collect sensing data (and the associated information, if any) for sensing result generation?

[0184] - Which Sensing Function performs sensing result generation?

[0185] - Whether and what the above associated information is required for sensing result generation

[0186] NOTE: Implications to RAN or RAN dependent aspects will be coordinated with RAN WGs.

[0187] 5.5 Key Issue #5: Sensing Result Exposure

[0188] This key issue addresses the exposure of sensing results to support sensing services. The aspects to be studied in this key issue include:

[0189] - Study what types of sensing results with or without the sensing contextual information defined in TS 22.137 [2] could be exposed from the Core Network to the sensing service consumer.

[0190] - How the Core Network exposes sensing results to the sensing service consumer (e.g., one time, periodic or event trigger).

[0191] 5.6 Key Issue #6: Configuration Parameter Provisioning of Sensing Entities.

[0192] This Key Issue will study how parameter provisioning of sensing entities is performed.

[0193] In particular, this Key Issue will study:

[0194] - How and what parameters need to be exchanged between the sensing entities and the Core Network.

[0195] NOTE: This KI needs to be aligned with RAN WGs.

[0196] The integrated sensing and communication should be managed by the network. As it has been agreed in KI#3, the following issues should be addressed:

[0197] This key issue aims to study how to perform the Sensing entity(ies) and Sensing Function(s) discovery and (re-)selection, in particular:

[0198] - When required, for the discovery and (re-)selection of the Sensing entity(ies), the study needs to address the following aspects:

[0199] - Which entity(ies) performs the discovery and (re-)selection of the Sensing entity(ies);

[0200] - What the information and / or criteria are taken into account for the discovery and (re-)selection of the Sensing entity(ies); and

[0201] - The procedure(s) for the discovery and (re-)selection of the Sensing entity(ies).

[0202] - When required, for the discovery and (re-)selection of the Sensing Function(s), the study needs to address the following aspects:

[0203] - Which entity(ies) performs the discovery and (re-)selection of Sensing Function(s);

[0204] - What the information and / or criteria are taken into account for the discovery and (re-)selection of Sensing Function(s); and

[0205] - The procedure(s) for the discovery and (re-)selection of the Sensing Function(s).

[0206] The present disclosure considers and provides solutions to support sensing entity and sensing function registration, discovery, and selection.

[0207] The following description of examples of the present disclosure, with reference to the accompanying drawings, is provided to assist in a comprehensive understanding of certain examples of the present disclosure. The description includes various specific details to assist in that understanding but these are to be regarded as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the examples described herein can be made without departing from the scope of the invention or disclosure.

[0208] The same or similar components may be designated by the same or similar reference numerals, although they may be illustrated in different drawings.

[0209] Detailed descriptions of techniques, structures, constructions, functions or processes known in the art may be omitted for clarity and conciseness, and to avoid obscuring the subject matter of the present disclosure.

[0210] The terms and words used herein are not limited to the bibliographical or standard meanings, but are merely used to enable a clear and consistent understanding of the disclosure.

[0211] Throughout the description of this specification, the words "comprise", "include" and "contain" and variations of the words, for example "comprising" and "comprises", means "including but not limited to", and is not intended to (and does not) exclude other features, elements, components, integers, steps, processes, operations, functions, characteristics, properties and / or groups thereof.

[0212] Throughout the description of this specification, the singular form, for example "a", "an" and "the", encompasses the plural unless the context otherwise requires. For example, reference to "an object" includes reference to one or more of such objects.

[0213] Throughout the description, the expression "at least one of A, B and / or C" (or the like) and the expression "one or more of A, B and / or C" (or the like) should be seen to separately include all possible combinations, for example: A, B, C, A and B, A and C, A and B and C.

[0214] Throughout the description of this specification, language in the general form of "X for Y" (where Y is some action, process, operation, function, activity or step and X is some means for carrying out that action, process, operation, function, activity or step) encompasses means X adapted, configured or arranged specifically, but not necessarily exclusively, to do Y.

[0215] Features, elements, components, integers, steps, processes, operations, functions, characteristics, properties and / or groups thereof described or disclosed in conjunction with a particular aspect, embodiment or example are to be understood to be applicable to any other aspect, embodiment or example described herein unless incompatible therewith.

[0216] The following examples are applicable to, and use terminology associated with, 3GPP 4G (e.g., LTE) and / or 5G (e.g., NR). However, the skilled person will appreciate that the techniques disclosed herein are not limited to these examples or to 3GPP 4G (e.g., LTE) and / or 5G (e.g., NR), and may be applied in any suitable system or standard, for example one or more existing and / or future generation wireless communication systems or standards (e.g., B5G, 5G-Advanced, 6G etc.). The skilled person will appreciate that the techniques disclosed herein may be applied in any existing or future releases of 3GPP 4G (e.g., LTE) and / or 5G (e.g., NR) and / or 5G Advanced and / or 6G, and / or (3GPP Release 17, 18, 19, 20, etc.) or any other relevant standard. For example, the functionality of the various network entities and other features disclosed herein may be applied to corresponding or equivalent entities or features in other communication systems or standards. Corresponding or equivalent entities or features may be regarded as entities or features that perform the same or similar role, function, operation or purpose within the network.

[0217] Furthermore. the following also applies to the present disclosure:

[0218] The terms functionality / use-case / configuration / scenario / site may be used interchangeably.

[0219] The terms model and model functionality may be used interchangeably.

[0220] This disclosure also apply to non-3GPP entities.

[0221] The concepts, proposals, solutions, methods, embodiments, figures, and / or examples, presented in this disclosure, would apply to various type of communication systems, such as 4G, 4G-Advanced, 5G, 5G-Advanced, and 6G.

[0222] A particular network entity may be implemented as a network element on dedicated hardware, as a software instance running on a dedicated hardware, and / or as a virtualised function instantiated on an appropriate platform, e.g. on a cloud infrastructure.

[0223] The skilled person will appreciate that the present disclosure is not limited to the specific examples disclosed herein. For example:

[0224] The techniques disclosed herein are not limited to 3GPP 4G or 5G or 5G-Advanced and also apply to B5G and 6G systems.

[0225] One or more entities in the examples disclosed herein may be replaced with one or more alternative entities performing equivalent or corresponding functions, processes or operations.

[0226] One or more of the messages in the examples disclosed herein may be replaced with one or more alternative messages, signals or other type of information carriers that communicate equivalent or corresponding information.

[0227] One or more further elements, entities and / or messages may be added to the examples disclosed herein.

[0228] One or more non-essential elements, entities and / or messages may be omitted in certain examples.

[0229] The functions, processes or operations of a particular entity in one example may be divided between two or more separate entities in an alternative example.

[0230] The functions, processes or operations of two or more separate entities in one example may be performed by a single entity in an alternative example.

[0231] Information carried by a particular message in one example may be carried by two or more separate messages in an alternative example.

[0232] Information carried by two or more separate messages in one example may be carried by a single message in an alternative example.

[0233] The order in which operations are performed may be modified, if possible, in alternative examples.

[0234] The transmission of information between network entities is not limited to the specific form, type and / or order of messages described in relation to the examples disclosed herein.

[0235] In the description below the following terms are used:

[0236] Sensing Service Consumer: The entity that may consume the Sensing Result. The Sensing Service Consumer may also request the Sensing Result, trigger sensing process.

[0237] Sensing Entity: The Sensing Entity referring to a Sensing Transmitter or to a Sensing Receiver, e.g. UE, mobile phones, TRP / RAN node / gNB, UAV, RIS (Intelligent Reflecting Surface), vehicle, etc.

[0238] Sensing Function: Indicating the logical function which is involved to support Sensing Service. The Sensing Function cannot be a Sensing Entity.

[0239] Sensing Service: Capability to collect and provide information about object and / or characteristics of the environment using radio signals.

[0240] 3GPP sensing data: data derived from 3GPP radio signals impacted (e.g., reflected, refracted, diffracted) by an object or environment of interest for sensing purposes, and optionally processed within the 5G system.

[0241] Sensing result: processed 3GPP sensing data requested by a service consumer.

[0242] Sensing signals: Transmissions on the 3GPP radio interface that can be used for sensing purposes. The sensing signals could be the signals for sensing purposes only and / or the signals for sensing and / or communication between NW and UEs or between UEs and UEs (e.g. via sidelink).

[0243] 5G Wireless sensing: 5GS feature providing capabilities to get information about characteristics of the environment and / or objects within the environment (e.g., shape, size, orientation, speed, location, distances or relative motion between objects, etc.) using NR radio frequency signals, which, in some cases, can be extended by information created via previously specified functionalities in EPC and / or E-UTRAN.

[0244] non-3GPP sensing data: data provided by non-3GPP sensors (e.g., video, LiDAR, sonar) about an object or environment of interest for sensing purposes.

[0245] Sensing assistance information: information that is provided to the 5G system from a trusted third-party and can be used to support the derivation of a sensing result. This information does not contain 3GPP sensing data.

[0246] Sensing contextual information: information that is exposed with the sensing results by 5G or future (e.g. 6G) system to a trusted third-party which provides context to the conditions under which the sensing results were derived, e.g. the associated time (window), sensing operation / mode / type, sensing algorithm related information, matric / information related to sensing performance evaluation, involved sensing entities, etc. This information does not contain 3GPP sensing data.

[0247] Sensing group: a set of sensing transmitters and sensing receivers whose location is known and whose sensing data can be collected synchronously.

[0248] Sensing transmitter: a sensing transmitter is the entity that sends out the sensing signal which the sensing service will use in its operation. A Sensing transmitter is part of a RAN node or a UE. A Sensing transmitter can be located in the same or different entity as the Sensing receiver.

[0249] Sensing receiver: a sensing receiver is an entity that receives the sensing signal which the sensing service will use in its operation. A sensing receiver is part of a RAN node or a UE. A Sensing receiver can be located in the same or different entity as the Sensing transmitter.

[0250] Sensing Transmitter and Sensing Receiver: could be any combination of UE, TRP / gNB, e.g. UE-UE, TRP-TRP, TRP-UE, etc.

[0251] Target sensing service area: a cartesian location area that needs to be sensed by deriving characteristics of the environment and / or objects within the environment with certain sensing service quality from the impacted (e.g., reflected, refracted, diffracted) 3GPP radio signals. This includes both indoor and outdoor environments.

[0252] ISAC network topologies:

[0253] Device-free sensing: that the sensing targets (e.g., a bird) are not capable of transmitting and / or receiving the sensing signal, or means that the sensing procedure does not rely on the transmitting and / or receiving of the sensing target (e.g., a target vehicle).

[0254] Device-based sensing: the sensing targets are capable of transmitting and / or receiving the sensing signal, and the sensing procedure relies on the transmitting and / or receiving of the sensing target. A typical example is the wireless-based localization to localize mobile devices.

[0255] In the present disclosure both device-free and device-based sensing is considered, e.g. the sensing object may be an object that can or cannot transmit or receive (radio) signals.

[0256] 5GC Network Function for Sensing

[0257] The present disclosure introduces sensing related functionalities within the core network. The sensing related functionalities will be supported by sensing related core / 5GC NF(s). The sensing related core / 5GC NF may be a new NF, e.g. sensing function (SF); or the enhancement to existing 5GC NF, e.g. NEF, PCF, SMF, NWDAF, LMF, etc. Based on operator's policies and deployment, the sensing related core NF may be standalone core NF, or co-location with other 5GC NFs (e.g. NEF, PCF, SMF, NWDAF, etc.). Consequently, although certain network entities may be referred to in the description below as providing new functionality, it is not only limited to those certain entities providing such functionality.

[0258] The sensing related functionalities / NF support one or more of the following:

[0259] * Authorization and Revocation of sensing services (request), sensing entities, sensing scenario / operation (e.g. UE-based or gNB / TRP / NW-based sensing, monostatic / bistatics / Multistatic sensing, etc.).

[0260] * Provide configuration parameter / policies / user consent data / user privacy data of / to sensing entities, e.g. by provisioning.

[0261] * Sensing entity and / or sensing function discovery and / or (re-)selection

[0262] * Sensing data and associated information collection and transport, e.g. trigger the sensing data and information collection, determine the method / path of sensing data and information transfer / transport (e.g. data transfer via CP, UP, LPP or other data path), provide the configuration of the signals related to sensing (e.g. radio signals specific for sensing services / purpose and / or the signal for general communication but can be used for sensing services / purpose), etc.

[0263] * Determine / calculate sensing results, and / or determine the methods / algorithms for calculating sensing results.

[0264] * Sensing results exposure to the consumer. Exposing the required / authorized sensing related data, sensing results, or sensing contextual information. The consumer may be (trusted and / or untrusted) 3rdparty / AF, any 5GC NFs, OAM, RAN node, UE, etc. The exposure and report may be request-based / one shot, periodic, event triggered (e.g. when the target object / movement is detected), etc.

[0265] Sensing Related Information and Sensing Entity Registration

[0266] Figure 3 provides an example procedure for the registration of sensing related information and / or sensing entities in accordance with the present disclosure. The procedure of Figure 3 is not only limited to the steps shown therein, and steps may be omitted, introduced, and / or reordered in order to provide equivalent, reduced, or further functionality. The steps of Figure 3 are described below.

[0267] 1a. Sensing entity registers their sensing related (capability) information to the RAN node, and core network functions, (e.g. AMF, UDM, SF, PCF, NRF, etc.), using the registration procedures defined in TS 23.502. The AMF, UDM and other relevant core network functions store the sensing related (capability) information of the UE(s).

[0268] 1b. One or more RAN node may indicate their capability information related to sensing to the core network. The sensing related information of the RAN node may also be pre-configured to the core network (e.g. NRF, AMF, PCF, UDM, SF, etc.); therefore, the core network has the prior knowledge of the sensing capability of the RAN node.

[0269] * If the RAN node indicates the sensing related information that is different from the pre-configured information, the information indicated by the RAN node may override the previous configured information.

[0270] * The RAN node may indicate the sensing related information during N2 / NGAP interface (the interface / tunnel between RAN node and core network) establishment / modification. The sensing related information may be at per RAN node / gNB, per cell, per CU, per DU granularity.

[0271] A UE or RAN node may support sensing services and / or register / indicate one or more of the sensing related (capability) information to the network:

[0272] * The (different) sensing mode / operations could be supported, e.g. network-based and / or UE-based sensing; monostatic sensing, bi-static sensing, Multistatic sensing; device-based, device-free sensing; etc.

[0273] * The capabilities of determine / calculate sensing results, and / or the supporting methods / algorithms for calculating sensing results.

[0274] * Act as a sensing (signal / data) receiver and / or sensing (signal / data) transmitter

[0275] * Measure radio signal, e.g. for sensing purposes and / or regular communication purposes

[0276] * Generate and / or transmit signals, e.g. for sensing purposes. This may be based on request from the network (e.g. RAN node or SF) or sensing consumer

[0277] * Generate and / or transmit which types signals, and / or measure which types of radio signal, e.g. CSI-RC, DL / UL reference signals, broadcast signal, unicast signal, etc.

[0278] * Report sensing results, sensing data, sensing contextual information or other assistance information related to sensing environment, radio signal, errors etc., e.g. to RAN node, sensing related function in core network, 3rdparty (e.g. AF / AS). This may be based on request from the network (e.g. RAN node or SF) or sensing consumer.

[0279] * Able to configure the radio signals for sensing services / purposes, e.g. a RAN node may be able to do this.

[0280] * Types of supporting sensing service, e.g. detection of certain types of objects (e.g. humans, animals, vehicles, UAVs, buildings, etc.), certain types of detections (e.g. detection of moving / non-stationary objects, shape (variation) of objects, etc.).

[0281] * capability to require the network to transmit sensing related signals for measurement, e.g. whether the sensing entity (e.g. UE) is capable or allowed to require RAN node / 5GC NF / SF to transmit sensing signal or not.

[0282] 1c. The SF (sensing function) may register itself to NRF and other NFs if necessary, e.g. by invoking Nnrf_NFManagement_NFRegister. The SF may register its NF profile to the NRF. The SF registration information may include:

[0283] * Sensing service management related information can be supported by this SF

[0284] * SF location information, IP information, address information, ID information

[0285] * SF sensing capability information

[0286] * The time window that this SF can support sensing services

[0287] * The list of sensing entities (e.g. UEs / SUPIs / GPSIs, RAN node) that can be supported by this SF (e.g. for sensing services, different types of sensing operations) different sensing operations may be UE-based and / or nw-based sensing.)

[0288] * SF support the sensing operations / service per type (e.g. UE-based, nw-based sensing, device-based, device-free sensing, etc.)

[0289] * The RAT and / or access type and / or radio interface-type information of the supported sensing services (e.g. LTE, 5G, 6G, non-3GPP, 3GPP, etc.)

[0290] * Supported sensing results determination methods / algorithms

[0291] * Types of supported sensing service, e.g. detection of certain types of objects (e.g. humans, animals, vehicles, UAVs, buildings, etc.), certain types of detections (e.g. detection of moving / non-stationary objects, shape (variation) of objects, etc.).

[0292] 1d. The OAM may also be aware of the sensing related information of sensing entity, a RAN node / gNB, a cell, a CU, a DU, UE, UAV, AGV, etc. e.g. the RAN node may inform the OAM of the sensing capability information of RAN node / gNB, a cell, a CU, a DU, UE; the OAM may also receive the sensing capability information, e.g. by pre-configuration by the operators; the core NF (e.g. NRF, SF, etc.) may inform OAM of the sensing related information of RAN node / gNB, a cell, a CU, a DU, UE;.

[0293] 2. The entities that receive the sensing related registration / indication information (e.g. from the UE, RAN node, CU, DU, SF, etc.) may store the information for future use, e.g. for sensing service / entity discovery and / or selection, etc.

[0294] 3. The entities that receive the sensing related registration / indication information send responses to the registration UE / RAN node / SF etc., in step 3a, 3b, 3c. The response may indicate the information registration is accepted and / or rejected.

[0295] Sensing Function Discovery

[0296] Figure 4 provides an example procedure for sensing function discovery in accordance with the present disclosure. The procedure of Figure 4 is not only limited to the steps shown therein, and steps may be omitted, introduced, and / or reordered in order to provide equivalent, reduced, or further functionality. The steps of Figure 4 are described below.

[0297] In the procedure of Figure 4 described below, the consumer of the sensing function discovery may be the sensing service consumer or other core NF (e.g. AMF, PCF, NEF, etc.)

[0298] 1. The sensing function discovery consumer may trigger the sensing function / functionality discovery, towards / within the core network, e.g. sends the discovery request to NRF.

[0299] The sensing discovery consumer may be a 3rdparty, AF, AS, or core NF, OAM, Ran node or UE.

[0300] The sensing function discovery may be triggered by the sensing service consumer, e.g. if the sensing service consumer is different from the sensing function discovery consumer; or triggered based on the internal logic of the sensing discovery consumer, e.g. the sensing service consumer is the same as the sensing function discovery consumer.

[0301] The consumer may include one or more of the following information in the sensing function / functionality discovery request:

[0302] * The required NF functionality or NF type, e.g. the NF that support sensing services related functionalities or SF.

[0303] * The required / referred / expected sensing mode / operations, e.g. network-based and / or UE-based sensing, device-based, device-free, etc.

[0304] * The required / referred / expected method to methods / algorithms for calculating sensing results, e.g. AI based algorithms or other methods; or the types of radio signals that can be supported for sensing purposes.

[0305] * Area of interests of the corresponding discovery request or sensing services

[0306] * Required / referred / expected sensing location of the sensing function

[0307] * Time window for the potential sensing services

[0308] * Required / referred / expected available time of the sensing function(s), e.g. for sensing signal measurement / transmission / reception, for providing sensing results, etc.

[0309] * The required / referred / expected supporting types sensing service, e.g. detection of certain types of objects (e.g. humans, animals, vehicles, UAVs, buildings, etc.), certain types of detections (e.g. detection of moving / non-stationary objects, shape (variation) of objects, etc.).

[0310] * Candidate list of sensing entities to be supported by the SF, for the potential sensing services. e.g. the (ID / name / address) list of receivers or transmitters of the sensing signals, the SUPIs or GPSIs of UEs, the NF (set / instance) IDs / IP addresses of SFs, the name / ID / tunnel address of RAN node, cell ID, beam ID, TRP ID, sensing group ID (e.g. an group of one or more sensing entities), etc.

[0311] * The required / referred / expected accuracy / confidence level / trustworthiness of sensing results, sensing data (measurements)

[0312] * The required / referred / expected access Type (3GPP / non-3GPP) and RAT type (e.g. LTE, NR, 6G and other rat types).

[0313] * The required / referred / expected capability / (work) load / availability of SF or the potential sensing services.

[0314] 2. The NRF authorizes the Discovery Request.

[0315] Based on the profile of the expected NF / NF service and the type of the NF service consumer, the NRF determines whether the NF service consumer is allowed to discover the expected NF instance(s) / set / (sensing) group.

[0316] Based on information in the sensing function discover request, the core NF (e.g. NRF) determines the SF(s) that can fulfill the information in the request.

[0317] The core NF (e.g. NRF) may also return the SF(s) that cannot fulfill all required information in the discovery request, but can meet some of that. The core NF (e.g. NRF) may also include the NF profile and other sensing related information can be supported by those SF(s) in the discovery response.

[0318] 3. If allowed, the NRF determines a set of NF instance(s) matching discovery request and internal policies of the NRF and sends the NF profile(s) of the determined NF instances. For the scenario when NF instance(s) reside in a target PLMN, the NRF in HPLMN may further query a NRF in that target PLMN. Each NF profile containing at least the output required parameters to the NF service consumer via Discovery Response message.

[0319] 4. The core NF (e.g. NRF) returns the discovery results based on the information it determine in step 2 and step 3 to the consumer of the discovery service.

[0320] If the consumer of the sensing discovery service is not the sensing service consumer, the discovery results may be sent to the sensing service consumer from the consumer of the sensing discovery service for further actions, e.g. SF selection for the potential / required sensing service.

[0321] Sensing Entity Discovery and (Re-)Selection

[0322] Figure 5 provides an example procedure for sensing entity discover and (re-) selection in accordance with the present disclosure. The procedure of Figure 5 is not only limited to the steps shown therein, and steps may be omitted, introduced, and / or reordered in order to provide equivalent, reduced, or further functionality. The steps of Figure 5 are described below.

[0323] The sensing entities that are to be involved in the sensing service should be discovered and / or selected, e.g. by SF or the sensing service consumer.

[0324] 1. [Optional] The sensing service consumer triggers a sensing service towards the core network, e.g. SF, other sensing related NF, NEF or PCF, etc. If the sensing service consumer is an untrusted AF, the request may be sent via NEF.

[0325] 2. The SF, other sensing related NF, NEF or PCF triggers sensing entity discovery, to discover the sensing entities that are available / allowed to join the sensing service(s). The sensing service may be a future or ongoing service.

[0326] The sensing entity discovery may be triggered due to the request from a sensing service consumer, the internal logic of the sensing related NF, operator configuration, sensing related event, etc.

[0327] The SF, other sensing related NF, NEF or PCF that triggers sensing entity discover determines the sensing method / operation / mode and / or sensing topology. The detailed required information included in the sensing entity discovery request may be determined based on the sensing method / operation / mode and / or sensing topology.

[0328] The SF, other sensing related NF, NEF or PCF that triggers sensing entity discovery may include one or more of the following information in the sensing entity discovery request:

[0329] * The sensing entity type, e.g. the NF that support sensing services related functionalities, UE, RAN node, UAV, vehicle, etc.

[0330] * The required sensing entity type, e.g. sensing transmitter and / or sensing receiver; stationary or nonstationary devices, etc.

[0331] * The required / referred / expected sensing mode / operations, e.g. network-based and / or UE-based sensing; device-based, device-free sensing; monostatic sensing, bi-static sensing, Multistatic sensing, etc.

[0332] * The required / referred / expected method to methods / algorithms for calculating sensing results, e.g. AI based algorithms or other methods; or the types of radio signals that can be supported for sensing purposes.

[0333] ** This may be applicable for UE-based sensing operation.

[0334] * Area of interests of the corresponding discovery request or sensing services

[0335] * Required / referred / expected sensing location of the sensing entities

[0336] * Time window for the potential sensing services

[0337] * Required / referred / expected available time of the sensing function(s), e.g. for sensing signal measurement / transmission / reception, for providing sensing results, etc.

[0338] * The required / referred / expected supporting types sensing service, e.g. detection of certain type of objects (e.g. humans, animals, vehicles, UAVs, buildings, etc.), certain types of detections (e.g. detection of moving / non-stationary objects, shape (variation) of objects, etc.).

[0339] * Candidate list of sensing entities, E.g. the (ID / name / address) list of receivers or transmitters of the sensing signals / data, the SUPIs or GPSIs of UEs, the NF (set / instance) IDs / IP addresses of SFs, the name / ID / tunnel address of RAN node, cell ID, beam ID, TRP ID, sensing group ID (e.g. an group of one or more sensing entities), etc.

[0340] * The required / referred / expected accuracy / confidence level / trustworthiness of sensing results, sensing data (measurements)

[0341] * The required / referred / expected access Type (3GPP / non-3GPP) and RAT type (e.g. LTE, NR, 6G and other rat types).

[0342] * The required / referred / expected capability / (work) load / availability of sensing entities.

[0343] The sensing entity discovery may be triggered towards UDM, e.g. to discover the UEs to join the sensing services; towards OAM or AMF, e.g. to discover RAN node / gNB to join the sensing services; towards NRF, e.g. to discover other SFs or core NF that supports sensing related capabilities to join the sensing services.

[0344] 3. Upon receiving the sensing entity discovery request, the UDM / OAM / AMF / NRF authorize the sensing entity discovery service request, if needed. The core NFs or OAM determine the discovery results based on the information in the discovery request.

[0345] 4. The core NFs or OAM in step 3 send the discovery results back to the discovery service consumer in step 2.

[0346] 5. If the discovery service consumer is SF or the NF that is responsible for determining the sensing entities, it determines the sensing entities to join the sensing service, e.g. based on the information in the discovery response, the required information in the sensing service consumer request, operator's policy and regulation, user consent and privacy of UEs (e.g. sensing entities / transmitter / receivers), etc.

[0347] If the discovery service consumer is not SF or the NF that is responsible for determine the sensing entities, it forwards the discovery results to the SF or the NF that is responsible for determine the sensing entities. Then the SF or the NF that is responsible for determining the sensing entities determine the sensing entities, the same as the above paragraph.

[0348] 6. The SF or the NF that is responsible for determining the sensing entities may send the decision of sensing entities to the corresponding selected entities, e.g. after sensing entity discovery, or together with the sensing service request that triggers sensing service operation.

[0349] Therefore, the selected entities are able to prepare for the sensing services.

[0350] This step may happen together with sensing service trigger / request or sensing information configuration stage.

[0351] 7. The sensing entities may response to the SF, by indicate whether they accept or not accept the sensing request / to act as sensing entities. If the sensing entity does not accept the request, it may include the cause value (e.g. due to load, available time for sensing, mobility, etc.) in the response / notify.

[0352] 8. The SF may perform sensing entity re-selection, e.g. based on the response from the sensing entities in step 7. One or more of Step 2 - 6 may be repeated for sensing entity re-selection / refinement.

[0353] Sensing Entity and / or Sensing Function Re-Selection

[0354] The sensing service consumer and / or the sensing network function may determine to re-select the sensing function(s) and / or the sensing entities, e.g. during the sensing service operation or before the sensing service was triggered.

[0355] The re-selection may occur due to one or more of: the sensing function(s) and / or sensing entities are not available, capacity / load of the sensing function(s) and / or sensing entities, privacy information or (user) consent information related to sensing is updated / revoked, accuracy / error of sensing results / sensing data measurement / sensing data transmission, delay of sensing data / signal transmission, delay of sensing results (reporting), etc.

[0356] The re-selection procedure may be the same as the procedures in Figure 4 and Figure 5.

[0357] Authorization and Revocation to Support Sensing Service

[0358] For the purpose of communication network management and to protect the communication security, the devices / entities to be involved into sensing service operation / process may need to be authorized / authenticated by the network.

[0359] Even after the sensing services / entities are authorized / authenticated, the network may revoke / update the authorization / authentication. In this case, unauthorized / unauthenticated sensing entities should be removed from the sensing service operation, new sensing entities may be discovered and / or selected to replace the removed sensing entities; the sensing service may be revoked / suspended / terminated.

[0360] Authorization may be network-based (e.g. PCF-based or SF-based, etc.). If the sensing entity indicates its sensing Capability information in the Registration Request message, and / or if the sensing entity is authorized to join the sensing service (e.g. based on subscription / SLA data), the corresponding policies (e.g. UE / session management / sensing policy) related to sensing. The policies may be related to the service flows of sensing services and / or the sensing entities.

[0361] The SF and PCF may interact with each other to determine the parameters related to (sensing) policies for the sensing entities.

[0362] A sensing entity may be authorized / revoked (e.g. by the network, PCF, SF, AMF, etc.) to do one or more of the following:

[0363] * Join / leave a sensing service, e.g. NW-based or UE- based sensing services; monostatic sensing, bi-static sensing, Multistatic sensing; device-based, device-free sensing; etc.

[0364] * Join / leave sensing service(s) in specific areas / location, or for specific sensing objects, sensing detection type (e.g. moving object), etc.

[0365] * Perform as sensing transmitter and / or receiver

[0366] * Transfer sensing data, e.g. to other sensing entities, RAN node, sensing functions, etc.

[0367] A sensing service consumer may be authorized / revoked to request / consume sensing service, e.g. by the network, PCF, SF, AMF, etc.

[0368] * The sensing service consumer may contact PCF (e.g. via NEF) to check whether it is authorized to request / consume sensing service.

[0369] * The sensing service consumer may send a service request to SF (e.g. via NEF), then the SF contacts PCF to check whether the consumer is authorized to request / consume sensing service.

[0370] * When the consumer's authorization of sensing service is revoked, the PCF may notice the SF and / or the consumer. Then the corresponding sensing service (e.g. the sensing service required by the consumer) may be terminated, or the sensing related information (e.g. sensing result / data / contextual information) will not be exposed to this consumer.

[0371] According to an embodiment, a method for sensing function (SF) discovery and selection in a mobile communications network may be provided.

[0372] According to an embodiment, the method may include transmitting, from a sensing service consumer to a network repository function (NRF),a discovery request corresponding to a sensing service.

[0373] According to an embodiment, the method may include determining, by the NRF, one or more sensing functions (SF) based on the discovery request.

[0374] According to an embodiment, the method may include transmitting, from the NRF to the sensing service consumer, an indication of the one or more SFs.

[0375] According to an embodiment, the method may include selecting, by the sensing service consumer, a SF from the one or more SFs to provide the sensing service.

[0376] According to an embodiment, the discovery request includes information on network function type and a sensing service area, and the one or more SFs are SFs that match the information of the discovery request, wherein the network function type is a network function that supports the sensing service.

[0377] According to an embodiment, the discovery request is transmitted to the NRF from the sensing service consumer via a network exposure function (NEF) and the indication of the one or more SFs is transmitted from the NRF to the sensing service consumer via the NEF.

[0378] According to an embodiment, the method may include transmitting, from each of the one or more SFs to the NRF, a registration request including a network function (NF) profile of the respective SF.

[0379] According to an embodiment, the method may include registering, by the NRF, the NF profiles of the one or more SFs.

[0380] According to an embodiment, the method may include transmitting, from the NRF to each of the SFs, a respective registration response.

[0381] According to an embodiment, the NF profile of a SF includes information on a type of sensing supported by the SF and / or SF location information.

[0382] According to an embodiment, a type of sensing includes one or more of user equipment (UE)-based, network-based, device-based, device-free, object detection, object movement detection, and detection of certain types of object.

[0383] According to an embodiment, the method may include transmitting, from the sensing service consumer to the SF, a sensing service request.

[0384] According to an embodiment, the method may include selecting, by the SF, one or more sensing entities from a plurality of sensing entities based on the sensing service request for the sensing service.

[0385] According to an embodiment, the method may include transmitting, from the SF to a NF, in response to the sensing service request, a request for sensing entity information.

[0386] According to an embodiment, the method may include transmitting, from the NF to the SF, information on the plurality of sensing entities.

[0387] According to an embodiment, the request for sensing entity information includes an area of interest and / or a list of sensing entities, and the plurality of sensing entities are sensing entities included in the area of interest and / or the list of sensing entities.

[0388] According to an embodiment, the method may include determining, by the NF, the plurality of sensing entities based on the area of interest and the list of sensing entities.

[0389] According to an embodiment, the NF transmits to the SF, information on the sensing entities included in the list.

[0390] According to an embodiment, the NF is an access and mobility management function (AMF), or an Operations, Administration, and Maintenance (OAM) entity.

[0391] According to an embodiment, the selecting, by the SF, is based on an area of interest included in the sensing service request and / or the plurality of sensing entities includes one or more of a user equipment (UE) and a gNB.

[0392] According to an embodiment, the method may include reselecting one or more sensing entities based on the sensing service request for an ongoing sensing service corresponding to the sensing service request and / or transmitting, from the SF to the selected one or more sensing entities, a notification of selection for a sensing service.

[0393] According to an embodiment, the method may include transmitting, from each of the plurality of sensing entities to the NF, a registration request including sensing-related information of the respective sensing entity,

[0394] According to an embodiment, the information on the plurality of sensing entities includes the sensing-related information.

[0395] According to an embodiment, the sensing-related information includes capability information of the respective sensing entity and / or each of the plurality of sensing entities is authorised by the network to perform as a sensing transmitter and / or a sensing receiver.

[0396] According to an embodiment, the method may include transmitting, from the NF to the plurality of sensing entities, a registration response in response to the registration request.

[0397] According to an embodiment, the method may include authorising, by the SF, the sensing service consumer to request a sensing service.

[0398] According to an embodiment, a mobile communications network comprising a sensing function (NF), a network repository function (NRF), a network function, and access and mobility management function (AMF), an Operations, Administration, and Maintenance (OAM) entity, and a plurality of sensing entities may be provided, where the mobile communications network is configured to implement the method.

[0399] According to an embodiment, a method of a sensing function (SF) for use in a mobile communications network may be provided.

[0400] According to an embodiment, the method may include transmitting, from the SF to an network repository function (NRF), a registration request including a network function (NF) profile of the SF;

[0401] According to an embodiment, the method may include receiving, at the SF from the NRF, a registration response.

[0402] According to an embodiment, the method may include receiving, from a sensing service consumer, a sensing service request.

[0403] According to an embodiment, the method may include selecting, by the SF, one or more sensing entities from a plurality of sensing entities based on the sensing service request for the sensing service.

[0404] According to an embodiment, a sensing function (SF) for use in a mobile communications network may be provided, wherein the SF is configured to implement the method.

[0405] According to an embodiment, a method of a sensing entity for use in a mobile communications network may be provided.

[0406] According to an embodiment, the method may include transmitting, to a network function (NF), a registration request including sensing-related information of the sensing entity.

[0407] According to an embodiment, the method may include receiving, from a sensing function (SF), a notification of selection of the sensing entity for a sensing service.

[0408] According to an embodiment, the method may include transmitting, from the sensing entity to the SF, a response accepting the selection.

[0409] According to an embodiment, a sensing entity for use in a mobile communications network may be provided, wherein the sensing entity is configured to implement the method.

[0410] According to an embodiment, a method of a network repository function (NRF) for use in a mobile communications network may be provided.

[0411] According to an embodiment, the method may include receiving, from each of one or more sensing functions (SFs), a registration request including a network function (NF) profile of the respective SF.

[0412] According to an embodiment, the method may include registering the NF profiles of the one or more SFs.

[0413] According to an embodiment, the method may include receiving, from a sensing service consumer, a discovery request corresponding to a sensing service.

[0414] According to an embodiment, the method may include determining one or more SFs based on the discovery request and the registered NF profiles.

[0415] According to an embodiment, the method may include transmitting, to the sensing service consumer, an indication of the determined one or more SFs.

[0416] According to an embodiment, a network repository function (NRF) for use in a mobile communications network may be provided, wherein the NRF is configured to implement the method.

[0417] Although the procedures described herein have been described separately, they and any of their constituent steps may also be combined and functionality of each introduced into one another unless incompatible.

[0418] Certain examples of the present disclosure may be provided in the form of an apparatus / device / network entity configured to perform one or more defined network functions and / or a method therefor. Such an apparatus / device / network entity may comprise one or more elements, for example one or more of receivers, transmitters, transceivers, processors, controllers, modules, units, and the like, each element configured to perform one or more corresponding processes, operations and / or method steps for implementing the techniques described herein. For example, an operation / function of X may be performed by a module configured to perform X (or an X-module). Certain examples of the present disclosure may be provided in the form of a system (e.g., a network) comprising one or more such apparatuses / devices / network entities, and / or a method therefor.

[0419] It will be appreciated that examples of the present disclosure may be realized in the form of hardware, software or a combination of hardware and software. Certain examples of the present disclosure may provide a computer program comprising instructions or code which, when executed, implement a method, system and / or apparatus in accordance with any aspect, example and / or embodiment disclosed herein. Certain embodiments of the present disclosure provide a machine-readable storage storing such a program.

[0420] Figure 6 is a block diagram of an exemplary network entity / function that may be used in examples of the present disclosure, such as the techniques disclosed in relation to any of the preceding figures. For example, any of the network entities, network function etc. (e.g. UE, BS, gNB / eNB, ATG entities, NTN nodes, etc.) may be provided in the form of the network entity illustrated in Figure 6. The skilled person will appreciate that a network entity / function may be implemented, for example, as a network element on a dedicated hardware, as a software instance running on a dedicated hardware, and / or as a virtualised function instantiated on an appropriate platform, e.g. on a cloud infrastructure.

[0421] The entity 600 comprises a processor (or controller) 601, a transmitter 603 and a receiver 605. The receiver 605 is configured for receiving one or more messages from one or more other network entities, for example as described above. The transmitter 603 is configured for transmitting one or more messages to one or more other network entities, for example as described above. The processor 601 is configured for performing one or more operations, for example according to the operations as described above.

[0422] It will be appreciated that, in each example / embodiment / aspect etc. described above, one or more features or operations may be omitted, modified or moved (e.g., to change the order of the features or the operations), if desired and appropriate.

[0423] Additionally, where the figures illustrating example method flows include text in relation to a specific step / operation, it will be appreciated that this text is simply an example of the corresponding step / operation, where a more general definition (such as may be found in the description of the corresponding step) may apply for the step / operation.

[0424] Additionally, regarding all of the above, one or more features or operations etc. from any example / embodiment may be combined with features or operations from any other example / embodiment. That is, the present disclosure should be considered to include all combinations of examples / embodiments disclosed herein, as appropriate, as well as combinations of individual features within and between each example / embodiment, as appropriate.

[0425] The techniques described herein may be implemented using any suitably configured apparatus and / or system. Such an apparatus and / or system may be configured to perform a method according to any aspect, embodiment or example disclosed herein. Such an apparatus may comprise one or more elements, for example one or more of receivers, transmitters, transceivers, processors, controllers, modules, units, and the like, each element configured to perform one or more corresponding processes, operations and / or method steps for implementing the techniques described herein. For example, an operation / function of X may be performed by a module configured to perform X (or an X-module). The one or more elements may be implemented in the form of hardware, software, or any combination of hardware and software.

[0426] It will be appreciated that examples of the present disclosure may be implemented in the form of hardware, software or any combination of hardware and software. Any such software may be stored in the form of volatile or non-volatile storage, for example a storage device like a ROM, whether erasable or rewritable or not, or in the form of memory such as, for example, RAM, memory chips, device or integrated circuits or on an optically or magnetically readable medium such as, for example, a CD, DVD, magnetic disk or magnetic tape or the like.

[0427] It will be appreciated that the storage devices and storage media are embodiments of machine-readable storage that are suitable for storing a program or programs comprising instructions that, when executed, implement certain examples of the present disclosure. Accordingly, certain examples provide a program comprising code for implementing a method, apparatus or system according to any example, embodiment and / or aspect disclosed herein, and / or a machine-readable storage storing such a program. Still further, such programs may be conveyed electronically via any medium, for example a communication signal carried over a wired or wireless connection.

[0428] While the disclosure has been shown and described with reference to certain examples, it will be understood by those skilled in the art that various changes in form and detail may be made therein without departing from the scope of the disclosure.

[0429] The reader's attention is directed to all papers and documents which are filed concurrently with or previous to this specification in connection with this application and which are open to public inspection with this specification, and the contents of all such papers and documents are incorporated herein by reference.

[0430]

[0431] Acronyms and Definitions

[0432] 3GPP 3rdGeneration Partnership Project

[0433] 5G 5thGeneration

[0434] 5GC 5G Core

[0435] 5QI 5G QoS Identifier

[0436] 5GS 5G System

[0437] 5GSM 5G System Session Management

[0438] 5GMM 5G System Mobility Management

[0439] AF Application Function

[0440] AI Artificial Intelligence

[0441] AM Acknowledged Mode

[0442] AMF Access and Mobility Management Function

[0443] AS Access Stratum

[0444] ASP Application Service Provider

[0445] ATG Air-To-Ground

[0446] AUSF Authentication Server Function

[0447] CDN Content Delivery Network

[0448] CU Central Unit

[0449] DCAF Data Collection Application Function

[0450] DNAI Data Network Access Identifier

[0451] DNN Data Network Name

[0452] DNS Domain Name Server

[0453] DRB Data Radio Bearer

[0454] DU Distributed Unit

[0455] EDT Early Data Transmission

[0456] eMTC Enhanced Machine-Type Communications

[0457] eNB Evolved Node B

[0458] EPC Evolved Packet Core

[0459] E-UTRAN Evolved Universal Terrestrial Radio Access Network

[0460] FEC Forward Error Correction

[0461] FQDN Fully Qualified Domain Name

[0462] GBR Guaranteed Bit Rate

[0463] gNB Next generation Node B

[0464] GPSI Generic Public Subscription Identifier

[0465] HSS Home Subscriber Service

[0466] IAB Integrated Access and Backhaul

[0467] ID Identity / Identifier

[0468] IIoT Industrial Internet of Things

[0469] IMEI International Mobile Equipment Identities

[0470] IP Internet Protocol

[0471] I-SMF Intermediate SMF

[0472] LADN Local Area Data Network

[0473] LL SSM Lower Layer SSM

[0474] LTE Long Term Evolution

[0475] LTE-M LTE Machine-Type Communication

[0476] MBMS Multimedia Broadcast / Multicast Service

[0477] MBS Multicast / Broadcast Service

[0478] MBSF Multicast / Broadcast Service Function

[0479] MBSTF Multicast / Broadcast Service Transport Function

[0480] MB-SMF Multicast / Broadcast Session Management Function

[0481] MB-UPF Multicast / Broadcast User Plane Function

[0482] MTC Machine-Type Communication

[0483] MCCH Multicast Control Channel

[0484] MTCH Multicast Traffic Channel

[0485] ML Machine Learning

[0486] MME Mobility Management Entity

[0487] MN Master Node

[0488] MNF Monitoring Network Function

[0489] MNO Mobile Network Operator

[0490] MPDCCH MTC Physical Downlink Control Channel

[0491] MT Mobile Termination

[0492] NAS Non-Access Stratum

[0493] NR-IoT Narrowband Internet of Things

[0494] NEF Network Exposure Function

[0495] NRF Network Repository Function

[0496] NG-RAN Next Generation Radio Access Network

[0497] NG-eNB Next Generation eNB

[0498] NGAP Next Generation Application Protocol

[0499] NR New Radio

[0500] NSA Non-Standalone

[0501] NSSF Network Slice Selection Function

[0502] NTN Non-Terrestrial Networks

[0503] NW Network

[0504] NWDAF Network Data Analytics Function

[0505] OS Operating System

[0506] OSAPP OS Application

[0507] PCF Policy Control Function

[0508] PCO Protocol Configuration Options

[0509] PDR Packet Detection Rule

[0510] PDU Protocol Data Unit

[0511] PLMN Public Land Mobile Network

[0512] PTM Point To Multipoint

[0513] PTP Point to Point

[0514] PDSCH Physical Downlink Shared Channel

[0515] PUCCH Physical Uplink Control Channel

[0516] PUSCH Physical Uplink Shared Channel

[0517] PUR Preconfigured Uplink Resources

[0518] QFI QoS Flow Identifier (ID)

[0519] QoS Quality of Service

[0520] RACH Random Access Channel

[0521] RAN Radio Access Network

[0522] RRC Radio Resource Control

[0523] RSD Route Selection Descriptor

[0524] SA Standalone

[0525] SDAP Service Data Adaptation Protocol

[0526] SDU Service Data Unit

[0527] SGW Serving Gateway

[0528] SIM Subscriber Identity Module

[0529] SLA Service Level Agreement

[0530] SM Session Management

[0531] SMF Session Management Function

[0532] SN Secondary Node

[0533] S-NSSAI Single Network Slice Selection Assistance Information

[0534] SSB Synchronization Signal Block

[0535] SSM Source Specific IP Multicast address

[0536] SSC Session and Service Continuity

[0537] SRB Signaling Radio Bearer

[0538] SUPI Subscription Permanent Identifier

[0539] TA Tracking Area

[0540] TAI Tracking Area Identity

[0541] TE Terminal Equipment

[0542] TM Transparent Mode

[0543] TMGI Temporary Mobile Group Identity

[0544] TS Technical Specification

[0545] UAV Unmanned Aerial Vehicle

[0546] UDM Unified Data Manager

[0547] UDR Unified Data Repository

[0548] UE User Equipment

[0549] UL Uplink

[0550] UM Unacknowledged Mode

[0551] UP User Plane

[0552] UPF User Plane Function

[0553] URLLC Ultra-Reliable and Low-Latency Communication

[0554] URSP UE Route Selection Policy

Claims

1.A method performed by network function (NF) in a communication system, the method comprising:receiving, from a sensing service consumer, a sensing service request;transmitting, to access and mobility management function (AMF), a request message for information on at least one sensing entity in a target area after reception of the sensing service request;receiving, from the AMF, the information on the at least one sensing entity in the target area ; andselecting at least one sensing entity to join a sensing service based on the information on the at least one sensing entity.2.The method of claim 1,wherein the information on the at least one sensing entity corresponds to at least one identifier (ID) of the at least one sensing entity.3.The method of claim 1, further comprising:registering a profile of the NF to network repository function (NRF),wherein the profile includes at least one of NF location information or a type of supported sensing service..4.The method of claim 1, further comprising:performing authorization of the requested sensing service after receiving the sensing service request.5.The method of claim 1, further comprising:performing authorization of each of the at least one sensing entity as at least one of a sensing transmitter or a sensing receiver.6.A method performed by access and mobility management function (AMF) in a communication system, the method comprising:receiving, from network function (NF), a request message for information on at least one sensing entity in a target area; andtransmitting, to the NF, the information on the at least one sensing entity in the target area.7.The method of claim 6, further comprising:receiving, from a sensing entity, a registration request message; andtransmitting, to the sensing entity, a message for accepting the registration request message;wherein information on the sensing entity is received from the sensing entity; andwherein the information received from the sensing entity includes a sensing capability of the sensing entity.8.The method of claim 6,wherein the information on the at least one sensing entity corresponds to at least one identifier (ID) of the at least one sensing entity.9.A network entity corresponding to network function (NF) in a communication system, the network entity comprising:at least one transceiver;at least one processor coupled with the at least one transceiver and configured to:receive, from a sensing service consumer, a sensing service request;transmit, to access and mobility management function (AMF), a request message for information on at least one sensing entity in a target area after reception of the sensing service request;receive, from the AMF, the information on the at least one sensing entity in the target area ; andselect at least one sensing entity to join a sensing service based on the information on the at least one sensing entity.10.The network entity of claim 9,wherein the information on the at least one sensing entity corresponds to at least one identifier (ID) of the at least one sensing entity.11.The network entity of claim 9, wherein the at least one processor is further configured to:register a profile of the NF to network repository function (NRF),wherein the profile includes at least one of NF location information or a type of supported sensing service..12.The network entity of claim 9, wherein the at least one processor is further configured to:perform authorization of the requested sensing service after receiving the sensing service request.13.The network entity of claim 9, wherein the at least one processor is further configured to:perform authorization of each of the at least one sensing entity as at least one of a sensing transmitter or a sensing receiver.14.A network entity corresponding to access and mobility management function (AMF) in a communication system, the network entity comprising:at least one transceiver;at least one processor coupled with the at least one transceiver and configured to:receive, from network function (NF), a request message for information on at least one sensing entity in a target area; andtransmit, to the NF, the information on the at least one sensing entity in the target area.15.The network entity of claim 14, wherein the at least one processor is further configured to:receive, from a sensing entity, a registration request message; andtransmit, to the sensing entity, a message for accepting the registration request message;wherein information on the sensing entity is received from the sensing entity; andwherein the information received from the sensing entity includes a sensing capability of the sensing entity.