按照截图格式,对下面的内容进行总结,要求:1、summary尽量控制在word半页之内;2、在控制内...

생성일: 2026년 3월 3일

답변에 사용된 모델 GPT-5.2 Thinking by Chat01

질문

image.pngimage.png
ISAC文稿分析.docx

按照截图格式,对下面的内容进行总结,要求:1、summary尽量控制在word半页之内;2、在控制内容长度的前提下,尽量囊括所有公司的所有观点,观点相近的进行合并,格式见截图。
ISAC
OPPO(RP-260060、 RP-260384)

Table 5: Sensing-related requirements
Indoor Office Indoor Factory Urban Macro
Sensing use case human motion monitoring (e.g., respiration detection) indoor human/AGV detection & tracking outdoor human/vehicle/UAV detection & tracking
Detection Probability 95% 95% [95%]
False Alarm Probability 5% 5% [5%]
Horizontal Localization Accuracy N/A 1m [5m or 10m]
Vertical Localization Accuracy N/A 1m
Velocity Accuracy N/A 1.5m/s for pedestrian,
15m/s for AGV
Proposal 3: Adopt following updates to Table 5 (Sensing related requirements)
 Add one more row to describe the corresponding sensing use cases under each deployment scenario.
 Add one more column for the indoor office (InH) scenario to accommodate human motion monitoring category provided in TS22.137.
 Apply indoor factory scenario to indoor human/AGV detection & tracking.
 Apply urban macro scenario t outdoor human/vehicle detection & tracking.
 Use requirement values from TS22.137 for Table 5.

Proposal 1: RAN plenary to leave prioritization of sensing scenarios decided by SA to RAN WG, or at least to keep motion monitoring along with object detection and tracking.
• For the second choice above, a corresponding TP is given as below.
TP Start

5.4.4 Sensing
Editor note: More sensing use cases can be included depending on further discussion.
The 6GR and 6G RAN architecture shall at least support use cases of detection and/or tracking of passive objects, at least including the following sensing scenarios involving UAVs, human, vehicles and AGVs, as defined in [ref. to TS22.137, TR22.837].
• Object detection & tracking
• Motion monitoring
End of TP

CMCC(RP-260076、RP-260079、RP-260091)
In this contribution, we provide our view on 6G sensing use cases and related KPIs.
Proposal 1: Support the KPIs listed in Table 1 for 6G sensing.
Table 1 Sensing-related requirements
Indoor Factory Urban Macro
Detection Probability 95% 95%,
99% for UAV
False Alarm Probability 5% 5%,
1% for UAV
Horizontal Localization Accuracy 2 m 5 m
Vertical Localization Accuracy N/A 5 m
Velocity Accuracy 1 m/s 1 m/s

Proposal 2: Define sensing capacity as a sensing-related requirement with the following definition:

Sensing capacity is defined as the maximum number of the targets [per sector] when sensing results of all targets in observation zone fulfil other sensing requirements with [95%] probability.
Proposal 3: Support the KPI on sensing capacity listed in Table 2 for 6G sensing.

Table 2 Sensing-related requirements
Indoor Factory Urban Macro
Sensing capacity 40 40

Proposal 1: 6GR should study cooperative/multi-static sensing mechanism involving multiple UEs and/or TRPs.
Proposal 2: 6GR should study environment awareness/reconstruction to assist communication.
Proposal 3: 6GR should study delay/angle/Doppler profiles feedback for sensing assist communication.

Samsung(RP-260198)
Table 5.1.17-1: Sensing-related requirements
Indoor Factory Urban Macro
Detection Probability 95% [95%]
False Alarm Probability 5% [5%]
Horizontal Localization Accuracy 2 m [5 m or 10m]
Vertical Localization Accuracy N/A 8 m (Note 1)
Velocity Accuracy 2 m/s 4 m/s
Note 1: The applicability of vertical localization accuracy depends on the type of sensing target.

Huawei(RP-260209、RP-260217、RP-260330)
The minimum requirements for Sensing-related requirements defined in ITU TPR are summarized in Table 5.1.17-1.
Table 5.1.17-1: Sensing-related requirements
Indoor Factory Urban Macro
Detection Probability 95% 95% [95%]
False Alarm Probability 5% 5% [5%]
Horizontal Localization Accuracy 2m 5m [5m or 10m]
Vertical Localization Accuracy N/A 8m
Velocity Accuracy 2m/s 4m/s

In particular, the performance requirement for detection and/or tracking of vehicles is defined as follows:
For moving target with speed up to 120km/h:

Horizontal Localization accuracy: 3m

Velocity Accuracy: 3m/s

The 6G system shall be able to provide sensing functions characterizing environmental object as follows:
• Measure and reconstruct a relatively large Environment Object
• [sub meter to meter-level] reconstruction accuracy

Proposal 1: RAN plenary shall identify use cases, corresponding deployment scenarios and performance targets for ISAC by March 2026 the latest, to match the RAN WG level study timeline (starting PHY design in April 2026).

New use cases beyond 5G-A shall be addressed and completed at RAN#111

Proposal 2: 6G shall support use case of target detection and tracking, e.g. road digitization, with the below performance target:
• Moving target up to 120km/h:

Localization accuracy: horizontal 3m

Velocity accuracy: 3m/s

Proposal 3: 6G shall be able to provide sensing functions characterizing environmental object [6] as described:
• Measure and reconstruct a relatively large Environment Object
• [sub meter to meter-level] reconstruction accuracy

Proposal 4: 6G shall study mechanism of collecting and utilizing measurement data relevant to environmental information to improve communication performance and user experience, e.g. for optimizing communication and positioning services.

Proposal 5: 6G shall enable efficient resource utilization by considering trade-off between sensing and communication performance.
• Corresponding technical aspects shall be studied thoroughly in RAN WG study, with performance evaluation provided from both communication and sensing perspective before reaching the conclusion.
Proposal 6: Adopt the following text proposal in Sec 5 for ISAC services requirements in section 5.4.4 of TR 38.914.
The 6GR and 6G RAN architecture shall at least support use cases of detection and/or tracking of passive objects, at least including UAVs, human, vehicles and AGVs.
6GR and 6G RAN architecture shall support the use cases with the corresponding performance requirements as defined in TR 22.870:

use case of target detection and tracking for UAV, vehicles, and AGVs

use case of improvement of communication performance
6GR and 6G RAN architecture shall support mechanism of collecting and utilizing measurement data relevant to environmental information to improve communication performance and user experience, e.g., for optimizing communication and positioning services.
6GR and 6G RAN architecture shall enable efficient resource utilization by considering trade-off between sensing and communication performance.

Proposal: Remove “human” from the sensing section (i.e., section 5.4.4) of TR 38.914.

QC(RP-260239、RP-260240)
The current RAN TR does not include TPR targets for Sensing. To align with the latest ITU-R IMT-2030 TPR Report [3], it is proposed to define the following targets:
Table 4. Proposed target value for Sensing capabilities
Requirement Indoor Factory Urban Macro
Detection probability 95% 95%
False alarm probability 5% 5%
Horizontal localization accuracy 2 m 5 m
Vertical localization accuracy N/A 8 m (Note 1)
Velocity accuracy 2 m/s 4 m/s
Note 1: The applicability of vertical localization accuracy depends on the type of sensing target.

Proposal 2: It is proposed to consider the following requirements for 6G Sensing (to be added in sec 5.4.4):
• 6GR shall enable both RAN-embedded and RAN-external (e.g. Camera, Wi-Fi, UWB, etc.) sensing techniques.
• 6GR shall enable all sensing modes (TRP monostatic, UE monostatic, TRP-TRP bistatic, TRP-UE bistatic, UE-TRP bistatic, UE-UE bistatic), and cooperative sensing involving one or multiple UEs and/or one or multiple base stations.
• 6GR shall enable usage of the measurements obtained by sensing to improve communication performance.
APPLE(RP-260242、RP-260243)

Proposal 2.3: For ISAC in the 6G first release, representative use cases should cover different sensing targets (UAV, human, vehicle/bike) , different environments (outdoor, home and factory) and different sensing modes (involving network and UE). Capture at least the following use cases in TR 38.914
o Commercial, e.g.
o TR 22.870 use case 7.5 (low-altitude UAV supervision)
o TR 22.837 use case 5.26 (automotive manoeuvring and navigation service)
o Industrial, e.g.
o TR 22.870 use case 7.27 (robots collaborating in sensing in smart factories)
o TR 22.837 use case 5.9 (AGV detection and tracking in factories)
o Safety, e.g.
o TR 22.870 use case 7.15 (infrastructure collapse monitoring)
o TR 22.837 use case 5.1 (intruder detection in smart home)
o Sensing assisted communications, e.g.
o TR 22.870 use case 7.20 (sensing assisted communication in industry park)
o TR 22.837 use case 5.21 (seamless XR streaming)

Xiaomi(RP-260260、RP-260354)
Proposal 1: To facilitate requirement definition for sensing as a new service in 6G, RAN selects a subset of use cases for object detection and tracking and defines the representative deployment scenarios accordingly.
Proposal 2: To facilitate requirement definition for sensing as a new service in 6G, RAN prioritizes detection and tracking for the following use cases
• UAV related use cases
• Human related use cases
• Automotive related use cases
• AGV related use cases
Proposal 3: Sensing modes with UE involvement should be studied for detection and tracking at least for following target types: UAV, human, vehicle and AGV.
Proposal 4: For supporting 6G sensing services, the following requirements can be considered as a guidance,
• Sensing Performance (e.g. accuracy, coverage, latency) should be guaranteed
• Impact on communication shall be minimized
o Meeting given sensing requirements should not cause unacceptable degradation of communication KPIs (e.g. throughput, latency, reliability)
• Radio resources should be used efficiently
o Sensing resources should not be over-provisioned.
o Reuse of existing communication signals (SSB, CSI-RS, DMRS) for sensing where possible
• Scalability/Flexibility
o ISAC should scale with target density and sensing demand, without requiring dedicated infrastructure everywhere
o Support for distributed transmitters and receivers without overwhelming coordination overhead
• Interoperability
o At least bistatic sensing operations should support multi-vendor environments. Hence, standardized sensing data formats and signaling procedures should be developed.

In the above technical performance requirements, the sensing target is a passive object, which is not connected to the radio network for communication.
The minimum requirements for Sensing-related requirements are summarized in Table 5.1.17-1.
Table 5.1.17-1: Sensing-related requirements
Indoor Factory Urban Macro
Detection Probability 95% 95%
False Alarm Probability 5% 5%
Horizontal Localization Accuracy 2m 5m
Vertical Localization Accuracy N/A 8 m (Note 1)
Velocity Accuracy 2m/s 4 m/s
Note 1: The applicability of vertical localization accuracy depends on the type of sensing target.

For 3GPP internal study, the minimum requirements for sensing-related requirements are summarized in Table 5.1.17-2.
Table 5.1.17-2: Sensing-related requirements for 3GPP internal study
Indoor Hotspot Urban grid
Detection Probability 95% 95%
False Alarm Probability 5% 5%
Horizontal Localization Accuracy 2m 5m
Vertical Localization Accuracy N/A 8 m (Note 2)
Velocity Accuracy 2m/s 4 m/s
Note 2: The applicability of vertical localization accuracy depends on the type of sensing target.

MediaTek Inc(RP-260260)
Proposal 1: The following typical sensing scenarios should be captured in the TR 38.914

human health and motion monitoring

intrusion detection

sensing assisted communication

Proposal 2: Capture in TR38.914 to target efficient resource utilization, including resource allocation and signal design, to achieve the required sensing performance for the served use case(s) while the same spectrum is also serving 6G communication.

VIAVI Solutions, ZTE Corporation(RP-260310)
In this VIAVI-ZTE collaboration project on ISAC, both CP-OFDM and pulse waveform on software and hardware are implemented to demonstrate its effectiveness for road collapse use case. It preliminarily proves the feasibility of this sensing use case. The results show that pulse waveform is effective for sensing operations, outperforms existing communications waveform in sensing performance. As the pulse waveform can be transmitted in TDM mode with minimum effect to communications performance, it can provide an effective sensing solution for 6G requiring accurate sensing for many new use cases.
Proposal: 6G shall support ISAC use case on infrastructure collapse monitoring.

T-Mobile USA, Ericsson, Nokia, Verizon(RP-260312)
The 6GR and 6G RAN architecture shall at least support use cases of detection and/or tracking of passive objects, at least including UAVs, human, vehicles and AGVs.
 The 6GR sensing shall support target detection under NLOS and LOS conditions between the base station and the target.
 Dynamic radio resource sharing between communication and sensing shall be supported.
 Sensing data shall be visible and collected in the RAN domain.
 The 6GR sensing shall support FR1, FR2, and any new bands such as FR3.

ZTE(RP-260333、RP-260334、RP-260336)
The following TP is suggested:
5.4.4 Sensing
Editor note: More sensing use cases can be included depending on further discussion.
The 6GR and 6G RAN architecture shall at least support use cases of detection and/or tracking of passive objects, at least including UAVs, human, vehicles and AGVs.
6GR shall at least fulfill sensing requirements as described in Clause 5.1.17.
6GR shall additionally support use cases of ship detection and/or tracking, infrastructure collapse monitoring, and structural health monitoring.
6GR shall enable sensing services for digital twin to assist communication.

The 6GR and 6G RAN architecture shall at least support use cases of detection and/or tracking of passive objects, at least including UAVs, human, vehicles and AGVs. 6GR shall at least support sensing use cases include the detection and tracking of UAV, Pedestrian, Vehicle, AGV and Ship, infrastructure collapse monitoring, and structural health monitoring. The 6GR should enable, and improve if suitable, state-of-art sensing techniques, such as RAN-embedded (based on RAN wireless sensing signal) and RAN-external (e.g. Radar, Lidar, Camara, IEEE802.11 station, UWB, etc.). The 6GR sensing shall exploit high bandwidth, massive antenna systems, network architecture/ functionalities. 6GR sensing shall support indoors and outdoors scenarios. 6GR shall support regulatory sensing requirements. 6GR design targets for sensing requirement include: 1. Support accuracy and latency as defined in TS22.137, and TR 22.870 for some use cases 3. Reduced network complexity 3. Reduced device cost 4. Reduced device power consumption 5. Efficient signalling over the air interface and in the network 6. Support for hybrid sensing methods 7. Scalability (support for large number of sensing objects) 8. High security 9. High availability
Table 5.1.17-1: Sensing-related requirements
Indoor Factory Urban Macro
Detection Probability 95% 95%
False Alarm Probability 5% 5%
Horizontal Localization Accuracy 2m 5
Vertical Localization Accuracy N/A 8m (Note)
Velocity Accuracy 2 m/s 4 m/s

NTT DOCOMO(RP-260348)

Proposal 4: For the evaluation of sensing-related requirements in Sect. 5.1.17 of TR 38.914, target values should be discussed based on the agreed values in ITU-R WP 5D as follows.
Table 5.1.17-1: Sensing-related requirements
Indoor Factory Urban Macro
Detection Probability 95% [95%]
False Alarm Probability 5% [5%]
Horizontal Localization Accuracy 2 m [5m or 10m]
Vertical Localization Accuracy N/A 8 m (Note 1)
Velocity Accuracy 2 m/s 4 m/s
Note 1: The applicability of vertical localization accuracy depends on the type of sensing target.

VIVO(RP-260370)
Observation 1: Environmental reconstruction (Digital Twin of the environment) is beneficial for some industries, such as autonomous driving in intelligent transportation, or autonomous motion of AGVs and collaborative robots in smart factories.
Observation 2: Environmental reconstruction information (Digital Twin information) can be used in aNB or UE to enhance communication and sensing performance.
Observation 3: Micro-Doppler modeling improves detection probability of UAVs under low radial velocity conditions and facilitates identification of UAV-specific characteristics, enabling differentiation of UAV types and discrimination from other flying objects such as birds.
Proposal 1: The deployment scenarios and KPIs in Table 1 and Table 2 for detection and/or tracking of UAVs, human, vehicles and AGVs are supported.
Table 1: Deployment scenarios for Object detection and tracking
Sensing target of detection and/or tracking Related deployment scenario
UAV Urban macro
Human Outdoor: Urban macro/urban grid
Indoor: Indoor hotspot/factory
AGV Indoor factory
Vehicle Urban grid

Table 2: KPIs for Object detection and tracking
Use cases
Confidence level [%] Positioning accuracy[m] Radial velocity accuracy[m/s] Sensing latency[ms] Missed detection probability False alarm probability
Horizontal vertical
UAV [90%] [2] [2] [2] [<1000] [5%] [5%]
Human [90%] [2] N/A [0.5] [<1000] [5%] [5%]
AGV [90%] [1] N/A [1] [<1000] [5%] [5%]
Vehicle [90%] [2] N/A [2] [<1000] [5%] [5%]

Proposal 2: For deployment scenarios for sensing evaluation and UE-involved sensing modes (e.g., TRP-UE DL, UE-TRP UL), the moving speed of UE is assumed to be (0, 0.3] km/h.
Proposal 3: Environmental reconstruction (Digital Twin of the environment) should be studied for 6G sensing. It can reuse the sensing KPIs already agreed by RAN. One deployment scenario is urban grid.
Proposal 4: Environmental reconstruction information (Digital Twin of the environment) to assist communication and sensing should be studied. The related KPIs are communication KPIs depending on use cases. One deployment scenario is urban grid.
Proposal 5: Micro-Doppler related use cases including blade rotation of UAV and human respiration should be prioritized in the study of sensing. The related deployment scenarios of blade rotation of UAV and human respiration can reuse the deployment scenarios for UAV and human in Table 1. The related KPI is accuracy of micro-Doppler.

CEWiT, Indian Institute of Technology Madras (IITM), Tejas Networks, Indian Institute of Technology Kanpur (IITK)( RP-260378)
The minimum requirements for Sensing-related requirements are summarized in Table 5.1.17-1.
Table 5.1.17-1: Sensing-related requirements
Indoor Factory Urban Macro
Detection Probability 95% [95%]
False Alarm Probability 5% [5%]
Horizontal Localization Accuracy 2m [5m or 10m]
Vertical Localization Accuracy N/A 8m Note 1
Velocity Accuracy 2 m/s 4m/s
Note 1: The applicability of vertical localization accuracy depends on the type of sensing target.

SK Telecom(RP-260388)
Proposal 1. According to the agreement in RAN, RAN WGs should study all sensing modes (i.e., TRP monostatic, TRP-TRP bistatic, TRP-UE DL, UE-TRP UL, UE-UE bistatic and UE monostatic), and RAN plenary may consider sending an LS to the WGs to ensure the alignment between WG study scope and RAN agreement made in RAN#109.
Proposal 2. RAN WGs should take into account all use cases related to sensing identified in TR 22.870 for their study.
Robert Bosch GmbH(RP-260478)
Observation 1: Existing 5G NR sidelink and physical channels cannot support UE-UE bistatic and UE-monostatic sensing.

Proposal 1: RAN should consider the use cases from TR 22.870 and do not preclude any use case.
Proposal 2: Bi/multi-static sensing mode with multiple TRPs should be studied as part of the 6GR for 6G Day-1.
Proposal 3: RAN should clarify whether 5G NR sidelink should be enhanced to support UE-based sensing modes for 6G Day-1.

Lenovo(RP-260484)
Observation 1. Cooperative and multi-static sensing operation facilitates re-using of the same sensing signal transmission for multiple measurements, leading to increased energy efficiency and measurement diversity/accuracy
Observation 2. While sensing primarily considers target as a physical object without a UE identity/function, sensing operation may also be applied to the physical objects associated (e.g., attached to) a UE device, with mutual benefit between sensing, positioning and communications.
Proposal 1. 6GR to study cooperative and multi-static sensing modes
Proposal 2. 6GR to study both sensing scenarios where sensing target is not associated with a UE entity as well as the case where sensing target is associated (e.g., attached) to a UE.
Observation 3. It is motivated to re-use the parameters defined for the deployment scenarios of the underlying communication scenarios for defining deployment scenarios for sensing, both to avoid sensing-specific deployments as well as to evaluate mutual impact (interference or constructive use) between sensing and communication transmissions
Proposal 3. Re-use the same scenario assumptions & parameters to define sensing deployment scenarios, including at least carrier frequencies, system bandwidth, (cell/sector) layout, ISD, antenna configurations (UE and BS), UE dropping, communication traffic model
Observation 4. Additional sensing-related definitions are required to be added on top of each deployment per-sensing use-case/scenario and/or per-target type to define an evaluation scenario for sensing.
Proposal 4. The evaluation of the sensing performance needs to consider the radio resource multiplexing scheme and any potential interference or mutual impact with communication evaluation.
Proposal 5. RAN to consider sensing Tx/Rx node definition, target related parameters/dropping, known environment objects, when available (e.g., EO type 1/2), and necessary channel features, as additional parameters for defining a sensing scenario.
Observation 5. The current false-alarm definition present in 38.914 does not capture the case where a target is detected on two different instances (e.g., delay taps) due to multi-path or shadow effect of one target, where at least one (or multiple) target is present
Proposal 6. 6GR to consider definition of false alarm metrics both conditioned to no target being present and in the multi-target scenarios.
Observation 6. Resolution is an informative KPI of a sensing operation and needed when sensing is performed in the presence of multiple closely located sensing targets, e.g., pedestrians in a pathway. Moreover, sensing resolution is impacted by the algorithm complexity and multiple aggregated sensing links and may not be trivially inferred from the system parameters.
Proposal 7. Consider sensing resolution as a metric defining sensing KPIs.
Observation 7. The number of sensing targets does not sufficiently define the sensing overhead or needed complexity.
Proposal 8 RAN to consider sensing capacity in terms of the supported sensing areas over which a sensing KPI is expected to be delivered.

Observation 8. Sensing latency and refreshing rate are both informative metrics of the sensing capability, both in terms of the service KPI, as well as the resulting measurements overhead when sensing operation is present.
Proposal 9. RAN to consider Sensing latency and refreshing rate as a sensing KPI.
Proposal 10. As part of the sensing evaluations, the use-cases of object detection and tracking, sensing-assisted positioning enhancements (sensing of a UE as a passive object), as well as sensing-assisted communication enhancements should be considered.
Proposal 11. RAN to consider adopting the values for the target KPIs as presented in Table 1 for the initial minimum sensing target KPIs. Further categories and target KPI requirements can be considered based on iterations of 6GR evaluations, and the progress of the study of 6G use-cases and system requirements [TR 22.870].

AT&T(RP-260486)
The 6GR and 6G RAN architecture shall support at least TRP-TRP monostatic, TRP-TRP bi/multi-static sensing and UE-TRP bistatic/multistatic modes using a flexible data collection/reporting framework.

Telstra, T-Mobile USA, Deutsche Telekom, Telenor, Turkcell, KDDI, Boost Mobile Network, Jio Platforms, Rakuten Mobile, Telecom Italia, Telefonica, Telus(RP-260497)

5.4.4 Sensing
*** START TEXT PROPOSAL ***
The 6GR and 6G RAN architecture shall at least support use cases of detection and/or tracking of:
• passive objects, at least including UAVs, human, vehicles, and AGVs and
• extreme weather events such as fire and flood.

사고

Summarizing user request for a Chinese template

The user wants a Chinese summary with a clear template—Issue Name, Brief Summary, and Main options. Each option will describe different companies, including tdoc numbers, with supporting sections for our views. I'll aim for about 250-350 Chinese characters, making sure to include citations and link the provided document.

Summarizing proposed KPIs and use cases

Companies like Samsung, Huawei, Xiaomi, and OPPO are proposing various KPIs, including indoor factory accuracy and velocity metrics. Options include adopting baseline TPR-aligned KPIs, expanding scenarios (e.g., indoor office), or adding additional metrics like latency or sensing capacity. Some also suggest expanding use cases like health monitoring, infrastructure collapse, or digital twin applications.

Summarizing 6G RAN Sensing Requirements

The 6G RAN TR 38.914 ISAC/Sensing requirements are being debated, with discussions on use cases like object detection vs. motion monitoring, and whether human detection should be included. Issues also include aligning with ITU-R IMT-2030 TPR and defining additional KPIs, architecture capabilities, and sensing modes.

Summarizing options for KPIs and use cases expansion

The timeline request suggests two main options:

  1. Adopt minimum KPIs aligned with ITU-R TPR, including various accuracy metrics for indoor factories, urban macro, and UAVs.
  2. Expand deployment scenarios to include use cases like motion monitoring in offices and additional cases like ship detection, infrastructure collapse, and digital twins. Both options have support from various companies.

Summarizing options for sensing KPIs and architecture in 6G ISAC

The user requested a summary in a specific format, so I’ll provide the four options concisely:

  1. Adopt baseline KPIs, including sensing capacity and accuracy.
  2. Expand scenarios, adding motion monitoring and more use cases.
  3. Add new KPIs like latency and micro-doppler accuracy.
  4. Define architecture requirements for sensing modes and RAN functionality. My recommendation is to align KPIs with ITU-R and include optional scenarios, with a timeline for March 2026.

Preparing summary in Chinese with citations

I'll write the summary in Chinese, keeping the option headings in their original form. The citations should be inline rather than in parentheses, as suggested by policy. I'll use "website" as the citation since the tool didn't provide line numbers. The summary will be concise, fitting within 250–350 Chinese characters, with relevant RP numbers included.

Thought for 1m 44s

답변

Issue Name: TR 38.914(6G ISAC/Sensing)用例/场景优先级、KPI目标与架构能力(5.4.4 & 5.1.17)

  • Brief summary of the issue(key points, background, etc.)
    目前RAN侧需尽快对6G感知(ISAC)代表性用例、部署场景与性能指标(TPR/KPI)达成一致,并在TR 38.914中形成可落地文字/表格:一方面多家公司建议对齐ITU-R IMT-2030 TPR/TS22.137/TR22.870给出最低KPI表;另一方面对是否纳入“人体/运动监测”、是否增加室内办公(InH)、以及**扩展用例(数字孪生/环境重建、基础设施坍塌监测、船舶/极端天气等)**存在不同侧重点;同时也有公司提出新增KPI维度(容量、分辨率、时延/刷新率等)与架构能力(多种感知模式、RAN内外融合、资源共享等)。(ISAC文稿分析.docx)

Main options or WFs

Option 1:先固化“最低KPI基线表”(对齐TPR),作为所有评估共同起点

  • 内容:Indoor Factory & Urban Macro 的检测概率/虚警率/水平与垂直精度/速度精度等(主流共识为95%/5%、2m/5m、垂直8m、速度2/4m/s,部分提议Urban水平精度可为[5m或10m];UAV可更严)。
  • Supported by:Samsung[RP-260198]、Huawei[RP-260209/260217/260330]、QC[RP-260239/260240]、Xiaomi[RP-260260/260354]、ZTE[RP-260333/260334/260336]、NTT DOCOMO[RP-260348]、CEWiT/IITM/Tejas/IITK[RP-260378]、CMCC(含UAV更严KPI)[RP-260076/260079/260091]。(ISAC文稿分析.docx)

Option 2:并行明确“代表性用例+场景映射”,决定Day-1覆盖范围(含争议点:人体/运动监测)

  • 内容:
    • OPPO:建议新增Indoor Office列以容纳人体运动/健康监测(如呼吸),并在表中补充“各场景对应用例”行;同时建议保持“Motion monitoring”与“Object detection & tracking”并列。
    • Apple:建议6G首发用例覆盖多目标(UAV/人/车)、多环境(室外/家庭/工厂)、多模式(网络与UE参与),并给出商业/工业/安全/感知辅助通信的代表用例清单。
    • ZTE/VIAVI、Telco联合:强调基础设施坍塌监测、以及**极端天气(火/洪)**等扩展用例。
  • Supported by:OPPO[RP-260060/260384]、Apple[RP-260242/260243]、MediaTek(健康/入侵/感知辅助通信)[RP-260260]、VIAVI+ZTE(坍塌监测验证)[RP-260310]、ZTE(船舶/结构健康/数字孪生等)[RP-260333/260334/260336]、Telstra等多运营商[RP-260497]、VIVO(目标-场景映射/微多普勒)[RP-260370]、Xiaomi(按UAV/人/车/AGV优先)[RP-260260/260354]。(ISAC文稿分析.docx)

Option 3:在基线KPI之外,新增“补充KPI/定义”,用于后续评估与标准化

  • 内容:感知容量(最大目标数)分辨率感知时延与刷新率微多普勒精度;并建议澄清“虚警”在多径/多目标情况下的定义;部分还提出车辆(120km/h)特定精度目标。
  • Supported by:CMCC(容量40/扇区定义)[RP-260076/260079/260091]、Lenovo(容量/分辨率/时延&刷新率/虚警定义等)[RP-260484]、VIVO(微多普勒与数字孪生)[RP-260370]、Huawei(车辆120km/h:3m/3m/s;环境重建精度)[RP-260209/260217/260330]。(ISAC文稿分析.docx)

Option 4:在5.4.4补充“架构/机制要求”,保证实现路径(模式、融合、资源共享、数据可见性等)

  • 内容:支持RAN-embedded + RAN-external(相机/Wi-Fi/UWB等)、支持全感知模式(TRP/UE单站、TRP-TRP/UE-TRP/UE-UE双/多站、协作多点)、测量用于感知辅助通信动静态资源共享/权衡、NLOS/LOS、频段覆盖(FR1/FR2/FR3)、RAN域数据采集与上报框架;并讨论是否需增强sidelink以支持UE类模式。
  • Supported by:QC[RP-260239/260240]、CMCC(协作多站/环境感知/反馈)[RP-260076/260079/260091]、Xiaomi(UE参与、复用通信信号、互操作)[RP-260260/260354]、T-Mobile USA/Ericsson/Nokia/Verizon(资源共享、数据可见性、FR1/2/3等)[RP-260312]、SK Telecom(覆盖所有模式、全用例)[RP-260388]、Robert Bosch(sidelink与UE模式问题)[RP-260478]、Lenovo(场景复用与评估参数完善)[RP-260484]、AT&T(灵活数据收集/上报框架)[RP-260486]、ZTE(RAN内外融合/数字孪生等)[RP-260333/260334/260336]、Huawei(测量数据用于提升通信、资源权衡)[RP-260209/260217/260330]。(ISAC文稿分析.docx)

Our view, comments, questions, suggestion

  • 建议采用Option 1作为最低KPI“硬基线”(先对齐TPR/共识表),同时在TR中明确“垂直精度适用性依目标类型”。
  • 用例与场景上建议采用Option 2的分层写法:Day-1先覆盖“被动目标检测/跟踪(UAV/车/AGV/人)+ 感知辅助通信”,并将“运动/健康监测、数字孪生/环境重建、坍塌/结构健康、极端天气”等作为可选/扩展用例进入后续迭代(避免一次性塞满导致无法收敛)。
  • KPI扩展建议把容量/时延&刷新率/分辨率/微多普勒作为研究与评估指标(Option 3),先定义术语与评估口径(含多目标虚警定义),再逐步固化目标值。
  • 架构文本建议吸收Option 4的共识点:全模式+协作多站+RAN内外融合+资源共享+数据可见性/上报框架,并把sidelink增强问题列为待澄清事项。
  • 待确认问题:①“human”是否在5.4.4中保留(存在删除提议);②Indoor Office(InH)是否作为正式场景还是研究项;③极端天气/船舶等是否纳入Day-1还是扩展项;④RAN与SA之间用例优先级划分与时间表如何对齐。(ISAC文稿分析.docx)

이 Q&A 공유하기