update data modeling picture

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/Table/Background-knowledge/Data-Model-and-Terminology_timecho.md

@@ -234,7 +234,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_timecho.md). **Note**: SQL statements for creating tree-to-table views **must be executed in table mode**.
 
@@ -274,23 +274,23 @@ 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-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>
 
 
@@ -326,23 +326,23 @@ 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-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>
 
 ### 3.3 Scenario 3: Dual-Mode Integration
@@ -366,7 +366,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-new-4-en.png" alt="" style="width: 70%;"/>
+      <img src="/img/data-modeling-new-8-en.png" alt="" style="width: 70%;"/>
 </div>
 
 ##### 3.3.2.2 How to mode when there are no device identifier columns or attribute columns?
@@ -375,7 +375,7 @@ The application scenarios mainly include three categories:
 - **Table View**: Place all data points into a single table. There is no limit to the number of data point columns; it can reach hundreds of thousands. If data points have the same data type, they can be treated as the same type of device.
 
 <div style="text-align: center;">
-      <img src="/img/Data-model-en08.png" alt="" style="width: 70%;"/>
+      <img src="/img/data-modeling-new-9-en.png" alt="" style="width: 70%;"/>
 </div>
 
 ##### 3.3.2.3 How to mode when a device has both sub-devices and data points?
@@ -384,5 +384,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-new-5-en.png" alt="" style="width: 70%;"/>
+      <img src="/img/data-modeling-new-10-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/Master/Tree/Background-knowledge/Data-Model-and-Terminology_timecho.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_timecho.md). **Note**: SQL statements for creating tree-to-table views **must be executed in table mode**.
 
@@ -279,23 +279,23 @@ 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-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>
 
 
@@ -331,23 +331,23 @@ 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-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>
 
 ### 3.3 Scenario 3: Dual-Mode Integration
@@ -371,7 +371,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-new-4-en.png" alt="" style="width: 70%;"/>
+      <img src="/img/data-modeling-new-8-en.png" alt="" style="width: 70%;"/>
 </div>
 
 ##### 3.3.2.2 How to mode when there are no device identifier columns or attribute columns?
@@ -380,7 +380,7 @@ The application scenarios mainly include three categories:
 - **Table View**: Place all data points into a single table. There is no limit to the number of data point columns; it can reach hundreds of thousands. If data points have the same data type, they can be treated as the same type of device.
 
 <div style="text-align: center;">
-      <img src="/img/Data-model-en08.png" alt="" style="width: 70%;"/>
+      <img src="/img/data-modeling-new-9-en.png" alt="" style="width: 70%;"/>
 </div>
 
 ##### 3.3.2.3 How to mode when a device has both sub-devices and data points?
@@ -389,5 +389,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-new-5-en.png" alt="" style="width: 70%;"/>
+      <img src="/img/data-modeling-new-10-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>