Method and system for integrating management of multi-service systems based on unified data base

Abstract

The application provides a multi-service system integration management method and system based on a unified data base. Firstly, a service requirement description set of the multi-service system is acquired, which is mapped with data source capability information of the unified data base to obtain a service requirement mapping result. Then, integration execution rules of the multi-service system are constructed based on the service requirement mapping result. Next, the integration execution rules are sent to service processing modules of each service system to trigger service processing and obtain service cooperative execution results. Finally, integration management instructions are generated according to the service cooperative execution results and sent to a unified data base management module and the service processing modules of each service system to perform integration optimization operations, so that the integration management of multi-service systems in the ecological environment monitoring field can be efficiently realized.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of computer, in particular, to a multi-service system integration management method and system based on unified data base. BACKGROUND

[0002] In the field of ecological environment monitoring, with the continuous deepening and refinement of monitoring work, multiple service systems are often constructed to handle different types of monitoring tasks, such as air quality monitoring system, water quality monitoring system, soil pollution monitoring system, etc. These service systems run independently, with unique business processing logic and data storage methods.

[0003] Currently, each service system mainly relies on its own business rules and local data when processing its own business. When it comes to cross-system collaboration, there are many problems. On the one hand, different service systems lack a unified standard for describing business requirements, resulting in inaccurate and incomplete information transmission when communicating cross-system collaboration requirements, making it difficult to accurately understand each other's business requirements. On the other hand, there is a lack of effective integration mechanism between each service system and data source. Each system independently accesses its own data source, and data cannot be shared and efficiently utilized. When cross-system business data is interacted, problems such as data inconsistency and data transmission delay may occur, seriously affecting the collaboration efficiency and accuracy of ecological environment monitoring business, and failing to meet the needs of modern ecological environment monitoring for efficient integration management of multiple service systems. SUMMARY

[0004] In view of the above-mentioned problems, in combination with the first aspect of the present application, the embodiments of the present application provide a multi-service system integration management method based on unified data base, which comprises:

[0005] Obtaining a set of business requirement descriptions of multiple service systems, the set of business requirement descriptions including daily business processing requirement descriptions and cross-system collaborative business requirement descriptions of each service system, each business requirement description corresponding to unique business identification information;

[0006] Mapping the set of business requirement descriptions with data source capability information of the unified data base, matching the corresponding data source type and data providing method in the unified data base according to the data requirement content in each business requirement description, to obtain a business requirement mapping result;

[0007] Based on the business requirement mapping result, constructing an integrated execution rule of the multi-service system, the integrated execution rule including data source calling sequence rule of each service system and cross-system business data interaction timing rule;

[0008] The integrated execution rule is sent to the business processing modules of the business systems, triggering the business processing modules of the business systems to call the data sources of the unified data base for business processing according to the integrated execution rule, so as to obtain a business cooperative execution result.

[0009] An integrated management instruction of the multiple business systems is generated according to the business cooperative execution result, and the integrated management instruction is sent to the management module of the unified data base and the business processing modules of the business systems to perform an integrated optimization operation, wherein the integrated management instruction comprises a business processing parameter adjustment instruction and a data source allocation optimization instruction.

[0010] In another aspect, the embodiment of the present application also provides a multiple business system integrated management system based on a unified data base, which comprises a processor, a machine readable storage medium, the machine readable storage medium is connected with the processor, the machine readable storage medium is used for storing programs, instructions or codes, and the processor is used for executing the programs, instructions or codes in the machine readable storage medium to realize the above method.

[0011] Based on the above aspects, the embodiment of the present application can obtain a set of business demand descriptions including daily and cross-system cooperative business demand descriptions, and give unique business identification information, map the set of business demand descriptions with the data source capability information of the unified data base, and according to the data demand content in each business demand, match the corresponding data source type and providing mode to obtain an accurate business demand mapping result, effectively solve the problem of information mismatching and insufficient utilization between the business systems and the data sources, and realize efficient docking of data. Based on the business demand mapping result, the integrated execution rule of the multiple business systems is constructed, the data source calling sequence of each business system and the cross-system business data interaction timing are determined, the integrated execution rule is sent to the business processing modules of the business systems and the business processing is triggered to obtain a business cooperative execution result, the efficiency and accuracy of business cooperation are improved. According to the business cooperative execution result, the integrated management instruction is generated and sent to the management module of the unified data base and the business processing modules of the business systems to perform the integrated optimization operation, which comprises business processing parameter adjustment and data source allocation optimization, and the system parameters and resource allocation can be dynamically adjusted according to the actual business execution situation, and the efficiency and stability of the multiple business system integrated management are continuously improved. BRIEF DESCRIPTION OF DRAWINGS

[0012] Figure 1 is an execution flow schematic diagram of the multiple business system integrated management method based on a unified data base provided by the embodiment of the present application.

[0013] Figure 2 is a schematic diagram of exemplary hardware and software components of the multiple business system integrated management system based on a unified data base provided by the embodiment of the present application. DETAILED DESCRIPTION

[0014] The application will be described in detail below with reference to the accompanying drawings, Figure 1 is a flowchart of a multi-service system integration management method based on a unified data base provided by an embodiment of the application. The multi-service system integration management method based on a unified data base will be described in detail below.

[0015] Step S110: Obtain a service requirement description set of the multi-service system, the service requirement description set containing daily service processing requirement descriptions and cross-system collaborative service requirement descriptions of each service system, each service requirement description corresponding to unique service identification information.

[0016] This embodiment takes a regional ecological environment monitoring and management integrated platform as an application scenario, which integrates an atmospheric environment monitoring system, a water environment monitoring system, a soil environment monitoring system, an ecological management scheduling system, an environmental emergency response system and multiple service systems. When obtaining the service requirement description set, the related information is collected through the requirement collection modules of the service systems.

[0017] The daily service processing requirement description of the atmospheric environment monitoring system is "dynamically adjusting the monitoring frequency according to the regional meteorological conditions at different time periods each day, collecting the particulate matter concentration, gaseous pollutant concentration and other data of each monitoring point, needing to determine the validity of the monitoring point data in combination with the terrain data, regularly calling the meteorological data interface to obtain the wind speed, wind direction, temperature layer data to assist the pollution diffusion trajectory simulation, at the same time, encrypting the data collection frequency and preferentially obtaining the monitoring data around the key pollution sources during the pollution early warning period", and the corresponding service identification information is "DQ-001".

[0018] The daily service processing requirement description of the water environment monitoring system is "setting the monitoring period according to the river basin partition, collecting the pH value, dissolved oxygen content, permanganate index, heavy metal ion concentration and other water quality parameters of the dry stream, branch stream and reservoir section, needing to synchronously obtain the section water level, flow rate data to calculate the pollutant flux, adjusting the sampling frequency in real time according to the rainfall amount in the flood season, and needing to associate the monitoring data of the coastal sewage outlet for tracing analysis", and the service identification information is "SJ-001".

[0019] The cross-system collaborative business requirement description is as follows: "When the atmospheric environment monitoring system detects that the concentration of pollutants in the region continuously exceeds the standard, the information such as the exceeding standard period, the type of pollutants, and the concentration change trend needs to be synchronized to the ecological management dispatching system, the ecological management dispatching system calls the pollution source list database to screen the key control objects according to the information, and simultaneously pushes the exceeding standard warning information to the environmental emergency response system, the environmental emergency response system starts the emergency monitoring plan and feeds back the emergency resource allocation state", and the corresponding business identification information is "XT-001". The business requirement description set is formed by aggregating these business requirement descriptions, and is stored in the requirement information database. Each description contains a business target, data dependency, processing period, trigger condition, and the like.

[0020] Step S120: mapping processing is performed on the business requirement description set and the data source capability information of the unified data basement, the corresponding data source type and data providing mode in the unified data basement are matched according to the data requirement content in each business requirement description, and a business requirement mapping result is obtained.

[0021] The unified data basement integrates multiple data sources such as an atmospheric monitoring database, a water quality monitoring database, a soil monitoring database, a meteorological database, a hydrological database, a pollution source list database, a terrain database, and an emergency resource database. During the mapping processing, the corresponding data source is matched according to the specific data requirement of each business requirement.

[0022] For the requirement of the atmospheric environment monitoring system "DQ-001", the data such as the concentration of particulate matter and the concentration of gaseous pollutants needs to be matched with the atmospheric monitoring database, the atmospheric monitoring database stores data according to the monitoring point number and the time stamp, and provides a multi-condition query interface according to the region, the period, and the type of pollutants; the wind speed, the wind direction, and the temperature stratification data in the meteorological data need to be matched with the meteorological database, the meteorological database supports two modes of timed batch data pushing and real-time querying; the terrain data needs to be matched with the terrain database, and the terrain database provides a data slicing download service based on the latitude and longitude range.

[0023] The water quality parameter data in the requirement of the water environment monitoring system "SJ-001" comes from the water quality monitoring database, the water quality monitoring database adopts a distributed storage architecture, supports combined querying according to the river basin, the section type, and the monitoring index, and provides two interfaces of real-time data stream and historical data batch export; the water level and flow rate data in the hydrological data come from the hydrological database, support querying according to the hydrological station number and the time range, and can automatically calculate the average flow rate according to the request parameters; the coastal sewage outlet monitoring data comes from the sub-database of the pollution source list database, and provides a filtering query service according to the river basin and the type of sewage outlet. Through the above mapping, the corresponding data source and data acquisition mode of each business requirement are determined.

[0024] Step S121: Analyzing each service requirement description in the set of service requirement descriptions, extracting data requirement type and data call frequency information in each service requirement description.

[0025] Each description in the set of service requirement descriptions is analyzed. Taking the atmospheric environment monitoring system "DQ-001" requirement as an example, the content is analyzed sentence by sentence, the data related expressions are identified, and the data requirement type and data call frequency information are determined through semantic analysis.

[0026] In terms of data requirement type, "collecting particulate matter concentration, gaseous pollutant concentration and other data of each monitoring point" belongs to active data acquisition requirement, which clearly specifies the source object and specific indicators of the data; "calling weather data interface to obtain wind speed and direction data regularly" belongs to periodic data acquisition requirement, which contains fixed time interval requirement; "combining terrain data to determine the validity of monitoring point data" belongs to conditional data acquisition requirement, which needs to trigger the acquisition of terrain data when verifying the rationality of monitoring point location; "encrypting data collection frequency and prioritizing the acquisition of monitoring data around key pollution sources during pollution warning period" belongs to triggered data acquisition requirement, which automatically adjusts the frequency and priority of data acquisition when the pollution warning state is activated.

[0027] The extraction of data call frequency information needs to be combined with the business execution rules. The business adjusts the monitoring frequency by time period in daily routine, with higher frequency in morning and evening peak hours, lower frequency in noon and night, and the average number of calls to the atmospheric monitoring database per unit time is counted; the periodicity of calling weather data is once an hour, so the call frequency to the weather database is determined; the terrain data is called infrequently, only triggered when a new monitoring point is added or the monitoring range is adjusted, and the frequency per unit time is calculated according to the historical average monthly call number; the encrypted call frequency during pollution warning period is calculated according to the historical warning duration and the number of calls during the period. The business identification information "DQ-001" is associated with the extracted various data requirement types and corresponding call frequency information, and stored to form a basic requirement information table.

[0028] Step S1211: Iterating through each service requirement description in the set of service requirement descriptions, identifying the data related expression content in each service requirement description sentence by sentence.

[0029] The set of business requirement descriptions is traversed, and each description is processed sentence by sentence. Taking the requirement of the water environment monitoring system "SJ-001" as an example, its description content includes the sentences "set monitoring period according to river basin partition, collect pH value, dissolved oxygen content, permanganate index, heavy metal ion concentration and other water quality parameters of the main stream, tributaries and reservoir sections", "need to synchronously obtain section water level and flow rate data to calculate pollutant flux", "in the flood season, adjust the sampling frequency in real time according to the rainfall", "and need to associate the monitoring data of the coastal sewage outlet to perform source tracing analysis", "and need to update the historical database when generating the water quality status report every month", and the like.

[0030] The data collection, acquisition, association and update related expressions such as "collect pH value, dissolved oxygen content and other water quality parameters", "synchronously obtain section water level and flow rate data", "adjust the sampling frequency according to the rainfall", "associate the monitoring data of the coastal sewage outlet", and "update the historical database" are identified sentence by sentence, which are data related expression contents and are extracted separately for subsequent semantic analysis. For the data related content in the compound sentence, such as "calculate pollutant flux", which depends on the water level and flow rate data, the data acquisition part and the data processing part need to be separated, and only the data related expression is extracted.

[0031] Step S1212: performing semantic analysis processing on the data related expression content, distinguishing the data acquisition requirement expression, the data update requirement expression and the data sharing requirement expression in the data related expression content, and determining the requirement categories corresponding to the data acquisition requirement expression, the data update requirement expression and the data sharing requirement expression as the data requirement type.

[0032] The data related expression content of the extracted requirement of the water environment monitoring system "SJ-001" is subjected to semantic analysis. In the expression "collect pH value, dissolved oxygen content and other water quality parameters", the "collection" action clearly points to obtaining original data from monitoring equipment, which belongs to the data acquisition requirement expression, and the data acquisition requirement expression further includes the specific indicators and collection objects of the data, which are further subdivided into the requirement of acquiring conventional monitoring data.

[0033] In the expression "synchronously obtain section water level and flow rate data", "synchronous acquisition" indicates that the data needs to be consistent with the water quality parameter data in time, which belongs to the associated data acquisition requirement, emphasizing the timeliness matching of data acquisition. In the expression "associate the monitoring data of the coastal sewage outlet", the "association" action means obtaining related data from other data sources for joint analysis, which belongs to the associated query type data acquisition requirement.

[0034] The "updating historical database" in "generate water quality status report every month and update historical database" refers to writing processed report data into a storage system, which belongs to data update requirement expression. The data update requirement expression clearly defines the trigger condition and data object of the update. In the cross-system collaboration requirement, if there is a statement "push water quality exceeding standard information to ecological governance dispatching system", it belongs to data sharing requirement expression, and such expression is not involved in the current business requirement. Through the above analysis, the demand category corresponding to the data related expression content is determined as the data requirement type, including regular monitoring data acquisition, associated data acquisition, associated query data acquisition, data update, etc.

[0035] Step S1213: Count the number of times the corresponding business is executed in the historical preset time period in each business requirement description, and count the number of data calls each time the business is executed in the historical preset time period; based on the length of the historical preset time period, calculate the business execution frequency per unit time, and then combine the number of data calls each time the business is executed to determine the number of data calls per unit time corresponding to the business requirement description. The number of data calls per unit time is determined as the data call frequency information.

[0036] Taking the water environment monitoring system "SJ-001" requirement as an example, the historical preset time period is set to half a year. The execution of the business in this period is counted. The business sets the monitoring period according to the watershed partitioning, and the monitoring period of different watersheds is different. Some watersheds are monitored twice a week, and some watersheds are monitored three times a month. By summarizing the monitoring execution records of all watersheds, the total number of business executions in half a year is obtained.

[0037] The data call situation in each business execution process is counted. Each time the regular monitoring is performed, 4 water quality parameters are called from the water quality monitoring database, 2 water level and flow rate data are called from the hydrological database, and some watersheds also need to call the pollution source list database to obtain the data of the sewage outlet. Therefore, the number of data calls each time the business is executed varies from watershed to watershed. The average value of the number of calls each time the business is executed in all watersheds is taken as the average number of data calls each time the business is executed.

[0038] Based on the length of the historical preset time period (half a year, calculated as the total number of days per month), the total number of business executions is divided by the total number of days to obtain the business execution frequency per unit time (per day). The business execution frequency per unit time is multiplied by the average number of data calls each time the business is executed to obtain the number of data calls per unit time, i.e. the data call frequency information. For the additional calls in special periods such as flood season, the number of occurrences and the number of calls are counted separately and included in the overall data call frequency information according to the weight.

[0039] Step S1214: Store the business identification information corresponding to each service requirement description and the extracted data requirement type and data call frequency information in association to form a basic requirement information table for each service requirement description.

[0040] A basic requirement information table is created for each service requirement description. Taking the water environment monitoring system "SJ-001" requirement as an example, the business identification information "SJ-001" is used as the primary key of the table. The table includes a data requirement type column, which records the types of regular monitoring data acquisition, associated data acquisition, associated query data acquisition, data update, etc.; and a data call frequency information column, which records the number of calls to the water quality monitoring database, hydrological database, and pollution source list database in a unit time and the total number of calls.

[0041] The table also includes a data requirement description column, which details the specific data indicators, sources, and conditions corresponding to each data requirement type, such as "regular monitoring data acquisition - water quality parameters: pH value, dissolved oxygen content, source: water quality monitoring database, condition: dry flow section collected every Monday and Thursday". Through associated storage, the business identification information is one-to-one corresponding to the data requirement type and data call frequency information, facilitating subsequent mapping processing and rule construction.

[0042] Step S1215: Aggregate the basic requirement information tables of all service requirement descriptions to obtain a requirement information set containing the business identification information, data requirement type, and data call frequency information of each service requirement description.

[0043] The basic requirement information tables of all service requirement descriptions, including the atmospheric environment monitoring system, water environment monitoring system, and cross-system collaboration requirements, are aggregated. During the aggregation process, the basic requirement information tables are grouped by business system category, such as atmospheric environment monitoring, water environment monitoring, and cross-system collaboration.

[0044] The requirement information set is stored in a structured data format and includes business identification information, belonging business system, data requirement type list, call frequency information of each data source, data requirement description, and other fields. Through aggregation, a comprehensive requirement information set is formed, providing complete input data for subsequent mapping processing with the data source capability information of the unified data foundation, ensuring that each data requirement of the business requirement can be accurately matched to the corresponding data source.

[0045] Step S122: Obtain the data source capability information of the unified data foundation, which includes the type identification, data storage format, and data output method of each data source in the unified data foundation.

[0046] The metadata management module of the unified data base obtains the data source capability information. The type identification of the atmospheric monitoring database is "DATA-ATMOS-001", the data storage format adopts a time series database format, the data is organized according to the monitoring point ID, timestamp and pollutant code, each record contains fields such as numerical value, precision and state identification, and the data output mode supports HTTP RESTful API query, MQTT real-time data stream push and batch CSV file export.

[0047] The type identification of the water quality monitoring database is "DATA-WATER-001", the data storage format adopts a combination of a relational database and file storage, structured data stores monitoring index values, and unstructured data stores water sample spectrum images, and the data output mode includes a SQL query interface, a WebSocket real-time data push and a time range compression package download.

[0048] The type identification of the weather database is "DATA-METEO-001", the data storage format is distributed time series storage, supports high concurrency reading and writing, the data output mode has a timed FTP batch upload, an API real-time query and a subscription push, and the subscription content can be customized according to the weather element type. The capability information of each data source also includes performance parameters such as maximum concurrent connection number, data update frequency and historical data retention period, which are sorted into a data source capability information table and stored in the metadata database.

[0049] Step S123: Match the data requirement type in each business requirement description with the type identification of the data source of the unified data base, and determine the candidate data source list corresponding to each data requirement type.

[0050] For the data acquisition requirement type in the atmospheric environment monitoring system "DQ-001" requirement, match "particulate matter concentration data acquisition" with the data source type identification. In the data source capability information, the type identification "DATA-ATMOS-001" of the atmospheric monitoring database corresponds to the business description containing particulate matter concentration, gaseous pollutant concentration and other monitoring data, so it is included in the candidate data source list.

[0051] The "weather data acquisition" requirement type matches the type identification "DATA-METEO-001" of the weather database, and this data source supports the output of wind speed, wind direction, temperature stratification and other weather elements, so it is included in the candidate data source list. For the "terrain data acquisition" requirement type, match the type identification "DATA-TERRAIN-001" of the terrain database, and the capability information of this data source includes the storage and output of terrain elevation, slope and other data, and is included in the candidate data source list.

[0052] Each data requirement type can correspond to multiple candidate data sources, for example, if there is a backup weather database, its type identification is different but the data content is the same, and it will also be included in the candidate list. Through the above matching processing, a candidate data source list containing all possible matching data sources is generated for each data requirement type.

[0053] Step S124: According to the data call frequency information in each service requirement description, the data sources in the candidate data source list whose data output response speed meets the data call frequency information are screened to obtain the target data source corresponding to each service requirement description.

[0054] For the data requirement type of "timely calling weather data" in the atmospheric environment monitoring system "DQ-001" requirement, the data call frequency information is once per hour. The historical data output response records of the weather database are extracted from the candidate data source list, which contain the start time and end time of each response to the data call request. The response time of each response is obtained by calculating the difference between the end time and the start time.

[0055] The average value of the historical response time of the weather database is calculated as its average response speed. Analyze the response speed requirement corresponding to the data call frequency information. The maximum response time allowed by the hourly call frequency can be determined according to the business processing period, for example, the data acquisition needs to be completed within 10 minutes to ensure that the subsequent analysis is on time.

[0056] The data sources in the candidate data source list whose average response speed corresponds to the response time that is less than or equal to the maximum allowed response time are screened out to form a preliminary screening data source list. Check if the data storage format of the weather database in the preliminary screening data source list is consistent with the data format requirement in the business requirement. The business requirement requires that the weather data be in JSON format, containing fields such as timestamp, element code, value, unit, etc. If the data output format of the weather database meets the requirements, the data source is retained and determined as the target data source corresponding to the data requirement type.

[0057] Step S1241: Extract the historical data output response record of each data source in the candidate data source list, which contains the response time of the data source responding to each data call request.

[0058] The historical data output response record of the candidate data source is extracted through the performance monitoring module of the unified data pedestal. Taking the water quality monitoring database as an example, its historical response record is stored in the performance log, and each record contains request ID, caller identification, request time, response start time, response completion time, request data volume, response status and other information.

[0059] The difference between the response completion time and the response start time is extracted from the records to obtain the response duration of each response data call request. For abnormal response records such as timeout non-response, response error, etc., they are separately marked but not included in the calculation of the normal response duration, to ensure that the extracted response duration can truly reflect the normal response performance of the data source. The extracted response duration is arranged in chronological order to form a historical response duration sequence of the data source.

[0060] Step S1242: Calculate the average value of the response duration in the historical data output response records of each data source, and determine the average value as the average response speed of the data source.

[0061] The historical response duration sequence of the water quality monitoring database is calculated, and after the marked abnormal response records are removed, the total number and total duration of the remaining effective response duration are counted. The average response duration of the data source is obtained by dividing the total duration by the number of effective response records, and the average response duration is determined as the average response speed of the data source.

[0062] During the calculation process, if there is a large difference in response duration in different time periods, such as slower response in peak period and faster response in low period, a weighted average can be performed according to the time period, giving higher weight to recent response data, so that the average response speed can better reflect the current actual performance. The average response speed, as an important indicator of data source capability, is stored in the data source capability information table.

[0063] Step S1243: Analyze the response speed requirement corresponding to the data call frequency information in each business requirement description, and determine the maximum data output response duration allowed by the business requirement according to the number of data calls per unit time.

[0064] The call frequency information of the water quality monitoring database in the SJ-001 requirement of the water environment monitoring system is analyzed. The number of calls per unit time reflects the time interval requirement of the business for data acquisition. If the number of calls per unit time is high, the business needs to acquire data more frequently, and the corresponding allowed maximum response duration should be short to avoid the accumulation of data acquisition delay affecting the business processing.

[0065] For example, if the number of calls per unit time is four times per hour, the time interval of each data call is about 15 minutes. Considering the time required for data processing, the allowed maximum data output response duration can be set to one third of the time interval. At the same time, combined with the overall processing period of the business, it is ensured that all data acquisition and processing can be completed within the business processing period, and the maximum data output response duration allowed by the business requirement is determined comprehensively.

[0066] Step S1244: Filter out the data sources in the candidate data source list whose average response time is less than or equal to the maximum data output response time allowed by the business requirement, and form a preliminary filtered data source list.

[0067] Compare the response time corresponding to the average response speed of the water quality monitoring database with the maximum data output response time allowed by the water environment monitoring system "SJ-001" requirement. If the average response time is less than or equal to the maximum allowed response time, the water quality monitoring database is included in the preliminary filtered data source list. For the hydrological database, the average response time in the historical data output response record is also calculated. If the time does not exceed the maximum allowed response time of the "SJ-001" requirement, it is also added to the preliminary filtered data source list.

[0068] After the preliminary filtered data source list is formed, each data source in the list needs to be further checked. Taking the requirement of the atmospheric environment monitoring system "DQ-001" as an example, the atmospheric monitoring database and the meteorological database filtered out preliminarily need to be checked for data storage format. The "DQ-001" requirement clearly requires the data format to be a structured data table, containing fields such as monitoring point number, monitoring time, pollutant type, and concentration value, and the field code needs to comply with the environmental monitoring data coding specification.

[0069] When checking the data storage format of the atmospheric monitoring database, it needs to be checked whether the data table structure contains all the above fields, and whether the data types of the fields match the requirements, such as the monitoring time should be date and time type, and the concentration value should be numerical type. At the same time, it is verified whether the field code is consistent with the specification, for example, whether the code of "PM2.5" in the pollutant type field meets the preset standard. If all format requirements are met, the atmospheric monitoring database is retained in the preliminary filtered list.

[0070] When checking the format of the meteorological database, it needs to be confirmed whether the wind speed and direction data provided by it are stored in the preset format, such as whether the wind speed unit is the unit specified in the requirement, whether the wind direction is recorded in the form of azimuth angle or wind direction code, and whether the naming of the data field is consistent with the field mapping relationship in the requirement. If there is a format inconsistency, such as the wind direction data using a word description instead of a code, the meteorological database will be removed from the preliminary filtered list.

[0071] For the preliminary filtered data source list of the soil environment monitoring system "TR-001" requirement, when checking the data storage format of the soil monitoring database, it needs to be verified whether the precision of the soil heavy metal content data meets the requirement, whether the recording method of the sampling depth field matches the stratification standard in the requirement, and whether the data is accompanied by necessary quality control identifiers such as sampling method code and laboratory number. Only data sources that meet all format requirements can be retained in the preliminary filtered list.

[0072] After the data storage format check, the remaining data sources are the target data sources corresponding to the business requirement description. For example, after screening, the water quality monitoring database and the hydrology database of the "SJ-001" requirement meet the format requirements and become its target data sources; the "DQ-001" requirement retains the atmospheric monitoring database and the meteorological database that meets the format requirements as the target data sources.

[0073] Step S125: Record the business identification information corresponding to each business requirement description, the type identification of the target data source, the data storage format, and the data output method, and integrate to form the business requirement mapping result.

[0074] A mapping record is established for each business requirement description, and the record content includes business identification information and detailed information of the target data source. Taking the "DQ-001" requirement as an example, the business identification information in its mapping record is "DQ-001", the type identification of the target data source is "atmospheric monitoring database-DQDB" and "meteorological database-QXDB", the data storage format is "structured data table (monitoring point number, time, pollutant type, concentration value)" and "structured data table (monitoring time, wind speed, wind direction, air pressure)", and the data output method is "atmospheric monitoring database-real-time data stream interface" and "meteorological database-timed data push service (once an hour)".

[0075] In the mapping record of the "SJ-001" requirement, the business identification information is "SJ-001", the target data source type identification is "water quality monitoring database-SJDB" and "hydrology database-SWDB", the data storage format is "water quality monitoring database-structured data table (section number, sampling time, pH value, dissolved oxygen, pollutant concentration)" and "hydrology database-structured data table (section number, monitoring time, flow, water level)", and the data output method is "water quality monitoring database-batch query interface (executed every morning)" and "hydrology database-event triggered interface (pushed when flow changes)".

[0076] In the mapping record of the "TR-001" requirement of the soil environment monitoring system, the business identification information is "TR-001", the target data source type identification is "soil monitoring database-TRDB", the data storage format is "structured data table (sampling point number, sampling time, soil type, heavy metal content, sampling depth)", and the data output method is "periodic full-volume synchronous interface (once a month)".

[0077] All the mapping records of the business requirement descriptions are integrated together to form the business requirement mapping result. The business requirement mapping result is stored in the form of structured data, and the corresponding target data source information can be quickly queried through the business identification information.

[0078] Step S130: constructing integrated execution rules of the multi-service system based on the service requirement mapping result, the integrated execution rules including data source calling sequence rules of each service system and cross-system service data interaction timing rules.

[0079] According to the service requirement mapping result, the corresponding service requirements and target data sources of each service system are sorted out, and the calling sequence of the data sources is determined; meanwhile, the cross-system collaborative service requirements are analyzed, and the data interaction sequence of each system service execution link is clarified, so as to construct complete integrated execution rules.

[0080] Step S131: according to the service requirement mapping result, all service requirement descriptions corresponding to each service system and target data sources corresponding to each service requirement description are classified according to business identification information.

[0081] The service requirement mapping result is classified according to the service system. The business identification information corresponding to the atmospheric environment monitoring system is "DQ-001", "DQ-002", etc., and all service requirement descriptions and corresponding target data sources under it are collected and sorted out, such as "DQ-001" corresponding to the atmospheric monitoring database and the meteorological database, and "DQ-002" corresponding to the air quality early warning database and the pollution source list database.

[0082] The business identification information corresponding to the water environment monitoring system is "SJ-001", "SJ-002", etc., and after classification, it can be seen that "SJ-001" corresponds to the water quality monitoring database and the hydrological database, and "SJ-002" corresponds to the water environment evaluation database and the sewage outlet monitoring database. Through the above classification, the business requirements and dependent data sources required for processing by each service system are clearly presented.

[0083] Step S132: for each service system, according to the business execution priority of each service requirement description in the service system, the calling sequence of the target data sources corresponding to each service requirement description is determined, and the data source calling sequence rules of the service system are formed.

[0084] The service requirement descriptions in each service system are prioritized, and the calling sequence of the target data sources is determined according to the priority. For example, in the atmospheric environment monitoring system, the priority of "DQ-001" (daily monitoring data collection) is lower than that of "DQ-003" (emergency monitoring in heavy pollution weather), so in the data source calling, the emergency monitoring data source corresponding to "DQ-003" will be called in priority to the regular data source of "DQ-001".

[0085] Step S1321: extracting the business emergency degree expression and business influence range expression in each service requirement description in each service system.

[0086] Extract relevant expressions from the business requirement description. The requirement description of the atmospheric environment monitoring system "DQ-003" contains "During the heavy pollution weather warning period, high-frequency collection of pollutant data is required to support emergency decision-making in a timely manner", among which "During the heavy pollution weather warning period", "high-frequency collection", and "timely support for emergency decision-making" are business urgency expressions; "covering the entire urban area and surrounding key industrial areas, data anomalies will affect the development of emergency emission reduction measures" is a business impact range expression.

[0087] In the requirement description of the water environment monitoring system "SJ-003" (emergency water pollution event monitoring), "After a sudden leakage event occurs, encrypted monitoring needs to be started immediately" is a business urgency expression; "The monitoring range includes all drinking water sources downstream of the incident point and sensitive ecological protection areas" is a business impact range expression.

[0088] Step S1322: Determine the urgency level of each business requirement description according to the business urgency expression, and determine the impact range level of each business requirement description according to the business impact range expression.

[0089] According to the intensity of the business urgency expression, the level is divided. The expressions "heavy pollution weather warning period", "high frequency", and "timely" in the "DQ-003" requirement indicate that the urgency is high, and are classified as the first level of urgency; the "daily regular collection" expression in the "DQ-001" requirement corresponds to the third level of urgency.

[0090] According to the coverage range of the business impact range expression, the level is divided. The "entire urban area and surrounding key industrial areas" coverage range of the "DQ-003" requirement is wide, and the impact range level is classified as the first level; the "certain industrial park area" coverage range of the "DQ-004" (local area monitoring) requirement is small, and the impact range level is classified as the third level.

[0091] Step S1323: Determine the business execution priority of each business requirement description according to the high and low of the urgency level and the wide and narrow of the impact range level. The higher the urgency level and the wider the impact range level, the higher the business execution priority.

[0092] Determine the priority by combining the two levels. The "DQ-003" has the first level of urgency and the first level of impact range, and the business execution priority is the highest; the "SJ-003" has the first level of urgency and the second level of impact range, and the priority is second; the "DQ-001" has the third level of urgency and the second level of impact range, and the priority is lower.

[0093] Step S1324: Arrange the target data sources corresponding to each business requirement description in the business system in order from high to low according to the business execution priority.

[0094] In the atmospheric environment monitoring system, the priority from high to low is "DQ-003", "DQ-002", "DQ-001", and the corresponding target data source calling order is emergency monitoring data source, early warning analysis data source and routine monitoring data source.

[0095] Step S1325: Record the calling sequence of the arranged target data sources and the business identifier information of the business demand description corresponding to each target data source, and form the data source calling sequence rule of the business system.

[0096] The data source calling sequence rule of the atmospheric environment monitoring system is recorded as: the first "emergency monitoring data source (corresponding to DQ-003)", the second "early warning analysis data source (corresponding to DQ-002)", and the third "routine monitoring data source (corresponding to DQ-001)". The calling trigger condition of each data source is also mentioned in the rule, such as "emergency monitoring data source is automatically activated for priority calling after the heavy pollution weather warning signal is issued".

[0097] Step S133: Identify the cross-system collaborative business demand description in the business demand description set, and extract all business systems and business execution links of each business system involved in the cross-system collaborative business demand description.

[0098] Identify the cross-system collaborative demand from the business demand description set. The "XT-001" demand description involves the atmospheric environment monitoring system, the ecological management and dispatching system, and the environmental emergency response system, wherein the business execution link of the atmospheric environment monitoring system is "excessive data acquisition and analysis", the link of the ecological management and dispatching system is "emission reduction scheme formulation", and the link of the environmental emergency response system is "early warning preparation and resource allocation".

[0099] Step S134: Determine the dependency relationship between the business execution links of each business system in the cross-system collaborative business demand description, set the data interaction sequence of the business execution links of each business system according to the dependency relationship, and form the cross-system business data interaction timing rule.

[0100] Analyze the dependency relationship of each link and formulate the interaction sequence. In the "XT-001" demand, the "emission reduction scheme formulation" of the ecological management and dispatching system depends on the result of "excessive data acquisition and analysis" of the atmospheric environment monitoring system, and the "early warning preparation" of the environmental emergency response system depends on the result of "scheme formulation" of the ecological management and dispatching system, so the data interaction sequence is atmospheric environment monitoring system-ecological management and dispatching system-environmental emergency response system.

[0101] Step S1341: Analyze the cross-system collaborative business demand description, determine the complete business process corresponding to the cross-system collaborative business demand description, split the complete business process into multiple continuous business execution links, and each business execution link corresponds to a business system.

[0102] According to the analysis of the "XT-001" requirement description, the complete business process is "atmospheric pollutants exceed the standard-data collection and analysis-developing emission reduction scheme-starting early warning preparation", which is divided into three business execution links: atmospheric environment monitoring system executes "pollutant data collection and analysis", ecological management and scheduling system executes "developing emission reduction scheme based on the data", and environmental emergency response system executes "starting early warning preparation according to the emission reduction scheme".

[0103] Step S1342: Analyze the input data sources required by each business execution link, and determine whether the input data comes from the output data of other business execution links of the business system. If yes, it is determined that the business execution link depends on the business execution link providing the input data.

[0104] The "developing emission reduction scheme" link of the ecological management and scheduling system needs to input atmospheric pollutant data and analysis report, which comes from the output of the atmospheric environment monitoring system, so it depends on the business execution link of the atmospheric environment monitoring system. The "early warning preparation" link of the environmental emergency response system needs to input the content of the emission reduction scheme, which comes from the output of the ecological management and scheduling system, so it depends on the business execution link of the ecological management and scheduling system.

[0105] Step S1343: According to the dependency relationship, a dependency relationship diagram of the business execution link is constructed. Each node in the dependency relationship diagram represents a business execution link, and the connection between the nodes represents the dependency relationship. The connection direction points from the business execution link providing data to the business execution link depending on data.

[0106] In the dependency relationship diagram of the "XT-001" requirement, node A is "atmospheric environment monitoring system-data collection and analysis", node B is "ecological management and scheduling system-scheme development", and node C is "environmental emergency response system-early warning preparation". The connection is from A to B and from B to C, which clearly shows the data dependency flow direction.

[0107] Step S1344: According to the dependency relationship diagram, the data interaction time interval of each business execution link is set according to the dependency order of the business execution link, so that the data of the previous business execution link can be obtained by the dependent business execution link in time after the data is output.

[0108] According to the requirement of the business process, the time interval is set. After the data of A link is output, B link needs to obtain the data within a specified time and start scheme development, and the data interaction time interval from A to B is set to a short time. After the scheme of B link is output, C link needs to obtain and start early warning preparation within a specified time, and the time interval from B to C is set to another time interval to ensure efficient connection of the whole process.

[0109] Step S1345: Record the sequence of business execution steps of each business system, data interaction time interval and data interaction content description, and form the cross-system business data interaction timing rules.

[0110] The timing rules required by "XT-001" are recorded as follows: sequence 1 "atmospheric environment monitoring system-data collection and analysis" outputs "pollutant over-standard data and analysis report"; sequence 2 "ecological management and dispatching system-scheme development" starts within a specified time after receiving, and outputs "emission reduction scheme"; sequence 3 "environmental emergency response system-early warning preparation" starts within a specified time after receiving the scheme. The data interaction content description specifies the format and key fields of the data of each step, such as the analysis report which needs to include the types, concentrations and distribution areas of over-standard pollutants.

[0111] Step S135: Integrate the data source calling sequence rules of all business systems and all cross-system business data interaction timing rules to form integrated execution rules of multiple business systems.

[0112] The data source calling sequence rules of each business system and the cross-system timing rules are summarized to form an integrated execution rule table. The table is classified by business systems and contains the data source calling sequence, trigger conditions of each system, as well as the execution sequence, time interval and data content of cross-system business, providing a unified standard for the coordinated operation of each business system.

[0113] Step S140: Distribute the integrated execution rules to the business processing modules of each business system, trigger the business processing modules of each business system to call the data sources of the unified data base for business processing according to the integrated execution rules, and obtain the business coordination execution results.

[0114] The integrated execution rules are distributed to each business system through a dedicated communication channel, and each business processing module calls the data source and performs business according to the rules, and the cross-system business completes data interaction according to the timing rules, and finally forms the business coordination execution results.

[0115] Step S141: Establish a communication link between the management module of the unified data base and the business processing modules of each business system.

[0116] An encrypted communication link is established, and a special protocol is used for data transmission. The management module of the unified data base and the business processing modules of the atmospheric environment monitoring system establish a main link and a backup link. The main link uses wired communication method, and the backup link uses wireless communication method, to ensure the stability of communication. Identity authentication and encryption negotiation are completed during the link establishment process to ensure the security of data transmission.

[0117] Step S142: The data source calling sequence rule and the cross-system business data interaction timing rule in the integrated execution rule are sent to the business processing module of the corresponding business system through the communication link.

[0118] The data source calling sequence rule of the atmospheric environment monitoring system is sent to its business processing module through the established communication link. The rule is transmitted in the form of a structured data packet and contains a check code to ensure integrity. The cross-system business data interaction timing rule "XT-001" is sent to the business processing modules of the atmospheric environment monitoring system, the ecological management and dispatching system, and the environmental emergency response system. Each system only receives the part of the rule related to itself.

[0119] Step S143: After receiving the data source calling sequence rule, the business processing module of each business system sends a data calling request to the data source of the unified data base according to the calling sequence in the data source calling sequence rule.

[0120] After receiving the rule, the business processing module of the atmospheric environment monitoring system sends a calling request to the emergency monitoring data source, the early warning analysis data source, and the routine monitoring data source in sequence when the trigger condition is met. The request contains business identification information, the time range of the required data, field list, and other parameters.

[0121] Step S1431: The business processing module of each business system parses the received data source calling sequence rule and extracts the target data source arrangement sequence and the corresponding business identification information of each target data source.

[0122] The business processing module of the atmospheric environment monitoring system parses the rule and extracts the target data source arrangement sequence as "emergency monitoring data source - early warning analysis data source - routine monitoring data source" and the corresponding business identification information "DQ-003" "DQ-002" "DQ-001".

[0123] Step S1432: The business processing module of each business system determines the target data source that needs to be called currently according to the target data source arrangement sequence and generates a data calling request containing the type identification of the target data source and the corresponding business identification information.

[0124] According to the arrangement sequence, the emergency monitoring data source needs to be called first. The business processing module generates a data calling request containing the target data source type identification "emergency monitoring data source - YJJC" and the business identification information "DQ-003", and notes that the data required is "high-frequency monitoring data of PM2.5 concentration in the last hour".

[0125] Step S1433: The business processing module of each business system checks the communication state between itself and the current target data source. If the communication state is normal, the data call request is directly sent. If the communication state is abnormal, a backup communication path is started, and the data call request is sent through the backup communication path.

[0126] The business processing module sends a communication test signal to the emergency monitoring data source. If a normal response is received, the communication state is determined to be normal, and the data call request is directly sent. If no response or an abnormal response is received, a backup communication path is started. The backup communication path uses a different network interface and transmission protocol, and the request is re-sent through the backup path.

[0127] Step S1434: After sending the data call request, the business processing module of each business system waits for the response information returned by the data source of the unified data foundation. If the response information is received within the preset waiting time, subsequent business processing is performed. If the response information is not received within the preset waiting time, the data call request is re-sent.

[0128] Timing starts after the request is sent. If the PM2.5 concentration data returned by the emergency monitoring data source is received within the preset waiting time, data verification and analysis are performed. If no response is received within the time, the call request is automatically re-sent, up to a specified number of times. If there is still no response, fault information is recorded and the next sequential data source is switched to.

[0129] Step S1435: After sequentially completing the call request sending of all target data sources in accordance with the target data source arrangement order, the business processing module of each business system records the sending time and response receiving time of each call request, and associates the corresponding business identification information and data source type identification.

[0130] For example, after completing the calls to the emergency monitoring data source, the meteorological data source, and the geographic information data source, the environmental emergency response system "YJ-001" records the sending time of calling the emergency monitoring data source as the first minute of a specific time period each day, and the response receiving time as the third minute of the time period; the sending time of calling the meteorological data source as the fifth minute of the time period, and the response receiving time as the sixth minute of the time period; and the sending time of calling the geographic information data source as the eighth minute of the time period, and the response receiving time as the ninth minute of the time period.

[0131] These recorded contents also include the data type of each call request (such as PM2.5 concentration data, wind speed data, and monitoring point coordinate data), request message number, response message status code, and other information. All records are arranged in chronological order into call log information and stored in the local log file of the business system, and are simultaneously uploaded to the log management module of the unified data foundation for centralized archiving.

[0132] Step S150: According to the business cooperation execution result, the integrated management instruction of the multi-business system is generated, and the integrated management instruction is sent to the management module of the unified data foundation and the business processing module of each business system to execute the integrated optimization operation. The integrated management instruction includes business processing parameter adjustment instruction and data source allocation optimization instruction.

[0133] In the regional ecological environment monitoring and management integrated platform, the business cooperation execution result covers the independent business processing result of each business system and the cross-system cooperative business processing result. For example, the result after the air environment monitoring system completes the pollutant concentration analysis, the water quality evaluation result of the water environment monitoring system, and the emission reduction scheme formulated by the ecological management scheduling system in the "XT-001" cross-system cooperative business and the warning preparation state of the environmental emergency response system.

[0134] Based on these results, the problems existing in the business processing process are analyzed, and the corresponding integrated management instruction is generated. If it is found that a certain business system processing takes too long, a business processing parameter adjustment instruction is generated; if some data sources appear response delay due to frequent calling, a data source allocation optimization instruction is generated, and then these instructions are sent to the corresponding module to execute optimization operation.

[0135] Step S151: Analyze the business cooperation execution result, extract the business processing completion information of each business system and the cross-system cooperative business processing completion information, and the business processing completion information includes business processing time and business processing accuracy.

[0136] When analyzing the business cooperation execution result, the business processing time and business processing accuracy of each business system are extracted from the result data. Taking the soil environment monitoring system "TR-001" as an example, the business processing time is the total time from receiving the data calling request to generating the soil pollution evaluation report; the business processing accuracy is determined by comparing the data in the evaluation report with the field sampling measured data.

[0137] For the cross-system cooperative business "XT-001", the business execution link time of each participating business system (such as the air environment monitoring system exceeding standard information sending time, ecological management scheduling system scheme formulation time, and environmental emergency response system warning preparation time) and the completion rate of the whole cooperative business (such as the proportion of the number of completing the emission reduction scheme formulation and warning preparation according to the plan to the total number of cooperation) are extracted.

[0138] Step S152: According to the business processing time, it is judged whether the business processing module of the corresponding business system exists processing delay, if the business processing time exceeds the preset time threshold, it is determined that the processing parameter of the business processing module of the business system needs to be adjusted, and the business processing parameter adjustment instruction containing the name of the parameter to be adjusted and the adjustment direction is generated.

[0139] The preset time consumption threshold is set according to the historical average processing time consumption of the business system and the importance of the business. For example, the preset time consumption threshold of the ecological management scheduling system "ZD-001" is two hours. If the time consumption of a certain business processing reaches three hours, it exceeds the threshold, and it is judged that there is processing delay.

[0140] The to-be-adjusted parameter name can include data processing thread number, data cache size, algorithm iteration number, etc. The adjustment direction is determined according to the delay reason. If the delay is caused by insufficient data processing threads, the adjustment direction is to increase the number of threads; if the delay is caused by insufficient cache, the adjustment direction is to increase the cache size. The generated business processing parameter adjustment instruction clearly marks these contents.

[0141] Step S153: Analyze the number of calls and data output of each data source in the business cooperative execution result, identify the data source with too many calls causing response delay, determine the need to optimize the allocation mode of the data source, and generate a data source allocation optimization instruction containing data source allocation ratio adjustment and standby data source activation suggestion.

[0142] The number of calls of each data source in the business cooperative execution process is counted, and the response time change of data output is combined to identify the data source with frequent calls and response delay. For example, the atmospheric monitoring database is called frequently during the high pollution period, causing the response speed to decrease.

[0143] For such data sources, the allocation ratio of each business system is adjusted to reduce the call quota of non-critical business; at the same time, it is suggested to activate the standby atmospheric monitoring database to share the pressure of the main data source. The data source allocation optimization instruction specifies the adjusted allocation ratio value and the activation condition of the standby data source (such as automatically activating when the main data source response delay exceeds a certain time length).

[0144] Step S154: Integrate the business processing parameter adjustment instruction and the data source allocation optimization instruction into integrated management instructions of multiple business systems, and add instruction effective time and instruction execution object identification to each integrated management instruction.

[0145] When integrating the instructions, classify and arrange them according to the instruction type and execution object. Add the effective time to each instruction, such as setting the business processing parameter adjustment instruction to take effect during the non-peak period of the day, and the data source allocation optimization instruction can take effect immediately.

[0146] The instruction execution object identification clearly indicates the receiving module of the instruction, such as the execution object identification of the business processing parameter adjustment instruction being the business processing module of the corresponding business system, and the execution object identification of the data source allocation optimization instruction being the management module of the unified data foundation. The integrated management instruction forms structured data, including instruction ID, type, content, effective time, execution object, etc.

[0147] Step S155: Establish an instruction transmission channel with the management module of the unified data base and the business processing module of each business system, send the corresponding integrated management instruction to the management module of the unified data base and the business processing module of each business system according to the instruction execution object identifier, trigger the management module of the unified data base to adjust the data source distribution mode, trigger the business processing module of each business system to adjust the business processing parameter, and execute the integrated optimization operation.

[0148] The instruction transmission channel is established through an encrypted communication protocol to ensure the security and integrity of the instruction transmission. According to the instruction execution object identifier, the business processing parameter adjustment instruction is sent to the business processing module of the corresponding business system, which adjusts the data processing thread quantity, cache size and other parameters according to the instruction content after receiving the instruction.

[0149] After receiving the data source distribution optimization instruction, the management module of the unified data base reconfigures the calling quota of the data source and enables the standby data source. After executing the optimization operation, each module feeds back the execution result, the integrated management platform records the instruction execution situation, and forms the optimization operation log.

[0150] Figure 2 A schematic diagram of exemplary hardware and software components of a multi-business system integration management system 100 based on a unified data base that can implement the idea of the present application is shown. For example, the processor 120 can be used in the multi-business system integration management system 100 based on a unified data base, and is used to execute the functions in the present application.

[0151] The multi-business system integration management system 100 based on a unified data base can be a general server or a special-purpose server, both of which can be used to implement the multi-business system integration management method based on a unified data base of the present application. Although only one server is shown in the present application, for the sake of convenience, the functions described in the present application can be implemented in a distributed manner on multiple similar platforms to balance the processing load.

[0152] For example, the unified data foundation based multi-business system integration management system 100 can include a network port 110 connected to a network, one or more processors 120 for executing program instructions, a communication bus 130, and different forms of storage media 140, such as a disk, a ROM, or a RAM, or any combination thereof. The unified data foundation based multi-business system integration management system 100 can also include program instructions stored in a ROM, a RAM, or other types of non-transitory storage media, or any combination thereof, for example. The methods of the present application can be implemented according to these program instructions. The unified data foundation based multi-business system integration management system 100 also includes an I / O interface 150 between the computer and other input and output devices.

[0153] For ease of illustration, only one processor is described in the unified data foundation based multi-business system integration management system 100. However, it should be noted that the unified data foundation based multi-business system integration management system 100 in the present application can also include multiple processors, so the steps performed by one processor described in the present application can also be jointly performed or separately performed by multiple processors. For example, if the processor of the unified data foundation based multi-business system integration management system 100 performs steps A and B, it should be understood that steps A and B can also be jointly performed by two different processors or separately performed in one processor. For example, a first processor performs step A, a second processor performs step B, or the first processor and the second processor jointly perform steps A and B.

[0154] In addition, the present application also provides a readable storage medium, wherein computer executable instructions are pre-set in the readable storage medium, and when a processor executes the computer executable instructions, the unified data foundation based multi-business system integration management method is implemented.

[0155] It should be noted that, in order to simplify the description of the present application and to help understand one or more embodiments of the present application, in the foregoing description of the embodiments of the present application, various features are sometimes combined into one embodiment, figure or description thereof.

Claims

1. A method for managing integration of multi-services based on a unified data foundation, characterized by, The method comprises: obtaining a service demand description set of a multi-service system, the service demand description set comprising daily service processing demand descriptions and cross-system collaborative service demand descriptions of each service system, each service demand description corresponding to unique service identification information; mapping the service demand description set and data source capability information of a unified data base, matching the data source type and data providing mode in the unified data base according to the data demand content in each service demand description to obtain a service demand mapping result, specifically comprising: parsing each service demand description in the service demand description set to extract the data demand type and data call frequency information in each service demand description; obtaining data source capability information of the unified data base, the data source capability information comprising type identification, data storage format and data output mode of each data source in the unified data base; matching the data demand type in each service demand description with the type identification of the data source of the unified data base to determine a candidate data source list corresponding to each data demand type; screening the data source in the candidate data source list whose data output response speed meets the data call frequency information according to the data call frequency information in each service demand description to obtain a target data source corresponding to each service demand description; recording the service identification information, type identification, data storage format and data output mode of the target data source corresponding to each service demand description to integrate and form a service demand mapping result; constructing an integrated execution rule of the multi-service system based on the service demand mapping result, the integrated execution rule comprising data source call sequence rules and cross-system business data interaction timing rules of each service system; the construction of the integrated execution rule of the multi-service system based on the service demand mapping result comprises: obtaining all service demand descriptions corresponding to each service system and target data sources corresponding to each service demand description according to the service identification information based on the service demand mapping result; determining the call sequence of the target data sources corresponding to each service demand description according to the business execution priority of each service demand description in the service system to form the data source call sequence rule of the service system for each service system; identifying the cross-system collaborative service demand descriptions in the service demand description set, extracting all service systems and business execution links of each service system involved in the cross-system collaborative service demand descriptions; determining the dependency relationship between the business execution links of each service system in the cross-system collaborative service demand descriptions, setting the data interaction sequence of the business execution links of each service system according to the dependency relationship to form a cross-system business data interaction timing rule; integrating the data source call sequence rules of all service systems and all cross-system business data interaction timing rules to form the integrated execution rule of the multi-service system; issuing the integrated execution rule to the business processing modules of each service system to trigger the business processing modules of each service system to call the data sources of the unified data base for business processing according to the integrated execution rule to obtain a business collaborative execution result; According to the business cooperation execution result, an integrated management instruction of the multi-business system is generated, and the integrated management instruction is sent to a management module of a unified data base and a business processing module of each business system to perform an integrated optimization operation, wherein the integrated management instruction includes a business processing parameter adjustment instruction and a data source allocation optimization instruction.

2. The unified data foundation-based multi-service system integration management method according to claim 1, characterized in that, The data requirement type and data call frequency information in each business requirement description are extracted by analyzing each business requirement description in the business requirement description set. Each business requirement description in the business requirement description set is traversed, and data-related expression content in each business requirement description is identified sentence by sentence. The data-related expression content is subjected to semantic analysis processing, and data acquisition requirement expressions, data update requirement expressions, and data sharing requirement expressions in the data-related expression content are distinguished, and the requirement categories corresponding to the data acquisition requirement expressions, the data update requirement expressions, and the data sharing requirement expressions are determined as the data requirement type. The number of business executions of the corresponding business in a historical preset time period in each business requirement description is counted, and the number of data calls at each business execution in the historical preset time period is counted; based on the length of the historical preset time period, the business execution frequency per unit time is calculated, and in combination with the number of data calls at each business execution, the number of data calls per unit time corresponding to the business requirement description is determined, and the number of data calls per unit time is determined as the data call frequency information. The business identification information corresponding to each business requirement description is associated with the extracted data requirement type and data call frequency information and stored to form a basic requirement information table of each business requirement description. The basic requirement information tables of all business requirement descriptions are summarized to obtain a requirement information set containing the business identification information, the data requirement type, and the data call frequency information of each business requirement description.

3. The unified data foundation-based multi-service system integration management method of claim 1, wherein, According to the data call frequency information in each business requirement description, data sources in the candidate data source list whose data output response speed meets the data call frequency information are screened to obtain the target data source corresponding to each business requirement description, including: The historical data output response records of each data source in the candidate data source list are extracted, and the historical data output response records contain the response time of each data source responding to a data call request; The average value of the response time in the historical data output response records of each data source is calculated, and the average value is determined as the average response speed of the data source; The response speed requirement corresponding to the data call frequency information in each business requirement description is analyzed, and the maximum data output response time allowed by the business requirement is determined according to the number of data calls per unit time; Data sources in the candidate data source list whose average response speed meets the maximum data output response time allowed by the business requirement are screened out to form a preliminary screening data source list. Check whether the data storage format of each data source in the preliminary screening data source list is consistent with the data format requirement in the business requirement description, retain the data source with consistent data storage format, and determine the retained data source as the target data source corresponding to the business requirement description.

4. The unified data foundation-based multi-service system integration management method of claim 1, wherein, According to the business execution priority of each business requirement description in the business system, determine the calling sequence of the target data source corresponding to each business requirement description, form the data source calling sequence rule of the business system, including: Extract the business emergency degree expression and business influence range expression in each business requirement description in the business system; Determine the emergency degree level of each business requirement description according to the business emergency degree expression, and determine the influence range level of each business requirement description according to the business influence range expression; According to the high and low of the emergency degree level and the wide and narrow of the influence range level, determine the business execution priority of each business requirement description, the higher the emergency degree level and the wider the influence range level, the higher the business execution priority; Arrange the target data source corresponding to each business requirement description in the business system in order from high to low according to the business execution priority; Record the calling sequence of the arranged target data source and the business identifier information of the business requirement description corresponding to each target data source, and form the data source calling sequence rule of the business system.

5. The unified data foundation-based multi-service system integration management method of claim 1, wherein, According to the dependence relationship, set the data interaction sequence of the business execution link of each business system, and form the cross-system business data interaction time sequence rule, including: Parse the cross-system collaborative business requirement description, determine the complete business process corresponding to the cross-system collaborative business requirement description, split the complete business process into multiple continuous business execution links, each business execution link corresponding to a business system; Analyze the required input data source of each business execution link, judge whether the input data comes from the output data of the business execution link of other business system, if yes, determine that the business execution link depends on the business execution link providing input data; According to the dependence relationship, construct the dependence relationship diagram of the business execution link, each node in the dependence relationship diagram represents a business execution link, and the connection between the nodes represents the dependence relationship, and the connection direction points from the business execution link providing data to the business execution link depending on data; According to the dependence sequence of the business execution link in the dependence relationship diagram, set the data interaction time interval of each business execution link, so that the data of the previous business execution link can be obtained by the subsequent dependent business execution link in time after the data is output; Record the sequence, data interaction time interval and data interaction content description of the business execution link of each business system, and form the cross-system business data interaction time sequence rule.

6. The unified data foundation-based multi-service system integration management method of claim 1, wherein, The integrated execution rule is sent to the business processing module of each business system, and the business processing module of each business system is triggered to call the data source of the unified data foundation according to the integrated execution rule to perform business processing, and obtain the business collaborative execution result, including: A communication link is established between the management module of the unified data base and the business processing modules of the various business systems; The data source calling sequence rules and the cross-system business data interaction timing rules in the integrated execution rules are sent to the business processing modules of the corresponding business systems through the communication link; After receiving the data source calling sequence rules, the business processing modules of the various business systems send data calling requests to the data sources of the unified data base according to the calling sequence in the data source calling sequence rules; After receiving the data calling requests, the data sources of the unified data base return the required data to the business processing modules of the corresponding business systems according to the data provision mode, and the business processing modules of the various business systems perform business processing operations using the returned data; When cross-system business data interaction is involved, the business processing modules of the various business systems complete cross-system data transmission and collaborative business processing according to the time interval and data interaction content description in the cross-system business data interaction timing rules, and aggregate the business processing results of all business systems to form a business collaboration execution result; After receiving the data source calling sequence rules, the business processing modules of the various business systems send data calling requests to the data sources of the unified data base according to the calling sequence in the data source calling sequence rules, including: The business processing modules of the various business systems parse the received data source calling sequence rules and extract the target data source arrangement sequence and the corresponding business identification information of each target data source in the rules; The business processing modules of the various business systems determine the target data source that needs to be called currently based on the target data source arrangement sequence, and generate a data calling request containing the type identification of the target data source and the corresponding business identification information; The business processing modules of the various business systems check the communication state between themselves and the current target data source. If the communication state is normal, the data calling request is sent directly. If the communication state is abnormal, a backup communication path is started, and the data calling request is sent through the backup communication path; After sending the data calling request, the business processing modules of the various business systems wait for the response information returned by the data sources of the unified data base. If the response information is received within the preset waiting time, subsequent business processing is performed. If the response information is not received within the preset waiting time, the data calling request is resent; After sequentially completing the calling request sending of all target data sources according to the target data source arrangement sequence, the business processing modules of the various business systems record the sending time and response receiving time of each calling request to form calling log information.

7. The unified data foundation-based multi-service system integration management method of claim 1, wherein, The business collaboration execution result is parsed, and the business processing completion information of each business system and the cross-system collaborative business processing completion information are extracted. The business processing completion information includes business processing time consumption and business processing accuracy rate; The business collaboration execution result is parsed, and the business processing completion information of each business system and the cross-system collaborative business processing completion information are extracted. The business processing completion information includes business processing time consumption and business processing accuracy rate; According to the business processing time consumption judgment, it is judged whether the business processing module of the corresponding business system exists processing delay, if the business processing time consumption exceeds the preset time consumption threshold, it is determined that the processing parameter of the business processing module of the business system needs to be adjusted, and the business processing parameter adjustment instruction containing the to-be-adjusted parameter name and the adjustment direction is generated; The analysis of the business processing parameter adjustment instruction and the data source distribution optimization instruction is integrated as the integrated management instruction of the multiple business systems, the instruction execution time and the instruction execution object identification are added for each integrated management instruction; The instruction transmission channel is established with the management module of the unified data base and the business processing module of each business system, the corresponding integrated management instruction is sent to the management module of the unified data base and the business processing module of each business system according to the instruction execution object identification, the management module of the unified data base is triggered to adjust the data source distribution mode, the business processing module of each business system is triggered to adjust the business processing parameter, and the integrated optimization operation is executed. The application discloses a kind of integrated management method of multiple business systems based on unified data base, including processor and memory, the memory and the processor connection, the memory is used to store program, instruction or code, the processor is used to execute the program, instruction or code in the memory, to realize the integrated management method of multiple business systems based on unified data base in any one of the above claims 1-7.

8. A unified data foundation-based multi-service system integration management system, characterized by, ​

Images