Support of sensing data and the associated information collection and transport
The method facilitates efficient collection and transfer of sensing data by configuring a sensing function to generate configuration information for sensing entities, addressing the lack of data transfer capabilities in current 5G systems and enhancing sensing services.
Patent Information
- Application Number
- PCT/KR2026/005891
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2026-04-08
- Filing Date
- 2026-05-07
- Publication Date
- 2026-11-12
AI Technical Summary
Current 5G communication systems lack the capability to efficiently support the collection and transfer of sensing data and associated information, which is essential for integrated sensing and communication functionalities.
A method and apparatus are provided to facilitate the collection and transfer of sensing data by configuring a sensing function to generate configuration information for sensing entities, enabling direct connections for data exchange, and processing the received sensing data to support sensing services.
Enables reliable collection and delivery of sensing data, supporting enhanced sensing services in wireless communication networks.
Smart Images

Figure KR2026005891_12112026_PF_FP_ABST
Abstract
Description
SUPPORT OF SENSING DATA AND THE ASSOCIATED INFORMATION COLLECTION AND TRANSPORT
[0001] Certain examples of the present disclosure relate to methods, apparatus and / or systems for facilitating the collection and / or obtaining of sensing data or sensing related information. In various examples, a sensing function is provided (e.g. in the core network) which is configured to generate configuration information for a sensing operation. The configuration information may usable by one or more sensing entities for obtaining sensing data and / or information related to sensing, for provision in response to a request from the sensing function. Various examples of the present disclosure provide examples of signals, sensing data, and characteristics or parameters of said signals and sensing data, any one or more of which may be used in sensing results determination.
[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] Description of Related Art
[0009] The content of the following documents is referred to below and / or their content provides background information that the following disclosure should be considered in the context of:
[0010] [1] 3GPP TS 22.137, "Service requirements for Integrated Sensing and Communication" (e.g. Release 19, v19.1.0).
[0011] [2] 3GPP TR 22.837, "Feasibility Study on Integrated Sensing and Communication" (e.g. Release 19, v19.4.0).
[0012] [3] 3GPP SID RP-242348, "Revised SID: Study on channel modelling for Integrated Sensing And Communication (ISAC) for NR"
[0013] [4] 3GPP TR 38.901, "Study on channel model for frequencies from 0.5 to 100 GHz" (e.g. Release 18, v18.0.0).
[0014] [5] 3GPP S2-2502780, "New SID on Study on Architecture Enhancement to support Integrated Sensing and Communication"
[0015] [6] 3GPP SP-250067, "New SID on Study on Architecture Enhancement to support Integrated Sensing and Communication"
[0016] [7] TR 23.700-14, "Study on Integrated Sensing and Communication" (e.g. Release 20, V0.1.0)
[0017] Note: indicated version numbers are provided for illustrative purposes, other (including future) versions of these documents are considered also.
[0018] 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 (5GS) are now widely deployed, while beyond 5G (B5G) and 6G systems are being considered.
[0019] 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.
[0020] 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 B5G systems, such as 6G, are currently being considered and developed, and are expected to at least partly build on 5G systems.
[0021] New frameworks and architectures are being developed as part of 5G network (and beyond, such as 6G networks) in order to increase the range of functionality and use cases available through 5G networks.
[0022] Amongst new features being developed, there are features relating to integrated sensing and communication.
[0023] 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.
[0024] According to a first aspect, there is provided a method of a sensing function in a wireless communication network, the method comprising: based on a sensing service request, selecting at least one sensing entity; transmitting, to the at least one sensing entity, a sensing request including configuration information for sensing; receiving, from the at least one sensing entity, sensing data; and processing the received sensing data.
[0025] According to an example, the sensing service request is received from a consumer entity; and wherein processing the received sensing data comprises: transmitting a sensing result including the sensing data to the consumer entity, or determining sensing results based on the sensing data, and transmitting the sensing results to the consumer entity.
[0026] According to an example, the method comprises: discovering at least one candidate sensing entity; and selecting the at least one sensing entity from among the at least one candidate sensing entity.
[0027] According to an example, the sensing request is transmitted and / or the sensing data is received over a direct connection established between each sensing entity and the sensing function.
[0028] According to an example, the method comprises: transmit, to one or more of the at least one sensing entity, a request for establishing the direct connection; and receive, from the one or more sensing entity, an indication that the direct connection has been established.
[0029] According to an example, the request for establishing the direct connection comprises connection information of the sensing function.
[0030] According to an example, the connection information includes one or more of: information indicating a destination of the sensing data, an IP address of the sensing function, or a fully qualified domain name (FQDN) of the sensing function.
[0031] According to an example, the sensing request includes information on reporting the sensing data.
[0032] According to an example, the information on reporting the sensing data comprises one or more of: a time to report the sensing data, a periodicity for reporting the sensing data, an event according to which the sensing data is to be reported, one or more criteria for reporting the sensing data, or a threshold volume of data to collect before reporting the sensing data.
[0033] According to an example, the sensing service request comprises one or more of: area of interest (AOI) or target sensing area, required accuracy level of sensing results, required latency of sensing results, required detection probability of sensing results, required false alarm probability of sensing results, a list of candidate sensing entities, one or more sensing objects, or assistance information for determining the configuration information or sensing results.
[0034] According to a second aspect, there is provided a method of a sensing entity in a wireless communication network, the method comprising: receiving, from a sensing function, a sensing request including configuration information for sensing; performing data sensing based on the configuration information; and based on the sensing request, transmitting, to the sensing function, sensing data obtained at least in part from the data sensing.
[0035] According to an example, the sensing request is received and / or the sensing data is transmitted over a direct connection established between the sensing entity and the sensing function.
[0036] According to an example, the method comprises: receiving, from the sensing function, a request for establishing the direct connection; and establishing the direct connection based on the request for establishing the direct connection.
[0037] According to an example, the request for establishing the direct connection comprises connection information of the sensing function.
[0038] According to an example, the connection information includes one or more of: information indicating a destination of the sensing data, an IP address of the sensing function, or a fully qualified domain name (FQDN) of the sensing function.
[0039] According to an example, the sensing request includes information on reporting the sensing data.
[0040] According to an example, the information on reporting the sensing data comprises one or more of: a time to report the sensing data, a periodicity for reporting the sensing data, an event according to which the sensing data is to be reported, one or more criteria for reporting the sensing data, or a threshold volume of data to collect before reporting the sensing data.
[0041] According to an example, the performing of the data sensing and / or the transmitting of the sensing data is based on the information on reporting the sensing data.
[0042] According to an example, the sensing entity is a RAN node.
[0043] According to an example, the method comprises processing results of the data sensing to obtain the sensing data.
[0044] According to an example, the method comprises: transmitting at least part of the sensing data to another sensing entity; and / or receiving, from another sensing entity, a part of the sensing data, wherein the part of the sensing data is obtained by the other sensing entity.
[0045] According to a third aspect, there is provided one or more entity configured to operate as a sensing function in a wireless communication network, the one or more entity configured to: based on a sensing service request, select at least one sensing entity; transmit, to the at least one sensing entity, a sensing request including configuration information for sensing; receive, from the at least one sensing entity, sensing data; and process the received sensing data.
[0046] According to a fourth aspect, there is provided one or more entity configured to operate as a sensing entity in a wireless communication network, the one or more entity configured to: receive, from a sensing function, a sensing request including configuration information for sensing; perform data sensing based on the configuration information; and based on the sensing request, transmit, to the sensing function, sensing data obtained at least in part from the data sensing.
[0047] According to a fifth aspect, there is provided one or more entity configured to perform a method according to any method described above.
[0048] According to a sixth aspect, there is provided a computer-readable storage medium comprising instructions which, when executed by at least one processor, cause one or more entity including the at least one processor to perform a method according to any one of the methods described above.
[0049] According to a seventh aspect, there is provided a network comprising one or more entity according to the third aspect, one or more entity according to the fourth aspect, and, optionally, a consumer entity.
[0050] 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.
[0051] According to one embodiment, the present disclosure can efficiently support sensing services in a wireless communication network. Thereby, it provides an advantageous effect of enabling reliable collection and delivery of sensing data.
[0052] Embodiments / examples of the present disclosure are further described hereinafter with reference to the accompanying drawings, in which:
[0053] Figure 1A shows an example of a system with monostatic sensing.
[0054] Figure 1B shows an example of a system with bistatic sensing.
[0055] Figure 2 is a table for Performance requirements for 5G Wireless sensing.
[0056] Figure 3 is a call flow diagram showing a procedure for collecting and transporting sensing data or information according to various examples of the present disclosure.
[0057] Figure 4 is a block diagram illustrating an example structure of a network entity according to various examples of the present disclosure.
[0058] Figure 5A and Figure 5B is a call flow diagram showing a procedure for collecting and transporting sensing data or information according to various examples of the present disclosure.
[0059] Figure 6 is a procedure of Sensing Data and the Associated Information Collection and Transport.
[0060] Figure 7A and Figure 7B is a procedure of Sensing Data and the Associated Information Collection and Transport.
[0061] Figure 8 is a flow diagram illustrating a method of a sensing function according to various examples of the disclosure.
[0062] Figure 9 is a flow diagram illustrating a method of a sensing entity according to various examples of the disclosure.
[0063] 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.
[0064] The same or similar components may be designated by the same or similar reference numerals, although they may be illustrated in different drawings.
[0065] 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.
[0066] 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.
[0067] 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.
[0068] 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.
[0069] Throughout the description, the expression "at least one of A, B and / or C" (or the like), the expression "and / or", 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.
[0070] 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.
[0071] 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.
[0072] Certain examples of the present disclosure relate to methods, apparatus and / or systems for facilitating the collection and / or obtaining of sensing data or sensing related information. In various examples, a sensing function is provided (e.g. in the core network) which is configured to generate configuration information for a sensing operation. The configuration information may usable by one or more sensing entities for obtaining sensing data and / or information related to sensing, for provision in response to a request from the sensing function. Various examples of the present disclosure provide examples of signals, sensing data, and characteristics or parameters of said signals and sensing data, any one or more of which may be used in sensing results determination.
[0073] The following examples are applicable to, and use terminology associated with, 3GPP 5G. However, the skilled person will appreciate that the techniques disclosed herein are not limited to these examples or to 3GPP 5G, 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. The skilled person will appreciate that the techniques disclosed herein may be applied in any existing or future releases of 3GPP 5G NR 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. In particular, the following disclosure should be considered at least in relation to 6G also, which uses or is expected to use at least part of the 5G architecture, or equivalent, and to which the present disclosure also relates.
[0074] A particular network entity may be implemented 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.
[0075] The skilled person will appreciate that the present disclosure is not limited to the specific examples disclosed herein. For example:
[0076] The techniques disclosed herein are not limited to 3GPP LTE, LTE-A, 5G, B5G or 6G.
[0077] 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.
[0078] 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.
[0079] One or more further elements, entities and / or messages may be added to the examples disclosed herein.
[0080] One or more non-essential elements, entities and / or messages may be omitted in certain examples.
[0081] 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.
[0082] 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.
[0083] Information carried by a particular message in one example may be carried by two or more separate messages in an alternative example.
[0084] Information carried by two or more separate messages in one example may be carried by a single message in an alternative example.
[0085] The order in which operations are performed may be modified, if possible, in alternative examples.
[0086] 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.
[0087] 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.
[0088] 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.
[0089] A network according to one or more of the examples disclosed herein may include one or more of a Network Data Analytics Function (NWDAF) entity, an Access and Mobility Management Function (AMF) entity, a Session Management Function (SMF) entity, a Network Slice Selection Function (NSSF) entity, a Network Repository Function (NRF) entity, Application Function (AF) entity, and an Operation and Maintenance (OAM) entity. The network may include one or more Service Consumers (including one or more of the entities mentioned above and / or one or more other entities) that receive analytics from NWDAF. The skilled person will appreciate that a network may omit one or more of the entities mentioned above and / or may comprise one or more additional entities.
[0090] All proposals, embodiments, and examples disclosed herein may also apply for, but are not limited to, NR NTN, LTE-M / eMTC NTN, E-UTRA NTN or even 6G NTN.
[0091] As described above, the integrated sensing and communication is highly data driven. As it has been agreed in ISAC KI#4, 3GPP SA2 will work on the solutions to support Sensing Data and the Associated Information Collection and Transport. However, the current 5GC design and functionality is not able to support the sensing data and information collection and transfer without enhancement. The following identified questions in key issue#4 description shall be addressed by 3GPP SA2:
[0092] How to collect sensing data (and the associated information, if any) for sensing result generation?
[0093] Which Sensing Function performs sensing result generation?
[0094] Whether and what the above associated information is required for sensing result generation
[0095] Various embodiments and examples of the present disclosure aim to provide solutions to one or more of the above issues. For example, various examples aim to provide an end-to-end solution to support sensing data and information collection and transfer.
[0096] The following terms (with given definition) may be used herein:
[0097] Sensing Service Consumer: The entity that may consume the Sensing Result. The Sensing Service Consumer may also request the Sensing Result.
[0098] Sensing Entity: The Sensing Entity may refer 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.
[0099] Sensing Function (SF): May indicate the logical function which is involved to support Sensing Service. The Sensing Function cannot be a Sensing Entity. The SF may be the core NF that hosts the sensing function / functionality.
[0100] Sensing Service: Capability to collect and provide information about object and / or characteristics of the environment using radio signals.
[0101] 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.
[0102] Sensing result: Processed 3GPP sensing data as may be requested by a service consumer.
[0103] Sensing signals: Transmissions on the 3GPP radio interface that may be used for sensing purposes. The sensing signals may be signals for sensing purposes only and / or signals for sensing and / or communication between NW and UEs or between UEs and UEs (e.g. via sidelink).
[0104] 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, may be extended by information created via previously specified functionalities in EPC and / or E-UTRAN.
[0105] 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.
[0106] Sensing assistance information: Information that is provided to the 5G system from a third-party (e.g. a trusted third-party) and that may be used to support the derivation of a sensing result. This information does not contain 3GPP sensing data.
[0107] Sensing contextual information: Information that is exposed with the sensing results by 5G or future (e.g. 6G) system to a third-party (e.g. 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, metric / information related to sensing performance evaluation, involved sensing entities, the type of sensing area (e.g. Urban / rural, road / highway / railway, indoor / outdoor, etc.) etc. This information does not contain 3GPP sensing data.
[0108] Sensing group: A set of sensing transmitters and sensing receivers whose location may be known and whose sensing data may be collected synchronously.
[0109] Sensing transmitter: A sensing transmitter is an entity that sends out the sensing signal which the sensing service will use in its operation. A Sensing transmitter may be part of a RAN node or a UE. A Sensing transmitter may be located in the same or different entity as a / the Sensing receiver.
[0110] 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 may be part of a RAN node or a UE. A sensing receiver may be located in the same or different entity as a / the sensing transmitter.
[0111] Sensing transmitter (Rx) / sensing receiver (Tx): Locations are selected among the TRPs / gNB / RAN node and UEs locations in the corresponding communication scenario
[0112] Sensing Transmitter and Sensing Receiver: May be or include any combination of UE, TRP / gNB, e.g. UE-UE, TRP-TRP, TRP-UE, etc.
[0113] Target sensing service area: A location area (e.g. a cartesian location area) that needs to be sensed by deriving characteristic(s) 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 may include both indoor and outdoor environments.
[0114] Device-free sensing: That the sensing target(s) (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).
[0115] Device-based sensing: That the sensing target(s) 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.
[0116] In the present disclosure, both device-free and device-based sensing are considered, e.g. the sensing object might be an object that can or cannot transmit or receive (radio) signals.
[0117] Sensing process / sensing operation: May include one or more of the following procedures: sensing authorization, sensing function and / or sensing entity registration, discovery, (re-)selection; sensing configuration; sensing signal / data generation, transmission, measurement; sensing signal / data transfer; sensing result computation / calculation; exposure of sensing results, sensing data / signal, sensing contextual data, etc.
[0118] Herein, when reference is made to a sensing transmitter or sensing receiver, it will be understood that more general reference can be made to an entity, network entity or apparatus, which may itself be part of another entity or a system.
[0119] Acronyms and Definitions (as may be used herein)
[0120] 3GPP 3rdGeneration Partnership Project
[0121] 5G 5thGeneration
[0122] 5GC 5G Core
[0123] 5QI 5G QoS Identifier
[0124] 5GS 5G System
[0125] 5GSM 5G System Session Management
[0126] 5GMM 5G System Mobility Management
[0127] AF Application Function
[0128] AI Artificial Intelligence
[0129] AIML Artificial Intelligence / Machine Learning
[0130] AM Acknowledged Mode
[0131] AMF Access and Mobility Management Function
[0132] AS Application Server
[0133] AS RAI Access Stratum Release Assistance Information
[0134] ASP Application Service Provider
[0135] ATSSS Access Traffic Steering Switching & Splitting
[0136] AUSF Authentication Server Function
[0137] CIoT Cellular Internet of Things
[0138] CP Control Plane
[0139] CQI Channel Quality Indicator
[0140] CSI Channel Status Information
[0141] DCQR Downlink Channel Quality Report
[0142] DNAI Data Network Access Identifier
[0143] DNN Data Network Name
[0144] DNS Domain Name Server
[0145] DRB Data Radio Bearer
[0146] EDT Early Data Transmission
[0147] eMTC enhanced Machine-Type Communication
[0148] eNB Evolved Node B
[0149] EPS Evolved Packet System
[0150] FQDN Fully Qualified Domain Name
[0151] GBR Guaranteed Bit Rate
[0152] GMLC Gateway Mobile Location Centre
[0153] gNB Next generation Node B
[0154] GPSI Generic Public Subscription Identifier
[0155] IAB Integrated Access and Backhaul
[0156] ID Identity / Identifier
[0157] IIoT Industrial Internet of Things
[0158] IMEI International Mobile Equipment Identities
[0159] IMS IP Multimedia Subsystem
[0160] IP Internet Protocol
[0161] I-SMF Intermediate SMF
[0162] LMF Location Management Function
[0163] MA-PDU Multiple Access PDU
[0164] ML Machine Learning
[0165] MME Mobility Management Entity
[0166] MN Master Node
[0167] MO Mobile Originating
[0168] MNO Mobile Network Operator
[0169] MPS Multimedia Priority Services
[0170] MT Mobile Termination
[0171] NAS Non-Access Stratum
[0172] NB-IoT Narrowband (NB) Internet of Things (IoT)
[0173] NEF Network Exposure Function
[0174] NRF Network Repository Function
[0175] NG-RAN Next Generation Radio Access Network
[0176] NG-eNB Next Generation eNB
[0177] NSA Non-Standalone
[0178] NTN Non-Terrestrial Network
[0179] NW Network
[0180] NWDAF Network Data Analytics Function
[0181] OAM Operations, Administration and Maintenance
[0182] OS Operating System
[0183] PCF Policy Control Function
[0184] PCC Policy and Charging Control
[0185] PDCCH Physical Downlink Control Channel
[0186] PDR Packet Detection Rule
[0187] PDU Protocol Data Unit
[0188] PMF Performance Measurement Function
[0189] PRACH Physical Random Access Channel
[0190] PRS Positioning Reference Signal
[0191] PRU Positioning Reference Unit
[0192] PUSCH Physical Uplink Shared Channel
[0193] QFI QoS Flow Identifier (ID)
[0194] QoE Quality of Experience
[0195] QoS Quality of Service
[0196] RACH Random Access Channel
[0197] RAN Radio Access Network
[0198] RAT Radio Access Technology
[0199] RLC-AM Radio Link Control Acknowledge Mode
[0200] RLC-UM Radio Link Control Unacknowledge Mode
[0201] SA Standalone
[0202] SBA Service-Based Architecture
[0203] SBI Service-Based Interface
[0204] SCEF Service Capability Exposure Function
[0205] SCP Service-Based Communication Proxy
[0206] SCTP Stream Control Transmission Protocol
[0207] SDAP Service Data Adaptation Protocol
[0208] SDU Service Data Unit
[0209] SF Sensing Function
[0210] SIM Subscriber Identity Module
[0211] SLA Service Level Agreement
[0212] SM Session Management
[0213] SMF Session Management Function
[0214] SN Secondary Node
[0215] S-NSSAI Single Network Slice Selection Assistance Information
[0216] SRS Sounding Reference Signal
[0217] SSC Session and Service Continuity
[0218] SUPI Subscription Permanent Identifier
[0219] TAI Tracking Area Identity
[0220] TE Terminal Equipment
[0221] TN Terrestrial Network
[0222] TS Technical Specification
[0223] UDM Unified Data Manager
[0224] UDR Unified Data Repository
[0225] UE User Equipment
[0226] UL Uplink
[0227] UM Unacknowledged Mode
[0228] UP User Plane
[0229] UPF User Plane Function
[0230] URLLC Ultra-Reliable and Low-Latency Communication
[0231] URSP UE Route Selection Policy
[0232] XRM Extended Reality and Media
[0233] 3GPP SA1 work on Integrated Sensing and Communication
[0234] As it has been documented in TR 22.837, there are various use cases requiring 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. Other various use cases include, for example, to detect rainfall and flood, management of traffic flow and parking control, health and sleep monitoring at home, etc.
[0235] As it has been documented in TS 22.137 [1],
[0236] 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.
[0237] 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.
[0238] 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.
[0239] 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.
[0240] In some cases, 5G wireless sensing can also use non-3GPP type sensors (e.g., Radar, camera) to further support the 3GPP-based sensing.
[0241] SA1 consolidated the functional requirement to support integrated sensing by 3GPP. As documented in clause 7.1 of TR 22.837 [2], the functional requirements include the following tables:
[0242] Table 1 - Table 7.1.1-1 of TR 22.837 General Consolidated Requirements CPR #Consolidated Potential RequirementOriginal PR #CommentCPR 7.1.1-1The 5G system shall be able to provide 5G wireless sensing service in a sensing service area location using sensing transmitters and sensing receivers.PR 5.2.6-1PR 5.9.6-1PR 5.11.6-1P.R 5.14.6-1PR 5.1.6-2CPR 7.1.1-2Subject to regulation and operator policy, the 5G network shall be able to activate, configure, and deactivate 5G wireless sensing based on parameters such as location and network conditions (e.g. network load).P.R 5.14.6-3P.R 5.13.6-7PR 5.8.6-6CPR 7.1.1-3Subject to user consent, regulation, and operator's policy, the 5G system shall be able to collect non-3GPP sensing data from authorized non-3GPP sensors and securely provide it to 5G network.PR.5.4.6-1PR 5.21.6-2CPR 7.1.1-4The 5G system shall support continuity for 5G wireless sensing service (e.g. for sensing a moving object).PR 5.23.6 -1PR 5.18.6.1CPR 7.1.1-5Subject to operator's policy, the 5G System shall be able to provide the 5G wireless sensing service in case of roaming.PR 5.24.6-1CPR 7.1.1-6Subject to user consent, regulation, and operator's policy, the 5G system should support the combination of the 3GPP sensing data and non-3GPP sensing data to derive a combined sensing result.PR 5.21.6-3PR 5.4.6-4PR 5.27.6-2CPR 7.1.1-7Subject to regulation and operator's policy, 5G network shall provide prioritization among 5G wireless sensing services (e.g. prioritizing between communication and sensing services).PR 6.2.2-1CPR 7.1.1-8The 5G system shall be able to enable UEs without 5G coverage to use unlicensed spectrum to provide 5G wireless sensing service.PR 5.25.6-3PR 5.1.6-5PR 5.25.6-2CPR 7.1.1-9Subject to regulation, the 5G system shall enable UEs supporting V2X application to perform 5G Wireless sensing when not served by RAN using the allowed ITS spectrum and unlicensed spectrum.PR 5.30.6-2CPR 7.1.1-10The 5G system shall be able to provide sensing service to detect, identify and / or track one or more objects (e.g., UAVs, birds) and their environment.Note: There is a need to clarify "identify" during normative phase.PR 5.12.6-2PR 5.10.6-1CPR 7.1.1-11Based on operator's policies, operator's control and regulation, the 5G system shall be able to collect 3GPP sensing data from sensing receivers for processing.PR 5.2.6-4PR. 5.3.6-1PR. 5.6.6-1PR. 5.7.6-1PR 5.8.6-2PR.5.1.6-4PR 5.9.6-3PR 5.11.6-2PR 5.13.6-3PR 5.17.6-4PR 5.2.6-5PR. 5.3.6-2PR 5.13.6-1PR 5.21.6-1CPR 7.1.1-12Subject to operator's policy, the 5G system may be able to use sensing assistance information to derive the sensing result.PR 5.22.6-2
[0243] - Configuration and authorization
[0244] Table 2 - Table 7.1.2-1 of TR 22.837 Configuration and authorization Consolidated Requirements CPR #Consolidated Potential RequirementOriginal PR #CommentCPR 7.1.2-1The 5G system shall be able to provide mechanisms for an MNO to configure UEs supporting V2X application for 5G Wireless sensing service when not served by RAN.PR 5.30.6-1CPR 7.1.2-2Subject to regulation and operator's policies, the 5G network shall be able to configure and / or authorize or revoke authorization of sensing service, sensing transmitter(s) and sensing receiver(s) for 5G wireless sensing service.NOTE: Such configuration and authorization can be based on sensing transmitter or sensing receiver location, specific time, sensing duration, sensing accuracy, target sensing geographical area, establishing of communication to transfer sensing data, etc.PR 5.2.6-3PR 5.15.6-1PR 5.9.6-2PR 5.20.6-2PR 5.8.6-1PR 5.8.6-4PR 5.28.6-1PR 5.1.6-1PR 5.5.6-3PR 5.11.6-4P.R 5.13.6-8P.R 5.10.6-2PR 5.17.6-3PR 5.24.6-2CPR 7.1.2-3Based on location, the 5G network shall be able to ensure that sensing transmitters and sensing receivers use licensed spectrum only in network coverage and under the full control of the operator who provides the coverage.NOTE 1: The above requirement does not apply for public safety and V2X networks with dedicated spectrum, where 5G wireless sensing can be allowed out of coverage or in partial coverage as well.PR 5.25.6-1PR 5.20.6-1
[0245] - Network exposure
[0246] Table 3 - Table 7.1.3-1 of TR 22.837 Network exposure Consolidated RequirementsCPR #Consolidated Potential RequirementOriginal PR #CommentCPR 7.1.3-1Subject to operator's policy, the 5G network shall be able to provide secure means to report sensing result to a trusted third-party requesting information about a target object when specific requested conditions are met.NOTE: These conditions could be e.g. the target object distance from the restricted area border or entering restricted area.PR 5.13.6-6CPR 7.1.3-2Subject to operator's policy, the 5G network shall be able to provide secure means to enable trusted third-party to request discovering a sensing group in the proximity of the UE that is requesting a 5G wireless sensing service from application server.PR 5.19.6-2CPR 7.1.3-3Subject to operator's policy and regulation, the 5G network shall provide secure means for a trusted third-party to request 5G wireless sensing service based on specific parameters (e.g. refresh rate, period of time, sensing KPIs, geographical location) and to receive the corresponding sensing results.PR 5.11.6-3PR 5.13.6-4PR 5.12.6-3PR 5.12.6-5PR 5.12.6-4PR 5.5.6-1PR 5.5.6-2PR 5.25.6-4PR 5.2.6-6PR 5.9.6-4PR 5.7.6-2PR 5.15.6-2PR 5.14.6-2PR 5.10.6-3PR 5.13.6-5PR 5.22.6-1PR 5.27.6-1PR 5.1.6-3PR 5.4.6-2PR 5.4.6-3CPR 7.1.3-4Subject to operator's policy, the 5G system shall be able to provide secure means for a trusted third-party to receive sensing results with contextual information.PR 5.8.6-5PR 5.3.6-3CPR 7.1.3-5Subject to user's consent, regulation and operator's policy, the 5G network may provide secure means to expose to a trusted third-party the combined sensing result derived from the joint processing of the 3GPP sensing data and non-3GPP sensing data.PR 5.21.6-4CPR 7.1.3-6Subject to operator's policy, the 5G network may provide secure means for the operator to expose information towards trusted third-party on whether a given sensing service is available and the estimated quality of the given service for a certain geographic area and time.PR 5.2.6-8PR 5.10.6-5PR 5.18.6-3CPR 7.1.3-7Subject to operator's policy, the 5G network may enable secure means for a trusted third party to provide sensing assistance information.PR 5.32.6-1
[0247] - Security
[0248] Table 4 - Table 7.1.4-1 of TR 22.837 Security Consolidated RequirementsCPR #Consolidated Potential RequirementOriginal PR #CommentCPR 7.1.4-1The 5G system shall provide a mechanism to protect identifiable information that can be derived from the 3GPP sensing data from eavesdropping.PR 5.16.6-1CPR 7.1.4-2The 5G system shall limit the exposure of the sensing results only to third party authorized to receive that sensing results.PR 6.1.2-1CPR 7.1.4-3The 5G system shall support encryption, integrity protection, privacy of the 3GPP sensing data, non-3GPP sensing data and sensing results, to protect the data inside the 5G system.PR 5.27.6-4PR 5.27.6-3PR 5.23.6 -2PR 6.1.2-2CPR 7.1.4-4The 5G system shall support appropriate sensing KPIs of 5G wireless sensing for both situations where consent can be obtained from the sensing targets, and where it cannot.PR 6.1.2-3CPR 7.1.4-5Subject to regulation and user's consent, the 5G network may associate sensing results and identity of the user together for further processing for a sensing target that has a UE and the UE is subscribed in the same network.PR 6.1.2-4
[0249] - Charging
[0250] Table 5 - Table 7.1.5-1 of TR 22.837 Charging Consolidated RequirementsCPR #Consolidated Potential RequirementOriginal PR #CommentCPR 7.1.5-1The 5G system shall be able to support charging for the 5G wireless sensing service (e.g. considering sensing KPIs, duration).PR 5.20.6-4PR 5.2.6-7PR 5.28.6-2
[0251] Sensing operation defined by 3GPP
[0252] As documented in clause 4.2 of TS 22.137 [1],
[0253] 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.
[0254] 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.
[0255] 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.
[0256] 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.
[0257] The 5G wireless sensing service could be consumed by either the 3GPP system or trusted third-party.
[0258] It is expected that the 5G wireless sensing service will work independently of positioning service.
[0259] There are some factors affecting the performance that the 5G wireless sensing service can achieve e.g.,
[0260] Operating frequencies and used bandwidth.
[0261] 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.
[0262] 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.
[0263] There are two major (or main) types of sensing operations: Monostatic and Bistatic sensing. There is also a more advanced scenario - Multistatic sensing.
[0264] In monostatic sensing, the sensing transmitter and sensing receiver are co-located in the same entity. An example of this is illustrated in Figure 1A, which is Figure 4.2-1: Example of sensing with co-located sensing receiver and sensing transmitter of TS 22.137 [1].
[0265] In bistatic sensing, the sensing receiver and sensing transmitter are in different entities. An example of this is illustrated in Figure 1B, which is Figure 4.2-2: Example of sensing with separated sensing receiver and sensing transmitter of TS 22.137 [1].
[0266] 5G wireless sensing performance requirements
[0267] As documented in clause 6 of TS 22.137 [1],
[0268] 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:
[0269] Accuracy of positioning estimatedescribes 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.
[0270] Accuracy of velocity estimatedescribes the closeness of the measured sensing result (i.e., velocity) of the target object to its true velocity.
[0271] Confidence leveldescribes the percentage of all the possible measured sensing results that can be expected to include the true sensing result considering the accuracy.
[0272] SensingResolutiondescribes the minimum difference in the measured magnitude of target objects (e.g., range, velocity) to be allowed to detect objects in different magnitude.
[0273] Missed detection probabilitydescribes 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.
[0274] False alarm probabilitydescribes 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.
[0275] 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.
[0276] 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.
[0277] 5G wireless sensing performance requirements are applied to 3GPP sensing data and sensing results.
[0278] The Performance requirements for 5G Wireless sensing are detailed in Table 6.2-1: Performance requirements for 5G Wireless sensing of TS 22.137 [1], as shown in Figure 2.
[0279] 3GPP RAN1 work on Study on channel modelling for Integrated Sensing and Communication (ISAC) for NR
[0280] 3GPP RAN1 working group studied channel modelling for integrated sensing and communication for NR for the objectives documented in SID RP-242348 [3], including:
[0281] 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:
[0282] UAVs
[0283] Humans indoors and outdoors
[0284] Automotive vehicles (at least outdoors)
[0285] Automated guided vehicles (e.g. in indoor factories)
[0286] Objects creating hazards on roads / railways, with a minimum size dependent on frequency
[0287] 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).
[0288] 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.)
[0289] For the above use cases, sensing modes and frequencies:
[0290] Identify details of the deployment scenarios corresponding to the above use cases.
[0291] Define channel modelling details for sensing using 38.901 as a starting point, and taking into account relevant measurements, including:
[0292] 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;
[0293] spatial consistency.
[0294] TRP is the Transmission and Reception Point.
[0295] The outcome of the study item is documented in TR 38.901 [4]. 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.
[0296] Standards background of ISAC in 3GPP SA2 working group
[0297] 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 [5]. Then the SID was further modified and approved during SA#107 meeting in March 2025 in SP-250067 [6]. The following aspects will be studied:
[0298] WT-1: Architecture and function enhancements to support sensing.
[0299] WT-2: Service authorization and revocation. This includes investigating mechanisms for authorization and revocation sensing service requests from the service consumer.
[0300] WT-3: Discovery and selection of sensing entities based on service requirements triggered by the service request and capability of the sensing entities.
[0301] WT-4: Sensing data and the associated information collection and transport mechanisms for result calculation.
[0302] 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.
[0303] WT-6: Configuration parameters / policy provisioning for the support of ISAC services.
[0304] 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 [7], including:
[0305] 5.1Key Issue #1: System Architecture to Support Sensing
[0306] 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.
[0307] NOTE:Solutions for other key issues may also impact general architecture aspects covered by this key issue.
[0308] 5.2Key Issue #2: Authorization and Revocation to Support Sensing Service
[0309] The key issue is to address the authorization and revocation for a particular sensing service, specifically:
[0310] authorization of sensing service requests and revocation of an on-going sensing service; and
[0311] authorization and revocation for the sensing entities if applicable.
[0312] 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:
[0313] 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;
[0314] whether and how to perform sensing service revocation if required, and the criteria for the revocation, based on the requirements from TS 22.137 ;
[0315] whether, how and which entity( / entities) performs the sensing service request authorization and sensing service revocation if required;
[0316] 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.
[0317] For the authorization and revocation for the sensing entities if applicable, the study needs to address the following aspects:
[0318] whether, when and which entity performs the authorization and revocation of the sensing entity( / entities);
[0319] if needed, the granularity of the sensing entity authorization, e.g. based on TS 22.137 ;
[0320] if needed, storage and management of the authorization information for the sensing entities.
[0321] NOTE:The authorization and revocation for the sensing entities can be related to the key issue #3 on sensing entities discovery and selection.
[0322] 5.3Key Issue #3: Sensing Entity and Sensing Function Discovery and (Re-)Selection
[0323] This key issue aims to study how to perform the Sensing entity(ies) and Sensing Function(s) discovery and (re-)selection, in particular:
[0324] When required, for the discovery and (re-)selection of the Sensing entity(ies), the study needs to address the following aspects:
[0325] Which entity(ies) performs the discovery and (re-)selection of the Sensing entity(ies);
[0326] What the information and / or criteria are taken into account for the discovery and (re-)selection of the Sensing entity(ies); and
[0327] The procedure(s) for the discovery and (re-)selection of the Sensing entity(ies).
[0328] When required, for the discovery and (re-)selection of the Sensing Function(s), the study needs to address the following aspects:
[0329] Which entity(ies) performs the discovery and (re-)selection of Sensing Function(s);
[0330] What the information and / or criteria are taken into account for the discovery and (re-)selection of Sensing Function(s); and
[0331] The procedure(s) for the discovery and (re-)selection of the Sensing Function(s).
[0332] 5.4Key Issue #4: Sensing Data and the Associated Information Collection and Transport
[0333] Integration of sensing and communication requires 3GPP network to collect and transfer sensing data and the associated information to a Sensing Function.
[0334] This Key Issue aims to study:
[0335] How to collect sensing data (and the associated information, if any) for sensing result generation?
[0336] Which Sensing Function performs sensing result generation?
[0337] Whether and what the above associated information is required for sensing result generation
[0338] NOTE:Implications to RAN or RAN dependent aspects will be coordinated with RAN WGs.
[0339] 5.5Key Issue #5: Sensing Result Exposure
[0340] This key issue addresses the exposure of sensing results to support sensing services. The aspects to be studied in this key issue include:
[0341] 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.
[0342] How the Core Network exposes sensing results to the sensing service consumer (e.g., one time, periodic or event trigger).
[0343] 5.6Key Issue #6: Configuration Parameter Provisioning of Sensing Entities.
[0344] This Key Issue will study how parameter provisioning of sensing entities is performed.
[0345] In particular, this Key Issue will study:
[0346] How and what parameters need to be exchanged between the sensing entities and the Core Network.
[0347] NOTE:This KI needs to be aligned with RAN WGs.
[0348] The integrated sensing and communication is highly data driven. As it has been agreed in ISAC KI#4, 3GPP SA2 will work on the solutions to support Sensing Data and the Associated Information Collection and Transport. However, the current 5GC design and functionality is not able to support the sensing data and information collection and transfer without enhancement.
[0349] Sensing related data / signals
[0350] Sensing detection / results may be determined by different types of algorithms. The radio / sensing signal(s) sent by the sensing transmitter(s) and / or received by sensing receiver(s) is / are the sensing data (e.g. major or main sensing data) that may be used to determine the sensing results for 3GPP-sensing, e.g. at the sensing receiver or another entity which obtains the sensing data from the sensing receiver.
[0351] In various examples, any one or more of the following radio signals, sensing signals or sensing data might be transmitted and / or measured for sensing results determination (e.g. for use in determining or obtaining sensing results):
[0352] UL and / or DL reference / sounding signals,
[0353] CRI-RS, SRS,
[0354] beam management related signals,
[0355] RRM related signals,
[0356] newly defined radio signals for sensing purposes (e.g. sensing reference signals),
[0357] etc.
[0358] In various examples (including examples in combination with those above defining radio signals, sensing signals or sensing data for use in determining sensing results), any one or more of the following characteristics or parameters of the radio signals, sensing signals or sensing data may be useful / used for sensing results determination (e.g. for use in determining or obtaining sensing results), e.g. by the network / SF / RAN node:
[0359] signal timing information, Time of departure (TOD), time of arrival (TOA), time difference of arrival (TDOA), and / or one way delay / time or RTT (round trip time);
[0360] At RX: signal (arrival) angle information, angle of arrival (AOA) and / or Zenith Angle of Arrival (ZOA);
[0361] At TX: signal (departure) angle information, angle of departure (AOD) and / or Zenith Angle of Departure (ZoD);
[0362] AoA, ZoA, AoD and / or ZoD at target;
[0363] signal strength information, Sent / departure signal strength / power (i.e. sent signal strength, sent signal power, departure signal strength, departure signal power), received signal strength (RSS) / power, Signal-to-Noise Ratio (SNR), effective bandwidth of the received waveform and / or path-overlap coefficient (POC);
[0364] Doppler frequency;
[0365] Departure phase and / or arrival phase of sensing signals;
[0366] the number of direct path(s) and / or indirect path(s) for a target;
[0367] Channel estimation and / or modelling error;
[0368] Frequency offset / drifting;
[0369] Timing synchronization error, e.g. between (or between any two or more of) UEs, RAN node, core network NFs, OAM, 3rd parties / AFs, within the 3GPP network, between the 3GPP network and other external sources, etc.
[0370] Any one or more of the characteristics / parameters of the radio / sensing signals / data may be measured by one or more sensing entities and reported to the network (e.g. SF) to derive sensing results. For example, the SF, or another CN entity, may determine sensing results based on measured information (e.g. characteristics / parameters and / or radio / sensing signals or radio data) received from one or more sensing entities. The SF may also take other assistance information into account for one or more of sensing results calculation, the results of non-3GPP sensing, sensing environment related information, map information, whether the sensing service is aided by other devices (e.g. intelligent reflecting surface, IRS), etc. Said information may be provided by a sensing service consumer (e.g. in the sensing service / results request), requested by SF (e.g. from other 5GC NFs, RAN node, UE or other parties, etc.), pre-configured (e.g. by operators or vendors), etc.
[0371] It is to be understood that, in the present disclosure, SF is used as an example of a sensing related NF. However, in any step or operation described herein (e.g. any step or feature described in relation to the SF), the SF can be replaced by any other core NF or other entities that supports sensing related function / functionality.
[0372] The following describes example impacts on services, entities, and interfaces in accordance with an embodiment of the present disclosure.
[0373] The SSF (Sensing Service Function) may be configured to trigger sensing data collection and / or sensing data transmission towards one or more sensing entities. The SSF may also be configured to determine a configuration of radio signals for sensing and to indicate the determined configuration to the one or more sensing entities. The SSF may further be configured to receive sensing data reported from the one or more sensing entities, and to derive sensing results based on the received sensing data, which may include aggregated sensing data obtained from a plurality of sensing entities. The sensing results derived by the SSF may then be exposed to a sensing service consumer (e.g., an Application Function (AF) or another external consumer entity).
[0374] The UPF (User Plane Function) and the AMF (Access and Mobility Management Function) may be configured to support, if needed, the transfer of sensing data from the one or more sensing entities to the SSF.
[0375] Figure 1A illustrates a monostatic sensing arrangement within a 3GPP system(1000A), in accordance with an embodiment of the present disclosure.
[0376] As shown in Figure 1A, a sensing transmitter(1300A) and a sensing receiver(1200A) are co-located within the 3GPP system(1000A). The sensing transmitter(1300A) transmits sensing signals(1001A) towards one or more objects(1100A-1, 1100A-2) (e.g., a target object such as a drone, vehicle, person, or other physical entity) located within a sensing area. The sensing signals(1001A) are reflected, scattered, or otherwise affected by the one or more objects(1100A-1, 1100A-2), and the resulting signals (e.g., reflected sensing signals(1001A)) are received by the sensing receiver(1200A) co-located with the sensing transmitter(1300A).
[0377] The sensing receiver(1200A) provides 3GPP sensing data(1002A) (e.g., raw measurements, processed measurements, or a combination thereof) derived from the received signals to a Processing Module(1400A). The Processing Module(1400A) determines sensing results(1003A) based on the 3GPP sensing data(1002A). The sensing results(1003A) may include, for example, presence, position, velocity, shape, or other characteristics of the one or more objects(1100A-1, 1100A-2).
[0378] The 3GPP system(1000A) may expose the sensing results(1003A) to one or more consumers via a 5G wireless sensing service. The 5G wireless sensing service represents a conceptual sensing service exposed by the 3GPP system(1000A) and may be implemented by a combination of network entities (e.g., a sensing function), and need not be implemented as a single physical entity. The sensing results(1003A) may be further provided to an external entity, such as a trusted third party(1500A) (e.g., an Application Function (AF) or another consumer entity), based on a corresponding sensing service request.
[0379] It will be appreciated that the sensing transmitter(1300A), the sensing receiver(1200A), and the Processing Module(1400A)may be implemented within a single network entity (e.g., a single gNB) or across multiple network entities. In some embodiments, the sensing transmitter(1300A) and the sensing receiver(1200A) may correspond to a sensing entity as described elsewhere in the present disclosure, and the Processing Module(1400A) may correspond to, or be implemented within, a sensing function.
[0380] Figure 1B illustrates a bistatic sensing arrangement within a 3GPP system(1000B), in accordance with another embodiment of the present disclosure.
[0381] In contrast to the monostatic-like arrangement of Figure 1A, in Figure 1B the sensing transmitter(1300B) and the sensing receiver(1200B) are spatially separated from each other. The sensing transmitter(1300B) is located at a first position and transmits sensing signals(1001B) towards one or more objects(1100B-1, 1100B-2), while the sensing receiver(1200B) is located at a second position different from the first position and receives the sensing signals(1001B) after they have been reflected, scattered, or otherwise affected by the one or more objects(1100B-1, 1100B-2).
[0382] As in Figure 1A, the sensing receiver(1200B) provides 3GPP sensing data(1002B), derived from the received signals, to a Processing Module(1400B). The Processing Module(1400B) determines sensing results(1003B) based on the 3GPP sensing data(1002B), and the sensing results(1003B) are made available via the 5G wireless sensing service and optionally provided to a trusted third party(1500B).
[0383] In a bistatic arrangement, the geometry between the sensing transmitter(1300B), the one or more objects(1100B-1, 1100B-2), and the sensing receiver(1200B) may provide additional information regarding the one or more objects(1100B-1, 1100B-2) (e.g., based on the path difference between the transmitted sensing signals(1001B) and the received signals). It will be appreciated that the sensing transmitter(1300A) and the sensing receiver(1200B) in Figure 1B may be implemented in respective network entities (e.g., respective gNBs, or a combination of a gNB and a UE), or in any other suitable arrangement, and the Processing Module(1400B) may be implemented in any one of those network entities or in a separate network entity (e.g., a sensing function).
[0384] While Figures 1A and 1B illustrate monostatic-like and bistatic arrangements respectively, the present disclosure is not limited thereto, and other arrangements (e.g., multistatic arrangements involving multiple sensing transmitters and / or multiple sensing receivers) are also contemplated.
[0385] Figure 2 illustrates examples of sensing service categories together with associated key performance indicators (KPIs), in accordance with an embodiment of the present disclosure.
[0386] As illustrated in Figure 2, a sensing service may correspond to one of a plurality of sensing service categories, each associated with a respective sensing scenario (e.g., object detection and tracking, indoor / outdoor tracking, environment monitoring, motion monitoring). Each sensing service category may be characterized by a set of KPIs, including, for example, one or more of:
[0387] a confidence level;
[0388] an accuracy of positioning estimate (e.g., expressed in terms of horizontal and / or vertical accuracy);
[0389] an accuracy of velocity estimate (e.g., expressed in terms of horizontal and / or vertical velocity accuracy);
[0390] a sensing resolution (e.g., a range resolution and / or a velocity resolution);
[0391] a maximum sensing service latency;
[0392] a refreshing rate;
[0393] a missed detection rate; and / or
[0394] a false alarm rate.
[0395] These KPIs may correspond to, or be derived from, one or more parameters included in a sensing service request as described elsewhere in the present disclosure (e.g., a required accuracy level of sensing results, a required latency of sensing results, a required detection probability of sensing results, and / or a required false alarm probability of sensing results).
[0396] A sensing service category may further be associated with a sensing service description identifying a target sensing service area (e.g., indoor / outdoor) and a target sensing object (e.g., human, animal, UAV, vehicle, automated guided vehicle (AGV)). For example, a first sensing service category may correspond to detection of humans or UAVs in an indoor or outdoor environment, while a second sensing service category may correspond to environment monitoring (e.g., rainfall or flooding monitoring) of a particular environment.
[0397] It will be appreciated that the sensing service categories illustrated in Figure 2 are provided as non-limiting examples, and the present disclosure is not limited to any particular set of sensing service categories or KPIs.
[0398] Sensing data and associated information collection and transport
[0399] Figure 3 illustrates a method of sensing data and associated information collection and transport according to various examples of the present disclosure.
[0400] It will be understood that various examples of the present disclosure may include only part of the process shown in Figure 3. For example, various examples focus on the data sensing part (e.g. omitting operation 3(3003) onwards), various examples focus on the information collection part (e.g. omitting operations 0(3000)-2(3002) and 5a(3005a)-5c(3005c) onwards), various examples focus on the transport part (e.g. omitting operations 0(3000)-4(3004)), and various examples consider any combination of the different parts and, more generally, the different operations in Figure 3 as a whole.
[0401] The steps of Figure 3 may be described as follows:
[0402] Operation 0(3000): (This operation is optional) the sensing service consumer / client (3600) may send a sensing service request or sensing service subscription to core network, e.g. the sensing related NF (e.g. SF (3500), NEF or PCF), etc. The sensing service / operation may be triggered by the consumer(3600). In various examples, if the sensing service consumer(3600) is an untrusted AF, the request may be sent via NEF.
[0403] The sensing service consumer(3600) / client may include any one or more of the following information in the sensing service request / subscription:
[0404] Area of interest and / or geographical information of the corresponding sensing services.
[0405] The required, referred and / or expected sensing location or topology of potential sensing entities.
[0406] Timing information (e.g. time window, time stamps / points etc.) for the potential sensing services operation, sensing data collection and / or transfer, sensing result reporting / exposure, and / or valid period of sensing results / sensing data / sensing signal.
[0407] The required, referred and / or expected sensing mode / operations, e.g. network-based and / or UE-based sensing, device-based sensing, device-free sensing, monostatic sensing, bi-static sensing and / or Multistatic sensing, etc.
[0408] The required, referred and / or expected method to methods and / or algorithms for calculating sensing results, e.g. AI based algorithms or other methods; or the types of radio signals / sensing signals that can be used / measured / supported for the request sensing service.
[0409] The required, referred and / or expected sensing detection event (IDs): e.g.
[0410] types of sensing service, sensing targets, sensing object(s) and / or sensing detection events, e.g. detection of certain type of objects (e.g. humans, animals, vehicles, UAVs, AGV, buildings, etc.).
[0411] Number of sensing objects to be detected, e.g. single or multiple sensing objects / targets.
[0412] The required, referred and / or expected certain types of detections (e.g. detection of moving / non-stationary objects, shape (variation) of objects, new objects in sensing area, hazards, speed and / or direction of movement / mobility of sensing objects, and / or distance between sensing objects or between sensing object and reference, etc.
[0413] Sensing assistance information that can be used (i.e. usable) by core network / SF to determine sensing results and / or sensing operation / process configuration. For example, sensing environment information or different scenarios, e.g. outdoor / indoor, rural / urban, highway, railway, mobility speed of sensing objects, etc.
[0414] The required, referred and / or expected accuracy (or confidence) level (or trustworthiness) of sensing results.
[0415] Metric or information related to sensing performance evaluation and / or sensing results determination, e.g. requirements / threshold of detection probability, false alarm probability, resolution of the sensing results / data / signals.
[0416] E.g. the detection probability indicates the probability of detecting a target when a target actually exists.
[0417] E.g. the false alarm probability indicates the probability of detecting a target when a target does not exist.
[0418] The required, referred and / or expected access type (3GPP or non-3GPP) and RAT type (e.g. LTE, NR, 6G and other RAT types).
[0419] 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 and / or sensing group ID (e.g. an group of one or more sensing entities), etc.
[0420] Operation 1(3001): The SF (3500) determines configuration information for sensing service. This might be triggered by the request / subscription in operation 0(3000) from the consumer(3600), operator's policies and / or SF(3500)'s internal logics. The configuration information related to sensing (service) may include any one or more of the following:
[0421] Any one or more of the information detailed in operation 0(3000).
[0422] The path of sensing data and associated information transfer / reporting, e.g. via CP (e.g. via RAN node(3200), AMF(3300); or RRC, NAS, LPP, etc.) and / or UP (e.g. via UPF(3400), or GTP-U tunnel, UP tunnel between UPF(3400) and SF(3500), etc.).
[0423] The SF(3500) may trigger sensing entity discovery and selection after receiving the sensing service request from the consumer(3600), after the sensing operation is triggered by SF(3500) or operator.
[0424] The SF(3500) may determine (or select, identify etc.) the one or more sensing entities (e.g. sensing entity #1(3100-1) , sensing entity #2 (3100-2) , …, sensing entity #n 3100-n), e.g. as sensing transmitter and / or sensing receivers, for the corresponding sensing service. This may be based on discovery results, the information in the sensing consumer(3600)'s request, SF(3500)'s internal logic, operator's policies and / or pre-configured information on the sensing entities, etc.
[0425] The SF(3500) may determine the sensing topology, e.g. the topology for one or more sensing services, such as including one or more sensing entities in the same or different locations / areas.
[0426] Determine the sensing operation or mode, e.g. mono-static, bi-statics, or multi-static sensing; NW-based or UE-based sensing.
[0427] Radio signals for sensing operation, e.g. the radio signals to transmit and / or to receive or measure, by sensing transmitters and / or sensing receivers.
[0428] For example, UL and / or DL reference signals, CRI-RS, SRS, beam management related signals, RRM related signals, and / or newly defined radio signals for sensing purposes (e.g. sensing reference signals).
[0429] Radio signals configuration, e.g. frequency (or periodicity) of radio signals to transmission and reception (or measurement), etc.
[0430] The characteristic(s) and / or parameter(s) (e.g. of the above radio signal) to be measured or recorded, by sensing transmitter (TX) and / or sensing receiver (RX) or at target / sensing object, e.g. one or more of the characteristics / parameters of the radio / sensing signals / data listed in the section above headedSensing related data / signals.
[0431] one or more of the above characteristics / parameters of indirect or direct path(s) for a target.
[0432] The quality, errors, accuracy and / or resolution of the above characteristics / parameters or signals, e.g. for the sensing signal measurement and / or transmission / generation.
[0433] For sensing data / signal / measurement / results reporting, and / or event triggered / periodic / configured time point(s) reporting.
[0434] The above information may be determined based on the information indicated in operation 0(3000) from the consumer(3600), operator's policies, and / or SF(3500)'s internal logics.
[0435] The sensing service / correlation ID might be allocated (e.g. by SF(3500) or sensing service consumer(3600)) to correlate the sensing entities, the sensing consumer(3600), sensing configuration, and other information related to sensing service. The correlation ID might be per sensing service.
[0436] Operation 2(3002): The SF(3500) may send the sensing configuration information or sensing request for sensing (which may include the configuration information) to the selected one or more sensing entities, relevant RAN node / TRP (Transmission and Reception Point) or UEs, UAVs, etc. For example, the SF(3500) sends the configuration information or sensing request to sensing entity #1 (3100-1), sensing entity #2, (3100-2), sensing entity #3 (3100-3), …, sensing entity #n (3100-n), e.g. via or facilitated by RAN node(3200), AMF(3300) and / or UPF(3400).
[0437] In various examples, the SF(3500) may include the sensing service or correlation ID (or, more generally, identification information) together with the sensing configuration information or within the sensing request. The one or more sensing entities may store the sensing service / correlation ID during the sensing process / operation, include the sensing service / correlation ID in sensing signal transmission, sensing data reporting, or any other procedures during the sensing process.
[0438] In various examples, the configuration information may be sent from SF(3500) directly to the relevant RAN node (3200) / TRP as sensing entities, e.g. using sensing protocol or NR Positioning Protocol A ( NRPPa) protocol (being a protocol to carry information between an NG-RAN node and an LMF, e.g. to receive positioning information, measurements and to configure a RAN for positioning purpose); or from SF(3500) to the relevant RAN node / TRP via one or more other core NFs (e.g. AMF(3300), UPF(3400), etc.); or from SF(3500) to the relevant RAN node / TRP via OAM.
[0439] In various examples, the configuration information may be sent from SF(3500) directly to the relevant UEs as sensing entities (e.g. assuming one or more of the sensing entities is / are UE(s)), e.g. via control plane (CP) or user plane (UP). For example, SF(3500) sends the information to AMF (3300), then gNB (3200), then UE (3100-1), via CP; or SF(3500) sends / expose the information to UPF(3400) then to the UE via UP.
[0440] In various examples, the configuration information might be sent to the RAN node / gNB / TRP that serves the sensing entities (e.g. UEs). The RAN node / gNB / TRP may generate and / or transmit and / or measure the signal of UEs. The UE(s) to be measured might be configured, e.g. by the SF(3500), or determined by the RAN node / gNB / TRP, or all UEs in the cell / service area / coverage area.
[0441] The SF(3500) may include the timing information (e.g. time window, or starting and / or ending time) for sensing operation, to the sensing entities and / or other relevant entities involved into the sensing. Then they may perform the sensing operation (e.g. generate, transmit, measure sensing signal / data, as configured) based on the timing information.
[0442] Operation 3(3003): (This operation is optional) If the SF(3500) does not trigger the sensing signal transmission and reception, sensing data collection and / or transfer (at sensing entities) in operation 2(3002), the SF(3500) may send sensing data collection and / or transfer request to corresponding sensing entities (e.g. sensing receivers), when needed.
[0443] Operation 4(3004): The selected one or more sensing entites (e.g. sensing receiver(s) and / or sensing transmitter(s)) behave as configured, e.g. for sensing signal transmission and reception. The sensing entities perform sensing data and / or sensing signal transmission, reception, measurement and / or storage, e.g. based on the information and configuration received in operation 2(3002) or the configuration received from the serving RAN node / cell / gNB (e.g. as part of operation 2(3002)).
[0444] Operation 5(3005a, 3005b or 3005c): The one or more sensing entities may transfer / report any one or more of the following sensing related information to network, SF(3500), serving RAN node, gNB and / or other sensing entities (e.g. other UEs, UAVs, TRPs, RAN node): the sensing data / measurement, other assistance / contextual information and / or sensing results. This may happen if said other sensing entity will determine (part of) the sensing results (e.g. the one or more sensing entities may transmit any of the sensing related information to the other sensing entity / entities if such other sensing entity / entities is to determine at least part of the sensing results).
[0445] The one or more sensing entities may include the sensing service / correlation ID in the sensing data and assistance information report.
[0446] The one or more sensing entities may determine to transfer the sensing related information when the data is ready, when the logged data reach the limit of its storage, based on the timing information in the data transfer / sensing service request and / or when the UP tunnel for data transfer is established, etc.
[0447] In various examples. the sensing related information may be transferred via CP and / or UP, e.g. based on configuration of SF(3500) / serving RAN node / network, sensing entity's internal logic, load / congestion of CP and / or UP tunnels, etc.
[0448] Operation 5a(3005a):The sensing related information may be transferred from the sensing entity (e.g. sensing entity #1 (3100-1), which may be UE, UAV, AGV) to the serving gNB / RAN node (e.g. via CP / RRC), then to AMF ( 3300); e.g. via N2 / NGAP interface), then to SG (e.g. via event exposure); or the serving gNB / RAN node transfers the information directly to SF(3500) (e.g. via sensing protocol between ran node and SF(3500) or NRPPa).
[0449] Operation 5b(3005b): The sensing related information might be transfer from the sensing entity (e.g. sensing entity #1 (3100-1), which may be UE, UAV, AGV) to UPF (via serving gNB / RAN node) via UP / user plane, then the UPF (3400) sends / exposure the sensing information to SF(3500) via UP tunnel / connection (between UPF(3400) and SF(3500)) or UPF event exposure.
[0450] UP tunnel / connection establishment / modification between sensing entity / UPF(3400) and SF(3500) may be required. The sensing information may be routed / transmitted to SF(3500) based on the (source and / or destination) IP addresses / FQDN (Fully Qualified Domain Name) of the data packets.
[0451] The gNB / RAN node may not able to interpret the sensing information.
[0452] Or the sensing entity might be gNB / TRP / RAN node (e.g. sensing entity #2 100b), it may send the sensing related information to UPF(3400) (e.g. via UP tunnel / GTP-U tunnel), then the UPF(3400) sends / exposure the sensing information to SF(3500) via UP tunnel / connection (between UPF(3400) and SF(3500)) or UPF(3400) event exposure.
[0453] Operation 5c(3005c): The sensing related information might be transfer from the sensing entity (e.g. sensing entity #2 100b, which may be gNB / TRP / RAN node) to AMF (e.g. via NGAP / N2 interface), then the AMF sends the information to SF(3500) (e.g. via AMF / sensing related event exposure); or the sensing entity transfers the information directly to SF(3500) (e.g. via sensing protocol between ran node and SF(3500) or NRPPa).
[0454] Operation 6(3006): The SF(3500) may determine sensing results based on the sensing data and, optionally, sensing assistance information that may be reported from sensing entities.
[0455] In various examples, the SF(3500) may aggregate the sensing data and, optionally, the sensing assistance information received from one or more sensing entities / receivers. In various examples, different weight may be applied to the sensing data (e.g. to different sensing data) and, optionally, the sensing assistance information from different sensing entities / receivers, e.g. based on one or more of sensing data accuracy, capability of sensing entities, amount of sensing data collected, etc.
[0456] The SF(3500) may also require sensing data and, optionally, sensing assistance information from other core NF(s) and / or OAM, or non-3GPP sensing related data / results (e.g. from 3rd parities / sensing consumer(3600)) for (joint) sensing results determination.
[0457] Operation 7(3007): (This operation is optional) The SF(3500) may send / exposure the sensing results and optional sensing contextual information to sensing service consumer ( 3600), e.g. based on the request in operation 0(3000) (if any).
[0458] Note that, although some operations are explicitly identified as optional above, this should not be taken to mean that steps not explicitly identified as optional are mandatory. It will be appreciated that, depending on a focus of an example of the present disclosure, various operations (not explicitly indicated as optional) may be omitted.
[0459] According to examples of the present disclosure, there is provided an entity (e.g. sensing function) in a wireless communication network. The entity is configured to; obtain (e.g. generate, create, determine, receive) configuration information for a sensing service (or sensing operation); transmit the configuration information to one or more sensing entity (optionally, via one or more network entity such as RAN node(3200), AMF(3300) or UPF(3400)); and receive, from the one or more entity, sensing data obtained based on the configuration information.
[0460] In further examples, the configuration information may include or be included in a request for (or to perform) the sensing service. The request may trigger the one or more sensing entities, upon receiving it, to perform a sensing operation, sensing data collection and / or sensing data transmission.
[0461] In further examples, the one or more sensing entities may be selected by the entity as part of generating the configuration information or based on information from a sensing consumer(3600), where the information from the sensing consumer(3600) may indicate, to the entity, a need to obtain the configuration information and / or to perform / facilitate the sensing service.
[0462] In further examples, the entity may act or operate according to any feature or operation described above in relation to the SF(3500) of Figure 3. For example, the configuration information may include any one or more of the information or features indicated in relation to operation 1(3001) of Figure 3 above. For example, the configuration information may be sent by the entity according to any of the features or details described above in relation to operation 2(3002) of Figure 3.
[0463] Sensing related events
[0464] Table 6 - List of events related to sensing monitoring, measurement, detectionEventDetection criteriaWhich NF / (sensing) entity detects the eventDetection of sensing object(s)Target sensing object(s) / target(s) / hazard(s) is detected, e.g. by network or UEs. The sensing object(s) might be one or more objects.The sensing object(s) might be specific objects type, e.g. indicated by the service consumer, operator's configuration / policy, or the determination of sensing function or sensing entities. E.g. the sensing object(s) / target might be humans, animal, Automated Guided Vehicles (AGV), UAV, etc. are detected.The core NF(s) that host the sensing function / functionality, e.g. for sensing results determination and / or exposure. E.g. SF, AMF, etc.Sensing entity, e.g. sensing transmitter and / or sensing receiver; UE and / or RAN node.
[0465] Table 6 above provides an example of an event, examples of corresponding detection criteria (any one of more of which may be employed for the event), and examples of which NF (or sensing entity) may detect the event.
[0466] The event might be detected by the sensing entities, e.g. UE, then it is reported to RAN nodes, core NF related to sensing (e.g. SF), other sensing entities (e.g. UEs). If the UE detected the sensing event was trigger, the UE may report the results to the 3rd party / sensing service consumer, e.g. via RAN node and / or core network (e.g. via CP or UP), or over the top / via application layer.
[0467] The event might be detected by the sensing entities, e.g. the RAN node, then it is report to the core NF related to sensing (e.g. SF) and informed to the other sensing entities, e.g. UEs and / or other Ran node(s).
[0468] The event might be detected by the core NF that hosts the sensing logic functions, e.g. SF; then it is reported / exposed to the 3rd party / sensing service consumer, informed to sensing entities (e.g. one or more RAN nodes, UEs, etc.), or other SFs (e.g. in the same or different PLMNs), e.g. via SF event exposure service operations.
[0469] Figure 4 is a block diagram of an exemplary apparatus, or network entity, that may be used in examples of the present disclosure. The skilled person will appreciate said entity 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.
[0470] The entity 4000 comprises a processor (or controller) 4100, a transmitter 4300 and a receiver 4200. The receiver 4200 is configured for receiving one or more messages from one or more other network entities, for example as described above. The transmitter 4300 is configured for transmitting one or more messages to one or more other network entities, for example as described above. The processor 4100 is configured for performing one or more operations, for example according to the operations as described above. It will be appreciated that an entity as described herein may be a virtual or logical entity, which may be implemented using or in an apparatus which comprises a processor, an antenna, a receiver and / or a transmitter etc. but which does not itself have a physical form (i.e. would not be said to comprise a processor, an antenna, a receiver and / or a transmitter etc.).
[0471] Figure 5A and Figure 5B is illustrates a method of sensing data and associated information collection and transport according to various examples of the present disclosure.
[0472] It will be understood that various examples of the present disclosure may include only part of the process shown in Figure 5A and Figure 5B. For example, various examples focus on the establishment of the connection (e.g. omitting operation 5(step 5005) onwards), various examples focus on the information collection part (e.g. omitting operations 0(step 5000)-4(step 5004) and 7(step 5007) onwards), various examples focus on the transport part (e.g. omitting operations 0(step 5000)-6(step 5006)), and various examples consider any combination of the different parts and, more generally, the different operations in Figure 5A and Figure 5B as a whole.
[0473] It is to be understood that the various entities shown in Figure 5A and Figure 5B may instead be referred to as numbered entities, i.e. first entity, second entity, third entity etc., in place of the specific terms used in Figure 5A and Figure 5B.
[0474] The steps of Figure 5A and Figure 5B may be described as follows:
[0475] In step 5000, a sensing service consumer(5600) may send sensing service request to SSF (optionally, via NEF).
[0476] In the sensing service request, the sensing service consumer(5600) may include one or more of: AOI (area of interest) or target sensing area, required accuracy level and latency of sensing results, required detection probability and false alarm probability of sensing results, candidate list of sensing entities (if available), sensing objects and other assistance information that might be helpful for SSF to determine sensing service configuration or sensing results.
[0477] In various examples, the sensing service request includes one or more of any of the information described in relation to Operation 0 of Figure 3.
[0478] In step 5001, based on service consumer(5600)'s request, SSF(5500) may determine to trigger sensing related procedures within 5GS. The SSF(5500) may determine the configuration and control information for the corresponding sensing service. The SSF(5500) may coordinate with other NFs and / or OAM to determine the configuration and / or control information. The SSF(5500) may determine to trigger data collection towards selected sensing entities ( / entity). For example, the SSF(5500) may determine configuration information for a sensing entity(5100-n), to be provided to the sensing entity(5100-n).
[0479] The SSF(5500) may determine (or select, identify etc.) the one or more sensing entities (e.g. sensing entity #1(5100-1) , sensing entity #2 (5100-2) , …, sensing entity #n 5100-n), e.g. as sensing transmitter and / or sensing receivers, for the corresponding sensing service. This may be based on discovery results, the information in the sensing consumer(5600)'s request, SSF(5500)'s internal logic, operator's policies and / or pre-configured information on the sensing entities, etc. In various examples, determining the configuration information is performed according to any of the examples described in relation to Operation 1(3001) of Figure 3, e.g. the configuration information may include any of the information or features indicated in the description of Operation 1(3001) of Fig. 3.
[0480] The SSF(5500) may also determine to trigger direct connection for sensing data transfer towards selected sensing entities, if there is no direct connection between SSF(5500) and those sensing entities. If direct connection between SSF and the select sensing entity is available, step 5002-5004 can be skipped. In various examples, if a direct connection already exists between the SSF(5500) and one or more of the selected sensing entities, then the SSF(5500) may trigger establishment of a direct connection with any remaining ones of the selected sensing entities (i.e. those not already having a direction connection with the SSF(5500)). The SSF(5500) may also modify the existing direct connection with sensing entities / entity, to support the corresponding sensing service.
[0481] In various examples, the SSF(5500) triggers sensing related procedures of its own volition.
[0482] In step 5002, the SSF(5500) may send direct connection establishment request(s) to the selected sensing entities via AMF(5300). The SSF(5500) may also trigger sensing data collection in parallel or at any stage after step 1. For example, the direct connection establishment request may include an indication or request to collect sensing data, or an indication or request to collect sensing data may be sent separately to a sensing entity(5100-n) concurrently with performing a procedure to establish a direct connection with said sensing entity(5100-n) (e.g. sending a request to establish a direct connection to said sensing entity(5100-n)).
[0483] The SSF(5500) may perform AMF(5300) discovery (e.g. from NRF) and selection based on one or more (or all) of AMF(5300) service area, AMF(5300) capability (e.g. whether the AMF(5300) is enabled to support sensing related procedures, establishment of direct connection between SSF(5500) and sensing entity(5100-n), etc.), sensing service area, sensing objects (e.g. list of UE IDs, SUPI, GPSI) or candidate sensing entity list (if given, e.g. list of gNB IDs), etc.
[0484] The selected AMF(5300) may select list of sensing entities and / or provide the list of sensing entities to SSF(5500), based on SSF(5500) request. The AMF(5300) may select the list of sensing entities based on the information indicated by SSF(5500), the retrieved RAN node information from other NFs or OAM, etc. The SSF may determine the final list of selected sensing entities based on the list of sensing entities provided by AMF(5300).
[0485] The procedure of SSF(5500) selecting AMF(5300) and / or AMF(5300) selecting (candidate) sensing entity(5100-n) may occur after step 5001, before direct connection establishment is triggered. Then in step 5002, the SSF(5500) may send the request to the selected AMF(s) (5300). The AMF(s) (5300) may forward the request to the selected sensing entities. The selected sensing entities might be determined by SSF(5500) and / or indicated by SSF(5500) to AMF(5300), or based on AMF(5300)'s local knowledge after it has performed sensing entity selection procedure.
[0486] For example, in a sub-step 5002-1 (e.g. as part of step 5002, being an overall step of the SSF(5500) sending direct connection establishment request(s) to selected sensing entity / entities), SSF(5500) sends direct connection establishment request to AMF(5300), e.g. by invoking Namf_communication_N1N2MessageTransfer or other service operation. The SSF(5500) may include IP address / FQDN of the SSF(5500) to indicate the sensing data transfer via direct connection in N2 container. The IP address / FQDN of the SSF(5500) is the destination of sensing data transfer. The IP address / FQDN of the SSF(5500) can be replaced by any type of information that can represent the SSF(5500) information being the destination of sensing entity data and / or information transfer. The SSF(5500) may also include binding information (e.g. sensing service ID, sensing event ID, sensing function / SSF(5500) (instance) ID, ID allocated for binding, etc.) to associate the direct connection and / or the sensing entity to the corresponding sensing service or SSF(5500). In a sub-step 5002-2 (e.g. as another part of step 5002), based on in the information indicated by SSF(5500), the AMF(5300) may forward the direct connection establishment request to sensing entities via N2 message.
[0487] In step 5003, upon receiving the direct connection establishment request, each sensing entity may establish direct connection between said sensing entity (i.e. itself) and SSF(5500), e.g. based on the received IP address / FQDN or any other address or ID related information of SSF(5500). The sensing entity may also associate the direct connection to the corresponding SSF(5500) or sensing service using the received binding information (if sent by the SSF(5500)).
[0488] In step 5004, sensing entities may send acknowledgement to SSF(5500) via AMF(5300) to indicate the successful establishment of direct connection for sensing data and information transfer. For example, the sensing entities may indicate to the SSF(5500) that the direct connection is established. In various examples, instead of separately indicating that the direct connection is established, and if the SSF(5500) triggered sensing collection in step 5002, then a sensing entity may implicitly indicate that the direct connection is established by reporting / sending sensing data to the SSF(5500). For example, by transmitting collected sensing data or information to the SSF(5500), the SSF(5500) will implicitly be informed that the direct connection is established.
[0489] In a sub-step 5004-1 (e.g. as part of step 5004, being an overall step of sensing entities indicating successful establishment of the direct connection), a or each sensing entity sends acknowledgement to AMF(5300) via N2 message. In a sub-step 5004-2 (e.g. as another part of step 5004), the AMF(5300) forwards the acknowledgement to SSF(5500), e.g. via Namf_Communication_N2InfoNotify or other service operation.
[0490] In step 5005, if SSF(5500) does not trigger sensing collection in step 5002, the SSF may determine to trigger sensing data collection towards sensing entities in this step. The SSF(5500) may also indicate the determined configuration and control information for the corresponding sensing service to sensing entities. For example, the SSF(5500) may transmit the determined configuration information to a sensing entity or the sensing entities. Sensing data collection request maybe sent via direct connection, if established. Alternatively, the SSF(5500) may send the Sensing data collection request via CP through AMF(5300); then the AMF(5300) forwards the request to sensing entity.
[0491] In various examples, step 5005 is omitted or is optional. For example, if steps 5002-5004 are skipped due to there already being direct connection available between the SSF(5500) and the selected sensing entities, then step 5005 is performed. In another example, if sensing data collection is not triggered in parallel with sending direct connection establishment requests in step 5002, then step 5005 is performed.
[0492] In step 5006, the sensing entities perform sensing data collection, as configured by SSF(5500). For example, a sensing entity performed sensing data collection based on the configuration information received from the SSF(5500).
[0493] In step 5007, the SSF(5500) may request the sensing entity to report sensing data and information. For example, the SSF(5500) may transmit a request to each sensing entity to report sensing results, e.g. sensing data and / or sending information. The SSF(5500) may also indicate (e.g. via an indication included in the request or sent in parallel with the request) whether the sensing entity is required to (pre-)process the collected sensing data or not. (Pre-)Processing of collected sensing data may include one or more of derive part / intermediate sensing results, filter out necessary data, report certain amount of data volume, or report data collected within certain time window, etc.
[0494] In various examples, step 5007 is omitted or is optional. For example, the sensing entity / entities may be configured to report sensing data (or sensing information) without this needing to be triggered or prompted separately by the SSF(5500). For example, the configuration information (or control information, or configuration and control information) sent to the sensing entity by the SSF(5500) may indicate that sensing data is to be reported to the SSF(5500). This reporting may be configured for a specific time, periodically, or upon condition(s) being met or event(s) being triggered. In various examples, if sensing data collection is triggered in step 5002, then step 5007 is omitted and the sensing entities will report collected sensing data or information to the SSF(5500), e.g. based on the configuration information.
[0495] In step 5008, sensing entities report the collected sensing data and associated information to SSF(5500) via direct connection. This may be in response to the request in step 5007, or may be based on the configuration information or control information from the SSF.
[0496] Sensing entities may transfer sensing data based on explicit data transfer request from SSF(5500) in step 5007, periodically (e.g. based on the periodicity configured by SSF(5500)), or other criteria (e.g. event triggered, data collection reaches a certain volume, etc.).
[0497] In steps 5009-5010, SSF(5500) determines sensing results based on the sensing data and optional the sensing assistance information reported from sensing entities. The SSF may notify the sensing results to sensing service consumer(5600), e.g. in response to the request in step 5000.
[0498] Figure 6 is a procedure of Sensing Data and the Associated Information Collection and Transport.
[0499] In step 6000, sensing service consumer (6600) may send sensing service request to SSF.
[0500] The consumer(6600) may include the following information in the sensing service request: AOI and time window of the required sensing service, sensing objects (e.g. human, animals, etc.), sensing detection events (e.g. moving objects, new hazards, etc.), required accuracy level of sensing results, required detection probability and false alarm probability of sensing results, metrics for sensing performance evaluation, candidate list of sensing entities (if available) and other assistance information that is helpful for SSF(6500) to determine sensing configuration or sensing results.
[0501] In step 6001. SSF(6500) determines to the configuration and control information for a sensing service. This might be triggered by the request received in step 6000 from the consumer(6600), operator's policies, or SSF (6500) internal logics.
[0502] SSF(6500) may determine the sensing operation for the corresponding service (e.g. mono-static or bi-statics), one or more sensing entities (e.g. sensing entity #1(6100-1), sensing entity #2 (6100-2), …, sensing entity #n (6100-n)), configuration of the radio signals for sensing purposes, path of sensing data transfer (e.g. via CP or UP), etc. Sensing entities(6100-n) selection is addressed in KI#3. The configuration of the radio signals for sensing purposes may require coordination with RAN WGs.
[0503] In step 6002, The SSF(6500) sends the sensing configuration and control information to the selected sensing entities(6100-n). The SSF(6500) may also include a sensing service correlation ID.
[0504] In step 6003, if the SSF(6500) does not trigger the sensing signal transmission and reception at sensing entities(6100-n) at this step 6002, it may send sensing data collection and / or transfer request to sensing entities(6100-n), when needed.
[0505] In step 6004, The selected sensing receivers and sensing transmitters behave as configured. The sensing receivers perform sensing data collection based on configuration.
[0506] In step 6005, The sensing entities(6100-n) report the collected sensing data to SSF(6500) for sensing results calculation. The sensing entities(6100-n) may include the sensing service correlation ID in the report.
[0507] A sensing entity (e.g. a UE(6100-1)) may report the sensing data via user plane and / or control to the SSF(6500).
[0508] A sensing entity (e.g. a gNB(6100-2)) may report sensing data to SSF(6500) directly (e.g. based on sensing protocol) or via AMF(6300). The detailed procedure of sensing data transfer via user plane is FFS. It is FFS whether sensing protocol for data transfer between gNB(6100-2) and SSF(6500) is needed or not.
[0509] In step 6006, The SSF(6500) determines sensing results based on the sensing data and optional the sensing assistance information reported from sensing entities.
[0510] The SSF(6500) may apply different weights to the sensing data reported from different sensing entities(6100-n) when deriving the sensing result to achieve the required accuracy level.
[0511] The SSF(6500) may apply perform sensing entity SE selection again to select new sensing entities if the sensing result does not satisfy the service requirements in the Service Request.
[0512] In step 6007, the SSF(6500) may notify the sensing results and other associated information (if any) to sensing service consumer(6600).
[0513] The procedure of Figure 6 provides the end-to-end solution for KI#4 Sensing Data and the Associated Information Collection and Transport.
[0514] Sensing data and associated information needs to be collected by sensing entities and transported to SSF (Sensing Service Function) to support sensing results calculation. The procedure provides general solution for sensing data transmission to cover different sensing operations by assuming that the sensing entities (receivers) could be UEs and / or gNBs. When the sensing entity is a UE, it may transfer sensing data to SSF via CP and / or UP, based on SSF configuration. When the sensing entity is a gNB, the gNB may report sensing data to SSF directly (e.g. based on sensing protocol) or transfer sensing data to SSF via AMF.
[0515] Figure 7A and Figure 7B is a procedure of Sensing Data and the Associated Information Collection and Transport
[0516] In step 7000, a sensing service consumer(7600) may send sensing service request to SSF(7500) (via NEF).
[0517] In the sensing service request, the sensing service consumer(7600) may include: AOI or target sensing area, required accuracy level and latency of sensing results, required detection probability and false alarm probability of sensing results, candidate list of sensing entities (if available), sensing objects and other assistance information that might be helpful for SSF to determine sensing service configuration or sensing results.
[0518] In step 7001, based on service consumer(7600)'s request, SSF(7500) may determine to trigger sensing related procedures within 5GS.
[0519] The SSF(7500) may determine the configuration and control information for the corresponding sensing service.
[0520] The SSF(7500) may determine to trigger data collection towards selected one or more sensing entities (e.g. sensing entity #1(7100-1), sensing entity #2 (7100-2), …, sensing entity #n (7100-n)). Sensing entity discovery and selection is addressed in KI#3.
[0521] The SSF(7500) may also determine to trigger direct connection for sensing data transfer towards selected sensing entities, if there is no direct connection between SSF(7500) and those sensing entities. If direct connection between SSF(7500) and the select sensing entity is available, step 7002-7004 can be skipped.
[0522] In step 7002, The SSF(7500) may send direct connection establishment request to the selected sensing entities via AMF(7300). The SSF may also trigger sensing data collection in parallel.
[0523] The SSF(7500) may perform AMF(7300) discovery and selection based on AMF(7300) service area, AMF(7300) capability, sensing service area, sensing objects or candidate sensing entity list (if given), etc.
[0524] In step 7002-1, The SSF(7500) sends direct connection establishment request to AMF(7300), e.g. by invoking Namf_communication_N1N2MessageTransfer or other service operation. The SSF(7500) may include IP address / FQDN of the SSF(7500) to indicate the sensing data transfer via direct connection in N2 container. The IP address / FQDN of the SSF(7500) is the destination of sensing data transfer. The SSF(7500) may also include binding information (e.g. sensing service ID, sensing event ID, etc.) to associate the direct connection to the corresponding sensing service or SSF(7500).
[0525] In step 7002-2, based on in the information indicated by SSF(7500), the AMF(7300) may forward the direct connection establishment request to sensing entities via N2 message. The N2 message between AMF(7300) and NG-RAN is in RAN3 scope.
[0526] In step 7003, upon receiving the direct connection establishment request, each sensing entities establish direct connection between sensing entity and SSF(7500), e.g. based on the received IP address / FQDN information of SSF(7500). The sensing entity maybe also associated the direct connection to the corresponding SSF(7500) or sensing service using the received binding information.
[0527] Editor's Note: it is FFS which protocol (e.g. sensing protocol, NRPPa, etc.) for data transfer between gNB and SFF will be used.
[0528] In step 7004, sensing entities may send acknowledgement to SSF(7500) via AMF(7300) to indicate the successful establishment of direct connection for sensing data and information transfer.
[0529] In step 7004-1, sensing entity sends acknowledgement to AMF(7300) via N2 message.
[0530] In step 7004-2, the AMF(7300) forwards the acknowledgement to SSF(7500), e.g. via Namf_Communication_N2InfoNotify or other service operation.
[0531] In step 7005, if SSF(7500) does not trigger sensing collection in step 7002, the SFF may determine to trigger sensing data collection towards sensing entities in this step. The SSF(7500) may also indicate the determined configuration and control information for the corresponding sensing service to sensing entities.
[0532] Sensing data collection request maybe sent via direct connection, if established. Alternatively, the SSF(7500) may send the sensing data collection request via CP through AMF(7300); then the AMF(7300) forwards the request to sensing entity.
[0533] In step 7006, sensing entities perform sensing data collection, as configured by SSF.
[0534] In step 7007, the SSF(7500) may request the sensing entity to report sensing data and information.
[0535] In step 7008, sensing entities report the collected sensing data and associated information to SSF(7500) via direct connection.
[0536] Sensing entities may transfer sensing data based on explicit data transfer request from SSF (7500) in step 7007, periodically (e.g. based on the periodicity configured by SSF(7500)), or other criteria (e.g. event triggered, data collection reaches a certain volume, etc.).
[0537] In step 7009 - 7010, SSF(7500) determines sensing results based on the sensing data and optional the sensing assistance information reported from sensing entities. The SSF(7500) may notify the sensing results to sensing service consumer(7600) as request in step 7000. Sensing Result Exposure is discussed under KI#5.
[0538] The procedure provides the end-to-end solution for KI#4 Sensing Data and the Associated Information Collection and Transport to support gNB-based monostatic sensing scenarios. Sensing data and / or associated information needs to be collected by sensing entities and transported to SSF (Sensing Service Function) to support sensing results calculation. In this solution, the sensing entities / gNBs may collect sensing data and report the corresponding sensing data to SSF, based on SSF request. The sensing data might be transferred directly (e.g. based on sensing protocol) from sensing entities to SSF. To transfer the sensing data, direct connections between SSF and each sensing entities are established.
[0539] Figure 8 is a flow diagram illustrating a method of a sensing function according to an example of the disclosure.
[0540] In S8010, the sensing function, based on a sensing service request, selects at least one sensing entity.
[0541] In S8020, the sensing function transmits, to the at least one sensing entity, a sensing request including configuration information for sensing.
[0542] In S8030, the sensing function receives, from the at least one sensing entity, sensing data.
[0543] In S8040, the sensing function processes the received sensing data.
[0544] Figure 9 is a flow diagram illustrating a method of a sensing entity according to an example of the disclosure.
[0545] In S9010, the sensing entity receives, from a sensing function, a sensing request including configuration information for sensing
[0546] In S9020, the sensing entity performs data sensing based on the configuration information.
[0547] In S9030, the sensing entity, based on the sensing request, transmits, to the sensing function, sensing data obtained at least in part from the data sensing.
[0548] The solution is based on the following principles to support sensing data and information collection and transport:
[0549] Based on request from sensing service consumer, sensing function (SSF) determines the configuration information of the corresponding services and trigger sensing data collection and transfer towards selected sensing entities.
[0550] SSF triggers direct connection establishment towards sensing entity via AMF for sensing data transfer.
[0551] Based on the sensing data collection and / or sensing data transfer request from SSF, the sensing entities collect sensing data and transfer the sensing data to SSF via direct connection as configured.
[0552] Throughout this disclosure, the terms 'sensing function (SF)' and 'sensing service function (SSF)' may be used interchangeably to refer to a network function that supports sensing services in a wireless communication network.
[0553] According to an embodiment, there is provided a computer-readable storage medium comprising instructions which, when executed by at least one processor of an electronic device, cause the electronic device to perform a method according to any one or more of the embodiments, examples etc. described herein.
[0554] 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. For example, referring to the method shown by the call flow diagram of any of the figures, it will be understood that one or more of the operations of these methods may be omitted. Additionally, one or more features or operations from any example / embodiment may be combined with features or operations from any other example / embodiment. In particular, regardless of whether or not a pointer towards a combination of features / examples is found herein, the present disclosure should be considered to include all combinations of two or more of the embodiments, examples etc. disclosed herein, and all combinations of two or more of the features disclosed herein.
[0555] 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.
[0556] 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.
[0557] 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.
[0558] While the present disclosure has been shown, illustrated 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.
[0559] 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.
[0560] Various features and examples of the present disclosure are described in the Annex below
[0561] Various examples of the disclosure are provided by the following numbered Clauses:
Claims
1.A method of a sensing function in a wireless communication network, the method comprising:based on a sensing service request, selecting at least one sensing entity, wherein the sensing service request is triggered from a sensing service consumer and is initiated towards the sensing function;transmitting, to the at least one sensing entity, a sensing request including configuration information for sensing;receiving, from the at least one sensing entity, sensing data; andprocessing the received sensing data.2.The method of claim 1, wherein the sensing service request is received from a sensing service consumer; andwherein processing the received sensing data comprises:transmitting a sensing result including the sensing data to the sensing service consumer, ordetermining sensing results based on the sensing data, and transmitting the sensing results to the sensing service consumer.3.The method of claim 1, wherein the method comprises:discovering at least one candidate sensing entity; andselecting the at least one sensing entity from among the at least one candidate sensing entity.4.The method of claim 1, wherein the sensing request is transmitted or the sensing data is received over a direct connection established between each sensing entity and the sensing function.5.The method of claim 4, wherein the method comprises:transmitting, to one or more of the at least one sensing entity, a request for establishing the direct connection; andreceiving, from the one or more sensing entity, an indication that the direct connection has been established, wherein the request for establishing the direct connection comprises connection information of the sensing function, wherein the connection information includes one or more of:information indicating a destination of the sensing data, an IP address of the sensing function, or a fully qualified domain name (FQDN) of the sensing function.6.The method of claim 1, wherein the sensing request includes information on reporting the sensing data, wherein the information on reporting the sensing data comprises one or more of:a time to report the sensing data,a periodicity for reporting the sensing data,an event according to which the sensing data is to be reported, orone or more criteria for reporting the sensing data.7.The method of claim 1, wherein the sensing service request comprises one or more of:area of interest (AOI) or target sensing area, orone or more sensing objects.8.A method of a sensing entity in a wireless communication network, the method comprising:receiving, from a sensing function, a sensing request including configuration information for sensing;performing data sensing based on the configuration information; andbased on the sensing request, transmitting, to the sensing function, sensing data obtained at least in part from the data sensing.9.The method of claim 8, wherein the sensing request is received or the sensing data is transmitted over a direct connection established between the sensing entity and the sensing function.10.The method of claim 9, wherein the method comprises:receiving, from the sensing function, a request for establishing the direct connection; andestablishing the direct connection based on the request for establishing the direct connection, wherein the request for establishing the direct connection comprises connection information of the sensing function, wherein the connection information includes one or more of:information indicating a destination of the sensing data, an IP address of the sensing function, or a fully qualified domain name (FQDN) of the sensing function.11.The method of claim 8, wherein the sensing request includes information on reporting the sensing data, wherein the information on reporting the sensing data comprises one or more of:a time to report the sensing data,a periodicity for reporting the sensing data,an event according to which the sensing data is to be reported, orone or more criteria for reporting the sensing data.12.The method of claim 11, wherein the performing of the data sensing or the transmitting of the sensing data is based on the information on reporting the sensing data.13.The method of claim 8, wherein the method comprises processing results of the data sensing to obtain the sensing data.14.One or more entity configured to operate as a sensing function in a wireless communication network, the one or more entity configured to:based on a sensing service request, select at least one sensing entity, wherein the sensing service request is triggered from a sensing service consumer and is initiated towards the sensing function via a sensing related NF;transmit, to the at least one sensing entity, a sensing request including configuration information for sensing;receive, from the at least one sensing entity, sensing data; andprocess the received sensing data.15.One or more entity configured to operate as a sensing entity in a wireless communication network, the one or more entity configured to:receive, from a sensing function, a sensing request including configuration information for sensing;perform data sensing based on the configuration information; andbased on the sensing request, transmit, to the sensing function, sensing data obtained at least in part from the data sensing.
