3GPP TSG RAN WG1 #120bis R1-2503113
Wuhan, China, April 7th – 11th, 2025
Agenda Item: 9.7
Source: Ad-Hoc Chair (Huawei)
Title: Session notes for 9.7 Study on channel modelling for Integrated Sensing And Communication (ISAC) for NR
Document for: Discussion, Decision
Study on channel modelling for Integrated Sensing And Communication (ISAC) for NR
Please refer to RP-242348 for detailed scope of the SI.
[120bis-R19-ISAC] Email discussion on Rel-19 ISAC channel model – Yingyang (xiaomi)
To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc
[Post-120bis-ISAC-01] – Jerome (AT&T)
Email discussion for agreement on simulation assumptions for ISAC channel model calibrations, from XXX to YYY.
Moderator to provide parameter tables and calibration template for sensing targets based on agreements from RAN1#120-bis
[Post-120bis-ISAC-02] – Yingyang (Xiaomi)
Email discussion for agreement on parameter values for monostatic background channel, and values of parameters for monostatic RCS of UAV with large size and AGV, from XXX to YYY.
[Post-120bis-ISAC-03] – Yingyang (Xiaomi)
Email discussion for endorsement of draft CR for TR38.901 update to introduce ISAC channel model, from XXX to YYY (until later than Post-120bis-ISAC-02).
R1-2502552 Draft CR for TR 38.901 to introduce channel model for ISAC Xiaomi, AT&T
R1-2503072 Draft CR for TR 38.901 to introduce channel model for ISAC Xiaomi, AT&T
ISAC deployment scenarios
Please provide your inputs on calibrations is to this sub-agenda item.
R1-2501817 Views on Rel-19 ISAC deployment scenarios vivo
R1-2501839 Discussion on ISAC deployment scenarios and requirements EURECOM
R1-2501926 Discussion on ISAC deployment scenarios InterDigital, Inc.
R1-2501935 Deployment scenarios for integrated sensing and communication with NR NVIDIA
R1-2502002 Discussion on ISAC deployment scenarios CATT, CICTCI
R1-2502029 Discussion on ISAC deployment scenarios China Telecom
R1-2502051 Discussion on ISAC Deployment Scenarios Nokia, Nokia Shanghai Bell
R1-2502054 Discussion on ISAC deployment scenarios Tiami Networks
R1-2502062 Discussion on ISAC deployment scenarios ZTE Corporation, Sanechips
R1-2502067 Discussion on ISAC deployment scenarios Panasonic
R1-2502170 Discussion on ISAC channel model calibration CMCC, China Southern Power Grid
R1-2502207 Deployment scenarios for ISAC channel model Huawei, HiSilicon
R1-2502285 Discussion on ISAC channel model calibration OPPO
R1-2502325 Discussion on ISAC deployment scenarios Sony
R1-2502378 Discussion on ISAC deployment scenarios Samsung
R1-2502416 Discussion on ISAC deployment scenarios CALTTA
R1-2502418 Discussion on ISAC channel calibration BUPT, CMCC
R1-2502451 Deployment scenarios and evaluation assumptions for ISAC channel model Xiaomi
R1-2502465 Discussion on ISAC deployment scenarios TOYOTA InfoTechnology Center
R1-2502588 Discussion on ISAC deployment scenarios Lenovo
R1-2502623 Discussion on ISAC deployment scenarios Apple
R1-2502714 Discussion on ISAC deployment scenario MediaTek Inc.
R1-2502725 Discussion on ISAC Deployment Scenarios Ericsson
R1-2502820 Discussion on ISAC deployment scenarios LG Electronics
R1-2502849 Discussion on ISAC deployment scenarios Qualcomm Incorporated
R1-2502922 Considerations on ISCA deployment scenarios CAICT
R1-2502731 FL Summary #1 on ISAC Scenarios and Calibrations Moderator (AT&T)
R1-2502732 FL Summary #2 on ISAC Scenarios and Calibrations Moderator (AT&T)
Agreement
For the purposes of large scale calibration for UAV sensing targets, the following revised calibration parameters are proposed below in Table x. Note that the change bars are against the agreements from RAN1#120.
Table x. Simulation assumptions for large scale calibration for UAV sensing targets
Agreement
For the purposes of full calibration for UAV sensing targets, the following calibration parameters are proposed below in Table x.
Table x. Simulation assumptions for full calibration for UAV sensing targets
R1-2502733 FL Summary #3 on ISAC Scenarios and Calibrations Moderator (AT&T)
Agreement
For the purposes of large scale calibrations for Automotive sensing targets, the following parameters are proposed below in Table x.
FFS: which type of UE is used for UT in different sensing mode
FFS: impact of spatial consistency, if any, in case of vehicle with 5 scattering points
FFS: cell layout for ISD = 250 m
Table x. Simulation assumptions for large scale calibration for Automotive sensing targets
R1-2502734 FL Summary #4 on ISAC Scenarios and Calibrations Moderator (AT&T)
ISAC channel modelling
R1-2501818 Views on Rel-19 ISAC channel modelling vivo, BUPT
R1-2501840 Discussion on ISAC channel modeling EURECOM
R1-2501878 Discussion on ISAC channel modeling Spreadtrum, UNISOC
R1-2501927 Discussion on ISAC channel modeling InterDigital, Inc.
R1-2501933 Channel modelling for integrated sensing and communication with NR NVIDIA
R1-2502003 Discussion on ISAC channel modelling CATT, CICTCI
R1-2502030 Discussion on ISAC channel modelling China Telecom
R1-2502052 Discussion on ISAC channel modeling Nokia, Nokia Shanghai Bell
R1-2502055 Discussion on ISAC Channel Modeling Tiami Networks
R1-2502063 Joint views on mono-static background channel modeling ZTE Corporation, Sanechips, OPPO, BUPT, BJTU, CAICT, Xiaomi
R1-2502171 Discussion on channel modeling methodology for ISAC CMCC, BUPT, SEU, PML
R1-2502208 Channel modelling for ISAC Huawei, HiSilicon
R1-2502286 Study on ISAC channel modelling OPPO
R1-2502326 Discussion on Channel Modelling for ISAC Sony
R1-2502379 Discussion on ISAC channel modelling Samsung
R1-2502417 Discussion on channel modelling for ISAC CALTTA, ZTE Corporation, Sanechips
R1-2502419 ISAC Channel Modeling and Measurement Validation BUPT, CMCC, VIVO
R1-2502452 Discussion on ISAC channel model Xiaomi, BJTU, BUPT
R1-2502466 Discussion on ISAC channel modelling TOYOTA InfoTechnology Center
R1-2502565 Discussion on ISAC channel modelling Tejas Network Limited
R1-2502572 Discussion on ISAC Channel Modeling NIST
R1-2502587 Discussion on Channel Modelling for ISAC Lenovo
R1-2502624 Discussion on ISAC channel modelling Apple
R1-2502715 Discussion on ISAC channel modelling MediaTek Inc.
R1-2502726 Discussion on ISAC Channel Modelling Ericsson
R1-2502736 Discussions on ISAC Channel Modeling AT&T
R1-2502776 Discussion on ISAC Channel Modelling NTT DOCOMO, INC.
R1-2502814 Discussion on ISAC channel modelling Panasonic
R1-2502821 Discussion on ISAC channel modelling LG Electronics
R1-2502850 Discussion on ISAC channel modelling Qualcomm Incorporated
R1-2502923 Considerations on ISAC channel modelling CAICT
R1-2502553 Summary #1 on ISAC channel modelling Moderator (Xiaomi)
Agreement
In order to generate Tx-target link, target-Rx link and the background channel, the above table on reference TRs (excluding the already agreed part) is adopted for the mapping between reference TRs and a pair of nodes (STX, SRX, target)
Note: continue discussion for updating the table with RSU type UE
FFS: the generation of background channel based on reference TRs is subject to the addition of low-energy clusters
Agreement
To generate the parameters (in the steps before concatenation), the large-scale parameters and the small-scale parameters used to generate the Tx-target link are respectively the same as that of the target-Rx link for monostatic sensing, where departure angle on one link and arrival angle on the other link are reciprocal.
FFS: whether this applies to initial phase
Agreement
Normalization on the product of three polarization matrixes of a direct/indirect path generated by stochastic cluster, i.e., CPMtx,sp,rx= CPMsp,rx . CPMsp . CPMtx,sp is supported
The scaling factor is
Agreement
Power normalization of target channel after path dropping of the target channel is not supported.
Agreement
On the monostatic RCS for human with RCS model 2
The monostatic RCS for a scattering point of the target is generated by
The values/pattern A*B1, i.e., is deterministic based on incident/scattered angles
Where,
FFS how many rows of the values/pattern A*B1 are defined for the target
Note: each row has a defined applicable range of and
Note: whether the RCS is elevation angle dependent or dependent on both elevation and horizontal angles can be separately discussed
Agreement
The following mean and standard deviation values of XPR of targets are agreed for monostatic sensing and bistatic sensing as follows:
UAV: (13.75, 7.07) dB
Human: (19.81, 4.25) dB
Vehicle: (21.12, 6.88) dB
R1-2502554 Summary #2 on ISAC channel modelling Moderator (Xiaomi)
Agreement
When spatial consistency is enabled, the 1-by-1 random coupling generated by concatenation Option 3 is not updated per simulation drop even if Tx, target, Rx positions change during simulation.
Agreement
The following working assumption is confirmed
R1-2502555 Summary #3 on ISAC channel modelling Moderator (Xiaomi)
Working assumption
For vehicle with single/multiple scattering points, the bistatic RCS is generated by
The values/pattern of A*B1 of bistatic RCS is given by:
where
is applied to the within 0~180 degrees. k1= 6 and k2=. is the absolute bistatic angle between the incident ray and scattering ray within the plane of incident direction () and scattering direction ().
The angles of () are the projections of the bisector angle on the vertical plane and the horizontal plane, respectively.
FFS: RCS value when is 180 degrees
The effect of forward scattering is -Inf in Rel-19
5 sets of parameters Applicable Range of and Applicable Range of are applicable as defined for the monostatic RCS of vehicle with single/multiple SPSTs
FFS: how to avoid angular discontinuity
Continue study on a new formula for to resolve the issue of angular discontinuity.
The new formula should retain following property: the linear bistatic RCS for a vehicle with single scattering point is the sum of the bistatic RCS of the multiple scattering points of the vehicle
the following formula can be a reference for the study
Note: the working assumption agreed on Thursday was updated on Friday as follows: k1= 6 and k2=
R1-2502556 Summary #4 on ISAC channel modelling Moderator (Xiaomi)
Agreement
On background channel for mono-static sensing, the following details are provided:
reference points are dropped for one Tx, based on the Gamma distribution for distance and height of reference point.
The LOS AOD between Tx and the first reference point, which is denoted as AOD1, is generated based on uniform distribution .
The LOS AOD between Tx and the second reference point is AOD1 +
The LOS AOD between Tx and the third reference point is AOD1 +
The background channel is generated based on the channel generated as in existing TR between the real Tx and the reference point assuming NLOS condition.
The antenna field pattern and array orientation of reference point are set same as Tx.
Arrival angles for both azimuth and elevation and are set equal to departure angles
The absolute delay model d3D and as agreed for bistatic sensing for the same sensing scenario applies. Down-select one option from the following:
Option 0: no scaling factor is applied to d3D
Option 1: An offset is applied to d3D, i.e., d3D-c1
Option 2: A scaling factor d_s is multiplied to d3D, i.e., d3D*d_s. d_s is a value within range [0, 1].
Note: The adjustment of absolute delay doesn’t impact the generation of NLOS clusters between the Tx and each reference point
The mono-static background channel for the Tx would be sum of channels of the links between the Tx and all related reference points, which is
FFS: Doppler frequency in background channel for monostatic sensing
The rays in a stochastic cluster with ZOA at BS less than D degree are dropped
D=[90] for RMa,
D=[60] for UMa
D=[50] for UMi
Note: this threshold for ZOA is not applicable to other sensing scenarios
Agreement
To generate the background channel, the power threshold (-25 dB) for removing clusters in step 6 in section 7.5, TR 38.901 is reused.
Agreement
The ISAC background channel can be generated between a sensing Tx and a sensing Rx or RP (relevant for monostatic case) via the following steps:
Step 1: generate a first set of clusters/rays according to TR 38.901(or other related TRs)
Step 2: generate a second set of NLOS clusters/rays according to TR 38.901 (or other related TRs), where the power of the second set of clusters/rays should be scaled down such that
is the power of the NLOS cluster with the strongest power from the first set.
is the power of the n-th cluster from the second set.
Where, N is the number of clusters, M is the number of rays within each cluster, value of G relates to power
N=360, M=1, G = -25dB, no further change from 38.901, 36.777, 38.858 (i.e., utilizing the same DS, ASA, ASD, ZSA, ZSD, , as used for the first step)
The step 2 is an additional modeling component
For email discussion
Proposal
The values of the parameters to generate background channel for TRP monostatic and UE monostatic sensing for each sensing scenario are provided in the following table
FFS parameter values for other scenarios (e.g. indoor factory)
Email discussion/approval checking the values after April meeting, including validation for newly agreed parameters
The email discussion includes all scenarios, TRP monostatic and UE monostatic
The email discussion includes how to merge results provided by companies
Agreement
For human as a sensing target with a single scattering point, the height of the scattering point is 1.5 m.
Agreement
In sensing scenario UMi, UMa, RMa, if the height of a scattering point of target is less than 1.5m, for pathloss calculation, down-selection one of the options below:
Option 4: use in Table 7.4.1-1: Pathloss models in TR 38.901
Option 5: use hUT 1.5 m for pathloss calculation
Agreement
For sensing scenario UMi, UMa, RMa, UMi-AV, UMa-AV and RMa-AV, the height of a scattering point of a target is used to calculate the LOS probability and pathloss, regardless of the lower bound in the existing TRs that are referred to generate ISAC channel.
FFS for the case where the height of a scattering point of target is less than 1.5m in sensing scenario UMi, UMa, RMa
For email approval
[FL3] Proposal 4.2.1-1
On the monostatic RCS of UAV of large size,
The values/pattern of component A*B1 are generated by the following parameters
When is in the range [0°,45° ] or [135°,180°],
The standard deviation of component B2 is 2.50 dB
For email approval
[FL3] Proposal 4.2.3-1
On the monostatic RCS of AGV with single scattering point,
The values/pattern of component A*B1 are generated by the following parameters
When is in the range [0°,30° ),
The standard deviation of component B2 is 2.51 dB
|