update pictures in data model

src/UserGuide/Master/Table/Background-knowledge/Data-Model-and-Terminology_apache.md

@@ -113,7 +113,7 @@ The application scenarios mainly include two categories:
 - If different types of devices in the scenario have different hierarchical paths and data point sets, create branches under the database node by device type. Each device type can have a different data point structure.
 
 <div style="text-align: center;">
-      <img src="/img/Data-model-en-11.png" alt="" style="width: 70%;"/>
+      <img src="/img/data-model-new-1-en.png" alt="" style="width: 70%;"/>
 </div>
 
 ##### 3.1.3.2 How to model when there are no devices, only data points?
@@ -165,7 +165,7 @@ The application scenarios mainly include two categories:
 - Even if devices are related or have hierarchical relationships, it is recommended to create a table for each type of device.
 
 <div style="text-align: center;">
-      <img src="/img/Data-model-en04.png" alt="" style="width: 70%;"/>
+      <img src="/img/data-model-new-2-en.png" alt="" style="width: 70%;"/>
 </div>
 
 ##### 3.2.3.2 How to model when there are no device identifier columns or attribute columns?
@@ -181,5 +181,5 @@ The application scenarios mainly include two categories:
 - Each device has multiple sub-devices and data point information. It is recommended to create a table for each type of device for management.
 
 <div style="text-align: center;">
-      <img src="/img/Data-model-en06.png" alt="" style="width: 70%;"/>
+      <img src="/img/data-model-new-3-en.png" alt="" style="width: 70%;"/>
 </div>

src/UserGuide/Master/Table/Background-knowledge/Data-Model-and-Terminology_timecho.md

@@ -115,7 +115,7 @@ The application scenarios mainly include three categories:
 - If different types of devices in the scenario have different hierarchical paths and data point sets, create branches under the database node by device type. Each device type can have a different data point structure.
 
 <div style="text-align: center;">
-      <img src="/img/Data-model-en-11.png" alt="" style="width: 70%;"/>
+      <img src="/img/data-model-new-1-en.png" alt="" style="width: 70%;"/>
 </div>
 
 ##### 3.1.3.2 How to model when there are no devices, only data points?
@@ -167,7 +167,7 @@ The application scenarios mainly include three categories:
 - Even if devices are related or have hierarchical relationships, it is recommended to create a table for each type of device.
 
 <div style="text-align: center;">
-      <img src="/img/Data-model-en04.png" alt="" style="width: 70%;"/>
+      <img src="/img/data-model-new-2-en.png" alt="" style="width: 70%;"/>
 </div>
 
 ##### 3.2.3.2 How to model when there are no device identifier columns or attribute columns?
@@ -183,7 +183,7 @@ The application scenarios mainly include three categories:
 - Each device has multiple sub-devices and data point information. It is recommended to create a table for each type of device for management.
 
 <div style="text-align: center;">
-      <img src="/img/Data-model-en06.png" alt="" style="width: 70%;"/>
+      <img src="/img/data-model-new-3-en.png" alt="" style="width: 70%;"/>
 </div>
 
 ### 3.3 Scenario 3: Dual-Model Integration
@@ -207,7 +207,7 @@ The application scenarios mainly include three categories:
 - **Table View**T: Create a table view for each type of device, with each table view having different tags and data point sets.
 
 <div style="text-align: center;">
-      <img src="/img/Data-model-en-10.png" alt="" style="width: 70%;"/>
+      <img src="/img/data-model-new-4-en.png" alt="" style="width: 70%;"/>
 </div>
 
 ##### 3.3.2.2 How to model when there are no device identifier columns or attribute columns?
@@ -225,5 +225,5 @@ The application scenarios mainly include three categories:
 - **Table View**: Create multiple tables to manage each layer of structural information according to device classification.
 
 <div style="text-align: center;">
-      <img src="/img/Data-model-en09.png" alt="" style="width: 70%;"/>
+      <img src="/img/data-model-new-5-en.png" alt="" style="width: 70%;"/>
 </div>

src/UserGuide/Master/Tree/Background-knowledge/Data-Model-and-Terminology_apache.md

@@ -115,7 +115,7 @@ The application scenarios mainly include two categories:
 - If different types of devices in the scenario have different hierarchical paths and data point sets, create branches under the database node by device type. Each device type can have a different data point structure.
 
 <div style="text-align: center;">
-      <img src="/img/Data-model-en-11.png" alt="" style="width: 70%;"/>
+      <img src="/img/data-model-new-1-en.png" alt="" style="width: 70%;"/>
 </div>
 
 ##### 3.1.3.2 How to model when there are no devices, only data points?
@@ -167,7 +167,7 @@ The application scenarios mainly include two categories:
 - Even if devices are related or have hierarchical relationships, it is recommended to create a table for each type of device.
 
 <div style="text-align: center;">
-      <img src="/img/Data-model-en04.png" alt="" style="width: 70%;"/>
+      <img src="/img/data-model-new-2-en.png" alt="" style="width: 70%;"/>
 </div>
 
 ##### 3.2.3.2 How to model when there are no device identifier columns or attribute columns?
@@ -183,5 +183,5 @@ The application scenarios mainly include two categories:
 - Each device has multiple sub-devices and data point information. It is recommended to create a table for each type of device for management.
 
 <div style="text-align: center;">
-      <img src="/img/Data-model-en06.png" alt="" style="width: 70%;"/>
+      <img src="/img/data-model-new-3-en.png" alt="" style="width: 70%;"/>
 </div>

src/UserGuide/Master/Tree/Background-knowledge/Data-Model-and-Terminology_timecho.md

@@ -117,7 +117,7 @@ The application scenarios mainly include three categories:
 - If different types of devices in the scenario have different hierarchical paths and data point sets, create branches under the database node by device type. Each device type can have a different data point structure.
 
 <div style="text-align: center;">
-      <img src="/img/Data-model-en-11.png" alt="" style="width: 70%;"/>
+      <img src="/img/data-model-new-1-en.png" alt="" style="width: 70%;"/>
 </div>
 
 ##### 3.1.3.2 How to model when there are no devices, only data points?
@@ -169,7 +169,7 @@ The application scenarios mainly include three categories:
 - Even if devices are related or have hierarchical relationships, it is recommended to create a table for each type of device.
 
 <div style="text-align: center;">
-      <img src="/img/Data-model-en04.png" alt="" style="width: 70%;"/>
+      <img src="/img/data-model-new-2-en.png" alt="" style="width: 70%;"/>
 </div>
 
 ##### 3.2.3.2 How to model when there are no device identifier columns or attribute columns?
@@ -185,7 +185,7 @@ The application scenarios mainly include three categories:
 - Each device has multiple sub-devices and data point information. It is recommended to create a table for each type of device for management.
 
 <div style="text-align: center;">
-      <img src="/img/Data-model-en06.png" alt="" style="width: 70%;"/>
+      <img src="/img/data-model-new-3-en.png" alt="" style="width: 70%;"/>
 </div>
 
 ### 3.3 Scenario 3: Dual-Model Integration
@@ -209,7 +209,7 @@ The application scenarios mainly include three categories:
 - **Table View**T: Create a table view for each type of device, with each table view having different tags and data point sets.
 
 <div style="text-align: center;">
-      <img src="/img/Data-model-en-10.png" alt="" style="width: 70%;"/>
+      <img src="/img/data-model-new-4-en.png" alt="" style="width: 70%;"/>
 </div>
 
 ##### 3.3.2.2 How to model when there are no device identifier columns or attribute columns?
@@ -227,5 +227,5 @@ The application scenarios mainly include three categories:
 - **Table View**: Create multiple tables to manage each layer of structural information according to device classification.
 
 <div style="text-align: center;">
-      <img src="/img/Data-model-en09.png" alt="" style="width: 70%;"/>
+      <img src="/img/data-model-new-5-en.png" alt="" style="width: 70%;"/>
 </div>

src/UserGuide/latest-Table/Background-knowledge/Data-Model-and-Terminology_apache.md

@@ -113,7 +113,7 @@ The application scenarios mainly include two categories:
 - If different types of devices in the scenario have different hierarchical paths and data point sets, create branches under the database node by device type. Each device type can have a different data point structure.
 
 <div style="text-align: center;">
-      <img src="/img/Data-model-en-11.png" alt="" style="width: 70%;"/>
+      <img src="/img/data-model-new-1-en.png" alt="" style="width: 70%;"/>
 </div>
 
 ##### 3.1.3.2 How to model when there are no devices, only data points?
@@ -165,7 +165,7 @@ The application scenarios mainly include two categories:
 - Even if devices are related or have hierarchical relationships, it is recommended to create a table for each type of device.
 
 <div style="text-align: center;">
-      <img src="/img/Data-model-en04.png" alt="" style="width: 70%;"/>
+      <img src="/img/data-model-new-2-en.png" alt="" style="width: 70%;"/>
 </div>
 
 ##### 3.2.3.2 How to model when there are no device identifier columns or attribute columns?
@@ -181,5 +181,5 @@ The application scenarios mainly include two categories:
 - Each device has multiple sub-devices and data point information. It is recommended to create a table for each type of device for management.
 
 <div style="text-align: center;">
-      <img src="/img/Data-model-en06.png" alt="" style="width: 70%;"/>
+      <img src="/img/data-model-new-3-en.png" alt="" style="width: 70%;"/>
 </div>

src/UserGuide/latest-Table/Background-knowledge/Data-Model-and-Terminology_timecho.md

@@ -115,7 +115,7 @@ The application scenarios mainly include three categories:
 - If different types of devices in the scenario have different hierarchical paths and data point sets, create branches under the database node by device type. Each device type can have a different data point structure.
 
 <div style="text-align: center;">
-      <img src="/img/Data-model-en-11.png" alt="" style="width: 70%;"/>
+      <img src="/img/data-model-new-1-en.png" alt="" style="width: 70%;"/>
 </div>
 
 ##### 3.1.3.2 How to model when there are no devices, only data points?
@@ -167,7 +167,7 @@ The application scenarios mainly include three categories:
 - Even if devices are related or have hierarchical relationships, it is recommended to create a table for each type of device.
 
 <div style="text-align: center;">
-      <img src="/img/Data-model-en04.png" alt="" style="width: 70%;"/>
+      <img src="/img/data-model-new-2-en.png" alt="" style="width: 70%;"/>
 </div>
 
 ##### 3.2.3.2 How to model when there are no device identifier columns or attribute columns?
@@ -183,7 +183,7 @@ The application scenarios mainly include three categories:
 - Each device has multiple sub-devices and data point information. It is recommended to create a table for each type of device for management.
 
 <div style="text-align: center;">
-      <img src="/img/Data-model-en06.png" alt="" style="width: 70%;"/>
+      <img src="/img/data-model-new-3-en.png" alt="" style="width: 70%;"/>
 </div>
 
 ### 3.3 Scenario 3: Dual-Model Integration
@@ -207,7 +207,7 @@ The application scenarios mainly include three categories:
 - **Table View**T: Create a table view for each type of device, with each table view having different tags and data point sets.
 
 <div style="text-align: center;">
-      <img src="/img/Data-model-en-10.png" alt="" style="width: 70%;"/>
+      <img src="/img/data-model-new-4-en.png" alt="" style="width: 70%;"/>
 </div>
 
 ##### 3.3.2.2 How to model when there are no device identifier columns or attribute columns?
@@ -225,5 +225,5 @@ The application scenarios mainly include three categories:
 - **Table View**: Create multiple tables to manage each layer of structural information according to device classification.
 
 <div style="text-align: center;">
-      <img src="/img/Data-model-en09.png" alt="" style="width: 70%;"/>
+      <img src="/img/data-model-new-5-en.png" alt="" style="width: 70%;"/>
 </div>

src/UserGuide/latest/Background-knowledge/Data-Model-and-Terminology_apache.md

@@ -115,7 +115,7 @@ The application scenarios mainly include two categories:
 - If different types of devices in the scenario have different hierarchical paths and data point sets, create branches under the database node by device type. Each device type can have a different data point structure.
 
 <div style="text-align: center;">
-      <img src="/img/Data-model-en-11.png" alt="" style="width: 70%;"/>
+      <img src="/img/data-model-new-1-en.png" alt="" style="width: 70%;"/>
 </div>
 
 ##### 3.1.3.2 How to model when there are no devices, only data points?
@@ -167,7 +167,7 @@ The application scenarios mainly include two categories:
 - Even if devices are related or have hierarchical relationships, it is recommended to create a table for each type of device.
 
 <div style="text-align: center;">
-      <img src="/img/Data-model-en04.png" alt="" style="width: 70%;"/>
+      <img src="/img/data-model-new-2-en.png" alt="" style="width: 70%;"/>
 </div>
 
 ##### 3.2.3.2 How to model when there are no device identifier columns or attribute columns?
@@ -183,5 +183,5 @@ The application scenarios mainly include two categories:
 - Each device has multiple sub-devices and data point information. It is recommended to create a table for each type of device for management.
 
 <div style="text-align: center;">
-      <img src="/img/Data-model-en06.png" alt="" style="width: 70%;"/>
+      <img src="/img/data-model-new-3-en.png" alt="" style="width: 70%;"/>
 </div>

src/UserGuide/latest/Background-knowledge/Data-Model-and-Terminology_timecho.md

@@ -117,7 +117,7 @@ The application scenarios mainly include three categories:
 - If different types of devices in the scenario have different hierarchical paths and data point sets, create branches under the database node by device type. Each device type can have a different data point structure.
 
 <div style="text-align: center;">
-      <img src="/img/Data-model-en-11.png" alt="" style="width: 70%;"/>
+      <img src="/img/data-model-new-1-en.png" alt="" style="width: 70%;"/>
 </div>
 
 ##### 3.1.3.2 How to model when there are no devices, only data points?
@@ -169,7 +169,7 @@ The application scenarios mainly include three categories:
 - Even if devices are related or have hierarchical relationships, it is recommended to create a table for each type of device.
 
 <div style="text-align: center;">
-      <img src="/img/Data-model-en04.png" alt="" style="width: 70%;"/>
+      <img src="/img/data-model-new-2-en.png" alt="" style="width: 70%;"/>
 </div>
 
 ##### 3.2.3.2 How to model when there are no device identifier columns or attribute columns?
@@ -185,7 +185,7 @@ The application scenarios mainly include three categories:
 - Each device has multiple sub-devices and data point information. It is recommended to create a table for each type of device for management.
 
 <div style="text-align: center;">
-      <img src="/img/Data-model-en06.png" alt="" style="width: 70%;"/>
+      <img src="/img/data-model-new-3-en.png" alt="" style="width: 70%;"/>
 </div>
 
 ### 3.3 Scenario 3: Dual-Model Integration
@@ -209,7 +209,7 @@ The application scenarios mainly include three categories:
 - **Table View**T: Create a table view for each type of device, with each table view having different tags and data point sets.
 
 <div style="text-align: center;">
-      <img src="/img/Data-model-en-10.png" alt="" style="width: 70%;"/>
+      <img src="/img/data-model-new-4-en.png" alt="" style="width: 70%;"/>
 </div>
 
 ##### 3.3.2.2 How to model when there are no device identifier columns or attribute columns?
@@ -227,5 +227,5 @@ The application scenarios mainly include three categories:
 - **Table View**: Create multiple tables to manage each layer of structural information according to device classification.
 
 <div style="text-align: center;">
-      <img src="/img/Data-model-en09.png" alt="" style="width: 70%;"/>
+      <img src="/img/data-model-new-5-en.png" alt="" style="width: 70%;"/>
 </div>

src/zh/UserGuide/Master/Table/Background-knowledge/Data-Model-and-Terminology_apache.md

@@ -114,7 +114,7 @@ IoTDB 提供了两种数据建模方式——树模型和表模型，其特点
 - 如场景中不同类型的设备具备不同的层级路径和测点集合，可以在数据库节点下按设备类型创建分支。每种设备下可以有不同的测点结构。
 
 <div style="text-align: center;">
-      <img src="/img/Data-model-02.png" alt="" style="width: 70%;"/>
+      <img src="/img/data-model-new-1.png" alt="" style="width: 70%;"/>
 </div>
 
 ##### 3.1.3.2 如果场景中没有设备，只有测点，如何建模？
@@ -166,7 +166,7 @@ IoTDB 提供了两种数据建模方式——树模型和表模型，其特点
 - 即使设备之间有联系，或有层级关系，也推荐为每一类设备建一张表。
 
 <div style="text-align: center;">
-      <img src="/img/data-modeling06.png" alt="" style="width: 70%;"/>
+      <img src="/img/ddata-model-new-2.png" alt="" style="width: 70%;"/>
 </div>
 
 ##### 3.2.3.2 如果没有设备标识列和属性列，如何建模？
@@ -182,5 +182,5 @@ IoTDB 提供了两种数据建模方式——树模型和表模型，其特点
 - 每个设备有多个子设备及测点信息，推荐为每类设备建一个表进行管理。
 
 <div style="text-align: center;">
-      <img src="/img/Modeling-scheme06.png" alt="" style="width: 70%;"/>
+      <img src="/img/data-model-new-3.png" alt="" style="width: 70%;"/>
 </div>

src/zh/UserGuide/Master/Table/Background-knowledge/Data-Model-and-Terminology_timecho.md

@@ -115,7 +115,7 @@ IoTDB 提供了两种数据建模方式——树模型和表模型，其特点
 - 如场景中不同类型的设备具备不同的层级路径和测点集合，可以在数据库节点下按设备类型创建分支。每种设备下可以有不同的测点结构。
 
 <div style="text-align: center;">
-      <img src="/img/Data-model-02.png" alt="" style="width: 70%;"/>
+      <img src="/img/data-model-new-1.png" alt="" style="width: 70%;"/>
 </div>
 
 ##### 3.1.3.2 如果场景中没有设备，只有测点，如何建模？
@@ -167,7 +167,7 @@ IoTDB 提供了两种数据建模方式——树模型和表模型，其特点
 - 即使设备之间有联系，或有层级关系，也推荐为每一类设备建一张表。
 
 <div style="text-align: center;">
-      <img src="/img/data-modeling06.png" alt="" style="width: 70%;"/>
+      <img src="/img/data-model-new-2.png" alt="" style="width: 70%;"/>
 </div>
 
 ##### 3.2.3.2 如果没有设备标识列和属性列，如何建模？
@@ -183,7 +183,7 @@ IoTDB 提供了两种数据建模方式——树模型和表模型，其特点
 - 每个设备有多个子设备及测点信息，推荐为每类设备建一个表进行管理。
 
 <div style="text-align: center;">
-      <img src="/img/Modeling-scheme06.png" alt="" style="width: 70%;"/>
+      <img src="/img/data-model-new-3.png" alt="" style="width: 70%;"/>
 </div>
 
 ### 3.3 场景三：双模型结合
@@ -207,7 +207,7 @@ IoTDB 提供了两种数据建模方式——树模型和表模型，其特点
 - 表视图：为每种类型的设备建立一张表视图，每个表视图具有不同的标签和测点集合。
 
 <div style="text-align: center;">
-      <img src="/img/Data-model-01.png" alt="" style="width: 70%;"/>
+      <img src="/img/data-model-new-4.png" alt="" style="width: 70%;"/>
 </div>
 
 ##### 3.3.2.2 如果没有设备标识列和属性列，如何建模？
@@ -227,5 +227,5 @@ IoTDB 提供了两种数据建模方式——树模型和表模型，其特点
 - 表视图：按照设备分类，建立多个表对每一层结构信息进行管理。
 
 <div style="text-align: center;">
-      <img src="/img/Modeling-scheme03.png" alt="" style="width: 70%;"/>
+      <img src="/img/data-model-new-5.png" alt="" style="width: 70%;"/>
 </div>