Database for urban comprehensive management service platform

Abstract

The invention relates to the technical field of digital management, in particular to a database for an urban comprehensive management service platform, and view governance data in the database stores data for marking acquired image data; related data of the algorithm warehouse stores algorithms required by urban comprehensive management; the algorithm training related data stores related data for performing optimization training on an algorithm required by urban comprehensive management; the event thematic database information is used for storing corresponding data of each function module of urban comprehensive management; the intelligent scheduling related data stores the data required by the processing flow for deploying and realizing all functions of the urban comprehensive management, so as to realize the flow processing result; the system management data stores data used for managing an event processing flow; and the monitoring operation and maintenance related data is used for storing data required by operation and maintenance of the urban comprehensive management service platform.

Description

Technical Field

[0001] The present invention relates to the field of digital management technology, in particular to a database used for a city comprehensive management service platform. Background Art

[0002] In order to realize the automation of the entire process of urban management, a variety of urban comprehensive management service platforms have been built, which enables intelligent urban management to realize the intelligent distribution of tasks and improve the efficiency of urban management. In this process, urban management has huge content, complex processes, and involves many departments. Therefore, there are many types of data and the data volume is huge. It is necessary to design a database in a targeted manner to facilitate data management and scheduling. Summary of the invention

[0003] In view of the above-mentioned deficiencies of the prior art and the needs of intelligent city management, the present invention establishes a database for an urban comprehensive management service platform, providing data support for intelligent city management.

[0004] In order to achieve the above objectives, the following technical solutions are proposed: A database for an urban comprehensive management service platform, including view governance data, algorithm warehouse data, algorithm training related data, event subject library information, intelligent scheduling related data, system management data, and monitoring and operation related data. The view management data stores data for annotating the collected image data; The algorithm warehouse related data stores the algorithms required for comprehensive urban management; The algorithm training related data stores the relevant data for optimizing the training of the algorithm required for comprehensive urban management; The event subject database information is used to store the corresponding data of each functional module of urban comprehensive management; The intelligent dispatching related data stores the data required for the processing flow of various functions of urban comprehensive management to achieve the process processing results; The system management data stores data used to manage the event processing process; The monitoring and operation and maintenance related data is used to store data required for the operation and maintenance of the urban comprehensive management service platform.

[0005] As a preferred solution, the view management data includes district / street / community level information, point name, device type, IP information, status information, location information, international code, venue label, industry label and location label.

[0006] As a preferred solution, the data related to the algorithm repository includes algorithm model data and algorithm registration information data, where the algorithm registration information data includes algorithm type, algorithm tag, algorithm resource, and algorithm priority.

[0007] As a preferred solution, the data related to algorithm training includes data to be annotated, annotation information data, annotation task data, training task data, training resource status data, and model output related data.

[0008] As a preferred solution, the data related to intelligent scheduling includes algorithm scheduling request data, algorithm scheduling status data, device resource status data, and structured output data.

[0009] As a preferred solution, the database adopts the E-R design method, and data flow is realized through the E-R design diagram. The E-R design diagram includes alarm events, camera information, area information, camera tag information, task information table, subtask information table, algorithm information table, role information table, user information table, permission module information table, and permission information table.

[0010] As a preferred solution, the entity relationships of each part in the E-R design diagram are as follows: There is a one-to-many relationship between camera information and alarm events; there is a one-to-many relationship between area information and camera information; there is a many-to-many relationship between camera information and camera tags; there is a one-to-many relationship between camera information and subtask information; there is a one-to-many relationship between task information and subtask information; there is a many-to-many relationship between role information and user information; there is a many-to-many relationship between role information and permission modules; there is a many-to-many relationship between permission information and permission modules.

[0011] As a preferred solution, the database adopts the method of one master, two slaves, and three sentinels to realize the distribution of the database.

[0012] Based on the same concept, a data processing flow for the urban comprehensive management service platform is also proposed. Using any one of the above-mentioned databases for the urban comprehensive management service platform, the following steps are executed: Preprocess the images for information annotation in the view governance data output to the data related to intelligent scheduling; The data related to intelligent scheduling obtains the corresponding intelligent processing algorithm from the data related to the algorithm repository according to the preprocessed images; The preprocessed images and the intelligent processing algorithm process the event according to the data in the management event processing flow in the system management data to obtain a processing result; The data related to intelligent scheduling outputs the preprocessed images, intelligent processing algorithm, and processing result of the same event processing to the event theme library information; The algorithm training-related data trains the intelligent processing algorithms in the algorithm repository according to the information in the event topic library to obtain optimized algorithms; The intelligent processing algorithms output by the algorithm repository-related data, the optimized algorithms output by the algorithm training-related data, and the processing results in the system management data are input into the monitoring and operation and maintenance-related data, and the monitoring and operation and maintenance-related data monitors and manages the intelligent processing algorithms output by the algorithm repository-related data, the optimized algorithms output by the algorithm training-related data, and the processing results in the system management data.

[0013] Compared with the prior art, the beneficial effects of the present invention are as follows: The present invention provides a database for an urban comprehensive management service platform. Through the architecture design of the database, intelligent scheduling of processes can be achieved, resources are reasonably allocated, and the operation efficiency is relatively high. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] Figure 1 It is the data flow diagram in Embodiment 1; Figure 2 It is the alarm event E-R diagram in Embodiment 1; Figure 3 It is the camera E-R diagram in Embodiment 1; Figure 4 It is the area information E-R diagram in Embodiment 1; Figure 5 It is the camera label E-R diagram in Embodiment 1; Figure 6 It is the task information table E-R diagram in Embodiment 1; Figure 7 It is the sub-task information table E-R diagram in Embodiment 1; Figure 8 It is the algorithm information table E-R diagram in Embodiment 1; Figure 9 It is the overall database E-R diagram in Embodiment 1; Figure 10 It is the heterogeneous fusion multi-type database system diagram in Embodiment 1. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0015] The present invention will be further described in detail below in conjunction with test examples and specific embodiments. However, this should not be construed as limiting the scope of the above-mentioned subject matter of the present invention to the following embodiments. Any technology implemented based on the content of the present invention belongs to the scope of the present invention.

[0016] Embodiment 1 A database for an urban comprehensive management service platform, the data flow diagram is as Figure 1As shown, it includes view governance data, algorithm repository data, algorithm training-related data, event topic library information, intelligent scheduling-related data, system management data, and monitoring and operation and maintenance-related data.

[0017] The view governance data stores the data used to annotate the collected image data; the algorithm repository-related data stores the algorithms required for urban comprehensive management; the algorithm training-related data stores the relevant data for optimizing and training the algorithms required for urban comprehensive management; the event topic library information is used to store the corresponding data of each functional module of urban comprehensive management; the intelligent scheduling-related data stores the data required to allocate the processing flow for realizing each function of urban comprehensive management to achieve the process processing result; the system management data stores the data used to manage the event processing flow; the monitoring and operation and maintenance-related data is used to store the data required for the operation and maintenance of the urban comprehensive management service platform.

[0018] Furthermore, the view governance data includes district / street / community level information, point name, device type, IP information, status information, location information, international code, venue label, industry label, and location label.

[0019] The algorithm repository-related data includes algorithm model data and algorithm registration information data, where the algorithm registration information data includes algorithm type, algorithm label, algorithm resource, and algorithm priority.

[0020] The algorithm training-related data includes data to be annotated, annotation information data, annotation task data, training task data, training resource status data, and model output-related data.

[0021] The intelligent scheduling-related data includes algorithm scheduling request data, algorithm scheduling status data, device resource status data, and structured output data.

[0022] The database adopts the E-R design method. The E-R diagram is mainly composed of three elements: entity, attribute, and relationship. Data flow is realized through the E-R design diagram. The E-R design diagram includes alarm event, camera information, area information, camera label information, task information table, subtask information table, algorithm information table, role information table, user information table, permission module information table, and permission information table. The alarm event E-R diagram is as Figure 2 shown, and the attributes include time target box coordinates, push status, review status, event capture picture, 10s video before and after the time, camera ID, algorithm type, pusher, task ID, subtask ID, event, and manufacturer ID.

[0023] The camera E-R diagram is as Figure 3As shown, the attribute information includes the RTSP stream address, lens name, installation address, camera IP, camera port, longitude, latitude, community where installed, national standard code of the camera, area ID, and street where installed. The E-R diagram of the area information is as Figure 4 shown. The attribute information includes the area name, area level, and parent ID. The E-R diagram of the camera label is as Figure 5 shown, including the label name, label description, label type, parent ID, and label level. The E-R diagram of the task information table is as Figure 6 shown. The attribute information includes the time range for task execution, task priority, task creator ID, progress of creating subtasks, task execution frequency, task name, task running status, task description, task type, list of cameras for task execution, and algorithm ID for task execution. The E-R diagram of the subtask information table is as Figure 7 shown. The attribute information includes the algorithm ID, subtask UUID, subtask start time, subtask end time, task ID corresponding to the subtask, camera ID, and frame extraction service address. The E-R diagram of the algorithm information table is as Figure 8 shown. The attribute information includes the algorithm description, algorithm stop address, algorithm call address, algorithm name, algorithm unique number, algorithm type, algorithm version, whether to remove duplicates, duplicate removal ratio, and algorithm call parameter template. The overall database E-R diagram is as Figure 9 shown. The sub-diagrams of each E-R diagram are connected by relationships, including having, belonging to, and composing, etc. Through connections such as having, belonging to, and composing, the sub-diagrams are connected into the overall E-R diagram. The description of the E-R design diagram is shown in Table 1.

[0024] Table 1 Description of the E-R Design Diagram The entity relationships of each part in the E-R design diagram include: There is a one-to-many relationship between camera information and alarm events; there is a one-to-many relationship between area information and camera information; there is a many-to-many relationship between camera information and camera labels; there is a one-to-many relationship between camera information and subtask information; there is a one-to-many relationship between task information and subtask information; there is a many-to-many relationship between role information and user information; there is a many-to-many relationship between role information and permission modules; there is a many-to-many relationship between permission information and permission modules.

[0025] In addition, there are various types of data in the database. Generally speaking, they can be classified into structured data and unstructured data. Structured data can be further divided into text (string type), attributes (discrete categorical values or classification information), and numerical values (continuous integer or floating-point data, etc.). Unstructured data can be divided into feature vector data (extracted from images), as well as objects such as pictures, videos, documents, files, or binary files, etc. In addition, different data types have different operations (such as SQL relational queries, fuzzy queries, vector index queries, etc.), different data scales (conventional data volume and massive data volume), and different access mode (OLTP / OLAP) characteristics. All of the above requirements need to combine multiple database types to form a heterogeneous fusion multi-type database support system. The diagram of the heterogeneous fusion multi-type database system is as shown in Figure 10 shown Among them, based on the above heterogeneous fusion multi-type database system, the targeted storage types and customized development directions for data of each part are as follows: Mysql: It mainly stores relational data types and first needs to complete secondary adaptation and development in the K8S container cloud environment, especially the development for topology binding requirements; and adaptation and development on the A+D hardware platform.

[0026] PostgreSql: It mainly stores vector feature storage databases and first needs to complete secondary adaptation and development in the K8S container cloud environment, especially the development for topology binding requirements; and adaptation and development on the A+D hardware platform.

[0027] IntellifDB: It is developed based on Mysql / PostgrSql and conducts secondary encapsulation development for SQL queries, providing a distributed massive feature vector storage and query solution; and adaptation and development on the A+D hardware platform.

[0028] TiDB: It can store large-scale relational data and relational data with relatively high reliability requirements and relatively low requirements for latency, concurrency, and throughput. In the project, it is necessary to complete secondary adaptation and development of TiDB in the K8S container cloud environment, especially the development for topology binding requirements; and adaptation and development on the A+D hardware platform.

[0029] For data with high requirements for query response such as data collection data with dynamically added fields, it can be considered to be stored in MongoDB. At the same time, in the project, MongoDB needs to complete secondary adaptation and development in the K8S container cloud environment, especially the development for topology binding requirements; and adaptation and development on the A+D hardware platform.

[0030] Data that requires efficient text search and fuzzy search can be stored in ES. At the same time, ElasticSearch needs to complete secondary adaptation development in the K8S container cloud environment, especially the development for topology binding requirements; as well as adaptation development on the A+D hardware platform.

[0031] Configuration data, cache data, session status and other data can be stored in Redis. At the same time, Redis in the project needs to complete secondary adaptation development in the K8S container cloud environment, especially the development of topology binding requirements; as well as adaptation development on the A+D hardware platform.

[0032] In terms of security considerations: Business application data and device configuration documents must be backed up for recovery in case of problems.

[0033] When backing up data to other devices, a dedicated backup channel must be used to ensure the integrity of data transmission.

[0034] The integrity of data should be checked when it is backed up locally.

[0035] Professional backup equipment and tools must be used for data backup, and data transmission and storage must be encrypted.

[0036] Database access control Users can only log in to the application software with their account and access the database through the application software, and there is no other way to operate the database.

[0037] User Account Security The password of the user account is encrypted to ensure that the plain text of the password does not appear anywhere. When the user logs in, the client and server keys are double encrypted and decrypted to ensure that the password will not be leaked in the HTTP call process, and the password of the server user account is signed with SM3 before entering the database.

[0038] Roles and permissions Determine the operation permissions of each role on the database table, such as create, retrieve, update, delete, etc. Each role has the permissions that are just enough to complete the task, no more and no less. When assigning roles to users during application, the permissions of each user are equal to the sum of the permissions of the roles he holds.

[0039] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present invention should be included in the protection scope of the present invention.

Claims

1. A database for an urban comprehensive management service platform, characterized in that: Including view governance data, algorithm warehouse data, algorithm training related data, event subject library information, intelligent scheduling related data, system management data and monitoring operation and maintenance related data, The view management data stores data for annotating the collected image data; The algorithm warehouse related data stores the algorithms required for comprehensive urban management; The algorithm training related data stores the relevant data for optimizing the training of the algorithm required for comprehensive urban management; The event subject database information is used to store the corresponding data of each functional module of urban comprehensive management; The intelligent dispatching related data stores the data required for the processing flow of various functions of urban comprehensive management to achieve the process processing results; The system management data stores data used to manage the event processing process; The monitoring and operation and maintenance related data is used to store data required for the operation and maintenance of the urban comprehensive management service platform.

2. A database for a city comprehensive management service platform as claimed in claim 1, characterized in that: The view management data includes district / street / community level information, point name, device type, IP information, status information, location information, international code, venue label, industry label and location label.

3. A database for a city comprehensive management service platform as claimed in claim 1, characterized in that: The algorithm warehouse related data includes algorithm model data and algorithm registration information data, wherein the algorithm registration information data includes algorithm type, algorithm label, algorithm resource and algorithm priority.

4. A database for a city comprehensive management service platform as claimed in claim 1, characterized in that: The algorithm training related data includes data to be labeled, labeling information data, labeling task data, training task data, training resource status data and model output related data.

5. A database for a city comprehensive management service platform as claimed in claim 1, characterized in that: The intelligent scheduling related data includes algorithm scheduling request data, algorithm scheduling status data, device resource status data and structured output data.

6. A database for a city comprehensive management service platform as claimed in claim 1, characterized in that: The database adopts the ER design method and realizes data flow through the ER design diagram. The ER design diagram includes alarm events, camera information, area information, camera label information, task information table, subtask information table, algorithm information table, role information table, user information table, permission module information table, and permission information table.

7. A database for a city comprehensive management service platform as claimed in claim 6, characterized in that: The entity relationships of the various parts in the ER design diagram include: The relationship between camera information and alarm events is one-to-many; the relationship between area information and camera information is one-to-many; the relationship between camera information and camera tags is many-to-many; the relationship between camera information and subtask information is one-to-many; the relationship between task information and subtask information is one-to-many; the relationship between role information and user information is many-to-many; the relationship between role information and permission modules is many-to-many; the relationship between permission information and permission modules is many-to-many.

8. A database for a city comprehensive management service platform as claimed in claim 1, characterized in that: The database adopts a one-master, two-slave and three-sentinel mode to achieve database distribution.

9. A data processing process for an urban comprehensive management service platform, characterized in that: Using a database for a city comprehensive management service platform as described in any one of claims 1 to 8, perform the following steps: The view management data outputs the pre-processed image with information annotation to the intelligent scheduling related data; The intelligent scheduling related data obtains the corresponding intelligent processing algorithm from the algorithm warehouse related data according to the pre-processed image; The preprocessing image and the intelligent processing algorithm process the event according to the data of the management event processing flow in the system management data to obtain the processing result; The intelligent scheduling related data outputs the pre-processed image, intelligent processing algorithm and processing result of the same event processing to the event subject library information; The algorithm training related data trains the intelligent processing algorithm in the algorithm warehouse according to the event subject library information to obtain an optimized algorithm; The intelligent processing algorithm output by the algorithm warehouse related data, the optimization algorithm output by the algorithm training related data, and the processing results in the system management data are input into the monitoring and operation and maintenance related data, and the monitoring and operation and maintenance related data monitors and manages the intelligent processing algorithm output by the algorithm warehouse related data, the optimization algorithm output by the algorithm training related data, and the processing results in the system management data.

Images