Component data acquisition system and method oriented to two-stage database dynamic interaction
Through component development technology, a dynamic interactive data acquisition system for two-level databases has been constructed, which solves the problem that existing systems are difficult to meet the needs of diversified data acquisition and realizes efficient data acquisition and management.
Patent Information
- Application Number
- CN202411345287.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-09-25
- Publication Date
- 2025-02-14
AI Technical Summary
The existing data acquisition system is difficult to meet the troops' diverse combat data acquisition needs, and the acquisition efficiency is low and dependent on manual operations.
Using component development technology, a dynamic interactive system for two-level databases is built, including server terminals and handheld terminals. Through the visual construction of data components and distributed design, data collection, transmission and analysis are realized.
It improves the efficiency of data collection and management, adapts to the wide geographical and multi-point characteristics of training data collection, and realizes the rapid recycling and storage of various on-site data.
Smart Images

Figure CN119441175A_ABST
Abstract
Description
Technical Field
[0001] The present invention belongs to the technical field of componentized data collection, and in particular relates to a componentized data collection system and method for dynamic interaction of two-level databases. Background Art
[0002] With the continuous development and application of big data technology, military data plays an increasingly important role in combat decision-making support, military training planning, weapons and equipment management, and other aspects. All countries have regarded military data as an important strategic resource. However, the military training activities cover a wide geographical range, the types of equipment used are diverse, and the combat operations are complex and changeable. It is very difficult to comprehensively collect all kinds of combat data. Commonly used data collection systems basically collect a certain type of data for a certain equipment or device, which is difficult to meet the requirements of the troops for various data collection. At present, combat data collection is still mainly manual, the preparation of data collection tables is cumbersome, and the efficiency of on-site collection is low. Summary of the invention
[0003] In view of the above problems, the present invention applies component development technology, constructs various data components, and develops a componentized data acquisition system and method for dynamic interaction of two-level databases, which can provide technical support in data acquisition table compilation, data acquisition, data transmission, data visualization analysis, etc.
[0004] The present invention adopts the following technical scheme to achieve: a componentized data acquisition system for dynamic interaction of two-level databases, comprising: a server terminal, deployed in a command center; the server terminal is configured to select corresponding data components to form callable data type components, and visually construct a data acquisition model based on the data type components;
[0005] N handheld terminals are deployed at corresponding collection points as required; N is an integer greater than or equal to 1; the N handheld terminals are configured to parse the data collection model to form a data collection table, the data collection table is configured to collect field data, and transmit the field data back to the command center in encrypted form.
[0006] In a further embodiment, a data management subsystem is deployed in the server terminal, and the data management subsystem includes: a data management user login module, a basic information management module, a collection model management module and a collection data management module;
[0007] The basic information management module is configured to implement the addition, deletion, modification, and inspection management of basic information related to acquisition personnel, combat operations, and system users;
[0008] The acquisition model management module is configured to realize visual construction of the data acquisition model and distribution to each handheld terminal;
[0009] The acquisition data management module is configured to enable the server terminal to receive combat data sent by each handheld terminal, as well as query and analyze historical acquisition data.
[0010] In a further embodiment, a data acquisition subsystem is deployed in each handheld terminal, and the data acquisition subsystem includes: a data acquisition user login module, a data acquisition module and a data upload module;
[0011] The data collection module is configured to receive a data collection model sent by the server and parse the data collection model into a structured data collection table;
[0012] The data upload module is configured to transmit the training data back to the command center in a wireless encrypted form.
[0013] In a further embodiment, the construction process of the data acquisition model is as follows:
[0014] Create the data type represented by the data component, define various attributes of the data type, and encapsulate the data type and corresponding attributes to form a callable data component list;
[0015] Drag and drop the data components in the data component list, and define their names, properties, and structural levels to form a data collection model.
[0016] In a further embodiment, each data component of the handheld terminal is implemented as a view View, and the drawing of the view View is defined to be completed by a size function Measure(), a position function Layout(), and a drawing function Draw();
[0017] Among them, the size function Measure() includes: the function measure() used to measure the size of the view View, the function onMeasure() used to measure the width and height of the custom data component itself and its sub-Views, and the function setMeasuredDimension() used to store the measured width and height of the sub-View;
[0018] The position function Layout() includes: function layout(), which is used for the view View to determine its own position in its parent View; function onLayout(), which is used to determine the position of the child View; function setFrame(), which is used to determine the position of the view View itself;
[0019] The drawing function Draw() includes: a function draw() or a function onDraw() for drawing a view.
[0020] In a further embodiment, when constructing a data collection model, the data collection task is decomposed according to the structural hierarchical relationship of the model according to the task requirements;
[0021] The structural hierarchical relationship includes "exercise d, stage ds, action dsa, link dsal" which are subordinate to each other in sequence; wherein d represents the number of the exercise task, ds represents the stage number within the exercise task d, dsa represents the action number within the stage ds in the exercise task d, and dsal represents the link number of the action dsa in the stage ds in the exercise task d.
[0022] The componentized data collection method for dynamic interaction of two-level databases using the componentized data collection system for dynamic interaction of two-level databases as described above comprises the following steps:
[0023] Build SQL Server database and SQLite database on the server terminal and handheld terminal respectively;
[0024] The data collection model of the server terminal is sent to the handheld terminal by using the data collection and delivery solution, and the handheld terminal analyzes the data collection model to form a data collection table;
[0025] The collected data return solution is used to traverse each data collection table in the SQLite database through data statements, and each data is extracted to the corresponding field of each data component table in the SQL Server database according to the structural hierarchical relationship of the data collection model.
[0026] In a further embodiment, the specific process of the data collection and distribution scheme is as follows:
[0027] Step 101: Create four data tables in the SQL Server database to obtain a data structure table of the acquisition model, wherein the data structure table of the acquisition model is used to express the structural hierarchical relationship of the data acquisition model, and the task data is described through the structural hierarchical relationship;
[0028] Step 102: According to the acquisition model data structure table in the SQL Server database, a SQLite data structure table with the same structure is constructed in the handheld terminal;
[0029] Step 103: Reconstruct the acquisition model data structure table in the SQL Server database using database statements to obtain acquisition model data, and copy the acquisition model data into the SQLite data structure table to convert it into a DB file that can be read by SQLite;
[0030] Step 104: Send the DB file to the handheld terminal using ADB technology;
[0031] Step 105: The handheld terminal reads the DB file using an enumeration method, parses the data component according to its data type and corresponding attribute, and presents the data collection model in the form of a multi-level data table on the handheld terminal interface.
[0032] In a further embodiment, the specific process of the collected data return scheme is as follows:
[0033] Step 201: constructing a SQLite data collection structure table of all data type components on the server terminal according to the storage method and characteristics of the SQLite database;
[0034] Step 202: Using ADB technology, the SQLite data collection storage structure table is sent to the handheld terminal along with the DB file;
[0035] Step 203: collect data using a handheld terminal, and store the collected field data and corresponding data type components in a SQLite collection data storage structure table according to a subordinate relationship;
[0036] Step 204: using ADB technology, copy the collected field data to a specified path of the server terminal, and store it in the form of a DB file to obtain a collected data DB file;
[0037] Step 205: Apply database statements to traverse each data table in the collection data DB file under the specified path, extract all data in the table into corresponding fields in each data component table of the SQL Server database, and complete the data return operation.
[0038] Beneficial effects of the present invention: Based on component development technology, the present invention constructs a variety of data components, covering various types of field data, and realizes the visual construction of data acquisition models; based on distributed design technology, it constructs a "server-side + handheld terminal" application architecture, which is better adapted to the wide geographical area and multiple points of training data acquisition; the interaction mode between the server-side and the handheld terminal is designed to facilitate the rapid recovery and storage of various types of collected field data. The system has a wide range of application scenarios, strong adaptability, and good flexibility, and can effectively improve the efficiency of training data acquisition and management. BRIEF DESCRIPTION OF THE DRAWINGS
[0039] Figure 1 This is a diagram of a componentized data acquisition system for dynamic interaction between two-level databases in Example 1.
[0040] Figure 2 This is a system functional structure diagram of Example 1.
[0041] Figure 3 A flowchart showing a list of data components.
[0042] Figure 4 This is the implementation process of the handheld terminal data component.
[0043] Figure 5 This is the structural diagram of the data acquisition model.
[0044] Figure 6 Flowchart of the data collection and distribution plan.
[0045] Figure 7 Flowchart of the data collection and transmission solution. DETAILED DESCRIPTION
[0046] The present invention will be further described below in conjunction with the accompanying drawings and embodiments.
[0047] Example 1
[0048] like Figure 1 As shown, this embodiment discloses a componentized data collection system for dynamic interaction of two-level databases, including: a server terminal and N handheld terminals, N is an integer greater than or equal to 1, and the server terminal in this embodiment is 1. Among them, the server terminal is deployed in the command center, and the server terminal is configured to select corresponding data components and visually construct a data collection model. The handheld terminal is deployed at the corresponding collection point on site according to demand, and is configured to parse the data collection model to form a data collection table. The data collection table is configured for collectors to collect on-site data, and the on-site data is transmitted back to the command center in an encrypted form, so as to facilitate query, statistics and other operations on the data collected on site, such as at the training site.
[0049] In a further embodiment, Figure 2 The server terminal and the handheld terminal shown are respectively equipped with data management subsystems.
[0050] The data management subsystem includes: data management user login module, basic information management module, collection model management module and collection data management module. Furthermore, the basic information management module is configured to implement the addition, deletion, modification and inspection management of basic information related to collection personnel, combat operations and system users; the collection model management module is configured to implement the visual construction of data collection models and distribution to various handheld terminals; the collection data management module is configured to implement the reception of combat data sent by the server terminal to each handheld terminal, as well as the query and analysis of historical collection data.
[0051] Correspondingly, the data collection subsystem includes: a data collection user login module, a data collection module and a data upload module. Among them, the data collection module is configured to receive the data collection model sent by the server, and parse the data collection model into a structured data collection table; such as timing, taking pictures, recording, text input, integer input, etc., to assist the collector to complete the collection of combat data.
[0052] The data upload module is configured to transmit the training data back to the command center in a wireless and encrypted form.
[0053] In a further embodiment, in order to ensure the comprehensiveness of the data model, commonly used data types are encapsulated and integrated into data type components, mainly including 12 types of data components such as text class, time class, date class, timing class, integer class, decimal class, single choice class, multiple choice class, sound class, image class, video class, positioning class, etc. Correspondingly, the construction process of the data acquisition model is as follows: Create data types represented by data components, such as text, integer, timing and other data types. Define various attributes of the data type, such as encoding rules, presentation style, operation method and other attribute content. Encapsulate the data type and the corresponding various attributes to form a callable data component list, such as Figure 3 shown.
[0054] It should be noted that the data component in this embodiment is developed mainly using the treeview control in Winform, with each component represented by a Treeview node, and the component code, style, action and other attribute information are encapsulated therein to form a data component list. According to the data collection requirements, the user can select the corresponding component from the list and drag it directly to the main interface to realize the visual construction of the collection model. Take the "single choice" component as an example to implement the component. ① Component coding implementation: Each component is assigned a unique code to realize the custom combination of components. The component coding is implemented by an enumeration class, which stores the names of each component and the component codes in an enumeration type. ② Component attribute encapsulation: Based on the various controls provided by the Visual Studio platform, the appearance style of the data component and the operation method of recording data are designed and encapsulated, and the encapsulated data component is displayed in the tree list of the TreeViewExt control through a loop statement. ③ Component draggable implementation: In order to facilitate the user to build the collection model, the draggable function of the data component is designed. Each data component in the list can be added to the main interface by dragging the mouse, and its name, attributes and structural hierarchy can be defined to form a data collection model.
[0055] In this embodiment, the handheld terminal is an Android operating system. In Android, View is the base class of all controls in Android, so each data component list of the handheld terminal is implemented as a view View. The steps mainly include:
[0056] First: define the drawing of the view View by the size function Measure(), the position function Layout(), and the drawing function Draw().
[0057] Second: define the page layout of data components. The 12 types of data components set in the current system are based on inheriting LinearLayout controls and constructing corresponding parameter functions to achieve this; the 12 types of data components are text, time, date, timing, integer, decimal, single-choice, multiple-choice, sound, image, video, and positioning.
[0058] Third: define the operational function events of data components, such as encoding rules, presentation styles, operation methods and other attribute contents.
[0059] Fourth: data caching and clearing.
[0060] Furthermore, each data component of the handheld terminal is implemented as a view View, and the drawing of the view View is defined to be completed by a size function Measure(), a position function Layout(), and a drawing function Draw().
[0061] Among them, the size function Measure() includes: the function measure() used to measure the size of the view View, the function onMeasure() used to measure the width and height of the custom data component itself and its sub-Views, and the function setMeasuredDimension() used to store the measured width and height of the sub-View;
[0062] The position function Layout() includes: function layout(), which is used for the view View to determine its own position in its parent View; function onLayout(), which is used to determine the position of the child View; function setFrame(), which is used to determine the position of the view View itself;
[0063] The drawing function Draw() includes: a function draw() or a function onDraw() for drawing a view. It should be noted that the function draw() or the function onDraw() is selected according to the application scenario. Taking the "current time" data component as an example, its implementation method is:
[0064] The function of the "Current Time" data component is: click the "button" to obtain the current time displayed on the page, and cache the data, display the cached data and clear it.
[0065] First: Use the Measure() function and Layout() function to measure the size and position of the View (container of the data component); use the Draw() function to draw the View to provide a container for the "current time" data component.
[0066] Second: By inheriting LinearLayout, construct a parameter function, public TimeView(Contextcontext, AttributeSet attrs, int defStyleAttr){super(context, attrs, defStyleAttr);}, which contains three parameters: Context / AttributeSet / int. Then construct a LayoutInflater object through the from() method of LayoutInflater, call the inflate() method to load time_xml (the XML specifies the style of the "current time" data component), and realize the dynamic display of component layout.
[0067] Third: Add textView control to realize text display, EditView control to realize display and obtain the current time, and button event processing to realize click to obtain the current time and assign it to EditView.
[0068] Fourth: Use Acahe to implement data caching, and set the method setData(String key,Object obj) to obtain acahe.getOnbject(key) to obtain cached data and display it, and set setClear(string key) to clear the cached data.
[0069] Considering that the various types of data of on-site activities are not independent, they are related to each other, that is, there is a hierarchical structure, such as training and exercise activities. For example, when collecting the effectiveness data of a certain type of equipment, it is necessary to clarify which combat operation and which exercise operation it belongs to. Therefore, it is necessary to construct a collection model structure to clarify the subordinate relationship of each data component to facilitate the comparative analysis of training and exercise data. According to the characteristics and processes of exercise tasks, daily training, and various assessment activities, while ensuring the clear expression of the data model hierarchy, it is also necessary to take into account the workload of software development. The collection model is designed as a four-layer structure, which is used to express "exercise, stage, action, link".
[0070] Its structure is as Figure 5As shown in the figure, when constructing a data collection model, the data collection task is decomposed according to the structural hierarchical relationship of the model according to the task requirements; the structural hierarchical relationship includes "exercise d, stage ds, action dsa, link dsal" which are subordinate to each other in sequence; wherein d represents the number of the exercise task, ds represents the stage number within the exercise task d, dsa represents the action number within the stage ds of the exercise task d, and dsal represents the link number of the action dsa in the stage ds of the exercise task d. In other words, when constructing a data collection model, the data collection task needs to be decomposed according to the four-layer structure of the model according to the process and characteristics of the training task. Finally, at the link level, select the corresponding data component by dragging and dropping to complete the construction of the entire data collection model.
[0071] Example 2
[0072] The componentized data acquisition system for dynamic interaction of two-level databases disclosed in Example 1 adopts the application form of "server-side + handheld terminal", the server-side database is SQL Server, and the handheld terminal database is SQLite.
[0073] This embodiment discloses a componentized data collection method for dynamic interaction between two-level databases, including the following steps:
[0074] Build SQL Server database and SQLite database on the server terminal and handheld terminal respectively; build data collection scheme and interactive protocol and method of collected data for SQL Server database and SQLite database to ensure that data collection scheme is smoothly and accurately sent to handheld terminal and collected data is smoothly and accurately uploaded to server.
[0075] In other words, the data collection and delivery solution is used to deliver the data collection model of the server terminal to the handheld terminal, and the handheld terminal analyzes the data collection model to form a data collection table;
[0076] The collected data return solution is used to traverse each data collection table in the SQLite database through data statements, and each data is extracted to the corresponding field of each data component table in the SQL Server database according to the structural hierarchical relationship of the data collection model.
[0077] Further, such as Figure 6 As shown in the figure, the specific process of data collection and distribution plan is as follows:
[0078] Step 101: Create four data tables in the SQL Server database to obtain a data structure table of the acquisition model, wherein the data structure table of the acquisition model is used to express the structural hierarchical relationship of the data acquisition model, and the task data is described through the structural hierarchical relationship;
[0079] Step 102: According to the acquisition model data structure table in the SQL Server database, a SQLite data structure table with the same structure is constructed in the handheld terminal;
[0080] Step 103: Reconstruct the acquisition model data structure table in the SQL Server database using database statements to obtain acquisition model data, and copy the acquisition model data into the SQLite data structure table to convert it into a DB file that can be read by SQLite;
[0081] Step 104: Use ADB technology to send the DB file to the handheld terminal; the ADB technology in this embodiment is Android Debug Bridge, which plays the role of debugging bridge. Eclipse Through DDMS To debug Android programs.
[0082] Step 105: The handheld terminal reads the DB file using an enumeration method, parses the data component according to its data type and corresponding attribute, and presents the data collection model in the form of a multi-level data table on the handheld terminal interface.
[0083] like,
[0084]
[0085]
[0086] Collected data transmission mainly refers to transmitting the data collected by the handheld terminal back to the server for users to consult, count and analyze. The SQL Server database on the server side stores data in the form of data component tables. The fields of each storage table are the component titles of each data type, and the stored data types can be different. As a lightweight database, the SQLite database creates tables to store data of the same type, and each storage table contains the same type of data. However, SQLServer and SQLite store data in different ways. The collected data in SQLite cannot be directly copied to SQL Server. Database statements are required to traverse each data table in the SQLite database and extract each data into the corresponding fields in each data component table in the SQL Server database according to the hierarchical relationship of the collection model.
[0087] Specifically, Figure 7 As shown in the figure, the specific process of the data collection and transmission scheme is as follows:
[0088] Step 201: constructing a SQLite data collection structure table of all data type components on the server terminal according to the storage method and characteristics of the SQLite database;
[0089] Step 202: Using ADB technology, the SQLite data collection storage structure table is sent to the handheld terminal along with the DB file;
[0090] Step 203: collect data using a handheld terminal, and store the collected field data and corresponding data type components in a SQLite collection data storage structure table according to a subordinate relationship;
[0091] Step 204: using ADB technology, copy the collected field data to a specified path of the server terminal, and store it in the form of a DB file to obtain a collected data DB file;
[0092] Step 205: Apply database statements to traverse each data table in the collection data DB file under the specified path, extract all data in the table into corresponding fields in each data component table of the SQL Server database, and complete the data return operation.
[0093] In other words, use the select statement to read the collected data and ID in the SQLite data table and store them in the cache; find the corresponding data table in the SQL database according to the ID, and use the insert statement and update statement to store or update the collected data in the data table. At the same time, back up the collected data and ID in the SQLite data table to the original record table in the SQL database to prevent data loss.
[0094] In actual applications, the data management subsystem was developed based on the Visual Studio platform and deployed on the server side based on the Windows system. The data acquisition subsystem was developed using the Fragment+GreenDao+Butterknife open source framework structure and deployed on a handheld terminal based on the Andriod system, and was applied in the training activities of a certain type of pontoon bridge.
Claims
1. A componentized data collection system for dynamic interaction between two-level databases, characterized by: include: A server terminal is deployed in the command center; the server terminal is configured to select corresponding data components to form callable data type components, and visually construct a data acquisition model based on the data type components; N handheld terminals are deployed at corresponding collection points according to needs; N is an integer greater than or equal to 1; the N handheld terminals are configured to parse the data collection model to form a data collection table, the data collection table is configured to collect field data and transmit the field data back to the command center in an encrypted form.
2. The componentized data acquisition system for dynamic interaction of two-level databases according to claim 1 is characterized in that: A data management subsystem is deployed in the server terminal, and the data management subsystem includes: a data management user login module, a basic information management module, a collection model management module and a collection data management module; The basic information management module is configured to implement the addition, deletion, modification, and inspection management of basic information related to acquisition personnel, combat operations, and system users; The acquisition model management module is configured to realize visual construction of the data acquisition model and distribution to each handheld terminal; The acquisition data management module is configured to enable the server terminal to receive combat data sent by each handheld terminal, as well as query and analyze historical acquisition data.
3. The componentized data acquisition system for dynamic interaction between two-level databases according to claim 1 is characterized in that: A data acquisition subsystem is deployed in each handheld terminal, and the data acquisition subsystem includes: a data acquisition user login module, a data acquisition module and a data upload module; The data collection module is configured to receive a data collection model sent by the server and parse the data collection model into a structured data collection table; The data upload module is configured to transmit the training data back to the command center in a wireless encrypted form.
4. The componentized data acquisition system for dynamic interaction between two-level databases according to claim 1 is characterized in that: The construction process of the data acquisition model is as follows: Create the data type represented by the data component, define various attributes of the data type, and encapsulate the data type and corresponding attributes to form a callable data component list; Drag and drop the data components in the data component list, and define their names, properties, and structural levels to form a data collection model.
5. The componentized data acquisition system for dynamic interaction between two-level databases according to claim 1 is characterized in that: Each data component of the handheld terminal is implemented as a view View, and the drawing of the view View is defined by the size function Measure(), the position function Layout(), and the drawing function Draw(); Among them, the size function Measure() includes: the function measure() for measuring the size of the view View, the function onMeasure() for measuring the width and height of the custom data component itself and its sub-Views, and the function setMeasuredDimension() for storing the measured width and height of the sub-View; The position function Layout() includes: function layout(), which is used for the view View to determine its own position in its parent View; function onLayout(), which is used to determine the position of the child View; function setFrame(), which is used to determine the position of the view View itself; The drawing function Draw() includes: a function draw() or a function onDraw() for drawing a view.
6. The componentized data acquisition system for dynamic interaction between two-level databases according to claim 1 is characterized in that: When building a data collection model, the data collection tasks are decomposed according to the structural hierarchical relationship of the model based on the task requirements; The structural hierarchical relationship includes "exercise d, stage ds, action dsa, link dsal" which are sequentially subordinate to each other; wherein d represents the number of the exercise task, ds represents the stage number within the exercise task d, dsa represents the action number within the stage ds in the exercise task d, and dsal represents the link number of the action dsa in the stage ds in the exercise task d.
7. A componentized data collection method for dynamic interaction of two-level databases using the componentized data collection system for dynamic interaction of two-level databases as claimed in any one of claims 1 to 6, characterized in that: The following steps are involved: Build SQL Server database and SQLite database on the server terminal and handheld terminal respectively; The data collection model of the server terminal is sent to the handheld terminal by using the data collection and delivery solution, and the handheld terminal analyzes the data collection model to form a data collection table; The collected data return solution is used to traverse each data collection table in the SQLite database through data statements, and each data is extracted to the corresponding field of each data component table in the SQL Server database according to the structural hierarchical relationship of the data collection model.
8. The componentized data collection method for dynamic interaction between two-level databases according to claim 7 is characterized in that: The specific process of the data collection and distribution plan is as follows: Step 101: Create four data tables in the SQL Server database to obtain a data structure table of the acquisition model, wherein the data structure table of the acquisition model is used to express the structural hierarchical relationship of the data acquisition model, and the task data is described through the structural hierarchical relationship; Step 102: According to the acquisition model data structure table in the SQL Server database, a SQLite data structure table with the same structure is constructed in the handheld terminal; Step 103: Use select, insert, and update statements to copy the acquisition model data built in the SQL Server database into the SQLite data structure table, thereby converting it into a DB file that can be read by SQLite; Step 104: Send the DB file to the handheld terminal using ADB technology; Step 105: The handheld terminal reads the DB file using an enumeration method, parses the data component according to its data type and corresponding attribute, and presents the data collection model in the form of a multi-level data table on the handheld terminal interface.
9. The componentized data collection method for dynamic interaction between two-level databases according to claim 7, characterized in that: The specific process of the data collection and transmission scheme is as follows: Step 201: constructing a SQLite data collection structure table of all data type components on the server terminal according to the storage method and characteristics of the SQLite database; Step 202: Using ADB technology, the SQLite data collection storage structure table is sent to the handheld terminal along with the DB file; Step 203: collect data using a handheld terminal, and store the collected field data and corresponding data type components in a SQLite collection data storage structure table according to a subordinate relationship; Step 204: using ADB technology, copy the collected field data to a specified path of the server terminal, and store it in the form of a DB file to obtain a collected data DB file; Step 205: Apply database statements to traverse each data table in the collection data DB file under the specified path, extract all data in the table into corresponding fields in each data component table of the SQL Server database, and complete the data return operation.