Multi-service system integrated management method and system based on unified data base

Abstract

The invention provides a multi-service system integrated management method and system based on a unified data base, and the method comprises the steps: firstly obtaining a service demand description set of a multi-service system, mapping the service demand description set with data source capability information of the unified data base, and obtaining a service demand mapping result; constructing an integrated execution rule of the multi-service system based on the service demand mapping result, issuing the integrated execution rule to the service processing module of each service system, and triggering service processing to obtain a service collaborative execution result; and finally, generating an integrated management instruction according to a business collaborative execution result, and sending the integrated management instruction to a unified data base management module and business processing modules of the business systems to execute integrated optimization operation, so that integrated management of the multi-business 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 and have unique business processing logic and data storage methods.

[0003] Currently, when each service system processes its own business, it mainly relies on its own business rules and local data. 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, which leads to 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, which seriously affects the collaboration efficiency and accuracy of ecological environment monitoring business, and cannot meet the demand of modern ecological environment monitoring for efficient integration management of multi-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: obtaining a set of business requirement descriptions of multi-service systems, the set of business requirement descriptions containing daily business processing requirement descriptions and cross-system collaborative business requirement descriptions of each service system, and each business requirement description corresponds to unique business identification information; 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, and obtaining a business requirement mapping result; constructing an integrated execution rule of multi-service systems based on the business requirement mapping result, the integrated execution rule containing data source calling sequence rule of each service system and cross-system business data interaction timing rule; issuing the integrated execution rule to the business processing module of each service system, triggering the business processing module of each service system to call the data source of the unified data base for business processing according to the integrated execution rule, and obtaining a business collaboration execution result; Based on the business collaborative execution results, integrated management instructions for multiple business systems are generated, and the integrated management instructions are sent to the management module of the unified data base and the business processing modules of each business system to perform integrated optimization operations. The integrated management instructions include business processing parameter adjustment instructions and data source allocation optimization instructions.

[0005] On the other hand, an embodiment of the present invention also provides a multi-business system integration management system based on a unified data base, including a processor and a machine-readable storage medium, the machine-readable storage medium is connected to the processor, the machine-readable storage medium is used to store programs, instructions or codes, and the processor is used to execute the programs, instructions or codes in the machine-readable storage medium to implement the above method.

[0006] Based on the above aspects, the embodiment of the present invention obtains a set of daily and cross-system collaborative business demand descriptions and assigns unique business identification information, and maps the business demand description set with the data source capability information of the unified data base. It can match the corresponding data source type and provision method according to the data demand content in each business demand, obtain accurate business demand mapping results, effectively solve the problem of information mismatch and insufficient utilization between each business system and the data source, and achieve efficient data docking. Based on the business demand mapping results, the integrated execution rules of multiple business systems are constructed, the data source call sequence of each business system and the cross-system business data interaction timing are clarified, the integrated execution rules are sent to the business processing modules of each business system and the business processing is triggered to obtain business collaborative execution results, thereby improving the efficiency and accuracy of business collaboration. According to the business collaborative execution results, integrated management instructions are generated and sent to the unified data base management module and the business processing modules of each business system to perform integrated optimization operations, including business processing parameter adjustment and data source allocation optimization. It can dynamically adjust system parameters and resource allocation according to actual business execution conditions, and continuously improve the efficiency and stability of multi-business system integrated management. BRIEF DESCRIPTION OF THE DRAWINGS

[0007] Figure 1 It is a schematic diagram of the execution flow of the multi-business system integration management method based on the unified data base provided by an embodiment of the present invention.

[0008] Figure 2 It is a schematic diagram of exemplary hardware and software components of a multi-business system integrated management system based on a unified data base provided by an embodiment of the present invention. DETAILED DESCRIPTION

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

[0010] Step S110: Obtain a service requirement description set of the multi-service system, which contains daily service processing requirement descriptions and cross-system collaborative service requirement descriptions of each service system. Each service requirement description corresponds to unique service identification information.

[0011] This embodiment takes a regional ecological environment monitoring and management integrated platform as an application scenario. The platform 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, relevant information is collected through the requirement collection modules of the service systems.

[0012] 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 every 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, and at the same time, encrypting the data collection frequency and preferentially obtaining the monitoring data around the key pollution sources during pollution early warning”, and the corresponding service identification information is “DQ-001”.

[0013] 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 main stream, tributary and reservoir section, needing to synchronously obtain the section water level and flow rate data to calculate the pollutant flux, adjusting the sampling frequency in real time according to the rainfall 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”.

[0014] The cross-system collaborative service requirement description is, for example, “when the atmospheric environment monitoring system monitors that the concentration of pollutants in the region continuously exceeds the standard, the information such as the over-standard period, the type of pollutants, the concentration change trend is synchronously sent to the ecological management scheduling system, the ecological management scheduling system calls the pollution source list database to screen the key control objects according to the information, and at the same time, the over-standard early warning information is pushed 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 service identification information is “XT-001”. These service requirement descriptions are summarized to form the service requirement description set, which is stored in the requirement information database. Each description contains service targets, data dependencies, processing periods, trigger conditions and the like.

[0015] Step S120: mapping the set of service requirement descriptions with the data source capability information of the unified data base, matching the corresponding data source type and data providing mode in the unified data base according to the data requirement content in each service requirement description, to obtain a service requirement mapping result.

[0016] The unified data base 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 process, the specific data requirements of each service requirement are matched with the corresponding data sources.

[0017] For the atmospheric environment monitoring system "DQ-001" requirement, the particulate matter concentration and gaseous pollutant concentration data need to be matched with the atmospheric monitoring database, which stores data according to monitoring point number and timestamp and provides multi-condition query interfaces according to region, time period, and pollutant type. The wind speed, wind direction, and temperature layer data in the meteorological data need to be matched with the meteorological database, which supports both timed batch data pushing and real-time querying. The terrain data need to be matched with the terrain database, which provides data slicing download services based on latitude and longitude ranges.

[0018] The water quality parameter data in the water environment monitoring system "SJ-001" requirement comes from the water quality monitoring database, which uses a distributed storage architecture, supports combined queries according to river basin, section type, and monitoring index, and provides both real-time data streaming and historical data batch export interfaces. The water level and flow rate data in the hydrological data come from the hydrological database, which supports queries according to hydrological station number and time range and can automatically calculate flow rate averages based on request parameters. The coastal outfall monitoring data comes from the pollution source list database, which provides filtering and querying services according to river basin and outfall type. Through the above mapping, the corresponding data sources and data acquisition methods for each service requirement are determined.

[0019] Step S121: parsing each service requirement description in the set of service requirement descriptions to extract data requirement type and data call frequency information.

[0020] Each description in the set of service requirement descriptions is parsed. 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.

[0021] As for the data requirement type, "collecting data such as particulate matter concentration and gaseous pollutant concentration at each monitoring point" belongs to active data acquisition requirement, which specifies the source object and specific indicators of data; "calling weather data interface to obtain wind speed and direction data at regular intervals" belongs to periodic data acquisition requirement, which contains fixed time interval requirement; "determining monitoring point data validity in combination with terrain data" belongs to conditional data acquisition requirement, which needs to trigger terrain data acquisition when verifying the rationality of monitoring point location; "encrypting data collection frequency and giving priority to acquiring 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.

[0022] The extraction of data call frequency information needs to be combined with the business execution rules. The business adjusts the monitoring frequency at different time periods every day in the daily state, and the monitoring frequency is higher in peak hours such as morning and evening, and lower in the afternoon and at night. The average number of calls to the atmospheric monitoring database per unit time is counted. The weather data is called once an hour, so the call frequency to the weather database is determined. The terrain data is called infrequently, only when a new monitoring point is added or the monitoring range is adjusted, and the unit time frequency is calculated according to the historical average monthly call number. The encrypted call frequency during the pollution warning period is obtained according to the historical warning duration and the call number during the period. The business identification information "DQ-001" is associated with the extracted various data requirement types and corresponding call frequency information, and the basic requirement information table is formed.

[0023] Step S1211: traversing each business requirement description in the business requirement description set, identifying data-related expression content in each business requirement description sentence by sentence.

[0024] Traverse the business requirement description set and process each description sentence by sentence. Taking the water environment monitoring system "SJ-001" requirement as an example, its description content includes sentences such as "set monitoring period according to river basin partition, collect water quality parameters such as pH value, dissolved oxygen content, permanganate index, and heavy metal ion concentration at main stream, tributary, and reservoir section" "need to synchronize to acquire section water level and flow rate data to calculate pollutant flux" "adjust sampling frequency in real time according to rainfall during flood season" "and need to associate coastal outfall monitoring data for source tracing analysis" "need to update historical database when generating water quality status report every month" and the like.

[0025] The data-related expressions such as "collecting water quality parameters such as pH value and dissolved oxygen content", "synchronously acquiring cross-section water level and flow rate data", "adjusting sampling frequency according to rainfall", "associating with coastal sewage outlet monitoring data", and "updating historical database" are identified sentence by sentence, which are related to data collection, acquisition, association, and updating. These expressions are data-related expression contents and are extracted separately for subsequent semantic analysis. For the data-related contents in complex sentences, such as "calculating pollutant flux", which depends on water level and flow rate data, the data acquisition part and the data processing part need to be separated, and only the data-related expressions are extracted.

[0026] Step S1212: performing semantic analysis on the data-related expression contents, distinguishing the data acquisition demand expression, the data update demand expression, and the data sharing demand expression in the data-related expression contents, and determining the demand categories corresponding to the data acquisition demand expression, the data update demand expression, and the data sharing demand expression as data demand types.

[0027] The data-related expression contents of the water environment monitoring system "SJ-001" requirement are analyzed semantically. In the expression "collecting water quality parameters such as pH value and dissolved oxygen content", the "collection" action clearly points to obtaining raw data from monitoring equipment, which belongs to data acquisition demand expression. This data acquisition demand expression also contains specific indicators and collection objects, and is further divided into routine monitoring data acquisition demand.

[0028] In the expression "synchronously acquiring cross-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 associated data acquisition demand and emphasizes the timeliness matching of data acquisition. In the expression "associating with coastal sewage outlet monitoring data", the "association" action means obtaining related data from other data sources for joint analysis, which belongs to associated query data acquisition demand.

[0029] In the expression "updating historical database when generating water quality status report every month", "updating historical database" involves writing processed report data into a storage system, which belongs to data update demand expression. This data update demand expression clearly specifies the trigger condition and data object of the update. In the cross-system collaboration requirement, if there is an expression "pushing water quality exceeding standard information to the ecological governance dispatching system", it belongs to data sharing demand expression. However, such expressions are not involved in this business requirement. Through the above analysis, the demand categories corresponding to the data-related expression contents are determined as data demand types, including routine monitoring data acquisition, associated data acquisition, associated query data acquisition, data update, and other types.

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

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

[0032] The data call situation in each service execution process is counted. Each time the routine 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 call the pollution source list database to obtain the data of the sewage outlet. Therefore, the number of data calls each time the service is executed varies from watershed to watershed, and the average number of data calls each time the service is executed is taken as the average number of data calls each time the service is executed.

[0033] Based on the length of the historical preset time period (the total number of days is calculated based on the average number of days per month for half a year), the total number of service executions is divided by the total number of days to obtain the service execution frequency per unit time (per day). The service execution frequency per unit time is multiplied by the average number of data calls each time the service is executed to obtain the data call frequency per unit time, i.e. the data call frequency information. For the additional calls in special periods such as the 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.

[0034] Step S1214: Store the service 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.

[0035] 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 service 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 routine monitoring data acquisition, associated data acquisition, associated query data acquisition, and data update; and a data call frequency information column, which records the number of calls to the water quality monitoring database, the hydrological database, and the pollution source list database per unit time and the total number of calls.

[0036] 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 "Routine monitoring data acquisition - water quality parameters: pH value, dissolved oxygen content, source: water quality monitoring database, condition: dry stream section collected every Monday and Thursday". Through associated storage, it ensures that the business identification information corresponds to the data requirement type and data call frequency information, facilitating subsequent mapping processing and rule construction.

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

[0038] The basic requirement information table of all business requirement descriptions, such as atmospheric environment monitoring system, water environment monitoring system and cross-system collaboration requirements, is aggregated. During the aggregation process, the basic requirement information table is grouped according to business system categories, such as atmospheric environment monitoring category, water environment monitoring category and cross-system collaboration category.

[0039] The requirement information set is stored in a structured data format, containing 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.

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

[0041] The data source capability information is obtained through the metadata management module of the unified data foundation. The type identification of the atmospheric monitoring database is "DATA-ATMOS-001", the data storage format uses a time series database format, organizes data according to monitoring point ID, timestamp and pollutant code, and each record contains fields such as value, precision and status identification, and the data output method supports HTTP RESTful API query, MQTT real-time data stream push and batch CSV file export.

[0042] The type identification of the water quality monitoring database is "DATA-WATER-001", the data storage format uses a combination of relational database and file storage, structured data storage monitoring indicators values, unstructured data storage water sample spectrum, data output methods include SQL query interface, WebSocket real-time data push and time range compressed package download.

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

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

[0045] 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.

[0046] The "meteorological data acquisition" requirement type matches the type identification "DATA-METEO-001" of the meteorological database, and this data source explicitly supports the data output of wind speed, wind direction, temperature stratification and other meteorological elements, so it is included in the candidate data source list. For the "terrain data acquisition" requirement type, match to the type identification "DATA-TERRAIN-001" of the terrain database, 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.

[0047] Each data requirement type may correspond to multiple candidate data sources, for example, if there is a backup meteorological database with different type identification but the same data content, it will also be included in the candidate list. Through the above matching process, a candidate data source list containing all possible matching data sources is generated for each data requirement type.

[0048] Step S124: According to the data call frequency information in each business requirement description, filter the data sources in the candidate data source list whose data output response speed meets the data call frequency information, and obtain the target data source corresponding to each business requirement description.

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

[0050] The average value of the response duration of the meteorological database is calculated as its average response speed. The response speed requirement corresponding to the data calling frequency information is analyzed, and the maximum response duration allowed by the calling frequency of once per hour 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.

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

[0052] Step S1241: Extract the historical data output response records of each data source in the candidate data source list, which contain the response duration of each response data calling request of the data source.

[0053] The historical data output response records of the candidate data source are extracted through the performance monitoring module of the unified data pedestal. Taking the water quality monitoring database as an example, its historical response records are 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.

[0054] The difference between the response completion time and the response start time is extracted from these records to obtain the response duration of each response data calling request. For abnormal response records such as timeout non-response, response error, etc., they are marked separately but not included in the calculation of 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 the historical response duration sequence of the data source.

[0055] 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.

[0056] The historical response time sequence of the water quality monitoring database is calculated, and after the marked abnormal response records are removed, the total number and total time of the remaining valid response time are counted. The total time is divided by the number of valid response records to obtain the average response time of the data source, which is determined as the average response speed of the data source.

[0057] During the calculation process, if there is a large difference in response time in different time periods, such as slower response during peak hours and faster response during low hours, 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.

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

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

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

[0061] 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 service demand, and form a preliminary filtered data source list.

[0062] The average response time corresponding to the average response speed of the water quality monitoring database is compared with the maximum data output response time allowed by the SJ-001 demand of the water environment monitoring system. 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, and if the time does not exceed the maximum allowed response time of the SJ-001 demand, it is also added to the preliminary filtered data source list.

[0063] After the preliminary screening of the data source list, each data source in the list needs to be further checked. Taking the atmospheric environment monitoring system "DQ-001" requirement as an example, the atmospheric monitoring database and the meteorological database screened 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.

[0064] 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-mentioned fields, and whether the data types of the fields match the requirements, such as the monitoring time should be of date and time type, and the concentration value should be of numerical type. At the same time, it needs to be 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 the format requirements are met, the atmospheric monitoring database will be retained in the preliminary screening list.

[0065] 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 screening list.

[0066] For the preliminary screening 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 the format requirements can be retained in the preliminary screening list.

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

[0068] 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.

[0069] A mapping record is established for each business requirement description, including business identification information, detailed information of target data sources. For example, the mapping record of "DQ-001" requirement, the business identification information is "DQ-001", the type identification of target data sources is "atmospheric monitoring database-DQDB" and "weather database-QXDB", the data storage formats are "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 modes are "atmospheric monitoring database-real-time data stream interface" and "weather database-timed data push service (once an hour)".

[0070] In the mapping record of "SJ-001" requirement, the business identification information is "SJ-001", the type identification of target data sources is "water quality monitoring database-SJDB" and "hydrological database-SWDB", the data storage formats are "water quality monitoring database-structured data table (section number, sampling time, pH value, dissolved oxygen, pollutant concentration)" and "hydrological database-structured data table (section number, monitoring time, flow, water level)", and the data output modes are "water quality monitoring database-batch query interface (executed at dawn every day)" and "hydrological database-event triggered interface (pushed when flow changes)".

[0071] In the mapping record of "TR-001" requirement of soil environment monitoring system, the business identification information is "TR-001", the type identification of target data sources 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 mode is "periodic full amount synchronization interface (once a month)".

[0072] All the mapping records of business requirement descriptions are integrated together to form a 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.

[0073] Step S130: Based on the business requirement mapping result, an integrated execution rule of the multi-business system is constructed, which includes the data source calling sequence rule of each business system and the cross-system business data interaction timing rule.

[0074] According to the business requirement mapping result, the corresponding business requirements and target data sources of each business system are sorted out, and the calling sequence of data sources is determined. At the same time, the cross-system collaborative business requirements are analyzed, and the data interaction sequence of each system business execution link is clarified, so as to construct a complete integrated execution rule.

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

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

[0077] 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 business system are clearly presented.

[0078] Step S132: For each business system, according to the business execution priority of each business requirement description in the business system, the calling order of the target data source corresponding to each business requirement description is determined to form the data source calling order rule of the business system.

[0079] The business requirement descriptions in each business system are prioritized, and the calling order of the target data source 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".

[0080] Step S1321: Extract the business emergency degree expression and the business influence range expression in each business requirement description in each business system.

[0081] The relevant expressions are extracted from the business requirement descriptions. The "DQ-003" requirement description in the atmospheric environment monitoring system 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 emergency degree 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 influence range expression.

[0082] In the demand description of the water environment monitoring system "SJ-003" (monitoring of sudden water pollution events), "immediately start encrypted monitoring after a sudden leakage event occurs" is a business emergency level expression, and "the monitoring range includes all drinking water sources and sensitive ecological protection areas downstream of the incident point" is a business impact range expression.

[0083] Step S1322: Determine the emergency level of each business demand description according to the business emergency level expression, and determine the impact range level of each business demand description according to the business impact range expression.

[0084] The level is divided according to the strength of the business emergency level expression. The expressions "during heavy pollution weather warning", "high frequency", and "timely" in the "DQ-003" demand indicate that the emergency level is high, and are classified as the first level of emergency level; the "daily regular collection" expression in the "DQ-001" demand corresponds to the third level of emergency level.

[0085] The level is divided according to the coverage of the business impact range expression. The "DQ-003" demand has a wide coverage of "the entire urban area and surrounding key industrial areas", and the impact range level is classified as the first level; the "DQ-004" (local area monitoring) demand has a small coverage of "around an industrial park", and the impact range level is classified as the third level.

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

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

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

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

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

[0091] 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 rule also specifies the calling trigger conditions of each data source, such as "the emergency monitoring data source is automatically activated for priority calling after the heavy pollution weather warning signal is issued".

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

[0093] Identify the cross-system collaborative requirement from the set of business requirement descriptions. The "XT-001" requirement description involves the atmospheric environment monitoring system, the ecological management and dispatching system, and the environmental emergency response system, among which the business execution link of the atmospheric environment monitoring system is "excessive data collection and analysis", the link of the ecological management and dispatching system is "emission reduction scheme development", and the link of the environmental emergency response system is "early warning preparation and resource allocation".

[0094] Step S134: Determine the dependency relationship between the business execution links of each business system in the cross-system collaborative business requirement 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.

[0095] Analyze the dependency relationship between each link and determine the interaction sequence. In the "XT-001" requirement, the "emission reduction scheme development" of the ecological management and dispatching system depends on the result of the "excessive data collection and analysis" of the atmospheric environment monitoring system, and the "early warning preparation" of the environmental emergency response system depends on the result of the "scheme development" 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.

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

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

[0098] Step S1342: Analyze the input data source required by each business execution link, determine whether the input data is 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.

[0099] The "developing emission reduction scheme" link of the ecological management and scheduling system needs to input the atmospheric pollutant exceeding 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 emission reduction scheme content, 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.

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

[0101] In the dependency relationship graph of "XT-001" demand, 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.

[0102] Step S1344: According to the dependency relationship in the dependency relationship graph, the data interaction time interval of each business execution link is set to enable the dependent business execution link to obtain the data in time after the previous business execution link outputs the data.

[0103] According to the requirements of the business process, set the time interval. After A link outputs data, B link needs to obtain data and start scheme development within a specified time, set the data interaction time interval from A to B as a short time; after B link outputs the scheme, C link needs to obtain and start early warning preparation within a specified time, set the time interval from B to C as another time, to ensure efficient connection of the whole process.

[0104] Step S1345: Record the sequence, data interaction time interval and data interaction content description of each business execution link of the business system, and form the cross-system business data interaction time sequence rule.

[0105] The timing rule required by "XT-001" is 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 scheduling system-scheme formulation" 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 clearly describes the format and key fields of the data in each link, such as the analysis report which needs to include the types, concentrations and distribution areas of over-standard pollutants.

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

[0107] 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.

[0108] Step S140: The integrated execution rules are issued to the business processing modules of each business system, triggering 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 obtaining the business coordination execution result.

[0109] The integrated execution rules are issued 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 result.

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

[0111] An encrypted communication link is built 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, and the backup link uses wireless communication to ensure communication stability. Identity authentication and encryption negotiation are completed during link establishment to ensure data transmission security.

[0112] Step S142: The data source calling sequence rules and 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.

[0113] The data source calling sequence rule of the atmospheric environment monitoring system is sent to the business processing module thereof through the established communication link, the rule is transmitted in the form of a structured data packet, and a check code is included 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 scheduling system and the environmental emergency response system, and each system only receives the rule part related to itself.

[0114] Step S143: After the business processing module of each business system receives the data source calling sequence rule, the business processing module 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.

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

[0116] 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 business identification information corresponding to each target data source in the rule.

[0117] 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 business identification information corresponding to each data source as "DQ-003", "DQ-002" and "DQ-001".

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

[0119] According to the arrangement sequence, the emergency monitoring data source needs to be called first, and the business processing module generates a data calling request including 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 one hour".

[0120] 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 calling request is directly sent; if the communication state is abnormal, a backup communication path is started, and the data calling request is sent through the backup communication path.

[0121] 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 a 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 different network interfaces and transmission protocols, and the request is re-sent through the backup path.

[0122] Step S1434: After sending the data call request, the business processing module of each business system waits for the data source of the unified data base to return response information. If the response information is received within a predetermined waiting time, subsequent business processing is performed. If the response information is not received within the predetermined waiting time, the data call request is re-sent.

[0123] Timing starts after the request is sent. If PM2.5 concentration data returned by the emergency monitoring data source is received within a predetermined waiting time, data verification and analysis are performed. If no response is received within the time period, 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 switched to the next sequential data source.

[0124] Step S1435: After sending the call request of all target data sources in the order of the target data source arrangement, 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.

[0125] For example, after the environmental emergency response system "YJ-001" completes the call of the emergency monitoring data source, the meteorological data source, and the geographic information data source, it 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; 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.

[0126] 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 simultaneously uploaded to the log management module of the unified data base for centralized archiving.

[0127] Step S150: According to the business coordination execution result, an integrated management instruction of multiple business systems is generated, and the integrated management instruction is sent to the management module of the unified data base and the business processing module of each business system to perform integrated optimization operation. The integrated management instruction includes business processing parameter adjustment instruction and data source allocation optimization instruction.

[0128] In the regional ecological environment monitoring and management integrated platform, the business collaboration execution result includes the independent business processing result of each business system and the cross-system collaborative 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 collaborative business and the warning preparation state of the environmental emergency response system.

[0129] Based on these results, the problems existing in the business processing process are analyzed, and the corresponding integrated management instructions are 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 distribution optimization instruction is generated, and then these instructions are sent to the corresponding module to perform optimization operation.

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

[0131] When analyzing the business collaboration execution result, the business processing time and the business processing accuracy are extracted from the result data for each business system. 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.

[0132] For the cross-system collaborative 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, environmental emergency response system warning preparation time) and the completion rate of the whole collaborative 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 collaboration) are extracted.

[0133] Step S152: Determine whether the business processing module of the corresponding business system exists processing delay according to the business processing time, 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.

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

[0135] The to-be-adjusted parameter name can include a data processing thread number, a data cache size, an algorithm iteration number, and the like. The adjustment direction is determined according to the delay cause. If the delay is caused by insufficient data processing threads, the adjustment direction is to increase the thread number. If the delay is caused by insufficient cache, the adjustment direction is to increase the cache size. The generated business processing parameter adjustment instruction explicitly marks these contents.

[0136] Step S153: Analyzing the calling times and data output of each data source in the business cooperative execution result, identifying the data source with excessive calling times causing response delay, determining the need to optimize the allocation mode of the data source, and generating a data source allocation optimization instruction containing data source allocation proportion adjustment and standby data source enabling suggestion.

[0137] The calling times of each data source in the business cooperative execution process are counted, and the response time length change of data output is combined to identify the data source with frequent calling and response delay. For example, the calling times of the atmospheric monitoring database increase sharply during the high pollution period, causing the response speed to decrease.

[0138] For such data sources, the allocation proportion of the data sources among the business systems is adjusted to reduce the calling quota of non-critical business; at the same time, it is suggested to enable a standby atmospheric monitoring database to share the pressure of the main data source. The data source allocation optimization instruction specifies the adjusted allocation proportion value and the enabling condition of the standby data source (such as automatically enabling when the main data source response delay exceeds a certain time length).

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

[0140] When integrating the instructions, they are classified and arranged according to the instruction type and execution object. The effective time is added to each instruction, such as the business processing parameter adjustment instruction can be set to take effect during the non-peak period of the business on the same day, and the data source allocation optimization instruction can take effect immediately.

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

[0142] 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.

[0143] The instruction transmission channel is established through an encrypted communication protocol to ensure the security and integrity of 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.

[0144] 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.

[0145] 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, a processor 120 can be used in the multi-business system integration management system 100 based on a unified data base and used to perform the functions in the present application.

[0146] The multi-business system integration management system 100 based on a unified data base can be a general-purpose 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.

[0147] For example, the multi-business system integration management system 100 based on a unified data base 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. Exemplarily, the multi-business system integration management system 100 based on a unified data base can also include program instructions stored in a ROM, a RAM, or other types of non-transitory storage media, or any combination thereof. The method of the present application can be implemented according to these program instructions. The multi-business system integration management system 100 based on a unified data base also includes an I / O interface 150 between the computer and other input / output devices.

[0148] For the convenience of description, only one processor is described in the multi-service system integration management system based on unified data base 100. However, it should be noted that the multi-service system integration management system based on unified data base 100 in the present application can also include multiple processors, and thus 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 multi-service system integration management system based on unified data base 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.

[0149] In addition, the embodiment of the present application further provides a readable storage medium, wherein computer executable instructions are preset in the readable storage medium, and when a processor executes the computer executable instructions, the multi-service system integration management method based on unified data base is realized.

[0150] It should be noted that, in order to simplify the description of the present application and to help the understanding of 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 multi-business system integrated management method based on a unified data base, characterized in that: The method comprises: Obtain a set of business requirement descriptions for multiple business systems, wherein the set of business requirement descriptions includes a description of daily business processing requirements and a description of cross-system collaborative business requirements for each business system, and each business requirement description corresponds to unique business identification information; Mapping the business requirement description set with the data source capability information of the unified data base, matching the data requirement content in each business requirement description with the corresponding data source type and data provision method in the unified data base, to obtain a business requirement mapping result; Building integration execution rules for multiple business systems based on the business requirements mapping results, wherein the integration execution rules include data source call sequence rules for each business system and cross-system business data interaction timing rules; The integrated execution rules are issued to the business processing modules of each business system, triggering the business processing modules of each business system to call the data source of the unified data base to perform business processing according to the integrated execution rules, and obtain the business collaborative execution results; Based on the business collaborative execution results, integrated management instructions for multiple business systems are generated, and the integrated management instructions are sent to the management module of the unified data base and the business processing modules of each business system to perform integrated optimization operations. The integrated management instructions include business processing parameter adjustment instructions and data source allocation optimization instructions.

2. The multi-business system integrated management method based on a unified data base according to claim 1, characterized in that: The business requirement description set is mapped with the data source capability information of the unified data base, and the data requirement content in each business requirement description is matched with the corresponding data source type and data provision method in the unified data base to obtain a business requirement mapping result, including: Parsing each business requirement description in the business requirement description set, and extracting data requirement type and data call frequency information in each business requirement description; Acquire data source capability information of the unified data base, wherein the data source capability information includes the type identifier, data storage format, and data output method of each data source in the unified data base; Match the data requirement type in each business requirement description with the type identifier of the data source of the unified data base to determine the candidate data source list corresponding to each data requirement type; According to the data call frequency information in each business requirement description, filter the data sources in the candidate data source list whose data output response speed matches the data call frequency information to obtain the target data source corresponding to each business requirement description; Record the business identification information, target data source type identification, data storage format and data output method corresponding to each business requirement description, and integrate them to form the business requirement mapping results.

3. The multi-business system integrated management method based on a unified data base according to claim 2, characterized in that: The step of parsing each business requirement description in the business requirement description set and extracting data requirement type and data call frequency information in each business requirement description includes: Traversing each business requirement description in the business requirement description set, and identifying data-related description content in each business requirement description sentence by sentence; Performing semantic analysis on the data-related expression content, distinguishing data acquisition requirement expressions, data update requirement expressions, and data sharing requirement expressions in the data-related expression content, and determining the requirement categories corresponding to the data acquisition requirement expressions, data update requirement expressions, and data sharing requirement expressions as data requirement types; Counting the number of business executions of the corresponding business in each business requirement description within a historical preset time period, and counting the number of data calls during each business execution within the historical preset time period; calculating the business execution frequency per unit time based on the length of the historical preset time period, and then combining the number of data calls during each business execution to determine the number of data calls per unit time corresponding to the business requirement description, and determining the number of data calls per unit time 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 the data call frequency information to form a basic requirement information table for each business requirement description; Summarize the basic requirement information tables of all business requirement descriptions to obtain a requirement information set including the business identification information, data requirement type and data call frequency information of each business requirement description.

4. The multi-business system integrated management method based on a unified data base according to claim 2, characterized in that: The method of screening the data source in the candidate data source list according to the data call frequency information in each business requirement description, wherein the data source whose data output response speed meets the data call frequency information, and obtaining the target data source corresponding to each business requirement description, includes: Extracting a historical data output response record of each data source in the candidate data source list, wherein the historical data output response record includes a response time of each response of the data source to a data call request; Calculate the average response time in the historical data output response records of each data source, and determine the average response speed of the data source as the average response speed; Analyze the response speed requirements corresponding to the data call frequency information in each business requirement description, and determine the maximum data output response time allowed by the business requirement based on the number of data calls per unit time; Filter out data sources whose average response speed corresponds to a response time that is less than or equal to the maximum data output response time allowed by the business requirement in the candidate data source list to form a preliminary screened data source list; Check whether the data storage format of each data source in the preliminary screened data source list is consistent with the data format requirements in the business requirement description, retain the data sources with consistent data storage formats, and determine the retained data sources as the target data source corresponding to the business requirement description.

5. The multi-service system integration management method based on a unified data base according to claim 1, characterized in that: The construction of the integrated execution rules of the multi-business system based on the business requirements mapping result includes: According to the business requirement mapping result, all business requirement descriptions corresponding to each business system and the target data source corresponding to each business requirement description are obtained by classifying according to the business identification information; For each business system, determine the order of calling the target data sources corresponding to each business requirement description based on the business execution priority of each business requirement description within the business system, and form the data source calling sequence rule for the business system; Identify the cross-system collaborative business requirement description in the business requirement description set, and extract all business systems and business execution links of each business system involved in the cross-system collaborative business requirement description; Determine the dependencies between the business execution links of each business system in the cross-system collaborative business requirements description, set the data interaction sequence of the business execution links of each business system based on the dependencies, and form the cross-system business data interaction timing rules; Integrate the data source call sequence rules of all business systems and all cross-system business data interaction timing rules to form integrated execution rules for multiple business systems.

6. The multi-business system integrated management method based on a unified data base according to claim 5, characterized in that: For each business system, the order of calling target data sources corresponding to each business requirement description is determined according to the business execution priority of each business requirement description in the business system, thereby forming a data source calling sequence rule for the business system, including: Extract the business urgency and business impact scope from the business requirement descriptions within each business system; Determine the urgency level of each business requirement description based on the business urgency statement, and determine the impact level of each business requirement description based on the business impact statement; Determine the service execution priority of each service requirement description based on the urgency level and the scope of impact level. The higher the urgency level and the wider the scope of impact, the higher the service execution priority of the service requirement description; Arrange the target data sources corresponding to each business requirement description in the business system in descending order of business execution priority; The order of calling the arranged target data sources and the business identification information of the business requirement description corresponding to each target data source are recorded to form the data source calling sequence rules of the business system.

7. The multi-service system integration management method based on a unified data base according to claim 5, characterized in that: Determining the dependency relationships between the business execution links of each business system in the cross-system collaborative business requirement description, setting the data interaction sequence of the business execution links of each business system according to the dependency relationships, and forming a cross-system business data interaction timing rule includes: Analyze the cross-system collaborative business requirement description, determine the complete business process corresponding to the cross-system collaborative business requirement description, and split the complete business process into multiple consecutive business execution links, each of which corresponds to a business system; Analyze the source of input data required for each business execution link to determine whether the input data comes from the output data of the business execution link of other business systems. If so, determine that the business execution link is dependent on the business execution link that provides the input data; Construct a dependency graph of the business execution links based on the dependency relationships, where each node in the dependency graph represents a business execution link, and the lines between the nodes represent the dependency relationships, with the direction of the lines being from the business execution link that provides the data to the business execution link that depends on the data; According to the order of dependency of the business execution links in the dependency diagram, set the data exchange time interval of each business execution link so that after the previous business execution link outputs data, the next dependent business execution link can obtain the data in time; Record the sequence of business execution links, data interaction time intervals and data interaction content descriptions of each business system to form cross-system business data interaction timing rules.

8. The multi-service system integration management method based on a unified data base according to claim 1, characterized in that: The integrated execution rules are sent to the business processing modules of each business system, triggering the business processing modules of each business system to call the data source of the unified data base to perform business processing according to the integrated execution rules, and obtaining the business collaborative execution results, including: Establish a communication link between the management module of the unified data base and the business processing modules of each business system; Sending the data source call sequence rule and the cross-system business data interaction timing rule in the integration execution rule to the business processing module of the corresponding business system through the communication link; After receiving the data source call sequence rule, the business processing module of each business system sends a data call request to the data source of the unified data base according to the call sequence in the data source call sequence rule; After receiving the data call request, the data source of the unified data base returns the required data to the business processing module of the corresponding business system according to the data provision method, and the business processing module of each business system uses the returned data to perform business processing operations; When cross-system business data interaction is involved, the business processing modules of each business system 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 summarize the business processing results of all business systems to form a business collaborative execution result; After receiving the data source call sequence rule, the business processing module of each business system sends a data call request to the data source of the unified data base according to the call sequence in the data source call sequence rule, including: The business processing module of each business system parses the received data source call sequence rule, extracts the target data source arrangement sequence in the rule and the business identification information corresponding to each target data source; The business processing module of each business system determines the target data source that needs to be called according to the order of the target data sources, and generates a data call request containing the type identification of the target data source and the corresponding business identification information; The business processing module of each business system checks the communication status between itself and the current target data source. If the communication status is normal, the data call request is directly sent; if the communication status is abnormal, the backup communication path is activated and the data call request is sent through the backup communication path. After sending the data call request, the business processing module of each business system waits for the data source of the unified data base to return a response message. If the response message is received within the preset waiting time, the subsequent business processing is performed; if the response message is not received within the preset waiting time, the data call request is resent; After completing the sending of call requests to all target data sources in the order in which the target data sources are arranged, the business processing module of each business system records the sending time and response receiving time of each call request to form call log information.

9. The multi-business system integrated management method based on a unified data base according to claim 1, characterized in that: Generating an integrated management instruction for multiple business systems according to the business collaborative execution result, and sending the integrated management instruction to the management module of the unified data base and the business processing modules of each business system to perform integrated optimization operations, includes: Analyze the business collaborative execution results, extract the business processing completion status information of each business system and the cross-system collaborative business processing completion status information, wherein the business processing completion status information includes the business processing time and the business processing accuracy rate; Determine whether there is a processing delay in the business processing module of the corresponding business system based on the business processing time; if the business processing time exceeds a preset time threshold, determine that a processing parameter of the business processing module of the business system needs to be adjusted, and generate a business processing parameter adjustment instruction including the name of the parameter to be adjusted and the adjustment direction; Analyze the number of calls and data output of each data source in the business collaborative execution results, identify the data source that has been called too many times and caused response delays, determine that the allocation method of the data source needs to be optimized, and generate a data source allocation optimization instruction including a data source allocation ratio adjustment and a backup data source activation suggestion; Integrate the business processing parameter adjustment instruction and the data source allocation optimization instruction into an integrated management instruction for a multi-business system, and add an instruction effective time and an instruction execution object identifier to each integrated management instruction; Establish an instruction transmission channel with the management module of the unified data base and the business processing modules of each business system, and send the corresponding integrated management instructions to the management module of the unified data base and the business processing modules of each business system according to the instruction execution object identifier, triggering the management module of the unified data base to adjust the data source allocation method, triggering the business processing modules of each business system to adjust the business processing parameters, and performing integrated optimization operations.

10. A multi-business system integrated management system based on a unified data base, characterized in that: It includes a processor and a memory, the memory is connected to the processor, the memory is used to store programs, instructions or codes, and the processor is used to execute the programs, instructions or codes in the memory to implement the multi-business system integration management method based on a unified data base as described in any one of claims 1 to 9.

Images