Database integration system applied to base station
By integrating cache, timing and relational databases, the problem of excessive pressure on a single server in the base station application system is solved, efficient data storage and query are achieved, and user experience is improved.
Patent Information
- Application Number
- CN202422182697.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Utility models(China)
- Current Assignee / Owner
- Filing Date
- 2024-09-05
- Publication Date
- 2025-08-22
- Estimated Expiration
- 2034-09-05
AI Technical Summary
In existing base station application systems, a single server is prone to downtime or the response rate decreases under large data volume and high query frequency, which affects the efficiency of data query.
The integrated solution of cache database, timing database and relational database is adopted. The cache database is used to display data in real time, the timing database processes real-time data, and the relational database stores business and historical data, sharing server pressure.
It improves data storage and query efficiency, reduces server pressure, meets the needs of high concurrent access and massive time-series data processing, and optimizes the user experience.
Smart Images

Figure CN223260178U_ABST
Abstract
Description
Technical Field
[0001] The utility model relates to the field of base station systems, in particular to a database integration system applied to base stations. Background Art
[0002] In existing base station application systems, data at multiple levels are generally involved, such as real-time power generation data, real-time power consumption data, diesel remaining data, etc. Therefore, the data designed is relatively complex and the data changes continuously over time, so the data is relatively complex.
[0003] The logic of existing databases is generally as follows: 1. The device is connected to a single server, and the device sends real-time data to the server and saves or displays it in real time; 2. When the user queries data, it directly enters the predetermined server and displays the data.
[0004] However, in actual use, it was found that this design has the following problems: 1. When the database storage capacity is greater than the predetermined value, a single server may experience downtime or data delays; 2. When the query frequency is high, the server database pressure is high and the response rate will decrease, affecting the query (especially real-time data). Utility Model Content
[0005] The main purpose of this utility model is to propose a database integration system for base station applications, which aims to integrate cache databases, time series databases and relational databases to reduce the pressure on the data channel of the server and optimize the storage, query and response speed of data.
[0006] To achieve the above objectives, the present invention proposes a database integration system for base station applications, comprising:
[0007] Server, the server is used to access the storage layer, the storage layer includes a cache database, a time series database and a relational database,
[0008] The cache database is used to display data directly to the server page;
[0009] The time series database is used to process real-time data;
[0010] The relational database is used to store business data and historical monitoring data;
[0011] When the device generates data, the data is sent to the data management service center through the EMQ message management system. The data management service center sends the data to the time series database. At the same time, the data service center sends the data to the cache database through the spring framework. The relational database is also used to store data information of the time series database.
[0012] The cache database Redis takes advantage of Redis's fast query speed to quickly display data to customers, reducing server pressure while improving user experience.
[0013] The time series database InfluxDB, which leverages its high write and query performance, can process large-scale time series data.
[0014] The relational database PostgreSQL persistently stores business data and processed historical monitoring data. All collected detailed device data is written to a time series database (leveraging the time series database's high-frequency write capability). This provides a data foundation for future user queries of device historical data (leveraging the time series database's fast retrieval capabilities). The platform's device location historical data module directly retrieves data from the time series database. The time series database stores hotspot data for the past six months. The time series database stores highly granular data.
[0015] By effectively combining cache databases, time series databases, and relational databases, a flexible data management solution is provided, enabling data storage, efficient query, and real-time monitoring (dynamic energy data), effectively reducing database pressure and meeting the needs of high-concurrency access, massive time series data processing, and complex relational data storage. BRIEF DESCRIPTION OF THE DRAWINGS
[0016] Figure 1 This is a framework diagram of the utility model.
[0017] In the figure,
[0018] 1 is the server,
[0019] 2 is the storage layer, 21 is the cache database, 22 is the time series database, 23 is the relational database,
[0020] 3 is the data management service center,
[0021] 4 is the EMQ message management system,
[0022] 5 is the device,
[0023] 6 is the spring framework. DETAILED DESCRIPTION
[0024] The following will be combined with the accompanying drawings to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the embodiments described are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of the present invention.
[0025] It should be noted that if the embodiments of the present invention involve directional indications (such as up, down, left, right, front, back, top, bottom, inside, outside, vertical, horizontal, longitudinal, counterclockwise, clockwise, circumferential, radial, axial...), then the directional indications are only used to explain the relative position relationship, movement status, etc. between the components in a certain specific posture (as shown in the accompanying drawings). If the specific posture changes, the directional indications will also change accordingly.
[0026] In addition, if there are descriptions involving "first" or "second" in the embodiments of the present invention, the descriptions of "first" or "second" are only for descriptive purposes and cannot be understood as indicating or implying their relative importance or implicitly indicating the number of the indicated technical features. Therefore, the features specified as "first" or "second" may explicitly or implicitly include at least one of such features. In addition, the technical solutions between the various embodiments can be combined with each other, but this must be based on the fact that ordinary technicians in this field can implement them. When the combination of technical solutions is contradictory or cannot be implemented, it should be deemed that such a combination of technical solutions does not exist and is not within the scope of protection required by the present invention.
[0027] like Figure 1 As shown, a database integration system for base station applications includes:
[0028] Server, the server is used to access the storage layer, the storage layer includes a cache database, a time series database and a relational database,
[0029] The cache database is used to display data directly to the server page;
[0030] The time series database is used to process real-time data;
[0031] The relational database is used to store business data and historical monitoring data;
[0032] When the device generates data, the data is sent to the data management service center through the EMQ message management system. The data management service center sends the data to the time series database. At the same time, the data service center sends the data to the cache database through the spring framework. The relational database is also used to store data information of the time series database.
[0033] The cache database Redis takes advantage of its fast query speed to quickly display data to customers, reducing server pressure while improving user experience.
[0034] InfluxDB, a time series database, leverages the high write and query performance of time series databases to process large-scale time series data.
[0035] The relational database PostgreSQL persistently stores business data and processed historical monitoring data. All collected detailed device data is written to a time series database (leveraging the time series database's high-frequency write capability). This provides a data foundation for future user queries of device historical data (leveraging the time series database's fast retrieval capabilities). The platform's device location historical data module directly retrieves data from the time series database. The time series database stores hotspot data for the past six months. The time series database stores highly granular data.
[0036] By effectively combining cache databases, time series databases, and relational databases, a flexible data management solution is provided, enabling data storage, efficient query, and real-time monitoring (dynamic energy data), effectively reducing database pressure and meeting the needs of high-concurrency access, massive time series data processing, and complex relational data storage.
[0037] Specifically, the data management service center is a DMS service, which includes data migration, data monitoring, and access control, thereby realizing data processing, wherein the relational database can also directly store the data processed by the data management service center.
[0038] Specifically, the Spring framework is used to present data in a modular format. This means that a device has multiple data interfaces. The Spring framework can display the data from each interface as line graphs, bar charts, and other display formats on the page as needed, allowing users to directly access the desired data. After the data acquisition program collects data from the device, in order to present real-time data to the customer as quickly as possible, we use a cache database as a real-time repository. This temporarily caches the data that users need to see, and then quickly displays this data to the user through visualization tools from the Redis cache database.
[0039] Specifically, the business data includes company information, role information, user information, equipment information, equipment location, power generation, and oil volume. This basic information is the key to the equipment, thereby reducing the delay caused by the server directly accessing a single database. For the basic data required for the operation of the platform (company information, role information, user information, and some basic configuration information, etc.), a relational database is used to save it. In addition, for data uploaded by the device for more than 6 months, it is synchronized from the time series database to the relational database through a scheduled task to achieve the purpose of data persistence. The data of the reporting function module mainly comes from the relational database. The relational database stores data with a larger coarse granularity.
[0040] Specifically, the EMQ message management system is emqbroker, and the device sends messages to the EMQ message management system through the mqtt+ssl protocol.
[0041] Specifically, the cache database is used to display data in real time.
[0042] Specifically, the server is a web service.
[0043] The above description is only a preferred embodiment of the present invention and does not limit the patent scope of the present invention. All equivalent structural transformations made by using the contents of the present invention specification and drawings under the practical concept of the present invention, or direct / indirect application in other related technical fields are included in the patent protection scope of the present invention.
Claims
1. A database integration system for base station applications, characterized in that: include, Server, the server is used to access the storage layer, the storage layer includes a cache database, a time series database and a relational database, The cache database is used to display data directly to the server page; The time series database is used to process real-time data; The relational database is used to store business data and historical monitoring data; When the device generates data, the data is sent to the data management service center through the EMQ message management system. The data management service center sends the data to the time series database. At the same time, the data service center sends the data to the cache database through the spring framework. The relational database is also used to store data information of the time series database.
2. The database integration system for base station applications according to claim 1, wherein: The data management service center is a DMS service, which includes data migration, data monitoring and access control.
3. The database integration system for base station applications according to claim 1, wherein: The spring framework is used to present data in a modular manner.
4. The database integration system for base station applications according to claim 1, wherein: The business data includes company information, role information, user information, equipment information, equipment location, power generation, and oil volume.
5. The database integration system for base station applications according to claim 1, wherein: The EMQ message management system is an emq broker, and the device sends messages to the EMQ message management system via the mqtt+ssl protocol.
6. The database integration system for base station applications according to claim 1, wherein: The cache database is used to display data in real time.
7. The database integration system for base station applications according to claim 1, wherein: The server is a web service.