Sensing signal configuration and sensing data reporting for wireless sensing in integrated sensing and communications system
By defining Sensing Report Units and configuring sensing signals with grids, the challenges of efficient sensing data reporting and configuration in integrated sensing and communications systems are addressed, enhancing target detection and tracking in B5G/6G systems.
Patent Information
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- MEDIATEK SINGAPORE PTE LTD
- Filing Date
- 2025-01-03
- Publication Date
- 2026-07-09
AI Technical Summary
Existing systems face challenges in efficiently configuring sensing signals and reporting sensing data in integrated sensing and communications systems, particularly in B5G/6G systems, where sensing devices need to report data to a Sensing Function (SF) or Base Station (BS) and configure sensing signals to BS or User Equipment (UE).
The proposed solution involves defining Sensing Report Units (SRUs) as basic reporting units, with specific quantities and IDs, and configuring sensing signals and reporting data through grids of varying dimensions, allowing for differentiated target tracking and resource allocation.
This approach enables efficient sensing data reporting and configuration, reducing latency and improving target detection and tracking performance by allowing precise resource management and processing.
Smart Images

Figure CN2025070389_09072026_PF_FP_ABST
Abstract
Description
SENSING SIGNAL CONFIGURATION AND SENSING DATA REPORTING FOR WIRELESS SENSING IN INTEGRATED SENSING AND COMMUNICATIONS SYSTEMTECHNICAL FIELD
[0001] The present disclosure relates to integrated sensing and communications (ISAC) , and particularly relates to sensing sensing signal configuration and sensing data reporting.BACKGROUND
[0002] The background description provided herein is for the purpose of generally presenting the context of the disclosure. Work of the presently named inventors, to the extent the work is described in this background section, as well as aspects of the description that may not otherwise qualify as prior art at the time of filing, are neither expressly nor impliedly admitted as prior art against the present disclosure.
[0003] The B5G / 6G system is envisioned to achieve radar sensing. If a sensing device, for example BS and UE, supports sensing capability, it may need to report sensing data to Sensing Function (SF) or BS. Besides, (SF) or BS needs to configure sensing signal to BS or UE.SUMMARY
[0004] We propose the sensing data reporting contents and reporting ways.
[0005] We propose the sensing signal configuration contents and configuration ways.BRIEF DESCRIPTION OF THE DRAWINGS
[0006] Various embodiments of this disclosure that are proposed as examples will be described in detail with reference to the following figures, wherein like numerals reference like elements, and wherein:
[0007] Fig. 1 shows two examples of the definition of ‘grid’ ;
[0008] Fig. 2 shows an example of the definition of grid of size;
[0009] Fig. 3 shows two examples of total power of SRU;
[0010] Fig. 4 shows an example of the calculation of average power of noise and clutter;
[0011] Fig. 5 shows an example of the relationship of SRU ID reporting and configuration;
[0012] Fig. 6 shows an example of the procedure of SRU ID reporting and configurations;
[0013] Fig. 7 shows an exemplary block diagram of a user equipment (UE) according to an embodiment of the disclosure.DETAILED DESCRIPTION OF EMBODIMENTS
[0014] Sensing Report Unit (SRU) is defined as the basic reporting unit which corresponds to a target or part of a target. It includes quantities of multiple domains (target ID, delay, doppler, angle, resource ID, power, degree of confidence) . All quantities are summarized in the following table.
[0015] It should be noted that we take baseline quantities as the 1st option, extended quantities as other options. In the following, these quantities are explained one by one.
[0016] Format of SRU: SRU #n: {target ID, delay, doppler, angle (AoD, ZoD, AoA, ZoA) , resource ID (cell ID, resource set / resource ID) , power, degree of confidence} . Regarding as the reporting value, absolute values can be directly reported (option 1) . Reporting relative values is another option, such as taking one SRU as the reference, the other SRUs report the difference between the reference SRU, for each quantity.
[0017] As mentioned above, there may be multiple SRUs reported. So how to differentiate of SRU? If sensing data can be distinguished through quantities of four domains, it is reported as an independent SRU. The four domains include delay, doppler, angle and resource (cell ID, resource set / resource ID) . In this way, the SRUs may correspond to different targets or multiple parts of the same target, or to different measurement results of the same target using different sensing resources (e.g., from different BSs or different Tx beams) . It should be noted that this means the Rx receiver may not perform target clustering operation.
[0018] Total number of SRUs = target number *part number of one target *Tx node number *Tx beam number of one Tx node
[0019] What is SRU ID? It is used to differentiate SRUs, so that the BS / SF and UE can control the subsequent sensing operations of different SRUs (or targets) respectively, including sensing resource allocation and Rx side signal reception and signal processing. There are two options for reporting, option 1, SRU ID can be implicit in the order of reported SRU; option 2, SRU ID can be explicit expressed by an integer.
[0020] What is ‘grid’ ? ‘Grid’ is defined as the granularity of sensing report data including delay, doppler, angle (AoD, ZoD, AoA, ZoA) , etc. Grid can be one dimension or multiple dimensions according to the reporting data, e.g., one domain {delay} , two domains {delay, doppler} , six domains {delay, doppler, AoD, ZoD, AoA, ZoA} . Fig. 1 shows two examples of the definition of ‘grid’ , one dimension and two dimensions.
[0021] What is ‘Size of grid’ ? It is the size of grid in each domain. Size of grid shall be separately defined for each domain of sensing report data. For example, size of grid for [delay, doppler, AoD, ZoD, AoA, ZoA] is [s1 m, s2 m / s, s3 rad, s4 rad, s5 rad, s6 rad] respectively.
[0022] It is unnecessary to set up a special relationship between size of grid and the resolution which sensing Tx / Rx and sensing signal can achieve. That is, size of grid can be larger than, smaller than or equal to resolution. For example, sensing resolution may be larger than the size of grid due to the limitation of Tx / Rx nodes capability and sensing signal capability.
[0023] There are two options to decide the size of grid. Option 1, size of grid can be decided by Rx itself and reported to SF / BS along with sensing data. Option 2, default value (clearly stated in spec) can be used as size of grid. The default value can be set based on the resolution of usual Tx / Rx configurations (e.g., antenna aperture) and sensing signal configurations (e.g., BW, CPI) , and calculate the size of grid according to the equation in the table (take mono-static sensing as an example) of Fig. 2. An example of size of grid is also given in Fig. 2
[0024] Size of grid can also be defined in the following ways. Option 3, size of grid can be directly configured by SF / BS; or BW, CPI and Tx / Rx antenna aperture are configured, which are then used to calculate size of grid. Option 4, size of grid can be calculated based on the configurations of currently used Tx and Rx antenna and sensing signal.
[0025] Regarding as the reporting quantities of delay, doppler and angle domains, the measurement result of each domain is quantized with the size of grid as the granularity. The quantized result is reported to BS / SF. For example, measurement result of delay, doppler, AoD, ZoD, AoA, ZoA = [3.1m, 1.2m / s, 0.2, 0.2, 0.3, 0.4] , size of grid = [1.5m, 0.5m / s, 0.1772, 0.0886, 0.1772, 0.0886] , reporting data = [2, 2, 1, 2, 2, 5] .
[0026] As for reporting quantities of power domain, total power of SRU can be defined as total power of SRU = average power of SRU *size of SRU.
[0027] (1) average power of SRU, it’s the average power of SRU in the size of grid. Since grid can be one dimension or multiple dimensions, the average power is the average of all dimensions.
[0028] (2) size of SRU: it’s the number of grid. If grid is multiple dimensions, the size of SRU is product of the size of each dimension. It is used to express the size of target or size of part of target. The reported value may be decimal number (smaller than 1) when sensing resolution is smaller than size of grid. Rx node can report the total power of SRU, or separately report average power of SRU and size of SRU to SF / BS.
[0029] For example, grid is one dimension: size of grid = 1.5m, size of SRU = 2, average power of SRU = -90dBm, total power of SRU = -87dBm.
[0030] Another example, grid is two dimensions: size of grid = [1.5m, 0.5m / s] , size of SRU = 2, average power of SRU = -90dB, total power of SRU = -87dBm.
[0031] Fig. 3 shows two examples of the definition of total power of SRU.
[0032] Reporting data of average power of clutter and noise, this quantity includes clutter (static and dynamic) and noise which cannot be eliminated by Rx processing. It degrades the performance of target detection and identification. Assume that the distribution of all locations within the detection range (in delay, doppler, angle domain) is the same. We call it as average power of clutter and noise.
[0033] Here is the definition and calculation method of average power of clutter and noise. The total power in the detection range (based on 1D / 2D / 3D-FFT detection algorithm, the maximum sensing range of delay, doppler and angle domain that can be achieved with the configured sensing signal) subtracts the power of the detected targets and the eliminable interference and the eliminable clutter, and the remaining power is averaged over the entire sensing range. The granularity of averaging is grid, that is, the average noise and clutter power is power contained in the size of grid.
[0034] The subtracted power of target and interference clutter includes the power of detected targets, the power of clutter (dynamic or static) that can be estimated and eliminated, and the power of environmental objects that can be estimated and eliminated, etc.
[0035] It should be noted that since grid can be one dimension or multiple dimensions, the average operation is the average of all dimensions. Example: target detection is performed in delay and doppler domain. The sensing detection range is Rt. Size of grid is Rg. The total power of the whole sensing range is Pt. Power of the detected targets is P1. Power of eliminable clutter and static environmental objects is P2 and P3, respectively. The total power of clutter and noise (which cannot be eliminated) is Pn=Pt-P1-P2-P3. Average power of these clutter and noise is Pn / Pt*Pg.
[0036] SINR of SRU can be defined as SINR of SRU = average power of SRU (unit: dBm) -average power of noise and clutter (unit: dBm) . Rx node can report the average power of clutter and noise (option 1) or SINR (option 2) .
[0037] Fig. 4 shows an example of the calculation of average power of noise and clutter.
[0038] Sensing has some specific requirements on sensing data reporting. There is low latency requirement for sensing data reporting and processing, e.g., high latency requirement sensing task, sensing assisted comm operations. A large amount of sensing data needs to be reported. RAN needs to know sensing data, at least for part of use cases, including (1) sensing data integration of BS mono-static sensing and BS-UE bi-static sensing (DL) operated in BS; (2) low latency requirement sensing use cases and scenarios.
[0039] There are two different NW architectures (SF is on CN or on RAN) . For different NW architectures, corresponding reporting ways are provided in the following.
[0040] NW architecture option 1: SF is on RAN (BS)
[0041] The pros are lower latency and RAN know sensing data. UE (or BS) can report to BS (SF located) through RRC, MAC-CE and L1. RAN can know sensing data. Large amount of sensing data can be divided into some small packages (e.g., one message every SRU) . RRC can support this kind of reporting. The impact is that new interface is required between different BSs to exchange information.
[0042] NW architecture option 2: SF is on CN
[0043] The cons are higher latency and sensing data is transparent to RAN. UE (or BS) reports to SF through data plane. RAN doesn’ t know sensing data. The pros are current interface among UE, BS and CN can support, which is similar as positioning.
[0044] It is possible that two kinds of NW architectures existing simultaneously. That is, SF is on both RAN and CN, just their functions are different. Part of sensing data is reported to RAN, the other part or all data is reported to CN.
[0045] For the case of data reported to RAN, sensing data can include SRU ID, resource ID (cell ID, resource set / resource ID (Tx beam) ) , quantities of power domain, degree of confidence, etc. The reporting to RAN can be through L1 / MAC-CE (similar as L1-RSRP reporting) . The purpose is to allow RAN to quickly adjust sensing resource configuration (e.g., adjust Tx beams for target tracking, adjust resource power, time and frequency domain configuration (sensing link adaptation) based on sensing quality.
[0046] Another case is that all sensing data is reported to RAN, then RAN reports all or part of sensing data to CN.
[0047] The following is about configuration contents of sensing configurations.
[0048] Sensing configuration contents include {SRU ID (optional) , cell ID, resource set, resource} .
[0049] SRU ID: it corresponds to the SRU number in the latest sensing data reported within T1 to T2 moments before the current configuration information is received. It is optional content. For example, it doesn’ t need to be configured in target detection stage because no target is detected. It shall be configured in target tracking stage. It can be the same as the reported SRU ID, or mapping to the reported SRU ID with pre-defined rule. The purpose is to inform sensing nodes the configured resource is mainly used to measure which SRU (or target) , sensing nodes can then make specific processing. Fig. 5 shows an example of the relationship of SRU ID reporting and configuration.
[0050] Cell ID, resource set, resource: These configurations can refer to positioning’s configurations. Sensing signals can be from serving cell and neighbor cells. For each cell, multiple resource sets and resources may be configured to support sensing with multiple sensing signals (e.g., PRS and PTRS) and multiple Tx beams (e.g., TRS with multiple Tx beams) .
[0051] The following is about configuration ways of sensing configuration. NW informs UE the configuration and validation of sensing signal for both serving and neighbor cells through SIB / RRC / MAC-CE / DCI / paging / PEI.
[0052] The details ways are summarized in the following table.
[0053] Here we will explain why SRU / target ID is required in sensing configuration and reporting. The purpose is to inform sensing nodes the configured resource is mainly used to measure which SRU (or target) , sensing nodes can then make specific processing.
[0054] For example, UE detected multiple targets and reported to BS / CN (with SRU ID info) during the period of target detection stage. These targets were detected based on different Rx beams by UE, and UE has locally stored this information. Next, BS / CN needs UE to track certain detected targets. New resource (e.g., having directional and finer Tx beams) may be configured, which QCL relationship with the resource used in detection stage is also configured. But this QCL relationship isn’ t enough for UE to decide which Rx beams shall be used if without SRU ID. By using the configured SRU ID, UE can know which Rx beams shall be used for the following sensing signal reception and processing for each SRU.
[0055] One example about UE’s specific processing is the data and result in target detection stage can be as initial value or assistance information in target tracking stage. This can improve the performance of tracking stage or accelerate and simplify the processing of tracking stage. These data and result may be different for different targets. By using the configured SRU ID, UE can know which target data is used in the tracking stage.
[0056] Another example about UE’s specific processing is when need to track target continuously, Tx beam direction of sensing resource shall be adjusted along with the change of target location. When sensing resource is reconfigured, SRU ID shall also be configured, so that UE knows which target this resource is used for the tracking, while not using this resource for the detection of new target. In this way, UE can use the locally stored target’s information to assist the following operations.
[0057] Fig. 6 shows an example of SRU ID reporting and configurations. Target tracking operations #1: BS / SF configures SRU ID and resource ID based on UE’s reporting in target detection stage. Target tracking operations #2: besides UE reported target (SRU ID=2) , BS / SF can configure new target related resource to require UE to track. UE needs to make different operations respectively based on the configured SRU ID.
[0058] Fig. 7 shows an exemplary block diagram of a communication apparatus according to an embodiment of the disclosure. The communication apparatus 800 can be configured to implement various embodiments of the disclosure described herein. The communication apparatus 800 can include a processor 810, a memory 820, and a radio frequency (RF) module 830 that are coupled together as shown in Fig. 7. In different examples, the communication apparatus 800 can be a base station, a mobile phone, a tablet computer, a desktop computer, a vehicle carried device, and the like.
[0059] The processor 810 can be configured to perform various functions of the described above with reference to Figs. 1-6. The processor 810 can include signal processing circuitry to process received or to be transmitted data according to communication protocols specified in, for example, LTE and NR standards. Additionally, the processor 810 may execute program instructions, for example, stored in the memory 820, to perform functions related with different communication protocols. The processor 810 can be implemented with suitable hardware, software, or a combination thereof. For example, the processor 810 can be implemented with application specific integrated circuits (ASIC) , field programmable gate arrays (FPGA) , and the like, that includes circuitry. The circuitry can be configured to perform various functions of the processor 810.
[0060] In one example, the memory 820 can store program instructions that, when executed by the processor 810, cause the processor 810 to perform various functions as described herein. The memory 820 can include a read only memory (ROM) , a random access memory (RAM) , a flash memory, a solid state memory, a hard disk drive, and the like.
[0061] The RF module 830 can be configured to receive a digital signal from the processor 810 and accordingly transmit a signal to a base station in a wireless communication network via an antenna 840. In addition, the RF module 830 can be configured to receive a wireless signal from a base station and accordingly generate a digital signal which is provided to the processor 810. The RF module 830 can include digital to analog / analog to digital converters (DAC / ADC) , frequency down / up converters, filters, and amplifiers for reception and transmission operations. For example, the RF module 830 can include converter circuits, filter circuits, amplification circuits, and the like, for processing signals on different carriers or bandwidth parts.
[0062] The communication apparatus 800 can optionally include other components, such as input and output devices, additional CPU or signal processing circuitry, and the like. Accordingly, the communication apparatus 800 may be capable of performing other additional functions, such as executing application programs, and processing alternative communication protocols.
[0063] The processes and functions described herein can be implemented as a computer program which, when executed by one or more processors, can cause the one or more processors to perform the respective processes and functions. The computer program may be stored or distributed on a suitable medium, such as an optical storage medium or a solid-state medium supplied together with, or as part of, other hardware. The computer program may also be distributed in other forms, such as via the Internet or other wired or wireless telecommunication systems. For example, the computer program can be obtained and loaded into an apparatus, including obtaining the computer program through physical medium or distributed system, including, for example, from a server connected to the Internet.
[0064] The computer program may be accessible from a computer-readable medium providing program instructions for use by or in connection with a computer or any instruction execution system. A computer readable medium may include any apparatus that stores, communicates, propagates, or transports the computer program for use by or in connection with an instruction execution system, apparatus, or device. The computer-readable medium can be magnetic, optical, electronic, electromagnetic, infrared, or semiconductor system (or apparatus or device) or a propagation medium. The computer-readable medium may include a computer-readable non-transitory storage medium such as a semiconductor or solid state memory, magnetic tape, a removable computer diskette, a random access memory (RAM) , a read-only memory (ROM) , a magnetic disk and an optical disk, and the like. The computer-readable non-transitory storage medium can include all types of computer readable medium, including magnetic storage medium, optical storage medium, flash medium and solid state storage medium.
[0065] While aspects of the present disclosure have been described in conjunction with the specific embodiments thereof that are proposed as examples, alternatives, modifications, and variations to the examples may be made. Accordingly, embodiments as set forth herein are intended to be illustrative and not limiting. There are changes that may be made without departing from the scope of the claims set forth below.
Claims
1.A method, comprising:Sensing node reports sensing reporting data to BS or SF; wherein the reporting data contents include SRU ID, size of grid, resource ID, delay domain, doppler domain, angle domain quantities, and power domain quantities, and degree of confidence.2.A method, comprising:Sensing reporting data ways include two schemes for different network architecture; wherein the first way is UE (or BS) can report to BS (SF located) through RRC, MAC-CE and L1, and the second way is UE (or BS) reports to SF through data plane.3.A method, comprising:Sensing configuration contents include {SRU ID (optional) , cell ID, resource set, resource} .4.A method, comprising:Sensing configuration ways include NW informs UE the configuration and validation of sensing signal for both serving and neighbor cells through SIB / RRC / MAC-CE / DCI / paging / PEI.