CN112883098B - Multi-source heterogeneous system data fusion method - Google Patents

Multi-source heterogeneous system data fusion method Download PDF

Info

Publication number
CN112883098B
CN112883098B CN202110273604.3A CN202110273604A CN112883098B CN 112883098 B CN112883098 B CN 112883098B CN 202110273604 A CN202110273604 A CN 202110273604A CN 112883098 B CN112883098 B CN 112883098B
Authority
CN
China
Prior art keywords
data
enterprise
reported
interface
real time
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN202110273604.3A
Other languages
Chinese (zh)
Other versions
CN112883098A (en
Inventor
陈友良
李全明
李海港
陈慧
李振涛
褚衍玉
王守印
郑小龙
郭庞锋
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Jiangxi Academy Of Emergency Management
Senior Research Institute Of State Drug Administration Safety Emergency Drill Center Of State Drug Administration
China Academy of Safety Science and Technology CASST
Original Assignee
Jiangxi Academy Of Emergency Management
Senior Research Institute Of State Drug Administration Safety Emergency Drill Center Of State Drug Administration
China Academy of Safety Science and Technology CASST
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Jiangxi Academy Of Emergency Management, Senior Research Institute Of State Drug Administration Safety Emergency Drill Center Of State Drug Administration, China Academy of Safety Science and Technology CASST filed Critical Jiangxi Academy Of Emergency Management
Priority to CN202110273604.3A priority Critical patent/CN112883098B/en
Publication of CN112883098A publication Critical patent/CN112883098A/en
Application granted granted Critical
Publication of CN112883098B publication Critical patent/CN112883098B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/25—Integrating or interfacing systems involving database management systems
    • G06F16/252—Integrating or interfacing systems involving database management systems between a Database Management System and a front-end application
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/25—Integrating or interfacing systems involving database management systems
    • G06F16/258—Data format conversion from or to a database
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/28—Databases characterised by their database models, e.g. relational or object models
    • G06F16/284—Relational databases
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/70—Information retrieval; Database structures therefor; File system structures therefor of video data
    • G06F16/71—Indexing; Data structures therefor; Storage structures

Landscapes

  • Engineering & Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Data Mining & Analysis (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Software Systems (AREA)
  • Multimedia (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

The invention provides a data fusion method for a multi-source heterogeneous system, which comprises the following steps: acquiring monitoring data of an enterprise tailing pond, and transmitting the monitoring data to an Internet of things host through a TCP (transmission control protocol)/HTTP (hyper text transport protocol); issuing an API service; calling the API service, and determining enterprise reported data in the monitoring data; reporting the enterprise reported data by an operator private line network through an HTTP protocol; receiving the enterprise reported data in real time to obtain enterprise end data; and verifying the enterprise data, and storing the verified enterprise data into a database. The invention provides a data fusion method of a multi-source heterogeneous system, which adopts a mode of uniformly issuing an API interface, and an enterprise terminal reports data according to a data standard format by calling the interface, thereby solving the problems of inapplicability to enterprises with backward conditions and high investment cost in the prior art.

Description

Multi-source heterogeneous system data fusion method
Technical Field
The invention relates to the technical field of data fusion, in particular to a data fusion method of a multi-source heterogeneous system.
Background
Risk monitoring is a common means for ensuring safety in the safety production process. According to the related requirements in the safety regulation GB 39496-2020 of the tailings reservoir, after completing the data acquisition work of each enterprise end according to the file requirements of the safety production risk monitoring and early warning system data access standard specification of the tailings reservoir, each enterprise end needs to upload the data of the enterprise end to a government end platform, the enterprise needs to acquire information by monitoring equipment generally when acquiring the data of the enterprise end, the manufacturers of the monitoring equipment have a plurality of monitoring equipment, each monitoring equipment has differences, when the government end platform gathers and fuses the data of each enterprise end, the enterprise end platform mainly adopts the traditional data warehouse technology (ETL, Extract-Transform-Load) technology to Extract (Extract), convert (Transform) and Load (Load) the data from the source end to the target end, often needs the enterprise to have a prepositive bank and interact through a public network address, but the realization is difficult for laggard non-coal mine enterprises, but also adds cost to the enterprise. Therefore, the invention provides a data fusion method for a multi-source heterogeneous system, which adopts a mode of uniformly issuing an API interface, and an enterprise terminal reports data according to a data specification format by calling the interface, thereby solving the problems of inapplicability to enterprises with backward conditions and high investment cost in the prior art.
Disclosure of Invention
The invention provides a data fusion method of a multi-source heterogeneous system, which adopts a mode of uniformly issuing an API interface, and an enterprise terminal reports data according to a data standard format by calling the interface, thereby solving the problems of inapplicability to enterprises with backward conditions and high investment cost in the prior art.
The invention provides a data fusion method for a multi-source heterogeneous system, which comprises the following steps:
acquiring monitoring data of an enterprise tailing pond, and transmitting the monitoring data to an Internet of things host through a TCP (transmission control protocol)/HTTP (hyper text transport protocol);
issuing an API service;
calling the API service, and determining enterprise reported data in the monitoring data;
reporting the enterprise reported data by an operator private line network through an HTTP protocol;
receiving the enterprise reported data in real time to obtain enterprise end data;
and verifying the enterprise data, and storing the verified enterprise data into a database.
Further, the reporting data of the enterprise includes: static data, real-time monitoring data, alarm data and video data of the enterprise tailing pond.
Further, the publishing API service deploys an API schema for receiving data prior to the publishing API service.
Further, the API scheme for deploying the received data is determined according to the data acquisition scheme of the enterprise tailing pond; the data acquisition scheme of the enterprise tailing pond comprises the following steps: acquiring static data and acquiring real-time data, wherein the static data is updated according to monitoring conditions; the real-time data includes: dry sharing data, reservoir water level data, surface displacement data, wetting line data, rainfall data and internal displacement data.
Further, the enterprise reported data is received in real time through a plurality of interfaces when being received in real time; the interface includes: the system comprises a dry beach data interface, a reservoir water level interface, a displacement data interface, an internal inclinometry data interface, a wet line information data interface and a rainfall information interface.
Further, the interface also comprises a query enterprise ID interface.
Further, the calling the API service and determining the reporting data of the enterprise in the monitoring data includes:
calling the API service;
analyzing the API service to obtain enterprise data requirements and reporting format specifications;
extracting initialized enterprise reported data from the monitoring data according to the enterprise data requirement;
and adjusting the format of the initialized enterprise reported data according to the reporting format specification to obtain the enterprise reported data.
Further, the database is of various types including MS Sql, MySQL, Access, and Oracle.
Further, when reporting the enterprise reported data by using the operator private network through the HTTP protocol, the enterprise reported data is reported after being encrypted, and the process includes:
randomly generating a plurality of plaintext data blocks from the enterprise reported data; the number of the plaintext data blocks is preset, the number of the plaintext data blocks is preset according to the target number, and then the enterprise reported data is randomly generated into the plaintext data blocks with the target number;
determining a sub-key of data reported by an enterprise; randomly generating an encryption key, and then generating a plurality of groups of sub-keys according to a key rule, wherein the group number of the sub-keys is matched with the number of plaintext data blocks; the key rule is that there is a crossover between adjacent subkeys;
encrypting the plaintext data blocks respectively through the sub-keys to obtain a plurality of encrypted data blocks; arranging the plaintext data blocks according to a set sequence and then matching with a sub-key; encrypting the plaintext data block through the sub-key according to the matching result of the sub-key to obtain an encrypted data block;
and reporting the plurality of encrypted data blocks.
Further, when verifying the enterprise-side data, the integrity verification of the enterprise-side data is performed, and when performing the integrity verification of the enterprise-side data, the method includes the following steps:
identifying the enterprise reported data received in real time to obtain the reportOral information and enterprise data, and is marked as Di＝(kl,hi) Wherein D isiIndicating real-time received enterprise reported data identification data, klPort identification representing enterprise reported data received in real time; h isiRepresenting enterprise reported data received in real time;
obtaining an integrity check value according to the following formula;
A＝{σ(ck)}-{MID{Di}}∩{σ(ck)}
in the formula, A represents the integrity check value of the enterprise reported data received in real time, sigma represents the mapping relation between the target reported data and the interface for receiving the enterprise reported data in real time, and ckRepresents the kth target reception data, MID { D }iThe port identification is extracted from the data identification data received in real time from the enterprise, and the port identification represents a set;
when the integrity check value A of the enterprise reported data received in real time represents an empty set, the enterprise reported data received in real time is complete, otherwise, the enterprise reported data received in real time is incomplete, and the corresponding enterprise needs to report enterprise end data again.
Additional features and advantages of the invention will be set forth in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention. The objectives and other advantages of the invention will be realized and attained by the structure particularly pointed out in the written description and claims hereof as well as the appended drawings.
The technical solution of the present invention is further described in detail by the accompanying drawings and embodiments.
Drawings
The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and together with the description serve to explain the principles of the invention and not to limit the invention. In the drawings:
FIG. 1 is a flow chart of a data fusion method for a multi-source heterogeneous system according to the present invention;
FIG. 2 is a schematic diagram illustrating an implementation of a multi-source heterogeneous system data fusion method according to the present invention;
fig. 3 is an overall schematic diagram of a multi-source heterogeneous system data fusion method according to the present invention.
Detailed Description
The preferred embodiments of the present invention will be described in conjunction with the accompanying drawings, and it will be understood that they are described herein for the purpose of illustration and explanation and not limitation.
As shown in fig. 1 to fig. 3, an embodiment of the present invention provides a multi-source heterogeneous system data fusion method, including:
acquiring monitoring data of an enterprise tailing pond, and transmitting the monitoring data to a host of the Internet of things through a TCP (transmission control protocol)/HTTP (hyper text transport protocol);
step two, releasing API service;
calling the API service, and determining enterprise reported data in the monitoring data;
reporting the enterprise reported data through an HTTP protocol by utilizing an operator private line network;
fifthly, receiving the enterprise reported data in real time to obtain enterprise end data;
and step six, verifying the enterprise end data, and storing the verified enterprise end data into a database.
In the technical scheme, when enterprise reported data of an enterprise end are converged on a government end platform, firstly, monitoring data of an enterprise tailing pond are obtained through detection equipment, the monitoring data are transmitted to an internet of things host through a TCP (transmission control protocol)/HTTP (hyper text transport protocol), and then after API (application program interface) services are released, the enterprise reported data are determined in the monitoring data through calling the API services; then, reporting the enterprise reported data by an operator private line network through an HTTP protocol; then, receiving enterprise reported data in real time, thereby obtaining enterprise end data; and finally, verifying the enterprise data, and storing the verified enterprise data into a database. According to the technical scheme, the mode of issuing the API service is adopted, so that the enterprise terminal reports data according to the data specification format by calling the interface, and the enterprise terminal data reporting is completed.
In an embodiment of the present invention, the reporting data by the enterprise includes: static data, real-time monitoring data, alarm data and video data of the enterprise tailing pond.
In the technical scheme, when the enterprise reports the data of the enterprise terminal, only the static data, the real-time monitoring data, the alarm data and the video data of the enterprise tailing pond are reported. The data in the enterprise data are limited through the technical scheme, so that other parameters acquired from the monitoring equipment are only displayed at the client side and cannot be reported, and the influence of other irrelevant data on the reporting process is reduced.
In an embodiment provided by the present invention, the API scheme for receiving data is deployed before the API service is released.
In the above technical solution, API solution deployment is performed for the API interface before issuing the API service. By deploying the API scheme, each enterprise can report the requirements of the API scheme to enterprise data even if monitoring equipment of different manufacturers is adopted, and the API (application programming interface) can be deployed by programming, so that the application is very convenient to use and easy to execute deployment.
In an embodiment provided by the present invention, the API scheme for deploying the received data is determined according to a data collection scheme of an enterprise tailing pond; the data acquisition scheme of the enterprise tailing pond comprises the following steps: acquiring static data and acquiring real-time data, wherein the static data is updated according to monitoring conditions; the real-time data includes: dry sharing data, reservoir water level data, surface displacement data, wetting line data, rainfall data and internal displacement data.
In the technical scheme, when the API scheme for receiving data is deployed, static data and real-time data are deployed, the static data can be updated according to the real-time data, and when parameters such as reservoir capacity, dam height and catchment area change, the static data is updated in time; meanwhile, when the monitoring equipment changes and the early warning threshold value of the monitoring point changes, the early warning threshold value is updated in time through the enterprise terminal. The real-time data includes: dry beach, reservoir level, surface displacement, wet line, rainfall, internal displacement, etc.; the data is acquired by sensors or equipment such as an ultrasonic dry beach monitor, a radar level meter, a total station, an osmometer and the like. Wherein, the data information of the dry beach is as follows:
Figure BDA0002975605210000061
Figure BDA0002975605210000071
the reservoir level data information is as follows:
Figure BDA0002975605210000072
the surface displacement data information is as follows:
Figure BDA0002975605210000073
the saturation line data information is as follows:
Figure BDA0002975605210000081
the rainfall data information is as follows:
Figure BDA0002975605210000082
the internal displacement data information is as follows:
Figure BDA0002975605210000083
Figure BDA0002975605210000091
the device offline information is as follows:
Figure BDA0002975605210000092
the monitoring alarm information is as follows:
Figure BDA0002975605210000093
in an embodiment provided by the present invention, the enterprise reported data is received in real time through a plurality of interfaces; the interface includes: the system comprises a dry beach data interface, a reservoir water level interface, a displacement data interface, an internal inclinometry data interface, a wet line information data interface and a rainfall information interface.
In the above technical solution, when the enterprise reported data is received in real time to obtain the enterprise data, the data is received in real time through a plurality of interfaces, and the data parameters received by each interface are different, where the interfaces include: the system comprises a dry beach data interface, a reservoir water level interface, a displacement data interface, an internal inclinometry data interface, a wet line information data interface and a rainfall information interface. According to the technical scheme, the API service can be deployed for the single interface by setting the plurality of interfaces, and the interfaces do not influence each other during real-time receiving, so that the real-time receiving efficiency is improved.
The dry beach data interface transmits real-time monitoring data according to a field data change interval and a dynamic access interface, and can also issue API service after setting minutes by setting request frequency, so that dry beach data are obtained. When the API service is issued, the URL is requested in a post request mode: http://. is. 251.206:9281/monitoring/wkk/dryBeach, where is a hidden character, which indicates the display according to the actual use case, wherein the parameters code (device number), measurementTime (measurement time), value (dry beach length value), enterId (Enterprise code) are involved, and finally a json is returned, such as: { "code":200 "}, where 200 denotes that the request was successful; the data represents the enterprise ID of the enterprise; when the returned result is 400, the request parameter is indicated to be wrong; if 404 returns, it indicates that the request address is incorrect; if 500 is returned, an internal exception is indicated.
And the reservoir level interface transmits real-time monitoring data according to the field data change interval and the dynamic access interface, and can also issue the API service after setting minutes by setting the request frequency, so that the reservoir level is obtained. When the API service is issued, the URL is requested in a post request mode: http://. is. 251.206: 9281/monitoring/wkk/waterfevel, where is denotes hidden characters, which indicate the display according to the actual use case, wherein the parameters code (device number), measurementTime (measured time), value (library water level value), entrid (enterprise code), are referred to, and finally a json is returned, such as: { "code":200 "}, where 200 denotes that the request was successful; the data represents the enterprise ID of the enterprise; when the returned result is 400, the request parameter is indicated to be wrong; if 404 returns, it indicates that the request address is incorrect; if 500 is returned, an internal exception is indicated.
The displacement data interface transmits real-time monitoring data according to a field data change interval and a dynamic access interface, and can also issue API service after setting minutes by setting request frequency, so that displacement data are obtained. When the API service is issued, the URL is requested in a post request mode: http://. indicates. 251.206:9281/monitoring/wkk/displacement, where hidden characters are indicated, which are displayed according to actual use, wherein the parameters code (device number), measurementTime (measured time), valueX (X value), valueY (Y value), valueZ (Z value), entrid (enterprise code) are referred to, and in horizontal displacement, the downstream is marked as positive, the left bank (standing on the dam, determined to be facing downstream) is positive; otherwise, the voltage is negative; in the vertical displacement, the downward direction is marked as positive, and the reverse direction is negative, and finally a json is returned, such as: { "code":200 "}, where 200 denotes that the request was successful; the data represents the enterprise ID of the enterprise; when the returned result is 400, the request parameter is indicated to be wrong; if 404 returns, it indicates that the request address is incorrect; if 500 is returned, an internal exception is indicated.
The internal inclinometry data interface transmits real-time monitoring data according to a field data change interval and a dynamic access interface, and can also issue API service after setting minutes by setting request frequency, so that internal inclinometry data are obtained. When the API service is issued, the URL is requested in a post request mode: http://. gtat 251.206: 9281/monitoring/wkk/endoclonometer, wherein parameters code (device number), measurementTime (measured time), value X (X value), value Y (Y value), entrid (enterprise code) are involved, finally returning a json, such as: { "code":200 "}, where 200 denotes that the request was successful; the data represents the enterprise ID of the enterprise; when the returned result is 400, the request parameter is indicated to be wrong; if 404 returns, it indicates that the request address is incorrect; if 500 is returned, an internal exception is indicated.
The line-wetting credit data interface transmits real-time monitoring data according to a field data change interval and a dynamic access interface, and can issue API service after setting minutes by setting request frequency, so that line-wetting credit data are obtained. When the API service is issued, the URL is requested in a post request mode: http://. is. 251.206: 9281/monitoring/wkk/institutional line, where is meant hidden characters, which are shown according to actual usage, where are parameters code (device number), measurementTime (measurement time), value (saturation line level), enterId (enterprise code), and finally a json is returned, such as: { "code":200 "}, where 200 denotes that the request was successful; the data represents the enterprise ID of the enterprise; when the returned result is 400, the request parameter is indicated to be wrong; if 404 returns, it indicates that the request address is incorrect; if 500 is returned, an internal exception is indicated.
The rainfall information interface transmits real-time monitoring data according to a field data change interval and a dynamic access interface, and can issue API service after setting minutes by setting request frequency, so that rainfall information is obtained. When the API service is issued, the URL is requested in a post request mode: http://. is. 251.206:9281/monitoring/wkk/rainfall, where is meant hidden characters, which indicate the display according to the actual use case, where are related to the parameters code (device number), measurementTime (measured time), value (data value), entrid (business code), and finally a json is returned, such as: { "code":200 "}, where 200 denotes that the request was successful; the data represents the enterprise ID of the enterprise; when the returned result is 400, the request parameter is indicated to be wrong; if 404 returns, it indicates that the request address is incorrect; if 500 is returned, an internal exception is indicated.
In addition, the serial numbers of the equipment are all unique, the forms of the measuring time are all 'yyyy-MM-dd HH: MM: ss', the serial numbers of the enterprises are integers, the numbers are inquired and returned by an interface 7, and when the decimal precision is 0-8, so that a beach data interface, a reservoir level interface, a displacement data interface, an internal inclinometry data interface, an infiltration line credit data interface and a rainfall information interface can have the requirement of uniform form expression, and the management of enterprise end data is facilitated.
In one embodiment of the present invention, the interface further includes a query business ID interface.
In the technical scheme, when data reported by an enterprise are received in real time through a plurality of interfaces, an enterprise ID query interface is further arranged in the interfaces, an enterprise ID is obtained according to an enterprise name, the enterprise ID is received through the enterprise ID query interface, the enterprise ID is written into a configuration file, and a URL is requested through a post request mode: http://. x. 251.206: 9281/monitering/wkk/getEnterID, where x denotes hidden characters, which indicate display according to actual use, returns a json, such as: 200 { "code":200, "data":81052}, wherein 200 represents a successful request; the data represents the enterprise ID of the enterprise; if 400 is returned, the request parameter is wrong; if 404 returns, it indicates that the request address is incorrect; if 500 is returned, an internal exception is indicated. By the technical scheme, the enterprise end data in the stored database can contain the enterprise ID, and the reason of unsuccessful acquisition can be clearly known when the enterprise ID is not acquired successfully.
In an embodiment of the present invention, the calling the API service and determining the data reported by the enterprise in the monitoring data includes:
calling the API service;
analyzing the API service to obtain enterprise data requirements and reporting format specifications;
extracting initialized enterprise reported data from the monitoring data according to the enterprise data requirement;
and adjusting the format of the initialized enterprise reported data according to the reporting format specification to obtain the enterprise reported data.
In the technical scheme, when the API service is called and the data reported by the enterprise is determined in the monitoring data, the API service is called first, and the enterprise calls the issued API service; then, analyzing the called API service so as to obtain enterprise data requirements and reporting format specifications to be reported by an enterprise in the API service; further extracting initialized enterprise reported data from the detected data according to enterprise data requirements; and finally, carrying out format adjustment on the initialized enterprise reported data according to the reporting format specification to obtain the enterprise reported data. According to the technical scheme, the enterprise reported data have the same parameter data, the monitoring data obtained by the monitoring equipment of different manufacturers have slight difference, the monitoring data are extracted as the enterprise reported data only according to the enterprise data requirements, the reported formats are consistent, and the government end platform is facilitated to store.
In one embodiment provided by the invention, the database is a plurality of types of databases, including MS Sql, MySQL, Access and Oracle.
In the technical scheme, the enterprise data is seamlessly integrated into the database after verification, and the types of the database comprise MS Sql, MySQL, Access, Oracle and the like. Through the technical scheme, the types of the databases are various, so that the application range of the enterprise data can be widened, and the enterprise data can be stored in the databases under any condition.
In an embodiment of the present invention, when reporting the enterprise reported data by using the operator private network via the HTTP protocol, the enterprise reported data is reported after being encrypted, and the process includes:
randomly generating a plurality of plaintext data blocks from the enterprise reported data; the number of the plaintext data blocks is preset, the number of the plaintext data blocks is preset according to the target number, and then the enterprise reported data is randomly generated into the plaintext data blocks with the target number;
determining a sub-key of data reported by an enterprise; randomly generating an encryption key, and then generating a plurality of groups of sub-keys according to a key rule, wherein the group number of the sub-keys is matched with the number of plaintext data blocks; the key rule is that there is a crossover between adjacent subkeys;
encrypting the plaintext data blocks respectively through the sub-keys to obtain a plurality of encrypted data blocks; arranging the plaintext data blocks according to a set sequence and then matching with a sub-key; encrypting the plaintext data block through the sub-key according to the matching result of the sub-key to obtain an encrypted data block;
and reporting the plurality of encrypted data blocks.
In the technical scheme, when reporting the enterprise reported data through the HTTP, firstly carrying out encryption processing and then reporting, wherein in the process, firstly, randomly generating a plurality of plaintext data blocks from the enterprise reported data; then determining a sub-key of the data reported by the enterprise; then, encrypting the plaintext data blocks through the sub-keys respectively to obtain a plurality of encrypted data blocks; and finally, reporting the encrypted data block. According to the technical scheme, data leakage can be avoided when reporting is carried out through encryption processing, even if the data are obtained maliciously by other personnel, the encrypted enterprise reported data can not be obtained, and therefore the security of the enterprise reported data is enhanced.
In an embodiment of the present invention, when verifying the enterprise-side data, the integrity verification of the enterprise-side data includes performing integrity verification on the enterprise-side data, and when performing integrity verification on the enterprise-side data, the method includes the following steps:
identifying the enterprise reported data received in real time, obtaining interface information and enterprise end data, and recording as Di＝(kl,hi) Wherein D isiIndicating real-time received enterprise reported data identification data, klPort identification representing enterprise reported data received in real time; h isiRepresenting enterprise reported data received in real time;
obtaining an integrity check value according to the following formula;
A＝{σ(ck)}-{MID{Di}}∩{σ(ck)}
in the formula, A represents the integrity check value of the enterprise reported data received in real time, sigma represents the mapping relation between the target reported data and the interface for receiving the enterprise reported data in real time, and ckRepresents the kth target reception data, MID { D }iThe port identification is extracted from the data identification data received in real time from the enterprise, and the port identification represents a set;
when the integrity check value A of the enterprise reported data received in real time represents an empty set, the enterprise reported data received in real time is complete, otherwise, the enterprise reported data received in real time is incomplete, and the corresponding enterprise needs to report enterprise end data again.
In the technical scheme, integrity inspection is carried out on the enterprise terminal data when the enterprise terminal data are checked, so that the obtained enterprise terminal data correspond to the requirements of the published API service, incomplete enterprise terminal data are prevented from being stored in a database, the integrity inspection process can be automatically realized through a computer design program, and the integrity inspection speed is high and the accuracy is high.
It will be apparent to those skilled in the art that various changes and modifications may be made in the present invention without departing from the spirit and scope of the invention. Thus, if such modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to include such modifications and variations.

Claims (9)

1. A multi-source heterogeneous system data fusion method is characterized by comprising the following steps:
acquiring monitoring data of an enterprise tailing pond, and transmitting the monitoring data to an Internet of things host through a TCP (transmission control protocol)/HTTP (hyper text transport protocol);
issuing an API service;
calling the API service, and determining enterprise reported data in the monitoring data;
reporting the enterprise reported data by an operator private line network through an HTTP protocol;
receiving the enterprise reported data in real time to obtain enterprise end data;
verifying the enterprise data, and storing the verified enterprise data into a database;
when the enterprise data is checked, the integrity check of the enterprise data is carried out, and when the integrity check of the enterprise data is carried out, the method comprises the following steps:
identifying the enterprise reported data received in real time, acquiring interface information and enterprise end data, and recording as follows:
Di＝(kl,hi)
wherein D isiIndicating real-time received enterprise reported data identification data, klPort identification representing enterprise reported data received in real time; h isiRepresenting enterprise reported data received in real time;
obtaining an integrity check value according to the following formula;
A＝{σ(ck)}-{MID{Di}}∩{σ(ck)}
in the formula, A represents the integrity check value of the enterprise reported data received in real time, sigma represents the mapping relation between the target reported data and the interface for receiving the enterprise reported data in real time, and ckRepresents the kth target reception data, MID { D }iThe port identification is extracted from the data identification data received in real time from the enterprise, and the port identification represents a set;
when the integrity check value A of the enterprise reported data received in real time represents an empty set, the enterprise reported data received in real time is complete, otherwise, the enterprise reported data received in real time is incomplete, and the corresponding enterprise needs to report enterprise end data again.
2. The multi-source heterogeneous system data fusion method of claim 1, wherein reporting the data by the enterprise comprises: static data, real-time monitoring data, alarm data and video data of the enterprise tailing pond.
3. The multi-source heterogeneous system data fusion method of claim 1, wherein an API scheme for receiving data is deployed prior to the release of the API service.
4. The multi-source heterogeneous system data fusion method of claim 2, wherein the API scheme for deploying the received data is determined according to an enterprise tailing pond data acquisition scheme; the data acquisition scheme of the enterprise tailing pond comprises the following steps: acquiring static data and acquiring real-time data, wherein the static data is updated according to monitoring conditions; the real-time data includes: dry sharing data, reservoir water level data, surface displacement data, wetting line data, rainfall data and internal displacement data.
5. The multi-source heterogeneous system data fusion method according to claim 1, wherein the real-time reception is performed through a plurality of interfaces when the enterprise reported data is received in real time; the interface includes: the system comprises a dry beach data interface, a reservoir water level interface, a displacement data interface, an internal inclinometry data interface, a wet line information data interface and a rainfall information interface.
6. The multi-source heterogeneous system data fusion method of claim 5, further comprising a query enterprise ID interface in the interface.
7. The multi-source heterogeneous system data fusion method of claim 1, wherein the calling the API service and determining the reported data of the enterprise in the monitoring data comprises:
calling the API service;
analyzing the API service to obtain enterprise data requirements and reporting format specifications;
extracting initialized enterprise reported data from the monitoring data according to the enterprise data requirement;
and adjusting the format of the initialized enterprise reported data according to the reporting format specification to obtain the enterprise reported data.
8. The multi-source heterogeneous system data fusion method of claim 1, wherein the database is a multi-type database comprising MS Sql, MySQL, Access and Oracle.
9. The multi-source heterogeneous system data fusion method according to claim 1, wherein when reporting the enterprise reported data by using an operator private network via an HTTP protocol, the enterprise reported data is reported after being encrypted, and the process includes:
randomly generating a plurality of plaintext data blocks from the enterprise reported data; the number of the plaintext data blocks is preset, the number of the plaintext data blocks is preset according to the target number, and then the enterprise reported data is randomly generated into the plaintext data blocks with the target number;
determining a sub-key of data reported by an enterprise; randomly generating an encryption key, and then generating a plurality of groups of sub-keys according to a key rule, wherein the group number of the sub-keys is matched with the number of plaintext data blocks; the key rule is that there is a crossover between adjacent subkeys;
encrypting the plaintext data blocks respectively through the sub-keys to obtain a plurality of encrypted data blocks; arranging the plaintext data blocks according to a set sequence and then matching with a sub-key; encrypting the plaintext data block through the sub-key according to the matching result of the sub-key to obtain an encrypted data block;
and reporting the plurality of encrypted data blocks.
CN202110273604.3A 2021-03-15 2021-03-15 Multi-source heterogeneous system data fusion method Active CN112883098B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202110273604.3A CN112883098B (en) 2021-03-15 2021-03-15 Multi-source heterogeneous system data fusion method

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202110273604.3A CN112883098B (en) 2021-03-15 2021-03-15 Multi-source heterogeneous system data fusion method

Publications (2)

Publication Number Publication Date
CN112883098A CN112883098A (en) 2021-06-01
CN112883098B true CN112883098B (en) 2021-10-26

Family

ID=76042480

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202110273604.3A Active CN112883098B (en) 2021-03-15 2021-03-15 Multi-source heterogeneous system data fusion method

Country Status (1)

Country Link
CN (1) CN112883098B (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116415206B (en) * 2023-06-06 2023-08-22 中国移动紫金(江苏)创新研究院有限公司 Operator multiple data fusion method, system, electronic equipment and computer storage medium

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108449407A (en) * 2018-03-14 2018-08-24 中煤科工集团重庆研究院有限公司 Multi-source heterogeneous coal mine safety monitoring collecting method
CN109710678A (en) * 2018-12-27 2019-05-03 成都电科智联科技有限公司 A kind of real time data system and operation method of industry big data monitoring management

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11494484B2 (en) * 2016-10-24 2022-11-08 Nubeva, Inc. Leveraging instrumentation capabilities to enable monitoring services

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108449407A (en) * 2018-03-14 2018-08-24 中煤科工集团重庆研究院有限公司 Multi-source heterogeneous coal mine safety monitoring collecting method
CN109710678A (en) * 2018-12-27 2019-05-03 成都电科智联科技有限公司 A kind of real time data system and operation method of industry big data monitoring management

Also Published As

Publication number Publication date
CN112883098A (en) 2021-06-01

Similar Documents

Publication Publication Date Title
CN110457957B (en) Information processing method and device of electronic bill, electronic equipment and medium
CN106570944B (en) A kind of receive applied to express mail posts the System and method for for testing view
CN104135521A (en) Method and system of identifying data abnormal values of environment automatic monitoring network
CN109739137B (en) Intelligent terminal system for water conservancy Internet of things sensing and controlling platform
CN105574698A (en) Intelligent storage management system based on big data
CN103745190A (en) Two-dimensional code-based performance and monitoring data presentation method
CN103778516A (en) All-dimensional safety positioning trade information integration method
CN112883098B (en) Multi-source heterogeneous system data fusion method
CN111738558B (en) Visualization method, device, equipment and storage medium for behavior risk identification
CN102158890A (en) Methods, equipment and systems for sending and receiving test data
RU2369866C1 (en) Method of complex enviromental region monitoring
CN104764486A (en) Civil engineering surveying informatization system
CN110659289B (en) Material quality detection test report management method and system
CN105336172A (en) Electronic license plate and Internet of Vehicles addressing method based on network digital genes
CN109614430B (en) Configurable data acquisition and data verification system and method based on WLAN
CN112633761B (en) Index data query method, device, equipment and storage medium
CN114297277A (en) Carbon emission activity data acquisition method and device, electronic equipment and storage medium
CN110362626A (en) One kind being based on the convenience-for-people inquiry system of block chain network and application method
CN113506096A (en) Inter-system interface method based on industrial internet identification analysis system
CN210955189U (en) Sample entrusted detection logistics and information management system based on block chain
CN107612144B (en) Substation equipment importance detection system and method
CN202904581U (en) Grouting recording instrument system provided with digital signature
CN101901211A (en) Processing method of report form
CN203117685U (en) Remote monitoring system for offshore piling
CN101894100A (en) Report processing device and system

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant