Upload folder using huggingface_hub
Browse filesThis view is limited to 50 files because it contains too many changes. See raw diff
- diagrams-and-tables/annotations/cn_diagram_01.json +107 -0
- diagrams-and-tables/annotations/cn_diagram_02.json +101 -0
- diagrams-and-tables/annotations/cn_diagram_03.json +244 -0
- diagrams-and-tables/annotations/cn_diagram_04.json +89 -0
- diagrams-and-tables/annotations/cn_diagram_05.json +109 -0
- diagrams-and-tables/annotations/cn_diagram_06.json +150 -0
- diagrams-and-tables/annotations/cn_diagram_07.json +109 -0
- diagrams-and-tables/annotations/cn_diagram_08.json +118 -0
- diagrams-and-tables/annotations/cn_diagram_09.json +190 -0
- diagrams-and-tables/annotations/cn_diagram_10.json +177 -0
- diagrams-and-tables/annotations/cn_diagram_11.json +361 -0
- diagrams-and-tables/annotations/cn_diagram_12.json +261 -0
- diagrams-and-tables/annotations/cn_diagram_13.json +318 -0
- diagrams-and-tables/annotations/cn_diagram_14.json +165 -0
- diagrams-and-tables/annotations/cn_diagram_15.json +101 -0
- diagrams-and-tables/annotations/cn_diagram_16.json +301 -0
- diagrams-and-tables/annotations/cn_diagram_17.json +83 -0
- diagrams-and-tables/annotations/cn_diagram_18.json +177 -0
- diagrams-and-tables/annotations/cn_diagram_19.json +153 -0
- diagrams-and-tables/annotations/cn_diagram_20.json +218 -0
- diagrams-and-tables/annotations/cn_diagram_21.json +178 -0
- diagrams-and-tables/annotations/cn_diagram_22.json +262 -0
- diagrams-and-tables/annotations/cn_diagram_23.json +146 -0
- diagrams-and-tables/annotations/cn_diagram_24.json +252 -0
- diagrams-and-tables/annotations/cn_diagram_25.json +268 -0
- diagrams-and-tables/annotations/cn_diagram_26.json +211 -0
- diagrams-and-tables/annotations/cn_diagram_27.json +345 -0
- diagrams-and-tables/annotations/cn_diagram_28.json +265 -0
- diagrams-and-tables/annotations/cn_diagram_29.json +335 -0
- diagrams-and-tables/annotations/cn_diagram_30.json +149 -0
- diagrams-and-tables/annotations/cn_diagram_31.json +133 -0
- diagrams-and-tables/annotations/cn_diagram_32.json +89 -0
- diagrams-and-tables/annotations/cn_diagram_33.json +193 -0
- diagrams-and-tables/annotations/cn_diagram_34.json +81 -0
- diagrams-and-tables/annotations/cn_diagram_35.json +141 -0
- diagrams-and-tables/annotations/cn_diagram_36.json +169 -0
- diagrams-and-tables/annotations/cn_diagram_37.json +149 -0
- diagrams-and-tables/annotations/cn_diagram_38.json +105 -0
- diagrams-and-tables/annotations/cn_diagram_39.json +229 -0
- diagrams-and-tables/annotations/cn_diagram_40.json +132 -0
- diagrams-and-tables/annotations/cn_diagram_41.json +82 -0
- diagrams-and-tables/annotations/cn_diagram_42.json +95 -0
- diagrams-and-tables/annotations/cn_diagram_43.json +121 -0
- diagrams-and-tables/annotations/cn_diagram_44.json +269 -0
- diagrams-and-tables/annotations/cn_diagram_45.json +301 -0
- diagrams-and-tables/annotations/cn_diagram_46.json +105 -0
- diagrams-and-tables/annotations/cn_diagram_47.json +204 -0
- diagrams-and-tables/annotations/cn_diagram_48.json +111 -0
- diagrams-and-tables/annotations/cn_diagram_49.json +69 -0
- diagrams-and-tables/annotations/cn_diagram_50.json +85 -0
diagrams-and-tables/annotations/cn_diagram_01.json
ADDED
|
@@ -0,0 +1,107 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
[
|
| 2 |
+
{
|
| 3 |
+
"type": "title",
|
| 4 |
+
"text": "2.2.3 英特尔® Geti™ 平台"
|
| 5 |
+
},
|
| 6 |
+
{
|
| 7 |
+
"type": "title",
|
| 8 |
+
"text": "intel GeTi"
|
| 9 |
+
},
|
| 10 |
+
{
|
| 11 |
+
"type": "text",
|
| 12 |
+
"text": "英特尔® Geti™ 平台使企业团队能够快速构建计算机视觉 AI 模型。通过直观的图形界面,用户可以添加图像或视频数据、进行标注、训练、重新训练、导出以及优化 AI 模型以便部署。配备了最先进的技术,如主动学习、任务链和智能标注,英特尔® Geti™ 平台减少了劳动密集型任务,实现了协作模型开发,并加快了模型创建的速度。\n\n英特尔® Geti™ 平台提供的功能包括:\n\n• 定制化的计算机视觉任务:英特尔® Geti™ 平台加速了 AI 任务的模型创建,如分类、对象检测、语义分割或异常检测。\n• 直观的用户界面:英特尔® Geti™ 平台提供了便捷的图形用户界面和交互功能,如标注助手,允许几乎没有 AI 经验的团队成员协助计算机视觉模型训练。\n• 任务链:使用英特尔® Geti™ 平台,用户可以通过链接两个或更多任务来训练模型,而无需编写额外的代码,从而使用多步骤的智能应用程序。\n• 智能标注:英特尔® Geti™ 平台提供了使用铅笔、多边形工具和 OpenCV GrabCut 等绘图功能加速数据标注和图像分割,提高用户体验。\n• 超参数优化:英特尔® Geti™ 平台内置的优化方法使数据科学家的工作变得更加轻松,通过精炼对模型学习过程至关重要的超参数。\n• 生产就绪的模型:英特尔® Geti™ 平台输出的深度学习模型可以是 TensorFlow* 或 PyTorch* 格式。该平台还可以输出为 OpenVINO™ 工具包优化的模型,以便在英特尔® 架构的 CPU、GPU 和 VPU 上运行。"
|
| 13 |
+
},
|
| 14 |
+
{
|
| 15 |
+
"type": "title",
|
| 16 |
+
"text": "英特尔® Geti™ 平台的优势"
|
| 17 |
+
},
|
| 18 |
+
{
|
| 19 |
+
"type": "text",
|
| 20 |
+
"text": "• 节省时间:英特尔® Geti™ 平台通过提供一个无需编码的直观平台,帮助缩短开发 AI 应用计算机视觉模型所需的时间。这加快了通常需要长时间训练计划的自定义 AI 模型创建的工作流程。\n• 节省成本:英特尔® Geti™ 平台有助于消除进入 AI 领域的障碍(如培训或支付专业服务费用),使计算机视觉 AI 建模对各种组织更加容易和经济高效,特别是对于较小的公司来说。降低与人员培训相关的成本进一步增加了整体价值。\n• 灵活部署:英特尔® Geti™ 平台可以在本地部署或通过云虚拟机部署,为那些使用这两种基础设施之一或两者的组织提供灵活性。"
|
| 21 |
+
},
|
| 22 |
+
{
|
| 23 |
+
"type": "title",
|
| 24 |
+
"text": "英特尔® Geti™ 平台的使用流程示例"
|
| 25 |
+
},
|
| 26 |
+
{
|
| 27 |
+
"type": "diagram_caption",
|
| 28 |
+
"text": "图:使用英特尔® Geti™ 平台训练 AI 模型的流程示意图"
|
| 29 |
+
},
|
| 30 |
+
{
|
| 31 |
+
"type": "diagram",
|
| 32 |
+
"nodes": [
|
| 33 |
+
{
|
| 34 |
+
"id": "A",
|
| 35 |
+
"text": "1 数据收集"
|
| 36 |
+
},
|
| 37 |
+
{
|
| 38 |
+
"id": "B",
|
| 39 |
+
"text": "2 主动集"
|
| 40 |
+
},
|
| 41 |
+
{
|
| 42 |
+
"id": "C",
|
| 43 |
+
"text": "3 标注"
|
| 44 |
+
},
|
| 45 |
+
{
|
| 46 |
+
"id": "D",
|
| 47 |
+
"text": "4 训练"
|
| 48 |
+
},
|
| 49 |
+
{
|
| 50 |
+
"id": "E",
|
| 51 |
+
"text": "5 优化"
|
| 52 |
+
},
|
| 53 |
+
{
|
| 54 |
+
"id": "F",
|
| 55 |
+
"text": "6 导出"
|
| 56 |
+
}
|
| 57 |
+
],
|
| 58 |
+
"relationships": [
|
| 59 |
+
{
|
| 60 |
+
"source": "A",
|
| 61 |
+
"target": "B"
|
| 62 |
+
},
|
| 63 |
+
{
|
| 64 |
+
"source": "B",
|
| 65 |
+
"target": "C"
|
| 66 |
+
},
|
| 67 |
+
{
|
| 68 |
+
"source": "B",
|
| 69 |
+
"target": "D",
|
| 70 |
+
"label": "主动学习"
|
| 71 |
+
},
|
| 72 |
+
{
|
| 73 |
+
"source": "C",
|
| 74 |
+
"target": "D"
|
| 75 |
+
},
|
| 76 |
+
{
|
| 77 |
+
"source": "C",
|
| 78 |
+
"target": "D",
|
| 79 |
+
"label": "预测"
|
| 80 |
+
},
|
| 81 |
+
{
|
| 82 |
+
"source": "D",
|
| 83 |
+
"target": "E"
|
| 84 |
+
},
|
| 85 |
+
{
|
| 86 |
+
"source": "E",
|
| 87 |
+
"target": "F"
|
| 88 |
+
},
|
| 89 |
+
{
|
| 90 |
+
"source": "G",
|
| 91 |
+
"target": "C"
|
| 92 |
+
},
|
| 93 |
+
{
|
| 94 |
+
"source": "H",
|
| 95 |
+
"target": "B"
|
| 96 |
+
}
|
| 97 |
+
]
|
| 98 |
+
},
|
| 99 |
+
{
|
| 100 |
+
"type": "text",
|
| 101 |
+
"text": "02 英特尔® 技术方案"
|
| 102 |
+
},
|
| 103 |
+
{
|
| 104 |
+
"type": "page_number",
|
| 105 |
+
"text": "35"
|
| 106 |
+
}
|
| 107 |
+
]
|
diagrams-and-tables/annotations/cn_diagram_02.json
ADDED
|
@@ -0,0 +1,101 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
[
|
| 2 |
+
{
|
| 3 |
+
"type": "text",
|
| 4 |
+
"text": "机器学习模型部署在英特尔® 私有云中的高性能计算服务器上,使用英特尔® 至强® 可扩展处理器进行训练。模型在数十万张晶圆图像上训练之后,部署到生产线的边缘位置。边缘上的模型推理工作负载(在摄像头控制器上)可以卸载到英特尔® ARC A770 独立 GPU 上,以加速图像分析。英特尔® 至强® 可扩展处理器提供强大的计算能力来处理繁重的工作负载,加快训练过程。根据我们的经验,模型训练的速度比使用其他处理器快达 50%,现阶段每季度进行一次完整迭代训练流程(如下图)。"
|
| 5 |
+
},
|
| 6 |
+
{
|
| 7 |
+
"type": "diagram_caption",
|
| 8 |
+
"text": "Figure. Our solution spans the entire machine-learning lifecycle, from raw data acquisition and labeling to training and validation to deployment."
|
| 9 |
+
},
|
| 10 |
+
{
|
| 11 |
+
"type": "diagram",
|
| 12 |
+
"nodes": [
|
| 13 |
+
{
|
| 14 |
+
"id": "A",
|
| 15 |
+
"text": "Machine-Learning Lifecycle"
|
| 16 |
+
},
|
| 17 |
+
{
|
| 18 |
+
"id": "B",
|
| 19 |
+
"text": "Acquire Image"
|
| 20 |
+
},
|
| 21 |
+
{
|
| 22 |
+
"id": "C",
|
| 23 |
+
"text": "Label Data"
|
| 24 |
+
},
|
| 25 |
+
{
|
| 26 |
+
"id": "D",
|
| 27 |
+
"text": "Machine-Learning Model Training"
|
| 28 |
+
},
|
| 29 |
+
{
|
| 30 |
+
"id": "E",
|
| 31 |
+
"text": "Validation"
|
| 32 |
+
},
|
| 33 |
+
{
|
| 34 |
+
"id": "F",
|
| 35 |
+
"text": "Deployment"
|
| 36 |
+
}
|
| 37 |
+
],
|
| 38 |
+
"relationships": [
|
| 39 |
+
{
|
| 40 |
+
"source": "A",
|
| 41 |
+
"target": "B"
|
| 42 |
+
},
|
| 43 |
+
{
|
| 44 |
+
"source": "A",
|
| 45 |
+
"target": "C"
|
| 46 |
+
},
|
| 47 |
+
{
|
| 48 |
+
"source": "A",
|
| 49 |
+
"target": "D"
|
| 50 |
+
},
|
| 51 |
+
{
|
| 52 |
+
"source": "A",
|
| 53 |
+
"target": "E"
|
| 54 |
+
},
|
| 55 |
+
{
|
| 56 |
+
"source": "A",
|
| 57 |
+
"target": "F"
|
| 58 |
+
},
|
| 59 |
+
{
|
| 60 |
+
"source": "B",
|
| 61 |
+
"target": "C"
|
| 62 |
+
},
|
| 63 |
+
{
|
| 64 |
+
"source": "C",
|
| 65 |
+
"target": "D"
|
| 66 |
+
},
|
| 67 |
+
{
|
| 68 |
+
"source": "D",
|
| 69 |
+
"target": "E"
|
| 70 |
+
},
|
| 71 |
+
{
|
| 72 |
+
"source": "E",
|
| 73 |
+
"target": "F"
|
| 74 |
+
}
|
| 75 |
+
]
|
| 76 |
+
},
|
| 77 |
+
{
|
| 78 |
+
"type": "text",
|
| 79 |
+
"text": "收集的图像由包含 50 个底层核心算法的混合机器学习模型分析,包括各种如基于 ResNet50 的检查、语义剪辑分割(以实现像素级的缺陷识别)以及识别和测量(自动识别图像中的边缘类型和自动测量距离)等功能。模型经英特尔® OpenVINO™ 工具包优化,提高在英特尔® 硬件平台上的效率。工业视觉控制软件支持图像审查和模拟,所有功能以模块形式集成,便于扩展应用,支持低代码操作和流程向导。"
|
| 80 |
+
},
|
| 81 |
+
{
|
| 82 |
+
"type": "title",
|
| 83 |
+
"text": "方案优势"
|
| 84 |
+
},
|
| 85 |
+
{
|
| 86 |
+
"type": "text",
|
| 87 |
+
"text": "标准化设计实现了快速部署和易于扩展到新的用例。该解决方案能够准确识别晶圆研磨过程中的多种类型缺陷,包括凹痕、各种大小的划痕、研磨痕迹、污点、裂纹、气泡、晶圆偏移和安装偏移。与离线检查相比,使用在线检查可以更早地检测到多达 50% 的晶圆研磨问题。当警报响起时,可以对晶圆进行返工,这避免了下游过程中的整片晶圆分层。更重要的是,该解决方案超越了离线计量所能实现的:在问题发生时检测偏差,检测过程缺陷并迅速关闭工具,实现了检查框架清洁度和内环的新能力。\n\n帮助工厂实现业务效益:\n• 避免废品,每年为工厂节省高达 200 万美元。\n• 降低了业务风险。\n• 更高的产品质量。\n• 使工程师免于繁琐的手动离线检查。"
|
| 88 |
+
},
|
| 89 |
+
{
|
| 90 |
+
"type": "text",
|
| 91 |
+
"text": "03 成功案例"
|
| 92 |
+
},
|
| 93 |
+
{
|
| 94 |
+
"type": "footer",
|
| 95 |
+
"text": "intel."
|
| 96 |
+
},
|
| 97 |
+
{
|
| 98 |
+
"type": "page_number",
|
| 99 |
+
"text": "48"
|
| 100 |
+
}
|
| 101 |
+
]
|
diagrams-and-tables/annotations/cn_diagram_03.json
ADDED
|
@@ -0,0 +1,244 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
[
|
| 2 |
+
{
|
| 3 |
+
"type": "title",
|
| 4 |
+
"text": "4.2.3 工业电脑优选项目申请流程与节点安排"
|
| 5 |
+
},
|
| 6 |
+
{
|
| 7 |
+
"type": "title",
|
| 8 |
+
"text": "项目时间线"
|
| 9 |
+
},
|
| 10 |
+
{
|
| 11 |
+
"type": "diagram",
|
| 12 |
+
"nodes": [
|
| 13 |
+
{
|
| 14 |
+
"id": "A",
|
| 15 |
+
"text": "申请意向确认 提交申请材料"
|
| 16 |
+
},
|
| 17 |
+
{
|
| 18 |
+
"id": "B",
|
| 19 |
+
"text": "测试及验证申请"
|
| 20 |
+
},
|
| 21 |
+
{
|
| 22 |
+
"id": "C",
|
| 23 |
+
"text": "签发及相关测试函 市场推广活动"
|
| 24 |
+
}
|
| 25 |
+
],
|
| 26 |
+
"relationships": [
|
| 27 |
+
{
|
| 28 |
+
"source": "A",
|
| 29 |
+
"target": "B"
|
| 30 |
+
},
|
| 31 |
+
{
|
| 32 |
+
"source": "B",
|
| 33 |
+
"target": "C"
|
| 34 |
+
}
|
| 35 |
+
]
|
| 36 |
+
},
|
| 37 |
+
{
|
| 38 |
+
"type": "title",
|
| 39 |
+
"text": "项目流程"
|
| 40 |
+
},
|
| 41 |
+
{
|
| 42 |
+
"type": "diagram",
|
| 43 |
+
"nodes": [
|
| 44 |
+
{
|
| 45 |
+
"id": "A",
|
| 46 |
+
"text": "提交线上报名申请"
|
| 47 |
+
},
|
| 48 |
+
{
|
| 49 |
+
"id": "B",
|
| 50 |
+
"text": "发送申请材料(产品规格信息、报名表、第三方机构测试报告等)"
|
| 51 |
+
},
|
| 52 |
+
{
|
| 53 |
+
"id": "C",
|
| 54 |
+
"text": "英特尔项目团队初审"
|
| 55 |
+
},
|
| 56 |
+
{
|
| 57 |
+
"id": "D",
|
| 58 |
+
"text": "材料齐全?"
|
| 59 |
+
},
|
| 60 |
+
{
|
| 61 |
+
"id": "E",
|
| 62 |
+
"text": "客户使用软件调优测试工具测试并将寄送样机至英特尔复测"
|
| 63 |
+
},
|
| 64 |
+
{
|
| 65 |
+
"id": "F",
|
| 66 |
+
"text": "技术工程对接及验证"
|
| 67 |
+
},
|
| 68 |
+
{
|
| 69 |
+
"id": "G",
|
| 70 |
+
"text": "是否通过测试?"
|
| 71 |
+
},
|
| 72 |
+
{
|
| 73 |
+
"id": "H",
|
| 74 |
+
"text": "签发测试函"
|
| 75 |
+
},
|
| 76 |
+
{
|
| 77 |
+
"id": "I",
|
| 78 |
+
"text": "签收测试函"
|
| 79 |
+
},
|
| 80 |
+
{
|
| 81 |
+
"id": "J",
|
| 82 |
+
"text": "申请"
|
| 83 |
+
},
|
| 84 |
+
{
|
| 85 |
+
"id": "K",
|
| 86 |
+
"text": "验证"
|
| 87 |
+
},
|
| 88 |
+
{
|
| 89 |
+
"id": "L",
|
| 90 |
+
"text": "签发"
|
| 91 |
+
},
|
| 92 |
+
{
|
| 93 |
+
"id": "M",
|
| 94 |
+
"text": "客户"
|
| 95 |
+
},
|
| 96 |
+
{
|
| 97 |
+
"id": "N",
|
| 98 |
+
"text": "英特尔"
|
| 99 |
+
},
|
| 100 |
+
{
|
| 101 |
+
"id": "O",
|
| 102 |
+
"text": "20天"
|
| 103 |
+
},
|
| 104 |
+
{
|
| 105 |
+
"id": "P",
|
| 106 |
+
"text": "30天"
|
| 107 |
+
},
|
| 108 |
+
{
|
| 109 |
+
"id": "Q",
|
| 110 |
+
"text": "20天"
|
| 111 |
+
}
|
| 112 |
+
],
|
| 113 |
+
"relationships": [
|
| 114 |
+
{
|
| 115 |
+
"source": "A",
|
| 116 |
+
"target": "B"
|
| 117 |
+
},
|
| 118 |
+
{
|
| 119 |
+
"source": "A",
|
| 120 |
+
"target": "J"
|
| 121 |
+
},
|
| 122 |
+
{
|
| 123 |
+
"source": "A",
|
| 124 |
+
"target": "M"
|
| 125 |
+
},
|
| 126 |
+
{
|
| 127 |
+
"source": "B",
|
| 128 |
+
"target": "C"
|
| 129 |
+
},
|
| 130 |
+
{
|
| 131 |
+
"source": "B",
|
| 132 |
+
"target": "D",
|
| 133 |
+
"label": "否"
|
| 134 |
+
},
|
| 135 |
+
{
|
| 136 |
+
"source": "B",
|
| 137 |
+
"target": "J"
|
| 138 |
+
},
|
| 139 |
+
{
|
| 140 |
+
"source": "B",
|
| 141 |
+
"target": "M"
|
| 142 |
+
},
|
| 143 |
+
{
|
| 144 |
+
"source": "C",
|
| 145 |
+
"target": "D"
|
| 146 |
+
},
|
| 147 |
+
{
|
| 148 |
+
"source": "C",
|
| 149 |
+
"target": "J"
|
| 150 |
+
},
|
| 151 |
+
{
|
| 152 |
+
"source": "C",
|
| 153 |
+
"target": "N"
|
| 154 |
+
},
|
| 155 |
+
{
|
| 156 |
+
"source": "D",
|
| 157 |
+
"target": "F",
|
| 158 |
+
"label": "是"
|
| 159 |
+
},
|
| 160 |
+
{
|
| 161 |
+
"source": "D",
|
| 162 |
+
"target": "J"
|
| 163 |
+
},
|
| 164 |
+
{
|
| 165 |
+
"source": "D",
|
| 166 |
+
"target": "N"
|
| 167 |
+
},
|
| 168 |
+
{
|
| 169 |
+
"source": "E",
|
| 170 |
+
"target": "F"
|
| 171 |
+
},
|
| 172 |
+
{
|
| 173 |
+
"source": "E",
|
| 174 |
+
"target": "G",
|
| 175 |
+
"label": "否"
|
| 176 |
+
},
|
| 177 |
+
{
|
| 178 |
+
"source": "E",
|
| 179 |
+
"target": "K"
|
| 180 |
+
},
|
| 181 |
+
{
|
| 182 |
+
"source": "E",
|
| 183 |
+
"target": "M"
|
| 184 |
+
},
|
| 185 |
+
{
|
| 186 |
+
"source": "F",
|
| 187 |
+
"target": "G"
|
| 188 |
+
},
|
| 189 |
+
{
|
| 190 |
+
"source": "F",
|
| 191 |
+
"target": "K"
|
| 192 |
+
},
|
| 193 |
+
{
|
| 194 |
+
"source": "F",
|
| 195 |
+
"target": "N"
|
| 196 |
+
},
|
| 197 |
+
{
|
| 198 |
+
"source": "G",
|
| 199 |
+
"target": "H",
|
| 200 |
+
"label": "是"
|
| 201 |
+
},
|
| 202 |
+
{
|
| 203 |
+
"source": "G",
|
| 204 |
+
"target": "K"
|
| 205 |
+
},
|
| 206 |
+
{
|
| 207 |
+
"source": "G",
|
| 208 |
+
"target": "N"
|
| 209 |
+
},
|
| 210 |
+
{
|
| 211 |
+
"source": "H",
|
| 212 |
+
"target": "I"
|
| 213 |
+
},
|
| 214 |
+
{
|
| 215 |
+
"source": "H",
|
| 216 |
+
"target": "L"
|
| 217 |
+
},
|
| 218 |
+
{
|
| 219 |
+
"source": "H",
|
| 220 |
+
"target": "N"
|
| 221 |
+
},
|
| 222 |
+
{
|
| 223 |
+
"source": "I",
|
| 224 |
+
"target": "L"
|
| 225 |
+
},
|
| 226 |
+
{
|
| 227 |
+
"source": "I",
|
| 228 |
+
"target": "M"
|
| 229 |
+
}
|
| 230 |
+
]
|
| 231 |
+
},
|
| 232 |
+
{
|
| 233 |
+
"type": "text",
|
| 234 |
+
"text": "04 合作伙伴加速项目和产品推荐"
|
| 235 |
+
},
|
| 236 |
+
{
|
| 237 |
+
"type": "footer",
|
| 238 |
+
"text": "* 每家客户每个应用 x 等级最多只能申请一台机器\n** 每批次开放时间与名额有限,请您与英特尔客户经理联系锁定意向\n*** 锁定报名意向后,英特尔将向您发送线上报名链接,届时正式启动项目参与\n**** 流程中的天数为自然天天数"
|
| 239 |
+
},
|
| 240 |
+
{
|
| 241 |
+
"type": "page_number",
|
| 242 |
+
"text": "67"
|
| 243 |
+
}
|
| 244 |
+
]
|
diagrams-and-tables/annotations/cn_diagram_04.json
ADDED
|
@@ -0,0 +1,89 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
[
|
| 2 |
+
{
|
| 3 |
+
"type": "title",
|
| 4 |
+
"text": "4.3.5 养老信托"
|
| 5 |
+
},
|
| 6 |
+
{
|
| 7 |
+
"type": "text",
|
| 8 |
+
"text": "在信托行业回归本源的监管导向和社会养老需求增加的背景下,资产服务信托和公益慈善信托是目前养老信托的主要布局方向。\n养老信托不同于其他以获取投资收益为主要目标的金融产品,是指委托人(个人、家庭或法人)以养老资金管理、养老生活保障或养老慈善事业为核心目的,将财产委托给受托人(信托公司),信托公司根据合同约定向受益人(通常为委托人本人、家庭成员、公司员工、符合慈善信托标准的群体或组织等)提供财产保值增值、定期分配、养老规划及养老资源对接等信托业务安排。"
|
| 9 |
+
},
|
| 10 |
+
{
|
| 11 |
+
"type": "diagram_caption",
|
| 12 |
+
"text": "图表4-36 信托基本结构示意图"
|
| 13 |
+
},
|
| 14 |
+
{
|
| 15 |
+
"type": "diagram",
|
| 16 |
+
"nodes": [
|
| 17 |
+
{
|
| 18 |
+
"id": "A",
|
| 19 |
+
"text": "受托人"
|
| 20 |
+
},
|
| 21 |
+
{
|
| 22 |
+
"id": "B",
|
| 23 |
+
"text": "委托人"
|
| 24 |
+
},
|
| 25 |
+
{
|
| 26 |
+
"id": "C",
|
| 27 |
+
"text": "信托"
|
| 28 |
+
},
|
| 29 |
+
{
|
| 30 |
+
"id": "D",
|
| 31 |
+
"text": "受益人"
|
| 32 |
+
},
|
| 33 |
+
{
|
| 34 |
+
"id": "E",
|
| 35 |
+
"text": "财产保管"
|
| 36 |
+
},
|
| 37 |
+
{
|
| 38 |
+
"id": "F",
|
| 39 |
+
"text": "资产配置"
|
| 40 |
+
},
|
| 41 |
+
{
|
| 42 |
+
"id": "G",
|
| 43 |
+
"text": "运作服务"
|
| 44 |
+
},
|
| 45 |
+
{
|
| 46 |
+
"id": "H",
|
| 47 |
+
"text": "......"
|
| 48 |
+
}
|
| 49 |
+
],
|
| 50 |
+
"relationships": [
|
| 51 |
+
{
|
| 52 |
+
"source": "A",
|
| 53 |
+
"target": "C"
|
| 54 |
+
},
|
| 55 |
+
{
|
| 56 |
+
"source": "B",
|
| 57 |
+
"target": "C"
|
| 58 |
+
},
|
| 59 |
+
{
|
| 60 |
+
"source": "C",
|
| 61 |
+
"target": "D"
|
| 62 |
+
},
|
| 63 |
+
{
|
| 64 |
+
"source": "C",
|
| 65 |
+
"target": "E"
|
| 66 |
+
},
|
| 67 |
+
{
|
| 68 |
+
"source": "C",
|
| 69 |
+
"target": "F"
|
| 70 |
+
},
|
| 71 |
+
{
|
| 72 |
+
"source": "C",
|
| 73 |
+
"target": "G"
|
| 74 |
+
},
|
| 75 |
+
{
|
| 76 |
+
"source": "C",
|
| 77 |
+
"target": "H"
|
| 78 |
+
}
|
| 79 |
+
]
|
| 80 |
+
},
|
| 81 |
+
{
|
| 82 |
+
"type": "text",
|
| 83 |
+
"text": "● 发挥制度优势,“金融+非金融”服务属性凸显\n根据法律规定,信托财产独立保管、运作,且与委托人其他财产相隔离,能够有效保障信托财产的安全。\n信托能够横跨货币、资本、商品等多元市场投资,可构建广泛、动态、灵活的投资组合。\n信托灵活的架构下,委托人能够根据个性化养老需求,灵活设置信托财产的分配机制,有效应对多元化养老场景要求。\n● 业务模式多元,满足不同客群差异化养老需求\n资产服务信托模式:定制化的综合养老金融服务方案\n资产服务信托项下的财富管理服务信托成为信托赋能养老事业发展的主要载体,信托计划的委托人主要分为自然人或家庭/家族成员、法人或非法人组织两类。其中自然人或家庭/家族成员主要通过家族信托、家庭服务信托和保险金信托来实现养老目的;法人则主要通过法人及非法人组织财富管理信托,以达到为员工提供补充养老、补充医疗资金、关爱特定困难员工等福利的效果。"
|
| 84 |
+
},
|
| 85 |
+
{
|
| 86 |
+
"type": "page",
|
| 87 |
+
"page": 55
|
| 88 |
+
}
|
| 89 |
+
]
|
diagrams-and-tables/annotations/cn_diagram_05.json
ADDED
|
@@ -0,0 +1,109 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
[
|
| 2 |
+
{
|
| 3 |
+
"type": "title",
|
| 4 |
+
"text": "家族信托:为高净值人群提供一站式综合养老保障"
|
| 5 |
+
},
|
| 6 |
+
{
|
| 7 |
+
"type": "text",
|
| 8 |
+
"text": "● 家族信托以1000万元设立门槛,通过跨代际资产配置与定制化条款设计,覆盖养老、医疗、传承等多元场景。\n● 委托人将财产委托信托公司,设定受益人及分配规则(如定期领取养老金、医疗专项支付),依托受托人投研能力实现资产增值,并进行家族成员日常养老支出、高端康养服务采购及财富传承安排。\n● 受托人发挥资源整合优势,对接优质养老机构居住权益等非金融增值服务,形成“财富管理+养老服务”双轨闭环,系统性满足品质养老需求。"
|
| 9 |
+
},
|
| 10 |
+
{
|
| 11 |
+
"type": "diagram_caption",
|
| 12 |
+
"text": "图表4-37 养老主题家族信托架构示意"
|
| 13 |
+
},
|
| 14 |
+
{
|
| 15 |
+
"type": "diagram",
|
| 16 |
+
"nodes": [
|
| 17 |
+
{
|
| 18 |
+
"id": "A",
|
| 19 |
+
"text": "委托人"
|
| 20 |
+
},
|
| 21 |
+
{
|
| 22 |
+
"id": "B",
|
| 23 |
+
"text": "受托人"
|
| 24 |
+
},
|
| 25 |
+
{
|
| 26 |
+
"id": "C",
|
| 27 |
+
"text": "养老服务咨询机构"
|
| 28 |
+
},
|
| 29 |
+
{
|
| 30 |
+
"id": "D",
|
| 31 |
+
"text": "养老主题家族信托"
|
| 32 |
+
},
|
| 33 |
+
{
|
| 34 |
+
"id": "E",
|
| 35 |
+
"text": "资产管理产品"
|
| 36 |
+
},
|
| 37 |
+
{
|
| 38 |
+
"id": "F",
|
| 39 |
+
"text": "投资顾问(或有)"
|
| 40 |
+
},
|
| 41 |
+
{
|
| 42 |
+
"id": "G",
|
| 43 |
+
"text": "受益人"
|
| 44 |
+
}
|
| 45 |
+
],
|
| 46 |
+
"relationships": [
|
| 47 |
+
{
|
| 48 |
+
"source": "A",
|
| 49 |
+
"target": "B",
|
| 50 |
+
"label": "签订信托合同"
|
| 51 |
+
},
|
| 52 |
+
{
|
| 53 |
+
"source": "A",
|
| 54 |
+
"target": "D",
|
| 55 |
+
"label": "财产委托"
|
| 56 |
+
},
|
| 57 |
+
{
|
| 58 |
+
"source": "B",
|
| 59 |
+
"target": "D",
|
| 60 |
+
"label": "管理信托财产"
|
| 61 |
+
},
|
| 62 |
+
{
|
| 63 |
+
"source": "C",
|
| 64 |
+
"target": "D",
|
| 65 |
+
"label": "付费(或有)"
|
| 66 |
+
},
|
| 67 |
+
{
|
| 68 |
+
"source": "C",
|
| 69 |
+
"target": "G",
|
| 70 |
+
"label": "付费 提供养老服务"
|
| 71 |
+
},
|
| 72 |
+
{
|
| 73 |
+
"source": "D",
|
| 74 |
+
"target": "E",
|
| 75 |
+
"label": "获取收益"
|
| 76 |
+
},
|
| 77 |
+
{
|
| 78 |
+
"source": "D",
|
| 79 |
+
"target": "F",
|
| 80 |
+
"label": "投资指令"
|
| 81 |
+
},
|
| 82 |
+
{
|
| 83 |
+
"source": "D",
|
| 84 |
+
"target": "G",
|
| 85 |
+
"label": "信托利益分配"
|
| 86 |
+
}
|
| 87 |
+
]
|
| 88 |
+
},
|
| 89 |
+
{
|
| 90 |
+
"type": "title",
|
| 91 |
+
"text": "家庭服务信托:综合财富管理服务的普惠化实践"
|
| 92 |
+
},
|
| 93 |
+
{
|
| 94 |
+
"type": "text",
|
| 95 |
+
"text": "● 家庭服务信托是信托三分类新规后的创新型业务,也是家族信托模式的“普惠型”实践,设立门槛为100万元,相较家族信托大幅降低,让更多大众富裕家庭有机会运用信托工具实现家庭财富保护和养老规划等多样化目的。\n● 家庭服务信托与家族信托的业务架构较为相似,但明确了不低于5年的信托期限和标准化的配置范围,提供更符合大众家庭的资产配置服务。"
|
| 96 |
+
},
|
| 97 |
+
{
|
| 98 |
+
"type": "title",
|
| 99 |
+
"text": "保险金信托:融合保险保障与养老规划双重优势"
|
| 100 |
+
},
|
| 101 |
+
{
|
| 102 |
+
"type": "text",
|
| 103 |
+
"text": "● 保险金信托是指信托公司接受单一自然人委托,或者接受单一自然人及其家庭成员共同委托,以人身保险合同的相关权利和对应利益以及后续支付保费所需资金作为信托财产设立信托。\n● 当保险合同约定的给付条件发生时,保险公司按照保险约定将对应资金划付至对应信托专户,由信托公司按照信托文件管理。"
|
| 104 |
+
},
|
| 105 |
+
{
|
| 106 |
+
"type": "page",
|
| 107 |
+
"page": 56
|
| 108 |
+
}
|
| 109 |
+
]
|
diagrams-and-tables/annotations/cn_diagram_06.json
ADDED
|
@@ -0,0 +1,150 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
[
|
| 2 |
+
{
|
| 3 |
+
"type": "title",
|
| 4 |
+
"text": "法人及非法人组织财富管理信托:企业为员工提供补充养老福利的重要途径"
|
| 5 |
+
},
|
| 6 |
+
{
|
| 7 |
+
"type": "text",
|
| 8 |
+
"text": "● 法人及非法人组织财富管理信托以1000万元为设立门槛,能够借助信托的功能实现多元目的。其中,以薪酬福利管理为信托目的、公司员工作为受益人的信托架构,能够为员工提供补充养老资金等各类福利。"
|
| 9 |
+
},
|
| 10 |
+
{
|
| 11 |
+
"type": "diagram_caption",
|
| 12 |
+
"text": "图表4-38 养老主题法人及非法人组织财富管理信托部分框架"
|
| 13 |
+
},
|
| 14 |
+
{
|
| 15 |
+
"type": "diagram",
|
| 16 |
+
"nodes": [
|
| 17 |
+
{
|
| 18 |
+
"id": "A",
|
| 19 |
+
"text": "委托人(企业)"
|
| 20 |
+
},
|
| 21 |
+
{
|
| 22 |
+
"id": "B",
|
| 23 |
+
"text": "受托人"
|
| 24 |
+
},
|
| 25 |
+
{
|
| 26 |
+
"id": "C",
|
| 27 |
+
"text": "企业补充养老信托"
|
| 28 |
+
},
|
| 29 |
+
{
|
| 30 |
+
"id": "D",
|
| 31 |
+
"text": "资产管理产品"
|
| 32 |
+
},
|
| 33 |
+
{
|
| 34 |
+
"id": "E",
|
| 35 |
+
"text": "受益人员工1"
|
| 36 |
+
},
|
| 37 |
+
{
|
| 38 |
+
"id": "F",
|
| 39 |
+
"text": "受益人员工2"
|
| 40 |
+
},
|
| 41 |
+
{
|
| 42 |
+
"id": "G",
|
| 43 |
+
"text": "受益人员工3"
|
| 44 |
+
},
|
| 45 |
+
{
|
| 46 |
+
"id": "H",
|
| 47 |
+
"text": "......"
|
| 48 |
+
}
|
| 49 |
+
],
|
| 50 |
+
"relationships": [
|
| 51 |
+
{
|
| 52 |
+
"source": "A",
|
| 53 |
+
"label": "签订信托合同"
|
| 54 |
+
},
|
| 55 |
+
{
|
| 56 |
+
"source": "A",
|
| 57 |
+
"target": "C",
|
| 58 |
+
"label": "财产 委托"
|
| 59 |
+
},
|
| 60 |
+
{
|
| 61 |
+
"source": "B",
|
| 62 |
+
"target": "C",
|
| 63 |
+
"label": "管理信托财产"
|
| 64 |
+
},
|
| 65 |
+
{
|
| 66 |
+
"source": "C",
|
| 67 |
+
"target": "D",
|
| 68 |
+
"label": "获取收益"
|
| 69 |
+
},
|
| 70 |
+
{
|
| 71 |
+
"source": "C",
|
| 72 |
+
"target": "E",
|
| 73 |
+
"label": "信托利益分配"
|
| 74 |
+
},
|
| 75 |
+
{
|
| 76 |
+
"source": "C",
|
| 77 |
+
"target": "F",
|
| 78 |
+
"label": "信托利益分配"
|
| 79 |
+
},
|
| 80 |
+
{
|
| 81 |
+
"source": "C",
|
| 82 |
+
"target": "G",
|
| 83 |
+
"label": "信托利益分配"
|
| 84 |
+
},
|
| 85 |
+
{
|
| 86 |
+
"source": "C",
|
| 87 |
+
"target": "H",
|
| 88 |
+
"label": "信托利益分配"
|
| 89 |
+
}
|
| 90 |
+
]
|
| 91 |
+
},
|
| 92 |
+
{
|
| 93 |
+
"type": "text",
|
| 94 |
+
"text": "● 此外,委托人还可借助该信托架构实现员工股权激励、薪酬递延支付等效果。同时,也可以通过其他行政服务管理信托的模式,实现对特定困难员工的关怀,包括对其养老生活的额外支持。"
|
| 95 |
+
},
|
| 96 |
+
{
|
| 97 |
+
"type": "title",
|
| 98 |
+
"text": "● 公益慈善信托模式:助力养老公益事业“向上向善”"
|
| 99 |
+
},
|
| 100 |
+
{
|
| 101 |
+
"type": "text",
|
| 102 |
+
"text": "● 在政策引导和社会需求下,养老慈善信托已经成为推动养老慈善事业发展的有力工具,数量持续扩容。在2024年全年新设的慈善信托中,信托目的涵盖扶老助老的慈善信托共155单,占比28.8%。履行了金融服务实体经济和社会民生的天职,实现了金融服务与社会公益的双赢。\n● 养老慈善信托通过信托架构,一方面帮助企业和高净值人群灵活、高效、可持续地管理慈善财产、实现慈善意愿;另一方面通过支持社会养老福利事业、资助养老慈善项目,使得广大老年群体、尤其是处于困境中的老年群体受益,是多层次养老保障体系的重要组成部分。\n● 养老慈善信托支持的慈善项目范畴广泛,包括:机构及社区养老设施及服务建设、特困老人救助、老年健康关怀、老年文化活动、养老慈善行业发展及人才培训等多个维度,以多元化的方式助力养老事业发展。"
|
| 103 |
+
},
|
| 104 |
+
{
|
| 105 |
+
"type": "diagram_caption",
|
| 106 |
+
"text": "图表4-39 养老慈善信托架构示意"
|
| 107 |
+
},
|
| 108 |
+
{
|
| 109 |
+
"type": "diagram",
|
| 110 |
+
"nodes": [
|
| 111 |
+
{
|
| 112 |
+
"id": "A",
|
| 113 |
+
"text": "委托人"
|
| 114 |
+
},
|
| 115 |
+
{
|
| 116 |
+
"id": "B",
|
| 117 |
+
"text": "养老慈善信托"
|
| 118 |
+
},
|
| 119 |
+
{
|
| 120 |
+
"id": "C",
|
| 121 |
+
"text": "养老相关慈善组织"
|
| 122 |
+
},
|
| 123 |
+
{
|
| 124 |
+
"id": "D",
|
| 125 |
+
"text": "老年群体"
|
| 126 |
+
}
|
| 127 |
+
],
|
| 128 |
+
"relationships": [
|
| 129 |
+
{
|
| 130 |
+
"source": "A",
|
| 131 |
+
"target": "B",
|
| 132 |
+
"label": "委托设立"
|
| 133 |
+
},
|
| 134 |
+
{
|
| 135 |
+
"source": "B",
|
| 136 |
+
"target": "C",
|
| 137 |
+
"label": "委托执行"
|
| 138 |
+
},
|
| 139 |
+
{
|
| 140 |
+
"source": "C",
|
| 141 |
+
"target": "D",
|
| 142 |
+
"label": "开展慈善活动"
|
| 143 |
+
}
|
| 144 |
+
]
|
| 145 |
+
},
|
| 146 |
+
{
|
| 147 |
+
"type": "page",
|
| 148 |
+
"page": 57
|
| 149 |
+
}
|
| 150 |
+
]
|
diagrams-and-tables/annotations/cn_diagram_07.json
ADDED
|
@@ -0,0 +1,109 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
[
|
| 2 |
+
{
|
| 3 |
+
"type": "title",
|
| 4 |
+
"text": "第一章 AI PC 的历史使命:\nAI 普惠首选终端"
|
| 5 |
+
},
|
| 6 |
+
{
|
| 7 |
+
"type": "text",
|
| 8 |
+
"text": "人工智能的需求正在爆发,大模型开启了普惠于人的路程。用户不仅需要公共的大模型服务,更需要的是专属自己的个人大模型。个人大模型将依托混合人工智能的方式,逐步实现普惠。我们看到,个人大模型的普惠要求和 PC 的承载优势完美契合,显示着 PC 将再一次承载技术普惠的历史使命,成为 AI 普惠的首选终端。"
|
| 9 |
+
},
|
| 10 |
+
{
|
| 11 |
+
"type": "diagram_caption",
|
| 12 |
+
"text": "图 1 PC 与 AI 大模型的天然匹配"
|
| 13 |
+
},
|
| 14 |
+
{
|
| 15 |
+
"type": "diagram",
|
| 16 |
+
"nodes": [
|
| 17 |
+
{
|
| 18 |
+
"id": "A",
|
| 19 |
+
"text": "能进行多模态自然语言交互"
|
| 20 |
+
},
|
| 21 |
+
{
|
| 22 |
+
"id": "B",
|
| 23 |
+
"text": "压缩后依然具备通用场景服务能力"
|
| 24 |
+
},
|
| 25 |
+
{
|
| 26 |
+
"id": "C",
|
| 27 |
+
"text": "需要强 AI 算力进行推理"
|
| 28 |
+
},
|
| 29 |
+
{
|
| 30 |
+
"id": "D",
|
| 31 |
+
"text": "需要基于个人数据和隐私信息进行微调和个性化服务"
|
| 32 |
+
},
|
| 33 |
+
{
|
| 34 |
+
"id": "E",
|
| 35 |
+
"text": "个人大模型"
|
| 36 |
+
},
|
| 37 |
+
{
|
| 38 |
+
"id": "F",
|
| 39 |
+
"text": "PC"
|
| 40 |
+
},
|
| 41 |
+
{
|
| 42 |
+
"id": "G",
|
| 43 |
+
"text": "具备全模态人机自然交互条件"
|
| 44 |
+
},
|
| 45 |
+
{
|
| 46 |
+
"id": "H",
|
| 47 |
+
"text": "承载最多场景的个人通用设备"
|
| 48 |
+
},
|
| 49 |
+
{
|
| 50 |
+
"id": "I",
|
| 51 |
+
"text": "最强的个人计算平台"
|
| 52 |
+
},
|
| 53 |
+
{
|
| 54 |
+
"id": "J",
|
| 55 |
+
"text": "存储容量最大、最受信赖的安全终端"
|
| 56 |
+
}
|
| 57 |
+
],
|
| 58 |
+
"relationships": [
|
| 59 |
+
{
|
| 60 |
+
"source": "A",
|
| 61 |
+
"target": "E"
|
| 62 |
+
},
|
| 63 |
+
{
|
| 64 |
+
"source": "B",
|
| 65 |
+
"target": "E"
|
| 66 |
+
},
|
| 67 |
+
{
|
| 68 |
+
"source": "C",
|
| 69 |
+
"target": "E"
|
| 70 |
+
},
|
| 71 |
+
{
|
| 72 |
+
"source": "D",
|
| 73 |
+
"target": "E"
|
| 74 |
+
},
|
| 75 |
+
{
|
| 76 |
+
"source": "E",
|
| 77 |
+
"target": "F"
|
| 78 |
+
},
|
| 79 |
+
{
|
| 80 |
+
"source": "F",
|
| 81 |
+
"target": "G"
|
| 82 |
+
},
|
| 83 |
+
{
|
| 84 |
+
"source": "F",
|
| 85 |
+
"target": "H"
|
| 86 |
+
},
|
| 87 |
+
{
|
| 88 |
+
"source": "F",
|
| 89 |
+
"target": "I"
|
| 90 |
+
},
|
| 91 |
+
{
|
| 92 |
+
"source": "F",
|
| 93 |
+
"target": "J"
|
| 94 |
+
}
|
| 95 |
+
]
|
| 96 |
+
},
|
| 97 |
+
{
|
| 98 |
+
"type": "text",
|
| 99 |
+
"text": "来源: IDC, 2023"
|
| 100 |
+
},
|
| 101 |
+
{
|
| 102 |
+
"type": "footer",
|
| 103 |
+
"text": "IDC | Lenovo 联想"
|
| 104 |
+
},
|
| 105 |
+
{
|
| 106 |
+
"type": "page_number",
|
| 107 |
+
"text": "4"
|
| 108 |
+
}
|
| 109 |
+
]
|
diagrams-and-tables/annotations/cn_diagram_08.json
ADDED
|
@@ -0,0 +1,118 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
[
|
| 2 |
+
{
|
| 3 |
+
"type": "header",
|
| 4 |
+
"text": "AI PC 产业 (中国) 白皮书"
|
| 5 |
+
},
|
| 6 |
+
{
|
| 7 |
+
"type": "diagram_caption",
|
| 8 |
+
"text": "图 5 个人智能体提升 AI PC 的自主性与易用性"
|
| 9 |
+
},
|
| 10 |
+
{
|
| 11 |
+
"type": "diagram",
|
| 12 |
+
"nodes": [
|
| 13 |
+
{
|
| 14 |
+
"id": "A",
|
| 15 |
+
"text": "用户图标"
|
| 16 |
+
},
|
| 17 |
+
{
|
| 18 |
+
"id": "B",
|
| 19 |
+
"text": "自然语言交互 UI"
|
| 20 |
+
},
|
| 21 |
+
{
|
| 22 |
+
"id": "C",
|
| 23 |
+
"text": "意图理解 & 多任务分发平台 (基于个人本地大模型)"
|
| 24 |
+
},
|
| 25 |
+
{
|
| 26 |
+
"id": "D",
|
| 27 |
+
"text": "个性化本地知识库"
|
| 28 |
+
},
|
| 29 |
+
{
|
| 30 |
+
"id": "E",
|
| 31 |
+
"text": "个人智能体"
|
| 32 |
+
},
|
| 33 |
+
{
|
| 34 |
+
"id": "F",
|
| 35 |
+
"text": "本地模型"
|
| 36 |
+
},
|
| 37 |
+
{
|
| 38 |
+
"id": "G",
|
| 39 |
+
"text": "云端模型"
|
| 40 |
+
},
|
| 41 |
+
{
|
| 42 |
+
"id": "H",
|
| 43 |
+
"text": "应用"
|
| 44 |
+
},
|
| 45 |
+
{
|
| 46 |
+
"id": "I",
|
| 47 |
+
"text": "设备"
|
| 48 |
+
}
|
| 49 |
+
],
|
| 50 |
+
"relationships": [
|
| 51 |
+
{
|
| 52 |
+
"source": "A",
|
| 53 |
+
"target": "B"
|
| 54 |
+
},
|
| 55 |
+
{
|
| 56 |
+
"source": "B",
|
| 57 |
+
"target": "C"
|
| 58 |
+
},
|
| 59 |
+
{
|
| 60 |
+
"source": "C",
|
| 61 |
+
"target": "D",
|
| 62 |
+
"label": "查询知识库\n反馈新的 prompt"
|
| 63 |
+
},
|
| 64 |
+
{
|
| 65 |
+
"source": "B",
|
| 66 |
+
"target": "E"
|
| 67 |
+
},
|
| 68 |
+
{
|
| 69 |
+
"source": "C",
|
| 70 |
+
"target": "E"
|
| 71 |
+
},
|
| 72 |
+
{
|
| 73 |
+
"source": "E",
|
| 74 |
+
"target": "F",
|
| 75 |
+
"label": "模型调用\n反馈结果"
|
| 76 |
+
},
|
| 77 |
+
{
|
| 78 |
+
"source": "E",
|
| 79 |
+
"target": "G",
|
| 80 |
+
"label": "模型调用\n反馈结果"
|
| 81 |
+
},
|
| 82 |
+
{
|
| 83 |
+
"source": "E",
|
| 84 |
+
"target": "H",
|
| 85 |
+
"label": "应用 API 调用\n反馈结果"
|
| 86 |
+
},
|
| 87 |
+
{
|
| 88 |
+
"source": "E",
|
| 89 |
+
"target": "I",
|
| 90 |
+
"label": "操作设备功能\n返回操作结果"
|
| 91 |
+
}
|
| 92 |
+
]
|
| 93 |
+
},
|
| 94 |
+
{
|
| 95 |
+
"type": "text",
|
| 96 |
+
"text": "来源: IDC, 2023"
|
| 97 |
+
},
|
| 98 |
+
{
|
| 99 |
+
"type": "title",
|
| 100 |
+
"text": "终端内嵌个人大模型"
|
| 101 |
+
},
|
| 102 |
+
{
|
| 103 |
+
"type": "title",
|
| 104 |
+
"text": "本地为主,边缘与云为辅的大模型方案"
|
| 105 |
+
},
|
| 106 |
+
{
|
| 107 |
+
"type": "text",
|
| 108 |
+
"text": "随着用户对 AI 能力和大模型的调用变得像使用办公软件一样频繁,仅依赖云端提供相应的能力就变得昂贵、复杂且不够安全。因此,以模型的本地化推理为主,以边缘和云端推理为辅的混合大模型架构成为 AI PC 解决这一问题的关键。\n\n用户的大部分任务将能够依托 AI PC 本地模型完成。例如,用户能够在离线的情况下依靠本地大模型完成通过文字描述生成文档和 PPT 的任务。同时,本地模型还将承担意图理解和任务分配的功能,是个人智能体的底座。"
|
| 109 |
+
},
|
| 110 |
+
{
|
| 111 |
+
"type": "footer",
|
| 112 |
+
"text": "IDC | Lenovo 联想"
|
| 113 |
+
},
|
| 114 |
+
{
|
| 115 |
+
"type": "page_number",
|
| 116 |
+
"text": "17"
|
| 117 |
+
}
|
| 118 |
+
]
|
diagrams-and-tables/annotations/cn_diagram_09.json
ADDED
|
@@ -0,0 +1,190 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
[
|
| 2 |
+
{
|
| 3 |
+
"type": "title",
|
| 4 |
+
"text": "第三章 AI PC 的产业生态:\n以人为本、终端主导、AI 原生"
|
| 5 |
+
},
|
| 6 |
+
{
|
| 7 |
+
"type": "text",
|
| 8 |
+
"text": "在 AI PC 的推动下,PC 产业生态将从应用为本转向以人为本,从应用驱动转变为意图驱动。传统 PC 产业生态以操作系统为基础,用户在系统界面中直接进行操作,并管理和应用各式各样的应用程序。AI PC 产业生态中,个人智能体将成为第一入口,在大模型与应用生态的支持下,准确理解用户指令,给出恰当的反馈,跨应用进行调度,进而完成相对复杂的任务。模型、应用、算力厂商都需要围绕 AI PC(终端)形态下新的以人为本的需求做出改变,在研发工作中对 AI 的高效运行予以充分的考量,以适应 AI PC 新时代。"
|
| 9 |
+
},
|
| 10 |
+
{
|
| 11 |
+
"type": "diagram_caption",
|
| 12 |
+
"text": "图 7 PC 产业生态变革图"
|
| 13 |
+
},
|
| 14 |
+
{
|
| 15 |
+
"type": "diagram",
|
| 16 |
+
"nodes": [
|
| 17 |
+
{
|
| 18 |
+
"id": "A",
|
| 19 |
+
"text": "传统 PC 产业生态"
|
| 20 |
+
},
|
| 21 |
+
{
|
| 22 |
+
"id": "B",
|
| 23 |
+
"text": "用户"
|
| 24 |
+
},
|
| 25 |
+
{
|
| 26 |
+
"id": "C",
|
| 27 |
+
"text": "应用"
|
| 28 |
+
},
|
| 29 |
+
{
|
| 30 |
+
"id": "D",
|
| 31 |
+
"text": "功能"
|
| 32 |
+
},
|
| 33 |
+
{
|
| 34 |
+
"id": "E",
|
| 35 |
+
"text": "数据"
|
| 36 |
+
},
|
| 37 |
+
{
|
| 38 |
+
"id": "F",
|
| 39 |
+
"text": "操作系统"
|
| 40 |
+
},
|
| 41 |
+
{
|
| 42 |
+
"id": "G",
|
| 43 |
+
"text": "通用计算 / 芯片"
|
| 44 |
+
},
|
| 45 |
+
{
|
| 46 |
+
"id": "H",
|
| 47 |
+
"text": "AI PC 产业生态"
|
| 48 |
+
},
|
| 49 |
+
{
|
| 50 |
+
"id": "I",
|
| 51 |
+
"text": "用户"
|
| 52 |
+
},
|
| 53 |
+
{
|
| 54 |
+
"id": "J",
|
| 55 |
+
"text": "个人智能体"
|
| 56 |
+
},
|
| 57 |
+
{
|
| 58 |
+
"id": "K",
|
| 59 |
+
"text": "应用"
|
| 60 |
+
},
|
| 61 |
+
{
|
| 62 |
+
"id": "L",
|
| 63 |
+
"text": "模型"
|
| 64 |
+
},
|
| 65 |
+
{
|
| 66 |
+
"id": "M",
|
| 67 |
+
"text": "混合算力 / 芯片"
|
| 68 |
+
}
|
| 69 |
+
],
|
| 70 |
+
"relationships": [
|
| 71 |
+
{
|
| 72 |
+
"source": "A",
|
| 73 |
+
"target": "B"
|
| 74 |
+
},
|
| 75 |
+
{
|
| 76 |
+
"source": "A",
|
| 77 |
+
"target": "C"
|
| 78 |
+
},
|
| 79 |
+
{
|
| 80 |
+
"source": "A",
|
| 81 |
+
"target": "D"
|
| 82 |
+
},
|
| 83 |
+
{
|
| 84 |
+
"source": "A",
|
| 85 |
+
"target": "E"
|
| 86 |
+
},
|
| 87 |
+
{
|
| 88 |
+
"source": "A",
|
| 89 |
+
"target": "F"
|
| 90 |
+
},
|
| 91 |
+
{
|
| 92 |
+
"source": "A",
|
| 93 |
+
"target": "G"
|
| 94 |
+
},
|
| 95 |
+
{
|
| 96 |
+
"source": "B",
|
| 97 |
+
"target": "C"
|
| 98 |
+
},
|
| 99 |
+
{
|
| 100 |
+
"source": "B",
|
| 101 |
+
"target": "F"
|
| 102 |
+
},
|
| 103 |
+
{
|
| 104 |
+
"source": "C",
|
| 105 |
+
"target": "D"
|
| 106 |
+
},
|
| 107 |
+
{
|
| 108 |
+
"source": "C",
|
| 109 |
+
"target": "E"
|
| 110 |
+
},
|
| 111 |
+
{
|
| 112 |
+
"source": "C",
|
| 113 |
+
"target": "F"
|
| 114 |
+
},
|
| 115 |
+
{
|
| 116 |
+
"source": "D",
|
| 117 |
+
"target": "G"
|
| 118 |
+
},
|
| 119 |
+
{
|
| 120 |
+
"source": "E",
|
| 121 |
+
"target": "F"
|
| 122 |
+
},
|
| 123 |
+
{
|
| 124 |
+
"source": "E",
|
| 125 |
+
"target": "G"
|
| 126 |
+
},
|
| 127 |
+
{
|
| 128 |
+
"source": "F",
|
| 129 |
+
"target": "G"
|
| 130 |
+
},
|
| 131 |
+
{
|
| 132 |
+
"source": "H",
|
| 133 |
+
"target": "I"
|
| 134 |
+
},
|
| 135 |
+
{
|
| 136 |
+
"source": "H",
|
| 137 |
+
"target": "J"
|
| 138 |
+
},
|
| 139 |
+
{
|
| 140 |
+
"source": "H",
|
| 141 |
+
"target": "K"
|
| 142 |
+
},
|
| 143 |
+
{
|
| 144 |
+
"source": "H",
|
| 145 |
+
"target": "L"
|
| 146 |
+
},
|
| 147 |
+
{
|
| 148 |
+
"source": "H",
|
| 149 |
+
"target": "M"
|
| 150 |
+
},
|
| 151 |
+
{
|
| 152 |
+
"source": "I",
|
| 153 |
+
"target": "J"
|
| 154 |
+
},
|
| 155 |
+
{
|
| 156 |
+
"source": "J",
|
| 157 |
+
"target": "K"
|
| 158 |
+
},
|
| 159 |
+
{
|
| 160 |
+
"source": "J",
|
| 161 |
+
"target": "L"
|
| 162 |
+
},
|
| 163 |
+
{
|
| 164 |
+
"source": "K",
|
| 165 |
+
"target": "M"
|
| 166 |
+
},
|
| 167 |
+
{
|
| 168 |
+
"source": "L",
|
| 169 |
+
"target": "M"
|
| 170 |
+
},
|
| 171 |
+
{
|
| 172 |
+
"source": "A",
|
| 173 |
+
"target": "H",
|
| 174 |
+
"label": "变革"
|
| 175 |
+
}
|
| 176 |
+
]
|
| 177 |
+
},
|
| 178 |
+
{
|
| 179 |
+
"type": "text",
|
| 180 |
+
"text": "来源: IDC, 2023"
|
| 181 |
+
},
|
| 182 |
+
{
|
| 183 |
+
"type": "footer",
|
| 184 |
+
"text": "IDC | Lenovo 联想"
|
| 185 |
+
},
|
| 186 |
+
{
|
| 187 |
+
"type": "page_number",
|
| 188 |
+
"text": "23"
|
| 189 |
+
}
|
| 190 |
+
]
|
diagrams-and-tables/annotations/cn_diagram_10.json
ADDED
|
@@ -0,0 +1,177 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
[
|
| 2 |
+
{
|
| 3 |
+
"type": "text",
|
| 4 |
+
"text": "随着 AI 技术的不断进步,越来越多的企业加入 AI PC 的开放生态,形成用户、终端厂商、模型、应用、算力多层开放的繁荣生态。用户视野将发生变化,模型与应用的新关系将改变用户需求的底层逻辑。用户的需求是推动整个生态发展的关键要素,而终端厂商以场景需求为基础面向用户整合产业资源,提供软硬件一体的混合交付体验。模型厂商、芯片厂商也将与终端厂商产生更加紧密地联结。"
|
| 5 |
+
},
|
| 6 |
+
{
|
| 7 |
+
"type": "diagram_caption",
|
| 8 |
+
"text": "图 8 产业内供给关系变化"
|
| 9 |
+
},
|
| 10 |
+
{
|
| 11 |
+
"type": "diagram",
|
| 12 |
+
"nodes": [
|
| 13 |
+
{
|
| 14 |
+
"id": "A",
|
| 15 |
+
"text": "现在"
|
| 16 |
+
},
|
| 17 |
+
{
|
| 18 |
+
"id": "B",
|
| 19 |
+
"text": "用户"
|
| 20 |
+
},
|
| 21 |
+
{
|
| 22 |
+
"id": "C",
|
| 23 |
+
"text": "应用"
|
| 24 |
+
},
|
| 25 |
+
{
|
| 26 |
+
"id": "D",
|
| 27 |
+
"text": "终端厂商"
|
| 28 |
+
},
|
| 29 |
+
{
|
| 30 |
+
"id": "E",
|
| 31 |
+
"text": "模型"
|
| 32 |
+
},
|
| 33 |
+
{
|
| 34 |
+
"id": "F",
|
| 35 |
+
"text": "芯片"
|
| 36 |
+
},
|
| 37 |
+
{
|
| 38 |
+
"id": "G",
|
| 39 |
+
"text": "未来"
|
| 40 |
+
},
|
| 41 |
+
{
|
| 42 |
+
"id": "H",
|
| 43 |
+
"text": "用户"
|
| 44 |
+
},
|
| 45 |
+
{
|
| 46 |
+
"id": "I",
|
| 47 |
+
"text": "应用 / 插件"
|
| 48 |
+
},
|
| 49 |
+
{
|
| 50 |
+
"id": "J",
|
| 51 |
+
"text": "终端厂商"
|
| 52 |
+
},
|
| 53 |
+
{
|
| 54 |
+
"id": "K",
|
| 55 |
+
"text": "大模型"
|
| 56 |
+
},
|
| 57 |
+
{
|
| 58 |
+
"id": "L",
|
| 59 |
+
"text": "芯片"
|
| 60 |
+
},
|
| 61 |
+
{
|
| 62 |
+
"id": "M",
|
| 63 |
+
"text": "具备 AI 环境"
|
| 64 |
+
}
|
| 65 |
+
],
|
| 66 |
+
"relationships": [
|
| 67 |
+
{
|
| 68 |
+
"source": "A",
|
| 69 |
+
"target": "B"
|
| 70 |
+
},
|
| 71 |
+
{
|
| 72 |
+
"source": "A",
|
| 73 |
+
"target": "C"
|
| 74 |
+
},
|
| 75 |
+
{
|
| 76 |
+
"source": "A",
|
| 77 |
+
"target": "D"
|
| 78 |
+
},
|
| 79 |
+
{
|
| 80 |
+
"source": "A",
|
| 81 |
+
"target": "E"
|
| 82 |
+
},
|
| 83 |
+
{
|
| 84 |
+
"source": "A",
|
| 85 |
+
"target": "F"
|
| 86 |
+
},
|
| 87 |
+
{
|
| 88 |
+
"source": "B",
|
| 89 |
+
"target": "C"
|
| 90 |
+
},
|
| 91 |
+
{
|
| 92 |
+
"source": "B",
|
| 93 |
+
"target": "D"
|
| 94 |
+
},
|
| 95 |
+
{
|
| 96 |
+
"source": "C",
|
| 97 |
+
"target": "D"
|
| 98 |
+
},
|
| 99 |
+
{
|
| 100 |
+
"source": "C",
|
| 101 |
+
"target": "E"
|
| 102 |
+
},
|
| 103 |
+
{
|
| 104 |
+
"source": "D",
|
| 105 |
+
"target": "F"
|
| 106 |
+
},
|
| 107 |
+
{
|
| 108 |
+
"source": "A",
|
| 109 |
+
"target": "G"
|
| 110 |
+
},
|
| 111 |
+
{
|
| 112 |
+
"source": "G",
|
| 113 |
+
"target": "H"
|
| 114 |
+
},
|
| 115 |
+
{
|
| 116 |
+
"source": "G",
|
| 117 |
+
"target": "I"
|
| 118 |
+
},
|
| 119 |
+
{
|
| 120 |
+
"source": "G",
|
| 121 |
+
"target": "J"
|
| 122 |
+
},
|
| 123 |
+
{
|
| 124 |
+
"source": "G",
|
| 125 |
+
"target": "K"
|
| 126 |
+
},
|
| 127 |
+
{
|
| 128 |
+
"source": "G",
|
| 129 |
+
"target": "L"
|
| 130 |
+
},
|
| 131 |
+
{
|
| 132 |
+
"source": "H",
|
| 133 |
+
"target": "J"
|
| 134 |
+
},
|
| 135 |
+
{
|
| 136 |
+
"source": "I",
|
| 137 |
+
"target": "J"
|
| 138 |
+
},
|
| 139 |
+
{
|
| 140 |
+
"source": "I",
|
| 141 |
+
"target": "K"
|
| 142 |
+
},
|
| 143 |
+
{
|
| 144 |
+
"source": "J",
|
| 145 |
+
"target": "K"
|
| 146 |
+
},
|
| 147 |
+
{
|
| 148 |
+
"source": "J",
|
| 149 |
+
"target": "L"
|
| 150 |
+
}
|
| 151 |
+
]
|
| 152 |
+
},
|
| 153 |
+
{
|
| 154 |
+
"type": "text",
|
| 155 |
+
"text": "来源: IDC, 2023"
|
| 156 |
+
},
|
| 157 |
+
{
|
| 158 |
+
"type": "title",
|
| 159 |
+
"text": "3.1 用户:生态话语权显著提升"
|
| 160 |
+
},
|
| 161 |
+
{
|
| 162 |
+
"type": "title",
|
| 163 |
+
"text": "用户成为行业生态创新的驱动者和创造者"
|
| 164 |
+
},
|
| 165 |
+
{
|
| 166 |
+
"type": "text",
|
| 167 |
+
"text": "PC 行业的前几次产业变革主要由终端、OS 或是芯片厂商推动,用户被动接纳新的技术和产品,调整和适应自己的使用工具的习惯、提升使用工具的熟练度。"
|
| 168 |
+
},
|
| 169 |
+
{
|
| 170 |
+
"type": "footer",
|
| 171 |
+
"text": "IDC | Lenovo 联想"
|
| 172 |
+
},
|
| 173 |
+
{
|
| 174 |
+
"type": "page_number",
|
| 175 |
+
"text": "24"
|
| 176 |
+
}
|
| 177 |
+
]
|
diagrams-and-tables/annotations/cn_diagram_11.json
ADDED
|
@@ -0,0 +1,361 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
[
|
| 2 |
+
{
|
| 3 |
+
"type": "header",
|
| 4 |
+
"text": "工业设备网联化技术与实践白皮书\n工业设备网联化现状及趋势"
|
| 5 |
+
},
|
| 6 |
+
{
|
| 7 |
+
"type": "text",
|
| 8 |
+
"text": "不确定性的随机网络,难以胜任高速实时性数据通信。为此,世界上的各大公司纷纷开发出自己的实时工业以太网,例如:PROFINET、EtherCAT等。而TSN(Time Sensitive Network)-时间敏感型网络的出现,解决了用单一网络连接不同工业以太协议的问题,并与OPC-UA结合实现了IT与OT的融合通信。"
|
| 9 |
+
},
|
| 10 |
+
{
|
| 11 |
+
"type": "diagram_caption",
|
| 12 |
+
"text": "图2-3 大部分工业实时以太协议舍弃TCP/IP层"
|
| 13 |
+
},
|
| 14 |
+
{
|
| 15 |
+
"type": "diagram",
|
| 16 |
+
"nodes": [
|
| 17 |
+
{
|
| 18 |
+
"id": "A",
|
| 19 |
+
"text": "L2标准以太+标准IP"
|
| 20 |
+
},
|
| 21 |
+
{
|
| 22 |
+
"id": "B",
|
| 23 |
+
"text": "Category A"
|
| 24 |
+
},
|
| 25 |
+
{
|
| 26 |
+
"id": "C",
|
| 27 |
+
"text": "IT / RT Services "
|
| 28 |
+
},
|
| 29 |
+
{
|
| 30 |
+
"id": "D",
|
| 31 |
+
"text": "TCP/UDP"
|
| 32 |
+
},
|
| 33 |
+
{
|
| 34 |
+
"id": "E",
|
| 35 |
+
"text": "IP"
|
| 36 |
+
},
|
| 37 |
+
{
|
| 38 |
+
"id": "F",
|
| 39 |
+
"text": "Standard"
|
| 40 |
+
},
|
| 41 |
+
{
|
| 42 |
+
"id": "G",
|
| 43 |
+
"text": "Standard Ethernet TCP/IP, EtherNet/IP, Modbus/TCP"
|
| 44 |
+
},
|
| 45 |
+
{
|
| 46 |
+
"id": "H",
|
| 47 |
+
"text": "标准以太+标准IP/定制协议"
|
| 48 |
+
},
|
| 49 |
+
{
|
| 50 |
+
"id": "I",
|
| 51 |
+
"text": "Category B"
|
| 52 |
+
},
|
| 53 |
+
{
|
| 54 |
+
"id": "J",
|
| 55 |
+
"text": "IT Services "
|
| 56 |
+
},
|
| 57 |
+
{
|
| 58 |
+
"id": "K",
|
| 59 |
+
"text": "RT Services "
|
| 60 |
+
},
|
| 61 |
+
{
|
| 62 |
+
"id": "L",
|
| 63 |
+
"text": "TCP/UDP"
|
| 64 |
+
},
|
| 65 |
+
{
|
| 66 |
+
"id": "M",
|
| 67 |
+
"text": "Special Process Data Protocol"
|
| 68 |
+
},
|
| 69 |
+
{
|
| 70 |
+
"id": "N",
|
| 71 |
+
"text": "IP"
|
| 72 |
+
},
|
| 73 |
+
{
|
| 74 |
+
"id": "O",
|
| 75 |
+
"text": "Standard"
|
| 76 |
+
},
|
| 77 |
+
{
|
| 78 |
+
"id": "P",
|
| 79 |
+
"text": "Powerlink, Sercos-III, Profinet v2"
|
| 80 |
+
},
|
| 81 |
+
{
|
| 82 |
+
"id": "Q",
|
| 83 |
+
"text": "标准以太/定制硬件+标准IP/定制协议"
|
| 84 |
+
},
|
| 85 |
+
{
|
| 86 |
+
"id": "R",
|
| 87 |
+
"text": "Category C"
|
| 88 |
+
},
|
| 89 |
+
{
|
| 90 |
+
"id": "S",
|
| 91 |
+
"text": "IT Services"
|
| 92 |
+
},
|
| 93 |
+
{
|
| 94 |
+
"id": "T",
|
| 95 |
+
"text": "RT Services"
|
| 96 |
+
},
|
| 97 |
+
{
|
| 98 |
+
"id": "U",
|
| 99 |
+
"text": "TCP/UDP"
|
| 100 |
+
},
|
| 101 |
+
{
|
| 102 |
+
"id": "V",
|
| 103 |
+
"text": "Special Process Data Protocol"
|
| 104 |
+
},
|
| 105 |
+
{
|
| 106 |
+
"id": "W",
|
| 107 |
+
"text": "IP"
|
| 108 |
+
},
|
| 109 |
+
{
|
| 110 |
+
"id": "X",
|
| 111 |
+
"text": "Special RT"
|
| 112 |
+
},
|
| 113 |
+
{
|
| 114 |
+
"id": "Y",
|
| 115 |
+
"text": "EtherCAT, Profinet v3"
|
| 116 |
+
},
|
| 117 |
+
{
|
| 118 |
+
"id": "Z",
|
| 119 |
+
"text": "支持 IEEE1588"
|
| 120 |
+
},
|
| 121 |
+
{
|
| 122 |
+
"id": "AA",
|
| 123 |
+
"text": "物理相同"
|
| 124 |
+
},
|
| 125 |
+
{
|
| 126 |
+
"id": "AB",
|
| 127 |
+
"text": "Ethernet/MAC"
|
| 128 |
+
},
|
| 129 |
+
{
|
| 130 |
+
"id": "AC",
|
| 131 |
+
"text": "Ethernet/MAC"
|
| 132 |
+
},
|
| 133 |
+
{
|
| 134 |
+
"id": "AD",
|
| 135 |
+
"text": "Ethernet/MAC"
|
| 136 |
+
}
|
| 137 |
+
],
|
| 138 |
+
"relationships": [
|
| 139 |
+
{
|
| 140 |
+
"source": "A",
|
| 141 |
+
"target": "B"
|
| 142 |
+
},
|
| 143 |
+
{
|
| 144 |
+
"source": "A",
|
| 145 |
+
"target": "C"
|
| 146 |
+
},
|
| 147 |
+
{
|
| 148 |
+
"source": "A",
|
| 149 |
+
"target": "D"
|
| 150 |
+
},
|
| 151 |
+
{
|
| 152 |
+
"source": "A",
|
| 153 |
+
"target": "E"
|
| 154 |
+
},
|
| 155 |
+
{
|
| 156 |
+
"source": "A",
|
| 157 |
+
"target": "F"
|
| 158 |
+
},
|
| 159 |
+
{
|
| 160 |
+
"source": "A",
|
| 161 |
+
"target": "G"
|
| 162 |
+
},
|
| 163 |
+
{
|
| 164 |
+
"source": "A",
|
| 165 |
+
"target": "AB"
|
| 166 |
+
},
|
| 167 |
+
{
|
| 168 |
+
"source": "C",
|
| 169 |
+
"target": "D"
|
| 170 |
+
},
|
| 171 |
+
{
|
| 172 |
+
"source": "D",
|
| 173 |
+
"target": "E"
|
| 174 |
+
},
|
| 175 |
+
{
|
| 176 |
+
"source": "E",
|
| 177 |
+
"target": "F"
|
| 178 |
+
},
|
| 179 |
+
{
|
| 180 |
+
"source": "F",
|
| 181 |
+
"target": "AB"
|
| 182 |
+
},
|
| 183 |
+
{
|
| 184 |
+
"source": "H",
|
| 185 |
+
"target": "I"
|
| 186 |
+
},
|
| 187 |
+
{
|
| 188 |
+
"source": "H",
|
| 189 |
+
"target": "J"
|
| 190 |
+
},
|
| 191 |
+
{
|
| 192 |
+
"source": "H",
|
| 193 |
+
"target": "K"
|
| 194 |
+
},
|
| 195 |
+
{
|
| 196 |
+
"source": "H",
|
| 197 |
+
"target": "L"
|
| 198 |
+
},
|
| 199 |
+
{
|
| 200 |
+
"source": "H",
|
| 201 |
+
"target": "M"
|
| 202 |
+
},
|
| 203 |
+
{
|
| 204 |
+
"source": "H",
|
| 205 |
+
"target": "N"
|
| 206 |
+
},
|
| 207 |
+
{
|
| 208 |
+
"source": "H",
|
| 209 |
+
"target": "O"
|
| 210 |
+
},
|
| 211 |
+
{
|
| 212 |
+
"source": "H",
|
| 213 |
+
"target": "P"
|
| 214 |
+
},
|
| 215 |
+
{
|
| 216 |
+
"source": "H",
|
| 217 |
+
"target": "Z"
|
| 218 |
+
},
|
| 219 |
+
{
|
| 220 |
+
"source": "H",
|
| 221 |
+
"target": "AC"
|
| 222 |
+
},
|
| 223 |
+
{
|
| 224 |
+
"source": "J",
|
| 225 |
+
"target": "K"
|
| 226 |
+
},
|
| 227 |
+
{
|
| 228 |
+
"source": "J",
|
| 229 |
+
"target": "L"
|
| 230 |
+
},
|
| 231 |
+
{
|
| 232 |
+
"source": "K",
|
| 233 |
+
"target": "M"
|
| 234 |
+
},
|
| 235 |
+
{
|
| 236 |
+
"source": "L",
|
| 237 |
+
"target": "N"
|
| 238 |
+
},
|
| 239 |
+
{
|
| 240 |
+
"source": "L",
|
| 241 |
+
"target": "M"
|
| 242 |
+
},
|
| 243 |
+
{
|
| 244 |
+
"source": "M",
|
| 245 |
+
"target": "N"
|
| 246 |
+
},
|
| 247 |
+
{
|
| 248 |
+
"source": "M",
|
| 249 |
+
"target": "O"
|
| 250 |
+
},
|
| 251 |
+
{
|
| 252 |
+
"source": "N",
|
| 253 |
+
"target": "O"
|
| 254 |
+
},
|
| 255 |
+
{
|
| 256 |
+
"source": "O",
|
| 257 |
+
"target": "AC"
|
| 258 |
+
},
|
| 259 |
+
{
|
| 260 |
+
"source": "Q",
|
| 261 |
+
"target": "R"
|
| 262 |
+
},
|
| 263 |
+
{
|
| 264 |
+
"source": "Q",
|
| 265 |
+
"target": "S"
|
| 266 |
+
},
|
| 267 |
+
{
|
| 268 |
+
"source": "Q",
|
| 269 |
+
"target": "T"
|
| 270 |
+
},
|
| 271 |
+
{
|
| 272 |
+
"source": "Q",
|
| 273 |
+
"target": "U"
|
| 274 |
+
},
|
| 275 |
+
{
|
| 276 |
+
"source": "Q",
|
| 277 |
+
"target": "V"
|
| 278 |
+
},
|
| 279 |
+
{
|
| 280 |
+
"source": "Q",
|
| 281 |
+
"target": "W"
|
| 282 |
+
},
|
| 283 |
+
{
|
| 284 |
+
"source": "Q",
|
| 285 |
+
"target": "X"
|
| 286 |
+
},
|
| 287 |
+
{
|
| 288 |
+
"source": "Q",
|
| 289 |
+
"target": "Y"
|
| 290 |
+
},
|
| 291 |
+
{
|
| 292 |
+
"source": "Q",
|
| 293 |
+
"target": "Z"
|
| 294 |
+
},
|
| 295 |
+
{
|
| 296 |
+
"source": "Q",
|
| 297 |
+
"target": "AD"
|
| 298 |
+
},
|
| 299 |
+
{
|
| 300 |
+
"source": "S",
|
| 301 |
+
"target": "U"
|
| 302 |
+
},
|
| 303 |
+
{
|
| 304 |
+
"source": "S",
|
| 305 |
+
"target": "T"
|
| 306 |
+
},
|
| 307 |
+
{
|
| 308 |
+
"source": "T",
|
| 309 |
+
"target": "V"
|
| 310 |
+
},
|
| 311 |
+
{
|
| 312 |
+
"source": "U",
|
| 313 |
+
"target": "V"
|
| 314 |
+
},
|
| 315 |
+
{
|
| 316 |
+
"source": "U",
|
| 317 |
+
"target": "W"
|
| 318 |
+
},
|
| 319 |
+
{
|
| 320 |
+
"source": "V",
|
| 321 |
+
"target": "W"
|
| 322 |
+
},
|
| 323 |
+
{
|
| 324 |
+
"source": "V",
|
| 325 |
+
"target": "X"
|
| 326 |
+
},
|
| 327 |
+
{
|
| 328 |
+
"source": "W",
|
| 329 |
+
"target": "X"
|
| 330 |
+
},
|
| 331 |
+
{
|
| 332 |
+
"source": "X",
|
| 333 |
+
"target": "AD"
|
| 334 |
+
},
|
| 335 |
+
{
|
| 336 |
+
"source": "AA",
|
| 337 |
+
"target": "AB"
|
| 338 |
+
},
|
| 339 |
+
{
|
| 340 |
+
"source": "AA",
|
| 341 |
+
"target": "AC"
|
| 342 |
+
},
|
| 343 |
+
{
|
| 344 |
+
"source": "AA",
|
| 345 |
+
"target": "AD"
|
| 346 |
+
}
|
| 347 |
+
]
|
| 348 |
+
},
|
| 349 |
+
{
|
| 350 |
+
"type": "text",
|
| 351 |
+
"text": "广域IP化:大部分的工业以太在实时处理过程中舍弃了TCP/IP层,因此从本质上讲是工业以太总线。进入工业智能时代,工业互联网正在推动企业生产系统走向现场少人化、无人化,控制系统加速走向远程集中控制模式,让操作人员可以在更安全、更舒适的集中控制室完成生产任务,也让大型企业得以在更大范围内实现总部、多基地之间的生产要素调度和优化,为此,工业控制系统需要走向广域云化。工控系统的IP化是实现整个网络端到端统一语言都说“普通话”、IT与OT网络融合的基础。当然,要实现远程的云化实时控制,一张确定性的广域网络必不可少。"
|
| 352 |
+
},
|
| 353 |
+
{
|
| 354 |
+
"type": "page_number",
|
| 355 |
+
"text": "05"
|
| 356 |
+
},
|
| 357 |
+
{
|
| 358 |
+
"type": "footer",
|
| 359 |
+
"text": "打造先进工业网络 加速工业互联网创新发展"
|
| 360 |
+
}
|
| 361 |
+
]
|
diagrams-and-tables/annotations/cn_diagram_12.json
ADDED
|
@@ -0,0 +1,261 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
[
|
| 2 |
+
{
|
| 3 |
+
"type": "header",
|
| 4 |
+
"text": "HarmonyOS NEXT 安全技术白皮书"
|
| 5 |
+
},
|
| 6 |
+
{
|
| 7 |
+
"type": "header",
|
| 8 |
+
"text": "2 HarmonyOS 概述"
|
| 9 |
+
},
|
| 10 |
+
{
|
| 11 |
+
"type": "text",
|
| 12 |
+
"text": "分布式软总线是手机、智能穿戴、平板、智慧屏、车机等多种终端设备的统一基座,为设备之间的互联互通提供了统一的分布式通信能力,能够快速发现并连接设备,高效地分发任务和传输数据。"
|
| 13 |
+
},
|
| 14 |
+
{
|
| 15 |
+
"type": "diagram_caption",
|
| 16 |
+
"text": "图2-1 分布式软总线示意图"
|
| 17 |
+
},
|
| 18 |
+
{
|
| 19 |
+
"type": "diagram",
|
| 20 |
+
"nodes": [
|
| 21 |
+
{
|
| 22 |
+
"id": "A",
|
| 23 |
+
"text": "终端设备"
|
| 24 |
+
},
|
| 25 |
+
{
|
| 26 |
+
"id": "B",
|
| 27 |
+
"text": "设备A"
|
| 28 |
+
},
|
| 29 |
+
{
|
| 30 |
+
"id": "C",
|
| 31 |
+
"text": "设备B"
|
| 32 |
+
},
|
| 33 |
+
{
|
| 34 |
+
"id": "D",
|
| 35 |
+
"text": "设备C"
|
| 36 |
+
},
|
| 37 |
+
{
|
| 38 |
+
"id": "E",
|
| 39 |
+
"text": "设备D"
|
| 40 |
+
},
|
| 41 |
+
{
|
| 42 |
+
"id": "F",
|
| 43 |
+
"text": "......"
|
| 44 |
+
},
|
| 45 |
+
{
|
| 46 |
+
"id": "G",
|
| 47 |
+
"text": "分布式软总线"
|
| 48 |
+
},
|
| 49 |
+
{
|
| 50 |
+
"id": "H",
|
| 51 |
+
"text": "数据与计算中心"
|
| 52 |
+
},
|
| 53 |
+
{
|
| 54 |
+
"id": "I",
|
| 55 |
+
"text": "决策中心"
|
| 56 |
+
},
|
| 57 |
+
{
|
| 58 |
+
"id": "J",
|
| 59 |
+
"text": "总线中枢"
|
| 60 |
+
},
|
| 61 |
+
{
|
| 62 |
+
"id": "K",
|
| 63 |
+
"text": "互联管理中心"
|
| 64 |
+
},
|
| 65 |
+
{
|
| 66 |
+
"id": "L",
|
| 67 |
+
"text": "组网&拓扑管理"
|
| 68 |
+
},
|
| 69 |
+
{
|
| 70 |
+
"id": "M",
|
| 71 |
+
"text": "发现"
|
| 72 |
+
},
|
| 73 |
+
{
|
| 74 |
+
"id": "N",
|
| 75 |
+
"text": "连接"
|
| 76 |
+
},
|
| 77 |
+
{
|
| 78 |
+
"id": "O",
|
| 79 |
+
"text": "任务&数据总线(消息、字节、文件、流)"
|
| 80 |
+
},
|
| 81 |
+
{
|
| 82 |
+
"id": "P",
|
| 83 |
+
"text": "安全"
|
| 84 |
+
},
|
| 85 |
+
{
|
| 86 |
+
"id": "Q",
|
| 87 |
+
"text": "设备Profile"
|
| 88 |
+
},
|
| 89 |
+
{
|
| 90 |
+
"id": "R",
|
| 91 |
+
"text": "基础通信"
|
| 92 |
+
},
|
| 93 |
+
{
|
| 94 |
+
"id": "S",
|
| 95 |
+
"text": "协议栈"
|
| 96 |
+
},
|
| 97 |
+
{
|
| 98 |
+
"id": "T",
|
| 99 |
+
"text": "软硬协同"
|
| 100 |
+
},
|
| 101 |
+
{
|
| 102 |
+
"id": "U",
|
| 103 |
+
"text": "WLAN"
|
| 104 |
+
},
|
| 105 |
+
{
|
| 106 |
+
"id": "V",
|
| 107 |
+
"text": "Bluetooth"
|
| 108 |
+
},
|
| 109 |
+
{
|
| 110 |
+
"id": "W",
|
| 111 |
+
"text": "BLE"
|
| 112 |
+
},
|
| 113 |
+
{
|
| 114 |
+
"id": "X",
|
| 115 |
+
"text": "NFC"
|
| 116 |
+
},
|
| 117 |
+
{
|
| 118 |
+
"id": "Y",
|
| 119 |
+
"text": "红外"
|
| 120 |
+
},
|
| 121 |
+
{
|
| 122 |
+
"id": "Z",
|
| 123 |
+
"text": "USB"
|
| 124 |
+
},
|
| 125 |
+
{
|
| 126 |
+
"id": "AA",
|
| 127 |
+
"text": "Ethernet"
|
| 128 |
+
},
|
| 129 |
+
{
|
| 130 |
+
"id": "AB",
|
| 131 |
+
"text": "Modem (2/3/4/5G)"
|
| 132 |
+
},
|
| 133 |
+
{
|
| 134 |
+
"id": "AC",
|
| 135 |
+
"text": "......"
|
| 136 |
+
}
|
| 137 |
+
],
|
| 138 |
+
"relationships": [
|
| 139 |
+
{
|
| 140 |
+
"source": "A",
|
| 141 |
+
"target": "B"
|
| 142 |
+
},
|
| 143 |
+
{
|
| 144 |
+
"source": "A",
|
| 145 |
+
"target": "C"
|
| 146 |
+
},
|
| 147 |
+
{
|
| 148 |
+
"source": "A",
|
| 149 |
+
"target": "D"
|
| 150 |
+
},
|
| 151 |
+
{
|
| 152 |
+
"source": "A",
|
| 153 |
+
"target": "E"
|
| 154 |
+
},
|
| 155 |
+
{
|
| 156 |
+
"source": "A",
|
| 157 |
+
"target": "F"
|
| 158 |
+
},
|
| 159 |
+
{
|
| 160 |
+
"source": "G",
|
| 161 |
+
"target": "J"
|
| 162 |
+
},
|
| 163 |
+
{
|
| 164 |
+
"source": "G",
|
| 165 |
+
"target": "O"
|
| 166 |
+
},
|
| 167 |
+
{
|
| 168 |
+
"source": "G",
|
| 169 |
+
"target": "P"
|
| 170 |
+
},
|
| 171 |
+
{
|
| 172 |
+
"source": "G",
|
| 173 |
+
"target": "Q"
|
| 174 |
+
},
|
| 175 |
+
{
|
| 176 |
+
"source": "H",
|
| 177 |
+
"target": "J"
|
| 178 |
+
},
|
| 179 |
+
{
|
| 180 |
+
"source": "I",
|
| 181 |
+
"target": "J"
|
| 182 |
+
},
|
| 183 |
+
{
|
| 184 |
+
"source": "J",
|
| 185 |
+
"target": "K"
|
| 186 |
+
},
|
| 187 |
+
{
|
| 188 |
+
"source": "K",
|
| 189 |
+
"target": "L"
|
| 190 |
+
},
|
| 191 |
+
{
|
| 192 |
+
"source": "K",
|
| 193 |
+
"target": "M"
|
| 194 |
+
},
|
| 195 |
+
{
|
| 196 |
+
"source": "K",
|
| 197 |
+
"target": "N"
|
| 198 |
+
},
|
| 199 |
+
{
|
| 200 |
+
"source": "R",
|
| 201 |
+
"target": "S"
|
| 202 |
+
},
|
| 203 |
+
{
|
| 204 |
+
"source": "R",
|
| 205 |
+
"target": "T"
|
| 206 |
+
},
|
| 207 |
+
{
|
| 208 |
+
"source": "R",
|
| 209 |
+
"target": "U"
|
| 210 |
+
},
|
| 211 |
+
{
|
| 212 |
+
"source": "R",
|
| 213 |
+
"target": "V"
|
| 214 |
+
},
|
| 215 |
+
{
|
| 216 |
+
"source": "R",
|
| 217 |
+
"target": "W"
|
| 218 |
+
},
|
| 219 |
+
{
|
| 220 |
+
"source": "R",
|
| 221 |
+
"target": "X"
|
| 222 |
+
},
|
| 223 |
+
{
|
| 224 |
+
"source": "R",
|
| 225 |
+
"target": "Y"
|
| 226 |
+
},
|
| 227 |
+
{
|
| 228 |
+
"source": "R",
|
| 229 |
+
"target": "Z"
|
| 230 |
+
},
|
| 231 |
+
{
|
| 232 |
+
"source": "R",
|
| 233 |
+
"target": "AA"
|
| 234 |
+
},
|
| 235 |
+
{
|
| 236 |
+
"source": "R",
|
| 237 |
+
"target": "AB"
|
| 238 |
+
},
|
| 239 |
+
{
|
| 240 |
+
"source": "R",
|
| 241 |
+
"target": "AC"
|
| 242 |
+
}
|
| 243 |
+
]
|
| 244 |
+
},
|
| 245 |
+
{
|
| 246 |
+
"type": "title",
|
| 247 |
+
"text": "分布式设备虚拟化"
|
| 248 |
+
},
|
| 249 |
+
{
|
| 250 |
+
"type": "text",
|
| 251 |
+
"text": "分布式设备虚拟化平台可以实现不同设备的资源融合、设备管理、数据处理,多种设备共同形成一个超级虚拟终端。针对不同类型的任务,为用户匹配并选择能力合适的执行硬件,让业务连续地在不同设备间流转,充分发挥不同设备的资源优势。"
|
| 252 |
+
},
|
| 253 |
+
{
|
| 254 |
+
"type": "footer",
|
| 255 |
+
"text": "文档版本 V1.0 (2024-08-13) 版权所有 © 华为技术有限公司"
|
| 256 |
+
},
|
| 257 |
+
{
|
| 258 |
+
"type": "page_number",
|
| 259 |
+
"text": "5"
|
| 260 |
+
}
|
| 261 |
+
]
|
diagrams-and-tables/annotations/cn_diagram_13.json
ADDED
|
@@ -0,0 +1,318 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
[
|
| 2 |
+
{
|
| 3 |
+
"type": "header",
|
| 4 |
+
"text": "HarmonyOS NEXT 安全技术白皮书 2 HarmonyOS 概述"
|
| 5 |
+
},
|
| 6 |
+
{
|
| 7 |
+
"type": "diagram_caption",
|
| 8 |
+
"text": "图2-2 分布式设备虚拟化示意图"
|
| 9 |
+
},
|
| 10 |
+
{
|
| 11 |
+
"type": "diagram",
|
| 12 |
+
"nodes": [
|
| 13 |
+
{
|
| 14 |
+
"id": "A",
|
| 15 |
+
"text": "设备A"
|
| 16 |
+
},
|
| 17 |
+
{
|
| 18 |
+
"id": "B",
|
| 19 |
+
"text": "直播类应用"
|
| 20 |
+
},
|
| 21 |
+
{
|
| 22 |
+
"id": "C",
|
| 23 |
+
"text": "通话类应用"
|
| 24 |
+
},
|
| 25 |
+
{
|
| 26 |
+
"id": "D",
|
| 27 |
+
"text": "健身类应用"
|
| 28 |
+
},
|
| 29 |
+
{
|
| 30 |
+
"id": "E",
|
| 31 |
+
"text": "多设备虚拟化Kit"
|
| 32 |
+
},
|
| 33 |
+
{
|
| 34 |
+
"id": "F",
|
| 35 |
+
"text": "多设备虚拟化平台"
|
| 36 |
+
},
|
| 37 |
+
{
|
| 38 |
+
"id": "G",
|
| 39 |
+
"text": "设备管理与安全"
|
| 40 |
+
},
|
| 41 |
+
{
|
| 42 |
+
"id": "H",
|
| 43 |
+
"text": "数据处理与增强"
|
| 44 |
+
},
|
| 45 |
+
{
|
| 46 |
+
"id": "I",
|
| 47 |
+
"text": "设备虚拟与接入"
|
| 48 |
+
},
|
| 49 |
+
{
|
| 50 |
+
"id": "J",
|
| 51 |
+
"text": "OS"
|
| 52 |
+
},
|
| 53 |
+
{
|
| 54 |
+
"id": "K",
|
| 55 |
+
"text": "设备B"
|
| 56 |
+
},
|
| 57 |
+
{
|
| 58 |
+
"id": "L",
|
| 59 |
+
"text": "智慧屏、智能穿戴、车机等设备"
|
| 60 |
+
},
|
| 61 |
+
{
|
| 62 |
+
"id": "M",
|
| 63 |
+
"text": "多设备虚拟化SDK"
|
| 64 |
+
},
|
| 65 |
+
{
|
| 66 |
+
"id": "N",
|
| 67 |
+
"text": "设备管理"
|
| 68 |
+
},
|
| 69 |
+
{
|
| 70 |
+
"id": "O",
|
| 71 |
+
"text": "设备虚拟化"
|
| 72 |
+
},
|
| 73 |
+
{
|
| 74 |
+
"id": "P",
|
| 75 |
+
"text": "数据处理"
|
| 76 |
+
},
|
| 77 |
+
{
|
| 78 |
+
"id": "Q",
|
| 79 |
+
"text": "OS适配"
|
| 80 |
+
},
|
| 81 |
+
{
|
| 82 |
+
"id": "R",
|
| 83 |
+
"text": "OS"
|
| 84 |
+
}
|
| 85 |
+
],
|
| 86 |
+
"relationships": [
|
| 87 |
+
{
|
| 88 |
+
"source": "A",
|
| 89 |
+
"target": "B"
|
| 90 |
+
},
|
| 91 |
+
{
|
| 92 |
+
"source": "A",
|
| 93 |
+
"target": "C"
|
| 94 |
+
},
|
| 95 |
+
{
|
| 96 |
+
"source": "A",
|
| 97 |
+
"target": "D"
|
| 98 |
+
},
|
| 99 |
+
{
|
| 100 |
+
"source": "A",
|
| 101 |
+
"target": "E"
|
| 102 |
+
},
|
| 103 |
+
{
|
| 104 |
+
"source": "A",
|
| 105 |
+
"target": "F"
|
| 106 |
+
},
|
| 107 |
+
{
|
| 108 |
+
"source": "F",
|
| 109 |
+
"target": "G"
|
| 110 |
+
},
|
| 111 |
+
{
|
| 112 |
+
"source": "F",
|
| 113 |
+
"target": "H"
|
| 114 |
+
},
|
| 115 |
+
{
|
| 116 |
+
"source": "F",
|
| 117 |
+
"target": "I"
|
| 118 |
+
},
|
| 119 |
+
{
|
| 120 |
+
"source": "A",
|
| 121 |
+
"target": "J"
|
| 122 |
+
},
|
| 123 |
+
{
|
| 124 |
+
"source": "A",
|
| 125 |
+
"target": "K"
|
| 126 |
+
},
|
| 127 |
+
{
|
| 128 |
+
"source": "K",
|
| 129 |
+
"target": "L"
|
| 130 |
+
},
|
| 131 |
+
{
|
| 132 |
+
"source": "K",
|
| 133 |
+
"target": "M"
|
| 134 |
+
},
|
| 135 |
+
{
|
| 136 |
+
"source": "M",
|
| 137 |
+
"target": "N"
|
| 138 |
+
},
|
| 139 |
+
{
|
| 140 |
+
"source": "M",
|
| 141 |
+
"target": "O"
|
| 142 |
+
},
|
| 143 |
+
{
|
| 144 |
+
"source": "M",
|
| 145 |
+
"target": "P"
|
| 146 |
+
},
|
| 147 |
+
{
|
| 148 |
+
"source": "M",
|
| 149 |
+
"target": "Q"
|
| 150 |
+
},
|
| 151 |
+
{
|
| 152 |
+
"source": "K",
|
| 153 |
+
"target": "R"
|
| 154 |
+
}
|
| 155 |
+
]
|
| 156 |
+
},
|
| 157 |
+
{
|
| 158 |
+
"type": "title",
|
| 159 |
+
"text": "分布式数据管理"
|
| 160 |
+
},
|
| 161 |
+
{
|
| 162 |
+
"type": "text",
|
| 163 |
+
"text": "分布式数据管理基于分布式软总线的能力,实现应用程序数据和用户数据的分布式管理。用户数据不再与单一物理设备绑定,业务逻辑与数据存储分离,应用跨设备运行时数据无缝衔接,为打造一致、流畅的用户体验创造了基础条件。"
|
| 164 |
+
},
|
| 165 |
+
{
|
| 166 |
+
"type": "diagram_caption",
|
| 167 |
+
"text": "图2-3 分布式数据管理示意图"
|
| 168 |
+
},
|
| 169 |
+
{
|
| 170 |
+
"type": "diagram",
|
| 171 |
+
"nodes": [
|
| 172 |
+
{
|
| 173 |
+
"id": "A",
|
| 174 |
+
"text": "设备A:应用程序数据&用户数据"
|
| 175 |
+
},
|
| 176 |
+
{
|
| 177 |
+
"id": "B",
|
| 178 |
+
"text": "设备/用户/应用Profile"
|
| 179 |
+
},
|
| 180 |
+
{
|
| 181 |
+
"id": "C",
|
| 182 |
+
"text": "状态事件/位置"
|
| 183 |
+
},
|
| 184 |
+
{
|
| 185 |
+
"id": "D",
|
| 186 |
+
"text": "文本数据"
|
| 187 |
+
},
|
| 188 |
+
{
|
| 189 |
+
"id": "E",
|
| 190 |
+
"text": "媒体数据"
|
| 191 |
+
},
|
| 192 |
+
{
|
| 193 |
+
"id": "F",
|
| 194 |
+
"text": "......"
|
| 195 |
+
},
|
| 196 |
+
{
|
| 197 |
+
"id": "G",
|
| 198 |
+
"text": "设备B:应用程序数据&用户数据"
|
| 199 |
+
},
|
| 200 |
+
{
|
| 201 |
+
"id": "H",
|
| 202 |
+
"text": "设备/用户/应用Profile"
|
| 203 |
+
},
|
| 204 |
+
{
|
| 205 |
+
"id": "I",
|
| 206 |
+
"text": "状态事件/位置"
|
| 207 |
+
},
|
| 208 |
+
{
|
| 209 |
+
"id": "J",
|
| 210 |
+
"text": "文本数据"
|
| 211 |
+
},
|
| 212 |
+
{
|
| 213 |
+
"id": "K",
|
| 214 |
+
"text": "超级虚拟终端:应用程序数据&用户数据"
|
| 215 |
+
},
|
| 216 |
+
{
|
| 217 |
+
"id": "L",
|
| 218 |
+
"text": "设备/用户/应用Profile"
|
| 219 |
+
},
|
| 220 |
+
{
|
| 221 |
+
"id": "M",
|
| 222 |
+
"text": "状态事件/位置"
|
| 223 |
+
},
|
| 224 |
+
{
|
| 225 |
+
"id": "N",
|
| 226 |
+
"text": "文本数据"
|
| 227 |
+
},
|
| 228 |
+
{
|
| 229 |
+
"id": "O",
|
| 230 |
+
"text": "媒体数据"
|
| 231 |
+
},
|
| 232 |
+
{
|
| 233 |
+
"id": "P",
|
| 234 |
+
"text": "......"
|
| 235 |
+
}
|
| 236 |
+
],
|
| 237 |
+
"relationships": [
|
| 238 |
+
{
|
| 239 |
+
"source": "A",
|
| 240 |
+
"target": "B"
|
| 241 |
+
},
|
| 242 |
+
{
|
| 243 |
+
"source": "A",
|
| 244 |
+
"target": "C"
|
| 245 |
+
},
|
| 246 |
+
{
|
| 247 |
+
"source": "A",
|
| 248 |
+
"target": "D"
|
| 249 |
+
},
|
| 250 |
+
{
|
| 251 |
+
"source": "A",
|
| 252 |
+
"target": "E"
|
| 253 |
+
},
|
| 254 |
+
{
|
| 255 |
+
"source": "A",
|
| 256 |
+
"target": "F"
|
| 257 |
+
},
|
| 258 |
+
{
|
| 259 |
+
"source": "A",
|
| 260 |
+
"target": "K",
|
| 261 |
+
"label": "数据同步管理"
|
| 262 |
+
},
|
| 263 |
+
{
|
| 264 |
+
"source": "G",
|
| 265 |
+
"target": "H"
|
| 266 |
+
},
|
| 267 |
+
{
|
| 268 |
+
"source": "G",
|
| 269 |
+
"target": "I"
|
| 270 |
+
},
|
| 271 |
+
{
|
| 272 |
+
"source": "G",
|
| 273 |
+
"target": "J"
|
| 274 |
+
},
|
| 275 |
+
{
|
| 276 |
+
"source": "G",
|
| 277 |
+
"target": "K",
|
| 278 |
+
"label": "数据同步管理"
|
| 279 |
+
},
|
| 280 |
+
{
|
| 281 |
+
"source": "K",
|
| 282 |
+
"target": "L"
|
| 283 |
+
},
|
| 284 |
+
{
|
| 285 |
+
"source": "K",
|
| 286 |
+
"target": "M"
|
| 287 |
+
},
|
| 288 |
+
{
|
| 289 |
+
"source": "K",
|
| 290 |
+
"target": "N"
|
| 291 |
+
},
|
| 292 |
+
{
|
| 293 |
+
"source": "K",
|
| 294 |
+
"target": "O"
|
| 295 |
+
},
|
| 296 |
+
{
|
| 297 |
+
"source": "K",
|
| 298 |
+
"target": "P"
|
| 299 |
+
}
|
| 300 |
+
]
|
| 301 |
+
},
|
| 302 |
+
{
|
| 303 |
+
"type": "title",
|
| 304 |
+
"text": "分布式任务调度"
|
| 305 |
+
},
|
| 306 |
+
{
|
| 307 |
+
"type": "text",
|
| 308 |
+
"text": "分布式任务调度基于分布式软总线、分布式数据管理等技术特性,构建统一的分布式服务管理(发现、同步、注册、调用)机制,支持对跨设备的应用进行远程启动、远程调用、远程连接以及迁移等操作,能够根据不同设备的能力、位置、业务运行状态、资源使用情况,以及用户的习惯和意图,选择合适的设备运行分布式任务。"
|
| 309 |
+
},
|
| 310 |
+
{
|
| 311 |
+
"type": "footer",
|
| 312 |
+
"text": "文档版本 V1.0 (2024-08-13) 版权所有 © 华为技术有限公司"
|
| 313 |
+
},
|
| 314 |
+
{
|
| 315 |
+
"type": "page_number",
|
| 316 |
+
"text": "6"
|
| 317 |
+
}
|
| 318 |
+
]
|
diagrams-and-tables/annotations/cn_diagram_14.json
ADDED
|
@@ -0,0 +1,165 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
[
|
| 2 |
+
{
|
| 3 |
+
"type": "header",
|
| 4 |
+
"text": "HarmonyOS NEXT 安全技术白皮书 5 HarmonyOS “正确的设备”系统安全架构"
|
| 5 |
+
},
|
| 6 |
+
{
|
| 7 |
+
"type": "diagram_caption",
|
| 8 |
+
"text": "图5-1 HarmonyOS 系统安全架构"
|
| 9 |
+
},
|
| 10 |
+
{
|
| 11 |
+
"type": "diagram",
|
| 12 |
+
"nodes": [
|
| 13 |
+
{
|
| 14 |
+
"id": "A",
|
| 15 |
+
"text": "云服务、应用市场"
|
| 16 |
+
},
|
| 17 |
+
{
|
| 18 |
+
"id": "B",
|
| 19 |
+
"text": "上架检测、代码唯一分发途径(签名)、OTA升级、设备查找、华为账号等"
|
| 20 |
+
},
|
| 21 |
+
{
|
| 22 |
+
"id": "C",
|
| 23 |
+
"text": "底座安全机制"
|
| 24 |
+
},
|
| 25 |
+
{
|
| 26 |
+
"id": "D",
|
| 27 |
+
"text": "加密和数据保护:文件加密、密钥管理"
|
| 28 |
+
},
|
| 29 |
+
{
|
| 30 |
+
"id": "E",
|
| 31 |
+
"text": "完整性保护:安全启动链、启动链加固、代码强制签名、XPM、JIT Fort"
|
| 32 |
+
},
|
| 33 |
+
{
|
| 34 |
+
"id": "F",
|
| 35 |
+
"text": "隔离和访问控制:AccessTOKEN、SE-Harmony、SECCOMP、应用沙盒等"
|
| 36 |
+
},
|
| 37 |
+
{
|
| 38 |
+
"id": "G",
|
| 39 |
+
"text": "漏洞防利用:PAN/PXN、PAC CFI、PAC DFI、HKIP、XOM、uPPL、坚盾守护模式等"
|
| 40 |
+
},
|
| 41 |
+
{
|
| 42 |
+
"id": "H",
|
| 43 |
+
"text": "HarmonyOS内核&系统框架"
|
| 44 |
+
},
|
| 45 |
+
{
|
| 46 |
+
"id": "I",
|
| 47 |
+
"text": "芯片"
|
| 48 |
+
},
|
| 49 |
+
{
|
| 50 |
+
"id": "J",
|
| 51 |
+
"text": "计算可信根"
|
| 52 |
+
},
|
| 53 |
+
{
|
| 54 |
+
"id": "K",
|
| 55 |
+
"text": "内存安全:PAC保护"
|
| 56 |
+
},
|
| 57 |
+
{
|
| 58 |
+
"id": "L",
|
| 59 |
+
"text": "安全隔离:SE、Trustzone"
|
| 60 |
+
},
|
| 61 |
+
{
|
| 62 |
+
"id": "M",
|
| 63 |
+
"text": "启动可信根"
|
| 64 |
+
},
|
| 65 |
+
{
|
| 66 |
+
"id": "N",
|
| 67 |
+
"text": "安全启动:一机一授权"
|
| 68 |
+
},
|
| 69 |
+
{
|
| 70 |
+
"id": "O",
|
| 71 |
+
"text": "启动链:PAC CFI、DICE启动"
|
| 72 |
+
},
|
| 73 |
+
{
|
| 74 |
+
"id": "P",
|
| 75 |
+
"text": "存储可信根"
|
| 76 |
+
},
|
| 77 |
+
{
|
| 78 |
+
"id": "Q",
|
| 79 |
+
"text": "数据加密:inline加密引擎、硬件加密引擎等"
|
| 80 |
+
}
|
| 81 |
+
],
|
| 82 |
+
"relationships": [
|
| 83 |
+
{
|
| 84 |
+
"source": "A",
|
| 85 |
+
"target": "B"
|
| 86 |
+
},
|
| 87 |
+
{
|
| 88 |
+
"source": "C",
|
| 89 |
+
"target": "D"
|
| 90 |
+
},
|
| 91 |
+
{
|
| 92 |
+
"source": "C",
|
| 93 |
+
"target": "E"
|
| 94 |
+
},
|
| 95 |
+
{
|
| 96 |
+
"source": "C",
|
| 97 |
+
"target": "F"
|
| 98 |
+
},
|
| 99 |
+
{
|
| 100 |
+
"source": "C",
|
| 101 |
+
"target": "G"
|
| 102 |
+
},
|
| 103 |
+
{
|
| 104 |
+
"source": "C",
|
| 105 |
+
"target": "H"
|
| 106 |
+
},
|
| 107 |
+
{
|
| 108 |
+
"source": "I",
|
| 109 |
+
"target": "J"
|
| 110 |
+
},
|
| 111 |
+
{
|
| 112 |
+
"source": "J",
|
| 113 |
+
"target": "K"
|
| 114 |
+
},
|
| 115 |
+
{
|
| 116 |
+
"source": "J",
|
| 117 |
+
"target": "L"
|
| 118 |
+
},
|
| 119 |
+
{
|
| 120 |
+
"source": "I",
|
| 121 |
+
"target": "M"
|
| 122 |
+
},
|
| 123 |
+
{
|
| 124 |
+
"source": "M",
|
| 125 |
+
"target": "N"
|
| 126 |
+
},
|
| 127 |
+
{
|
| 128 |
+
"source": "M",
|
| 129 |
+
"target": "O"
|
| 130 |
+
},
|
| 131 |
+
{
|
| 132 |
+
"source": "I",
|
| 133 |
+
"target": "P"
|
| 134 |
+
},
|
| 135 |
+
{
|
| 136 |
+
"source": "P",
|
| 137 |
+
"target": "Q"
|
| 138 |
+
}
|
| 139 |
+
]
|
| 140 |
+
},
|
| 141 |
+
{
|
| 142 |
+
"type": "text",
|
| 143 |
+
"text": "遵循可信计算理论,HarmonyOS 的安全设计整体根植于信任根,根据不同的保护对象和资产选择合适的信任根,如芯片、服务器等。"
|
| 144 |
+
},
|
| 145 |
+
{
|
| 146 |
+
"type": "title",
|
| 147 |
+
"text": "完整性保护"
|
| 148 |
+
},
|
| 149 |
+
{
|
| 150 |
+
"type": "text",
|
| 151 |
+
"text": "是系统安全的根基,确保系统软件和应用程序全生命周期的完整合法,未被非法篡改,是支撑安全策略正确实施的前提。"
|
| 152 |
+
},
|
| 153 |
+
{
|
| 154 |
+
"type": "title",
|
| 155 |
+
"text": "隔离及访问控制"
|
| 156 |
+
},
|
| 157 |
+
{
|
| 158 |
+
"type": "footer",
|
| 159 |
+
"text": "文档版本 V1.0 (2024-08-13) 版权所有 © 华为技术有限公司"
|
| 160 |
+
},
|
| 161 |
+
{
|
| 162 |
+
"type": "page_number",
|
| 163 |
+
"text": "23"
|
| 164 |
+
}
|
| 165 |
+
]
|
diagrams-and-tables/annotations/cn_diagram_15.json
ADDED
|
@@ -0,0 +1,101 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
[
|
| 2 |
+
{
|
| 3 |
+
"type": "header",
|
| 4 |
+
"text": "HarmonyOS NEXT 安全技术白皮书 6 HarmonyOS “正确的访问数据” 分级访问控制架构"
|
| 5 |
+
},
|
| 6 |
+
{
|
| 7 |
+
"type": "diagram_caption",
|
| 8 |
+
"text": "发送方生成的加密数据格式"
|
| 9 |
+
},
|
| 10 |
+
{
|
| 11 |
+
"type": "diagram",
|
| 12 |
+
"nodes": [
|
| 13 |
+
{
|
| 14 |
+
"id": "A",
|
| 15 |
+
"text": "加密数据格式"
|
| 16 |
+
},
|
| 17 |
+
{
|
| 18 |
+
"id": "B",
|
| 19 |
+
"text": "数据密文(数据加密密钥加密)"
|
| 20 |
+
},
|
| 21 |
+
{
|
| 22 |
+
"id": "C",
|
| 23 |
+
"text": "数据明文"
|
| 24 |
+
},
|
| 25 |
+
{
|
| 26 |
+
"id": "D",
|
| 27 |
+
"text": "数据权限文件密文(数据所有者私钥签名,接收方公钥加密)"
|
| 28 |
+
},
|
| 29 |
+
{
|
| 30 |
+
"id": "E",
|
| 31 |
+
"text": "数据加密密钥(AES-GCM密钥)"
|
| 32 |
+
},
|
| 33 |
+
{
|
| 34 |
+
"id": "F",
|
| 35 |
+
"text": "数据访问控制信息"
|
| 36 |
+
},
|
| 37 |
+
{
|
| 38 |
+
"id": "G",
|
| 39 |
+
"text": "数据执行权限(是否允许打印、截屏等)"
|
| 40 |
+
},
|
| 41 |
+
{
|
| 42 |
+
"id": "H",
|
| 43 |
+
"text": "授权访问用户信息(可访问该文件的账号信息)"
|
| 44 |
+
}
|
| 45 |
+
],
|
| 46 |
+
"relationships": [
|
| 47 |
+
{
|
| 48 |
+
"source": "A",
|
| 49 |
+
"target": "B"
|
| 50 |
+
},
|
| 51 |
+
{
|
| 52 |
+
"source": "A",
|
| 53 |
+
"target": "D"
|
| 54 |
+
},
|
| 55 |
+
{
|
| 56 |
+
"source": "B",
|
| 57 |
+
"target": "C"
|
| 58 |
+
},
|
| 59 |
+
{
|
| 60 |
+
"source": "D",
|
| 61 |
+
"target": "E"
|
| 62 |
+
},
|
| 63 |
+
{
|
| 64 |
+
"source": "D",
|
| 65 |
+
"target": "F"
|
| 66 |
+
},
|
| 67 |
+
{
|
| 68 |
+
"source": "F",
|
| 69 |
+
"target": "G"
|
| 70 |
+
},
|
| 71 |
+
{
|
| 72 |
+
"source": "F",
|
| 73 |
+
"target": "H"
|
| 74 |
+
}
|
| 75 |
+
]
|
| 76 |
+
},
|
| 77 |
+
{
|
| 78 |
+
"type": "text",
|
| 79 |
+
"text": "数据的接收方如果想要访问数据明文,必须先获取数据加密密钥(AES-GCM 密钥)。根据当前的加密数据格式,数据加密密钥作为数据权限文件的一部分,被数据所有者指定的接收方数据保护凭据公钥加密。授权用户设备上的系统数据加密分享服务,会使用本地管理的数据保护凭据私钥进行解密,并验证数据权限文件的完整性(使用数据所有者的数据保护凭据公钥验签);解密后会获得数据执行权限和数据加密密钥,后者会进一步用于解密数据密文获得明文数据。"
|
| 80 |
+
},
|
| 81 |
+
{
|
| 82 |
+
"type": "text",
|
| 83 |
+
"text": "系统数据加密分享服务定义了绑定访问控制策略的加密数据格式,保证了用户对数据设置的访问控制权限不可剥离、不可篡改;任意非授权的用户都无法解密数据权限文件。"
|
| 84 |
+
},
|
| 85 |
+
{
|
| 86 |
+
"type": "title",
|
| 87 |
+
"text": "基于动态沙箱的数据权限管控"
|
| 88 |
+
},
|
| 89 |
+
{
|
| 90 |
+
"type": "text",
|
| 91 |
+
"text": "为实现数据在接收方的延伸控制,用户选定应用访问数据时,系统数据加密分享服务会将数据执行权限为 HarmonyOS 上的应用权限,并安装对应权限的应用沙箱;该沙箱对于底层系统服务(包括文件系统、以及屏幕控制、打印服务等)的访问控制权限,全部由系统数据加密分享服务定义。当该应用沙箱访问数据时,对底层系统服务的访问行为均受到系统控制,从而保证发送方设置的数据执行权限在接收方得到管控。"
|
| 92 |
+
},
|
| 93 |
+
{
|
| 94 |
+
"type": "footer",
|
| 95 |
+
"text": "文档版本 V1.0 (2024-08-13) 版权所有 © 华为技术有限公司"
|
| 96 |
+
},
|
| 97 |
+
{
|
| 98 |
+
"type": "page_number",
|
| 99 |
+
"text": "42"
|
| 100 |
+
}
|
| 101 |
+
]
|
diagrams-and-tables/annotations/cn_diagram_16.json
ADDED
|
@@ -0,0 +1,301 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
[
|
| 2 |
+
{
|
| 3 |
+
"type": "header",
|
| 4 |
+
"text": "HarmonyOS NEXT 安全技术白皮书 7 HarmonyOS 应用生态治理架构"
|
| 5 |
+
},
|
| 6 |
+
{
|
| 7 |
+
"type": "diagram_caption",
|
| 8 |
+
"text": "图7-2 HarmonyOS 应用程序生命周期关键技术和措施"
|
| 9 |
+
},
|
| 10 |
+
{
|
| 11 |
+
"type": "diagram",
|
| 12 |
+
"nodes": [
|
| 13 |
+
{
|
| 14 |
+
"id": "A",
|
| 15 |
+
"text": "开发阶段(开发工具)"
|
| 16 |
+
},
|
| 17 |
+
{
|
| 18 |
+
"id": "B",
|
| 19 |
+
"text": "开发"
|
| 20 |
+
},
|
| 21 |
+
{
|
| 22 |
+
"id": "C",
|
| 23 |
+
"text": "开发者实名认证"
|
| 24 |
+
},
|
| 25 |
+
{
|
| 26 |
+
"id": "D",
|
| 27 |
+
"text": "安全编码编译"
|
| 28 |
+
},
|
| 29 |
+
{
|
| 30 |
+
"id": "E",
|
| 31 |
+
"text": "安全调试模式"
|
| 32 |
+
},
|
| 33 |
+
{
|
| 34 |
+
"id": "F",
|
| 35 |
+
"text": "代码混淆"
|
| 36 |
+
},
|
| 37 |
+
{
|
| 38 |
+
"id": "G",
|
| 39 |
+
"text": "安全检测"
|
| 40 |
+
},
|
| 41 |
+
{
|
| 42 |
+
"id": "H",
|
| 43 |
+
"text": "上架"
|
| 44 |
+
},
|
| 45 |
+
{
|
| 46 |
+
"id": "I",
|
| 47 |
+
"text": "发布profile申请"
|
| 48 |
+
},
|
| 49 |
+
{
|
| 50 |
+
"id": "J",
|
| 51 |
+
"text": "开发者证书签名"
|
| 52 |
+
},
|
| 53 |
+
{
|
| 54 |
+
"id": "K",
|
| 55 |
+
"text": "发布阶段(应用市场)"
|
| 56 |
+
},
|
| 57 |
+
{
|
| 58 |
+
"id": "L",
|
| 59 |
+
"text": "审核和检测"
|
| 60 |
+
},
|
| 61 |
+
{
|
| 62 |
+
"id": "M",
|
| 63 |
+
"text": "开发者、应用合法性"
|
| 64 |
+
},
|
| 65 |
+
{
|
| 66 |
+
"id": "N",
|
| 67 |
+
"text": "安全隐私漏洞检测"
|
| 68 |
+
},
|
| 69 |
+
{
|
| 70 |
+
"id": "O",
|
| 71 |
+
"text": "应用行为检测"
|
| 72 |
+
},
|
| 73 |
+
{
|
| 74 |
+
"id": "P",
|
| 75 |
+
"text": "发布"
|
| 76 |
+
},
|
| 77 |
+
{
|
| 78 |
+
"id": "Q",
|
| 79 |
+
"text": "应用加密"
|
| 80 |
+
},
|
| 81 |
+
{
|
| 82 |
+
"id": "R",
|
| 83 |
+
"text": "代码签名"
|
| 84 |
+
},
|
| 85 |
+
{
|
| 86 |
+
"id": "S",
|
| 87 |
+
"text": "下架"
|
| 88 |
+
},
|
| 89 |
+
{
|
| 90 |
+
"id": "T",
|
| 91 |
+
"text": "违规应用下架"
|
| 92 |
+
},
|
| 93 |
+
{
|
| 94 |
+
"id": "U",
|
| 95 |
+
"text": "吊销开发者证书"
|
| 96 |
+
},
|
| 97 |
+
{
|
| 98 |
+
"id": "V",
|
| 99 |
+
"text": "运行阶段(操作系统)"
|
| 100 |
+
},
|
| 101 |
+
{
|
| 102 |
+
"id": "W",
|
| 103 |
+
"text": "安装"
|
| 104 |
+
},
|
| 105 |
+
{
|
| 106 |
+
"id": "X",
|
| 107 |
+
"text": "来源管控"
|
| 108 |
+
},
|
| 109 |
+
{
|
| 110 |
+
"id": "Y",
|
| 111 |
+
"text": "企业应用"
|
| 112 |
+
},
|
| 113 |
+
{
|
| 114 |
+
"id": "Z",
|
| 115 |
+
"text": "运行"
|
| 116 |
+
},
|
| 117 |
+
{
|
| 118 |
+
"id": "AA",
|
| 119 |
+
"text": "应用沙箱隔离"
|
| 120 |
+
},
|
| 121 |
+
{
|
| 122 |
+
"id": "AB",
|
| 123 |
+
"text": "隐私权限保护"
|
| 124 |
+
},
|
| 125 |
+
{
|
| 126 |
+
"id": "AC",
|
| 127 |
+
"text": "安全控件/picker"
|
| 128 |
+
},
|
| 129 |
+
{
|
| 130 |
+
"id": "AD",
|
| 131 |
+
"text": "应用风险行为管控"
|
| 132 |
+
},
|
| 133 |
+
{
|
| 134 |
+
"id": "AE",
|
| 135 |
+
"text": "更新"
|
| 136 |
+
},
|
| 137 |
+
{
|
| 138 |
+
"id": "AF",
|
| 139 |
+
"text": "禁止未经检测的热更新"
|
| 140 |
+
}
|
| 141 |
+
],
|
| 142 |
+
"relationships": [
|
| 143 |
+
{
|
| 144 |
+
"source": "A",
|
| 145 |
+
"target": "K"
|
| 146 |
+
},
|
| 147 |
+
{
|
| 148 |
+
"source": "K",
|
| 149 |
+
"target": "V"
|
| 150 |
+
},
|
| 151 |
+
{
|
| 152 |
+
"source": "A",
|
| 153 |
+
"target": "B"
|
| 154 |
+
},
|
| 155 |
+
{
|
| 156 |
+
"source": "B",
|
| 157 |
+
"target": "C"
|
| 158 |
+
},
|
| 159 |
+
{
|
| 160 |
+
"source": "B",
|
| 161 |
+
"target": "D"
|
| 162 |
+
},
|
| 163 |
+
{
|
| 164 |
+
"source": "B",
|
| 165 |
+
"target": "E"
|
| 166 |
+
},
|
| 167 |
+
{
|
| 168 |
+
"source": "B",
|
| 169 |
+
"target": "F"
|
| 170 |
+
},
|
| 171 |
+
{
|
| 172 |
+
"source": "B",
|
| 173 |
+
"target": "G"
|
| 174 |
+
},
|
| 175 |
+
{
|
| 176 |
+
"source": "A",
|
| 177 |
+
"target": "H"
|
| 178 |
+
},
|
| 179 |
+
{
|
| 180 |
+
"source": "H",
|
| 181 |
+
"target": "I"
|
| 182 |
+
},
|
| 183 |
+
{
|
| 184 |
+
"source": "H",
|
| 185 |
+
"target": "J"
|
| 186 |
+
},
|
| 187 |
+
{
|
| 188 |
+
"source": "K",
|
| 189 |
+
"target": "L"
|
| 190 |
+
},
|
| 191 |
+
{
|
| 192 |
+
"source": "L",
|
| 193 |
+
"target": "M"
|
| 194 |
+
},
|
| 195 |
+
{
|
| 196 |
+
"source": "L",
|
| 197 |
+
"target": "N"
|
| 198 |
+
},
|
| 199 |
+
{
|
| 200 |
+
"source": "L",
|
| 201 |
+
"target": "O"
|
| 202 |
+
},
|
| 203 |
+
{
|
| 204 |
+
"source": "K",
|
| 205 |
+
"target": "P"
|
| 206 |
+
},
|
| 207 |
+
{
|
| 208 |
+
"source": "P",
|
| 209 |
+
"target": "Q"
|
| 210 |
+
},
|
| 211 |
+
{
|
| 212 |
+
"source": "P",
|
| 213 |
+
"target": "R"
|
| 214 |
+
},
|
| 215 |
+
{
|
| 216 |
+
"source": "K",
|
| 217 |
+
"target": "S"
|
| 218 |
+
},
|
| 219 |
+
{
|
| 220 |
+
"source": "S",
|
| 221 |
+
"target": "T"
|
| 222 |
+
},
|
| 223 |
+
{
|
| 224 |
+
"source": "S",
|
| 225 |
+
"target": "U"
|
| 226 |
+
},
|
| 227 |
+
{
|
| 228 |
+
"source": "V",
|
| 229 |
+
"target": "W"
|
| 230 |
+
},
|
| 231 |
+
{
|
| 232 |
+
"source": "W",
|
| 233 |
+
"target": "X"
|
| 234 |
+
},
|
| 235 |
+
{
|
| 236 |
+
"source": "W",
|
| 237 |
+
"target": "Y"
|
| 238 |
+
},
|
| 239 |
+
{
|
| 240 |
+
"source": "V",
|
| 241 |
+
"target": "Z"
|
| 242 |
+
},
|
| 243 |
+
{
|
| 244 |
+
"source": "Z",
|
| 245 |
+
"target": "AA"
|
| 246 |
+
},
|
| 247 |
+
{
|
| 248 |
+
"source": "Z",
|
| 249 |
+
"target": "AB"
|
| 250 |
+
},
|
| 251 |
+
{
|
| 252 |
+
"source": "Z",
|
| 253 |
+
"target": "AC"
|
| 254 |
+
},
|
| 255 |
+
{
|
| 256 |
+
"source": "Z",
|
| 257 |
+
"target": "AD"
|
| 258 |
+
},
|
| 259 |
+
{
|
| 260 |
+
"source": "V",
|
| 261 |
+
"target": "AE"
|
| 262 |
+
},
|
| 263 |
+
{
|
| 264 |
+
"source": "AE",
|
| 265 |
+
"target": "AF"
|
| 266 |
+
}
|
| 267 |
+
]
|
| 268 |
+
},
|
| 269 |
+
{
|
| 270 |
+
"type": "text",
|
| 271 |
+
"text": "如图 7-2 所示,我们在应用全生命周期的不同阶段,分别提供不同的关键技术和措施,来解决生态构建的重大挑战问题。"
|
| 272 |
+
},
|
| 273 |
+
{
|
| 274 |
+
"type": "title",
|
| 275 |
+
"text": "7.2 HarmonyOS 应用程序 “纯净” 开发"
|
| 276 |
+
},
|
| 277 |
+
{
|
| 278 |
+
"type": "text",
|
| 279 |
+
"text": "对于 HarmonyOS 开发者,提供开发者注册、账号管理、实名认证,并进行开发者证书管理,开发者的应用开发以及调测提供配套管理能力。"
|
| 280 |
+
},
|
| 281 |
+
{
|
| 282 |
+
"type": "text",
|
| 283 |
+
"text": "开发工具提供安全能力,帮助开发者进行代码级以及二进制相关的安全与隐私检查,确保开发者能够快速开发出高质量 HarmonyOS 程序。"
|
| 284 |
+
},
|
| 285 |
+
{
|
| 286 |
+
"type": "text",
|
| 287 |
+
"text": "同时,DevEco Studio 为开发者提供应用来源管控和完整性保护的安全能力,例如:DevEco Studio 能够自动化帮助开发者进行秘钥的生成和管理,自动化的签名管理、自动化的调试证书管理和自动化的调测设备管理,方便开发者开发的应用或服务能够快速上架。"
|
| 288 |
+
},
|
| 289 |
+
{
|
| 290 |
+
"type": "text",
|
| 291 |
+
"text": "实名认证要求:依据国家互联网信息办公室 2016 年 6 月 28 日发布的《移动互联网应用程序信息服务管理规定》,同时为了促进生态健康有序发展,保护开发者、用户的合法权益,申请成为一个 HarmonyOS 开发者需要注册账号,注册账号时可以同步进行实名认证,实名认证包括个人开发者实名认证和企业开发者实名认证;确保应用的开发者是可以被追溯的。在应用上架发布环节仍需要实名认证,建议注册时立即实名认证。"
|
| 292 |
+
},
|
| 293 |
+
{
|
| 294 |
+
"type": "footer",
|
| 295 |
+
"text": "文档版本 V1.0 (2024-08-13) 版权所有 © 华为技术有限公司"
|
| 296 |
+
},
|
| 297 |
+
{
|
| 298 |
+
"type": "page_number",
|
| 299 |
+
"text": "45"
|
| 300 |
+
}
|
| 301 |
+
]
|
diagrams-and-tables/annotations/cn_diagram_17.json
ADDED
|
@@ -0,0 +1,83 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
[
|
| 2 |
+
{
|
| 3 |
+
"type": "header",
|
| 4 |
+
"text": "HarmonyOS NEXT 安全技术白皮书 11 HarmonyOS 安全能力开放使能生态"
|
| 5 |
+
},
|
| 6 |
+
{
|
| 7 |
+
"type": "text",
|
| 8 |
+
"text": "意 URL 检测能力向三方开发者提供了集成简单、免运营、可信赖的安全服务,降低安全浏览服务的实现成本。"
|
| 9 |
+
},
|
| 10 |
+
{
|
| 11 |
+
"type": "title",
|
| 12 |
+
"text": "应用设备状态检测 (Device Verify)"
|
| 13 |
+
},
|
| 14 |
+
{
|
| 15 |
+
"type": "text",
|
| 16 |
+
"text": "应用设备状态检测向开发者提供了管理应用在某设备上使用状态的能力,该服务基于设备证书对设备身份进行认证并签发 DeviceToken,应用的服务器使用 DeviceToken 到 Device Security 服务器查询和管理应用在该设备的使用状态。"
|
| 17 |
+
},
|
| 18 |
+
{
|
| 19 |
+
"type": "text",
|
| 20 |
+
"text": "应用场景:对应用在某台设备上的使用状态进行管理和检测,包括判断应用是否在该设备上首次安装,或在该设备上用户是否已获取了优惠券等的状态检测,以支撑业务进行新用户营销活动。"
|
| 21 |
+
},
|
| 22 |
+
{
|
| 23 |
+
"type": "title",
|
| 24 |
+
"text": "可信服务证明"
|
| 25 |
+
},
|
| 26 |
+
{
|
| 27 |
+
"type": "text",
|
| 28 |
+
"text": "位置信息的安全风险:在一些对安全性较高的场景下,应用在终端侧会获取设备的位置信息,应用服务器把位置信息当做因子一起参与业务逻辑判断或风控检测。但由于应用在 REE 侧获取的位置信息存在被篡改和仿冒的风险,带来以下风险:\n1) 营销活动薅羊毛:电商、银行类应用经常会在指定城市开展营销活动。如果位置信息被篡改,可以快速切换到目标城市,获得参与营销活动资格;\n2) 逃避风控检测:诈骗集团通过前期的诈骗资料收集以及植入木马(盗取验证码和密码)等,交易时通过返回被篡改的地理位置逃避风险的检测;\n3) 游戏外挂:对一些依赖地理位置信息的应用实施攻击行为,通过篡改地理位置,可以瞬间移动到 NPC,破坏游戏平衡。\n人脸图像存在与位置信息同样的安全风险:在金融类应用中,一些业务需要人脸识别通过后才能完成,当前应用的流程一般是先采集人脸数据、再上传到应用服务器完成人脸识别。但如果在设备采集的人脸被篡改,服务器人脸识别通过,带来安全风险、甚至财产损失。\nHarmonyOS 系统向应用提供安全摄像头和安全地理位置能力,如下图所示:"
|
| 29 |
+
},
|
| 30 |
+
{
|
| 31 |
+
"type": "diagram",
|
| 32 |
+
"nodes": [
|
| 33 |
+
{
|
| 34 |
+
"id": "A",
|
| 35 |
+
"text": "业务APP云侧服务"
|
| 36 |
+
},
|
| 37 |
+
{
|
| 38 |
+
"id": "B",
|
| 39 |
+
"text": "业务APP"
|
| 40 |
+
},
|
| 41 |
+
{
|
| 42 |
+
"id": "C",
|
| 43 |
+
"text": "Kit"
|
| 44 |
+
},
|
| 45 |
+
{
|
| 46 |
+
"id": "D",
|
| 47 |
+
"text": "安全摄像头"
|
| 48 |
+
},
|
| 49 |
+
{
|
| 50 |
+
"id": "E",
|
| 51 |
+
"text": "安全地理位置"
|
| 52 |
+
}
|
| 53 |
+
],
|
| 54 |
+
"relationships": [
|
| 55 |
+
{
|
| 56 |
+
"source": "A",
|
| 57 |
+
"target": "B",
|
| 58 |
+
"label": "上传结果到云服务,完成验证"
|
| 59 |
+
},
|
| 60 |
+
{
|
| 61 |
+
"source": "B",
|
| 62 |
+
"target": "C",
|
| 63 |
+
"label": "调用安全摄像头接口或安全地理位置接口"
|
| 64 |
+
},
|
| 65 |
+
{
|
| 66 |
+
"source": "C",
|
| 67 |
+
"target": "D"
|
| 68 |
+
},
|
| 69 |
+
{
|
| 70 |
+
"source": "C",
|
| 71 |
+
"target": "E"
|
| 72 |
+
}
|
| 73 |
+
]
|
| 74 |
+
},
|
| 75 |
+
{
|
| 76 |
+
"type": "footer",
|
| 77 |
+
"text": "文档版本 V1.0 (2024-08-13) 版权所有 © 华为技术有限公司"
|
| 78 |
+
},
|
| 79 |
+
{
|
| 80 |
+
"type": "page_number",
|
| 81 |
+
"text": "64"
|
| 82 |
+
}
|
| 83 |
+
]
|
diagrams-and-tables/annotations/cn_diagram_18.json
ADDED
|
@@ -0,0 +1,177 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
[
|
| 2 |
+
{
|
| 3 |
+
"type": "text",
|
| 4 |
+
"text": "\"BMC 启动至 CPU 上电\"之间长达数百毫秒的安全盲区,防止攻击者利用预启动阶段进行恶意植入或篡改。图 5 展示了鲲鹏 TPCM 的整体实现架构。"
|
| 5 |
+
},
|
| 6 |
+
{
|
| 7 |
+
"type": "diagram_caption",
|
| 8 |
+
"text": "图 5 鲲鹏 TPCM 整体架构"
|
| 9 |
+
},
|
| 10 |
+
{
|
| 11 |
+
"type": "diagram",
|
| 12 |
+
"nodes": [
|
| 13 |
+
{
|
| 14 |
+
"id": "A",
|
| 15 |
+
"text": "可信管理中心"
|
| 16 |
+
},
|
| 17 |
+
{
|
| 18 |
+
"id": "B",
|
| 19 |
+
"text": "计算部件"
|
| 20 |
+
},
|
| 21 |
+
{
|
| 22 |
+
"id": "C",
|
| 23 |
+
"text": "操作系统"
|
| 24 |
+
},
|
| 25 |
+
{
|
| 26 |
+
"id": "D",
|
| 27 |
+
"text": "应用"
|
| 28 |
+
},
|
| 29 |
+
{
|
| 30 |
+
"id": "E",
|
| 31 |
+
"text": "应用"
|
| 32 |
+
},
|
| 33 |
+
{
|
| 34 |
+
"id": "F",
|
| 35 |
+
"text": "度量代理"
|
| 36 |
+
},
|
| 37 |
+
{
|
| 38 |
+
"id": "G",
|
| 39 |
+
"text": "OS Loader(Grub)"
|
| 40 |
+
},
|
| 41 |
+
{
|
| 42 |
+
"id": "H",
|
| 43 |
+
"text": "OS度量控制"
|
| 44 |
+
},
|
| 45 |
+
{
|
| 46 |
+
"id": "I",
|
| 47 |
+
"text": "BIOS"
|
| 48 |
+
},
|
| 49 |
+
{
|
| 50 |
+
"id": "J",
|
| 51 |
+
"text": "华为自研Grub度量控制"
|
| 52 |
+
},
|
| 53 |
+
{
|
| 54 |
+
"id": "K",
|
| 55 |
+
"text": "鲲鹏主板"
|
| 56 |
+
},
|
| 57 |
+
{
|
| 58 |
+
"id": "L",
|
| 59 |
+
"text": "防护部件"
|
| 60 |
+
},
|
| 61 |
+
{
|
| 62 |
+
"id": "M",
|
| 63 |
+
"text": "iBMC"
|
| 64 |
+
},
|
| 65 |
+
{
|
| 66 |
+
"id": "N",
|
| 67 |
+
"text": "应用"
|
| 68 |
+
},
|
| 69 |
+
{
|
| 70 |
+
"id": "O",
|
| 71 |
+
"text": "TSB软件基"
|
| 72 |
+
},
|
| 73 |
+
{
|
| 74 |
+
"id": "P",
|
| 75 |
+
"text": "华为自研TPCM固件"
|
| 76 |
+
},
|
| 77 |
+
{
|
| 78 |
+
"id": "Q",
|
| 79 |
+
"text": "带外管理面硬件"
|
| 80 |
+
},
|
| 81 |
+
{
|
| 82 |
+
"id": "R",
|
| 83 |
+
"text": "TCM"
|
| 84 |
+
}
|
| 85 |
+
],
|
| 86 |
+
"relationships": [
|
| 87 |
+
{
|
| 88 |
+
"source": "A",
|
| 89 |
+
"target": "B"
|
| 90 |
+
},
|
| 91 |
+
{
|
| 92 |
+
"source": "A",
|
| 93 |
+
"target": "L"
|
| 94 |
+
},
|
| 95 |
+
{
|
| 96 |
+
"source": "B",
|
| 97 |
+
"target": "C"
|
| 98 |
+
},
|
| 99 |
+
{
|
| 100 |
+
"source": "C",
|
| 101 |
+
"target": "D"
|
| 102 |
+
},
|
| 103 |
+
{
|
| 104 |
+
"source": "C",
|
| 105 |
+
"target": "E"
|
| 106 |
+
},
|
| 107 |
+
{
|
| 108 |
+
"source": "C",
|
| 109 |
+
"target": "F"
|
| 110 |
+
},
|
| 111 |
+
{
|
| 112 |
+
"source": "B",
|
| 113 |
+
"target": "G"
|
| 114 |
+
},
|
| 115 |
+
{
|
| 116 |
+
"source": "G",
|
| 117 |
+
"target": "H"
|
| 118 |
+
},
|
| 119 |
+
{
|
| 120 |
+
"source": "B",
|
| 121 |
+
"target": "I"
|
| 122 |
+
},
|
| 123 |
+
{
|
| 124 |
+
"source": "I",
|
| 125 |
+
"target": "J"
|
| 126 |
+
},
|
| 127 |
+
{
|
| 128 |
+
"source": "B",
|
| 129 |
+
"target": "K"
|
| 130 |
+
},
|
| 131 |
+
{
|
| 132 |
+
"source": "L",
|
| 133 |
+
"target": "M"
|
| 134 |
+
},
|
| 135 |
+
{
|
| 136 |
+
"source": "M",
|
| 137 |
+
"target": "N"
|
| 138 |
+
},
|
| 139 |
+
{
|
| 140 |
+
"source": "M",
|
| 141 |
+
"target": "O"
|
| 142 |
+
},
|
| 143 |
+
{
|
| 144 |
+
"source": "L",
|
| 145 |
+
"target": "P"
|
| 146 |
+
},
|
| 147 |
+
{
|
| 148 |
+
"source": "L",
|
| 149 |
+
"target": "Q"
|
| 150 |
+
},
|
| 151 |
+
{
|
| 152 |
+
"source": "Q",
|
| 153 |
+
"target": "R"
|
| 154 |
+
}
|
| 155 |
+
]
|
| 156 |
+
},
|
| 157 |
+
{
|
| 158 |
+
"type": "text",
|
| 159 |
+
"text": "TPCM 技术的实现依托可信计算 3.0 架构,强调“计算组件”与“防护组件”的物理与逻辑隔离。系统中的 BMC 作为防护部件,运行可信软件基 (Trusted Software Base, TSB),在 BMC 核与独立的 TCM 核之间建立加密通信信道,并通过度量策略引擎和策略匹配模块对 BIOS、引导程序、操作系统核心、驱动模块乃至关键应用程序进行主动度量与比对。与此同时,运行在主机操作系统层的 TSB Agent 负责收集系统运行状态与动态完整性信息,并上报至 BMC 侧的度量控制模块。一旦系统中存在未授权的组件加载、程序行为超出策略范围,或白名单匹配失败,TPCM 系统可即时采取控制措施,例如中断异常进程、关闭被感染的 CPU 核心、冻结可疑模块加载,乃至强制重启服务器,从而形成一个完整的“发现—判断—控制”防御系统。"
|
| 160 |
+
},
|
| 161 |
+
{
|
| 162 |
+
"type": "title",
|
| 163 |
+
"text": "3.2 计算昇腾算力基础设施安全"
|
| 164 |
+
},
|
| 165 |
+
{
|
| 166 |
+
"type": "text",
|
| 167 |
+
"text": "华为昇腾处理器作为面向 AI 计算场景的自研 NPU,凭借高带宽内存、高吞吐率 AI Core 架构以及完整的软件栈支持,在云端和数据中心已得到广泛部署。随着大模型应用对数据隐私和模型保护需求愈发强烈,构建具备可信保护能力的 AI 执行环境成为 NPU 系统设计的重要课题。尤其在多租户、混合信任的云环境中,如何保障模型和数据在 AI 加速器上运行时不被泄露或篡改,已成为可信 AI 基础设施构建的核心问题。"
|
| 168 |
+
},
|
| 169 |
+
{
|
| 170 |
+
"type": "footer",
|
| 171 |
+
"text": "文档版本 V1.0 版权所有 © 华为技术有限公司"
|
| 172 |
+
},
|
| 173 |
+
{
|
| 174 |
+
"type": "page_number",
|
| 175 |
+
"text": "10"
|
| 176 |
+
}
|
| 177 |
+
]
|
diagrams-and-tables/annotations/cn_diagram_19.json
ADDED
|
@@ -0,0 +1,153 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
[
|
| 2 |
+
{
|
| 3 |
+
"type": "title",
|
| 4 |
+
"text": "NPU 可信计算"
|
| 5 |
+
},
|
| 6 |
+
{
|
| 7 |
+
"type": "text",
|
| 8 |
+
"text": "华为自研昇腾 NPU 芯片和 BMC 芯片均提供了内置硬件可信根,可提供安全启动、DICE 等安全能力,作为系统信任的“起点”,确保系统启动、运行过程中的关键操作(如固件验证、密钥生成)可被信任。抵御物理攻击(如芯片篡改)和逻辑攻击(如恶意代码注入),为上层安全机制提供“可信基础”。关键引导固件 BSBC、BaseBIOS、高安运行固件 HSM、iBMC 软件均通过 CC EAL4/5+ 高等级安全认证,为客户提供坚实算力安全底座。此外,华为昇腾服务器兼容支持标准 TPM,可为客户业务提供基于 TPM 的可信启动能力。昇腾平台还提供 NPU 应用度量与远程证明服务,能够对关键文件、强制访问控制策略及 NPU 运行状态进行持续度量,从而有效防范 NPU 关键软件组件的非授权修改,保障 NPU 软件栈的完整性与应用安全。"
|
| 9 |
+
},
|
| 10 |
+
{
|
| 11 |
+
"type": "title",
|
| 12 |
+
"text": "NPU 机密计算"
|
| 13 |
+
},
|
| 14 |
+
{
|
| 15 |
+
"type": "text",
|
| 16 |
+
"text": "为应对现实场景中复杂的信任格局,昇腾平台提出了以 NPU 为根、从硬件到运行时的全栈机密计算体系,命名为昇盾(NPU TEE),这一安全体系“以 NPU 为信任边界”,处于非可信域的主机系统,包括主机侧操作系统、驱动、AI 运行时框架和外设通信接口,无法访问 NPU TEE 内的敏感用户数据,最终实现数据在 NPU 侧的隔离与完整性校验。图 6 展示了昇腾机密计算的实现架构。"
|
| 17 |
+
},
|
| 18 |
+
{
|
| 19 |
+
"type": "diagram_caption",
|
| 20 |
+
"text": "图 6 昇腾 NPU TEE 实现架构"
|
| 21 |
+
},
|
| 22 |
+
{
|
| 23 |
+
"type": "diagram",
|
| 24 |
+
"nodes": [
|
| 25 |
+
{
|
| 26 |
+
"id": "A",
|
| 27 |
+
"text": "可信互联协议"
|
| 28 |
+
},
|
| 29 |
+
{
|
| 30 |
+
"id": "B",
|
| 31 |
+
"text": "昇腾 NPU TEE"
|
| 32 |
+
},
|
| 33 |
+
{
|
| 34 |
+
"id": "C",
|
| 35 |
+
"text": "NPU 0"
|
| 36 |
+
},
|
| 37 |
+
{
|
| 38 |
+
"id": "D",
|
| 39 |
+
"text": "TEE 扩展组件"
|
| 40 |
+
},
|
| 41 |
+
{
|
| 42 |
+
"id": "E",
|
| 43 |
+
"text": "NPU 私有内存"
|
| 44 |
+
},
|
| 45 |
+
{
|
| 46 |
+
"id": "F",
|
| 47 |
+
"text": "达芬奇计算单元"
|
| 48 |
+
},
|
| 49 |
+
{
|
| 50 |
+
"id": "G",
|
| 51 |
+
"text": "可信启动"
|
| 52 |
+
},
|
| 53 |
+
{
|
| 54 |
+
"id": "H",
|
| 55 |
+
"text": "远程证明"
|
| 56 |
+
},
|
| 57 |
+
{
|
| 58 |
+
"id": "I",
|
| 59 |
+
"text": "NPU N"
|
| 60 |
+
},
|
| 61 |
+
{
|
| 62 |
+
"id": "J",
|
| 63 |
+
"text": "TEE 扩展组件"
|
| 64 |
+
},
|
| 65 |
+
{
|
| 66 |
+
"id": "K",
|
| 67 |
+
"text": "NPU 私有内存"
|
| 68 |
+
},
|
| 69 |
+
{
|
| 70 |
+
"id": "L",
|
| 71 |
+
"text": "达芬奇计算单元"
|
| 72 |
+
},
|
| 73 |
+
{
|
| 74 |
+
"id": "M",
|
| 75 |
+
"text": "可信启动"
|
| 76 |
+
},
|
| 77 |
+
{
|
| 78 |
+
"id": "N",
|
| 79 |
+
"text": "远程证明"
|
| 80 |
+
}
|
| 81 |
+
],
|
| 82 |
+
"relationships": [
|
| 83 |
+
{
|
| 84 |
+
"source": "A",
|
| 85 |
+
"target": "C"
|
| 86 |
+
},
|
| 87 |
+
{
|
| 88 |
+
"source": "A",
|
| 89 |
+
"target": "I"
|
| 90 |
+
},
|
| 91 |
+
{
|
| 92 |
+
"source": "B",
|
| 93 |
+
"target": "C"
|
| 94 |
+
},
|
| 95 |
+
{
|
| 96 |
+
"source": "C",
|
| 97 |
+
"target": "D"
|
| 98 |
+
},
|
| 99 |
+
{
|
| 100 |
+
"source": "C",
|
| 101 |
+
"target": "E"
|
| 102 |
+
},
|
| 103 |
+
{
|
| 104 |
+
"source": "C",
|
| 105 |
+
"target": "F"
|
| 106 |
+
},
|
| 107 |
+
{
|
| 108 |
+
"source": "C",
|
| 109 |
+
"target": "G"
|
| 110 |
+
},
|
| 111 |
+
{
|
| 112 |
+
"source": "C",
|
| 113 |
+
"target": "H"
|
| 114 |
+
},
|
| 115 |
+
{
|
| 116 |
+
"source": "B",
|
| 117 |
+
"target": "I"
|
| 118 |
+
},
|
| 119 |
+
{
|
| 120 |
+
"source": "I",
|
| 121 |
+
"target": "J"
|
| 122 |
+
},
|
| 123 |
+
{
|
| 124 |
+
"source": "I",
|
| 125 |
+
"target": "K"
|
| 126 |
+
},
|
| 127 |
+
{
|
| 128 |
+
"source": "I",
|
| 129 |
+
"target": "L"
|
| 130 |
+
},
|
| 131 |
+
{
|
| 132 |
+
"source": "I",
|
| 133 |
+
"target": "M"
|
| 134 |
+
},
|
| 135 |
+
{
|
| 136 |
+
"source": "I",
|
| 137 |
+
"target": "N"
|
| 138 |
+
}
|
| 139 |
+
]
|
| 140 |
+
},
|
| 141 |
+
{
|
| 142 |
+
"type": "text",
|
| 143 |
+
"text": "昇腾平台设计了 TEE 扩展组件来实现 NPU 的信任边界,该组件对接 NPU 设备到可信互联协议上,NPU 上内存被 TEE 扩展组件隔离,使得 REE 侧恶意程序甚至管理员无法读取 NPU TEE 侧私有内存的模型和用户���理数据。在推理过程中,每个任务所使用的用户输入、中间计算结果、模型参数与 KV 缓存、甚至算子工作空间都在 NPU 私有内存上,并通过 TEE 扩展组件隔绝 REE 的访问。当 NPU 计算完当前用户任务并切换到其它用户的计算任务时,内存内容会被清除后释放,防止在共享计算资源场景下出现信息残留或交叉泄露。这一点在大模型推理中尤为关键,比如在处理 KV 缓存、注意"
|
| 144 |
+
},
|
| 145 |
+
{
|
| 146 |
+
"type": "footer",
|
| 147 |
+
"text": "文档版本 V1.0 版权所有 © 华为技术有限公司"
|
| 148 |
+
},
|
| 149 |
+
{
|
| 150 |
+
"type": "page_number",
|
| 151 |
+
"text": "11"
|
| 152 |
+
}
|
| 153 |
+
]
|
diagrams-and-tables/annotations/cn_diagram_20.json
ADDED
|
@@ -0,0 +1,218 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
[
|
| 2 |
+
{
|
| 3 |
+
"type": "text",
|
| 4 |
+
"text": "与 TDISP 等方案不同,CoDA 在当前硬件形态下即具备部署能力,且不依赖于异构设备进行安全认证与通道加解密,从而大幅降低部署门槛与复杂度。"
|
| 5 |
+
},
|
| 6 |
+
{
|
| 7 |
+
"type": "diagram_caption",
|
| 8 |
+
"text": "图 8 基于 PCIPC 模块的机密设备直通"
|
| 9 |
+
},
|
| 10 |
+
{
|
| 11 |
+
"type": "diagram",
|
| 12 |
+
"nodes": [
|
| 13 |
+
{
|
| 14 |
+
"id": "A",
|
| 15 |
+
"text": "Normal world"
|
| 16 |
+
},
|
| 17 |
+
{
|
| 18 |
+
"id": "B",
|
| 19 |
+
"text": "Host OS"
|
| 20 |
+
},
|
| 21 |
+
{
|
| 22 |
+
"id": "C",
|
| 23 |
+
"text": "VFIO driver"
|
| 24 |
+
},
|
| 25 |
+
{
|
| 26 |
+
"id": "D",
|
| 27 |
+
"text": "PCI driver"
|
| 28 |
+
},
|
| 29 |
+
{
|
| 30 |
+
"id": "E",
|
| 31 |
+
"text": "SMMU driver"
|
| 32 |
+
},
|
| 33 |
+
{
|
| 34 |
+
"id": "F",
|
| 35 |
+
"text": "Secure world"
|
| 36 |
+
},
|
| 37 |
+
{
|
| 38 |
+
"id": "G",
|
| 39 |
+
"text": "cVM0"
|
| 40 |
+
},
|
| 41 |
+
{
|
| 42 |
+
"id": "H",
|
| 43 |
+
"text": "Dev Driver"
|
| 44 |
+
},
|
| 45 |
+
{
|
| 46 |
+
"id": "I",
|
| 47 |
+
"text": "DMA"
|
| 48 |
+
},
|
| 49 |
+
{
|
| 50 |
+
"id": "J",
|
| 51 |
+
"text": "MMIO"
|
| 52 |
+
},
|
| 53 |
+
{
|
| 54 |
+
"id": "K",
|
| 55 |
+
"text": "cVM0"
|
| 56 |
+
},
|
| 57 |
+
{
|
| 58 |
+
"id": "L",
|
| 59 |
+
"text": "Dev Driver"
|
| 60 |
+
},
|
| 61 |
+
{
|
| 62 |
+
"id": "M",
|
| 63 |
+
"text": "DMA"
|
| 64 |
+
},
|
| 65 |
+
{
|
| 66 |
+
"id": "N",
|
| 67 |
+
"text": "MMIO"
|
| 68 |
+
},
|
| 69 |
+
{
|
| 70 |
+
"id": "O",
|
| 71 |
+
"text": "tmm"
|
| 72 |
+
},
|
| 73 |
+
{
|
| 74 |
+
"id": "P",
|
| 75 |
+
"text": "DA Module"
|
| 76 |
+
},
|
| 77 |
+
{
|
| 78 |
+
"id": "Q",
|
| 79 |
+
"text": "SMMU"
|
| 80 |
+
},
|
| 81 |
+
{
|
| 82 |
+
"id": "R",
|
| 83 |
+
"text": "PCIE Root Complex (PCIPC)"
|
| 84 |
+
},
|
| 85 |
+
{
|
| 86 |
+
"id": "S",
|
| 87 |
+
"text": "PCI Device"
|
| 88 |
+
}
|
| 89 |
+
],
|
| 90 |
+
"relationships": [
|
| 91 |
+
{
|
| 92 |
+
"source": "A",
|
| 93 |
+
"target": "B"
|
| 94 |
+
},
|
| 95 |
+
{
|
| 96 |
+
"source": "B",
|
| 97 |
+
"target": "C"
|
| 98 |
+
},
|
| 99 |
+
{
|
| 100 |
+
"source": "B",
|
| 101 |
+
"target": "D"
|
| 102 |
+
},
|
| 103 |
+
{
|
| 104 |
+
"source": "B",
|
| 105 |
+
"target": "E"
|
| 106 |
+
},
|
| 107 |
+
{
|
| 108 |
+
"source": "C",
|
| 109 |
+
"target": "P",
|
| 110 |
+
"label": "Forward vfio_pci_rw"
|
| 111 |
+
},
|
| 112 |
+
{
|
| 113 |
+
"source": "D",
|
| 114 |
+
"target": "P",
|
| 115 |
+
"label": "Forward msi"
|
| 116 |
+
},
|
| 117 |
+
{
|
| 118 |
+
"source": "E",
|
| 119 |
+
"target": "P",
|
| 120 |
+
"label": "Forward SMMU confia"
|
| 121 |
+
},
|
| 122 |
+
{
|
| 123 |
+
"source": "F",
|
| 124 |
+
"target": "G"
|
| 125 |
+
},
|
| 126 |
+
{
|
| 127 |
+
"source": "F",
|
| 128 |
+
"target": "K"
|
| 129 |
+
},
|
| 130 |
+
{
|
| 131 |
+
"source": "F",
|
| 132 |
+
"target": "O"
|
| 133 |
+
},
|
| 134 |
+
{
|
| 135 |
+
"source": "F",
|
| 136 |
+
"target": "Q"
|
| 137 |
+
},
|
| 138 |
+
{
|
| 139 |
+
"source": "F",
|
| 140 |
+
"target": "R"
|
| 141 |
+
},
|
| 142 |
+
{
|
| 143 |
+
"source": "F",
|
| 144 |
+
"target": "S"
|
| 145 |
+
},
|
| 146 |
+
{
|
| 147 |
+
"source": "G",
|
| 148 |
+
"target": "H"
|
| 149 |
+
},
|
| 150 |
+
{
|
| 151 |
+
"source": "G",
|
| 152 |
+
"target": "I"
|
| 153 |
+
},
|
| 154 |
+
{
|
| 155 |
+
"source": "G",
|
| 156 |
+
"target": "J"
|
| 157 |
+
},
|
| 158 |
+
{
|
| 159 |
+
"source": "K",
|
| 160 |
+
"target": "L"
|
| 161 |
+
},
|
| 162 |
+
{
|
| 163 |
+
"source": "K",
|
| 164 |
+
"target": "M"
|
| 165 |
+
},
|
| 166 |
+
{
|
| 167 |
+
"source": "K",
|
| 168 |
+
"target": "N"
|
| 169 |
+
},
|
| 170 |
+
{
|
| 171 |
+
"source": "M",
|
| 172 |
+
"target": "Q",
|
| 173 |
+
"label": "S-EL2"
|
| 174 |
+
},
|
| 175 |
+
{
|
| 176 |
+
"source": "N",
|
| 177 |
+
"target": "S",
|
| 178 |
+
"label": "S-EL2"
|
| 179 |
+
},
|
| 180 |
+
{
|
| 181 |
+
"source": "O",
|
| 182 |
+
"target": "P"
|
| 183 |
+
},
|
| 184 |
+
{
|
| 185 |
+
"source": "P",
|
| 186 |
+
"target": "Q"
|
| 187 |
+
},
|
| 188 |
+
{
|
| 189 |
+
"source": "P",
|
| 190 |
+
"target": "R"
|
| 191 |
+
},
|
| 192 |
+
{
|
| 193 |
+
"source": "Q",
|
| 194 |
+
"target": "R"
|
| 195 |
+
},
|
| 196 |
+
{
|
| 197 |
+
"source": "R",
|
| 198 |
+
"target": "S"
|
| 199 |
+
}
|
| 200 |
+
]
|
| 201 |
+
},
|
| 202 |
+
{
|
| 203 |
+
"type": "text",
|
| 204 |
+
"text": "在软件栈方面,CoDA 方案高度复用了 Linux 社区成熟的 VFIO、SMMU 与 PCIe 设备驱动能力。只要设备支持 VFIO 半虚拟化机制,即可无差别地接入 cVM。这意味着 GPU、NPU、NVMe SSD、智能网卡 (SmartNIC) 等 PCIe 设备,均可被透明、安全地直通到机密虚拟机中,无需更改驱动或框架层代码。在推理框架、数据服务、边缘推送等应用中,原有业务可无缝迁移至机密环境,带来极大便利性与性能优势。从性能角度看,CoDA 已在多类设备上完成测试与验证。以 NVMe 存储设备为例,测试结果显示 cVM 在直通模式下的顺序与随机访问性能与普通虚拟机持平,而相较于 virtio 等半虚拟化方案,性能提升超过 2 倍。"
|
| 205 |
+
},
|
| 206 |
+
{
|
| 207 |
+
"type": "text",
|
| 208 |
+
"text": "早期 PCIPC 设计以 Root Port 为隔离单位,无法区分同一设备下虚拟功能 (VF) 与物理功能 (PF) 的访问边界,考虑到实际应用中要求 SRIOV 设备也支持机密虚拟机直通,来实现多租户且高性能的云计算要求,升级后的 CoDA 方案采用“驱动结合转发”机制,使能了 SRIOV 特性。当 SRIOV 设备被切入安全世界的时候,非安全世界主机侧设备驱动依然能够通过 PF 配置 VF,PF 的 DMA 使用的是"
|
| 209 |
+
},
|
| 210 |
+
{
|
| 211 |
+
"type": "footer",
|
| 212 |
+
"text": "文档版本 V1.0 版权所有 © 华为技术有限公司"
|
| 213 |
+
},
|
| 214 |
+
{
|
| 215 |
+
"type": "page_number",
|
| 216 |
+
"text": "15"
|
| 217 |
+
}
|
| 218 |
+
]
|
diagrams-and-tables/annotations/cn_diagram_21.json
ADDED
|
@@ -0,0 +1,178 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
[
|
| 2 |
+
{
|
| 3 |
+
"type": "text",
|
| 4 |
+
"text": "但是随着存算分离与智能存储的深入应用,数据已不再局限于传统存储设备内部,而是频繁在计算节点、存储节点与网络之间流动,这显著扩大了潜在攻击面,传统以计算为核心的安全模型难以完全适用,如图 9 所示,潜在攻击面主要体现在以下几个方面:"
|
| 5 |
+
},
|
| 6 |
+
{
|
| 7 |
+
"type": "text",
|
| 8 |
+
"text": "• 数据传输安全:在存算分离架构下,数据需要跨节点、跨网络进行频繁传输,传输链路因此成为潜在攻击通道,容易遭受窃听、篡改或中间人攻击,给数据完整性与保密性带来威胁;"
|
| 9 |
+
},
|
| 10 |
+
{
|
| 11 |
+
"type": "text",
|
| 12 |
+
"text": "• 存储计算引擎可信性:随着计算功能下沉至存储节点,存储计算引擎可能成为攻击目标,若缺乏有效的可信执行与验证机制,计算过程透明性与结果可靠性将无法保障,存在被篡改或伪造的风险;"
|
| 13 |
+
},
|
| 14 |
+
{
|
| 15 |
+
"type": "text",
|
| 16 |
+
"text": "• 多租户隔离风险:在云化与共享资源环境中,不同租户的存算资源可能存在隔离不足,尤其在身份认证与授权机制薄弱时,可能导致租户间数据泄漏、越权访问甚至横向攻击,直接冲击系统的安全边界。"
|
| 17 |
+
},
|
| 18 |
+
{
|
| 19 |
+
"type": "diagram_caption",
|
| 20 |
+
"text": "图 10 「存储—计算」机密域框架"
|
| 21 |
+
},
|
| 22 |
+
{
|
| 23 |
+
"type": "diagram",
|
| 24 |
+
"nodes": [
|
| 25 |
+
{
|
| 26 |
+
"id": "A",
|
| 27 |
+
"text": "Confidential Computing"
|
| 28 |
+
},
|
| 29 |
+
{
|
| 30 |
+
"id": "B",
|
| 31 |
+
"text": "GPU"
|
| 32 |
+
},
|
| 33 |
+
{
|
| 34 |
+
"id": "C",
|
| 35 |
+
"text": "NPU"
|
| 36 |
+
},
|
| 37 |
+
{
|
| 38 |
+
"id": "D",
|
| 39 |
+
"text": "Accelerator Card"
|
| 40 |
+
},
|
| 41 |
+
{
|
| 42 |
+
"id": "E",
|
| 43 |
+
"text": "PCIPC"
|
| 44 |
+
},
|
| 45 |
+
{
|
| 46 |
+
"id": "F",
|
| 47 |
+
"text": "Confidential Storage"
|
| 48 |
+
},
|
| 49 |
+
{
|
| 50 |
+
"id": "G",
|
| 51 |
+
"text": "1. Hardware Identity"
|
| 52 |
+
},
|
| 53 |
+
{
|
| 54 |
+
"id": "H",
|
| 55 |
+
"text": "Measurement"
|
| 56 |
+
},
|
| 57 |
+
{
|
| 58 |
+
"id": "I",
|
| 59 |
+
"text": "Attestation"
|
| 60 |
+
},
|
| 61 |
+
{
|
| 62 |
+
"id": "J",
|
| 63 |
+
"text": "Hardware Root of Trust"
|
| 64 |
+
},
|
| 65 |
+
{
|
| 66 |
+
"id": "K",
|
| 67 |
+
"text": "3. Multi-layer Authentication"
|
| 68 |
+
},
|
| 69 |
+
{
|
| 70 |
+
"id": "L",
|
| 71 |
+
"text": "Entity Authentication"
|
| 72 |
+
},
|
| 73 |
+
{
|
| 74 |
+
"id": "M",
|
| 75 |
+
"text": "Access Policy Control"
|
| 76 |
+
},
|
| 77 |
+
{
|
| 78 |
+
"id": "N",
|
| 79 |
+
"text": "Confidential LUN"
|
| 80 |
+
},
|
| 81 |
+
{
|
| 82 |
+
"id": "O",
|
| 83 |
+
"text": "Confidential FS"
|
| 84 |
+
}
|
| 85 |
+
],
|
| 86 |
+
"relationships": [
|
| 87 |
+
{
|
| 88 |
+
"source": "A",
|
| 89 |
+
"target": "B"
|
| 90 |
+
},
|
| 91 |
+
{
|
| 92 |
+
"source": "A",
|
| 93 |
+
"target": "C"
|
| 94 |
+
},
|
| 95 |
+
{
|
| 96 |
+
"source": "A",
|
| 97 |
+
"target": "D"
|
| 98 |
+
},
|
| 99 |
+
{
|
| 100 |
+
"source": "A",
|
| 101 |
+
"target": "E"
|
| 102 |
+
},
|
| 103 |
+
{
|
| 104 |
+
"source": "B",
|
| 105 |
+
"target": "E"
|
| 106 |
+
},
|
| 107 |
+
{
|
| 108 |
+
"source": "C",
|
| 109 |
+
"target": "E"
|
| 110 |
+
},
|
| 111 |
+
{
|
| 112 |
+
"source": "D",
|
| 113 |
+
"target": "E"
|
| 114 |
+
},
|
| 115 |
+
{
|
| 116 |
+
"source": "E",
|
| 117 |
+
"target": "F",
|
| 118 |
+
"label": "2. I/O Encryption\n4. Confidential Device Assignment"
|
| 119 |
+
},
|
| 120 |
+
{
|
| 121 |
+
"source": "F",
|
| 122 |
+
"target": "G"
|
| 123 |
+
},
|
| 124 |
+
{
|
| 125 |
+
"source": "F",
|
| 126 |
+
"target": "N"
|
| 127 |
+
},
|
| 128 |
+
{
|
| 129 |
+
"source": "F",
|
| 130 |
+
"target": "O"
|
| 131 |
+
},
|
| 132 |
+
{
|
| 133 |
+
"source": "G",
|
| 134 |
+
"target": "H"
|
| 135 |
+
},
|
| 136 |
+
{
|
| 137 |
+
"source": "G",
|
| 138 |
+
"target": "I"
|
| 139 |
+
},
|
| 140 |
+
{
|
| 141 |
+
"source": "G",
|
| 142 |
+
"target": "J"
|
| 143 |
+
},
|
| 144 |
+
{
|
| 145 |
+
"source": "H",
|
| 146 |
+
"target": "J"
|
| 147 |
+
},
|
| 148 |
+
{
|
| 149 |
+
"source": "I",
|
| 150 |
+
"target": "J"
|
| 151 |
+
},
|
| 152 |
+
{
|
| 153 |
+
"source": "F",
|
| 154 |
+
"target": "K"
|
| 155 |
+
},
|
| 156 |
+
{
|
| 157 |
+
"source": "K",
|
| 158 |
+
"target": "L"
|
| 159 |
+
},
|
| 160 |
+
{
|
| 161 |
+
"source": "K",
|
| 162 |
+
"target": "M"
|
| 163 |
+
},
|
| 164 |
+
{
|
| 165 |
+
"source": "L",
|
| 166 |
+
"target": "M"
|
| 167 |
+
}
|
| 168 |
+
]
|
| 169 |
+
},
|
| 170 |
+
{
|
| 171 |
+
"type": "footer",
|
| 172 |
+
"text": "文档版本 V1.0 版权所有 © 华为技术有限公司"
|
| 173 |
+
},
|
| 174 |
+
{
|
| 175 |
+
"type": "page_number",
|
| 176 |
+
"text": "18"
|
| 177 |
+
}
|
| 178 |
+
]
|
diagrams-and-tables/annotations/cn_diagram_22.json
ADDED
|
@@ -0,0 +1,262 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
[
|
| 2 |
+
{
|
| 3 |
+
"type": "text",
|
| 4 |
+
"text": "为了实现上述目标,擎天机密计算设计在两个维度上提供安全隔离(如图 13 所示):"
|
| 5 |
+
},
|
| 6 |
+
{
|
| 7 |
+
"type": "diagram_caption",
|
| 8 |
+
"text": "图 13 擎天隔离方案"
|
| 9 |
+
},
|
| 10 |
+
{
|
| 11 |
+
"type": "diagram",
|
| 12 |
+
"nodes": [
|
| 13 |
+
{
|
| 14 |
+
"id": "A",
|
| 15 |
+
"text": "CSP-controlled System"
|
| 16 |
+
},
|
| 17 |
+
{
|
| 18 |
+
"id": "B",
|
| 19 |
+
"text": "Control Plane"
|
| 20 |
+
},
|
| 21 |
+
{
|
| 22 |
+
"id": "C",
|
| 23 |
+
"text": "ECS/VPC/EVS"
|
| 24 |
+
},
|
| 25 |
+
{
|
| 26 |
+
"id": "D",
|
| 27 |
+
"text": "QingTian Cards"
|
| 28 |
+
},
|
| 29 |
+
{
|
| 30 |
+
"id": "E",
|
| 31 |
+
"text": "QingTian Controller 云系统"
|
| 32 |
+
},
|
| 33 |
+
{
|
| 34 |
+
"id": "F",
|
| 35 |
+
"text": "Customer-controlled Instance"
|
| 36 |
+
},
|
| 37 |
+
{
|
| 38 |
+
"id": "G",
|
| 39 |
+
"text": "VM"
|
| 40 |
+
},
|
| 41 |
+
{
|
| 42 |
+
"id": "H",
|
| 43 |
+
"text": "Guest App"
|
| 44 |
+
},
|
| 45 |
+
{
|
| 46 |
+
"id": "I",
|
| 47 |
+
"text": "Guest OS"
|
| 48 |
+
},
|
| 49 |
+
{
|
| 50 |
+
"id": "J",
|
| 51 |
+
"text": "Enclave"
|
| 52 |
+
},
|
| 53 |
+
{
|
| 54 |
+
"id": "K",
|
| 55 |
+
"text": "Enclave App"
|
| 56 |
+
},
|
| 57 |
+
{
|
| 58 |
+
"id": "L",
|
| 59 |
+
"text": "TEE OS"
|
| 60 |
+
}
|
| 61 |
+
],
|
| 62 |
+
"relationships": [
|
| 63 |
+
{
|
| 64 |
+
"source": "A",
|
| 65 |
+
"target": "B"
|
| 66 |
+
},
|
| 67 |
+
{
|
| 68 |
+
"source": "A",
|
| 69 |
+
"target": "D"
|
| 70 |
+
},
|
| 71 |
+
{
|
| 72 |
+
"source": "A",
|
| 73 |
+
"target": "F",
|
| 74 |
+
"label": "隔离 1"
|
| 75 |
+
},
|
| 76 |
+
{
|
| 77 |
+
"source": "B",
|
| 78 |
+
"target": "C"
|
| 79 |
+
},
|
| 80 |
+
{
|
| 81 |
+
"source": "B",
|
| 82 |
+
"target": "D"
|
| 83 |
+
},
|
| 84 |
+
{
|
| 85 |
+
"source": "D",
|
| 86 |
+
"target": "E"
|
| 87 |
+
},
|
| 88 |
+
{
|
| 89 |
+
"source": "F",
|
| 90 |
+
"target": "G"
|
| 91 |
+
},
|
| 92 |
+
{
|
| 93 |
+
"source": "F",
|
| 94 |
+
"target": "J"
|
| 95 |
+
},
|
| 96 |
+
{
|
| 97 |
+
"source": "G",
|
| 98 |
+
"target": "H"
|
| 99 |
+
},
|
| 100 |
+
{
|
| 101 |
+
"source": "G",
|
| 102 |
+
"target": "I"
|
| 103 |
+
},
|
| 104 |
+
{
|
| 105 |
+
"source": "G",
|
| 106 |
+
"target": "J",
|
| 107 |
+
"label": "隔离 2"
|
| 108 |
+
},
|
| 109 |
+
{
|
| 110 |
+
"source": "J",
|
| 111 |
+
"target": "K"
|
| 112 |
+
},
|
| 113 |
+
{
|
| 114 |
+
"source": "J",
|
| 115 |
+
"target": "L"
|
| 116 |
+
}
|
| 117 |
+
]
|
| 118 |
+
},
|
| 119 |
+
{
|
| 120 |
+
"type": "text",
|
| 121 |
+
"text": "• 隔离维度 1:将『客户代码和数据』与『云厂商内部人员和云系统软件』隔离,抵御 CSP 内部人员攻击;"
|
| 122 |
+
},
|
| 123 |
+
{
|
| 124 |
+
"type": "text",
|
| 125 |
+
"text": "• 隔离维度 2:将『客户代码和数据』与『客户内部人员和低可信 Guest OS』隔离,抵御客户内部人员攻击。"
|
| 126 |
+
},
|
| 127 |
+
{
|
| 128 |
+
"type": "title",
|
| 129 |
+
"text": "隔离维度 1:假设 CSP 不可信"
|
| 130 |
+
},
|
| 131 |
+
{
|
| 132 |
+
"type": "text",
|
| 133 |
+
"text": "此隔离维度是基于 CSP 不可信的假设,其安全设计目标是将 ECS 实例中的『客户代码和数据』与『云厂商内部人员和云系统软件』进行隔离。"
|
| 134 |
+
},
|
| 135 |
+
{
|
| 136 |
+
"type": "diagram_caption",
|
| 137 |
+
"text": "图 14 擎天计算节点抵御 CSP 内部人员攻击"
|
| 138 |
+
},
|
| 139 |
+
{
|
| 140 |
+
"type": "diagram",
|
| 141 |
+
"nodes": [
|
| 142 |
+
{
|
| 143 |
+
"id": "A",
|
| 144 |
+
"text": "服务器(前端)"
|
| 145 |
+
},
|
| 146 |
+
{
|
| 147 |
+
"id": "B",
|
| 148 |
+
"text": "ECS VM1"
|
| 149 |
+
},
|
| 150 |
+
{
|
| 151 |
+
"id": "C",
|
| 152 |
+
"text": "Untrusted Guest OS (Rich OS)"
|
| 153 |
+
},
|
| 154 |
+
{
|
| 155 |
+
"id": "D",
|
| 156 |
+
"text": "Trusted Enclave"
|
| 157 |
+
},
|
| 158 |
+
{
|
| 159 |
+
"id": "E",
|
| 160 |
+
"text": "ECS VM2"
|
| 161 |
+
},
|
| 162 |
+
{
|
| 163 |
+
"id": "F",
|
| 164 |
+
"text": "Trusted Guest OS"
|
| 165 |
+
},
|
| 166 |
+
{
|
| 167 |
+
"id": "G",
|
| 168 |
+
"text": "QingTian Hypervisor"
|
| 169 |
+
},
|
| 170 |
+
{
|
| 171 |
+
"id": "H",
|
| 172 |
+
"text": "擎天卡(后端)"
|
| 173 |
+
},
|
| 174 |
+
{
|
| 175 |
+
"id": "I",
|
| 176 |
+
"text": "受限的管控 VM"
|
| 177 |
+
},
|
| 178 |
+
{
|
| 179 |
+
"id": "J",
|
| 180 |
+
"text": "网络"
|
| 181 |
+
},
|
| 182 |
+
{
|
| 183 |
+
"id": "K",
|
| 184 |
+
"text": "存储"
|
| 185 |
+
},
|
| 186 |
+
{
|
| 187 |
+
"id": "L",
|
| 188 |
+
"text": "安全"
|
| 189 |
+
},
|
| 190 |
+
{
|
| 191 |
+
"id": "M",
|
| 192 |
+
"text": "SDI NanoOS"
|
| 193 |
+
},
|
| 194 |
+
{
|
| 195 |
+
"id": "N",
|
| 196 |
+
"text": "硬件"
|
| 197 |
+
}
|
| 198 |
+
],
|
| 199 |
+
"relationships": [
|
| 200 |
+
{
|
| 201 |
+
"source": "A",
|
| 202 |
+
"target": "B"
|
| 203 |
+
},
|
| 204 |
+
{
|
| 205 |
+
"source": "A",
|
| 206 |
+
"target": "E"
|
| 207 |
+
},
|
| 208 |
+
{
|
| 209 |
+
"source": "A",
|
| 210 |
+
"target": "G"
|
| 211 |
+
},
|
| 212 |
+
{
|
| 213 |
+
"source": "B",
|
| 214 |
+
"target": "C"
|
| 215 |
+
},
|
| 216 |
+
{
|
| 217 |
+
"source": "B",
|
| 218 |
+
"target": "D"
|
| 219 |
+
},
|
| 220 |
+
{
|
| 221 |
+
"source": "E",
|
| 222 |
+
"target": "F"
|
| 223 |
+
},
|
| 224 |
+
{
|
| 225 |
+
"source": "A",
|
| 226 |
+
"target": "H"
|
| 227 |
+
},
|
| 228 |
+
{
|
| 229 |
+
"source": "H",
|
| 230 |
+
"target": "I"
|
| 231 |
+
},
|
| 232 |
+
{
|
| 233 |
+
"source": "H",
|
| 234 |
+
"target": "J"
|
| 235 |
+
},
|
| 236 |
+
{
|
| 237 |
+
"source": "H",
|
| 238 |
+
"target": "K"
|
| 239 |
+
},
|
| 240 |
+
{
|
| 241 |
+
"source": "H",
|
| 242 |
+
"target": "L"
|
| 243 |
+
},
|
| 244 |
+
{
|
| 245 |
+
"source": "H",
|
| 246 |
+
"target": "M"
|
| 247 |
+
},
|
| 248 |
+
{
|
| 249 |
+
"source": "H",
|
| 250 |
+
"target": "N"
|
| 251 |
+
}
|
| 252 |
+
]
|
| 253 |
+
},
|
| 254 |
+
{
|
| 255 |
+
"type": "footer",
|
| 256 |
+
"text": "文档版本 V1.0 版权所有 © 华为技术有限公司"
|
| 257 |
+
},
|
| 258 |
+
{
|
| 259 |
+
"type": "page_number",
|
| 260 |
+
"text": "26"
|
| 261 |
+
}
|
| 262 |
+
]
|
diagrams-and-tables/annotations/cn_diagram_23.json
ADDED
|
@@ -0,0 +1,146 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
[
|
| 2 |
+
{
|
| 3 |
+
"type": "title",
|
| 4 |
+
"text": "度量启动与远程证明"
|
| 5 |
+
},
|
| 6 |
+
{
|
| 7 |
+
"type": "text",
|
| 8 |
+
"text": "擎天 Enclave 提供完整的度量启动与远程证明能力,通过标准可信度量运算得到哈希值并保存在 QTSM 的 PCR 中,使得应用程序可获取当前环境的可信证明文档(Attestation Document),从而与外部实体运行密钥协商和端到端加密等安全协议。其远程证明 PKI 基于多级 CA 层级设计,遵循最大化瞬态安全原则,支持小时级证书轮转,且华为云每个部署均拥有独立的擎天 Attestation CA 以确保隔离性与安全性。华为云 KMS 和 IAM 服务已内置对该证明协议的支持,租户可通过设置 IAM 条件策略实现细粒度控制(如仅允许特定 Enclave 调用特定 KMS API)。典型应用流程中(如图 15 所示),Enclave 生成 RSA 密钥对并获取含公钥的证明文档,随后向 KMS 提交文档与密文请求解密;KMS 验证文档有效性并通过 IAM 策略检查后,使用该公钥对解密结果加密返回,最终由 Enclave 应用本地解封装获得明文。"
|
| 9 |
+
},
|
| 10 |
+
{
|
| 11 |
+
"type": "diagram_caption",
|
| 12 |
+
"text": "图 15 Enclave 应用与 KMS 服务配合进行安全解密的参考流程"
|
| 13 |
+
},
|
| 14 |
+
{
|
| 15 |
+
"type": "diagram",
|
| 16 |
+
"nodes": [
|
| 17 |
+
{
|
| 18 |
+
"id": "A",
|
| 19 |
+
"text": "QingTian Attestation PKI"
|
| 20 |
+
},
|
| 21 |
+
{
|
| 22 |
+
"id": "B",
|
| 23 |
+
"text": "QingTian Root Certificate"
|
| 24 |
+
},
|
| 25 |
+
{
|
| 26 |
+
"id": "C",
|
| 27 |
+
"text": "ECS Instance"
|
| 28 |
+
},
|
| 29 |
+
{
|
| 30 |
+
"id": "D",
|
| 31 |
+
"text": "Enclave"
|
| 32 |
+
},
|
| 33 |
+
{
|
| 34 |
+
"id": "E",
|
| 35 |
+
"text": "Enclave Application"
|
| 36 |
+
},
|
| 37 |
+
{
|
| 38 |
+
"id": "F",
|
| 39 |
+
"text": "Parent VM"
|
| 40 |
+
},
|
| 41 |
+
{
|
| 42 |
+
"id": "G",
|
| 43 |
+
"text": "Network Proxy"
|
| 44 |
+
},
|
| 45 |
+
{
|
| 46 |
+
"id": "H",
|
| 47 |
+
"text": "Relying Party (e.g., KMS)"
|
| 48 |
+
},
|
| 49 |
+
{
|
| 50 |
+
"id": "I",
|
| 51 |
+
"text": "Access Policy (reference measurements as access control conditions)"
|
| 52 |
+
},
|
| 53 |
+
{
|
| 54 |
+
"id": "J",
|
| 55 |
+
"text": "QTSM (Attestation Key)"
|
| 56 |
+
},
|
| 57 |
+
{
|
| 58 |
+
"id": "K",
|
| 59 |
+
"text": "Verifier"
|
| 60 |
+
},
|
| 61 |
+
{
|
| 62 |
+
"id": "L",
|
| 63 |
+
"text": "IAM PDP"
|
| 64 |
+
}
|
| 65 |
+
],
|
| 66 |
+
"relationships": [
|
| 67 |
+
{
|
| 68 |
+
"source": "A",
|
| 69 |
+
"target": "B"
|
| 70 |
+
},
|
| 71 |
+
{
|
| 72 |
+
"source": "A",
|
| 73 |
+
"target": "J",
|
| 74 |
+
"label": "Attestation Key Certification"
|
| 75 |
+
},
|
| 76 |
+
{
|
| 77 |
+
"source": "A",
|
| 78 |
+
"target": "K"
|
| 79 |
+
},
|
| 80 |
+
{
|
| 81 |
+
"source": "C",
|
| 82 |
+
"target": "D"
|
| 83 |
+
},
|
| 84 |
+
{
|
| 85 |
+
"source": "C",
|
| 86 |
+
"target": "F"
|
| 87 |
+
},
|
| 88 |
+
{
|
| 89 |
+
"source": "D",
|
| 90 |
+
"target": "E"
|
| 91 |
+
},
|
| 92 |
+
{
|
| 93 |
+
"source": "E",
|
| 94 |
+
"target": "G"
|
| 95 |
+
},
|
| 96 |
+
{
|
| 97 |
+
"source": "E",
|
| 98 |
+
"target": "J",
|
| 99 |
+
"label": "1\n2"
|
| 100 |
+
},
|
| 101 |
+
{
|
| 102 |
+
"source": "F",
|
| 103 |
+
"target": "G"
|
| 104 |
+
},
|
| 105 |
+
{
|
| 106 |
+
"source": "G",
|
| 107 |
+
"target": "H",
|
| 108 |
+
"label": "3\n6"
|
| 109 |
+
},
|
| 110 |
+
{
|
| 111 |
+
"source": "H",
|
| 112 |
+
"target": "K",
|
| 113 |
+
"label": "4"
|
| 114 |
+
},
|
| 115 |
+
{
|
| 116 |
+
"source": "H",
|
| 117 |
+
"target": "L",
|
| 118 |
+
"label": "5"
|
| 119 |
+
},
|
| 120 |
+
{
|
| 121 |
+
"source": "I",
|
| 122 |
+
"target": "L"
|
| 123 |
+
}
|
| 124 |
+
]
|
| 125 |
+
},
|
| 126 |
+
{
|
| 127 |
+
"type": "text",
|
| 128 |
+
"text": "每个 ECS 实例均拥有一个由服务生成的实例身份文档,提供实例的元数据信息,并在实例启动、停止或重启时更新。应用程序可通过实例元数据服务(IMDS)获取该文档及其数字签名,用于向远程依赖方验证实例属性,具备抗重放攻击能力。此“默认出生证”为实例提供初始身份证明,基于可传递信任原则安全获取应用访问凭证,从而避免在代码或配置中硬编码静态凭证。用户也可在创建 ECS 实例时配置 IAM 委托,该虚拟身份由 IAM 管理员创建,代表实例身份且无需静态凭证,有效降低长期凭证泄露风险。应用程序通过 IMDS 获取由 STS 签发的临时安全令牌,据此代表委托身份访问被授权的云服务资源。实例 IAM 委托作为实例的“机器身份”,使应用程序无需硬编码 AK/SK 等静态凭据即可安全调用云服务 API。"
|
| 129 |
+
},
|
| 130 |
+
{
|
| 131 |
+
"type": "title",
|
| 132 |
+
"text": "5.4 华为云擎天异构架构展望"
|
| 133 |
+
},
|
| 134 |
+
{
|
| 135 |
+
"type": "text",
|
| 136 |
+
"text": "在 AI 机密计算需求的推动下,算力需求的增长正驱动组合式 TEE 的快速演进。单个运行在 CPU 上的擎天 Enclave,正在扩展为可与多个加速器 TEE 互联的安全算力群组,从而形成更强大的安全算力。"
|
| 137 |
+
},
|
| 138 |
+
{
|
| 139 |
+
"type": "footer",
|
| 140 |
+
"text": "文档版本 V1.0 版权所有 © 华为技术有限公司"
|
| 141 |
+
},
|
| 142 |
+
{
|
| 143 |
+
"type": "page_number",
|
| 144 |
+
"text": "29"
|
| 145 |
+
}
|
| 146 |
+
]
|
diagrams-and-tables/annotations/cn_diagram_24.json
ADDED
|
@@ -0,0 +1,252 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
[
|
| 2 |
+
{
|
| 3 |
+
"type": "header",
|
| 4 |
+
"text": "6. AI 平台安全关键技术"
|
| 5 |
+
},
|
| 6 |
+
{
|
| 7 |
+
"type": "title",
|
| 8 |
+
"text": "6.1 A+K 异构机密计算加速平台"
|
| 9 |
+
},
|
| 10 |
+
{
|
| 11 |
+
"type": "text",
|
| 12 |
+
"text": "在面向 AI 的算力安全体系中,单一计算节点的可信保障已无法满足日益复杂的人工智能场景需求。尤其是在大模型推理、高性能训练、多端协同等任务中,CPU 与 NPU 等异构计算单元协同执行的需求持续上升,同时也带来了计算边界扩展、数据跨域流转所引发的安全挑战。为此,在 CPU 通用机密计算平台与 NPU 机密计算平台的基础上,HCIST 还提供异构协同的新型安全架构:A+K 机密计算加速平台(如图 16 所示)。该平台通过可信互联协议,建立跨设备信任传递与统一内存安全映射方案,实现了“双硬件信任根、端到端运行时隔离、任务级零信任验证”三位一体安全架构,从而在保障数据机密性的同时,充分释放计算资源的协同效能。"
|
| 13 |
+
},
|
| 14 |
+
{
|
| 15 |
+
"type": "diagram_caption",
|
| 16 |
+
"text": "图 16 华为 A+K 异构机密计算框架"
|
| 17 |
+
},
|
| 18 |
+
{
|
| 19 |
+
"type": "diagram",
|
| 20 |
+
"nodes": [
|
| 21 |
+
{
|
| 22 |
+
"id": "A",
|
| 23 |
+
"text": "鲲鹏 CPU"
|
| 24 |
+
},
|
| 25 |
+
{
|
| 26 |
+
"id": "B",
|
| 27 |
+
"text": "CPU REE环境"
|
| 28 |
+
},
|
| 29 |
+
{
|
| 30 |
+
"id": "C",
|
| 31 |
+
"text": "系统管理服务"
|
| 32 |
+
},
|
| 33 |
+
{
|
| 34 |
+
"id": "D",
|
| 35 |
+
"text": "Host OS"
|
| 36 |
+
},
|
| 37 |
+
{
|
| 38 |
+
"id": "E",
|
| 39 |
+
"text": "REE 共享内存"
|
| 40 |
+
},
|
| 41 |
+
{
|
| 42 |
+
"id": "F",
|
| 43 |
+
"text": "CPU TEE环境"
|
| 44 |
+
},
|
| 45 |
+
{
|
| 46 |
+
"id": "G",
|
| 47 |
+
"text": "AI训练/推理框架"
|
| 48 |
+
},
|
| 49 |
+
{
|
| 50 |
+
"id": "H",
|
| 51 |
+
"text": "CANN"
|
| 52 |
+
},
|
| 53 |
+
{
|
| 54 |
+
"id": "I",
|
| 55 |
+
"text": "可信启动与远程证明"
|
| 56 |
+
},
|
| 57 |
+
{
|
| 58 |
+
"id": "J",
|
| 59 |
+
"text": "Guest OS"
|
| 60 |
+
},
|
| 61 |
+
{
|
| 62 |
+
"id": "K",
|
| 63 |
+
"text": "TEE 私有内存"
|
| 64 |
+
},
|
| 65 |
+
{
|
| 66 |
+
"id": "L",
|
| 67 |
+
"text": "可信互联协议"
|
| 68 |
+
},
|
| 69 |
+
{
|
| 70 |
+
"id": "M",
|
| 71 |
+
"text": "昇腾 NPU"
|
| 72 |
+
},
|
| 73 |
+
{
|
| 74 |
+
"id": "N",
|
| 75 |
+
"text": "NPU 0"
|
| 76 |
+
},
|
| 77 |
+
{
|
| 78 |
+
"id": "O",
|
| 79 |
+
"text": "TEE扩展组件"
|
| 80 |
+
},
|
| 81 |
+
{
|
| 82 |
+
"id": "P",
|
| 83 |
+
"text": "NPU私有内存"
|
| 84 |
+
},
|
| 85 |
+
{
|
| 86 |
+
"id": "Q",
|
| 87 |
+
"text": "达芬奇计算单元"
|
| 88 |
+
},
|
| 89 |
+
{
|
| 90 |
+
"id": "R",
|
| 91 |
+
"text": "可信启动"
|
| 92 |
+
},
|
| 93 |
+
{
|
| 94 |
+
"id": "S",
|
| 95 |
+
"text": "远程证明"
|
| 96 |
+
},
|
| 97 |
+
{
|
| 98 |
+
"id": "T",
|
| 99 |
+
"text": "NPU N"
|
| 100 |
+
},
|
| 101 |
+
{
|
| 102 |
+
"id": "U",
|
| 103 |
+
"text": "TEE扩展组件"
|
| 104 |
+
},
|
| 105 |
+
{
|
| 106 |
+
"id": "V",
|
| 107 |
+
"text": "NPU私有内存"
|
| 108 |
+
},
|
| 109 |
+
{
|
| 110 |
+
"id": "W",
|
| 111 |
+
"text": "达芬奇计算单元"
|
| 112 |
+
},
|
| 113 |
+
{
|
| 114 |
+
"id": "X",
|
| 115 |
+
"text": "可信启动"
|
| 116 |
+
},
|
| 117 |
+
{
|
| 118 |
+
"id": "Y",
|
| 119 |
+
"text": "远程证明"
|
| 120 |
+
},
|
| 121 |
+
{
|
| 122 |
+
"id": "Z",
|
| 123 |
+
"text": "非信任实体"
|
| 124 |
+
},
|
| 125 |
+
{
|
| 126 |
+
"id": "AA",
|
| 127 |
+
"text": "可信实体"
|
| 128 |
+
}
|
| 129 |
+
],
|
| 130 |
+
"relationships": [
|
| 131 |
+
{
|
| 132 |
+
"source": "A",
|
| 133 |
+
"target": "B"
|
| 134 |
+
},
|
| 135 |
+
{
|
| 136 |
+
"source": "A",
|
| 137 |
+
"target": "F"
|
| 138 |
+
},
|
| 139 |
+
{
|
| 140 |
+
"source": "B",
|
| 141 |
+
"target": "C"
|
| 142 |
+
},
|
| 143 |
+
{
|
| 144 |
+
"source": "B",
|
| 145 |
+
"target": "D"
|
| 146 |
+
},
|
| 147 |
+
{
|
| 148 |
+
"source": "B",
|
| 149 |
+
"target": "E"
|
| 150 |
+
},
|
| 151 |
+
{
|
| 152 |
+
"source": "B",
|
| 153 |
+
"target": "F",
|
| 154 |
+
"label": "×"
|
| 155 |
+
},
|
| 156 |
+
{
|
| 157 |
+
"source": "B",
|
| 158 |
+
"target": "L",
|
| 159 |
+
"label": "×"
|
| 160 |
+
},
|
| 161 |
+
{
|
| 162 |
+
"source": "F",
|
| 163 |
+
"target": "G"
|
| 164 |
+
},
|
| 165 |
+
{
|
| 166 |
+
"source": "F",
|
| 167 |
+
"target": "H"
|
| 168 |
+
},
|
| 169 |
+
{
|
| 170 |
+
"source": "F",
|
| 171 |
+
"target": "I"
|
| 172 |
+
},
|
| 173 |
+
{
|
| 174 |
+
"source": "F",
|
| 175 |
+
"target": "J"
|
| 176 |
+
},
|
| 177 |
+
{
|
| 178 |
+
"source": "F",
|
| 179 |
+
"target": "K"
|
| 180 |
+
},
|
| 181 |
+
{
|
| 182 |
+
"source": "F",
|
| 183 |
+
"target": "L",
|
| 184 |
+
"label": "只有CPU TEE有访问NPU TEE内存的权限"
|
| 185 |
+
},
|
| 186 |
+
{
|
| 187 |
+
"source": "L",
|
| 188 |
+
"target": "N"
|
| 189 |
+
},
|
| 190 |
+
{
|
| 191 |
+
"source": "L",
|
| 192 |
+
"target": "T"
|
| 193 |
+
},
|
| 194 |
+
{
|
| 195 |
+
"source": "M",
|
| 196 |
+
"target": "N"
|
| 197 |
+
},
|
| 198 |
+
{
|
| 199 |
+
"source": "N",
|
| 200 |
+
"target": "O"
|
| 201 |
+
},
|
| 202 |
+
{
|
| 203 |
+
"source": "N",
|
| 204 |
+
"target": "P"
|
| 205 |
+
},
|
| 206 |
+
{
|
| 207 |
+
"source": "N",
|
| 208 |
+
"target": "Q"
|
| 209 |
+
},
|
| 210 |
+
{
|
| 211 |
+
"source": "N",
|
| 212 |
+
"target": "R"
|
| 213 |
+
},
|
| 214 |
+
{
|
| 215 |
+
"source": "N",
|
| 216 |
+
"target": "S"
|
| 217 |
+
},
|
| 218 |
+
{
|
| 219 |
+
"source": "M",
|
| 220 |
+
"target": "T"
|
| 221 |
+
},
|
| 222 |
+
{
|
| 223 |
+
"source": "T",
|
| 224 |
+
"target": "U"
|
| 225 |
+
},
|
| 226 |
+
{
|
| 227 |
+
"source": "T",
|
| 228 |
+
"target": "V"
|
| 229 |
+
},
|
| 230 |
+
{
|
| 231 |
+
"source": "T",
|
| 232 |
+
"target": "W"
|
| 233 |
+
},
|
| 234 |
+
{
|
| 235 |
+
"source": "T",
|
| 236 |
+
"target": "X"
|
| 237 |
+
},
|
| 238 |
+
{
|
| 239 |
+
"source": "T",
|
| 240 |
+
"target": "Y"
|
| 241 |
+
}
|
| 242 |
+
]
|
| 243 |
+
},
|
| 244 |
+
{
|
| 245 |
+
"type": "footer",
|
| 246 |
+
"text": "文档版本 V1.0 版权所有 © 华为技术有限公司"
|
| 247 |
+
},
|
| 248 |
+
{
|
| 249 |
+
"type": "page_number",
|
| 250 |
+
"text": "31"
|
| 251 |
+
}
|
| 252 |
+
]
|
diagrams-and-tables/annotations/cn_diagram_25.json
ADDED
|
@@ -0,0 +1,268 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
[
|
| 2 |
+
{
|
| 3 |
+
"type": "diagram_caption",
|
| 4 |
+
"text": "图18 Kuasar安全容器框架"
|
| 5 |
+
},
|
| 6 |
+
{
|
| 7 |
+
"type": "diagram",
|
| 8 |
+
"nodes": [
|
| 9 |
+
{
|
| 10 |
+
"id": "A",
|
| 11 |
+
"text": "kubernetes"
|
| 12 |
+
},
|
| 13 |
+
{
|
| 14 |
+
"id": "B",
|
| 15 |
+
"text": "containerd"
|
| 16 |
+
},
|
| 17 |
+
{
|
| 18 |
+
"id": "C",
|
| 19 |
+
"text": "CRI-O"
|
| 20 |
+
},
|
| 21 |
+
{
|
| 22 |
+
"id": "D",
|
| 23 |
+
"text": "docker"
|
| 24 |
+
},
|
| 25 |
+
{
|
| 26 |
+
"id": "E",
|
| 27 |
+
"text": "iSulad"
|
| 28 |
+
},
|
| 29 |
+
{
|
| 30 |
+
"id": "F",
|
| 31 |
+
"text": "sandboxer plugin"
|
| 32 |
+
},
|
| 33 |
+
{
|
| 34 |
+
"id": "G",
|
| 35 |
+
"text": "rust-sandboxer (lib)"
|
| 36 |
+
},
|
| 37 |
+
{
|
| 38 |
+
"id": "H",
|
| 39 |
+
"text": "vmm-sandboxer"
|
| 40 |
+
},
|
| 41 |
+
{
|
| 42 |
+
"id": "I",
|
| 43 |
+
"text": "wasm-sandboxer"
|
| 44 |
+
},
|
| 45 |
+
{
|
| 46 |
+
"id": "J",
|
| 47 |
+
"text": "quark-sandboxer"
|
| 48 |
+
},
|
| 49 |
+
{
|
| 50 |
+
"id": "K",
|
| 51 |
+
"text": "runc-sandboxer"
|
| 52 |
+
},
|
| 53 |
+
{
|
| 54 |
+
"id": "L",
|
| 55 |
+
"text": "microVM Sandbox"
|
| 56 |
+
},
|
| 57 |
+
{
|
| 58 |
+
"id": "M",
|
| 59 |
+
"text": "vmm-task"
|
| 60 |
+
},
|
| 61 |
+
{
|
| 62 |
+
"id": "N",
|
| 63 |
+
"text": "container"
|
| 64 |
+
},
|
| 65 |
+
{
|
| 66 |
+
"id": "O",
|
| 67 |
+
"text": "WASM Sandbox"
|
| 68 |
+
},
|
| 69 |
+
{
|
| 70 |
+
"id": "P",
|
| 71 |
+
"text": "wasm-task"
|
| 72 |
+
},
|
| 73 |
+
{
|
| 74 |
+
"id": "Q",
|
| 75 |
+
"text": "container"
|
| 76 |
+
},
|
| 77 |
+
{
|
| 78 |
+
"id": "R",
|
| 79 |
+
"text": "App Kernel Sandbox"
|
| 80 |
+
},
|
| 81 |
+
{
|
| 82 |
+
"id": "S",
|
| 83 |
+
"text": "quark-task"
|
| 84 |
+
},
|
| 85 |
+
{
|
| 86 |
+
"id": "T",
|
| 87 |
+
"text": "container"
|
| 88 |
+
},
|
| 89 |
+
{
|
| 90 |
+
"id": "U",
|
| 91 |
+
"text": "Runc Sandbox"
|
| 92 |
+
},
|
| 93 |
+
{
|
| 94 |
+
"id": "V",
|
| 95 |
+
"text": "runc-task"
|
| 96 |
+
},
|
| 97 |
+
{
|
| 98 |
+
"id": "W",
|
| 99 |
+
"text": "container"
|
| 100 |
+
},
|
| 101 |
+
{
|
| 102 |
+
"id": "X",
|
| 103 |
+
"text": "Kuasar"
|
| 104 |
+
},
|
| 105 |
+
{
|
| 106 |
+
"id": "Y",
|
| 107 |
+
"text": "Sandbox API framework"
|
| 108 |
+
}
|
| 109 |
+
],
|
| 110 |
+
"relationships": [
|
| 111 |
+
{
|
| 112 |
+
"source": "A",
|
| 113 |
+
"target": "F",
|
| 114 |
+
"label": "CRI"
|
| 115 |
+
},
|
| 116 |
+
{
|
| 117 |
+
"source": "B",
|
| 118 |
+
"target": "F"
|
| 119 |
+
},
|
| 120 |
+
{
|
| 121 |
+
"source": "C",
|
| 122 |
+
"target": "F"
|
| 123 |
+
},
|
| 124 |
+
{
|
| 125 |
+
"source": "D",
|
| 126 |
+
"target": "F"
|
| 127 |
+
},
|
| 128 |
+
{
|
| 129 |
+
"source": "E",
|
| 130 |
+
"target": "F"
|
| 131 |
+
},
|
| 132 |
+
{
|
| 133 |
+
"source": "F",
|
| 134 |
+
"target": "G",
|
| 135 |
+
"label": "Sandbox API"
|
| 136 |
+
},
|
| 137 |
+
{
|
| 138 |
+
"source": "F",
|
| 139 |
+
"target": "P",
|
| 140 |
+
"label": "Task API"
|
| 141 |
+
},
|
| 142 |
+
{
|
| 143 |
+
"source": "G",
|
| 144 |
+
"target": "H"
|
| 145 |
+
},
|
| 146 |
+
{
|
| 147 |
+
"source": "G",
|
| 148 |
+
"target": "I"
|
| 149 |
+
},
|
| 150 |
+
{
|
| 151 |
+
"source": "G",
|
| 152 |
+
"target": "J"
|
| 153 |
+
},
|
| 154 |
+
{
|
| 155 |
+
"source": "G",
|
| 156 |
+
"target": "K"
|
| 157 |
+
},
|
| 158 |
+
{
|
| 159 |
+
"source": "H",
|
| 160 |
+
"target": "L"
|
| 161 |
+
},
|
| 162 |
+
{
|
| 163 |
+
"source": "I",
|
| 164 |
+
"target": "O"
|
| 165 |
+
},
|
| 166 |
+
{
|
| 167 |
+
"source": "J",
|
| 168 |
+
"target": "R"
|
| 169 |
+
},
|
| 170 |
+
{
|
| 171 |
+
"source": "K",
|
| 172 |
+
"target": "U"
|
| 173 |
+
},
|
| 174 |
+
{
|
| 175 |
+
"source": "L",
|
| 176 |
+
"target": "M"
|
| 177 |
+
},
|
| 178 |
+
{
|
| 179 |
+
"source": "L",
|
| 180 |
+
"target": "N"
|
| 181 |
+
},
|
| 182 |
+
{
|
| 183 |
+
"source": "O",
|
| 184 |
+
"target": "P"
|
| 185 |
+
},
|
| 186 |
+
{
|
| 187 |
+
"source": "O",
|
| 188 |
+
"target": "Q"
|
| 189 |
+
},
|
| 190 |
+
{
|
| 191 |
+
"source": "R",
|
| 192 |
+
"target": "S"
|
| 193 |
+
},
|
| 194 |
+
{
|
| 195 |
+
"source": "R",
|
| 196 |
+
"target": "T"
|
| 197 |
+
},
|
| 198 |
+
{
|
| 199 |
+
"source": "U",
|
| 200 |
+
"target": "V"
|
| 201 |
+
},
|
| 202 |
+
{
|
| 203 |
+
"source": "U",
|
| 204 |
+
"target": "W"
|
| 205 |
+
},
|
| 206 |
+
{
|
| 207 |
+
"source": "X",
|
| 208 |
+
"target": "H"
|
| 209 |
+
},
|
| 210 |
+
{
|
| 211 |
+
"source": "X",
|
| 212 |
+
"target": "I"
|
| 213 |
+
},
|
| 214 |
+
{
|
| 215 |
+
"source": "X",
|
| 216 |
+
"target": "J"
|
| 217 |
+
},
|
| 218 |
+
{
|
| 219 |
+
"source": "X",
|
| 220 |
+
"target": "K"
|
| 221 |
+
},
|
| 222 |
+
{
|
| 223 |
+
"source": "X",
|
| 224 |
+
"target": "M"
|
| 225 |
+
},
|
| 226 |
+
{
|
| 227 |
+
"source": "X",
|
| 228 |
+
"target": "P"
|
| 229 |
+
},
|
| 230 |
+
{
|
| 231 |
+
"source": "X",
|
| 232 |
+
"target": "S"
|
| 233 |
+
},
|
| 234 |
+
{
|
| 235 |
+
"source": "X",
|
| 236 |
+
"target": "V"
|
| 237 |
+
},
|
| 238 |
+
{
|
| 239 |
+
"source": "Y",
|
| 240 |
+
"target": "F"
|
| 241 |
+
},
|
| 242 |
+
{
|
| 243 |
+
"source": "Y",
|
| 244 |
+
"target": "G"
|
| 245 |
+
}
|
| 246 |
+
]
|
| 247 |
+
},
|
| 248 |
+
{
|
| 249 |
+
"type": "text",
|
| 250 |
+
"text": "在当前容器运行时的 Shim v2 模型中,containerd 每创建一个 Pod,就要创建一个对应的 Shim 进程用于 Pod 的管理,Shim 进程再去创建虚拟机和容器,在这种场景下,管理面 Shim 进程和 Pod 的数量关系为 1:1。但在 Kuasar 中,只需要运行一个 Kuasar-Sandboxer 进程,containerd 对 Pod 的管理都是调用 Sandboxer 对外暴露的接口,不再需要为每个 Pod 都拉起一个管理进程,因此,管理面 Sandboxer 进程和 Pod 的数量关系为 1:N。这种模型可以大大减少常驻进程的数量,降低容器管理面底噪,整个架构也因此变得更清晰简洁。"
|
| 251 |
+
},
|
| 252 |
+
{
|
| 253 |
+
"type": "text",
|
| 254 |
+
"text": "基于 Kuasar 安全容器和 TEE 融合,实现 Kuasar 机密容器,保护容器镜像、工作负载及所运行虚机环境的机密性和完整性,防止非授权实体的非法访问,同时兼容云原生应用生态,提高机密计算的易用性。"
|
| 255 |
+
},
|
| 256 |
+
{
|
| 257 |
+
"type": "text",
|
| 258 |
+
"text": "图 19 展示了基于 Kuasar 和 secGear 的机密容器方案。这里 Kuasar 主要对接 QEMU 实现机密虚机生命周期管理,向上屏蔽不同类型的机密虚机,如鲲鹏 virtCCA/CCA 等。iSulad 是将拉取容器镜像动作卸载到机密容器内的 Kuasar-task,在机密容器内部拉取并解密容器镜像,保护容器镜像的机密性和完整性。而 secGear 用来屏蔽 TEE 硬件差异,提供统一的远程证明和镜像加解密密钥获取流程。"
|
| 259 |
+
},
|
| 260 |
+
{
|
| 261 |
+
"type": "footer",
|
| 262 |
+
"text": "文档版本 V1.0 版权所有 © 华为技术有限公司"
|
| 263 |
+
},
|
| 264 |
+
{
|
| 265 |
+
"type": "page_number",
|
| 266 |
+
"text": "35"
|
| 267 |
+
}
|
| 268 |
+
]
|
diagrams-and-tables/annotations/cn_diagram_26.json
ADDED
|
@@ -0,0 +1,211 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
[
|
| 2 |
+
{
|
| 3 |
+
"type": "diagram_caption",
|
| 4 |
+
"text": "图 20 网络设备三层密钥管理组件"
|
| 5 |
+
},
|
| 6 |
+
{
|
| 7 |
+
"type": "diagram",
|
| 8 |
+
"nodes": [
|
| 9 |
+
{
|
| 10 |
+
"id": "A",
|
| 11 |
+
"text": "APP"
|
| 12 |
+
},
|
| 13 |
+
{
|
| 14 |
+
"id": "B",
|
| 15 |
+
"text": "Storage data encryption"
|
| 16 |
+
},
|
| 17 |
+
{
|
| 18 |
+
"id": "C",
|
| 19 |
+
"text": "passwords"
|
| 20 |
+
},
|
| 21 |
+
{
|
| 22 |
+
"id": "D",
|
| 23 |
+
"text": "certificates"
|
| 24 |
+
},
|
| 25 |
+
{
|
| 26 |
+
"id": "E",
|
| 27 |
+
"text": "files"
|
| 28 |
+
},
|
| 29 |
+
{
|
| 30 |
+
"id": "F",
|
| 31 |
+
"text": "Transport data encryption"
|
| 32 |
+
},
|
| 33 |
+
{
|
| 34 |
+
"id": "G",
|
| 35 |
+
"text": "MacSec"
|
| 36 |
+
},
|
| 37 |
+
{
|
| 38 |
+
"id": "H",
|
| 39 |
+
"text": "SSH"
|
| 40 |
+
},
|
| 41 |
+
{
|
| 42 |
+
"id": "I",
|
| 43 |
+
"text": "TLS"
|
| 44 |
+
},
|
| 45 |
+
{
|
| 46 |
+
"id": "J",
|
| 47 |
+
"text": ""
|
| 48 |
+
},
|
| 49 |
+
{
|
| 50 |
+
"id": "K",
|
| 51 |
+
"text": "Cipher algorithm libs"
|
| 52 |
+
},
|
| 53 |
+
{
|
| 54 |
+
"id": "L",
|
| 55 |
+
"text": "对称加密算法"
|
| 56 |
+
},
|
| 57 |
+
{
|
| 58 |
+
"id": "M",
|
| 59 |
+
"text": "公钥加密算法"
|
| 60 |
+
},
|
| 61 |
+
{
|
| 62 |
+
"id": "N",
|
| 63 |
+
"text": "消息认证码"
|
| 64 |
+
},
|
| 65 |
+
{
|
| 66 |
+
"id": "O",
|
| 67 |
+
"text": "哈希算法"
|
| 68 |
+
},
|
| 69 |
+
{
|
| 70 |
+
"id": "P",
|
| 71 |
+
"text": "三层密钥管理"
|
| 72 |
+
},
|
| 73 |
+
{
|
| 74 |
+
"id": "Q",
|
| 75 |
+
"text": "工作密钥1"
|
| 76 |
+
},
|
| 77 |
+
{
|
| 78 |
+
"id": "R",
|
| 79 |
+
"text": "工作密钥n"
|
| 80 |
+
},
|
| 81 |
+
{
|
| 82 |
+
"id": "S",
|
| 83 |
+
"text": "主密钥"
|
| 84 |
+
},
|
| 85 |
+
{
|
| 86 |
+
"id": "T",
|
| 87 |
+
"text": "Hardware"
|
| 88 |
+
},
|
| 89 |
+
{
|
| 90 |
+
"id": "U",
|
| 91 |
+
"text": "Root key"
|
| 92 |
+
}
|
| 93 |
+
],
|
| 94 |
+
"relationships": [
|
| 95 |
+
{
|
| 96 |
+
"source": "A",
|
| 97 |
+
"target": "B"
|
| 98 |
+
},
|
| 99 |
+
{
|
| 100 |
+
"source": "A",
|
| 101 |
+
"target": "F"
|
| 102 |
+
},
|
| 103 |
+
{
|
| 104 |
+
"source": "B",
|
| 105 |
+
"target": "C"
|
| 106 |
+
},
|
| 107 |
+
{
|
| 108 |
+
"source": "B",
|
| 109 |
+
"target": "D"
|
| 110 |
+
},
|
| 111 |
+
{
|
| 112 |
+
"source": "B",
|
| 113 |
+
"target": "E"
|
| 114 |
+
},
|
| 115 |
+
{
|
| 116 |
+
"source": "F",
|
| 117 |
+
"target": "G"
|
| 118 |
+
},
|
| 119 |
+
{
|
| 120 |
+
"source": "F",
|
| 121 |
+
"target": "H"
|
| 122 |
+
},
|
| 123 |
+
{
|
| 124 |
+
"source": "F",
|
| 125 |
+
"target": "I"
|
| 126 |
+
},
|
| 127 |
+
{
|
| 128 |
+
"source": "A",
|
| 129 |
+
"target": "J",
|
| 130 |
+
"label": "Encryption"
|
| 131 |
+
},
|
| 132 |
+
{
|
| 133 |
+
"source": "J",
|
| 134 |
+
"target": "K"
|
| 135 |
+
},
|
| 136 |
+
{
|
| 137 |
+
"source": "J",
|
| 138 |
+
"target": "P"
|
| 139 |
+
},
|
| 140 |
+
{
|
| 141 |
+
"source": "K",
|
| 142 |
+
"target": "L"
|
| 143 |
+
},
|
| 144 |
+
{
|
| 145 |
+
"source": "K",
|
| 146 |
+
"target": "M"
|
| 147 |
+
},
|
| 148 |
+
{
|
| 149 |
+
"source": "K",
|
| 150 |
+
"target": "N"
|
| 151 |
+
},
|
| 152 |
+
{
|
| 153 |
+
"source": "K",
|
| 154 |
+
"target": "O"
|
| 155 |
+
},
|
| 156 |
+
{
|
| 157 |
+
"source": "P",
|
| 158 |
+
"target": "Q"
|
| 159 |
+
},
|
| 160 |
+
{
|
| 161 |
+
"source": "P",
|
| 162 |
+
"target": "R"
|
| 163 |
+
},
|
| 164 |
+
{
|
| 165 |
+
"source": "P",
|
| 166 |
+
"target": "S"
|
| 167 |
+
},
|
| 168 |
+
{
|
| 169 |
+
"source": "S",
|
| 170 |
+
"target": "Q"
|
| 171 |
+
},
|
| 172 |
+
{
|
| 173 |
+
"source": "S",
|
| 174 |
+
"target": "R"
|
| 175 |
+
},
|
| 176 |
+
{
|
| 177 |
+
"source": "T",
|
| 178 |
+
"target": "U"
|
| 179 |
+
},
|
| 180 |
+
{
|
| 181 |
+
"source": "S",
|
| 182 |
+
"target": "U",
|
| 183 |
+
"label": "Encryption protection"
|
| 184 |
+
}
|
| 185 |
+
]
|
| 186 |
+
},
|
| 187 |
+
{
|
| 188 |
+
"type": "text",
|
| 189 |
+
"text": "通过在设备生命周期各环节贯穿可验证的信任机制,HCIST 构建了面向未来的自主可信网络设备体系。该体系使设备能够在复杂、异构、跨域的算力环境中持续维持可信状态,不仅为管道安全提供了坚实的硬件基础,也为实现高性能通信安全与跨域算力协同提供了关键保障。"
|
| 190 |
+
},
|
| 191 |
+
{
|
| 192 |
+
"type": "title",
|
| 193 |
+
"text": "7.3 Scale Up 及 Scale Out 通信安全"
|
| 194 |
+
},
|
| 195 |
+
{
|
| 196 |
+
"type": "text",
|
| 197 |
+
"text": "随着大模型、生成式 AI 和多方数据协作的快速发展,算力需求呈指数级增长,单一计算节点已无法满足复杂任务的性能要求。越来越多的计算需要依托 Scale Up(单节点多芯片协同)和 Scale Out(跨节点、跨集群协作)来完成,从而实现更高吞吐和更低时延的数据传输。然而,这种高度互联的算力架构意味着模型权重、企业数据、RAG 索引、用户隐私等敏感信息将在不同计算芯片、节点、集群甚至数据中心之间高频流动,带来了比传统网络更复杂的安全挑战。"
|
| 198 |
+
},
|
| 199 |
+
{
|
| 200 |
+
"type": "text",
|
| 201 |
+
"text": "在算力集群内部和跨集群协作过程中,安全威胁呈现多维度特征:在 Scale Up 场景下,多租户共享硬件资源,恶意程序可通过固件漏洞、隐蔽信道或配置篡改发起攻击;在 Scale Out 场景中,跨框、跨地域的高带宽传输更容易面临线路嗅探、数据篡改与源地址伪造等威胁。同时,大模型训练和推理对性能的要求极为苛刻:部分场景下需实现纳秒级时延与 Tbps 级带宽,而传统基于软件加密的安全通信协议往往无法在性能和安全之间取得平衡。如何在保持高性能的同时保障安全,成为 HCIST 管道安全体系中的关键挑战之一。"
|
| 202 |
+
},
|
| 203 |
+
{
|
| 204 |
+
"type": "footer",
|
| 205 |
+
"text": "文档版本 V1.0 版权所有 © 华为技术有限公司 39"
|
| 206 |
+
},
|
| 207 |
+
{
|
| 208 |
+
"type": "page_number",
|
| 209 |
+
"text": "39"
|
| 210 |
+
}
|
| 211 |
+
]
|
diagrams-and-tables/annotations/cn_diagram_27.json
ADDED
|
@@ -0,0 +1,345 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
[
|
| 2 |
+
{
|
| 3 |
+
"type": "title",
|
| 4 |
+
"text": "8. 典型应用场景"
|
| 5 |
+
},
|
| 6 |
+
{
|
| 7 |
+
"type": "text",
|
| 8 |
+
"text": "HCIST 通过端管云协同的隐私保护架构与纵向全栈安全能力的有机整合,为各行业敏感数据处理场景提供安全可靠的算力支撑。整个架构既可以全栈式部署,发挥端管云协同优势,最大限度提升算力安全基础设施的安全特性,也可以对接不同厂商的算力底座,实现灵活的安全防御策略,适配不同的业务场景和软硬件设施。本章会从端云协同、数据安全、大模型保护、云原生安全特性等维度介绍 HCIST 在这些典型高价值场景中展现出的显著优势,虽然在案例介绍中以华为全栈设备为算力基础设施,但是在实际应用时也可以充分整合和对接不同厂商的算力设备及其安全特性,实现方案的灵活部署。"
|
| 9 |
+
},
|
| 10 |
+
{
|
| 11 |
+
"type": "title",
|
| 12 |
+
"text": "8.1 端云协同大模型推理"
|
| 13 |
+
},
|
| 14 |
+
{
|
| 15 |
+
"type": "text",
|
| 16 |
+
"text": "在 HCIST 算力基础设施安全技术能力的支撑下,HarmonyOS 的小艺个人隐私助理围绕“端云协同、端云安全等同、全栈安全”的核心理念,构建了一种以用户为中心的隐私保护体系(如图 23 所示)。该体系的关键特征并非简单地在端侧加密或云侧隔离,而是在端与云之间建立一套动态、可验证、基于信任链的协同机制,使用户数据在全链路中始终可控。无论数据是在设备本地生成,还是在云端被用于 AI 计算,所有传输、处理与存储路径都依托端云间强耦合的加密与策略管理实现精细化保护。通过端云协同安全框架,释放云上安全算力,达到保障业务体验的目的。"
|
| 17 |
+
},
|
| 18 |
+
{
|
| 19 |
+
"type": "diagram_caption",
|
| 20 |
+
"text": "图23 小艺场景端云协同大模型隐私机密推理"
|
| 21 |
+
},
|
| 22 |
+
{
|
| 23 |
+
"type": "diagram",
|
| 24 |
+
"nodes": [
|
| 25 |
+
{
|
| 26 |
+
"id": "A",
|
| 27 |
+
"text": "以用户为中心的隐私计算体系"
|
| 28 |
+
},
|
| 29 |
+
{
|
| 30 |
+
"id": "B",
|
| 31 |
+
"text": "端侧性能增强"
|
| 32 |
+
},
|
| 33 |
+
{
|
| 34 |
+
"id": "C",
|
| 35 |
+
"text": "端云等同 全栈安全"
|
| 36 |
+
},
|
| 37 |
+
{
|
| 38 |
+
"id": "D",
|
| 39 |
+
"text": "严密保护隐私"
|
| 40 |
+
},
|
| 41 |
+
{
|
| 42 |
+
"id": "E",
|
| 43 |
+
"text": "数据不存储"
|
| 44 |
+
},
|
| 45 |
+
{
|
| 46 |
+
"id": "F",
|
| 47 |
+
"text": "数据不泄露"
|
| 48 |
+
},
|
| 49 |
+
{
|
| 50 |
+
"id": "G",
|
| 51 |
+
"text": "数据不滥用"
|
| 52 |
+
},
|
| 53 |
+
{
|
| 54 |
+
"id": "H",
|
| 55 |
+
"text": "隐私安全新架构"
|
| 56 |
+
},
|
| 57 |
+
{
|
| 58 |
+
"id": "I",
|
| 59 |
+
"text": "端:芯片级硬件安全计算"
|
| 60 |
+
},
|
| 61 |
+
{
|
| 62 |
+
"id": "J",
|
| 63 |
+
"text": "端机密计算区"
|
| 64 |
+
},
|
| 65 |
+
{
|
| 66 |
+
"id": "K",
|
| 67 |
+
"text": "安全证明"
|
| 68 |
+
},
|
| 69 |
+
{
|
| 70 |
+
"id": "L",
|
| 71 |
+
"text": "安全系统"
|
| 72 |
+
},
|
| 73 |
+
{
|
| 74 |
+
"id": "M",
|
| 75 |
+
"text": "安全硬件"
|
| 76 |
+
},
|
| 77 |
+
{
|
| 78 |
+
"id": "N",
|
| 79 |
+
"text": "链路:安全会话通信"
|
| 80 |
+
},
|
| 81 |
+
{
|
| 82 |
+
"id": "O",
|
| 83 |
+
"text": "安全节点"
|
| 84 |
+
},
|
| 85 |
+
{
|
| 86 |
+
"id": "P",
|
| 87 |
+
"text": "安全盲化"
|
| 88 |
+
},
|
| 89 |
+
{
|
| 90 |
+
"id": "Q",
|
| 91 |
+
"text": "云:无状态计算不存储"
|
| 92 |
+
},
|
| 93 |
+
{
|
| 94 |
+
"id": "R",
|
| 95 |
+
"text": "云机密计算区"
|
| 96 |
+
},
|
| 97 |
+
{
|
| 98 |
+
"id": "S",
|
| 99 |
+
"text": "安全计算环境"
|
| 100 |
+
},
|
| 101 |
+
{
|
| 102 |
+
"id": "T",
|
| 103 |
+
"text": "安全可信"
|
| 104 |
+
},
|
| 105 |
+
{
|
| 106 |
+
"id": "U",
|
| 107 |
+
"text": "身份远程证明"
|
| 108 |
+
},
|
| 109 |
+
{
|
| 110 |
+
"id": "V",
|
| 111 |
+
"text": "节点直连端端加密"
|
| 112 |
+
},
|
| 113 |
+
{
|
| 114 |
+
"id": "W",
|
| 115 |
+
"text": "匿名身份管理"
|
| 116 |
+
},
|
| 117 |
+
{
|
| 118 |
+
"id": "X",
|
| 119 |
+
"text": "TEE可信环境"
|
| 120 |
+
},
|
| 121 |
+
{
|
| 122 |
+
"id": "Y",
|
| 123 |
+
"text": "安全芯片"
|
| 124 |
+
},
|
| 125 |
+
{
|
| 126 |
+
"id": "Z",
|
| 127 |
+
"text": "3rd Relay隔离两端信息"
|
| 128 |
+
},
|
| 129 |
+
{
|
| 130 |
+
"id": "AA",
|
| 131 |
+
"text": "身份匿名化不可追溯"
|
| 132 |
+
},
|
| 133 |
+
{
|
| 134 |
+
"id": "AB",
|
| 135 |
+
"text": "数据使用���全"
|
| 136 |
+
},
|
| 137 |
+
{
|
| 138 |
+
"id": "AC",
|
| 139 |
+
"text": "最小化运行时"
|
| 140 |
+
},
|
| 141 |
+
{
|
| 142 |
+
"id": "AD",
|
| 143 |
+
"text": "可证明机密分区"
|
| 144 |
+
},
|
| 145 |
+
{
|
| 146 |
+
"id": "AE",
|
| 147 |
+
"text": "全栈软件完整性"
|
| 148 |
+
},
|
| 149 |
+
{
|
| 150 |
+
"id": "AF",
|
| 151 |
+
"text": "TEE秘钥保护"
|
| 152 |
+
},
|
| 153 |
+
{
|
| 154 |
+
"id": "AG",
|
| 155 |
+
"text": "iTrustee安全OS"
|
| 156 |
+
},
|
| 157 |
+
{
|
| 158 |
+
"id": "AH",
|
| 159 |
+
"text": "安全研究人员独立审计机构"
|
| 160 |
+
},
|
| 161 |
+
{
|
| 162 |
+
"id": "AI",
|
| 163 |
+
"text": "AI可信治理"
|
| 164 |
+
}
|
| 165 |
+
],
|
| 166 |
+
"relationships": [
|
| 167 |
+
{
|
| 168 |
+
"source": "A",
|
| 169 |
+
"target": "C"
|
| 170 |
+
},
|
| 171 |
+
{
|
| 172 |
+
"source": "B",
|
| 173 |
+
"target": "C"
|
| 174 |
+
},
|
| 175 |
+
{
|
| 176 |
+
"source": "C",
|
| 177 |
+
"target": "D"
|
| 178 |
+
},
|
| 179 |
+
{
|
| 180 |
+
"source": "C",
|
| 181 |
+
"target": "H"
|
| 182 |
+
},
|
| 183 |
+
{
|
| 184 |
+
"source": "D",
|
| 185 |
+
"target": "E"
|
| 186 |
+
},
|
| 187 |
+
{
|
| 188 |
+
"source": "D",
|
| 189 |
+
"target": "F"
|
| 190 |
+
},
|
| 191 |
+
{
|
| 192 |
+
"source": "D",
|
| 193 |
+
"target": "G"
|
| 194 |
+
},
|
| 195 |
+
{
|
| 196 |
+
"source": "H",
|
| 197 |
+
"target": "I"
|
| 198 |
+
},
|
| 199 |
+
{
|
| 200 |
+
"source": "H",
|
| 201 |
+
"target": "N"
|
| 202 |
+
},
|
| 203 |
+
{
|
| 204 |
+
"source": "H",
|
| 205 |
+
"target": "Q"
|
| 206 |
+
},
|
| 207 |
+
{
|
| 208 |
+
"source": "I",
|
| 209 |
+
"target": "J"
|
| 210 |
+
},
|
| 211 |
+
{
|
| 212 |
+
"source": "J",
|
| 213 |
+
"target": "U"
|
| 214 |
+
},
|
| 215 |
+
{
|
| 216 |
+
"source": "J",
|
| 217 |
+
"target": "V"
|
| 218 |
+
},
|
| 219 |
+
{
|
| 220 |
+
"source": "J",
|
| 221 |
+
"target": "W"
|
| 222 |
+
},
|
| 223 |
+
{
|
| 224 |
+
"source": "J",
|
| 225 |
+
"target": "X"
|
| 226 |
+
},
|
| 227 |
+
{
|
| 228 |
+
"source": "J",
|
| 229 |
+
"target": "Y"
|
| 230 |
+
},
|
| 231 |
+
{
|
| 232 |
+
"source": "K",
|
| 233 |
+
"target": "U"
|
| 234 |
+
},
|
| 235 |
+
{
|
| 236 |
+
"source": "K",
|
| 237 |
+
"target": "V"
|
| 238 |
+
},
|
| 239 |
+
{
|
| 240 |
+
"source": "K",
|
| 241 |
+
"target": "W"
|
| 242 |
+
},
|
| 243 |
+
{
|
| 244 |
+
"source": "L",
|
| 245 |
+
"target": "X"
|
| 246 |
+
},
|
| 247 |
+
{
|
| 248 |
+
"source": "M",
|
| 249 |
+
"target": "Y"
|
| 250 |
+
},
|
| 251 |
+
{
|
| 252 |
+
"source": "N",
|
| 253 |
+
"target": "O"
|
| 254 |
+
},
|
| 255 |
+
{
|
| 256 |
+
"source": "N",
|
| 257 |
+
"target": "P"
|
| 258 |
+
},
|
| 259 |
+
{
|
| 260 |
+
"source": "O",
|
| 261 |
+
"target": "Z"
|
| 262 |
+
},
|
| 263 |
+
{
|
| 264 |
+
"source": "Q",
|
| 265 |
+
"target": "R"
|
| 266 |
+
},
|
| 267 |
+
{
|
| 268 |
+
"source": "R",
|
| 269 |
+
"target": "AB"
|
| 270 |
+
},
|
| 271 |
+
{
|
| 272 |
+
"source": "R",
|
| 273 |
+
"target": "AC"
|
| 274 |
+
},
|
| 275 |
+
{
|
| 276 |
+
"source": "R",
|
| 277 |
+
"target": "AD"
|
| 278 |
+
},
|
| 279 |
+
{
|
| 280 |
+
"source": "R",
|
| 281 |
+
"target": "AE"
|
| 282 |
+
},
|
| 283 |
+
{
|
| 284 |
+
"source": "R",
|
| 285 |
+
"target": "AF"
|
| 286 |
+
},
|
| 287 |
+
{
|
| 288 |
+
"source": "R",
|
| 289 |
+
"target": "AG"
|
| 290 |
+
},
|
| 291 |
+
{
|
| 292 |
+
"source": "R",
|
| 293 |
+
"target": "AH"
|
| 294 |
+
},
|
| 295 |
+
{
|
| 296 |
+
"source": "R",
|
| 297 |
+
"target": "AI"
|
| 298 |
+
},
|
| 299 |
+
{
|
| 300 |
+
"source": "S",
|
| 301 |
+
"target": "AB"
|
| 302 |
+
},
|
| 303 |
+
{
|
| 304 |
+
"source": "S",
|
| 305 |
+
"target": "AC"
|
| 306 |
+
},
|
| 307 |
+
{
|
| 308 |
+
"source": "S",
|
| 309 |
+
"target": "AD"
|
| 310 |
+
},
|
| 311 |
+
{
|
| 312 |
+
"source": "S",
|
| 313 |
+
"target": "AE"
|
| 314 |
+
},
|
| 315 |
+
{
|
| 316 |
+
"source": "S",
|
| 317 |
+
"target": "AF"
|
| 318 |
+
},
|
| 319 |
+
{
|
| 320 |
+
"source": "S",
|
| 321 |
+
"target": "AG"
|
| 322 |
+
},
|
| 323 |
+
{
|
| 324 |
+
"source": "T",
|
| 325 |
+
"target": "AH"
|
| 326 |
+
},
|
| 327 |
+
{
|
| 328 |
+
"source": "P",
|
| 329 |
+
"target": "AA"
|
| 330 |
+
},
|
| 331 |
+
{
|
| 332 |
+
"source": "T",
|
| 333 |
+
"target": "AI"
|
| 334 |
+
}
|
| 335 |
+
]
|
| 336 |
+
},
|
| 337 |
+
{
|
| 338 |
+
"type": "footer",
|
| 339 |
+
"text": "文档版本 V1.0 版权所有 © 华为技术有限公司 39"
|
| 340 |
+
},
|
| 341 |
+
{
|
| 342 |
+
"type": "page_number",
|
| 343 |
+
"text": "43"
|
| 344 |
+
}
|
| 345 |
+
]
|
diagrams-and-tables/annotations/cn_diagram_28.json
ADDED
|
@@ -0,0 +1,265 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
[
|
| 2 |
+
{
|
| 3 |
+
"type": "header",
|
| 4 |
+
"text": "NXP"
|
| 5 |
+
},
|
| 6 |
+
{
|
| 7 |
+
"type": "header",
|
| 8 |
+
"text": "oT)要变为现实,还缺什么"
|
| 9 |
+
},
|
| 10 |
+
{
|
| 11 |
+
"type": "text",
|
| 12 |
+
"text": "目前可使用的技术有很多,也有许多仍在开发中,这些新技术允许车辆相互通信、并与中央控制单元进行通信。这些智能汽车还可以感知道路、交通标志和道路标志,并使用GPS和通信链路,避免经过即将拥堵的道路,并避免在转弯处出现事故,或与中央控制单元配合,避免经过处于倒塌边缘的高危桥梁。"
|
| 13 |
+
},
|
| 14 |
+
{
|
| 15 |
+
"type": "text",
|
| 16 |
+
"text": "远程监控患者是另一个与使用有关的示例。例如,设想一下一个跟踪生物特征的植入式传感节点,向一个老年患者发出一个异常的读数信号。如果患者没有反响服用药,那么节点会拨打紧急电话联系名单的联系人,如果无人接听,节点会呼叫下一个联系人,最后如果仍无人接听,节点便会联系监控诊所或快速提供其他紧急援助。另一个示例是持续监控慢性疾病,帮助医生确定最佳的治疗方式,只需最少的人力干预。"
|
| 17 |
+
},
|
| 18 |
+
{
|
| 19 |
+
"type": "text",
|
| 20 |
+
"text": "所有以上用例的通用要求包括:\n1) 传感和数据采集功能(传感节点)\n2) 本地嵌入式处理功能层(本地嵌入式处理节点)\n3) 有线和/或无线通信功能(连接节点)\n4) 自动化任务并支持新的服务类别的软件\n5) 远程网络/基于云的嵌入式处理功能(远程嵌入式处理节点)\n6) 跨信号路径的完整安全性能"
|
| 21 |
+
},
|
| 22 |
+
{
|
| 23 |
+
"type": "diagram_caption",
|
| 24 |
+
"text": "物联网技术功能视图"
|
| 25 |
+
},
|
| 26 |
+
{
|
| 27 |
+
"type": "diagram",
|
| 28 |
+
"nodes": [
|
| 29 |
+
{
|
| 30 |
+
"id": "A",
|
| 31 |
+
"text": "传感和/或智能设备"
|
| 32 |
+
},
|
| 33 |
+
{
|
| 34 |
+
"id": "B",
|
| 35 |
+
"text": "连接节点"
|
| 36 |
+
},
|
| 37 |
+
{
|
| 38 |
+
"id": "C",
|
| 39 |
+
"text": "嵌入式处理节点层"
|
| 40 |
+
},
|
| 41 |
+
{
|
| 42 |
+
"id": "D",
|
| 43 |
+
"text": "连接节点"
|
| 44 |
+
},
|
| 45 |
+
{
|
| 46 |
+
"id": "E",
|
| 47 |
+
"text": "远程基于云的处理"
|
| 48 |
+
},
|
| 49 |
+
{
|
| 50 |
+
"id": "F",
|
| 51 |
+
"text": "应用/操作"
|
| 52 |
+
},
|
| 53 |
+
{
|
| 54 |
+
"id": "G",
|
| 55 |
+
"text": "通过带屏幕的设备由用户驱动或基于数据参数自动操作"
|
| 56 |
+
},
|
| 57 |
+
{
|
| 58 |
+
"id": "H",
|
| 59 |
+
"text": "洞察/大数据"
|
| 60 |
+
},
|
| 61 |
+
{
|
| 62 |
+
"id": "I",
|
| 63 |
+
"text": "商业智能数据分析"
|
| 64 |
+
},
|
| 65 |
+
{
|
| 66 |
+
"id": "J",
|
| 67 |
+
"text": "在所有节点上的软件"
|
| 68 |
+
},
|
| 69 |
+
{
|
| 70 |
+
"id": "K",
|
| 71 |
+
"text": "S"
|
| 72 |
+
},
|
| 73 |
+
{
|
| 74 |
+
"id": "L",
|
| 75 |
+
"text": "S"
|
| 76 |
+
},
|
| 77 |
+
{
|
| 78 |
+
"id": "M",
|
| 79 |
+
"text": "S"
|
| 80 |
+
},
|
| 81 |
+
{
|
| 82 |
+
"id": "N",
|
| 83 |
+
"text": "P"
|
| 84 |
+
},
|
| 85 |
+
{
|
| 86 |
+
"id": "O",
|
| 87 |
+
"text": "P"
|
| 88 |
+
},
|
| 89 |
+
{
|
| 90 |
+
"id": "P",
|
| 91 |
+
"text": "P"
|
| 92 |
+
},
|
| 93 |
+
{
|
| 94 |
+
"id": "Q",
|
| 95 |
+
"text": "C"
|
| 96 |
+
},
|
| 97 |
+
{
|
| 98 |
+
"id": "R",
|
| 99 |
+
"text": "C"
|
| 100 |
+
},
|
| 101 |
+
{
|
| 102 |
+
"id": "S",
|
| 103 |
+
"text": "C"
|
| 104 |
+
},
|
| 105 |
+
{
|
| 106 |
+
"id": "T",
|
| 107 |
+
"text": "P"
|
| 108 |
+
},
|
| 109 |
+
{
|
| 110 |
+
"id": "U",
|
| 111 |
+
"text": "C"
|
| 112 |
+
},
|
| 113 |
+
{
|
| 114 |
+
"id": "V",
|
| 115 |
+
"text": "P"
|
| 116 |
+
},
|
| 117 |
+
{
|
| 118 |
+
"id": "W",
|
| 119 |
+
"text": "S:传感"
|
| 120 |
+
},
|
| 121 |
+
{
|
| 122 |
+
"id": "X",
|
| 123 |
+
"text": "P:嵌入式处理"
|
| 124 |
+
},
|
| 125 |
+
{
|
| 126 |
+
"id": "Y",
|
| 127 |
+
"text": "C:通讯"
|
| 128 |
+
}
|
| 129 |
+
],
|
| 130 |
+
"relationships": [
|
| 131 |
+
{
|
| 132 |
+
"source": "A",
|
| 133 |
+
"target": "J"
|
| 134 |
+
},
|
| 135 |
+
{
|
| 136 |
+
"source": "A",
|
| 137 |
+
"target": "K"
|
| 138 |
+
},
|
| 139 |
+
{
|
| 140 |
+
"source": "A",
|
| 141 |
+
"target": "L"
|
| 142 |
+
},
|
| 143 |
+
{
|
| 144 |
+
"source": "A",
|
| 145 |
+
"target": "M"
|
| 146 |
+
},
|
| 147 |
+
{
|
| 148 |
+
"source": "A",
|
| 149 |
+
"target": "N"
|
| 150 |
+
},
|
| 151 |
+
{
|
| 152 |
+
"source": "A",
|
| 153 |
+
"target": "O"
|
| 154 |
+
},
|
| 155 |
+
{
|
| 156 |
+
"source": "A",
|
| 157 |
+
"target": "P"
|
| 158 |
+
},
|
| 159 |
+
{
|
| 160 |
+
"source": "B",
|
| 161 |
+
"target": "J"
|
| 162 |
+
},
|
| 163 |
+
{
|
| 164 |
+
"source": "B",
|
| 165 |
+
"target": "Q"
|
| 166 |
+
},
|
| 167 |
+
{
|
| 168 |
+
"source": "B",
|
| 169 |
+
"target": "R"
|
| 170 |
+
},
|
| 171 |
+
{
|
| 172 |
+
"source": "B",
|
| 173 |
+
"target": "S"
|
| 174 |
+
},
|
| 175 |
+
{
|
| 176 |
+
"source": "C",
|
| 177 |
+
"target": "J"
|
| 178 |
+
},
|
| 179 |
+
{
|
| 180 |
+
"source": "C",
|
| 181 |
+
"target": "T"
|
| 182 |
+
},
|
| 183 |
+
{
|
| 184 |
+
"source": "D",
|
| 185 |
+
"target": "J"
|
| 186 |
+
},
|
| 187 |
+
{
|
| 188 |
+
"source": "D",
|
| 189 |
+
"target": "U"
|
| 190 |
+
},
|
| 191 |
+
{
|
| 192 |
+
"source": "E",
|
| 193 |
+
"target": "J"
|
| 194 |
+
},
|
| 195 |
+
{
|
| 196 |
+
"source": "E",
|
| 197 |
+
"target": "V"
|
| 198 |
+
},
|
| 199 |
+
{
|
| 200 |
+
"source": "F",
|
| 201 |
+
"target": "V"
|
| 202 |
+
},
|
| 203 |
+
{
|
| 204 |
+
"source": "H",
|
| 205 |
+
"target": "V"
|
| 206 |
+
},
|
| 207 |
+
{
|
| 208 |
+
"source": "F",
|
| 209 |
+
"target": "G"
|
| 210 |
+
},
|
| 211 |
+
{
|
| 212 |
+
"source": "H",
|
| 213 |
+
"target": "I"
|
| 214 |
+
},
|
| 215 |
+
{
|
| 216 |
+
"source": "K",
|
| 217 |
+
"target": "L"
|
| 218 |
+
},
|
| 219 |
+
{
|
| 220 |
+
"source": "L",
|
| 221 |
+
"target": "M"
|
| 222 |
+
},
|
| 223 |
+
{
|
| 224 |
+
"source": "O",
|
| 225 |
+
"target": "P"
|
| 226 |
+
},
|
| 227 |
+
{
|
| 228 |
+
"source": "O",
|
| 229 |
+
"target": "R"
|
| 230 |
+
},
|
| 231 |
+
{
|
| 232 |
+
"source": "N",
|
| 233 |
+
"target": "Q"
|
| 234 |
+
},
|
| 235 |
+
{
|
| 236 |
+
"source": "P",
|
| 237 |
+
"target": "S"
|
| 238 |
+
},
|
| 239 |
+
{
|
| 240 |
+
"source": "R",
|
| 241 |
+
"target": "T"
|
| 242 |
+
},
|
| 243 |
+
{
|
| 244 |
+
"source": "T",
|
| 245 |
+
"target": "U"
|
| 246 |
+
},
|
| 247 |
+
{
|
| 248 |
+
"source": "U",
|
| 249 |
+
"target": "V"
|
| 250 |
+
}
|
| 251 |
+
]
|
| 252 |
+
},
|
| 253 |
+
{
|
| 254 |
+
"type": "footer",
|
| 255 |
+
"text": "白皮书"
|
| 256 |
+
},
|
| 257 |
+
{
|
| 258 |
+
"type": "page_number",
|
| 259 |
+
"text": "7"
|
| 260 |
+
},
|
| 261 |
+
{
|
| 262 |
+
"type": "footer",
|
| 263 |
+
"text": "arm.com / freescale.com"
|
| 264 |
+
}
|
| 265 |
+
]
|
diagrams-and-tables/annotations/cn_diagram_29.json
ADDED
|
@@ -0,0 +1,335 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
[
|
| 2 |
+
{
|
| 3 |
+
"type": "header",
|
| 4 |
+
"text": "工业数字化/智能化2030"
|
| 5 |
+
},
|
| 6 |
+
{
|
| 7 |
+
"type": "title",
|
| 8 |
+
"text": "3)技术支撑"
|
| 9 |
+
},
|
| 10 |
+
{
|
| 11 |
+
"type": "text",
|
| 12 |
+
"text": "要实现上述的新理念、新模式,工业软件的上云是大势所趋。工业软件应把握云计算变革的机会窗口,以云、AI、大数据作为关键底层技术支撑,走向全新的、云化的工业软件体系。(图4-30: 云化工业软件的关键底层技术)\n具体而言,新一代工业软件需要基于云计算的架构,依托云的技术特点,实现易集成、易开发、易协同、易扩展四大特点。\n易集成,主要指场景化SaaS。以基于模型为核心理念,工业界伙伴共同打造面向不同工业场景的工具链,形成可集成的场景化SaaS服务。\n易开发,主要指aPaaS。工业界伙伴将工业知识、经验、数据、工具沉淀在云平台,共建共享共用工业根服务,大幅降低工业软件开发门槛。\n易协同,主要指工业软件开发运营中心。工业界伙伴通过共同开发工具组件、按需调用API接口,不仅实现service乃至service on service的敏捷开发,也满足工业企业灵活按需使用、按使用量计费的需求。\n易扩展,主要指gPaaS、IaaS。基于云基础设施,工业企业基于场景需求,面向近期可以灵活调用云端算力、存储资源,实现资源配置的动态优化;面向远期也可以弹性满足业务升级扩容需求,大幅减少硬件置换和运维成本。(图4-31: 基于云计算架构的工业软件体系示意)"
|
| 13 |
+
},
|
| 14 |
+
{
|
| 15 |
+
"type": "diagram_caption",
|
| 16 |
+
"text": "图4-30: 云化工业软件的关键底层技术"
|
| 17 |
+
},
|
| 18 |
+
{
|
| 19 |
+
"type": "diagram",
|
| 20 |
+
"nodes": [
|
| 21 |
+
{
|
| 22 |
+
"id": "A",
|
| 23 |
+
"text": "基于云的计算框架"
|
| 24 |
+
},
|
| 25 |
+
{
|
| 26 |
+
"id": "B",
|
| 27 |
+
"text": "过去"
|
| 28 |
+
},
|
| 29 |
+
{
|
| 30 |
+
"id": "C",
|
| 31 |
+
"text": "未来"
|
| 32 |
+
},
|
| 33 |
+
{
|
| 34 |
+
"id": "D",
|
| 35 |
+
"text": "单机计算框架"
|
| 36 |
+
},
|
| 37 |
+
{
|
| 38 |
+
"id": "E",
|
| 39 |
+
"text": "云计算框架"
|
| 40 |
+
},
|
| 41 |
+
{
|
| 42 |
+
"id": "F",
|
| 43 |
+
"text": "本地开发部署"
|
| 44 |
+
},
|
| 45 |
+
{
|
| 46 |
+
"id": "G",
|
| 47 |
+
"text": "虚拟机"
|
| 48 |
+
},
|
| 49 |
+
{
|
| 50 |
+
"id": "H",
|
| 51 |
+
"text": "传统集中式数据库"
|
| 52 |
+
},
|
| 53 |
+
{
|
| 54 |
+
"id": "I",
|
| 55 |
+
"text": "本地固定资源"
|
| 56 |
+
},
|
| 57 |
+
{
|
| 58 |
+
"id": "J",
|
| 59 |
+
"text": "云端开发部署"
|
| 60 |
+
},
|
| 61 |
+
{
|
| 62 |
+
"id": "K",
|
| 63 |
+
"text": "容器集群"
|
| 64 |
+
},
|
| 65 |
+
{
|
| 66 |
+
"id": "L",
|
| 67 |
+
"text": "分布式云数据库"
|
| 68 |
+
},
|
| 69 |
+
{
|
| 70 |
+
"id": "M",
|
| 71 |
+
"text": "资源动态配置"
|
| 72 |
+
},
|
| 73 |
+
{
|
| 74 |
+
"id": "N",
|
| 75 |
+
"text": "AI"
|
| 76 |
+
},
|
| 77 |
+
{
|
| 78 |
+
"id": "O",
|
| 79 |
+
"text": "驱动工业应用提质增效、进一步少人化"
|
| 80 |
+
},
|
| 81 |
+
{
|
| 82 |
+
"id": "P",
|
| 83 |
+
"text": "大数据"
|
| 84 |
+
},
|
| 85 |
+
{
|
| 86 |
+
"id": "Q",
|
| 87 |
+
"text": "驱动精准分析、决策与创新应用"
|
| 88 |
+
}
|
| 89 |
+
],
|
| 90 |
+
"relationships": [
|
| 91 |
+
{
|
| 92 |
+
"source": "A",
|
| 93 |
+
"target": "B"
|
| 94 |
+
},
|
| 95 |
+
{
|
| 96 |
+
"source": "A",
|
| 97 |
+
"target": "C"
|
| 98 |
+
},
|
| 99 |
+
{
|
| 100 |
+
"source": "A",
|
| 101 |
+
"target": "N",
|
| 102 |
+
"label": "+"
|
| 103 |
+
},
|
| 104 |
+
{
|
| 105 |
+
"source": "A",
|
| 106 |
+
"target": "P",
|
| 107 |
+
"label": "+"
|
| 108 |
+
},
|
| 109 |
+
{
|
| 110 |
+
"source": "B",
|
| 111 |
+
"target": "C",
|
| 112 |
+
"label": "变革"
|
| 113 |
+
},
|
| 114 |
+
{
|
| 115 |
+
"source": "B",
|
| 116 |
+
"target": "D"
|
| 117 |
+
},
|
| 118 |
+
{
|
| 119 |
+
"source": "C",
|
| 120 |
+
"target": "E"
|
| 121 |
+
},
|
| 122 |
+
{
|
| 123 |
+
"source": "D",
|
| 124 |
+
"target": "F"
|
| 125 |
+
},
|
| 126 |
+
{
|
| 127 |
+
"source": "D",
|
| 128 |
+
"target": "G"
|
| 129 |
+
},
|
| 130 |
+
{
|
| 131 |
+
"source": "D",
|
| 132 |
+
"target": "H"
|
| 133 |
+
},
|
| 134 |
+
{
|
| 135 |
+
"source": "D",
|
| 136 |
+
"target": "I"
|
| 137 |
+
},
|
| 138 |
+
{
|
| 139 |
+
"source": "E",
|
| 140 |
+
"target": "J"
|
| 141 |
+
},
|
| 142 |
+
{
|
| 143 |
+
"source": "E",
|
| 144 |
+
"target": "K"
|
| 145 |
+
},
|
| 146 |
+
{
|
| 147 |
+
"source": "E",
|
| 148 |
+
"target": "L"
|
| 149 |
+
},
|
| 150 |
+
{
|
| 151 |
+
"source": "E",
|
| 152 |
+
"target": "M"
|
| 153 |
+
},
|
| 154 |
+
{
|
| 155 |
+
"source": "N",
|
| 156 |
+
"target": "O"
|
| 157 |
+
},
|
| 158 |
+
{
|
| 159 |
+
"source": "P",
|
| 160 |
+
"target": "Q"
|
| 161 |
+
}
|
| 162 |
+
]
|
| 163 |
+
},
|
| 164 |
+
{
|
| 165 |
+
"type": "diagram_caption",
|
| 166 |
+
"text": "图4-31: 基于云计算架构的工业软件体系示意"
|
| 167 |
+
},
|
| 168 |
+
{
|
| 169 |
+
"type": "diagram",
|
| 170 |
+
"nodes": [
|
| 171 |
+
{
|
| 172 |
+
"id": "A",
|
| 173 |
+
"text": "场景化 SaaS( 基于模型 )"
|
| 174 |
+
},
|
| 175 |
+
{
|
| 176 |
+
"id": "B",
|
| 177 |
+
"text": "MBSE"
|
| 178 |
+
},
|
| 179 |
+
{
|
| 180 |
+
"id": "C",
|
| 181 |
+
"text": "MBDx"
|
| 182 |
+
},
|
| 183 |
+
{
|
| 184 |
+
"id": "D",
|
| 185 |
+
"text": "MBM"
|
| 186 |
+
},
|
| 187 |
+
{
|
| 188 |
+
"id": "E",
|
| 189 |
+
"text": "系统设计仿真云服务"
|
| 190 |
+
},
|
| 191 |
+
{
|
| 192 |
+
"id": "F",
|
| 193 |
+
"text": "板级 EDA 云服务"
|
| 194 |
+
},
|
| 195 |
+
{
|
| 196 |
+
"id": "G",
|
| 197 |
+
"text": "工业仿真云服务"
|
| 198 |
+
},
|
| 199 |
+
{
|
| 200 |
+
"id": "H",
|
| 201 |
+
"text": "设计制造融合云服务"
|
| 202 |
+
},
|
| 203 |
+
{
|
| 204 |
+
"id": "I",
|
| 205 |
+
"text": "aPaaS ( 工业根服务 )"
|
| 206 |
+
},
|
| 207 |
+
{
|
| 208 |
+
"id": "J",
|
| 209 |
+
"text": "工业经验的根(工业基础资源库)"
|
| 210 |
+
},
|
| 211 |
+
{
|
| 212 |
+
"id": "K",
|
| 213 |
+
"text": "工业数据的根(工业数据管理平台)"
|
| 214 |
+
},
|
| 215 |
+
{
|
| 216 |
+
"id": "L",
|
| 217 |
+
"text": "工业软件的根(工业软件内核引擎)"
|
| 218 |
+
},
|
| 219 |
+
{
|
| 220 |
+
"id": "M",
|
| 221 |
+
"text": "工业智能的根(工业智能组件)"
|
| 222 |
+
},
|
| 223 |
+
{
|
| 224 |
+
"id": "N",
|
| 225 |
+
"text": "gPaaS"
|
| 226 |
+
},
|
| 227 |
+
{
|
| 228 |
+
"id": "O",
|
| 229 |
+
"text": "云"
|
| 230 |
+
},
|
| 231 |
+
{
|
| 232 |
+
"id": "P",
|
| 233 |
+
"text": "大数据"
|
| 234 |
+
},
|
| 235 |
+
{
|
| 236 |
+
"id": "Q",
|
| 237 |
+
"text": "AI"
|
| 238 |
+
},
|
| 239 |
+
{
|
| 240 |
+
"id": "R",
|
| 241 |
+
"text": "IaaS"
|
| 242 |
+
},
|
| 243 |
+
{
|
| 244 |
+
"id": "S",
|
| 245 |
+
"text": "工业软件开发运营中心"
|
| 246 |
+
},
|
| 247 |
+
{
|
| 248 |
+
"id": "T",
|
| 249 |
+
"text": "工业 SaaS 服务中心"
|
| 250 |
+
},
|
| 251 |
+
{
|
| 252 |
+
"id": "U",
|
| 253 |
+
"text": "工业软件 DevOps 工具链"
|
| 254 |
+
},
|
| 255 |
+
{
|
| 256 |
+
"id": "V",
|
| 257 |
+
"text": "工业云商店"
|
| 258 |
+
}
|
| 259 |
+
],
|
| 260 |
+
"relationships": [
|
| 261 |
+
{
|
| 262 |
+
"source": "A",
|
| 263 |
+
"target": "B"
|
| 264 |
+
},
|
| 265 |
+
{
|
| 266 |
+
"source": "A",
|
| 267 |
+
"target": "C"
|
| 268 |
+
},
|
| 269 |
+
{
|
| 270 |
+
"source": "A",
|
| 271 |
+
"target": "D"
|
| 272 |
+
},
|
| 273 |
+
{
|
| 274 |
+
"source": "B",
|
| 275 |
+
"target": "E"
|
| 276 |
+
},
|
| 277 |
+
{
|
| 278 |
+
"source": "C",
|
| 279 |
+
"target": "F"
|
| 280 |
+
},
|
| 281 |
+
{
|
| 282 |
+
"source": "C",
|
| 283 |
+
"target": "G"
|
| 284 |
+
},
|
| 285 |
+
{
|
| 286 |
+
"source": "D",
|
| 287 |
+
"target": "H"
|
| 288 |
+
},
|
| 289 |
+
{
|
| 290 |
+
"source": "I",
|
| 291 |
+
"target": "J"
|
| 292 |
+
},
|
| 293 |
+
{
|
| 294 |
+
"source": "I",
|
| 295 |
+
"target": "K"
|
| 296 |
+
},
|
| 297 |
+
{
|
| 298 |
+
"source": "I",
|
| 299 |
+
"target": "L"
|
| 300 |
+
},
|
| 301 |
+
{
|
| 302 |
+
"source": "I",
|
| 303 |
+
"target": "M"
|
| 304 |
+
},
|
| 305 |
+
{
|
| 306 |
+
"source": "N",
|
| 307 |
+
"target": "O"
|
| 308 |
+
},
|
| 309 |
+
{
|
| 310 |
+
"source": "N",
|
| 311 |
+
"target": "P"
|
| 312 |
+
},
|
| 313 |
+
{
|
| 314 |
+
"source": "N",
|
| 315 |
+
"target": "Q"
|
| 316 |
+
},
|
| 317 |
+
{
|
| 318 |
+
"source": "S",
|
| 319 |
+
"target": "T"
|
| 320 |
+
},
|
| 321 |
+
{
|
| 322 |
+
"source": "S",
|
| 323 |
+
"target": "U"
|
| 324 |
+
},
|
| 325 |
+
{
|
| 326 |
+
"source": "S",
|
| 327 |
+
"target": "V"
|
| 328 |
+
}
|
| 329 |
+
]
|
| 330 |
+
},
|
| 331 |
+
{
|
| 332 |
+
"type": "page_number",
|
| 333 |
+
"text": "58"
|
| 334 |
+
}
|
| 335 |
+
]
|
diagrams-and-tables/annotations/cn_diagram_30.json
ADDED
|
@@ -0,0 +1,149 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
[
|
| 2 |
+
{
|
| 3 |
+
"type": "header",
|
| 4 |
+
"text": "人工智能就绪度白皮书"
|
| 5 |
+
},
|
| 6 |
+
{
|
| 7 |
+
"type": "diagram_caption",
|
| 8 |
+
"text": "AI Ready硬实力变革分析框架"
|
| 9 |
+
},
|
| 10 |
+
{
|
| 11 |
+
"type": "diagram",
|
| 12 |
+
"nodes": [
|
| 13 |
+
{
|
| 14 |
+
"id": "A",
|
| 15 |
+
"text": "业务应用层"
|
| 16 |
+
},
|
| 17 |
+
{
|
| 18 |
+
"id": "B",
|
| 19 |
+
"text": "模型服务与编排层"
|
| 20 |
+
},
|
| 21 |
+
{
|
| 22 |
+
"id": "C",
|
| 23 |
+
"text": "基础设施层"
|
| 24 |
+
},
|
| 25 |
+
{
|
| 26 |
+
"id": "D",
|
| 27 |
+
"text": "服务治理层"
|
| 28 |
+
},
|
| 29 |
+
{
|
| 30 |
+
"id": "E",
|
| 31 |
+
"text": "产品与服务创新"
|
| 32 |
+
},
|
| 33 |
+
{
|
| 34 |
+
"id": "F",
|
| 35 |
+
"text": "交互式客户体验"
|
| 36 |
+
},
|
| 37 |
+
{
|
| 38 |
+
"id": "G",
|
| 39 |
+
"text": "智能洞察与决策"
|
| 40 |
+
},
|
| 41 |
+
{
|
| 42 |
+
"id": "H",
|
| 43 |
+
"text": "..."
|
| 44 |
+
},
|
| 45 |
+
{
|
| 46 |
+
"id": "I",
|
| 47 |
+
"text": "模型管理与服务化"
|
| 48 |
+
},
|
| 49 |
+
{
|
| 50 |
+
"id": "J",
|
| 51 |
+
"text": "智能体与应用编排"
|
| 52 |
+
},
|
| 53 |
+
{
|
| 54 |
+
"id": "K",
|
| 55 |
+
"text": "计算"
|
| 56 |
+
},
|
| 57 |
+
{
|
| 58 |
+
"id": "L",
|
| 59 |
+
"text": "网络"
|
| 60 |
+
},
|
| 61 |
+
{
|
| 62 |
+
"id": "M",
|
| 63 |
+
"text": "存储"
|
| 64 |
+
},
|
| 65 |
+
{
|
| 66 |
+
"id": "N",
|
| 67 |
+
"text": "数据"
|
| 68 |
+
},
|
| 69 |
+
{
|
| 70 |
+
"id": "O",
|
| 71 |
+
"text": "安全可信AI"
|
| 72 |
+
},
|
| 73 |
+
{
|
| 74 |
+
"id": "P",
|
| 75 |
+
"text": "AI全栈治理"
|
| 76 |
+
}
|
| 77 |
+
],
|
| 78 |
+
"relationships": [
|
| 79 |
+
{
|
| 80 |
+
"source": "A",
|
| 81 |
+
"target": "E"
|
| 82 |
+
},
|
| 83 |
+
{
|
| 84 |
+
"source": "A",
|
| 85 |
+
"target": "F"
|
| 86 |
+
},
|
| 87 |
+
{
|
| 88 |
+
"source": "A",
|
| 89 |
+
"target": "G"
|
| 90 |
+
},
|
| 91 |
+
{
|
| 92 |
+
"source": "A",
|
| 93 |
+
"target": "H"
|
| 94 |
+
},
|
| 95 |
+
{
|
| 96 |
+
"source": "B",
|
| 97 |
+
"target": "I"
|
| 98 |
+
},
|
| 99 |
+
{
|
| 100 |
+
"source": "B",
|
| 101 |
+
"target": "J"
|
| 102 |
+
},
|
| 103 |
+
{
|
| 104 |
+
"source": "C",
|
| 105 |
+
"target": "K"
|
| 106 |
+
},
|
| 107 |
+
{
|
| 108 |
+
"source": "C",
|
| 109 |
+
"target": "L"
|
| 110 |
+
},
|
| 111 |
+
{
|
| 112 |
+
"source": "C",
|
| 113 |
+
"target": "M"
|
| 114 |
+
},
|
| 115 |
+
{
|
| 116 |
+
"source": "C",
|
| 117 |
+
"target": "N"
|
| 118 |
+
},
|
| 119 |
+
{
|
| 120 |
+
"source": "D",
|
| 121 |
+
"target": "O"
|
| 122 |
+
},
|
| 123 |
+
{
|
| 124 |
+
"source": "D",
|
| 125 |
+
"target": "P"
|
| 126 |
+
}
|
| 127 |
+
]
|
| 128 |
+
},
|
| 129 |
+
{
|
| 130 |
+
"type": "text",
|
| 131 |
+
"text": "基础设施层是企业AI技术落地的物理与虚拟资源支撑体系,是承载AI模型训练、推理与部署的高可用性底座。它包含计算资源、网络架构、存储系统及数据语料等核心要素,为上层AI应用提供稳定、高效、可拓展的运行环境。"
|
| 132 |
+
},
|
| 133 |
+
{
|
| 134 |
+
"type": "text",
|
| 135 |
+
"text": "AI模型服务与编排层(AI Model Service and Orchestration Layer)是企业AI能力体系的中枢,扮演着承上启下的关键角色。它下接坚实的AI基础设施层(算力、网络、存储、数据),负责将底层资源与AI模型能力进行封装、管理与优化;上承多样化的业务应用场景,提供标准、高效、灵活的AI能力调用接口与智能编排服务。该层核心目标是屏蔽底层基础设施的复杂性,赋能上层应用的敏捷创新,确保企业能够高效、安全、可扩展地利用各类AI模型(包括基础大模型、行业模型、自研模型等)驱动业务价值。其关键要素包括多模型管理与服务化、智能体(Agent)与应用编排以及模型通信协议与集成。"
|
| 136 |
+
},
|
| 137 |
+
{
|
| 138 |
+
"type": "text",
|
| 139 |
+
"text": "服务治理层是保障企业AI系统合规、安全、可持续运行的安全防护和治理体系,涵盖安全可信AI和AI全栈治理两大支柱,旨在推动企业AI安全及治理从原则规范走向工程化落地。"
|
| 140 |
+
},
|
| 141 |
+
{
|
| 142 |
+
"type": "footer",
|
| 143 |
+
"text": "© 2025 毕马威华振会计师事务所(特殊普通合伙) — 中国合伙制会计师事务所,毕马威企业咨询(中国)有限公司 — 中国有限责任公司,毕马威会计师事务所 — 澳门特别行政区合伙制事务所,及毕马威会计师事务所 — 香港特别行政区合伙制事务所,均是与毕马威国际���限公司(英国私营担保有限公司)相关联的独立成员所全球组织中的成员。版权所有,不得转载。在中国印刷。"
|
| 144 |
+
},
|
| 145 |
+
{
|
| 146 |
+
"type": "page_number",
|
| 147 |
+
"text": "48"
|
| 148 |
+
}
|
| 149 |
+
]
|
diagrams-and-tables/annotations/cn_diagram_31.json
ADDED
|
@@ -0,0 +1,133 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
[
|
| 2 |
+
{
|
| 3 |
+
"type": "header",
|
| 4 |
+
"text": "毕马威银行业客户体验白皮书"
|
| 5 |
+
},
|
| 6 |
+
{
|
| 7 |
+
"type": "title",
|
| 8 |
+
"text": "任重道远\n客户体验已被赋予新的内涵,但调研发现银行体验现状仍存提升空间\n分析框架简介"
|
| 9 |
+
},
|
| 10 |
+
{
|
| 11 |
+
"type": "text",
|
| 12 |
+
"text": "我们的调研主要通过问卷的方式,并得到了京东科技的技术支持,在初步整理和分析问卷反馈结果后,我们发现,各类型银行的客户群体在银行各条线、渠道和场景的服务体验存在差异,不同类型银行客户的体验期望也不尽相同。客户体验管理在银行已经被赋予新的内涵,不仅仅是作为售后客户满意度的调查,而是延伸到售前、售中和售后等客户旅程的各个环节,作为产品设计、渠道建设、客户服务能力提升、系统优化等方面的重要输入,本次分析将目标银行按照不同类型(国有银行、股份制银行以及区域性银行)进行区分分别进行客户体验分析。本次调研主要分析银行的零售业务,包含厅堂服务、电子渠道、财富管理、信贷业务以及信用卡业务等业务条线和渠道维度的客户体验现状。除此之外,我们对以上调研项目将调研结果按照性别、银行客户粘性进行区分,在本文中,若客户在该银行的资产占家庭资产的 50% 以上,我们将该银行定义为客户的主办银行,具有较强的客户粘性,下文简称为主办行客户。若客户在该银行的资产占家庭资产的 50% 以下,我们将该银行定义为客户的使用银行,下文简称为使用行客户。"
|
| 13 |
+
},
|
| 14 |
+
{
|
| 15 |
+
"type": "diagram",
|
| 16 |
+
"nodes": [
|
| 17 |
+
{
|
| 18 |
+
"id": "A",
|
| 19 |
+
"text": "银行业客户体验"
|
| 20 |
+
},
|
| 21 |
+
{
|
| 22 |
+
"id": "B",
|
| 23 |
+
"text": "国有银行"
|
| 24 |
+
},
|
| 25 |
+
{
|
| 26 |
+
"id": "C",
|
| 27 |
+
"text": "股份制银行"
|
| 28 |
+
},
|
| 29 |
+
{
|
| 30 |
+
"id": "D",
|
| 31 |
+
"text": "区域性银行"
|
| 32 |
+
},
|
| 33 |
+
{
|
| 34 |
+
"id": "E",
|
| 35 |
+
"text": "业务种类"
|
| 36 |
+
},
|
| 37 |
+
{
|
| 38 |
+
"id": "F",
|
| 39 |
+
"text": "厅堂服务"
|
| 40 |
+
},
|
| 41 |
+
{
|
| 42 |
+
"id": "G",
|
| 43 |
+
"text": "电子渠道"
|
| 44 |
+
},
|
| 45 |
+
{
|
| 46 |
+
"id": "H",
|
| 47 |
+
"text": "财富管理"
|
| 48 |
+
},
|
| 49 |
+
{
|
| 50 |
+
"id": "I",
|
| 51 |
+
"text": "信贷业务"
|
| 52 |
+
},
|
| 53 |
+
{
|
| 54 |
+
"id": "J",
|
| 55 |
+
"text": "信用卡业务"
|
| 56 |
+
},
|
| 57 |
+
{
|
| 58 |
+
"id": "K",
|
| 59 |
+
"text": "•银行客户性别评估:评估各大银行种类客户中,男女性客户体验的异同。"
|
| 60 |
+
},
|
| 61 |
+
{
|
| 62 |
+
"id": "L",
|
| 63 |
+
"text": "•银行客户粘性评估:评估各大银行种类客户中,忠实客户与普通客户体验的异同。"
|
| 64 |
+
}
|
| 65 |
+
],
|
| 66 |
+
"relationships": [
|
| 67 |
+
{
|
| 68 |
+
"source": "A",
|
| 69 |
+
"target": "B"
|
| 70 |
+
},
|
| 71 |
+
{
|
| 72 |
+
"source": "A",
|
| 73 |
+
"target": "C"
|
| 74 |
+
},
|
| 75 |
+
{
|
| 76 |
+
"source": "A",
|
| 77 |
+
"target": "D"
|
| 78 |
+
},
|
| 79 |
+
{
|
| 80 |
+
"source": "B",
|
| 81 |
+
"target": "E"
|
| 82 |
+
},
|
| 83 |
+
{
|
| 84 |
+
"source": "C",
|
| 85 |
+
"target": "E"
|
| 86 |
+
},
|
| 87 |
+
{
|
| 88 |
+
"source": "D",
|
| 89 |
+
"target": "E"
|
| 90 |
+
},
|
| 91 |
+
{
|
| 92 |
+
"source": "E",
|
| 93 |
+
"target": "F"
|
| 94 |
+
},
|
| 95 |
+
{
|
| 96 |
+
"source": "E",
|
| 97 |
+
"target": "G"
|
| 98 |
+
},
|
| 99 |
+
{
|
| 100 |
+
"source": "E",
|
| 101 |
+
"target": "H"
|
| 102 |
+
},
|
| 103 |
+
{
|
| 104 |
+
"source": "E",
|
| 105 |
+
"target": "I"
|
| 106 |
+
},
|
| 107 |
+
{
|
| 108 |
+
"source": "E",
|
| 109 |
+
"target": "J"
|
| 110 |
+
}
|
| 111 |
+
]
|
| 112 |
+
},
|
| 113 |
+
{
|
| 114 |
+
"type": "text",
|
| 115 |
+
"text": "我们从调研中总结出影响国有银行、股份制银行与区域性银行客户体验的重要因素,并对可能的原因进行了分析。"
|
| 116 |
+
},
|
| 117 |
+
{
|
| 118 |
+
"type": "title",
|
| 119 |
+
"text": "1、影响银行业整体客户体验关键因素摘要"
|
| 120 |
+
},
|
| 121 |
+
{
|
| 122 |
+
"type": "text",
|
| 123 |
+
"text": "本次调研中,为洞悉影响银行整体客户体验的主要影响因素,我们主要从银行产品(产品好、选择范围广、到期收益高)、银行服务(服务好、业务专业、过程体验佳)、银行提供的权益(权益好、提供其"
|
| 124 |
+
},
|
| 125 |
+
{
|
| 126 |
+
"type": "page_number",
|
| 127 |
+
"text": "19"
|
| 128 |
+
},
|
| 129 |
+
{
|
| 130 |
+
"type": "footer",
|
| 131 |
+
"text": "© 2023 毕马威企业咨询(中国)有限公司 — 中国有限责任公司,是与英国私营担保有限公司 — 毕马威国际有限公司相关联的独立成员所全球性组织中的成员。版权所有,不得转载。在中国印刷。毕马威的名称和标识均为毕马威全球性组织中的独立成员所经许可后使用的商标。"
|
| 132 |
+
}
|
| 133 |
+
]
|
diagrams-and-tables/annotations/cn_diagram_32.json
ADDED
|
@@ -0,0 +1,89 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
[
|
| 2 |
+
{
|
| 3 |
+
"type": "header",
|
| 4 |
+
"text": "毕马威银行业客户体验白皮书"
|
| 5 |
+
},
|
| 6 |
+
{
|
| 7 |
+
"type": "text",
|
| 8 |
+
"text": "开始对网点进行全面的智能化改造,5 年时间,网点内部完成两次升级改造,网点内部布局领先与同行业其他银行。但股份制银行的网点劣势在于数量相对较少,相较国有银行的网点密集度,股份制银行网点布局稀疏,且大量集中于城区,客户前往银行的网点不便。虽然股份制银行利用数字化、科技化手段拓宽了银行业务办理渠道,增加了网点的辐射半径,但在中国消费者客户意识中,网点仍然是银行品牌的主要显性载体,网点仍然是银行开展业务的主战场。因此,股份制银行需考虑在现有网点数量下,如何优化网点布局,让客户体验网点方便快捷的服务。\n\n国有银行网点数量多,且银行数字化时间较早,网点内部智能设备多,相较其他两类银行,网点布局与环境较为均衡,客户认为网点不是国有银行最优先需要提升的维度,我们也观察到国有银行处于网点整体保持稳定、局部地区数量进行优化的阶段。"
|
| 9 |
+
},
|
| 10 |
+
{
|
| 11 |
+
"type": "title",
|
| 12 |
+
"text": "2.3 手机银行作为影响整体客户体验最重要的渠道,客户期望甚高"
|
| 13 |
+
},
|
| 14 |
+
{
|
| 15 |
+
"type": "text",
|
| 16 |
+
"text": "根据调研,手机银行的体验是影响客户对银行服务整体体验最重要的因素,完善手机银行功能,提升移动端用户体验是银行需要在未来需要持续重点投入以提升的方向。19% 的客户认为银行手机银行仍然需要继续优化,其中,27.7% 的国有银行客户认为银行需要优化手机银行界面设计、提升使用便利度,但对于将国有银行作为主办行的客户而言,他们倾向于依赖物理网点办理业务和进行咨询,反而对手机银行的重视程度不如其他银行的客户。在区域性银行客户中,男性客户更希望银行能够提升手机银行的功能和体验,说明男性客户更看中办理业务时的方便与快捷。和主办行客户相比,区域性银行的使用行客户更关注手机银行的体验,手机银行的体验是提升使用行客户体验的重要抓手。而对于股份制银行而言,手机银行功能更新速度快,相较其他类型的银行,界面、功能与使用体验均有优势,因此较少的客户认为股份制银行需要提升手机银行。"
|
| 17 |
+
},
|
| 18 |
+
{
|
| 19 |
+
"type": "title",
|
| 20 |
+
"text": "3、客户体验——厅堂服务篇"
|
| 21 |
+
},
|
| 22 |
+
{
|
| 23 |
+
"type": "title",
|
| 24 |
+
"text": "3.1 网点工作人员的服务态度是银行厅堂服务最重要的影响因素"
|
| 25 |
+
},
|
| 26 |
+
{
|
| 27 |
+
"type": "diagram_caption",
|
| 28 |
+
"text": "图 9:厅堂服务客户体验的影响因素"
|
| 29 |
+
},
|
| 30 |
+
{
|
| 31 |
+
"type": "diagram",
|
| 32 |
+
"nodes": [
|
| 33 |
+
{
|
| 34 |
+
"id": "A",
|
| 35 |
+
"text": "银行厅堂服务体验的影响因素"
|
| 36 |
+
},
|
| 37 |
+
{
|
| 38 |
+
"id": "B",
|
| 39 |
+
"text": "工作人员的服务态度和流程"
|
| 40 |
+
},
|
| 41 |
+
{
|
| 42 |
+
"id": "C",
|
| 43 |
+
"text": "厅堂内智能设备功能"
|
| 44 |
+
},
|
| 45 |
+
{
|
| 46 |
+
"id": "D",
|
| 47 |
+
"text": "网点提供的客户权益"
|
| 48 |
+
},
|
| 49 |
+
{
|
| 50 |
+
"id": "E",
|
| 51 |
+
"text": "厅堂环境和布置"
|
| 52 |
+
},
|
| 53 |
+
{
|
| 54 |
+
"id": "F",
|
| 55 |
+
"text": "厅堂内的人流和排队情况"
|
| 56 |
+
}
|
| 57 |
+
],
|
| 58 |
+
"relationships": [
|
| 59 |
+
{
|
| 60 |
+
"source": "A",
|
| 61 |
+
"target": "B"
|
| 62 |
+
},
|
| 63 |
+
{
|
| 64 |
+
"source": "A",
|
| 65 |
+
"target": "C"
|
| 66 |
+
},
|
| 67 |
+
{
|
| 68 |
+
"source": "A",
|
| 69 |
+
"target": "D"
|
| 70 |
+
},
|
| 71 |
+
{
|
| 72 |
+
"source": "A",
|
| 73 |
+
"target": "E"
|
| 74 |
+
},
|
| 75 |
+
{
|
| 76 |
+
"source": "A",
|
| 77 |
+
"target": "F"
|
| 78 |
+
}
|
| 79 |
+
]
|
| 80 |
+
},
|
| 81 |
+
{
|
| 82 |
+
"type": "page_number",
|
| 83 |
+
"text": "26"
|
| 84 |
+
},
|
| 85 |
+
{
|
| 86 |
+
"type": "footer",
|
| 87 |
+
"text": "© 2023 毕马威企业咨询(中国)有限公司 — 中国有限责任公司,是与英国私营担保有限公司 — 毕马威国际有限公司相关联的独立成员所全球性组织中的成员。版权所有,不得转载。在中国印刷。毕马威的名称和标识均为毕马威全球性组织中的独立成员所经许可后使用的商标。"
|
| 88 |
+
}
|
| 89 |
+
]
|
diagrams-and-tables/annotations/cn_diagram_33.json
ADDED
|
@@ -0,0 +1,193 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
[
|
| 2 |
+
{
|
| 3 |
+
"type": "header",
|
| 4 |
+
"text": "毕马威银行业客户体验白皮书"
|
| 5 |
+
},
|
| 6 |
+
{
|
| 7 |
+
"type": "text",
|
| 8 |
+
"text": "随着我国经济的高速发展,我国居民个人资产水平逐渐提高。其中,金融类资产的配置需求也不断增强,潜在的财富管理市场发展空间巨大。而对于银行而言,财富管理是轻资本业务,符合当下银行商业模式转型的方向,越来越多的银行将财富管理作为战略转型的重要板块。因此财富管理的客户体验逐渐受到各家银行的重视。本次调研数据显示,客户经理的专业程度、产品种类与产品收益率是财富管理板块影响客户体验的三大主要因素。其中,国有银行的客户更重视客户经理的专业程度,有 26.1% 的客户认为专业的客户经理是他们选择该行进行投资的重要原因。而对于股份制银行于区域性银行而言,产品的收益率是客户首要关注的因素,也是两类银行吸引客户的重要抓手。将各类银行深入分析后,各类客户的表现也不尽相同。\n\n虽然国有银行总体客户以客户经理的专业程度作为最重要的影响因素,但对于男性客户而言,产品的收益率情况是这些客户的第一关注点,占比达到 26.67%。由此可知,国有银行在对男性客户进行产品营销时,应以产品的收益率以及收益的保障情况入手,让客户迅速建立起对银行的信任。对于股份制银行的主办行客户而言,客户经理的专业程度反而是这类客户最关注的因素,客户占比达到了 39.24%。因股份制银行的主办行客户通常在过往的投资理财过程中,对该银行的产品收益与风险情况较为满意,产品已符合客户预期,因此客户经理能否为客户做好资产的合理配置,即成为了首要关注的因素。区域性银行的客户偏好基本与股份制银行一致,唯一不同的一点在于,部分客户认为客户经理的职业操守是影响财富管理体验的重要因素。相比国有银行和股份制银行,区域性银行的部分理财经理合规意识较弱,部分行为对客户的利益造成了损害,造成了区域性银行客户对银行信任度降低。"
|
| 9 |
+
},
|
| 10 |
+
{
|
| 11 |
+
"type": "title",
|
| 12 |
+
"text": "5.2 产品介绍的清晰度是线上理财体验最关键的影响因素之一,而理财经理的专业程度是影响线下网点理财体验的重要风向标"
|
| 13 |
+
},
|
| 14 |
+
{
|
| 15 |
+
"type": "diagram_caption",
|
| 16 |
+
"text": "图 19:银行 APP 与网点财富管理客户体验影响因素"
|
| 17 |
+
},
|
| 18 |
+
{
|
| 19 |
+
"type": "diagram",
|
| 20 |
+
"nodes": [
|
| 21 |
+
{
|
| 22 |
+
"id": "A",
|
| 23 |
+
"text": "APP 理财客户影响因素"
|
| 24 |
+
},
|
| 25 |
+
{
|
| 26 |
+
"id": "B",
|
| 27 |
+
"text": "能够及时通知投资状态"
|
| 28 |
+
},
|
| 29 |
+
{
|
| 30 |
+
"id": "C",
|
| 31 |
+
"text": "风险评估时给予建议和指引"
|
| 32 |
+
},
|
| 33 |
+
{
|
| 34 |
+
"id": "D",
|
| 35 |
+
"text": "产品信息条款介绍清晰易懂"
|
| 36 |
+
},
|
| 37 |
+
{
|
| 38 |
+
"id": "E",
|
| 39 |
+
"text": "产品挑选过程便捷"
|
| 40 |
+
},
|
| 41 |
+
{
|
| 42 |
+
"id": "F",
|
| 43 |
+
"text": "产品赎回很方便"
|
| 44 |
+
},
|
| 45 |
+
{
|
| 46 |
+
"id": "G",
|
| 47 |
+
"text": "功能齐全"
|
| 48 |
+
},
|
| 49 |
+
{
|
| 50 |
+
"id": "H",
|
| 51 |
+
"text": "交易扣款方便"
|
| 52 |
+
},
|
| 53 |
+
{
|
| 54 |
+
"id": "I",
|
| 55 |
+
"text": "收益查询和试算很方便"
|
| 56 |
+
},
|
| 57 |
+
{
|
| 58 |
+
"id": "J",
|
| 59 |
+
"text": "个性化推荐理财产品"
|
| 60 |
+
},
|
| 61 |
+
{
|
| 62 |
+
"id": "K",
|
| 63 |
+
"text": "风险测评方便快捷"
|
| 64 |
+
},
|
| 65 |
+
{
|
| 66 |
+
"id": "L",
|
| 67 |
+
"text": "推送理财知识"
|
| 68 |
+
},
|
| 69 |
+
{
|
| 70 |
+
"id": "M",
|
| 71 |
+
"text": "网点理财客户影响因素"
|
| 72 |
+
},
|
| 73 |
+
{
|
| 74 |
+
"id": "N",
|
| 75 |
+
"text": "专员投资理财指引简单易懂"
|
| 76 |
+
},
|
| 77 |
+
{
|
| 78 |
+
"id": "O",
|
| 79 |
+
"text": "专员耐心教导使用 APP"
|
| 80 |
+
},
|
| 81 |
+
{
|
| 82 |
+
"id": "P",
|
| 83 |
+
"text": "专员产品风险提示到位"
|
| 84 |
+
},
|
| 85 |
+
{
|
| 86 |
+
"id": "Q",
|
| 87 |
+
"text": "专员业务能力强很专业"
|
| 88 |
+
},
|
| 89 |
+
{
|
| 90 |
+
"id": "R",
|
| 91 |
+
"text": "专员推荐产品符合理财需求"
|
| 92 |
+
},
|
| 93 |
+
{
|
| 94 |
+
"id": "S",
|
| 95 |
+
"text": "专员解释产品简单明了"
|
| 96 |
+
},
|
| 97 |
+
{
|
| 98 |
+
"id": "T",
|
| 99 |
+
"text": "专员在风险评估时给予建议和指引"
|
| 100 |
+
},
|
| 101 |
+
{
|
| 102 |
+
"id": "U",
|
| 103 |
+
"text": "业务流程短填写资料少"
|
| 104 |
+
}
|
| 105 |
+
],
|
| 106 |
+
"relationships": [
|
| 107 |
+
{
|
| 108 |
+
"source": "A",
|
| 109 |
+
"target": "B"
|
| 110 |
+
},
|
| 111 |
+
{
|
| 112 |
+
"source": "A",
|
| 113 |
+
"target": "C"
|
| 114 |
+
},
|
| 115 |
+
{
|
| 116 |
+
"source": "A",
|
| 117 |
+
"target": "D"
|
| 118 |
+
},
|
| 119 |
+
{
|
| 120 |
+
"source": "A",
|
| 121 |
+
"target": "E"
|
| 122 |
+
},
|
| 123 |
+
{
|
| 124 |
+
"source": "A",
|
| 125 |
+
"target": "F"
|
| 126 |
+
},
|
| 127 |
+
{
|
| 128 |
+
"source": "A",
|
| 129 |
+
"target": "G"
|
| 130 |
+
},
|
| 131 |
+
{
|
| 132 |
+
"source": "A",
|
| 133 |
+
"target": "H"
|
| 134 |
+
},
|
| 135 |
+
{
|
| 136 |
+
"source": "A",
|
| 137 |
+
"target": "I"
|
| 138 |
+
},
|
| 139 |
+
{
|
| 140 |
+
"source": "A",
|
| 141 |
+
"target": "J"
|
| 142 |
+
},
|
| 143 |
+
{
|
| 144 |
+
"source": "A",
|
| 145 |
+
"target": "K"
|
| 146 |
+
},
|
| 147 |
+
{
|
| 148 |
+
"source": "A",
|
| 149 |
+
"target": "L"
|
| 150 |
+
},
|
| 151 |
+
{
|
| 152 |
+
"source": "M",
|
| 153 |
+
"target": "N"
|
| 154 |
+
},
|
| 155 |
+
{
|
| 156 |
+
"source": "M",
|
| 157 |
+
"target": "O"
|
| 158 |
+
},
|
| 159 |
+
{
|
| 160 |
+
"source": "M",
|
| 161 |
+
"target": "P"
|
| 162 |
+
},
|
| 163 |
+
{
|
| 164 |
+
"source": "M",
|
| 165 |
+
"target": "Q"
|
| 166 |
+
},
|
| 167 |
+
{
|
| 168 |
+
"source": "M",
|
| 169 |
+
"target": "R"
|
| 170 |
+
},
|
| 171 |
+
{
|
| 172 |
+
"source": "M",
|
| 173 |
+
"target": "S"
|
| 174 |
+
},
|
| 175 |
+
{
|
| 176 |
+
"source": "M",
|
| 177 |
+
"target": "T"
|
| 178 |
+
},
|
| 179 |
+
{
|
| 180 |
+
"source": "M",
|
| 181 |
+
"target": "U"
|
| 182 |
+
}
|
| 183 |
+
]
|
| 184 |
+
},
|
| 185 |
+
{
|
| 186 |
+
"type": "page_number",
|
| 187 |
+
"text": "36"
|
| 188 |
+
},
|
| 189 |
+
{
|
| 190 |
+
"type": "footer",
|
| 191 |
+
"text": "© 2023 毕马威企业咨询(中国)有限公司 — 中国有限责任公司,是与英国私营担保有限公司 — 毕马威国际有限公司相关联的独立成员所全球性组织中的成员。版权所有,不得转载。在中国印刷。毕马威的名称和标识均为毕马威全球性组织中的独立成员所经许可后使用的商标。"
|
| 192 |
+
}
|
| 193 |
+
]
|
diagrams-and-tables/annotations/cn_diagram_34.json
ADDED
|
@@ -0,0 +1,81 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
[
|
| 2 |
+
{
|
| 3 |
+
"type": "header",
|
| 4 |
+
"text": "毕马威银行业客户体验白皮书"
|
| 5 |
+
},
|
| 6 |
+
{
|
| 7 |
+
"type": "text",
|
| 8 |
+
"text": "APP 理财的关键因素包括能够及时通知投资状态、风险评估时给予建议和指引、产品信息、条款介绍清晰易懂、产品挑选过程便捷、产品赎回很方便、功能齐全、交易扣款方便、收益查询和试算很方便、风险测评方便快捷、个性化推荐理财产品、推送理财知识等因素。\n\n网点理财体验的关键因素包括专员投资理财指引简单易懂、专员耐心教导使用 APP,专员产品风险提示到位,专员业务能力强、很专业,专员推荐产品符合理财需求,专员解释产品简单明了,专员在风险评估时给予建议和指引,业务流程短、填写资料少。\n\n本次调研中,我们对在 APP 上与网点内购买理财的客户体验影响因素进行了调研分析。数据显示,在 APP 上购买理财的客户更关注产品条款的清晰程度。26.1% 国有银行客户与 27.5% 股份制银行客户认为,产品信息与条款介绍是否清晰易懂,是影响他们选择 APP 进行理财的关键因素,而选择该选项的区域性银行客户的比例更高,达到 59.5%。因客户在线上挑选理财产品时,无法即时与专业的理财经理沟通产品信息,因此对产品收益与风险清晰说明,是客户获得信息的最重要渠道。另外,客户还希望在 APP 购买理财时,银行能够提供便捷的产品挑选流程。20.3% 的国有银行客户与 31.25% 的股份制银行客户选择产品挑选过程的便捷性是决定他们使用 APP 理财的关键因素,使用线上渠道购买理财时,客户已需要处理大量的、复杂的产品信息,繁琐的 APP 操作无疑会消耗客户仅存的耐心,极大的降低客户体验。同时,线上理财的状态通知的及时性,也是客户关注的重要因素,23.2% 的国有银行客户与 38.13% 的股份制银行客户,期望银行能够及时更新通知投资状态。在缺少银行工作人员的情形下,部分客户会滋生缺乏安全感的情绪,对投资状态通知的及时性,会减轻客户担忧的情绪,增加客户对银行的信任感。\n\n影响客户在网点购买理财最关键的因素是理财经理的专业程度。调研发现,47.8% 的国有银行客户、26.9% 的股份制银行客户以及 73% 的区域性银行客户均认为理财经理的业务能力是影响他们在网点理财体验的关键因素。相较于线上,网点理财的最大优势即是理财经理能够与客户面对面进行服务。通过与客户的当面交谈,理财经理能够更深入的了解客户的基本情况与需求,为客户进行专业、个性化的资产配置建议,赢得客户的信任。"
|
| 9 |
+
},
|
| 10 |
+
{
|
| 11 |
+
"type": "title",
|
| 12 |
+
"text": "5.3 随着产品同质化水平越来越高,提升财富客户满意度的难度日益增加,银行需要从产品到服务等多方面发力"
|
| 13 |
+
},
|
| 14 |
+
{
|
| 15 |
+
"type": "text",
|
| 16 |
+
"text": "基于影响财富客户体验的重要影响因素,从硬性的产品竞争力,到软性的银行服务以及业务办理流程,我们归纳了五条银行财富管理业务的发展路径,并对客户进行调研,对发展路径的重要性进行识别。"
|
| 17 |
+
},
|
| 18 |
+
{
|
| 19 |
+
"type": "diagram_caption",
|
| 20 |
+
"text": "图 20:银行财富管理客户体验提升方向"
|
| 21 |
+
},
|
| 22 |
+
{
|
| 23 |
+
"type": "diagram",
|
| 24 |
+
"nodes": [
|
| 25 |
+
{
|
| 26 |
+
"id": "A",
|
| 27 |
+
"text": "财富管理提升方向"
|
| 28 |
+
},
|
| 29 |
+
{
|
| 30 |
+
"id": "B",
|
| 31 |
+
"text": "产品竞争力"
|
| 32 |
+
},
|
| 33 |
+
{
|
| 34 |
+
"id": "C",
|
| 35 |
+
"text": "对客户诚信度"
|
| 36 |
+
},
|
| 37 |
+
{
|
| 38 |
+
"id": "D",
|
| 39 |
+
"text": "产品赎回便利度"
|
| 40 |
+
},
|
| 41 |
+
{
|
| 42 |
+
"id": "E",
|
| 43 |
+
"text": "办理渠道多样化"
|
| 44 |
+
},
|
| 45 |
+
{
|
| 46 |
+
"id": "F",
|
| 47 |
+
"text": "客户理财服务体验"
|
| 48 |
+
}
|
| 49 |
+
],
|
| 50 |
+
"relationships": [
|
| 51 |
+
{
|
| 52 |
+
"source": "A",
|
| 53 |
+
"target": "B"
|
| 54 |
+
},
|
| 55 |
+
{
|
| 56 |
+
"source": "A",
|
| 57 |
+
"target": "C"
|
| 58 |
+
},
|
| 59 |
+
{
|
| 60 |
+
"source": "A",
|
| 61 |
+
"target": "D"
|
| 62 |
+
},
|
| 63 |
+
{
|
| 64 |
+
"source": "A",
|
| 65 |
+
"target": "E"
|
| 66 |
+
},
|
| 67 |
+
{
|
| 68 |
+
"source": "A",
|
| 69 |
+
"target": "F"
|
| 70 |
+
}
|
| 71 |
+
]
|
| 72 |
+
},
|
| 73 |
+
{
|
| 74 |
+
"type": "page_number",
|
| 75 |
+
"text": "37"
|
| 76 |
+
},
|
| 77 |
+
{
|
| 78 |
+
"type": "footer",
|
| 79 |
+
"text": "© 2023 毕马威企业咨询(中国)有限公司 — 中国有限责任公司,是与英国私营担保有限公司 — 毕马威��际有限公司相关联的独立成员所全球性组织中的成员。版权所有,不得转载。在中国印刷。毕马威的名称和标识均为毕马威全球性组织中的独立成员所经许可后使用的商标。"
|
| 80 |
+
}
|
| 81 |
+
]
|
diagrams-and-tables/annotations/cn_diagram_35.json
ADDED
|
@@ -0,0 +1,141 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
[
|
| 2 |
+
{
|
| 3 |
+
"type": "title",
|
| 4 |
+
"text": "1. 现制茶饮的发展与消费现状分析"
|
| 5 |
+
},
|
| 6 |
+
{
|
| 7 |
+
"type": "text",
|
| 8 |
+
"text": "现制茶饮由商家在店铺内依据消费者个性化需求现场制作、调配并销售,以“现做现卖,即产即饮”为突出特点,工艺简单,生产快捷,可以较大限度的保留食材营养成分,减少食品生产添加剂的使用。最初期的现制茶饮产品多以奶精等勾兑为主,多在档口或街边小店销售,随后逐渐历经了品类的丰富和品牌的打造,形成了如今产品种类细分、食材原料丰富、品牌定位明晰和产品知名度提升的发展新阶段。"
|
| 9 |
+
},
|
| 10 |
+
{
|
| 11 |
+
"type": "diagram_caption",
|
| 12 |
+
"text": "图 1-1 现制茶饮的发展历程$^{[1]}$"
|
| 13 |
+
},
|
| 14 |
+
{
|
| 15 |
+
"type": "diagram",
|
| 16 |
+
"nodes": [
|
| 17 |
+
{
|
| 18 |
+
"id": "A",
|
| 19 |
+
"text": "茶饮品类"
|
| 20 |
+
},
|
| 21 |
+
{
|
| 22 |
+
"id": "B",
|
| 23 |
+
"text": "1.0时代"
|
| 24 |
+
},
|
| 25 |
+
{
|
| 26 |
+
"id": "C",
|
| 27 |
+
"text": "2.0时代"
|
| 28 |
+
},
|
| 29 |
+
{
|
| 30 |
+
"id": "D",
|
| 31 |
+
"text": "3.0时代"
|
| 32 |
+
},
|
| 33 |
+
{
|
| 34 |
+
"id": "E",
|
| 35 |
+
"text": "4.0时代"
|
| 36 |
+
},
|
| 37 |
+
{
|
| 38 |
+
"id": "F",
|
| 39 |
+
"text": "粉末阶段\n(1995年以前)"
|
| 40 |
+
},
|
| 41 |
+
{
|
| 42 |
+
"id": "G",
|
| 43 |
+
"text": "➢ 产品以奶精勾兑的珍珠奶茶为主\n➢ 以街边小店或者档口店为主,品牌意识较低"
|
| 44 |
+
},
|
| 45 |
+
{
|
| 46 |
+
"id": "H",
|
| 47 |
+
"text": "街头阶段\n(1995—2015年)"
|
| 48 |
+
},
|
| 49 |
+
{
|
| 50 |
+
"id": "I",
|
| 51 |
+
"text": "➢ 产品以牛奶和茶叶冲泡的奶茶为主,部分品牌推出水果茶和气泡茶\n➢ 品牌开始公司化运作。门店以街边店为主,商场、写字楼等选址开始受到关注"
|
| 52 |
+
},
|
| 53 |
+
{
|
| 54 |
+
"id": "J",
|
| 55 |
+
"text": "新式茶饮阶段\n(2016—2023年)"
|
| 56 |
+
},
|
| 57 |
+
{
|
| 58 |
+
"id": "K",
|
| 59 |
+
"text": "➢ 产品种类丰富,有鲜果茶、乳茶、纯茶等\n➢ 品牌注重IP打造,产品研发能力、品牌知名度、门店标准化程度大幅提升"
|
| 60 |
+
},
|
| 61 |
+
{
|
| 62 |
+
"id": "L",
|
| 63 |
+
"text": "健康原叶鲜奶阶段\n(2023年至今)"
|
| 64 |
+
},
|
| 65 |
+
{
|
| 66 |
+
"id": "M",
|
| 67 |
+
"text": "➢ 产品种类更细分,食材原料更丰富,并强调真奶、真茶的健康属性\n➢ 品牌注重私域运营和数字化建设,并通过开放加盟、拓展海外市场等方式进一步攻占市场"
|
| 68 |
+
}
|
| 69 |
+
],
|
| 70 |
+
"relationships": [
|
| 71 |
+
{
|
| 72 |
+
"source": "A",
|
| 73 |
+
"target": "F"
|
| 74 |
+
},
|
| 75 |
+
{
|
| 76 |
+
"source": "A",
|
| 77 |
+
"target": "H"
|
| 78 |
+
},
|
| 79 |
+
{
|
| 80 |
+
"source": "A",
|
| 81 |
+
"target": "J"
|
| 82 |
+
},
|
| 83 |
+
{
|
| 84 |
+
"source": "A",
|
| 85 |
+
"target": "L"
|
| 86 |
+
},
|
| 87 |
+
{
|
| 88 |
+
"source": "B",
|
| 89 |
+
"target": "C"
|
| 90 |
+
},
|
| 91 |
+
{
|
| 92 |
+
"source": "B",
|
| 93 |
+
"target": "F"
|
| 94 |
+
},
|
| 95 |
+
{
|
| 96 |
+
"source": "C",
|
| 97 |
+
"target": "D"
|
| 98 |
+
},
|
| 99 |
+
{
|
| 100 |
+
"source": "C",
|
| 101 |
+
"target": "H"
|
| 102 |
+
},
|
| 103 |
+
{
|
| 104 |
+
"source": "D",
|
| 105 |
+
"target": "E"
|
| 106 |
+
},
|
| 107 |
+
{
|
| 108 |
+
"source": "D",
|
| 109 |
+
"target": "J"
|
| 110 |
+
},
|
| 111 |
+
{
|
| 112 |
+
"source": "E",
|
| 113 |
+
"target": "L"
|
| 114 |
+
},
|
| 115 |
+
{
|
| 116 |
+
"source": "F",
|
| 117 |
+
"target": "G"
|
| 118 |
+
},
|
| 119 |
+
{
|
| 120 |
+
"source": "H",
|
| 121 |
+
"target": "I"
|
| 122 |
+
},
|
| 123 |
+
{
|
| 124 |
+
"source": "J",
|
| 125 |
+
"target": "K"
|
| 126 |
+
},
|
| 127 |
+
{
|
| 128 |
+
"source": "L",
|
| 129 |
+
"target": "M"
|
| 130 |
+
}
|
| 131 |
+
]
|
| 132 |
+
},
|
| 133 |
+
{
|
| 134 |
+
"type": "text",
|
| 135 |
+
"text": "目前,现制茶饮和现磨咖啡是我国现制饮品市场的主要细分品类,其中以终端零售额计,现制茶饮是现制饮品市场中最大的细分品类,2023 年占现制饮品市场规模的约 50%,由 2018 年的 1085 亿元增加至 2023 年的 2585 亿元(人民币),预计到 2028 年将按照 17.3%的复合年增长率进一步增加至 5732 亿元。数据显示,截至 2023 年底,我国现制茶饮店总数已达约 46.4 万家,连锁现制茶饮店品牌数已达 2600 个。据测算 2024 年全国茶饮门店总数超过 66 万家$^{[1]}$,国民人均现制茶饮的年消费量预计从 2023 年的约 11 杯提升至 2028 年的约 26 杯,成为日常消费中重要的构成元素。"
|
| 136 |
+
},
|
| 137 |
+
{
|
| 138 |
+
"type": "page_number",
|
| 139 |
+
"text": "1"
|
| 140 |
+
}
|
| 141 |
+
]
|
diagrams-and-tables/annotations/cn_diagram_36.json
ADDED
|
@@ -0,0 +1,169 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
[
|
| 2 |
+
{
|
| 3 |
+
"type": "header",
|
| 4 |
+
"text": "第一章 工业网络的愿景"
|
| 5 |
+
},
|
| 6 |
+
{
|
| 7 |
+
"type": "title",
|
| 8 |
+
"text": "(一)工业网络的定义与范围"
|
| 9 |
+
},
|
| 10 |
+
{
|
| 11 |
+
"type": "text",
|
| 12 |
+
"text": "工业网络指工业企业生产经营活动中所使用的网络,是构建工业环境人、机、物全面互联的基础设施。通过满足企业生产、办公、安防、数据中心和云平台等设备连接和数据互通的功能需求,工业网络可以实现工业研发、设计、生产、销售、管理、服务等要素的互联,促进各种工业数据的充分流动和无缝集成。"
|
| 13 |
+
},
|
| 14 |
+
{
|
| 15 |
+
"type": "text",
|
| 16 |
+
"text": "工业网络由网络互联和数据互通两个层次组成$^{1}$。网络互联可实现要素间的泛在互联及数据传输;数据互通则通过数据和信息在各要素间、各系统间的无缝传递,使得异构系统在数据层面能相互“理解”,实现应用层面的互操作与信息集成。(图1-2:工业网络的范围)"
|
| 17 |
+
},
|
| 18 |
+
{
|
| 19 |
+
"type": "diagram_caption",
|
| 20 |
+
"text": "图1-2:工业网络的范围"
|
| 21 |
+
},
|
| 22 |
+
{
|
| 23 |
+
"type": "diagram",
|
| 24 |
+
"nodes": [
|
| 25 |
+
{
|
| 26 |
+
"id": "A",
|
| 27 |
+
"text": "数据互通"
|
| 28 |
+
},
|
| 29 |
+
{
|
| 30 |
+
"id": "B",
|
| 31 |
+
"text": "网络互联"
|
| 32 |
+
},
|
| 33 |
+
{
|
| 34 |
+
"id": "C",
|
| 35 |
+
"text": "信息模型"
|
| 36 |
+
},
|
| 37 |
+
{
|
| 38 |
+
"id": "D",
|
| 39 |
+
"text": "语义互操作"
|
| 40 |
+
},
|
| 41 |
+
{
|
| 42 |
+
"id": "E",
|
| 43 |
+
"text": "应用层通信"
|
| 44 |
+
},
|
| 45 |
+
{
|
| 46 |
+
"id": "F",
|
| 47 |
+
"text": "工厂外网"
|
| 48 |
+
},
|
| 49 |
+
{
|
| 50 |
+
"id": "G",
|
| 51 |
+
"text": "工厂内网"
|
| 52 |
+
},
|
| 53 |
+
{
|
| 54 |
+
"id": "H",
|
| 55 |
+
"text": "公网"
|
| 56 |
+
},
|
| 57 |
+
{
|
| 58 |
+
"id": "I",
|
| 59 |
+
"text": "专网(物理隔离/虚拟)"
|
| 60 |
+
},
|
| 61 |
+
{
|
| 62 |
+
"id": "J",
|
| 63 |
+
"text": "生产网络"
|
| 64 |
+
},
|
| 65 |
+
{
|
| 66 |
+
"id": "K",
|
| 67 |
+
"text": "办公网络"
|
| 68 |
+
},
|
| 69 |
+
{
|
| 70 |
+
"id": "L",
|
| 71 |
+
"text": "安防网络"
|
| 72 |
+
},
|
| 73 |
+
{
|
| 74 |
+
"id": "M",
|
| 75 |
+
"text": "IT网"
|
| 76 |
+
},
|
| 77 |
+
{
|
| 78 |
+
"id": "N",
|
| 79 |
+
"text": "OT网"
|
| 80 |
+
},
|
| 81 |
+
{
|
| 82 |
+
"id": "O",
|
| 83 |
+
"text": "工厂级"
|
| 84 |
+
},
|
| 85 |
+
{
|
| 86 |
+
"id": "P",
|
| 87 |
+
"text": "车间级"
|
| 88 |
+
},
|
| 89 |
+
{
|
| 90 |
+
"id": "Q",
|
| 91 |
+
"text": "现场级"
|
| 92 |
+
}
|
| 93 |
+
],
|
| 94 |
+
"relationships": [
|
| 95 |
+
{
|
| 96 |
+
"source": "A",
|
| 97 |
+
"target": "C"
|
| 98 |
+
},
|
| 99 |
+
{
|
| 100 |
+
"source": "A",
|
| 101 |
+
"target": "D"
|
| 102 |
+
},
|
| 103 |
+
{
|
| 104 |
+
"source": "A",
|
| 105 |
+
"target": "E"
|
| 106 |
+
},
|
| 107 |
+
{
|
| 108 |
+
"source": "B",
|
| 109 |
+
"target": "F"
|
| 110 |
+
},
|
| 111 |
+
{
|
| 112 |
+
"source": "B",
|
| 113 |
+
"target": "G"
|
| 114 |
+
},
|
| 115 |
+
{
|
| 116 |
+
"source": "F",
|
| 117 |
+
"target": "H"
|
| 118 |
+
},
|
| 119 |
+
{
|
| 120 |
+
"source": "F",
|
| 121 |
+
"target": "I"
|
| 122 |
+
},
|
| 123 |
+
{
|
| 124 |
+
"source": "G",
|
| 125 |
+
"target": "J"
|
| 126 |
+
},
|
| 127 |
+
{
|
| 128 |
+
"source": "G",
|
| 129 |
+
"target": "K"
|
| 130 |
+
},
|
| 131 |
+
{
|
| 132 |
+
"source": "G",
|
| 133 |
+
"target": "L"
|
| 134 |
+
},
|
| 135 |
+
{
|
| 136 |
+
"source": "J",
|
| 137 |
+
"target": "M"
|
| 138 |
+
},
|
| 139 |
+
{
|
| 140 |
+
"source": "J",
|
| 141 |
+
"target": "N"
|
| 142 |
+
},
|
| 143 |
+
{
|
| 144 |
+
"source": "M",
|
| 145 |
+
"target": "O"
|
| 146 |
+
},
|
| 147 |
+
{
|
| 148 |
+
"source": "N",
|
| 149 |
+
"target": "P"
|
| 150 |
+
},
|
| 151 |
+
{
|
| 152 |
+
"source": "N",
|
| 153 |
+
"target": "Q"
|
| 154 |
+
}
|
| 155 |
+
]
|
| 156 |
+
},
|
| 157 |
+
{
|
| 158 |
+
"type": "text",
|
| 159 |
+
"text": "网络互联方面,工业网络分为工厂内网和工厂外网,两者逻辑上相互隔离,通过网关、防火墙、网闸等方式连通。\n• 工厂内网包含生产网络、办公网络和安防网络等,用于生产要素互联以及企业IT管理系统间连接。其中,生产网络作为内网的核心构成部分,呈现出IT网络 (Information Technology, 信息技术) 和OT网络 (Operation Technology, 操作技术) 分层,工厂级、车间级和现场级分段的“两层���级”架构:IT网络主要由 IP 网络构成,服务于工厂级的通信;OT网络主要用于连接生产现场的控制器以及传感器、伺服器、监测设备等,服务于车间级、现场级的通信,对可靠性和确定性具有更高要求。\n• 工厂外网包含公网和专网,是以支撑工业企业全生命周期各项活动为目的,用于连接企业上下游、企业总部与分支机构、企业与云业务、企业与智能产品、企业与用户之间的网络$^{2}$。工厂外网通过各种形式的公网或专网实现互联,承担供应链上下游信息流动,数据跨园区、跨系统流动等功能。"
|
| 160 |
+
},
|
| 161 |
+
{
|
| 162 |
+
"type": "footer",
|
| 163 |
+
"text": "1 根据工业互联网产业联盟《工业互联网网络连接白皮书(2.0版)》,工业互联网功能架构主要由网络互联、数据互通、标识解析三大模块组成。标识解析不属于本报告研究范畴\n2 工厂内网和工厂外网定义参考工业互联网产业联盟2018年9月发布的《工业互联网网络连接白皮书》和2021年9月发布的《工业互联网网络连接白皮书(2.0版)》"
|
| 164 |
+
},
|
| 165 |
+
{
|
| 166 |
+
"type": "page_number",
|
| 167 |
+
"text": "15"
|
| 168 |
+
}
|
| 169 |
+
]
|
diagrams-and-tables/annotations/cn_diagram_37.json
ADDED
|
@@ -0,0 +1,149 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
[
|
| 2 |
+
{
|
| 3 |
+
"type": "header",
|
| 4 |
+
"text": "迈向智能世界:工业网络全连接"
|
| 5 |
+
},
|
| 6 |
+
{
|
| 7 |
+
"type": "text",
|
| 8 |
+
"text": "吞吐能力,让10Gbps 无处不在。SPE将从基于IEEE802.3cg的先进物理层技术APL演进到增强型EPL(Enhanced Physical Layer)。"
|
| 9 |
+
},
|
| 10 |
+
{
|
| 11 |
+
"type": "title",
|
| 12 |
+
"text": "(三)发展建议"
|
| 13 |
+
},
|
| 14 |
+
{
|
| 15 |
+
"type": "text",
|
| 16 |
+
"text": "固本强基,网络先行。在此,我们倡议广大工业企业从实际业务需求出发,以适度超前、经济适配作为大原则,在建网、用网、管网和护网的全生命周期环节进行积极应对和响应。"
|
| 17 |
+
},
|
| 18 |
+
{
|
| 19 |
+
"type": "text",
|
| 20 |
+
"text": "• 适度超前:切忌短视、急于求成、过于追求短期回报,而是应该将网络作为面向长期的基础设施,为未来5-10年制造升级预留一定冗余空间;\n• 经济适配:无需盲目追求最佳性能参数,而是针对性选取最合适、经济好用的网络技术,实现投资回报最优。(图4-6:对工业企业的发展建议)"
|
| 21 |
+
},
|
| 22 |
+
{
|
| 23 |
+
"type": "text",
|
| 24 |
+
"text": "建网方面,工业企业应站在全局视角,从顶层制定与业务活动相适配的网络规划,统筹考量IT与OT网,统一网络建设规范,打造面向未来、适度超前、IT与OT融合的“一体化”网络架构。"
|
| 25 |
+
},
|
| 26 |
+
{
|
| 27 |
+
"type": "text",
|
| 28 |
+
"text": "• 确立IT与OT融合发展观念:夯实工业网络作为基础设施的地位,改变IT与OT割裂、“数字化是IT的事”等错误认知,建立IT和OT融合的全局观,凝练共识、拉齐行动,把握工业网络发展主动权;\n• 探索建立IT与OT融合团队:传统工业企业中,IT系统和OT系统由不同团队建设管理,IT部门只关注IT、业务部门只关注OT,导致系统间数据传递与价值挖掘的不顺畅。工业企业要坚定决心打通IT和OT间的“墙”,考虑成立IT-OT融合团队,建立扁平、灵活化的协同工作机制,凝聚共识、共同推动IT与OT融合的落地实践$^{[46]}$;"
|
| 29 |
+
},
|
| 30 |
+
{
|
| 31 |
+
"type": "diagram_caption",
|
| 32 |
+
"text": "图4-6:对工业企业的发展建议"
|
| 33 |
+
},
|
| 34 |
+
{
|
| 35 |
+
"type": "diagram",
|
| 36 |
+
"nodes": [
|
| 37 |
+
{
|
| 38 |
+
"id": "A",
|
| 39 |
+
"text": "大原则"
|
| 40 |
+
},
|
| 41 |
+
{
|
| 42 |
+
"id": "B",
|
| 43 |
+
"text": "关键行动方向"
|
| 44 |
+
},
|
| 45 |
+
{
|
| 46 |
+
"id": "C",
|
| 47 |
+
"text": "适度超前"
|
| 48 |
+
},
|
| 49 |
+
{
|
| 50 |
+
"id": "D",
|
| 51 |
+
"text": "经济适配"
|
| 52 |
+
},
|
| 53 |
+
{
|
| 54 |
+
"id": "E",
|
| 55 |
+
"text": "建网"
|
| 56 |
+
},
|
| 57 |
+
{
|
| 58 |
+
"id": "F",
|
| 59 |
+
"text": "联网"
|
| 60 |
+
},
|
| 61 |
+
{
|
| 62 |
+
"id": "G",
|
| 63 |
+
"text": "用网"
|
| 64 |
+
},
|
| 65 |
+
{
|
| 66 |
+
"id": "H",
|
| 67 |
+
"text": "护网"
|
| 68 |
+
},
|
| 69 |
+
{
|
| 70 |
+
"id": "I",
|
| 71 |
+
"text": "建立IT和OT融合的全局观念,探索建立IT与OT的融合团队,凝练共识、拉齐行动<br/>基于融合化的网络架构,探索一网多能、一网多用,推动多业务的共网融合承载,并以开放态度拥抱新技术"
|
| 72 |
+
},
|
| 73 |
+
{
|
| 74 |
+
"id": "J",
|
| 75 |
+
"text": "存量工厂依据业务场景和约束条件,积极开展“哑设备”的联网化<br/>改造新建工厂可考虑IP到终端(IP到底)的一步到位,优先使用开放、兼容的应用层协议,让设备统一语言,都说“普通话”"
|
| 76 |
+
},
|
| 77 |
+
{
|
| 78 |
+
"id": "K",
|
| 79 |
+
"text": "观念上,明确“没有最好的技术,只有最合适的技术”,立足于场景需求,权衡技术性能和成本投入,追求最佳性价比<br/>选配上,积极拥抱无线化趋势,探索极简灵活的网络,实现“化繁为简”"
|
| 80 |
+
},
|
| 81 |
+
{
|
| 82 |
+
"id": "L",
|
| 83 |
+
"text": "探索网络数字孪生、网络数字地图等技术,实现网络的智能、自主,为网络的日常配置、调试、运维减负<br/>构建“非侵入式”安全架构,将网络和安全视为互为依存的整体,构筑韧性保障"
|
| 84 |
+
}
|
| 85 |
+
],
|
| 86 |
+
"relationships": [
|
| 87 |
+
{
|
| 88 |
+
"source": "A",
|
| 89 |
+
"target": "C"
|
| 90 |
+
},
|
| 91 |
+
{
|
| 92 |
+
"source": "A",
|
| 93 |
+
"target": "D"
|
| 94 |
+
},
|
| 95 |
+
{
|
| 96 |
+
"source": "B",
|
| 97 |
+
"target": "I"
|
| 98 |
+
},
|
| 99 |
+
{
|
| 100 |
+
"source": "B",
|
| 101 |
+
"target": "J"
|
| 102 |
+
},
|
| 103 |
+
{
|
| 104 |
+
"source": "B",
|
| 105 |
+
"target": "K"
|
| 106 |
+
},
|
| 107 |
+
{
|
| 108 |
+
"source": "B",
|
| 109 |
+
"target": "L"
|
| 110 |
+
},
|
| 111 |
+
{
|
| 112 |
+
"source": "E",
|
| 113 |
+
"target": "F"
|
| 114 |
+
},
|
| 115 |
+
{
|
| 116 |
+
"source": "E",
|
| 117 |
+
"target": "I"
|
| 118 |
+
},
|
| 119 |
+
{
|
| 120 |
+
"source": "F",
|
| 121 |
+
"target": "G"
|
| 122 |
+
},
|
| 123 |
+
{
|
| 124 |
+
"source": "F",
|
| 125 |
+
"target": "J"
|
| 126 |
+
},
|
| 127 |
+
{
|
| 128 |
+
"source": "G",
|
| 129 |
+
"target": "H"
|
| 130 |
+
},
|
| 131 |
+
{
|
| 132 |
+
"source": "G",
|
| 133 |
+
"target": "K"
|
| 134 |
+
},
|
| 135 |
+
{
|
| 136 |
+
"source": "H",
|
| 137 |
+
"target": "L"
|
| 138 |
+
}
|
| 139 |
+
]
|
| 140 |
+
},
|
| 141 |
+
{
|
| 142 |
+
"type": "footer",
|
| 143 |
+
"text": "46 中国信通院在《5G 全连接工厂建设白皮书(2022 年)》中就曾提出“建议改变原有工厂内 IT-OT 系统应用建设运营方式,组织 IT-OT 融合团队,对 IT-OT 进行一体化部署......形成 IT-OT 应用的统筹建设、统一运维、统一管理,并促进形成工厂内同时要加快推进云网融合,实现网络资源、计算资源、平台资源等横向打通,提升工厂生产运营管理效率”;OPC基金会在《Extending OPC UA to the field: OPC UA for Field eXchange ( FX ) 》提出“IT/OT organizational convergence where the boundary between organizations blurs and management of IT and OT groups operate to common strategies and processes.”"
|
| 144 |
+
},
|
| 145 |
+
{
|
| 146 |
+
"type": "page_number",
|
| 147 |
+
"text": "86"
|
| 148 |
+
}
|
| 149 |
+
]
|
diagrams-and-tables/annotations/cn_diagram_38.json
ADDED
|
@@ -0,0 +1,105 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
[
|
| 2 |
+
{
|
| 3 |
+
"type": "header",
|
| 4 |
+
"text": "openEuler 技术白皮书"
|
| 5 |
+
},
|
| 6 |
+
{
|
| 7 |
+
"type": "title",
|
| 8 |
+
"text": "openEuler 覆盖全场景的创新平台"
|
| 9 |
+
},
|
| 10 |
+
{
|
| 11 |
+
"type": "diagram_caption",
|
| 12 |
+
"text": "openEuler 场景拓展示意图"
|
| 13 |
+
},
|
| 14 |
+
{
|
| 15 |
+
"type": "diagram",
|
| 16 |
+
"nodes": [
|
| 17 |
+
{
|
| 18 |
+
"id": "A",
|
| 19 |
+
"text": "服务器"
|
| 20 |
+
},
|
| 21 |
+
{
|
| 22 |
+
"id": "B",
|
| 23 |
+
"text": "服务器"
|
| 24 |
+
},
|
| 25 |
+
{
|
| 26 |
+
"id": "C",
|
| 27 |
+
"text": "云计算"
|
| 28 |
+
},
|
| 29 |
+
{
|
| 30 |
+
"id": "D",
|
| 31 |
+
"text": "边缘"
|
| 32 |
+
},
|
| 33 |
+
{
|
| 34 |
+
"id": "E",
|
| 35 |
+
"text": "嵌入式"
|
| 36 |
+
},
|
| 37 |
+
{
|
| 38 |
+
"id": "F",
|
| 39 |
+
"text": "基础公共服务"
|
| 40 |
+
}
|
| 41 |
+
],
|
| 42 |
+
"relationships": [
|
| 43 |
+
{
|
| 44 |
+
"source": "A",
|
| 45 |
+
"target": "B"
|
| 46 |
+
},
|
| 47 |
+
{
|
| 48 |
+
"source": "A",
|
| 49 |
+
"target": "C"
|
| 50 |
+
},
|
| 51 |
+
{
|
| 52 |
+
"source": "A",
|
| 53 |
+
"target": "D"
|
| 54 |
+
},
|
| 55 |
+
{
|
| 56 |
+
"source": "A",
|
| 57 |
+
"target": "E"
|
| 58 |
+
},
|
| 59 |
+
{
|
| 60 |
+
"source": "A",
|
| 61 |
+
"target": "F"
|
| 62 |
+
},
|
| 63 |
+
{
|
| 64 |
+
"source": "B",
|
| 65 |
+
"target": "F"
|
| 66 |
+
},
|
| 67 |
+
{
|
| 68 |
+
"source": "C",
|
| 69 |
+
"target": "F"
|
| 70 |
+
},
|
| 71 |
+
{
|
| 72 |
+
"source": "D",
|
| 73 |
+
"target": "F"
|
| 74 |
+
},
|
| 75 |
+
{
|
| 76 |
+
"source": "E",
|
| 77 |
+
"target": "F"
|
| 78 |
+
}
|
| 79 |
+
]
|
| 80 |
+
},
|
| 81 |
+
{
|
| 82 |
+
"type": "text",
|
| 83 |
+
"text": "openEuler 已支持 X86、ARM、SW64、RISC-V、LoongArch 多处理器架构及 PowerPC 芯片架构,持续完善多样性算力生态体验。\nopenEuler 社区面向场景化的 SIG 不断组建,推动 openEuler 应用边界从最初的服务器场景,逐步拓展到云计算、边缘计算、嵌入式等更多场景。openEuler 正成为覆盖数字基础设施全场景的操作系统,新增发布面向边缘计算的版本 openEuler Edge、面向嵌入式的版本 openEuler Embedded。\nopenEuler 希望与广大生态伙伴、用户、开发者一起,通过联合创新、社区共建,不断增强场景化能力,最终实现统一操作系统支持多设备,应用一次开发覆盖全场景。"
|
| 84 |
+
},
|
| 85 |
+
{
|
| 86 |
+
"type": "title",
|
| 87 |
+
"text": "openEuler 开放透明的开源软件供应链管理"
|
| 88 |
+
},
|
| 89 |
+
{
|
| 90 |
+
"type": "text",
|
| 91 |
+
"text": "开源操作系统的构建过程,也是供应链聚合优化的过程。拥有可靠开源软件供应链,是大规模商用操作系统的基础。openEuler 从用户场景出发,回溯梳理相应的软件依赖关系,理清所有软件包的上游社区地址、源码和上游对应验证。完成构建验证、分发、实现生命周期管理。开源软件的构建、运行依赖关系、上游社区,三者之前形成闭环且完整透明的软件供应链管理。"
|
| 92 |
+
},
|
| 93 |
+
{
|
| 94 |
+
"type": "title",
|
| 95 |
+
"text": "2. 平台架构"
|
| 96 |
+
},
|
| 97 |
+
{
|
| 98 |
+
"type": "title",
|
| 99 |
+
"text": "系统框架"
|
| 100 |
+
},
|
| 101 |
+
{
|
| 102 |
+
"type": "text",
|
| 103 |
+
"text": "openEuler 是覆盖全场景的创新平台,在引领内核创新,夯实云化基座的基础上,面向计算架构互联总线、存储介质发展新趋势,创新分布式、实时加速引擎和基础服务,结合边缘、嵌入式领域竞争力探索,打造全场景协同的面向数字基础设施的开源操作系统。"
|
| 104 |
+
}
|
| 105 |
+
]
|
diagrams-and-tables/annotations/cn_diagram_39.json
ADDED
|
@@ -0,0 +1,229 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
[
|
| 2 |
+
{
|
| 3 |
+
"type": "header",
|
| 4 |
+
"text": "openEuler 技术白皮书"
|
| 5 |
+
},
|
| 6 |
+
{
|
| 7 |
+
"type": "title",
|
| 8 |
+
"text": "智能诊断"
|
| 9 |
+
},
|
| 10 |
+
{
|
| 11 |
+
"type": "title",
|
| 12 |
+
"text": "功能描述"
|
| 13 |
+
},
|
| 14 |
+
{
|
| 15 |
+
"type": "diagram",
|
| 16 |
+
"nodes": [
|
| 17 |
+
{
|
| 18 |
+
"id": "A",
|
| 19 |
+
"text": "用户输入"
|
| 20 |
+
},
|
| 21 |
+
{
|
| 22 |
+
"id": "B",
|
| 23 |
+
"text": "巡检本节点当前时间的健康状况"
|
| 24 |
+
},
|
| 25 |
+
{
|
| 26 |
+
"id": "C",
|
| 27 |
+
"text": "异常事件1/异常事件2"
|
| 28 |
+
},
|
| 29 |
+
{
|
| 30 |
+
"id": "D",
|
| 31 |
+
"text": "check.1/check.2/check.3"
|
| 32 |
+
},
|
| 33 |
+
{
|
| 34 |
+
"id": "E",
|
| 35 |
+
"text": "EulerCopilot框架"
|
| 36 |
+
},
|
| 37 |
+
{
|
| 38 |
+
"id": "F",
|
| 39 |
+
"text": "意图理解 -> 巡检"
|
| 40 |
+
},
|
| 41 |
+
{
|
| 42 |
+
"id": "G",
|
| 43 |
+
"text": "异常事件列表"
|
| 44 |
+
},
|
| 45 |
+
{
|
| 46 |
+
"id": "H",
|
| 47 |
+
"text": "意图理解 -> 定界"
|
| 48 |
+
},
|
| 49 |
+
{
|
| 50 |
+
"id": "I",
|
| 51 |
+
"text": "异常事件根因指标TOP3"
|
| 52 |
+
},
|
| 53 |
+
{
|
| 54 |
+
"id": "J",
|
| 55 |
+
"text": "意图理解 -> 定位"
|
| 56 |
+
},
|
| 57 |
+
{
|
| 58 |
+
"id": "K",
|
| 59 |
+
"text": "Profiling定位结果报告"
|
| 60 |
+
},
|
| 61 |
+
{
|
| 62 |
+
"id": "L",
|
| 63 |
+
"text": "巡检 Agent"
|
| 64 |
+
},
|
| 65 |
+
{
|
| 66 |
+
"id": "M",
|
| 67 |
+
"text": "● 1、自动进行异常事件检测\n● 2、输出异常事件列表"
|
| 68 |
+
},
|
| 69 |
+
{
|
| 70 |
+
"id": "N",
|
| 71 |
+
"text": "定界 Agent"
|
| 72 |
+
},
|
| 73 |
+
{
|
| 74 |
+
"id": "O",
|
| 75 |
+
"text": "● 1、自动进行异常事件定界\n● 2、输出定界结果TOP3根因指标"
|
| 76 |
+
},
|
| 77 |
+
{
|
| 78 |
+
"id": "P",
|
| 79 |
+
"text": "定位 Agent"
|
| 80 |
+
},
|
| 81 |
+
{
|
| 82 |
+
"id": "Q",
|
| 83 |
+
"text": "● 1、自动进行profiling定位分析\n● 2、输出profiling结果"
|
| 84 |
+
},
|
| 85 |
+
{
|
| 86 |
+
"id": "R",
|
| 87 |
+
"text": "智能体框架"
|
| 88 |
+
},
|
| 89 |
+
{
|
| 90 |
+
"id": "S",
|
| 91 |
+
"text": "Agents"
|
| 92 |
+
}
|
| 93 |
+
],
|
| 94 |
+
"relationships": [
|
| 95 |
+
{
|
| 96 |
+
"source": "A",
|
| 97 |
+
"target": "B"
|
| 98 |
+
},
|
| 99 |
+
{
|
| 100 |
+
"source": "A",
|
| 101 |
+
"target": "C"
|
| 102 |
+
},
|
| 103 |
+
{
|
| 104 |
+
"source": "A",
|
| 105 |
+
"target": "D"
|
| 106 |
+
},
|
| 107 |
+
{
|
| 108 |
+
"source": "A",
|
| 109 |
+
"target": "R"
|
| 110 |
+
},
|
| 111 |
+
{
|
| 112 |
+
"source": "B",
|
| 113 |
+
"target": "C"
|
| 114 |
+
},
|
| 115 |
+
{
|
| 116 |
+
"source": "B",
|
| 117 |
+
"target": "F"
|
| 118 |
+
},
|
| 119 |
+
{
|
| 120 |
+
"source": "C",
|
| 121 |
+
"target": "D"
|
| 122 |
+
},
|
| 123 |
+
{
|
| 124 |
+
"source": "C",
|
| 125 |
+
"target": "G"
|
| 126 |
+
},
|
| 127 |
+
{
|
| 128 |
+
"source": "C",
|
| 129 |
+
"target": "H"
|
| 130 |
+
},
|
| 131 |
+
{
|
| 132 |
+
"source": "D",
|
| 133 |
+
"target": "I"
|
| 134 |
+
},
|
| 135 |
+
{
|
| 136 |
+
"source": "D",
|
| 137 |
+
"target": "J"
|
| 138 |
+
},
|
| 139 |
+
{
|
| 140 |
+
"source": "E",
|
| 141 |
+
"target": "F"
|
| 142 |
+
},
|
| 143 |
+
{
|
| 144 |
+
"source": "E",
|
| 145 |
+
"target": "G"
|
| 146 |
+
},
|
| 147 |
+
{
|
| 148 |
+
"source": "E",
|
| 149 |
+
"target": "H"
|
| 150 |
+
},
|
| 151 |
+
{
|
| 152 |
+
"source": "E",
|
| 153 |
+
"target": "I"
|
| 154 |
+
},
|
| 155 |
+
{
|
| 156 |
+
"source": "E",
|
| 157 |
+
"target": "J"
|
| 158 |
+
},
|
| 159 |
+
{
|
| 160 |
+
"source": "E",
|
| 161 |
+
"target": "K"
|
| 162 |
+
},
|
| 163 |
+
{
|
| 164 |
+
"source": "E",
|
| 165 |
+
"target": "R"
|
| 166 |
+
},
|
| 167 |
+
{
|
| 168 |
+
"source": "F",
|
| 169 |
+
"target": "M"
|
| 170 |
+
},
|
| 171 |
+
{
|
| 172 |
+
"source": "G",
|
| 173 |
+
"target": "M"
|
| 174 |
+
},
|
| 175 |
+
{
|
| 176 |
+
"source": "H",
|
| 177 |
+
"target": "O"
|
| 178 |
+
},
|
| 179 |
+
{
|
| 180 |
+
"source": "I",
|
| 181 |
+
"target": "O"
|
| 182 |
+
},
|
| 183 |
+
{
|
| 184 |
+
"source": "J",
|
| 185 |
+
"target": "Q"
|
| 186 |
+
},
|
| 187 |
+
{
|
| 188 |
+
"source": "K",
|
| 189 |
+
"target": "Q"
|
| 190 |
+
},
|
| 191 |
+
{
|
| 192 |
+
"source": "L",
|
| 193 |
+
"target": "M"
|
| 194 |
+
},
|
| 195 |
+
{
|
| 196 |
+
"source": "L",
|
| 197 |
+
"target": "S"
|
| 198 |
+
},
|
| 199 |
+
{
|
| 200 |
+
"source": "N",
|
| 201 |
+
"target": "O"
|
| 202 |
+
},
|
| 203 |
+
{
|
| 204 |
+
"source": "N",
|
| 205 |
+
"target": "S"
|
| 206 |
+
},
|
| 207 |
+
{
|
| 208 |
+
"source": "P",
|
| 209 |
+
"target": "Q"
|
| 210 |
+
},
|
| 211 |
+
{
|
| 212 |
+
"source": "P",
|
| 213 |
+
"target": "S"
|
| 214 |
+
}
|
| 215 |
+
]
|
| 216 |
+
},
|
| 217 |
+
{
|
| 218 |
+
"type": "text",
|
| 219 |
+
"text": "1. 巡检:调用 Inspection Agent,对指定 IP 进行异常事件检测,为用户提供包含异常容器 ID 以及异常指标(cpu、memory 等)的异常事件列表\n2. 定界:调用 Demarcation Agent,对巡检结果中指定异常事件进行定界分析,输出导致该异常事件的根因指标 TOP3\n3. 定位:调用 Detection Agent,对定界结果中指定根因指标进行 Profiling 定位分析,为用户提供该根因指标异常的热点堆栈、热点系统时间、热点性能指标等信息"
|
| 220 |
+
},
|
| 221 |
+
{
|
| 222 |
+
"type": "title",
|
| 223 |
+
"text": "应用场景"
|
| 224 |
+
},
|
| 225 |
+
{
|
| 226 |
+
"type": "text",
|
| 227 |
+
"text": "智能诊断接口在本次 openEuler 24.03 LTS SP1 版本的功能范围是:具备单机异常事件检测 + 定界 + profiling 定位的能力。"
|
| 228 |
+
}
|
| 229 |
+
]
|
diagrams-and-tables/annotations/cn_diagram_40.json
ADDED
|
@@ -0,0 +1,132 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
[
|
| 2 |
+
{
|
| 3 |
+
"type": "header",
|
| 4 |
+
"text": "openEuler 技术白皮书"
|
| 5 |
+
},
|
| 6 |
+
{
|
| 7 |
+
"type": "title",
|
| 8 |
+
"text": "应用场景"
|
| 9 |
+
},
|
| 10 |
+
{
|
| 11 |
+
"type": "text",
|
| 12 |
+
"text": "主版本场景:正常编译使用系统默认的 gcc-12.3.1。\n副版本场景:需要使用 GCC 14 高版本特性构建相关应用,使用 SCL 工具将构建环境切换为 gcc-toolset-14 编译工具链的编译环境。"
|
| 13 |
+
},
|
| 14 |
+
{
|
| 15 |
+
"type": "diagram_caption",
|
| 16 |
+
"text": "GCC 主副版本切换示意图"
|
| 17 |
+
},
|
| 18 |
+
{
|
| 19 |
+
"type": "diagram",
|
| 20 |
+
"nodes": [
|
| 21 |
+
{
|
| 22 |
+
"id": "A",
|
| 23 |
+
"text": "用户"
|
| 24 |
+
},
|
| 25 |
+
{
|
| 26 |
+
"id": "B",
|
| 27 |
+
"text": "默认使用"
|
| 28 |
+
},
|
| 29 |
+
{
|
| 30 |
+
"id": "C",
|
| 31 |
+
"text": "系统默认GCC"
|
| 32 |
+
},
|
| 33 |
+
{
|
| 34 |
+
"id": "D",
|
| 35 |
+
"text": "副版本GCC调用"
|
| 36 |
+
},
|
| 37 |
+
{
|
| 38 |
+
"id": "E",
|
| 39 |
+
"text": "使用脚本切换副版本GCC"
|
| 40 |
+
},
|
| 41 |
+
{
|
| 42 |
+
"id": "F",
|
| 43 |
+
"text": "设置环境变量"
|
| 44 |
+
},
|
| 45 |
+
{
|
| 46 |
+
"id": "G",
|
| 47 |
+
"text": "副版本GCC"
|
| 48 |
+
},
|
| 49 |
+
{
|
| 50 |
+
"id": "H",
|
| 51 |
+
"text": "使用scl工具切换GCC并激活运行环境"
|
| 52 |
+
},
|
| 53 |
+
{
|
| 54 |
+
"id": "I",
|
| 55 |
+
"text": "新建bash shell并使能副版本路径"
|
| 56 |
+
}
|
| 57 |
+
],
|
| 58 |
+
"relationships": [
|
| 59 |
+
{
|
| 60 |
+
"source": "A",
|
| 61 |
+
"target": "B"
|
| 62 |
+
},
|
| 63 |
+
{
|
| 64 |
+
"source": "A",
|
| 65 |
+
"target": "E"
|
| 66 |
+
},
|
| 67 |
+
{
|
| 68 |
+
"source": "A",
|
| 69 |
+
"target": "H"
|
| 70 |
+
},
|
| 71 |
+
{
|
| 72 |
+
"source": "B",
|
| 73 |
+
"target": "C",
|
| 74 |
+
"label": "/usr/bin/gcc"
|
| 75 |
+
},
|
| 76 |
+
{
|
| 77 |
+
"source": "C",
|
| 78 |
+
"target": "G"
|
| 79 |
+
},
|
| 80 |
+
{
|
| 81 |
+
"source": "D",
|
| 82 |
+
"target": "E"
|
| 83 |
+
},
|
| 84 |
+
{
|
| 85 |
+
"source": "D",
|
| 86 |
+
"target": "F"
|
| 87 |
+
},
|
| 88 |
+
{
|
| 89 |
+
"source": "D",
|
| 90 |
+
"target": "G"
|
| 91 |
+
},
|
| 92 |
+
{
|
| 93 |
+
"source": "D",
|
| 94 |
+
"target": "H"
|
| 95 |
+
},
|
| 96 |
+
{
|
| 97 |
+
"source": "D",
|
| 98 |
+
"target": "I"
|
| 99 |
+
},
|
| 100 |
+
{
|
| 101 |
+
"source": "E",
|
| 102 |
+
"target": "F",
|
| 103 |
+
"label": "/opt/openEuler/gcc-toolset-X/root/usr/bin"
|
| 104 |
+
},
|
| 105 |
+
{
|
| 106 |
+
"source": "F",
|
| 107 |
+
"target": "G"
|
| 108 |
+
},
|
| 109 |
+
{
|
| 110 |
+
"source": "G",
|
| 111 |
+
"target": "I"
|
| 112 |
+
},
|
| 113 |
+
{
|
| 114 |
+
"source": "H",
|
| 115 |
+
"target": "I",
|
| 116 |
+
"label": "scl enable gcc-toolset-X bash"
|
| 117 |
+
}
|
| 118 |
+
]
|
| 119 |
+
},
|
| 120 |
+
{
|
| 121 |
+
"type": "title",
|
| 122 |
+
"text": "5. 内核创新"
|
| 123 |
+
},
|
| 124 |
+
{
|
| 125 |
+
"type": "title",
|
| 126 |
+
"text": "openEuler 内核中的新特性"
|
| 127 |
+
},
|
| 128 |
+
{
|
| 129 |
+
"type": "text",
|
| 130 |
+
"text": "openEuler 24.03 LTS SP1 基于 Linux Kernel 6.6 内核构建,在此基础上,同时吸收了社区高版本的有益特性及社区创新特性。\n● 内存管理 folio 特性:Linux 内存管理基于 page(页)转换到由 folio(拉丁语 folio,对开本)进行管理,相比 page,folio 可以由一个或多个 page 组成,采用 struct folio 参数的函数声明它将对整个(1 个或者多个)页面进行操作,而不仅仅是 PAGE_SIZE 字节,从而移除不必要复合页转换,降低误用 tail page 问题;从内存管理效率上采用 folio 减少 LRU 链表数量,提升内存回收效率。另一方,一次分配更多连续内存减少 page fault 次数,一定程度降低内存碎片化;而在 IO 方面,可以加速大 IO 的读写效率,提升吞吐。全量支持匿名页、文件页的 large folio,提供系统级别的开关控制,业务可以按需使用。对于 ARM64 架构,基于硬件 contiguous bit 技术(16 个连续 PTE 只占一个 TLB entry),可以进一步降低系统 TLB miss,从而提升整体系统性能。24.03 LTS SP1 版本新增支持 anonymous shmem 分配 mTHP 与支持 mTHP 的 lazyfree,进一步增加内存"
|
| 131 |
+
}
|
| 132 |
+
]
|
diagrams-and-tables/annotations/cn_diagram_41.json
ADDED
|
@@ -0,0 +1,82 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
[
|
| 2 |
+
{
|
| 3 |
+
"type": "header",
|
| 4 |
+
"text": "openEuler 技术白皮书"
|
| 5 |
+
},
|
| 6 |
+
{
|
| 7 |
+
"type": "text",
|
| 8 |
+
"text": "因此本特性旨在对现有 IMA 机制进行增强,有效提升对解释器类应用程序的完整性保护能力。"
|
| 9 |
+
},
|
| 10 |
+
{
|
| 11 |
+
"type": "title",
|
| 12 |
+
"text": "功能描述"
|
| 13 |
+
},
|
| 14 |
+
{
|
| 15 |
+
"type": "text",
|
| 16 |
+
"text": "本需求的核心功能是,对OS现有权限机制进行扩展,保证通过exec运行的程序(如./test.sh)和通过解释器间接运行的程序(bash ./test.sh)具备相同的权限检查流程。具体方案如下:\n➢ openEuler 24.03 LTS SP1版本针对execveat系统调用新增AT_CHECK参数的支持,实现对文件进行可执行权限检查并返回结果,而不真正地执行该文件;\n➢ 针对bash、jdk等组件进行功能扩展,调用execveat+CHECK对待运行的脚本文件或java文件进行可执行权限检查,只有当检查成功后,才可继续运行程序。\n该特性与IMA机制相结合,即可实现如下图所示的解释器类应用程序完整性保护方案。由解释器调用execveat触发对脚本程序的可执行权限检查,并间接触发IMA的exec检查策略,在有效实现脚本程序完整性保护的同时,避免开启IMA read检查策略导致的保护范围扩大化风险。"
|
| 17 |
+
},
|
| 18 |
+
{
|
| 19 |
+
"type": "diagram",
|
| 20 |
+
"nodes": [
|
| 21 |
+
{
|
| 22 |
+
"id": "A",
|
| 23 |
+
"text": "脚本文件"
|
| 24 |
+
},
|
| 25 |
+
{
|
| 26 |
+
"id": "B",
|
| 27 |
+
"text": "IMA摘要列表"
|
| 28 |
+
},
|
| 29 |
+
{
|
| 30 |
+
"id": "C",
|
| 31 |
+
"text": "解释器\n(bash/python/java/...)"
|
| 32 |
+
},
|
| 33 |
+
{
|
| 34 |
+
"id": "D",
|
| 35 |
+
"text": "openEuler IMA子系统"
|
| 36 |
+
},
|
| 37 |
+
{
|
| 38 |
+
"id": "E",
|
| 39 |
+
"text": "进程 (脚本程序)"
|
| 40 |
+
}
|
| 41 |
+
],
|
| 42 |
+
"relationships": [
|
| 43 |
+
{
|
| 44 |
+
"source": "A",
|
| 45 |
+
"target": "B",
|
| 46 |
+
"label": "预先生成"
|
| 47 |
+
},
|
| 48 |
+
{
|
| 49 |
+
"source": "A",
|
| 50 |
+
"target": "C",
|
| 51 |
+
"label": "① 打开文件"
|
| 52 |
+
},
|
| 53 |
+
{
|
| 54 |
+
"source": "B",
|
| 55 |
+
"target": "D",
|
| 56 |
+
"label": "部署阶段导入"
|
| 57 |
+
},
|
| 58 |
+
{
|
| 59 |
+
"source": "C",
|
| 60 |
+
"target": "D",
|
| 61 |
+
"label": "② 查询完整性\n③ 返回校验结果"
|
| 62 |
+
},
|
| 63 |
+
{
|
| 64 |
+
"source": "C",
|
| 65 |
+
"target": "E",
|
| 66 |
+
"label": "④ 解释执行"
|
| 67 |
+
}
|
| 68 |
+
]
|
| 69 |
+
},
|
| 70 |
+
{
|
| 71 |
+
"type": "text",
|
| 72 |
+
"text": "同时其他社区开发人员或用户可基于该特性,自行扩展其他解释器或类似机制的支持。"
|
| 73 |
+
},
|
| 74 |
+
{
|
| 75 |
+
"type": "title",
|
| 76 |
+
"text": "应用场景"
|
| 77 |
+
},
|
| 78 |
+
{
|
| 79 |
+
"type": "text",
|
| 80 |
+
"text": "在高安全要求的场景,用户可基于该特性实现“应用程序白名单”功能,即只允许通过 IMA 度量或校验的二进制程序或脚本程序才可在系统中运行。"
|
| 81 |
+
}
|
| 82 |
+
]
|
diagrams-and-tables/annotations/cn_diagram_42.json
ADDED
|
@@ -0,0 +1,95 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
[
|
| 2 |
+
{
|
| 3 |
+
"type": "header",
|
| 4 |
+
"text": "openEuler 技术白皮书"
|
| 5 |
+
},
|
| 6 |
+
{
|
| 7 |
+
"type": "diagram",
|
| 8 |
+
"nodes": [
|
| 9 |
+
{
|
| 10 |
+
"id": "A",
|
| 11 |
+
"text": "IMA"
|
| 12 |
+
},
|
| 13 |
+
{
|
| 14 |
+
"id": "B",
|
| 15 |
+
"text": "DIM"
|
| 16 |
+
},
|
| 17 |
+
{
|
| 18 |
+
"id": "C",
|
| 19 |
+
"text": "..."
|
| 20 |
+
},
|
| 21 |
+
{
|
| 22 |
+
"id": "D",
|
| 23 |
+
"text": "可信根框架"
|
| 24 |
+
},
|
| 25 |
+
{
|
| 26 |
+
"id": "E",
|
| 27 |
+
"text": "TPM"
|
| 28 |
+
},
|
| 29 |
+
{
|
| 30 |
+
"id": "F",
|
| 31 |
+
"text": "virtCCA"
|
| 32 |
+
},
|
| 33 |
+
{
|
| 34 |
+
"id": "G",
|
| 35 |
+
"text": "..."
|
| 36 |
+
}
|
| 37 |
+
],
|
| 38 |
+
"relationships": [
|
| 39 |
+
{
|
| 40 |
+
"source": "A",
|
| 41 |
+
"target": "D",
|
| 42 |
+
"label": "统一度量接口"
|
| 43 |
+
},
|
| 44 |
+
{
|
| 45 |
+
"source": "B",
|
| 46 |
+
"target": "D",
|
| 47 |
+
"label": "统一度量接口"
|
| 48 |
+
},
|
| 49 |
+
{
|
| 50 |
+
"source": "C",
|
| 51 |
+
"target": "D",
|
| 52 |
+
"label": "统一度量接口"
|
| 53 |
+
},
|
| 54 |
+
{
|
| 55 |
+
"source": "D",
|
| 56 |
+
"target": "E",
|
| 57 |
+
"label": "各类驱动程序"
|
| 58 |
+
},
|
| 59 |
+
{
|
| 60 |
+
"source": "D",
|
| 61 |
+
"target": "F",
|
| 62 |
+
"label": "各类驱动程序"
|
| 63 |
+
},
|
| 64 |
+
{
|
| 65 |
+
"source": "D",
|
| 66 |
+
"target": "G",
|
| 67 |
+
"label": "各类驱动程序"
|
| 68 |
+
}
|
| 69 |
+
]
|
| 70 |
+
},
|
| 71 |
+
{
|
| 72 |
+
"type": "title",
|
| 73 |
+
"text": "应用场景"
|
| 74 |
+
},
|
| 75 |
+
{
|
| 76 |
+
"type": "text",
|
| 77 |
+
"text": "当前该框架已实现对于 TPM 和 virtCCA 可信根的支持,用户可在支持 TPM 和 virtCCA 的环境中使能 IMA 特性,并通过可信根证明 IMA 度量结果的完整性。同时其他社区开发人员或硬件厂商可基于该特性,自行扩展完整性度量特性和硬件的支持。"
|
| 78 |
+
},
|
| 79 |
+
{
|
| 80 |
+
"type": "title",
|
| 81 |
+
"text": "secGear 特性增强"
|
| 82 |
+
},
|
| 83 |
+
{
|
| 84 |
+
"type": "text",
|
| 85 |
+
"text": "secGear 远程证明统一框架是机密计算远程证明相关的关键组件,屏蔽不同 TEE 远程证明差异,提供 Attestation Agent 和 Attestation Service 两个组件,Agent 供用户集成获取证明报告,对接证明服务;Service 可独立部署,支持 iTrustee、virtCCA 远程证明报告的验证。"
|
| 86 |
+
},
|
| 87 |
+
{
|
| 88 |
+
"type": "title",
|
| 89 |
+
"text": "功能描述"
|
| 90 |
+
},
|
| 91 |
+
{
|
| 92 |
+
"type": "text",
|
| 93 |
+
"text": "远程证明统一框架聚焦机密计算相关功能,部署服务时需要的服务运维等相关能力由服务部署第三方提供。远程证明统一框架的关键技术如下:"
|
| 94 |
+
}
|
| 95 |
+
]
|
diagrams-and-tables/annotations/cn_diagram_43.json
ADDED
|
@@ -0,0 +1,121 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
[
|
| 2 |
+
{
|
| 3 |
+
"type": "header",
|
| 4 |
+
"text": "openEuler 技术白皮书"
|
| 5 |
+
},
|
| 6 |
+
{
|
| 7 |
+
"type": "title",
|
| 8 |
+
"text": "功能描述"
|
| 9 |
+
},
|
| 10 |
+
{
|
| 11 |
+
"type": "diagram",
|
| 12 |
+
"nodes": [
|
| 13 |
+
{
|
| 14 |
+
"id": "A",
|
| 15 |
+
"text": "authHub"
|
| 16 |
+
},
|
| 17 |
+
{
|
| 18 |
+
"id": "B",
|
| 19 |
+
"text": "用户管理"
|
| 20 |
+
},
|
| 21 |
+
{
|
| 22 |
+
"id": "C",
|
| 23 |
+
"text": "应用注册"
|
| 24 |
+
},
|
| 25 |
+
{
|
| 26 |
+
"id": "D",
|
| 27 |
+
"text": "应用属性设置"
|
| 28 |
+
},
|
| 29 |
+
{
|
| 30 |
+
"id": "E",
|
| 31 |
+
"text": "用户鉴权"
|
| 32 |
+
},
|
| 33 |
+
{
|
| 34 |
+
"id": "F",
|
| 35 |
+
"text": "单点登录登出"
|
| 36 |
+
},
|
| 37 |
+
{
|
| 38 |
+
"id": "G",
|
| 39 |
+
"text": "用户管理"
|
| 40 |
+
},
|
| 41 |
+
{
|
| 42 |
+
"id": "H",
|
| 43 |
+
"text": "功能应用"
|
| 44 |
+
},
|
| 45 |
+
{
|
| 46 |
+
"id": "I",
|
| 47 |
+
"text": "主机服务"
|
| 48 |
+
},
|
| 49 |
+
{
|
| 50 |
+
"id": "J",
|
| 51 |
+
"text": "漏洞巡检"
|
| 52 |
+
},
|
| 53 |
+
{
|
| 54 |
+
"id": "K",
|
| 55 |
+
"text": "配置溯源"
|
| 56 |
+
},
|
| 57 |
+
{
|
| 58 |
+
"id": "L",
|
| 59 |
+
"text": "第三方集成应用"
|
| 60 |
+
}
|
| 61 |
+
],
|
| 62 |
+
"relationships": [
|
| 63 |
+
{
|
| 64 |
+
"source": "A",
|
| 65 |
+
"target": "B"
|
| 66 |
+
},
|
| 67 |
+
{
|
| 68 |
+
"source": "A",
|
| 69 |
+
"target": "E"
|
| 70 |
+
},
|
| 71 |
+
{
|
| 72 |
+
"source": "A",
|
| 73 |
+
"target": "H"
|
| 74 |
+
},
|
| 75 |
+
{
|
| 76 |
+
"source": "B",
|
| 77 |
+
"target": "C"
|
| 78 |
+
},
|
| 79 |
+
{
|
| 80 |
+
"source": "B",
|
| 81 |
+
"target": "D"
|
| 82 |
+
},
|
| 83 |
+
{
|
| 84 |
+
"source": "E",
|
| 85 |
+
"target": "F"
|
| 86 |
+
},
|
| 87 |
+
{
|
| 88 |
+
"source": "E",
|
| 89 |
+
"target": "G"
|
| 90 |
+
},
|
| 91 |
+
{
|
| 92 |
+
"source": "H",
|
| 93 |
+
"target": "I"
|
| 94 |
+
},
|
| 95 |
+
{
|
| 96 |
+
"source": "H",
|
| 97 |
+
"target": "J"
|
| 98 |
+
},
|
| 99 |
+
{
|
| 100 |
+
"source": "H",
|
| 101 |
+
"target": "K"
|
| 102 |
+
},
|
| 103 |
+
{
|
| 104 |
+
"source": "H",
|
| 105 |
+
"target": "L"
|
| 106 |
+
}
|
| 107 |
+
]
|
| 108 |
+
},
|
| 109 |
+
{
|
| 110 |
+
"type": "text",
|
| 111 |
+
"text": "authHub 基于 oauth2 协议,实现统一用户鉴权中心,用户鉴权中心功能包括:\n● 应用管理:应用部署后需要在 authHub 应用管理界面进行注册和配置,用户可以使用注册的应用的功能。\n● 用户鉴权:在 authHub 管理的应用中,用户可以实现单点登录和单点登出。"
|
| 112 |
+
},
|
| 113 |
+
{
|
| 114 |
+
"type": "title",
|
| 115 |
+
"text": "应用场景"
|
| 116 |
+
},
|
| 117 |
+
{
|
| 118 |
+
"type": "text",
|
| 119 |
+
"text": "Aops 适配 authHub 统一用户鉴权,支持第三方应用现有的鉴权对接 authHub,提升应用的可拓展性;不同应用间的鉴权通过 authHub 统一管理,管理服务的访问权限。"
|
| 120 |
+
}
|
| 121 |
+
]
|
diagrams-and-tables/annotations/cn_diagram_44.json
ADDED
|
@@ -0,0 +1,269 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
[
|
| 2 |
+
{
|
| 3 |
+
"type": "header",
|
| 4 |
+
"text": "openEuler 技术白皮书"
|
| 5 |
+
},
|
| 6 |
+
{
|
| 7 |
+
"type": "diagram",
|
| 8 |
+
"nodes": [
|
| 9 |
+
{
|
| 10 |
+
"id": "A",
|
| 11 |
+
"text": "Normal World"
|
| 12 |
+
},
|
| 13 |
+
{
|
| 14 |
+
"id": "B",
|
| 15 |
+
"text": "Host OS"
|
| 16 |
+
},
|
| 17 |
+
{
|
| 18 |
+
"id": "C",
|
| 19 |
+
"text": "libvirt"
|
| 20 |
+
},
|
| 21 |
+
{
|
| 22 |
+
"id": "D",
|
| 23 |
+
"text": "qemu"
|
| 24 |
+
},
|
| 25 |
+
{
|
| 26 |
+
"id": "E",
|
| 27 |
+
"text": "SMMU driver"
|
| 28 |
+
},
|
| 29 |
+
{
|
| 30 |
+
"id": "F",
|
| 31 |
+
"text": "KVM"
|
| 32 |
+
},
|
| 33 |
+
{
|
| 34 |
+
"id": "G",
|
| 35 |
+
"text": "开源修改组件"
|
| 36 |
+
},
|
| 37 |
+
{
|
| 38 |
+
"id": "H",
|
| 39 |
+
"text": "底层固件"
|
| 40 |
+
},
|
| 41 |
+
{
|
| 42 |
+
"id": "I",
|
| 43 |
+
"text": "virtCCA组件"
|
| 44 |
+
},
|
| 45 |
+
{
|
| 46 |
+
"id": "J",
|
| 47 |
+
"text": "Secure World"
|
| 48 |
+
},
|
| 49 |
+
{
|
| 50 |
+
"id": "K",
|
| 51 |
+
"text": "cVM0"
|
| 52 |
+
},
|
| 53 |
+
{
|
| 54 |
+
"id": "L",
|
| 55 |
+
"text": "用户态"
|
| 56 |
+
},
|
| 57 |
+
{
|
| 58 |
+
"id": "M",
|
| 59 |
+
"text": "OpenSSL"
|
| 60 |
+
},
|
| 61 |
+
{
|
| 62 |
+
"id": "N",
|
| 63 |
+
"text": "KAE引擎"
|
| 64 |
+
},
|
| 65 |
+
{
|
| 66 |
+
"id": "O",
|
| 67 |
+
"text": "UADK"
|
| 68 |
+
},
|
| 69 |
+
{
|
| 70 |
+
"id": "P",
|
| 71 |
+
"text": "内核态"
|
| 72 |
+
},
|
| 73 |
+
{
|
| 74 |
+
"id": "Q",
|
| 75 |
+
"text": "uacce"
|
| 76 |
+
},
|
| 77 |
+
{
|
| 78 |
+
"id": "R",
|
| 79 |
+
"text": "ACC VF驱动"
|
| 80 |
+
},
|
| 81 |
+
{
|
| 82 |
+
"id": "S",
|
| 83 |
+
"text": "cVM1"
|
| 84 |
+
},
|
| 85 |
+
{
|
| 86 |
+
"id": "T",
|
| 87 |
+
"text": "用户态"
|
| 88 |
+
},
|
| 89 |
+
{
|
| 90 |
+
"id": "U",
|
| 91 |
+
"text": "OpenSSL"
|
| 92 |
+
},
|
| 93 |
+
{
|
| 94 |
+
"id": "V",
|
| 95 |
+
"text": "KAE引擎"
|
| 96 |
+
},
|
| 97 |
+
{
|
| 98 |
+
"id": "W",
|
| 99 |
+
"text": "UADK"
|
| 100 |
+
},
|
| 101 |
+
{
|
| 102 |
+
"id": "X",
|
| 103 |
+
"text": "内核态"
|
| 104 |
+
},
|
| 105 |
+
{
|
| 106 |
+
"id": "Y",
|
| 107 |
+
"text": "uacce"
|
| 108 |
+
},
|
| 109 |
+
{
|
| 110 |
+
"id": "Z",
|
| 111 |
+
"text": "ACC VF驱动"
|
| 112 |
+
},
|
| 113 |
+
{
|
| 114 |
+
"id": "AA",
|
| 115 |
+
"text": "DA Module"
|
| 116 |
+
},
|
| 117 |
+
{
|
| 118 |
+
"id": "AB",
|
| 119 |
+
"text": "tmm"
|
| 120 |
+
},
|
| 121 |
+
{
|
| 122 |
+
"id": "AC",
|
| 123 |
+
"text": "ACC PF驱动"
|
| 124 |
+
},
|
| 125 |
+
{
|
| 126 |
+
"id": "AD",
|
| 127 |
+
"text": "S-EL2"
|
| 128 |
+
},
|
| 129 |
+
{
|
| 130 |
+
"id": "AE",
|
| 131 |
+
"text": "KAE Device(SEC/HPRE)"
|
| 132 |
+
}
|
| 133 |
+
],
|
| 134 |
+
"relationships": [
|
| 135 |
+
{
|
| 136 |
+
"source": "A",
|
| 137 |
+
"target": "B"
|
| 138 |
+
},
|
| 139 |
+
{
|
| 140 |
+
"source": "A",
|
| 141 |
+
"target": "G"
|
| 142 |
+
},
|
| 143 |
+
{
|
| 144 |
+
"source": "A",
|
| 145 |
+
"target": "H"
|
| 146 |
+
},
|
| 147 |
+
{
|
| 148 |
+
"source": "A",
|
| 149 |
+
"target": "I"
|
| 150 |
+
},
|
| 151 |
+
{
|
| 152 |
+
"source": "B",
|
| 153 |
+
"target": "C"
|
| 154 |
+
},
|
| 155 |
+
{
|
| 156 |
+
"source": "B",
|
| 157 |
+
"target": "D"
|
| 158 |
+
},
|
| 159 |
+
{
|
| 160 |
+
"source": "B",
|
| 161 |
+
"target": "E"
|
| 162 |
+
},
|
| 163 |
+
{
|
| 164 |
+
"source": "B",
|
| 165 |
+
"target": "F"
|
| 166 |
+
},
|
| 167 |
+
{
|
| 168 |
+
"source": "J",
|
| 169 |
+
"target": "K"
|
| 170 |
+
},
|
| 171 |
+
{
|
| 172 |
+
"source": "J",
|
| 173 |
+
"target": "S"
|
| 174 |
+
},
|
| 175 |
+
{
|
| 176 |
+
"source": "J",
|
| 177 |
+
"target": "AB"
|
| 178 |
+
},
|
| 179 |
+
{
|
| 180 |
+
"source": "J",
|
| 181 |
+
"target": "AE"
|
| 182 |
+
},
|
| 183 |
+
{
|
| 184 |
+
"source": "K",
|
| 185 |
+
"target": "L"
|
| 186 |
+
},
|
| 187 |
+
{
|
| 188 |
+
"source": "K",
|
| 189 |
+
"target": "P"
|
| 190 |
+
},
|
| 191 |
+
{
|
| 192 |
+
"source": "L",
|
| 193 |
+
"target": "M"
|
| 194 |
+
},
|
| 195 |
+
{
|
| 196 |
+
"source": "L",
|
| 197 |
+
"target": "N"
|
| 198 |
+
},
|
| 199 |
+
{
|
| 200 |
+
"source": "L",
|
| 201 |
+
"target": "O"
|
| 202 |
+
},
|
| 203 |
+
{
|
| 204 |
+
"source": "P",
|
| 205 |
+
"target": "Q"
|
| 206 |
+
},
|
| 207 |
+
{
|
| 208 |
+
"source": "P",
|
| 209 |
+
"target": "R"
|
| 210 |
+
},
|
| 211 |
+
{
|
| 212 |
+
"source": "S",
|
| 213 |
+
"target": "T"
|
| 214 |
+
},
|
| 215 |
+
{
|
| 216 |
+
"source": "S",
|
| 217 |
+
"target": "X"
|
| 218 |
+
},
|
| 219 |
+
{
|
| 220 |
+
"source": "T",
|
| 221 |
+
"target": "U"
|
| 222 |
+
},
|
| 223 |
+
{
|
| 224 |
+
"source": "T",
|
| 225 |
+
"target": "V"
|
| 226 |
+
},
|
| 227 |
+
{
|
| 228 |
+
"source": "T",
|
| 229 |
+
"target": "W"
|
| 230 |
+
},
|
| 231 |
+
{
|
| 232 |
+
"source": "X",
|
| 233 |
+
"target": "Y"
|
| 234 |
+
},
|
| 235 |
+
{
|
| 236 |
+
"source": "X",
|
| 237 |
+
"target": "Z"
|
| 238 |
+
},
|
| 239 |
+
{
|
| 240 |
+
"source": "AA",
|
| 241 |
+
"target": "AB"
|
| 242 |
+
},
|
| 243 |
+
{
|
| 244 |
+
"source": "AB",
|
| 245 |
+
"target": "AC"
|
| 246 |
+
},
|
| 247 |
+
{
|
| 248 |
+
"source": "AB",
|
| 249 |
+
"target": "AD"
|
| 250 |
+
}
|
| 251 |
+
]
|
| 252 |
+
},
|
| 253 |
+
{
|
| 254 |
+
"type": "title",
|
| 255 |
+
"text": "应用场景"
|
| 256 |
+
},
|
| 257 |
+
{
|
| 258 |
+
"type": "text",
|
| 259 |
+
"text": "面向密态数据库、安全云主机、机密多方计算、数据可信流通以及 AI 模型数据保护。"
|
| 260 |
+
},
|
| 261 |
+
{
|
| 262 |
+
"type": "title",
|
| 263 |
+
"text": "海光 CSV3 支持"
|
| 264 |
+
},
|
| 265 |
+
{
|
| 266 |
+
"type": "text",
|
| 267 |
+
"text": "海光第三代安全虚拟化技术(CSV3)在前二代技术的基础上继续增强,在CPU内部实现了虚拟机数据的安全隔离,禁止主机操作系统读写CSV3虚拟机内存,禁止主机操作系统读写虚拟机嵌套页表,保证了虚拟机数据的完整性,实现了CSV3虚拟机数据机密性和完整性的双重安全。"
|
| 268 |
+
}
|
| 269 |
+
]
|
diagrams-and-tables/annotations/cn_diagram_45.json
ADDED
|
@@ -0,0 +1,301 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
[
|
| 2 |
+
{
|
| 3 |
+
"type": "header",
|
| 4 |
+
"text": "openEuler 技术白皮书"
|
| 5 |
+
},
|
| 6 |
+
{
|
| 7 |
+
"type": "text",
|
| 8 |
+
"text": "在政府机构、AI、医疗、金融、多方计算等异构加速场景中,为数据安全保驾护航。"
|
| 9 |
+
},
|
| 10 |
+
{
|
| 11 |
+
"type": "title",
|
| 12 |
+
"text": "密码套件 openHiTLS"
|
| 13 |
+
},
|
| 14 |
+
{
|
| 15 |
+
"type": "text",
|
| 16 |
+
"text": "openHiTLS 旨在通过提供轻量化、可裁剪的软件技术架构及丰富的国际主流及中国商用密码算法、协议,满足云计算、大数据、AI、金融等多样化行业的安全需求。它具备算法先进、性能卓越、安全可靠、开放架构及多语言平滑兼容等特点,为开发者提供了一套安全、可扩展的密码解决方案。通过社区共建与生态建设,openHiTLS 推动密码安全标准在各行各业的加速落地,同时构建以 openEuler 为核心的安全开源生态,为用户带来更加安全、可靠的数字环境。"
|
| 17 |
+
},
|
| 18 |
+
{
|
| 19 |
+
"type": "diagram_caption",
|
| 20 |
+
"text": "openHiTLS 架构图"
|
| 21 |
+
},
|
| 22 |
+
{
|
| 23 |
+
"type": "diagram",
|
| 24 |
+
"nodes": [
|
| 25 |
+
{
|
| 26 |
+
"id": "A",
|
| 27 |
+
"text": "算法、协议、证书命令行工具"
|
| 28 |
+
},
|
| 29 |
+
{
|
| 30 |
+
"id": "B",
|
| 31 |
+
"text": "统一接口层"
|
| 32 |
+
},
|
| 33 |
+
{
|
| 34 |
+
"id": "C",
|
| 35 |
+
"text": "openHiTLS原生接口"
|
| 36 |
+
},
|
| 37 |
+
{
|
| 38 |
+
"id": "D",
|
| 39 |
+
"text": "基础安全协议"
|
| 40 |
+
},
|
| 41 |
+
{
|
| 42 |
+
"id": "E",
|
| 43 |
+
"text": "TLS1.X"
|
| 44 |
+
},
|
| 45 |
+
{
|
| 46 |
+
"id": "F",
|
| 47 |
+
"text": "DTLS"
|
| 48 |
+
},
|
| 49 |
+
{
|
| 50 |
+
"id": "G",
|
| 51 |
+
"text": "TLCP"
|
| 52 |
+
},
|
| 53 |
+
{
|
| 54 |
+
"id": "H",
|
| 55 |
+
"text": "RFC8998"
|
| 56 |
+
},
|
| 57 |
+
{
|
| 58 |
+
"id": "I",
|
| 59 |
+
"text": "......"
|
| 60 |
+
},
|
| 61 |
+
{
|
| 62 |
+
"id": "J",
|
| 63 |
+
"text": "数字证书基础"
|
| 64 |
+
},
|
| 65 |
+
{
|
| 66 |
+
"id": "K",
|
| 67 |
+
"text": "ASN.1"
|
| 68 |
+
},
|
| 69 |
+
{
|
| 70 |
+
"id": "L",
|
| 71 |
+
"text": "PKCS10/12"
|
| 72 |
+
},
|
| 73 |
+
{
|
| 74 |
+
"id": "M",
|
| 75 |
+
"text": "X509"
|
| 76 |
+
},
|
| 77 |
+
{
|
| 78 |
+
"id": "N",
|
| 79 |
+
"text": "......"
|
| 80 |
+
},
|
| 81 |
+
{
|
| 82 |
+
"id": "O",
|
| 83 |
+
"text": "密码算法"
|
| 84 |
+
},
|
| 85 |
+
{
|
| 86 |
+
"id": "P",
|
| 87 |
+
"text": "国际算法"
|
| 88 |
+
},
|
| 89 |
+
{
|
| 90 |
+
"id": "Q",
|
| 91 |
+
"text": "AES"
|
| 92 |
+
},
|
| 93 |
+
{
|
| 94 |
+
"id": "R",
|
| 95 |
+
"text": "CHACHA20"
|
| 96 |
+
},
|
| 97 |
+
{
|
| 98 |
+
"id": "S",
|
| 99 |
+
"text": "DSA"
|
| 100 |
+
},
|
| 101 |
+
{
|
| 102 |
+
"id": "T",
|
| 103 |
+
"text": "SHA3"
|
| 104 |
+
},
|
| 105 |
+
{
|
| 106 |
+
"id": "U",
|
| 107 |
+
"text": "SHA2"
|
| 108 |
+
},
|
| 109 |
+
{
|
| 110 |
+
"id": "V",
|
| 111 |
+
"text": "(EC) DH"
|
| 112 |
+
},
|
| 113 |
+
{
|
| 114 |
+
"id": "W",
|
| 115 |
+
"text": "RSA"
|
| 116 |
+
},
|
| 117 |
+
{
|
| 118 |
+
"id": "X",
|
| 119 |
+
"text": "ECC"
|
| 120 |
+
},
|
| 121 |
+
{
|
| 122 |
+
"id": "Y",
|
| 123 |
+
"text": "ECDSA"
|
| 124 |
+
},
|
| 125 |
+
{
|
| 126 |
+
"id": "Z",
|
| 127 |
+
"text": "Curve25519"
|
| 128 |
+
},
|
| 129 |
+
{
|
| 130 |
+
"id": "AA",
|
| 131 |
+
"text": "PBKDF2"
|
| 132 |
+
},
|
| 133 |
+
{
|
| 134 |
+
"id": "AB",
|
| 135 |
+
"text": "......"
|
| 136 |
+
},
|
| 137 |
+
{
|
| 138 |
+
"id": "AC",
|
| 139 |
+
"text": "国密算法"
|
| 140 |
+
},
|
| 141 |
+
{
|
| 142 |
+
"id": "AD",
|
| 143 |
+
"text": "SM2"
|
| 144 |
+
},
|
| 145 |
+
{
|
| 146 |
+
"id": "AE",
|
| 147 |
+
"text": "SM3"
|
| 148 |
+
},
|
| 149 |
+
{
|
| 150 |
+
"id": "AF",
|
| 151 |
+
"text": "SM4"
|
| 152 |
+
},
|
| 153 |
+
{
|
| 154 |
+
"id": "AG",
|
| 155 |
+
"text": "..."
|
| 156 |
+
},
|
| 157 |
+
{
|
| 158 |
+
"id": "AH",
|
| 159 |
+
"text": "随机数发生器"
|
| 160 |
+
},
|
| 161 |
+
{
|
| 162 |
+
"id": "AI",
|
| 163 |
+
"text": "DRBG-CTR/HASH/HMAC"
|
| 164 |
+
}
|
| 165 |
+
],
|
| 166 |
+
"relationships": [
|
| 167 |
+
{
|
| 168 |
+
"source": "B",
|
| 169 |
+
"target": "C"
|
| 170 |
+
},
|
| 171 |
+
{
|
| 172 |
+
"source": "D",
|
| 173 |
+
"target": "E"
|
| 174 |
+
},
|
| 175 |
+
{
|
| 176 |
+
"source": "D",
|
| 177 |
+
"target": "F"
|
| 178 |
+
},
|
| 179 |
+
{
|
| 180 |
+
"source": "D",
|
| 181 |
+
"target": "G"
|
| 182 |
+
},
|
| 183 |
+
{
|
| 184 |
+
"source": "D",
|
| 185 |
+
"target": "H"
|
| 186 |
+
},
|
| 187 |
+
{
|
| 188 |
+
"source": "D",
|
| 189 |
+
"target": "I"
|
| 190 |
+
},
|
| 191 |
+
{
|
| 192 |
+
"source": "J",
|
| 193 |
+
"target": "K"
|
| 194 |
+
},
|
| 195 |
+
{
|
| 196 |
+
"source": "J",
|
| 197 |
+
"target": "L"
|
| 198 |
+
},
|
| 199 |
+
{
|
| 200 |
+
"source": "J",
|
| 201 |
+
"target": "M"
|
| 202 |
+
},
|
| 203 |
+
{
|
| 204 |
+
"source": "J",
|
| 205 |
+
"target": "N"
|
| 206 |
+
},
|
| 207 |
+
{
|
| 208 |
+
"source": "O",
|
| 209 |
+
"target": "P"
|
| 210 |
+
},
|
| 211 |
+
{
|
| 212 |
+
"source": "O",
|
| 213 |
+
"target": "AC"
|
| 214 |
+
},
|
| 215 |
+
{
|
| 216 |
+
"source": "O",
|
| 217 |
+
"target": "AH"
|
| 218 |
+
},
|
| 219 |
+
{
|
| 220 |
+
"source": "P",
|
| 221 |
+
"target": "Q"
|
| 222 |
+
},
|
| 223 |
+
{
|
| 224 |
+
"source": "P",
|
| 225 |
+
"target": "R"
|
| 226 |
+
},
|
| 227 |
+
{
|
| 228 |
+
"source": "P",
|
| 229 |
+
"target": "S"
|
| 230 |
+
},
|
| 231 |
+
{
|
| 232 |
+
"source": "P",
|
| 233 |
+
"target": "T"
|
| 234 |
+
},
|
| 235 |
+
{
|
| 236 |
+
"source": "P",
|
| 237 |
+
"target": "U"
|
| 238 |
+
},
|
| 239 |
+
{
|
| 240 |
+
"source": "P",
|
| 241 |
+
"target": "V"
|
| 242 |
+
},
|
| 243 |
+
{
|
| 244 |
+
"source": "P",
|
| 245 |
+
"target": "W"
|
| 246 |
+
},
|
| 247 |
+
{
|
| 248 |
+
"source": "P",
|
| 249 |
+
"target": "X"
|
| 250 |
+
},
|
| 251 |
+
{
|
| 252 |
+
"source": "P",
|
| 253 |
+
"target": "Y"
|
| 254 |
+
},
|
| 255 |
+
{
|
| 256 |
+
"source": "P",
|
| 257 |
+
"target": "Z"
|
| 258 |
+
},
|
| 259 |
+
{
|
| 260 |
+
"source": "P",
|
| 261 |
+
"target": "AA"
|
| 262 |
+
},
|
| 263 |
+
{
|
| 264 |
+
"source": "P",
|
| 265 |
+
"target": "AB"
|
| 266 |
+
},
|
| 267 |
+
{
|
| 268 |
+
"source": "AC",
|
| 269 |
+
"target": "AD"
|
| 270 |
+
},
|
| 271 |
+
{
|
| 272 |
+
"source": "AC",
|
| 273 |
+
"target": "AE"
|
| 274 |
+
},
|
| 275 |
+
{
|
| 276 |
+
"source": "AC",
|
| 277 |
+
"target": "AF"
|
| 278 |
+
},
|
| 279 |
+
{
|
| 280 |
+
"source": "AC",
|
| 281 |
+
"target": "AG"
|
| 282 |
+
},
|
| 283 |
+
{
|
| 284 |
+
"source": "AH",
|
| 285 |
+
"target": "AI"
|
| 286 |
+
}
|
| 287 |
+
]
|
| 288 |
+
},
|
| 289 |
+
{
|
| 290 |
+
"type": "title",
|
| 291 |
+
"text": "功能描述"
|
| 292 |
+
},
|
| 293 |
+
{
|
| 294 |
+
"type": "title",
|
| 295 |
+
"text": "支持主流的密码协议和算法"
|
| 296 |
+
},
|
| 297 |
+
{
|
| 298 |
+
"type": "text",
|
| 299 |
+
"text": "支持国际主流及中国商用密码算法和协议,可根据场景需求选择合适的密码算法和协议。"
|
| 300 |
+
}
|
| 301 |
+
]
|
diagrams-and-tables/annotations/cn_diagram_46.json
ADDED
|
@@ -0,0 +1,105 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
[
|
| 2 |
+
{
|
| 3 |
+
"type": "header",
|
| 4 |
+
"text": "openEuler 技术白皮书"
|
| 5 |
+
},
|
| 6 |
+
{
|
| 7 |
+
"type": "text",
|
| 8 |
+
"text": "AI4C 的自动调优基于 OpenTuner (2015 Ansel et al.) 开发,通过插件驱动编译器采集优化特性相关参数信息,通过搜索算法调整关键决策参数(例如循环展开系数),通过插件注入编译过程修改决策,运行编译输出二进制获得反馈因子,迭代自动调优。"
|
| 9 |
+
},
|
| 10 |
+
{
|
| 11 |
+
"type": "text",
|
| 12 |
+
"text": "● 已集成一系列搜索算法,动态选择算法并共享搜索进;\n● 支持用户配置 yaml 自定义搜索空间和扩展底层搜索算法;\n● 支持细粒度代码块调优与粗粒度编译选项自动调优;\n● 在 cormark、dhrystone、Cbench 等 benchmark 上获得 3%~5% 不等的收益。"
|
| 13 |
+
},
|
| 14 |
+
{
|
| 15 |
+
"type": "diagram",
|
| 16 |
+
"nodes": [
|
| 17 |
+
{
|
| 18 |
+
"id": "A",
|
| 19 |
+
"text": "Source Code"
|
| 20 |
+
},
|
| 21 |
+
{
|
| 22 |
+
"id": "B",
|
| 23 |
+
"text": "Compiler"
|
| 24 |
+
},
|
| 25 |
+
{
|
| 26 |
+
"id": "C",
|
| 27 |
+
"text": "Applying Tuning Config"
|
| 28 |
+
},
|
| 29 |
+
{
|
| 30 |
+
"id": "D",
|
| 31 |
+
"text": "Recording Tuning Opportunity"
|
| 32 |
+
},
|
| 33 |
+
{
|
| 34 |
+
"id": "E",
|
| 35 |
+
"text": "Auto-Tuner"
|
| 36 |
+
},
|
| 37 |
+
{
|
| 38 |
+
"id": "F",
|
| 39 |
+
"text": "Search Driver"
|
| 40 |
+
},
|
| 41 |
+
{
|
| 42 |
+
"id": "G",
|
| 43 |
+
"text": "Profiler"
|
| 44 |
+
},
|
| 45 |
+
{
|
| 46 |
+
"id": "H",
|
| 47 |
+
"text": "Tuning Opportunities"
|
| 48 |
+
}
|
| 49 |
+
],
|
| 50 |
+
"relationships": [
|
| 51 |
+
{
|
| 52 |
+
"source": "A",
|
| 53 |
+
"target": "B"
|
| 54 |
+
},
|
| 55 |
+
{
|
| 56 |
+
"source": "B",
|
| 57 |
+
"target": "C"
|
| 58 |
+
},
|
| 59 |
+
{
|
| 60 |
+
"source": "B",
|
| 61 |
+
"target": "D"
|
| 62 |
+
},
|
| 63 |
+
{
|
| 64 |
+
"source": "B",
|
| 65 |
+
"target": "E",
|
| 66 |
+
"label": "yaml"
|
| 67 |
+
},
|
| 68 |
+
{
|
| 69 |
+
"source": "B",
|
| 70 |
+
"target": "G",
|
| 71 |
+
"label": "Binary"
|
| 72 |
+
},
|
| 73 |
+
{
|
| 74 |
+
"source": "C",
|
| 75 |
+
"target": "H"
|
| 76 |
+
},
|
| 77 |
+
{
|
| 78 |
+
"source": "E",
|
| 79 |
+
"target": "F"
|
| 80 |
+
},
|
| 81 |
+
{
|
| 82 |
+
"source": "F",
|
| 83 |
+
"target": "G",
|
| 84 |
+
"label": "feedback"
|
| 85 |
+
},
|
| 86 |
+
{
|
| 87 |
+
"source": "F",
|
| 88 |
+
"target": "H",
|
| 89 |
+
"label": "yaml"
|
| 90 |
+
}
|
| 91 |
+
]
|
| 92 |
+
},
|
| 93 |
+
{
|
| 94 |
+
"type": "title",
|
| 95 |
+
"text": "● AI 辅助编译优化(ACPO)"
|
| 96 |
+
},
|
| 97 |
+
{
|
| 98 |
+
"type": "text",
|
| 99 |
+
"text": "ACPO 提供全面的工具、库、算法,为编译器工程师提供简单易用的接口使用 AI 模型能力,替代或增强编译器中启发式优化决策算法。在编译器优化过程中,使用插件提取优化遍的输入结构化数据作为模型输入特征,getAdvice 运行预训练模型获得决策系数,编译器使用模型决策结果替代部分启发式决策,获得更好的性能。"
|
| 100 |
+
},
|
| 101 |
+
{
|
| 102 |
+
"type": "text",
|
| 103 |
+
"text": "■ 解耦编译器与 AI 模型和推理引擎,帮助算法开发者专注 AI 算法模型开发,简化模型应用成本,同时兼容多个编译器、模型、AI 推理框架等主流产品,提供 AI 模型的热更新能力;\n■ 实践落地 IPA Function Inline、RTL Loop Unroll 等不同优化阶段和优化过程,获得相对显著的收益。"
|
| 104 |
+
}
|
| 105 |
+
]
|
diagrams-and-tables/annotations/cn_diagram_47.json
ADDED
|
@@ -0,0 +1,204 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
[
|
| 2 |
+
{
|
| 3 |
+
"type": "header",
|
| 4 |
+
"text": "openEuler 技术白皮书"
|
| 5 |
+
},
|
| 6 |
+
{
|
| 7 |
+
"type": "diagram",
|
| 8 |
+
"nodes": [
|
| 9 |
+
{
|
| 10 |
+
"id": "A",
|
| 11 |
+
"text": "Program"
|
| 12 |
+
},
|
| 13 |
+
{
|
| 14 |
+
"id": "B",
|
| 15 |
+
"text": "Opt Passes"
|
| 16 |
+
},
|
| 17 |
+
{
|
| 18 |
+
"id": "C",
|
| 19 |
+
"text": "InlinerPass"
|
| 20 |
+
},
|
| 21 |
+
{
|
| 22 |
+
"id": "D",
|
| 23 |
+
"text": "FIModel::clearCache()"
|
| 24 |
+
},
|
| 25 |
+
{
|
| 26 |
+
"id": "E",
|
| 27 |
+
"text": "CollectFeatures\nclearFunctionLevel()"
|
| 28 |
+
},
|
| 29 |
+
{
|
| 30 |
+
"id": "F",
|
| 31 |
+
"text": "ModelDataFICollector\n(load ModelFile)"
|
| 32 |
+
},
|
| 33 |
+
{
|
| 34 |
+
"id": "G",
|
| 35 |
+
"text": "getAdvice"
|
| 36 |
+
},
|
| 37 |
+
{
|
| 38 |
+
"id": "H",
|
| 39 |
+
"text": "FIModel::invalidateCache()"
|
| 40 |
+
},
|
| 41 |
+
{
|
| 42 |
+
"id": "I",
|
| 43 |
+
"text": "Opt Passes"
|
| 44 |
+
},
|
| 45 |
+
{
|
| 46 |
+
"id": "J",
|
| 47 |
+
"text": "Executable"
|
| 48 |
+
},
|
| 49 |
+
{
|
| 50 |
+
"id": "K",
|
| 51 |
+
"text": "getAdvice"
|
| 52 |
+
},
|
| 53 |
+
{
|
| 54 |
+
"id": "L",
|
| 55 |
+
"text": "MDC->collectFeatures"
|
| 56 |
+
},
|
| 57 |
+
{
|
| 58 |
+
"id": "M",
|
| 59 |
+
"text": "FI->setMLCustomFeatures"
|
| 60 |
+
},
|
| 61 |
+
{
|
| 62 |
+
"id": "N",
|
| 63 |
+
"text": "FI->getAdvice"
|
| 64 |
+
},
|
| 65 |
+
{
|
| 66 |
+
"id": "O",
|
| 67 |
+
"text": "ShouldInline"
|
| 68 |
+
},
|
| 69 |
+
{
|
| 70 |
+
"id": "P",
|
| 71 |
+
"text": "trained ML model"
|
| 72 |
+
},
|
| 73 |
+
{
|
| 74 |
+
"id": "Q",
|
| 75 |
+
"text": "TF AOT Model"
|
| 76 |
+
},
|
| 77 |
+
{
|
| 78 |
+
"id": "R",
|
| 79 |
+
"text": "AOTModelRunner"
|
| 80 |
+
}
|
| 81 |
+
],
|
| 82 |
+
"relationships": [
|
| 83 |
+
{
|
| 84 |
+
"source": "A",
|
| 85 |
+
"target": "B"
|
| 86 |
+
},
|
| 87 |
+
{
|
| 88 |
+
"source": "B",
|
| 89 |
+
"target": "C"
|
| 90 |
+
},
|
| 91 |
+
{
|
| 92 |
+
"source": "C",
|
| 93 |
+
"target": "D"
|
| 94 |
+
},
|
| 95 |
+
{
|
| 96 |
+
"source": "C",
|
| 97 |
+
"target": "E"
|
| 98 |
+
},
|
| 99 |
+
{
|
| 100 |
+
"source": "C",
|
| 101 |
+
"target": "F"
|
| 102 |
+
},
|
| 103 |
+
{
|
| 104 |
+
"source": "C",
|
| 105 |
+
"target": "G"
|
| 106 |
+
},
|
| 107 |
+
{
|
| 108 |
+
"source": "C",
|
| 109 |
+
"target": "H"
|
| 110 |
+
},
|
| 111 |
+
{
|
| 112 |
+
"source": "C",
|
| 113 |
+
"target": "I"
|
| 114 |
+
},
|
| 115 |
+
{
|
| 116 |
+
"source": "D",
|
| 117 |
+
"target": "E"
|
| 118 |
+
},
|
| 119 |
+
{
|
| 120 |
+
"source": "E",
|
| 121 |
+
"target": "F"
|
| 122 |
+
},
|
| 123 |
+
{
|
| 124 |
+
"source": "F",
|
| 125 |
+
"target": "G"
|
| 126 |
+
},
|
| 127 |
+
{
|
| 128 |
+
"source": "G",
|
| 129 |
+
"target": "K",
|
| 130 |
+
"label": "Plugin"
|
| 131 |
+
},
|
| 132 |
+
{
|
| 133 |
+
"source": "H",
|
| 134 |
+
"target": "O",
|
| 135 |
+
"label": "Plugin"
|
| 136 |
+
},
|
| 137 |
+
{
|
| 138 |
+
"source": "I",
|
| 139 |
+
"target": "J"
|
| 140 |
+
},
|
| 141 |
+
{
|
| 142 |
+
"source": "K",
|
| 143 |
+
"target": "L"
|
| 144 |
+
},
|
| 145 |
+
{
|
| 146 |
+
"source": "K",
|
| 147 |
+
"target": "M"
|
| 148 |
+
},
|
| 149 |
+
{
|
| 150 |
+
"source": "K",
|
| 151 |
+
"target": "N"
|
| 152 |
+
},
|
| 153 |
+
{
|
| 154 |
+
"source": "K",
|
| 155 |
+
"target": "O"
|
| 156 |
+
},
|
| 157 |
+
{
|
| 158 |
+
"source": "L",
|
| 159 |
+
"target": "M"
|
| 160 |
+
},
|
| 161 |
+
{
|
| 162 |
+
"source": "M",
|
| 163 |
+
"target": "N"
|
| 164 |
+
},
|
| 165 |
+
{
|
| 166 |
+
"source": "N",
|
| 167 |
+
"target": "O"
|
| 168 |
+
},
|
| 169 |
+
{
|
| 170 |
+
"source": "N",
|
| 171 |
+
"target": "R"
|
| 172 |
+
},
|
| 173 |
+
{
|
| 174 |
+
"source": "P",
|
| 175 |
+
"target": "Q",
|
| 176 |
+
"label": "aot_compile_tf_model.py"
|
| 177 |
+
},
|
| 178 |
+
{
|
| 179 |
+
"source": "Q",
|
| 180 |
+
"target": "R"
|
| 181 |
+
}
|
| 182 |
+
]
|
| 183 |
+
},
|
| 184 |
+
{
|
| 185 |
+
"type": "title",
|
| 186 |
+
"text": "应用场景"
|
| 187 |
+
},
|
| 188 |
+
{
|
| 189 |
+
"type": "text",
|
| 190 |
+
"text": "AI4C 提供优化模型和调优插件实现不同应用的编译优化,支持开发者根据不同应用的性能瓶颈开发相应的优化模型,使用 AI4C 框架能力注入编译过程,实现性能提升,当前 AI4C 主要应用于数据库等互联网后端领域。"
|
| 191 |
+
},
|
| 192 |
+
{
|
| 193 |
+
"type": "text",
|
| 194 |
+
"text": "● RocksDB\n● MySQL\n● Doris\n● Nginx\n● Python\n● ..."
|
| 195 |
+
},
|
| 196 |
+
{
|
| 197 |
+
"type": "title",
|
| 198 |
+
"text": "RPM 国密签名支持"
|
| 199 |
+
},
|
| 200 |
+
{
|
| 201 |
+
"type": "text",
|
| 202 |
+
"text": "根据国内相关安全技术标准,在某些应用场景中需要采用国密算法实现对重要可执行程序来源的真实性和完整性保护。openEuler 当前采用 RPM 格式的软件包管理,软件包签名算法基于 openPGP 签名规范。openEuler 24.03 LTS SP1 版本基于 RPM 包管理机制扩展对于 SM2 签名算法和 SM3 摘要算法的支持。"
|
| 203 |
+
}
|
| 204 |
+
]
|
diagrams-and-tables/annotations/cn_diagram_48.json
ADDED
|
@@ -0,0 +1,111 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
[
|
| 2 |
+
{
|
| 3 |
+
"type": "header",
|
| 4 |
+
"text": "openEuler 技术白皮书"
|
| 5 |
+
},
|
| 6 |
+
{
|
| 7 |
+
"type": "title",
|
| 8 |
+
"text": "功能描述"
|
| 9 |
+
},
|
| 10 |
+
{
|
| 11 |
+
"type": "text",
|
| 12 |
+
"text": "本特性主要基于 RPM 组件以及其调用的 GnuPG2 签名工具,在现有 openPGP 签名体系的基础上,进行国密算法使能。特性涉及的软件包如下:"
|
| 13 |
+
},
|
| 14 |
+
{
|
| 15 |
+
"type": "diagram",
|
| 16 |
+
"nodes": [
|
| 17 |
+
{
|
| 18 |
+
"id": "A",
|
| 19 |
+
"text": "RPM"
|
| 20 |
+
},
|
| 21 |
+
{
|
| 22 |
+
"id": "B",
|
| 23 |
+
"text": "rpmsign"
|
| 24 |
+
},
|
| 25 |
+
{
|
| 26 |
+
"id": "C",
|
| 27 |
+
"text": "rpmkeys"
|
| 28 |
+
},
|
| 29 |
+
{
|
| 30 |
+
"id": "D",
|
| 31 |
+
"text": "rpm"
|
| 32 |
+
},
|
| 33 |
+
{
|
| 34 |
+
"id": "E",
|
| 35 |
+
"text": "GnuPG"
|
| 36 |
+
},
|
| 37 |
+
{
|
| 38 |
+
"id": "F",
|
| 39 |
+
"text": "gpg"
|
| 40 |
+
},
|
| 41 |
+
{
|
| 42 |
+
"id": "G",
|
| 43 |
+
"text": "openSSL"
|
| 44 |
+
},
|
| 45 |
+
{
|
| 46 |
+
"id": "H",
|
| 47 |
+
"text": "libcrypto"
|
| 48 |
+
}
|
| 49 |
+
],
|
| 50 |
+
"relationships": [
|
| 51 |
+
{
|
| 52 |
+
"source": "A",
|
| 53 |
+
"target": "B"
|
| 54 |
+
},
|
| 55 |
+
{
|
| 56 |
+
"source": "A",
|
| 57 |
+
"target": "C"
|
| 58 |
+
},
|
| 59 |
+
{
|
| 60 |
+
"source": "A",
|
| 61 |
+
"target": "D"
|
| 62 |
+
},
|
| 63 |
+
{
|
| 64 |
+
"source": "A",
|
| 65 |
+
"target": "E",
|
| 66 |
+
"label": "签名生成"
|
| 67 |
+
},
|
| 68 |
+
{
|
| 69 |
+
"source": "A",
|
| 70 |
+
"target": "G",
|
| 71 |
+
"label": "签名验证"
|
| 72 |
+
},
|
| 73 |
+
{
|
| 74 |
+
"source": "E",
|
| 75 |
+
"target": "F"
|
| 76 |
+
},
|
| 77 |
+
{
|
| 78 |
+
"source": "G",
|
| 79 |
+
"target": "H"
|
| 80 |
+
}
|
| 81 |
+
]
|
| 82 |
+
},
|
| 83 |
+
{
|
| 84 |
+
"type": "text",
|
| 85 |
+
"text": "在 RPM 软件包签名场景,用户可调用 gpg 命令生成 SM2 签名私钥和证书,并调用 rpmsign 命令为指定的 RPM 包添加基于 SM2+SM3 算法的数字签名。\n在 RPM 软件包验签场景,用户可调用 rpm 命令导入验签证书,并通过校验 RPM 包的数字签名信息从而验证软件包的真实性和完整性。"
|
| 86 |
+
},
|
| 87 |
+
{
|
| 88 |
+
"type": "title",
|
| 89 |
+
"text": "应用场景"
|
| 90 |
+
},
|
| 91 |
+
{
|
| 92 |
+
"type": "text",
|
| 93 |
+
"text": "用户可基于本特性提供的软件包国密签名/验签技术,构建基于国密算法的软件包验证能力,满足国内部分合规场景中的密码应用安全要求。"
|
| 94 |
+
},
|
| 95 |
+
{
|
| 96 |
+
"type": "title",
|
| 97 |
+
"text": "oneAPI 框架支持"
|
| 98 |
+
},
|
| 99 |
+
{
|
| 100 |
+
"type": "text",
|
| 101 |
+
"text": "Unified Acceleration Foundation (UXL) 正在推动构建开放的异构加速软件框架的标准化。其中oneAPI作为初始项目的目标是提供一种跨行业、开放、基于标准的统一编程模型,并为异构加速器(如 CPU、GPU、FPGA 和专用加速器)提供统一的开发体验。oneAPI 规范扩展了现有的开发者编程模型,通过并行编程语言 (Data Parallel C++) 或者一组加速软件库以及底层的硬件抽象接口 (Level Zero) 来支持跨架构的编程,从而支持多种加速硬件和处理器平台。为了提供兼容性并提高开发效率,oneAPI 规范基于行业标准,提供了多种开放的、跨平台和易用的开发者软件套件。"
|
| 102 |
+
},
|
| 103 |
+
{
|
| 104 |
+
"type": "title",
|
| 105 |
+
"text": "功能描述"
|
| 106 |
+
},
|
| 107 |
+
{
|
| 108 |
+
"type": "text",
|
| 109 |
+
"text": "为了在 openEuler 上完整的支持 oneAPI,我们从 openEuler 24.03 LTS 开始分别集成了"
|
| 110 |
+
}
|
| 111 |
+
]
|
diagrams-and-tables/annotations/cn_diagram_49.json
ADDED
|
@@ -0,0 +1,69 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
[
|
| 2 |
+
{
|
| 3 |
+
"type": "text",
|
| 4 |
+
"text": "因此,从移动智能终端安全实践来看,MCP、A2A、ANP 协议在身份认证设计、身份认证协议在终端场景下的适配、及授权机制三个维度仍有一定的完善空间。这些协议短板将直接影响移动智能终端场景下的 Agent 业务的安全程度,形成潜在的安全风险,例如:"
|
| 5 |
+
},
|
| 6 |
+
{
|
| 7 |
+
"type": "text",
|
| 8 |
+
"text": "○ 在终端内 Agent 协作场景下,身份认证适配不足可能引发身份仿冒风险、恶意 Agent 参与数据传输可能造成敏感数据篡改或数据泄露;"
|
| 9 |
+
},
|
| 10 |
+
{
|
| 11 |
+
"type": "text",
|
| 12 |
+
"text": "○ 当 Agent 调用终端工具与资源时,因缺乏针对性的身份认证方案,理论上存在非法 Agent 伪装系统组件的可能,进而威胁用户数据安全与设备稳定运行。"
|
| 13 |
+
},
|
| 14 |
+
{
|
| 15 |
+
"type": "text",
|
| 16 |
+
"text": "综上,为了加强移动智能终端上的 Agent 业务安全,需要从 Agent 身份校验和数据保护的思路出发,建设 Agent 可信身份基础设施。结合手机终端业务需求,可从三方面进行考虑,如图 5 所示。"
|
| 17 |
+
},
|
| 18 |
+
{
|
| 19 |
+
"type": "diagram_caption",
|
| 20 |
+
"text": "图 5 Agent 可信身份基础设施建设角度"
|
| 21 |
+
},
|
| 22 |
+
{
|
| 23 |
+
"type": "diagram",
|
| 24 |
+
"nodes": [
|
| 25 |
+
{
|
| 26 |
+
"id": "A",
|
| 27 |
+
"text": "Agent可信身份基础设施"
|
| 28 |
+
},
|
| 29 |
+
{
|
| 30 |
+
"id": "B",
|
| 31 |
+
"text": "身份防仿冒"
|
| 32 |
+
},
|
| 33 |
+
{
|
| 34 |
+
"id": "C",
|
| 35 |
+
"text": "数据防泄露"
|
| 36 |
+
},
|
| 37 |
+
{
|
| 38 |
+
"id": "D",
|
| 39 |
+
"text": "数据防篡改"
|
| 40 |
+
}
|
| 41 |
+
],
|
| 42 |
+
"relationships": [
|
| 43 |
+
{
|
| 44 |
+
"source": "A",
|
| 45 |
+
"target": "B"
|
| 46 |
+
},
|
| 47 |
+
{
|
| 48 |
+
"source": "A",
|
| 49 |
+
"target": "C"
|
| 50 |
+
},
|
| 51 |
+
{
|
| 52 |
+
"source": "A",
|
| 53 |
+
"target": "D"
|
| 54 |
+
}
|
| 55 |
+
]
|
| 56 |
+
},
|
| 57 |
+
{
|
| 58 |
+
"type": "text",
|
| 59 |
+
"text": "如图 6 所示,在 Agent 可信身份基础设施的身份防仿冒环节,核心是依托合规有效的数字证书对 Agent 可信身份进行全流程的注册与校验:注册阶段需将 Agent 的唯一身份标识、属性信息与数字证书进行绑定,确保身份信息的真实性与合规性;校验阶段则通过验证证书的有效期、颁发机构合法性、证书签名完整性等信息,核对 Agent 当前提交的身份信息与注册时绑定的身份信息是否一致,最终确认 Agent 身份的可信性,为后续的数据交互环节筑牢身份信任基础。"
|
| 60 |
+
},
|
| 61 |
+
{
|
| 62 |
+
"type": "text",
|
| 63 |
+
"text": "而针对数据防泄露与数据防篡改需求,其实施前提是 Agent 已通过前述的身份认证流程 —— 在确认 Agent 身份可信后,将采用安全强度符合行业规范与业务需求的密码算法套件(如包含对称加密算法、非对称加密算法、哈希算法的完整套件),对 Agent 与 Agent 之间、Agent 与工具或功能模块之间的全链路传输数据进行双重安全处理:一方面通过数据加密操作,将敏感传输数据转化为不可直接解读的密文,防止数据在传输过程中被未授权主体窃取、窥探,保障数据的机密性;另一方面通过数据签名操作,利用 Agent 的专属密钥"
|
| 64 |
+
},
|
| 65 |
+
{
|
| 66 |
+
"type": "page_number",
|
| 67 |
+
"text": "18"
|
| 68 |
+
}
|
| 69 |
+
]
|
diagrams-and-tables/annotations/cn_diagram_50.json
ADDED
|
@@ -0,0 +1,85 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
[
|
| 2 |
+
{
|
| 3 |
+
"type": "header",
|
| 4 |
+
"text": "移动 Agent 安全技术白皮书"
|
| 5 |
+
},
|
| 6 |
+
{
|
| 7 |
+
"type": "text",
|
| 8 |
+
"text": "对传输数据的哈希值进行签名,接收方通过验签可确认数据在传输过程中是否被篡改、替换或破坏,从而保障敏感数据的完整性,确保数据从发送端到接收端的一致性与可靠性。"
|
| 9 |
+
},
|
| 10 |
+
{
|
| 11 |
+
"type": "diagram_caption",
|
| 12 |
+
"text": "图 6 Agent 可信身份基础设施思路和措施"
|
| 13 |
+
},
|
| 14 |
+
{
|
| 15 |
+
"type": "diagram",
|
| 16 |
+
"nodes": [
|
| 17 |
+
{
|
| 18 |
+
"id": "A",
|
| 19 |
+
"text": "身份防仿冒"
|
| 20 |
+
},
|
| 21 |
+
{
|
| 22 |
+
"id": "B",
|
| 23 |
+
"text": "基于证书的Agent身份校验"
|
| 24 |
+
},
|
| 25 |
+
{
|
| 26 |
+
"id": "C",
|
| 27 |
+
"text": "数据防泄露"
|
| 28 |
+
},
|
| 29 |
+
{
|
| 30 |
+
"id": "D",
|
| 31 |
+
"text": "身份认证前提下的数据加密"
|
| 32 |
+
},
|
| 33 |
+
{
|
| 34 |
+
"id": "E",
|
| 35 |
+
"text": "数据防篡改"
|
| 36 |
+
},
|
| 37 |
+
{
|
| 38 |
+
"id": "F",
|
| 39 |
+
"text": "身份认证前提下的数据签名"
|
| 40 |
+
}
|
| 41 |
+
],
|
| 42 |
+
"relationships": [
|
| 43 |
+
{
|
| 44 |
+
"source": "A",
|
| 45 |
+
"target": "B"
|
| 46 |
+
},
|
| 47 |
+
{
|
| 48 |
+
"source": "C",
|
| 49 |
+
"target": "D"
|
| 50 |
+
},
|
| 51 |
+
{
|
| 52 |
+
"source": "E",
|
| 53 |
+
"target": "F"
|
| 54 |
+
}
|
| 55 |
+
]
|
| 56 |
+
},
|
| 57 |
+
{
|
| 58 |
+
"type": "text",
|
| 59 |
+
"text": "通过上述优化思路的落地,搭建可靠的 Agent 可信身份基础设施,既能广泛兼容多种异构智能体通信协议,又依托灵活架构具备协议扩展能力,破除不同类型终端 Agent 间的通信适配壁垒,为多场景交互奠定基础;在筑牢通信基础的同时,还会为终端智能体分配唯一身份标识,并搭配端到端全链路加密机制,实现从身份确认到数据传输的全链路可信,进一步强化现有协议在终端场景下的身份鉴权能力。在此过程中,基础设施严格遵循最小化信息披露原则,仅采集、传输业务必需信息,避免冗余数据暴露,切实保障用户隐私与数据安全;同时通过跨域的身份流转和数据全生命周期保护,实现 Agent 行为的透明可追溯。最终,这一系列作用将形成从身份验证到权限管控的完整安全链条,为终端 Agent 生态的健康发展提供有力支撑。"
|
| 60 |
+
},
|
| 61 |
+
{
|
| 62 |
+
"type": "title",
|
| 63 |
+
"text": "3.4 Agent 细粒度权限管理"
|
| 64 |
+
},
|
| 65 |
+
{
|
| 66 |
+
"type": "title",
|
| 67 |
+
"text": "3.4.1 Agent 行为分级"
|
| 68 |
+
},
|
| 69 |
+
{
|
| 70 |
+
"type": "text",
|
| 71 |
+
"text": "随着大模型智能体(AI Agent)技术的快速迭代,其在终端侧承担的任务能力越来越复杂,涉及跨应用操作、系统功能控制等多种行为。这种高度自动化、可组合、可自主规划的能力极大提升了智能体的可用性,但同时也让能力边界与行为安全变得愈发模糊。"
|
| 72 |
+
},
|
| 73 |
+
{
|
| 74 |
+
"type": "title",
|
| 75 |
+
"text": "3.4.1.1 Agent 行为能力分类"
|
| 76 |
+
},
|
| 77 |
+
{
|
| 78 |
+
"type": "text",
|
| 79 |
+
"text": "○ 感知能力:指 Agent 对系统状态(如 UI 结构、网络情况、传感器状态)的感知能力,为后续行为提供上下文支撑。\n○ 决策能力:指 Agent 根据感知输入、用户目标以及对话历史进行自主规划和多轮推理,决定下一步行动的能力。\n○ 记忆能力:指 Agent 在任务执行或对话中对用户信息、操作上下文等进行短期或长"
|
| 80 |
+
},
|
| 81 |
+
{
|
| 82 |
+
"type": "page_number",
|
| 83 |
+
"text": "19"
|
| 84 |
+
}
|
| 85 |
+
]
|