Update data model diagrams in Apache docs

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

@@ -235,7 +235,7 @@ Connection connection = DriverManager.getConnection(
 
 IoTDB supports **tree-to-table conversion**, as shown in the figure below:
 
-![](/img/tree-to-table-en-1.png)
+![](/img/data-modeling-new-1-en.png)
 
 This feature allows existing tree-model data to be transformed into table views. Users can then query the same dataset using either model. Detailed instructions are available in [Tree-to-Table View](../User-Manual/Tree-to-Table_apache.md). **Note**: SQL statements for creating tree-to-table views **must be executed in table mode**.
 
@@ -273,23 +273,23 @@ 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-new-1-en.png" alt="" style="width: 70%;"/>
+      <img src="/img/data-modeling-new-2-en.png" alt="" style="width: 70%;"/>
 </div>
 
 ##### 3.1.3.2 How to mode when there are no devices, only data points?
 
 - For example, in a monitoring system for a station, each data point has a unique number but does not correspond to any specific device.
 
 <div style="text-align: center;">
-      <img src="/img/Data-model-en02.png" alt="" style="width: 70%;"/>
+      <img src="/img/data-modeling-new-3.png" alt="" style="width: 70%;"/>
 </div>
 
 ##### 3.1.3.3 How to mode when a device has both sub-devices and data points?
 
 - For example, in an energy storage scenario, each layer of the structure monitors its voltage and current. The following mode approach can be used.
 
 <div style="text-align: center;">
-      <img src="/img/Data-model-en03.png" alt="" style="width: 70%;"/>
+      <img src="/img/data-modeling-new-4-en.png" alt="" style="width: 70%;"/>
 </div>
 
 
@@ -325,21 +325,21 @@ 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-new-2-en.png" alt="" style="width: 70%;"/>
+      <img src="/img/data-modeling-new-5-en.png" alt="" style="width: 70%;"/>
 </div>
 
 ##### 3.2.3.2 How to mode when there are no device identifier columns or attribute columns?
 
 - There is no limit to the number of columns; it can reach hundreds of thousands.
 
 <div style="text-align: center;">
-      <img src="/img/Data-model-en05.png" alt="" style="width: 70%;"/>
+      <img src="/img/data-modeling-new-6-en.png" alt="" style="width: 70%;"/>
 </div>
 
 ##### 3.2.3.3 How to mode when a device has both sub-devices and data points?
 
 - 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-new-3-en.png" alt="" style="width: 70%;"/>
+      <img src="/img/data-modeling-new-7-en.png" alt="" style="width: 70%;"/>
 </div>

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

@@ -239,7 +239,7 @@ Connection connection = DriverManager.getConnection(
 
 IoTDB supports **tree-to-table conversion**, as shown in the figure below:
 
-![](/img/tree-to-table-en-1.png)
+![](/img/data-modeling-new-1-en.png)
 
 This feature allows existing tree-model data to be transformed into table views. Users can then query the same dataset using either model. Detailed instructions are available in [Tree-to-Table View](../../latest-Table/User-Manual/Tree-to-Table_apache.md). **Note**: SQL statements for creating tree-to-table views **must be executed in table mode**.
 
@@ -278,23 +278,23 @@ 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-new-1-en.png" alt="" style="width: 70%;"/>
+      <img src="/img/data-modeling-new-2-en.png" alt="" style="width: 70%;"/>
 </div>
 
 ##### 3.1.3.2 How to  when there are no devices, only data points?
 
 - For example, in a monitoring system for a station, each data point has a unique number but does not correspond to any specific device.
 
 <div style="text-align: center;">
-      <img src="/img/Data-model-en02.png" alt="" style="width: 70%;"/>
+      <img src="/img/data-modeling-new-3.png" alt="" style="width: 70%;"/>
 </div>
 
 ##### 3.1.3.3 How to mode when a device has both sub-devices and data points?
 
 - For example, in an energy storage scenario, each layer of the structure monitors its voltage and current. The following mode approach can be used.
 
 <div style="text-align: center;">
-      <img src="/img/Data-model-en03.png" alt="" style="width: 70%;"/>
+      <img src="/img/data-modeling-new-4-en.png" alt="" style="width: 70%;"/>
 </div>
 
 
@@ -330,21 +330,21 @@ 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-new-2-en.png" alt="" style="width: 70%;"/>
+      <img src="/img/data-modeling-new-5-en.png" alt="" style="width: 70%;"/>
 </div>
 
 ##### 3.2.3.2 How to mode when there are no device identifier columns or attribute columns?
 
 - There is no limit to the number of columns; it can reach hundreds of thousands.
 
 <div style="text-align: center;">
-      <img src="/img/Data-model-en05.png" alt="" style="width: 70%;"/>
+      <img src="/img/data-modeling-new-6-en.png" alt="" style="width: 70%;"/>
 </div>
 
 ##### 3.2.3.3 How to mode when a device has both sub-devices and data points?
 
 - 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-new-3-en.png" alt="" style="width: 70%;"/>
+      <img src="/img/data-modeling-new-7-en.png" alt="" style="width: 70%;"/>
 </div>

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

@@ -235,7 +235,7 @@ Connection connection = DriverManager.getConnection(
 
 IoTDB supports **tree-to-table conversion**, as shown in the figure below:
 
-![](/img/tree-to-table-en-1.png)
+![](/img/data-modeling-new-1-en.png)
 
 This feature allows existing tree-model data to be transformed into table views. Users can then query the same dataset using either model. Detailed instructions are available in [Tree-to-Table View](../User-Manual/Tree-to-Table_apache.md). **Note**: SQL statements for creating tree-to-table views **must be executed in table mode**.
 
@@ -273,23 +273,23 @@ 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-new-1-en.png" alt="" style="width: 70%;"/>
+      <img src="/img/data-modeling-new-2-en.png" alt="" style="width: 70%;"/>
 </div>
 
 ##### 3.1.3.2 How to mode when there are no devices, only data points?
 
 - For example, in a monitoring system for a station, each data point has a unique number but does not correspond to any specific device.
 
 <div style="text-align: center;">
-      <img src="/img/Data-model-en02.png" alt="" style="width: 70%;"/>
+      <img src="/img/data-modeling-new-3.png" alt="" style="width: 70%;"/>
 </div>
 
 ##### 3.1.3.3 How to mode when a device has both sub-devices and data points?
 
 - For example, in an energy storage scenario, each layer of the structure monitors its voltage and current. The following mode approach can be used.
 
 <div style="text-align: center;">
-      <img src="/img/Data-model-en03.png" alt="" style="width: 70%;"/>
+      <img src="/img/data-modeling-new-4-en.png" alt="" style="width: 70%;"/>
 </div>
 
 
@@ -325,21 +325,21 @@ 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-new-2-en.png" alt="" style="width: 70%;"/>
+      <img src="/img/data-modeling-new-5-en.png" alt="" style="width: 70%;"/>
 </div>
 
 ##### 3.2.3.2 How to mode when there are no device identifier columns or attribute columns?
 
 - There is no limit to the number of columns; it can reach hundreds of thousands.
 
 <div style="text-align: center;">
-      <img src="/img/Data-model-en05.png" alt="" style="width: 70%;"/>
+      <img src="/img/data-modeling-new-6-en.png" alt="" style="width: 70%;"/>
 </div>
 
 ##### 3.2.3.3 How to mode when a device has both sub-devices and data points?
 
 - 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-new-3-en.png" alt="" style="width: 70%;"/>
+      <img src="/img/data-modeling-new-7-en.png" alt="" style="width: 70%;"/>
 </div>

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

@@ -239,7 +239,7 @@ Connection connection = DriverManager.getConnection(
 
 IoTDB supports **tree-to-table conversion**, as shown in the figure below:
 
-![](/img/tree-to-table-en-1.png)
+![](/img/data-modeling-new-1-en.png)
 
 This feature allows existing tree-model data to be transformed into table views. Users can then query the same dataset using either model. Detailed instructions are available in [Tree-to-Table View](../../latest-Table/User-Manual/Tree-to-Table_apache.md). **Note**: SQL statements for creating tree-to-table views **must be executed in table mode**.
 
@@ -278,23 +278,23 @@ 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-new-1-en.png" alt="" style="width: 70%;"/>
+      <img src="/img/data-modeling-new-2-en.png" alt="" style="width: 70%;"/>
 </div>
 
 ##### 3.1.3.2 How to  when there are no devices, only data points?
 
 - For example, in a monitoring system for a station, each data point has a unique number but does not correspond to any specific device.
 
 <div style="text-align: center;">
-      <img src="/img/Data-model-en02.png" alt="" style="width: 70%;"/>
+      <img src="/img/data-modeling-new-3.png" alt="" style="width: 70%;"/>
 </div>
 
 ##### 3.1.3.3 How to mode when a device has both sub-devices and data points?
 
 - For example, in an energy storage scenario, each layer of the structure monitors its voltage and current. The following mode approach can be used.
 
 <div style="text-align: center;">
-      <img src="/img/Data-model-en03.png" alt="" style="width: 70%;"/>
+      <img src="/img/data-modeling-new-4-en.png" alt="" style="width: 70%;"/>
 </div>
 
 
@@ -330,21 +330,21 @@ 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-new-2-en.png" alt="" style="width: 70%;"/>
+      <img src="/img/data-modeling-new-5-en.png" alt="" style="width: 70%;"/>
 </div>
 
 ##### 3.2.3.2 How to mode when there are no device identifier columns or attribute columns?
 
 - There is no limit to the number of columns; it can reach hundreds of thousands.
 
 <div style="text-align: center;">
-      <img src="/img/Data-model-en05.png" alt="" style="width: 70%;"/>
+      <img src="/img/data-modeling-new-6-en.png" alt="" style="width: 70%;"/>
 </div>
 
 ##### 3.2.3.3 How to mode when a device has both sub-devices and data points?
 
 - 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-new-3-en.png" alt="" style="width: 70%;"/>
+      <img src="/img/data-modeling-new-7-en.png" alt="" style="width: 70%;"/>
 </div>

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

@@ -235,7 +235,7 @@ Connection connection = DriverManager.getConnection(
 
 IoTDB 提供了树转表功能，如下图所示：
 
-![](/img/tree-to-table-1.png)
+![](/img/data-modeling-new-1.png)
 
 该功能支持通过创建表视图的方式，将已存在的树模型数据转化为表视图，进而通过表视图进行查询，实现了对同一份数据的树模型和表模型协同处理。更详细的功能介绍可参考[树转表视图](../User-Manual/Tree-to-Table_apache.md)，需要注意的是：​**创建树转表视图的 SQL 语句只允许在表模型下执行**​。
 
@@ -274,23 +274,23 @@ IoTDB 提供了树转表功能，如下图所示：
 - 如场景中不同类型的设备具备不同的层级路径和测点集合，可以在数据库节点下按设备类型创建分支。每种设备下可以有不同的测点结构。
 
 <div style="text-align: center;">
-      <img src="/img/data-model-new-1.png" alt="" style="width: 70%;"/>
+      <img src="/img/data-modeling-new-2.png" alt="" style="width: 70%;"/>
 </div>
 
 ##### 3.1.3.2 如果场景中没有设备，只有测点，如何建模？
 
 - 如场站的监控系统中，每个测点都有唯一编号，但无法对应到某些设备。
 
 <div style="text-align: center;">
-      <img src="/img/data-modeling04.png" alt="" style="width: 70%;"/>
+      <img src="/img/data-modeling-new-3.png" alt="" style="width: 70%;"/>
 </div>
 
 ##### 3.1.3.3 如果在一个设备下，既有子设备，也有测点，如何建模？
 
 - 如在储能场景中，每一层结构都要监控其电压和电流，可以采用如下建模方式。
 
 <div style="text-align: center;">
-      <img src="/img/Modeling-scheme05.png" alt="" style="width: 70%;"/>
+      <img src="/img/data-modeling-new-4.png" alt="" style="width: 70%;"/>
 </div>
 
 
@@ -326,21 +326,21 @@ IoTDB 提供了树转表功能，如下图所示：
 - 即使设备之间有联系，或有层级关系，也推荐为每一类设备建一张表。
 
 <div style="text-align: center;">
-      <img src="/img/data-model-new-2.png" alt="" style="width: 70%;"/>
+      <img src="/img/data-modeling-new-5.png" alt="" style="width: 70%;"/>
 </div>
 
 ##### 3.2.3.2 如果没有设备标识列和属性列，如何建模？
 
 - 列数没有数量限制，可以达到数十万以上。
 
 <div style="text-align: center;">
-      <img src="/img/data-modeling07.png" alt="" style="width: 70%;"/>
+      <img src="/img/data-modeling-new-6.png" alt="" style="width: 70%;"/>
 </div>
 
 ##### 3.2.3.3 如果在一个设备下，既有子设备，也有测点，如何建模？
 
 - 每个设备有多个子设备及测点信息，推荐为每类设备建一个表进行管理。
 
 <div style="text-align: center;">
-      <img src="/img/data-model-new-3.png" alt="" style="width: 70%;"/>
+      <img src="/img/data-modeling-new-7.png" alt="" style="width: 70%;"/>
 </div>

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

@@ -238,7 +238,7 @@ Connection connection = DriverManager.getConnection(
 
 IoTDB 提供了树转表功能，如下图所示：
 
-![](/img/tree-to-table-1.png)
+![](/img/data-modeling-new-1.png)
 
 该功能支持通过创建表视图的方式，将已存在的树模型数据转化为表视图，进而通过表视图进行查询，实现了对同一份数据的树模型和表模型协同处理。更详细的功能介绍可参考[树转表视图](../../latest-Table/User-Manual/Tree-to-Table_apache.md)，需要注意的是：​**创建树转表视图的 SQL 语句只允许在表模型下执行**​。
 
@@ -278,23 +278,23 @@ IoTDB 提供了树转表功能，如下图所示：
 - 如场景中不同类型的设备具备不同的层级路径和测点集合，可以在数据库节点下按设备类型创建分支。每种设备下可以有不同的测点结构。
 
 <div style="text-align: center;">
-      <img src="/img/data-model-new-1.png" alt="" style="width: 70%;"/>
+      <img src="/img/data-modeling-new-2.png" alt="" style="width: 70%;"/>
 </div>
 
 ##### 3.1.3.2 如果场景中没有设备，只有测点，如何建模？
 
 - 如场站的监控系统中，每个测点都有唯一编号，但无法对应到某些设备。
 
 <div style="text-align: center;">
-      <img src="/img/data-modeling04.png" alt="" style="width: 70%;"/>
+      <img src="/img/data-modeling-new-3.png" alt="" style="width: 70%;"/>
 </div>
 
 ##### 3.1.3.3 如果在一个设备下，既有子设备，也有测点，如何建模？
 
 - 如在储能场景中，每一层结构都要监控其电压和电流，可以采用如下建模方式。
 
 <div style="text-align: center;">
-      <img src="/img/Modeling-scheme05.png" alt="" style="width: 70%;"/>
+      <img src="/img/data-modeling-new-4.png" alt="" style="width: 70%;"/>
 </div>
 
 
@@ -330,21 +330,21 @@ IoTDB 提供了树转表功能，如下图所示：
 - 即使设备之间有联系，或有层级关系，也推荐为每一类设备建一张表。
 
 <div style="text-align: center;">
-      <img src="/img/data-model-new-2.png" alt="" style="width: 70%;"/>
+      <img src="/img/data-modeling-new-5.png" alt="" style="width: 70%;"/>
 </div>
 
 ##### 3.2.3.2 如果没有设备标识列和属性列，如何建模？
 
 - 列数没有数量限制，可以达到数十万以上。
 
 <div style="text-align: center;">
-      <img src="/img/data-modeling07.png" alt="" style="width: 70%;"/>
+      <img src="/img/data-modeling-new-6.png" alt="" style="width: 70%;"/>
 </div>
 
 ##### 3.2.3.3 如果在一个设备下，既有子设备，也有测点，如何建模？
 
 - 每个设备有多个子设备及测点信息，推荐为每类设备建一个表进行管理。
 
 <div style="text-align: center;">
-      <img src="/img/data-model-new-3.png" alt="" style="width: 70%;"/>
+      <img src="/img/data-modeling-new-7.png" alt="" style="width: 70%;"/>
 </div>