CN117271147A - Data synchronous processing method and device - Google Patents
Data synchronous processing method and device Download PDFInfo
- Publication number
- CN117271147A CN117271147A CN202311240213.7A CN202311240213A CN117271147A CN 117271147 A CN117271147 A CN 117271147A CN 202311240213 A CN202311240213 A CN 202311240213A CN 117271147 A CN117271147 A CN 117271147A
- Authority
- CN
- China
- Prior art keywords
- data
- interface
- cloud resource
- system interface
- upstream
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 230000001360 synchronised effect Effects 0.000 title claims abstract description 57
- 238000003672 processing method Methods 0.000 title abstract description 19
- 238000011144 upstream manufacturing Methods 0.000 claims abstract description 204
- 238000006243 chemical reaction Methods 0.000 claims abstract description 115
- 238000000034 method Methods 0.000 claims abstract description 102
- 238000012545 processing Methods 0.000 claims abstract description 47
- 230000008569 process Effects 0.000 claims description 46
- 230000004044 response Effects 0.000 claims description 30
- 238000004458 analytical method Methods 0.000 claims description 26
- 238000013507 mapping Methods 0.000 claims description 26
- 238000004590 computer program Methods 0.000 claims description 16
- 238000012795 verification Methods 0.000 claims description 13
- 210000001503 joint Anatomy 0.000 claims description 7
- 238000012216 screening Methods 0.000 claims description 6
- 238000007726 management method Methods 0.000 description 30
- 238000013523 data management Methods 0.000 description 18
- 238000010586 diagram Methods 0.000 description 12
- 238000012423 maintenance Methods 0.000 description 12
- 238000004891 communication Methods 0.000 description 10
- 230000006870 function Effects 0.000 description 10
- 238000005192 partition Methods 0.000 description 10
- 230000003416 augmentation Effects 0.000 description 6
- 238000004140 cleaning Methods 0.000 description 5
- 238000013499 data model Methods 0.000 description 5
- 238000013461 design Methods 0.000 description 5
- 238000011161 development Methods 0.000 description 5
- 238000003032 molecular docking Methods 0.000 description 5
- 230000003287 optical effect Effects 0.000 description 4
- 230000009471 action Effects 0.000 description 3
- 230000006978 adaptation Effects 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 230000008901 benefit Effects 0.000 description 2
- 238000000605 extraction Methods 0.000 description 2
- 239000000835 fiber Substances 0.000 description 2
- 230000006872 improvement Effects 0.000 description 2
- 230000010354 integration Effects 0.000 description 2
- 230000008520 organization Effects 0.000 description 2
- 230000000644 propagated effect Effects 0.000 description 2
- 239000004065 semiconductor Substances 0.000 description 2
- 230000001960 triggered effect Effects 0.000 description 2
- 230000003044 adaptive effect Effects 0.000 description 1
- 230000004888 barrier function Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 238000013480 data collection Methods 0.000 description 1
- 238000012217 deletion Methods 0.000 description 1
- 230000037430 deletion Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 230000007774 longterm Effects 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 239000000203 mixture Substances 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 238000012805 post-processing Methods 0.000 description 1
- 238000007781 pre-processing Methods 0.000 description 1
- 238000004153 renaturation Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
- 230000007704 transition Effects 0.000 description 1
- 238000013024 troubleshooting Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/52—Program synchronisation; Mutual exclusion, e.g. by means of semaphores
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/602—Providing cryptographic facilities or services
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
- G06F21/6209—Protecting access to data via a platform, e.g. using keys or access control rules to a single file or object, e.g. in a secure envelope, encrypted and accessed using a key, or with access control rules appended to the object itself
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2221/00—Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/21—Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/2107—File encryption
Abstract
The invention discloses a data synchronous processing method and device, and relates to the technical field of data processing. One embodiment of the method comprises the following steps: receiving a data synchronization instruction, and calling an upstream system interface through a data access interface to acquire cloud resource data from the upstream system interface; determining a downstream system interface, inquiring a data conversion rule set corresponding to the upstream data interface and the downstream data interface, and processing cloud resource data by using the data conversion rule set to obtain cloud resource intermediate data; and inputting the cloud resource intermediate data into the association relation between the configuration item and the sub item corresponding to the downstream system interface through the data synchronization interface to obtain cloud resource data to be synchronized, and pushing the cloud resource data to be synchronized to the downstream system interface by using a pushing mode corresponding to the downstream system interface. The embodiment analyzes the interface information of the upstream and downstream systems to split and extract a set of general business rules, converts upstream data into downstream required data and pushes the downstream required data to the downstream systems.
Description
Technical Field
The present invention relates to the field of data processing technologies, and in particular, to a method and an apparatus for data synchronous processing.
Background
The operation and maintenance system of the large-scale enterprise at present is more and more applied and more complicated in system components along with the expansion of the business field of the enterprise. The enterprise is huge, the IT system and the infrastructure are not generating data at any time, the data are various, the association between the data is complex, the data volume is large, and a very large barrier is caused for realizing the integration and data intercommunication of the business system. The maintenance and the communication of basic data among the cross systems are involved, and the service requirements among the systems are difficult to meet.
The existing popular data conversion, data cleaning tools or platforms in the market are all configured and executed in advance according to fixed rules based on the rules. However, in the conventional rule configuration and flow arrangement method, in the complex operation and maintenance system scheme configuration process, because the rule model is relatively single, the flow arrangement is complicated, the complexity of operation and maintenance system operation and maintenance data of a large enterprise cannot be met, and special service scenes of access, conversion and pushing of a large amount of operation and maintenance basic data configuration cannot be met.
Disclosure of Invention
In view of this, embodiments of the present invention provide a method and an apparatus for processing data synchronously, which at least can solve the problems in the prior art that data synchronization is complex and batch processing cannot be satisfied.
To achieve the above object, according to an aspect of an embodiment of the present invention, there is provided a data synchronization processing method, including: receiving a data synchronization instruction, and calling an upstream system interface through a data access interface to acquire cloud resource data from the upstream system interface; determining a downstream system interface, inquiring a data conversion rule set corresponding to the upstream data interface and the downstream data interface, and processing cloud resource data by using the data conversion rule set to obtain cloud resource intermediate data; and inputting the cloud resource intermediate data into the association relation between the configuration item and the sub item corresponding to the downstream system interface through the data synchronization interface to obtain cloud resource data to be synchronized, and pushing the cloud resource data to be synchronized to the downstream system interface by using a pushing mode corresponding to the downstream system interface.
Optionally, before the calling of the upstream system interface through the data access interface, the method further comprises: receiving configuration operation of first interface information of the data access interface; the first interface of the butt joint is an interface of an upstream system, and the first interface information comprises a first interface URL, an access mode and a request parameter; the calling the upstream system interface through the data access interface comprises the following steps: determining an access mode of an upstream system interface through a data access interface, accessing a first interface URL by using a request mode corresponding to the access mode to transmit request parameters to the upstream system interface, and then receiving cloud resource data returned by the upstream system interface.
Optionally, the first interface information further includes a first signature encryption rule; the determining the access mode of the upstream system interface through the data access interface, accessing the first interface URL by using the request mode corresponding to the access mode to transmit the request parameter to the upstream system interface, and then receiving cloud resource data returned by the upstream system interface, including: invoking a first signature encryption rule to process the request parameter through the data access interface to generate an encryption request parameter; determining an access mode of an upstream system interface, accessing a first interface URL of the upstream system interface by using a request mode corresponding to the access mode, and transmitting an encryption request parameter to the upstream system interface; and the upstream system interface performs verification processing on the signature in the encrypted request parameter, and returns cloud resource data corresponding to the request parameter when the verification result is passed.
Optionally, the first interface information further includes a data return format, and after the cloud resource data is acquired from the upstream system interface, the method further includes: determining a data return format of an upstream system interface, and analyzing the cloud resource data by using an analysis rule corresponding to the data return format to obtain analyzed cloud resource data.
Optionally, before the calling of the upstream system interface through the data access interface, the method further comprises: receiving configuration operation of local storage information of a data access interface; the local storage information comprises analysis rules corresponding to each data return format, field information accessed from an upstream system interface and a data table set; after the parsing cloud resource data is obtained, the method further comprises: determining field information corresponding to an upstream system interface, and screening target cloud resource data corresponding to the field information from the analysis cloud resource data; and storing the target cloud resource data into the data table in response to a selection operation of the data table.
Optionally, the processing cloud resource data using the data conversion rule set includes: determining a data conversion rule corresponding to each field information from the data conversion rule set, and processing the target cloud resource data of each field information by using the data conversion rule; the data conversion rule set comprises one or more of a field expansion rule and a multi-data source merging rule, and the field expansion rule comprises one or more of a field condition judging rule, a field splicing rule and a field dictionary conversion rule.
Optionally, before the cloud resource intermediate data is input into the association relationship between the configuration item and the sub item corresponding to the downstream system interface, the method further includes: receiving configuration operation of second interface information of the data synchronization interface; the second interface is an interface of a downstream system, and the second interface information comprises a configuration data source, a pushing mode, a pushing field, a configuration item and a sub item association relation; inputting the cloud resource intermediate data into the association relationship between the configuration item and the sub item corresponding to the downstream system interface to obtain cloud resource data to be synchronized, including: and extracting data corresponding to the push field from the cloud resource intermediate data, and inputting the extracted data into the association relation between the configuration item and the sub item to obtain the cloud resource data to be synchronized.
Optionally, the interface information further includes a second interface URL and a second signature encryption rule, and the pushing the cloud resource data to be synchronized to the downstream system interface by using a pushing manner corresponding to the downstream system interface includes: processing cloud resource data to be synchronized by using a second signature encryption rule to obtain encrypted cloud resource data; accessing a second interface URL, and pushing the encrypted cloud resource data to a downstream system interface by using a pushing mode; the downstream data interface checks the signature pair in the encrypted cloud resource data, and displays the cloud resource data to be synchronized when the checking result is passed; or generating an encrypted file based on the encrypted cloud resource data in a file generation mode, and storing the encrypted file under a preset catalog, so that a downstream system interface pulls the encrypted file from the preset catalog; the name of the encrypted file is generated based on the configuration item code of the downstream system interface.
Optionally, the method further comprises: responding to clicking execution operation of the data synchronization flow, and executing the data synchronization flow; or receiving a timing task configured for the data synchronization flow, and executing the data synchronization flow in response to the execution time point of the timing task; the data synchronization process comprises a data access node, a data conversion node and a data synchronization node, wherein the data access node comprises one or more data access steps, the data conversion node comprises one or more data conversion steps, and the data synchronization node comprises a data synchronization step.
Optionally, the method further comprises: receiving upstream tenant information transmitted by an upstream system interface and receiving downstream tenant information transmitted by a downstream system interface; receiving configuration operation of a mapping relation between upstream tenant information and downstream tenant information; and in response to receiving the data of the upstream tenant, determining a downstream tenant having a mapping relationship with the upstream tenant, so as to push the data to the downstream tenant.
Optionally, the method further comprises: creating a plurality of data tables according to the table creating rules and the general fields; the cleansing operation for the data in the data table is performed in response to reaching the cleansing time point, or in response to a selection operation for cleansing data of the data table.
Optionally, after the pushing the target cloud resource data to the downstream system interface, the method further includes: after receiving the execution completion information, the intermediate process data is obtained and displayed in response to the checking operation of the intermediate process data of the data synchronization flow.
To achieve the above object, according to another aspect of the embodiments of the present invention, there is provided a data synchronization processing apparatus including: the data access module is used for receiving the data synchronization instruction, and calling an upstream system interface through the data access interface so as to acquire cloud resource data from the upstream system interface; the data conversion module is used for determining a downstream system interface, inquiring a data conversion rule set corresponding to the upstream data interface and the downstream data interface, and processing cloud resource data by using the data conversion rule set to obtain cloud resource intermediate data; the data synchronization module is used for inputting the cloud resource intermediate data into the association relation between the configuration item and the sub item corresponding to the downstream system interface through the data synchronization interface to obtain cloud resource data to be synchronized, and pushing the cloud resource data to be synchronized to the downstream system interface by using a pushing mode corresponding to the downstream system interface.
Optionally, the data access module is configured to: receiving configuration operation of first interface information of the data access interface; the first interface of the butt joint is an interface of an upstream system, and the first interface information comprises a first interface URL, an access mode and a request parameter; and determining an access mode of the upstream system interface through the data access interface, accessing the first interface URL by using a request mode corresponding to the access mode to transmit the request parameters to the upstream system interface, and then receiving cloud resource data returned by the upstream system interface.
Optionally, the first interface information further includes a first signature encryption rule; the data access module is used for: invoking a first signature encryption rule to process the request parameter through the data access interface to generate an encryption request parameter; determining an access mode of an upstream system interface, accessing a first interface URL of the upstream system interface by using a request mode corresponding to the access mode, and transmitting an encryption request parameter to the upstream system interface; and the upstream system interface performs verification processing on the signature in the encrypted request parameter, and returns cloud resource data corresponding to the request parameter when the verification result is passed.
Optionally, the first interface information further includes a data return format, and the data access module is further configured to: determining a data return format of an upstream system interface, and analyzing the cloud resource data by using an analysis rule corresponding to the data return format to obtain analyzed cloud resource data.
Optionally, the data access module is configured to: receiving configuration operation of local storage information of a data access interface; the local storage information comprises analysis rules corresponding to each data return format, field information accessed from an upstream system interface and a data table set; the data conversion module is further configured to: determining field information corresponding to an upstream system interface, and screening target cloud resource data corresponding to the field information from the analysis cloud resource data; and storing the target cloud resource data into the data table in response to a selection operation of the data table.
Optionally, the data conversion module is configured to: determining a data conversion rule corresponding to each field information from the data conversion rule set, and processing the target cloud resource data of each field information by using the data conversion rule; the data conversion rule set comprises one or more of a field expansion rule and a multi-data source merging rule, and the field expansion rule comprises one or more of a field condition judging rule, a field splicing rule and a field dictionary conversion rule.
Optionally, the data synchronization module is further configured to: receiving configuration operation of second interface information of the data synchronization interface; the second interface is an interface of a downstream system, and the second interface information comprises a configuration data source, a pushing mode, a pushing field, a configuration item and a sub item association relation; and extracting data corresponding to the push field from the cloud resource intermediate data, and inputting the extracted data into the association relation between the configuration item and the sub item to obtain the cloud resource data to be synchronized.
Optionally, the interface information further includes a second interface URL and a second signature encryption rule, and the data synchronization module is configured to: processing cloud resource data to be synchronized by using a second signature encryption rule to obtain encrypted cloud resource data; accessing a second interface URL, and pushing the encrypted cloud resource data to a downstream system interface by using a pushing mode; the downstream data interface checks the signature pair in the encrypted cloud resource data, and displays the cloud resource data to be synchronized when the checking result is passed; or generating an encrypted file based on the encrypted cloud resource data in a file generation mode, and storing the encrypted file under a preset catalog, so that a downstream system interface pulls the encrypted file from the preset catalog; the name of the encrypted file is generated based on the configuration item code of the downstream system interface.
Optionally, the apparatus further includes a task management module, configured to: responding to clicking execution operation of the data synchronization flow, and executing the data synchronization flow; or receiving a timing task configured for the data synchronization flow, and executing the data synchronization flow in response to the execution time point of the timing task; the data synchronization process comprises a data access node, a data conversion node and a data synchronization node, wherein the data access node comprises one or more data access steps, the data conversion node comprises one or more data conversion steps, and the data synchronization node comprises a data synchronization step.
Optionally, the apparatus further includes a tenant management module, configured to: receiving upstream tenant information transmitted by an upstream system interface and receiving downstream tenant information transmitted by a downstream system interface; receiving configuration operation of a mapping relation between upstream tenant information and downstream tenant information; and in response to receiving the data of the upstream tenant, determining a downstream tenant having a mapping relationship with the upstream tenant, so as to push the data to the downstream tenant.
Optionally, the apparatus further includes a data table management module, configured to: creating a plurality of data tables according to the table creating rules and the general fields; the cleansing operation for the data in the data table is performed in response to reaching the cleansing time point, or in response to a selection operation for cleansing data of the data table.
Optionally, the apparatus further includes a data management module configured to: after receiving the execution completion information, the intermediate process data is obtained and displayed in response to the checking operation of the intermediate process data of the data synchronization flow.
To achieve the above object, according to still another aspect of the embodiments of the present invention, there is provided a data synchronization processing electronic device.
The electronic equipment of the embodiment of the invention comprises: one or more processors; and the storage device is used for storing one or more programs, and when the one or more programs are executed by the one or more processors, the one or more processors are enabled to realize the data synchronization processing method.
To achieve the above object, according to still another aspect of the embodiments of the present invention, there is provided a computer-readable medium having stored thereon a computer program which, when executed by a processor, implements any one of the above-described data synchronization processing methods.
To achieve the above object, according to still another aspect of an embodiment of the present invention, there is provided a computer program product. The computer program product of the embodiment of the invention comprises a computer program, and the program is executed by a processor to realize the data synchronization processing method provided by the embodiment of the invention.
According to the solution provided by the present invention, one embodiment of the above invention has the following advantages or beneficial effects: based on the theoretical basis of data management, upstream and downstream system data are synchronously subdivided into each step of data management, the general rules suitable for the process are split, so that a general idea of data access, conversion, pushing and timing scheduling of a complex scene is generated, the data access can shield the differences of different upstream system interfaces, data conversion can realize batch data integration, mapping conversion and the like, the data processing universality is realized, finally configuration item and sub item relation data are calculated and generated, and data pushing is completed by a pushing mode of the adaptive downstream system interfaces, so that batch data management is realized. Meanwhile, in order to improve flexibility of service expansion, rules of each process can be extracted to a front-end page for configuration, and the method has configuration data processing universality.
Further effects of the above-described non-conventional alternatives are described below in connection with the embodiments.
Drawings
The drawings are included to provide a better understanding of the invention and are not to be construed as unduly limiting the invention. Wherein:
FIG. 1 is a schematic flow chart of a data synchronization processing method according to an embodiment of the invention;
FIG. 2 is a flow chart of an alternative data synchronization processing method according to an embodiment of the invention;
FIG. 3 is a flow chart of another alternative data synchronization processing method according to an embodiment of the invention;
FIG. 4 is a flow chart of yet another alternative data synchronization processing method according to an embodiment of the present invention;
FIG. 5 is a flow chart of yet another alternative data synchronization processing method according to an embodiment of the present invention;
FIG. 6 is a schematic diagram of main modules of a data synchronization processing apparatus according to an embodiment of the present invention;
FIG. 7 (a) is a schematic diagram of a data synchronization process according to an embodiment of the present invention;
FIG. 7 (b) is a schematic diagram of the architecture of data access, conversion, synchronization;
FIG. 8 is an exemplary system architecture diagram in which embodiments of the present invention may be applied;
fig. 9 is a schematic diagram of a computer system suitable for use in implementing a mobile device or server of an embodiment of the invention.
Detailed Description
Exemplary embodiments of the present invention will now be described with reference to the accompanying drawings, in which various details of the embodiments of the present invention are included to facilitate understanding, and are to be considered merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the invention. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.
It is noted that embodiments of the invention and features of the embodiments may be combined with each other without conflict. In the technical scheme of the invention, the related aspects of acquisition, analysis, use, transmission, storage and the like of the personal information of the user accord with the regulations of related laws and regulations, are used for legal and reasonable purposes, are not shared, leaked or sold outside the legal use aspects and the like, and are subjected to supervision and management of a supervision department. Necessary measures should be taken for the personal information of the user to prevent illegal access to such personal information data, ensure that personnel having access to the personal information data comply with the regulations of the relevant laws and regulations, and ensure the personal information of the user.
Once these user personal information data are no longer needed, the risk should be minimized by limiting or even prohibiting the data collection and/or deletion. User privacy is protected, when applicable, by de-identifying the data, including in some related applications, such as by removing a particular identifier (e.g., date of birth, etc.), controlling the amount or specificity of stored data (e.g., collecting location data at a city level rather than at a specific address level), controlling how the data is stored, and/or other methods.
Data governance is a system that implements decision-making and responsibility-dividing by a series of information-related processes that are performed according to a agreed-upon model that describes Who (Who) can take What action (What) based on What information, when (white) and under What circumstances (white). The final goal of data management is to increase the value of data, the data management is very necessary, and is the basis for enterprises to realize digital strategy, which is a management system comprising organization, system, process and tools.
The data management is used as a theoretical basis of platform design abstract modeling, and on the basis, service splitting design is carried out by combining specific data model requirements of operation and maintenance of each scene. The theory of data management is integrated into the realization of the whole system, and a great deal of targeted technical improvement is needed in the processes of data access, data conversion, data synchronization and pushing. Traditional data management schemes can only be used as theoretical support, and specific landing needs to be adapted according to specific scenes. Many open-source data governance platforms and tools exist at present, but none of them is well suited to the business of such large commercial banking operation and maintenance basic data transfer. The main pain points are as follows:
1. The enterprise cloud interface algorithm signature confidentiality requirement is very high, and the adaptation needs to be specifically developed according to the signature algorithm rule;
2. the business model is very complex and special, the model process of intermediate data conversion needs to be developed and matched according to the data model, and related data among a plurality of basic configuration items, configuration sub-items of upper and lower levels, secondary configuration sub-items, two-dimensional table attributes and the like are related, so that the data management platform and tool of general business cannot meet the requirements;
3. the requirement of data quality, for the accessed field, the pushed field and the intermediate process all need to be configurable and traceable;
4. the data models are more in variety, the data quantity of each model is larger, if each model is developed and configured with one set of process, a large amount of renaturation work exists in the development and configuration process, a large amount of manpower resources are consumed, and meanwhile, the later maintenance cost is greatly increased.
Referring to fig. 1, a main flowchart of a data synchronization processing method provided by an embodiment of the present invention is shown, including the following steps:
s101: receiving a data synchronization instruction, and calling an upstream system interface through a data access interface to acquire cloud resource data from the upstream system interface;
S102: determining a downstream system interface, inquiring a data conversion rule set corresponding to the upstream data interface and the downstream data interface, and processing cloud resource data by using the data conversion rule set to obtain cloud resource intermediate data;
s103: and inputting the cloud resource intermediate data into the association relation between the configuration item and the sub item corresponding to the downstream system interface through the data synchronization interface to obtain cloud resource data to be synchronized, and pushing the cloud resource data to be synchronized to the downstream system interface by using a pushing mode corresponding to the downstream system interface.
In the above embodiment, for step S101, the data access module is configured to configure the access information of the product configuration item in the current scenario for the data interface specification provided by the upstream system, where the access information is mainly for the interface (i.e. the first interface) of the upstream system, and the upstream system may set multiple interfaces, for example, 6 clouds are set in the cloud computing scenario, so that there are 6 interfaces, and the general data access interface interfaces interface with these 6 interfaces. In practical operation, the required interface information needs to be communicated in advance, such as offline communication.
The first interface information of the upstream interface mainly includes a first interface URL (Uniform Resource Locator ), an access mode (such as post, get), and a request parameter (including a request header, a body, and the body includes configuration items such as a type, a time, and paging acquisition data). Taking the example of the cloud computing 6 interfaces, namely 6 interfaces URL, access mode, access parameters and the cloud.
Therefore, for cloud resource data transmitted by an upstream system interface, the universal data access interface firstly determines the access mode of the upstream system interface, accesses the interface URL of the upstream system interface by using a request mode corresponding to the access mode to transmit request parameters to the upstream system interface, and then receives the cloud resource data returned by the upstream system interface and analyzes and stores the cloud resource data. The data synchronization process can be triggered and executed by a timing task, or can be triggered and executed by manual clicking of a worker.
For step S102, the data access interface is configured to extract the upstream data and analyze and store the upstream data, and the subsequent conversion operation or synchronization operation is used, so that the accessed data can be directly queried at the interface, thereby facilitating data tracing. Because of the difference in data formats required by the upstream system and the downstream system, data conversion processing is also required after the upstream data is acquired.
The scheme also needs to configure data conversion rules according to service requirements, wherein the data conversion rules comprise two types: the field augmentation rule and the multiple data source merging rule comprise three augmentation types: a field condition judgment rule, a field splicing rule and a field dictionary conversion rule. One upstream system interface may correspond to multiple rules, one downstream system interface may also correspond to multiple rules, both in a many-to-many relationship, requiring both to communicate in advance to determine, different rules corresponding to different fields.
1) Field condition judgment rule: and performing new field assignment expansion according to the condition of certain field values so as to meet the field conversion service requirement. For example, the upstream data is that the occupancy rate of the CPU resource is 80%, the section where the ratio is located is determined to be high, and the high is the data required by the downstream, or the occupancy rate of the CPU resource is 80% and the high are transmitted to the downstream system together, and the specific information is determined according to the actual.
2) Field splicing rules: for a piece of data, new fields are spliced according to values of certain fields. For example, the source of the VPC data of the upstream system has a field A, B, C, the downstream system has a field F, and the values of a and B are spliced to form a-B, and at this time, a new field D may be added based on the source data of the VPC accessed upstream.
3) Field dictionary conversion rules: and mapping the field dictionary value corresponding to the upstream system into the field dictionary value of the downstream system. For example, field value matching conversion is carried out on file storage machine head data of an upstream system, namely, chinese characters transmitted from upstream are correspondingly converted into dictionary coding values needed by downstream.
The multi-data source merging rule refers to that according to the consistency of key values of a plurality of data sources, field extraction is carried out in the multi-data source and merged into a default basic data source so as to meet business requirements, and the multi-data source merging rule is applicable to host data and cluster data. For example, the cloud hard disk storage pool cluster data is divided into storage pool node information data and cluster relation data at an upstream system, and the storage pool node information data and the cluster relation data are required to be combined and then fed to a downstream system.
Thus, due to the different field requirements, a corresponding data conversion rule needs to be configured for each field, the data conversion including basic information including rule types and rule configuration information: the field expansion/multiple data source merging, configuration items (the configuration items need to support the support of special field attributes such as configuration sub items, relationship data, two-dimensional tables and the like), conversion objects and data tables, and the rule configuration information comprises: field augmentation (including augmentation field names, default values, configuration assignment conditions, configuration check rules, multiple data source merging (including merge conditions, base data sources (including key fields, key field types), merged data sources (including association fields, association field types, extraction fields)).
According to the scheme, the data conversion rule corresponding to each field information is determined from the data conversion rule set, and then the cloud resource data of each field information is processed by using the data conversion rule to obtain the cloud resource intermediate data. Data transitions also require a comparison of the data states (update/delete).
For step S103, the present solution is further configured with synchronization fields required by the downstream system, where it needs to be checked with the downstream service system, which fields are configured by the downstream. It should be noted that, some downstream systems do not need an upstream system interface data conversion process, but directly acquire the upstream system interface data, so that a data source of the downstream system interface, such as an upstream data access or a data conversion, needs to be configured. Whether upstream data access or data conversion, the description is herein described in terms of cloud resource intermediate data.
In the prior art, a service model is very complex and special, a model process of intermediate data conversion needs to be developed and matched according to a data model, related data among a plurality of basic configuration items, upper and lower configuration sub-items, secondary configuration sub-items, two-dimensional table attributes and the like are involved, and a general commercial data management platform and tool cannot meet the requirements. In order to solve the problem, in practical application, the data required to be transmitted by the downstream system interface can be directly displayed without further processing, so that the data synchronization interface needs to configure the association relationship between the configuration item and the sub-item of the docked downstream system interface. Wherein, the configuration item: a basic operation and data service model, such as a host information configuration item, contains various attributes of a physical host. Configuration sub-items: a class of basic operation data business models, but belongs to a sub-attribute of a certain configuration item, such as a CPU information configuration item is a sub-configuration item belonging to a host.
Taking the configuration item QWE as an example, the execution result of the configuration item E needs to be sent to the configuration item W, and after the configuration item W is processed, the execution result needs to be sent to the configuration item Q again, so that the configuration item W, the configuration item Q and the configuration item Q are in a multi-level overlapping relationship, and the configuration item W, the configuration item Q and the configuration item Q are in sub-item association relationship. Therefore, the cloud resource intermediate data is required to be input into the association relationship between the configuration item and the sub item to obtain the cloud resource data to be synchronized.
And synchronizing computing resources on the cloud, storage resources on the cloud, network resources on the cloud and database resources on the cloud from cloud products, wherein main data relate to VPC information, VPN, CLB, DC, CBS, storage pools, BMS, CFS, CVM and other different information. The data needs to be synchronized into a dragon boat CMDB and a private cloud N-CMDB, and the pushing modes of different downstream systems are different, wherein the dragon boat CMDB performs data synchronization in an HTTP interface mode, and the N-CMDB performs interaction in an NFT mode. And pushing the cloud resource data to be synchronized to a corresponding downstream system interface by using different pushing modes.
The method provided by the embodiment analyzes the information of the upstream and downstream system interfaces to split and extract the universal business rules, designs a set of universal middleware, reasonably blends the business rules into the intermediate steps, converts the data of the upstream system interface into the data required by the downstream system interface, and synchronizes the data to the downstream system interface.
Referring to fig. 2, a flowchart of an optional data synchronization processing method according to an embodiment of the present invention is shown, including the following steps:
s201: receiving configuration operation of first interface information of the data access interface; the first interface of the butt joint is an interface of an upstream system, and the first interface information comprises a first interface URL, an access mode, a request parameter, a first signature encryption rule and a data return format;
S202: receiving configuration operation of local storage information of a data access interface; the local storage information comprises analysis rules corresponding to each data return format, field information accessed from an upstream system interface and a data table set;
s203: invoking a first signature encryption rule to process the request parameter through the data access interface to generate an encryption request parameter;
s204: determining an access mode of an upstream system interface, accessing a first interface URL of the upstream system interface by using a request mode corresponding to the access mode, and transmitting an encryption request parameter to the upstream system interface; the upstream system interface performs verification processing on the signature in the encryption request parameter, and returns cloud resource data corresponding to the request parameter when a verification result is passed;
s205: determining a data return format of an upstream system interface, and performing analysis processing on cloud resource data by using an analysis rule corresponding to the data return format to obtain analysis cloud resource data;
s206: determining field information corresponding to an upstream system interface, and screening target cloud resource data corresponding to the field information from the analysis cloud resource data;
s207: and storing the target cloud resource data into the data table in response to a selection operation of the data table.
In the above embodiment, the general-purpose data interface is described in detail here with respect to steps S201 to S207. According to the description shown in fig. 1, the universal data interface interfaces with interfaces of the upstream system, such as 6 interfaces in the cloud computing scene, and interface information of the docking, including interface URL, access mode and request parameters. Thus invoking the upstream system interface via the data access interface, comprising: determining an access mode of an upstream system interface through a data access interface, accessing an interface URL of the upstream system interface by using a request mode corresponding to the access mode to transmit request parameters to the upstream system interface, and then receiving cloud resource data returned by the upstream system interface.
In the prior art, the signing confidentiality requirement of the enterprise cloud interface algorithm is very high, and the adaptation needs to be specifically developed according to the signing algorithm rule. To address this problem, the upstream system interface information of the docking of the present embodiment further includes a signature encryption rule (i.e., a first signature encryption rule). Therefore, before the data access interface is used for calling the upstream system interface to acquire the data, the signature encryption rule is also required to be called for processing the request parameters so as to generate encryption request parameters and transmit the encryption request parameters to the upstream system interface, so that the upstream system interface checks the signature in the encryption request parameters, and cloud resource data corresponding to the request parameters is returned under the condition that the check result is passed.
In the prior art, the existing technology or tools need to be independently adapted to each type of data, repeated development workload is large, and code unit testing amount is large. If the field is modified, the interface field is wrong, and the code needs to be modified again, and the period is long. The data to be docked is also unknown, and the difficulty of troubleshooting is great. In addition, the requirements of data quality require configurable and traceable access fields, push fields and intermediate processes. The field to be accessed is also required to be configured, specifically, the configuration operation of receiving the local storage information of the data access interface is received; the local storage information comprises analysis rules corresponding to the data return formats, field information accessed from an upstream system interface and a data table set.
The formats of cloud resource data returned by different upstream system interfaces may be different, and for this problem, the interface information of the upstream system interface may further include a data return format when the data access interface interfaces with the upstream system interface, so that an analysis rule corresponding to the different data return formats, such as a data return format 1-analysis rule 1 and a data return format 2-analysis rule 2, needs to be configured in advance. After receiving the cloud resource data returned by the upstream system interface, the data return format of the upstream system interface can be determined first, and then the analysis rule corresponding to the data return format is used to analyze the cloud resource data to obtain analyzed cloud resource data.
The fields possibly required by different upstream system interfaces are different, or the upstream system interfaces transmit a plurality of data, but only one or more fields of the data may be needed for data synchronization, which is also pre-communication negotiation, such as an upstream system interface a-field name and an upstream system interface B-field age, so that after receiving cloud resource data transmitted by the upstream system interfaces, or after analyzing the cloud resource data, target cloud resource data corresponding to the field information of the upstream system interfaces need to be screened.
Furthermore, the scheme also needs to create a plurality of data tables in advance according to the table creating rule and the general field so as to generate a data table set. The cloud resource data of all the upstream system interfaces can be stored in the same data table, or can be stored in a data table for each upstream system interface independently, and the data tables are determined according to the selection of staff. Thus, the target cloud resource data finally screened is stored in the selected data table.
Likewise, after the target cloud resource data is converted, a new batch of data is generated and also needs to be stored in the data table. Here, the data table may be reselected by a worker, for example, the target cloud resource data are all stored in the data table X, and the converted cloud resource data are stored in the intermediate table Y. In actual operation, the data can be stored in the same table, so that the data management is facilitated.
Because the data synchronization operation is always performed, the data volume in the data table is continuously increased, and the occupied resource volume is also increased. In order to solve the technical problem, the scheme also sets an automatic cleaning time point or manually selects the data table to execute the cleaning operation on the data in the data table, thereby releasing the resources.
The method provided by the embodiment combines the basic operation data business model rules of specific various products based on the data management basic theory, and realizes the configurable operation of interface information of the data access interface docking through the splitting, the extracting and the design of a large number of business models, thereby having certain universality. Compared with the existing data management scheme, the method has the advantages of flexible configuration and universality, greatly avoids repeated development work, and reduces development cost; in order to meet the data quality management requirements, the intermediate process data can be inquired and traced.
Referring to fig. 3, a flowchart of another optional data synchronization processing method according to an embodiment of the present invention is shown, including the following steps:
s301: receiving configuration operation of second interface information of the data synchronization interface; the second interface is a downstream system interface, and the second interface information comprises a configuration data source, a pushing mode, a pushing field, a configuration item and subitem association relationship, a second interface URL and a second signature encryption rule;
S302: extracting data corresponding to the push field from the cloud resource intermediate data, and inputting the extracted data into the association relation between the configuration item and the sub item to obtain cloud resource data to be synchronized;
s303: processing cloud resource data to be synchronized by using a second signature encryption rule to obtain encrypted cloud resource data;
s304: accessing a second interface URL, and pushing the encrypted cloud resource data to a downstream system interface by using a pushing mode; the downstream data interface checks the signature pair in the encrypted cloud resource data, and displays the cloud resource data to be synchronized when the checking result is passed;
s305: generating an encrypted file based on the encrypted cloud resource data in a file generation mode, and storing the encrypted file under a preset catalog, so that a downstream system interface pulls the encrypted file from the preset catalog; the name of the encrypted file is generated based on the configuration item code of the downstream system interface.
In the above embodiment, for steps S301 to S305, for the data interface specification provided by the downstream system, the synchronization information of the product in the current scenario is configured to push the data that is put in storage after the data access/data conversion to the downstream system. The second interface information of the butt joint configured for the data synchronization interface mainly comprises a configuration data source (upstream data access or data conversion), a pushing mode, a pushing field, a association relation of a configuration item and a sub item, a second interface URL and a second signature encryption rule.
In addition to the above information, for the data synchronization interface, other information may be configured, such as basic information and synchronization push configuration, where the basic information includes: active push/passive push, configuration items, target platform, synchronous push configuration includes two kinds of nft (N-CMDB) and rest interface (CMDB), nft (N-CMDB) includes: data type, configuration item data/relationship data, synchronization data source, data access/data conversion, synchronization field mapping configuration, key field configuration, configuration sub-items, rest interface (CMDB) comprising: gate URL, POST/GET, encryption signature configuration, request body, sync data source, data access/data conversion, sync field mapping configuration, key field configuration.
And calling a data synchronization interface, extracting cloud resource data from a data source, and extracting data corresponding to the push field from the cloud resource data. In the prior art, the requirements of data quality, for the accessed fields, the pushed fields and the intermediate processes all need to be configurable and traceable. Here, for the accessed field, the configuration, i.e. pushing, is needed, so that the data corresponding to the pushing field needs to be screened out from the extracted cloud resource data; the push fields are fields required by the downstream system interface, and the fields can be the same as fields of the upstream system interface, or can be processed by the upstream system interface, such as splicing, deleting and modifying, and are in the form of { (()) }, and the hierarchy and overlapping relation between the fields are shown in brackets.
And inputting the data into the association relation between the configuration items and the sub items to obtain cloud resource data to be synchronized required by a downstream system. In the case where cloud resource data is entered into the inventory table, these cloud resource data may be acquired from the intermediate table (corresponding to the data conversion case)/data table (corresponding to the data direct access case).
In the prior art, the signing confidentiality requirement of the enterprise cloud interface algorithm is very high, and the adaptation needs to be specifically developed according to the signing algorithm rule. To address this problem, the downstream system interface information of the docking of the present embodiment further includes a signature encryption rule (i.e., a second signature encryption rule). After the cloud resource data to be synchronized is obtained, the cloud resource data to be synchronized can be processed by using a second signature encryption rule, so that encrypted cloud resource data is obtained.
Different pushing modes of different downstream system interfaces are different, for the NFT mode, an encrypted file can be generated based on encrypted data by using the NFT file generation mode, and the encrypted file is stored under a preset catalog, so that the downstream system interfaces regularly pull the encrypted file from the preset catalog; the name of the encrypted file is generated based on the configuration item code of the downstream system interface. However, in the CMDB method, the interface URL of the downstream system interface is directly accessed to push the encrypted cloud resource data to the downstream data interface using a push method corresponding to the downstream system interface. After receiving the encrypted cloud resource data, the downstream data interface checks the signature pair in the encrypted cloud resource data, and displays cloud resource intermediate data under the condition that the check is passed.
The method provided by the embodiment of the invention is based on the data management basic theory, combines the basic operation data business model rules of specific various products, realizes flexible configuration operation of interface information of synchronous docking of data access through splitting, extracting and designing of a large number of business models, has certain universality, supports the timing pushing, dynamic field pushing and signature authentication of data, and greatly avoids repeated development work.
Referring to fig. 4, a flowchart of yet another optional data synchronization processing method according to an embodiment of the present invention is shown, including the following steps:
s401: responding to clicking execution operation of the data synchronization flow, and executing the data synchronization flow;
s402: receiving a timing task configured for the data synchronization flow, and executing the data synchronization flow in response to an execution time point reaching the timing task;
the data synchronization process comprises a data access node, a data conversion node and a data synchronization node, wherein the data access node comprises one or more data access steps, the data conversion node comprises one or more data conversion steps, and the data synchronization node comprises a data synchronization step.
In the above embodiment, for steps S401 to S402, the present solution further provides a task management module, and provides task timing configuration, batch execution, and result query for various task execution instances in the resource data synchronization application by using the cloud. The task management module provides three main functions: task timing configuration, task manual execution, task execution data query.
Here, the personnel is still required to configure timing tasks, select a data access node, a data conversion node and a data synchronization node, set a task execution mode and an execution time point (for example 020, representing 8 points per day), and perform data pushing on the target platform. The data of a plurality of upstream system interfaces are transferred to the same downstream system interface, so that the number of the intermediate data conversion nodes can be also a plurality of the intermediate data conversion nodes, which can be equal to the number of the data access nodes, or can be smaller than the number of the data access nodes, for example, some downstream system interfaces access the data of the upstream system interfaces, and the data conversion operation is not needed.
In addition to setting the timing task, manual clicking execution can be set, and after the data synchronization process is configured, a worker clicks an execute button to execute the data synchronization process. The data synchronization flow comprises the steps of extracting cloud resource data from an upstream system interface through a data access interface, storing the cloud resource data into a data table, then carrying out data conversion processing according to corresponding service requirements, extracting and assembling cloud resource data to be synchronized, which is required by a downstream system interface, and pushing the cloud resource data to a downstream system.
The present scheme can thus be regarded as a data synchronization scheme; the scheme is a solution under a special service scene, comprising purposes and use scenes, the scheme comprises an execution flow, and the scheme can be repeatedly used and executed. A plurality of processes are set under the scheme, and the business circulation is sequential or the workflow composed of the dependency relations. The method comprises the steps of setting a plurality of nodes under the process, wherein the nodes consist of steps, and the steps in operation and maintenance business generally correspond to one or more configuration and execution actions.
The scheme is also provided with a scene configuration module which is used for determining the service type according to the configuration items of the upstream system interface, carrying out partition management on the data synchronization flow and the data in the data synchronization flow based on the service type, wherein the request parameters of the upstream system interface comprise the upstream configuration items (similar data). The subsequent configuration operation of the authority of different staff to access the partition can be received, so that when the access of a certain staff to the partition is received, the authority is checked, and the access of the staff to the data in the data synchronization flow of the partition is allowed only under the condition that the check passes.
The method provided by the embodiment supports the configuration of the scene scheme with the authority and also supports the configuration of the task, thereby realizing a timing management mechanism.
Referring to fig. 5, a flowchart of yet another optional data synchronization processing method according to an embodiment of the present invention is shown, including the following steps:
s501: receiving upstream tenant information transmitted by an upstream system interface and receiving downstream tenant information transmitted by a downstream system interface;
s502: receiving configuration operation of a mapping relation between upstream tenant information and downstream tenant information;
s503: and in response to receiving the data of the upstream tenant, determining a downstream tenant having a mapping relationship with the upstream tenant, so as to push the data to the downstream tenant.
In the above embodiment, for steps S501 to S503, the present solution further sets a tenant management module, which is configured to maintain a mapping relationship between a dragon boat tenant, a private cloud tenant, and a public cloud platform tenant, and is mainly a mapping relationship between the dragon boat tenant and the public cloud platform tenant.
Synchronizing tenants of the public cloud platform from the public cloud platform, synchronizing tenants of the dragon boat from the dragon boat platform, establishing a mapping relation between the tenants by a worker, and providing the mapping relation for a data synchronization interface. For example, according to the service requirement, certain configuration item data of the upstream tenant C hopes to enter a certain subsystem of the downstream system tenant D, firstly, tenant data are synchronized from the upstream synchronous tenant data and the downstream system, then tenant mapping C-D is configured, and corresponding tenant mapping configuration is selected when the tenant mapping C-D is synchronized, so that certain configuration item data of the upstream tenant C can be pushed into the subsystem of the downstream system tenant D.
According to the method provided by the embodiment, the mapping relation between the tenants is established by staff from the tenant synchronized by the upstream system and the tenant synchronized by the downstream system, and the mapping relation is provided for the data synchronization module to use, so that the directional synchronization of the data is realized.
Referring to fig. 6, a schematic diagram of main modules of a data synchronization processing apparatus 600 according to an embodiment of the present invention is shown, including:
The data access module 601 is configured to receive a data synchronization instruction, and call an upstream system interface through the data access interface to obtain cloud resource data from the upstream system interface;
the data conversion module 602 is configured to determine a downstream system interface, query a data conversion rule set corresponding to the upstream data interface and the downstream data interface, and process cloud resource data using the data conversion rule set to obtain cloud resource intermediate data;
the data synchronization module 603 is configured to input, through the data synchronization interface, cloud resource intermediate data into a association relationship between a configuration item and a sub item corresponding to the downstream system interface, to obtain cloud resource data to be synchronized, and push the cloud resource data to be synchronized to the downstream system interface by using a pushing manner corresponding to the downstream system interface.
In the embodiment of the present invention, the data access module 601 is configured to: receiving configuration operation of first interface information of the data access interface; the first interface of the butt joint is an interface of an upstream system, and the first interface information comprises a first interface URL, an access mode and a request parameter; and determining an access mode of the upstream system interface through the data access interface, accessing the first interface URL by using a request mode corresponding to the access mode to transmit the request parameters to the upstream system interface, and then receiving cloud resource data returned by the upstream system interface.
In the embodiment of the invention, the first interface information further comprises a first signature encryption rule; the data access module 601 is configured to: invoking a first signature encryption rule to process the request parameter through the data access interface to generate an encryption request parameter; determining an access mode of an upstream system interface, accessing a first interface URL of the upstream system interface by using a request mode corresponding to the access mode, and transmitting an encryption request parameter to the upstream system interface; and the upstream system interface performs verification processing on the signature in the encrypted request parameter, and returns cloud resource data corresponding to the request parameter when the verification result is passed.
In the embodiment of the present invention, the first interface information further includes a data return format, and the data access module 601 is further configured to: determining a data return format of an upstream system interface, and analyzing the cloud resource data by using an analysis rule corresponding to the data return format to obtain analyzed cloud resource data.
In the embodiment of the present invention, the data access module 601 is configured to: receiving configuration operation of local storage information of a data access interface; the local storage information comprises analysis rules corresponding to each data return format, field information accessed from an upstream system interface and a data table set; the data conversion module 602 is further configured to: determining field information corresponding to an upstream system interface, and screening target cloud resource data corresponding to the field information from the analysis cloud resource data; and storing the target cloud resource data into the data table in response to a selection operation of the data table.
In the embodiment of the present invention, the data conversion module 602 is configured to: determining a data conversion rule corresponding to each field information from the data conversion rule set, and processing the target cloud resource data of each field information by using the data conversion rule; the data conversion rule set comprises one or more of a field expansion rule and a multi-data source merging rule, and the field expansion rule comprises one or more of a field condition judging rule, a field splicing rule and a field dictionary conversion rule.
In the embodiment of the present invention, the data synchronization module 603 is further configured to: receiving configuration operation of second interface information of the data synchronization interface; the second interface is an interface of a downstream system, and the second interface information comprises a configuration data source, a pushing mode, a pushing field, a configuration item and a sub item association relation; and extracting data corresponding to the push field from the cloud resource intermediate data, and inputting the extracted data into the association relation between the configuration item and the sub item to obtain the cloud resource data to be synchronized.
In the embodiment of the present invention, the interface information further includes a second interface URL and a second signature encryption rule, and the data synchronization module 603 is configured to: processing cloud resource data to be synchronized by using a second signature encryption rule to obtain encrypted cloud resource data; accessing a second interface URL, and pushing the encrypted cloud resource data to a downstream system interface by using a pushing mode; the downstream data interface checks the signature pair in the encrypted cloud resource data, and displays the cloud resource data to be synchronized when the checking result is passed; or generating an encrypted file based on the encrypted cloud resource data in a file generation mode, and storing the encrypted file under a preset catalog, so that a downstream system interface pulls the encrypted file from the preset catalog; the name of the encrypted file is generated based on the configuration item code of the downstream system interface.
The implementation device of the invention also comprises a task management module for: responding to clicking execution operation of the data synchronization flow, and executing the data synchronization flow; or receiving a timing task configured for the data synchronization flow, and executing the data synchronization flow in response to the execution time point of the timing task; the data synchronization process comprises a data access node, a data conversion node and a data synchronization node, wherein the data access node comprises one or more data access steps, the data conversion node comprises one or more data conversion steps, and the data synchronization node comprises a data synchronization step.
The implementation device of the invention also comprises a tenant management module for: receiving upstream tenant information transmitted by an upstream system interface and receiving downstream tenant information transmitted by a downstream system interface; receiving configuration operation of a mapping relation between upstream tenant information and downstream tenant information; and in response to receiving the data of the upstream tenant, determining a downstream tenant having a mapping relationship with the upstream tenant, so as to push the data to the downstream tenant.
The implementation device of the invention also comprises a data table management module which is used for: creating a plurality of data tables according to the table creating rules and the general fields; the cleansing operation for the data in the data table is performed in response to reaching the cleansing time point, or in response to a selection operation for cleansing data of the data table.
The implementation device of the invention also comprises a data management module for: after receiving the execution completion information, the intermediate process data is obtained and displayed in response to the checking operation of the intermediate process data of the data synchronization flow.
In addition, the implementation of the apparatus in the embodiments of the present invention has been described in detail in the above method, so that the description is not repeated here.
Referring to fig. 7 (a), an architecture schematic diagram of the present solution is shown, which mainly includes a task management module, a tenant management module, an access table management module, a scene management module, a data access module, a data conversion module, and a data synchronization module, where the access table management module and the tenant management module belong to an auxiliary module and mainly perform preprocessing operation; the data management module belongs to a post-processing module and is mainly used for checking and tracing data flow.
1. A scene management module: different scenes are set for different product configuration items, and staff of different product items configure individually authorized product scene data, and mainly perform authority management on the product configuration items according to service scenes. Comprises three core functional modules: the data access module, the data conversion module and the data synchronization module are shown in fig. 7 (b).
1) And the data access module is used for: and aiming at the data interface specification provided by the upstream system, configuring the access information of the product configuration item in the current scene so as to extract the data of the interface of the upstream system and analyze and store the data. The method mainly comprises basic configuration information (such as URL and request parameters) of a configuration interface, signature encryption rules (such as asymmetric encryption apikey), accessed field information, a data table and the like.
2) And a data conversion module: for the data which is configured to be accessed and put in storage, the operation processing of field conversion is carried out, and the data conversion rule comprises two types: the field augmentation rule and the multiple data source merging rule comprise three augmentation types: a field condition judgment rule, a field splicing rule and a field dictionary conversion rule. One upstream system interface may correspond to multiple rules, one downstream system interface may also correspond to multiple rules, both in a many-to-many relationship, requiring both to communicate in advance to determine, different rules corresponding to different fields.
3) And a data synchronization module: and aiming at the data interface specifications provided by the downstream system, configuring the synchronous information of the product in the current scene, and pushing the data which is subjected to data access/data conversion and then put in storage to the downstream system. Mainly, the method comprises the steps of configuring data sources, interface URLs, signature encryption rules (such as asymmetric encryption apikey), pushing modes, pushing fields, configuration items, sub item association relations and the like. And the data needed by the downstream system is extracted and assembled and pushed to the downstream system.
In addition, the scene management module is also used for determining the service type according to the configuration item of the upstream system and carrying out partition management on the data synchronization flow and the data in the data synchronization flow based on the service type. And receiving configuration operation of the authority of different staff to access the partition, and checking the authority of the partition when the access of a certain staff to the partition is received, wherein the access of the staff to the partition is allowed only when the verification passes the data synchronization flow and the data in the data synchronization flow of the partition.
2. The access table management module: before core scene function configuration is carried out, a worker is required to define a data table corresponding to each product configuration item aiming at data provided by an upstream system. According to the configuration of the access table of each product configuration item, the data accessed by the data access module, the data converted by the data conversion module and the data synchronously pushed by the data synchronization module are stored, and the accessed data can be directly inquired at the interface, so that the data can be traced.
To avoid stressing the database tables with large amounts of data, the data for each product configuration item may be stored separately. In order to avoid overlarge data volume caused by long-term batch running tasks and influence the performance of a database table, a background timing cleaning task and an interface manual data cleaning function are added in the access table management module.
3. And a data management module: and checking and verifying intermediate process data of each product configuration item according to the data quality requirement. The whole flow and data are visible and traceable from the access of the data to the data pushed to the downstream system, and the method comprises the steps of access data inquiry, conversion data inquiry and synchronous push data inquiry. For example, the data access interface pulls data from the upstream system interface, enters the data table, and can query the source data accessed by the current batch from the interface.
4. The task management module: task timing configuration, batch execution and result query are provided for various task execution instances in the cloud resource synchronization application. The task management module provides three main functions: task timing configuration, task manual execution and task execution data query, such as configuring a cron expression, and executing the configured task at regular time according to rules corresponding to the expression.
5. Tenant management module: and a worker is required to provide the tenant mapping relation needed to be used by the upstream and downstream configuration item data model for the data synchronization module in advance.
The scheme is used for providing a universal and configurable data conversion base between IT operation and maintenance systems of large commercial banks, and adapting an intermediate platform according to data required by upstream and downstream. And synchronizing cloud resource data from the cloud platform to the dragon boat CMDB system and the N-CMDB of the private cloud, wherein the data relate to configuration item information of various cloud product information such as VPC information, VPN, CLB, DC, CBS, storage pool, BMS, CFS, CVM and the like. The IT operation and maintenance refers to comprehensive management of the whole bank organization by adopting related methods, means, technologies, systems, processes, documents and the like in order to ensure that all-weather normal work of various network points, various systems, various application systems and the like of the bank is ensured.
Fig. 8 shows an exemplary system architecture 800, including terminal devices 801, 802, 803, a network 804, and a server 805 (by way of example only), to which embodiments of the invention may be applied.
The terminal devices 801, 802, 803 may be various electronic devices having a display screen and supporting web browsing, have various communication client applications installed, and a user may interact with the server 805 through the network 804 using the terminal devices 801, 802, 803 to receive or transmit messages, etc.
The network 804 serves as a medium for providing communication links between the terminal devices 801, 802, 803 and the server 805. The network 804 may include various connection types, such as wired, wireless communication links, or fiber optic cables, among others.
The server 805 may be a server providing various services, and it should be noted that the method provided by the embodiment of the present invention is generally performed by the server 805, and accordingly, the apparatus is generally disposed in the server 805.
It should be understood that the number of terminal devices, networks and servers in fig. 8 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.
Referring now to FIG. 9, there is illustrated a schematic diagram of a computer system 900 suitable for use in implementing an embodiment of the present invention. The terminal device shown in fig. 9 is only an example, and should not impose any limitation on the functions and the scope of use of the embodiment of the present invention.
As shown in fig. 9, the computer system 900 includes a Central Processing Unit (CPU) 901, which can execute various appropriate actions and processes according to a program stored in a Read Only Memory (ROM) 902 or a program loaded from a storage section 908 into a Random Access Memory (RAM) 903. In the RAM 903, various programs and data necessary for the operation of the system 900 are also stored. The CPU 901, ROM 902, and RAM 903 are connected to each other through a bus 904. An input/output (I/O) interface 905 is also connected to the bus 904.
The following components are connected to the I/O interface 905: an input section 906 including a keyboard, a mouse, and the like; an output portion 907 including a display such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and a speaker; a storage portion 908 including a hard disk or the like; and a communication section 909 including a network interface card such as a LAN card, a modem, or the like. The communication section 909 performs communication processing via a network such as the internet. The drive 910 is also connected to the I/O interface 905 as needed. A removable medium 911 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is installed as needed on the drive 910 so that a computer program read out therefrom is installed into the storage section 908 as needed.
In particular, according to embodiments of the present disclosure, the processes described above with reference to flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method shown in the flow chart. In such an embodiment, the computer program may be downloaded and installed from the network via the communication portion 909 and/or installed from the removable medium 911. The above-described functions defined in the system of the present invention are performed when the computer program is executed by a Central Processing Unit (CPU) 901.
The computer readable medium shown in the present invention may be a computer readable signal medium or a computer readable storage medium, or any combination of the two. The computer readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples of the computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In the present invention, however, the computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, with the computer-readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.
The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The modules involved in the embodiments of the present invention may be implemented in software or in hardware. The described modules may also be provided in a processor, for example, as: a processor comprises a data access module, a data conversion module and a data synchronization module. The names of these modules do not in any way constitute a limitation of the module itself, for example, a data synchronization module may also be described as a "synchronous data module".
As another aspect, the present invention also provides a computer-readable medium that may be contained in the apparatus described in the above embodiments; or may be present alone without being fitted into the device. The computer readable medium carries one or more programs which, when executed by a device, cause the device to perform any of the data synchronization processing methods described above.
The computer program product of the present invention comprises a computer program which, when executed by a processor, implements the data synchronization processing method in the embodiments of the present invention.
The above embodiments do not limit the scope of the present invention. It will be apparent to those skilled in the art that various modifications, combinations, sub-combinations and alternatives can occur depending upon design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present invention should be included in the scope of the present invention.
Claims (25)
1. A method for synchronously processing data, comprising:
receiving a data synchronization instruction, and calling an upstream system interface through a data access interface to acquire cloud resource data from the upstream system interface;
Determining a downstream system interface, inquiring a data conversion rule set corresponding to the upstream data interface and the downstream data interface, and processing cloud resource data by using the data conversion rule set to obtain cloud resource intermediate data;
and inputting the cloud resource intermediate data into the association relation between the configuration item and the sub item corresponding to the downstream system interface through the data synchronization interface to obtain cloud resource data to be synchronized, and pushing the cloud resource data to be synchronized to the downstream system interface by using a pushing mode corresponding to the downstream system interface.
2. The method of claim 1, wherein prior to said invoking the upstream system interface via the data access interface, the method further comprises:
receiving configuration operation of first interface information of the data access interface; the first interface of the butt joint is an interface of an upstream system, and the first interface information comprises a first interface URL, an access mode and a request parameter;
the calling the upstream system interface through the data access interface comprises the following steps:
determining an access mode of an upstream system interface through a data access interface, accessing a first interface URL by using a request mode corresponding to the access mode to transmit request parameters to the upstream system interface, and then receiving cloud resource data returned by the upstream system interface.
3. The method of claim 2, wherein the first interface information further comprises a first signature encryption rule;
the determining the access mode of the upstream system interface through the data access interface, accessing the first interface URL by using the request mode corresponding to the access mode to transmit the request parameter to the upstream system interface, and then receiving cloud resource data returned by the upstream system interface, including:
invoking a first signature encryption rule to process the request parameter through the data access interface to generate an encryption request parameter;
determining an access mode of an upstream system interface, accessing a first interface URL of the upstream system interface by using a request mode corresponding to the access mode, and transmitting an encryption request parameter to the upstream system interface; and the upstream system interface performs verification processing on the signature in the encrypted request parameter, and returns cloud resource data corresponding to the request parameter when the verification result is passed.
4. A method according to claim 2 or 3, wherein the first interface information further comprises a data return format, the method further comprising, after the acquiring cloud resource data from the upstream system interface:
Determining a data return format of an upstream system interface, and analyzing the cloud resource data by using an analysis rule corresponding to the data return format to obtain analyzed cloud resource data.
5. The method of claim 4, wherein prior to said invoking the upstream system interface via the data access interface, the method further comprises:
receiving configuration operation of local storage information of a data access interface; the local storage information comprises analysis rules corresponding to each data return format, field information accessed from an upstream system interface and a data table set;
after the parsing cloud resource data is obtained, the method further comprises:
determining field information corresponding to an upstream system interface, and screening target cloud resource data corresponding to the field information from the analysis cloud resource data; and
and storing the target cloud resource data into the data table in response to a selection operation of the data table.
6. The method of claim 5, wherein processing cloud resource data using the set of data conversion rules comprises:
determining a data conversion rule corresponding to each field information from the data conversion rule set, and processing the target cloud resource data of each field information by using the data conversion rule;
The data conversion rule set comprises one or more of a field expansion rule and a multi-data source merging rule, and the field expansion rule comprises one or more of a field condition judging rule, a field splicing rule and a field dictionary conversion rule.
7. The method of claim 1, wherein prior to said entering cloud resource intermediate data into configuration items and sub-item associations corresponding to downstream system interfaces, the method further comprises:
receiving configuration operation of second interface information of the data synchronization interface; the second interface is an interface of a downstream system, and the second interface information comprises a configuration data source, a pushing mode, a pushing field, a configuration item and a sub item association relation;
inputting the cloud resource intermediate data into the association relationship between the configuration item and the sub item corresponding to the downstream system interface to obtain cloud resource data to be synchronized, including:
and extracting data corresponding to the push field from the cloud resource intermediate data, and inputting the extracted data into the association relation between the configuration item and the sub item to obtain the cloud resource data to be synchronized.
8. The method of claim 7, wherein the interface information further includes a second interface URL and a second signature encryption rule, and the pushing the cloud resource data to be synchronized to the downstream system interface using a pushing manner corresponding to the downstream system interface includes:
Processing cloud resource data to be synchronized by using a second signature encryption rule to obtain encrypted cloud resource data;
accessing a second interface URL, and pushing the encrypted cloud resource data to a downstream system interface by using a pushing mode; the downstream data interface checks the signature pair in the encrypted cloud resource data, and displays the cloud resource data to be synchronized when the checking result is passed; or (b)
Generating an encrypted file based on the encrypted cloud resource data in a file generation mode, and storing the encrypted file under a preset catalog, so that a downstream system interface pulls the encrypted file from the preset catalog; the name of the encrypted file is generated based on the configuration item code of the downstream system interface.
9. The method according to claim 1, wherein the method further comprises:
responding to clicking execution operation of the data synchronization flow, and executing the data synchronization flow; or (b)
Receiving a timing task configured for the data synchronization flow, and executing the data synchronization flow in response to an execution time point reaching the timing task;
the data synchronization process comprises a data access node, a data conversion node and a data synchronization node, wherein the data access node comprises one or more data access steps, the data conversion node comprises one or more data conversion steps, and the data synchronization node comprises a data synchronization step.
10. The method according to claim 1, wherein the method further comprises:
receiving upstream tenant information transmitted by an upstream system interface and receiving downstream tenant information transmitted by a downstream system interface;
receiving configuration operation of a mapping relation between upstream tenant information and downstream tenant information;
and in response to receiving the data of the upstream tenant, determining a downstream tenant having a mapping relationship with the upstream tenant, so as to push the data to the downstream tenant.
11. The method according to claim 1, wherein the method further comprises:
creating a plurality of data tables according to the table creating rules and the general fields;
the cleansing operation for the data in the data table is performed in response to reaching the cleansing time point, or in response to a selection operation for cleansing data of the data table.
12. The method of claim 1, wherein after the pushing the target cloud resource data to the downstream system interface, the method further comprises:
after receiving the execution completion information, the intermediate process data is obtained and displayed in response to the checking operation of the intermediate process data of the data synchronization flow.
13. A data synchronization processing apparatus, comprising:
The data access module is used for receiving the data synchronization instruction, and calling an upstream system interface through the data access interface so as to acquire cloud resource data from the upstream system interface;
the data conversion module is used for determining a downstream system interface, inquiring a data conversion rule set corresponding to the upstream data interface and the downstream data interface, and processing cloud resource data by using the data conversion rule set to obtain cloud resource intermediate data;
the data synchronization module is used for inputting the cloud resource intermediate data into the association relation between the configuration item and the sub item corresponding to the downstream system interface through the data synchronization interface to obtain cloud resource data to be synchronized, and pushing the cloud resource data to be synchronized to the downstream system interface by using a pushing mode corresponding to the downstream system interface.
14. The apparatus of claim 13, wherein the data access module is configured to:
receiving configuration operation of first interface information of the data access interface; the first interface of the butt joint is an interface of an upstream system, and the first interface information comprises a first interface URL, an access mode and a request parameter; and
determining an access mode of an upstream system interface through a data access interface, accessing a first interface URL by using a request mode corresponding to the access mode to transmit request parameters to the upstream system interface, and then receiving cloud resource data returned by the upstream system interface.
15. The apparatus of claim 14, wherein the first interface information further comprises a first signature encryption rule;
the data access module is used for:
invoking a first signature encryption rule to process the request parameter through the data access interface to generate an encryption request parameter;
determining an access mode of an upstream system interface, accessing a first interface URL of the upstream system interface by using a request mode corresponding to the access mode, and transmitting an encryption request parameter to the upstream system interface; and the upstream system interface performs verification processing on the signature in the encrypted request parameter, and returns cloud resource data corresponding to the request parameter when the verification result is passed.
16. The apparatus of claim 14 or 15, wherein the first interface information further comprises a data return format, the data access module further configured to:
determining a data return format of an upstream system interface, and analyzing the cloud resource data by using an analysis rule corresponding to the data return format to obtain analyzed cloud resource data.
17. The apparatus of claim 16, wherein the data access module is configured to:
Receiving configuration operation of local storage information of a data access interface; the local storage information comprises analysis rules corresponding to each data return format, field information accessed from an upstream system interface and a data table set;
the data conversion module is further configured to:
determining field information corresponding to an upstream system interface, and screening target cloud resource data corresponding to the field information from the analysis cloud resource data; and
and storing the target cloud resource data into the data table in response to a selection operation of the data table.
18. The apparatus of claim 17, wherein the data conversion module is configured to:
determining a data conversion rule corresponding to each field information from the data conversion rule set, and processing the target cloud resource data of each field information by using the data conversion rule;
the data conversion rule set comprises one or more of a field expansion rule and a multi-data source merging rule, and the field expansion rule comprises one or more of a field condition judging rule, a field splicing rule and a field dictionary conversion rule.
19. The apparatus of claim 13, wherein the data synchronization module is further configured to:
Receiving configuration operation of second interface information of the data synchronization interface; the second interface is an interface of a downstream system, and the second interface information comprises a configuration data source, a pushing mode, a pushing field, a configuration item and a sub item association relation; and
and extracting data corresponding to the push field from the cloud resource intermediate data, and inputting the extracted data into the association relation between the configuration item and the sub item to obtain the cloud resource data to be synchronized.
20. The apparatus of claim 19, wherein the interface information further comprises a second interface URL, a second signature encryption rule, and the data synchronization module is configured to:
processing cloud resource data to be synchronized by using a second signature encryption rule to obtain encrypted cloud resource data;
accessing a second interface URL, and pushing the encrypted cloud resource data to a downstream system interface by using a pushing mode; the downstream data interface checks the signature pair in the encrypted cloud resource data, and displays the cloud resource data to be synchronized when the checking result is passed; or (b)
Generating an encrypted file based on the encrypted cloud resource data in a file generation mode, and storing the encrypted file under a preset catalog, so that a downstream system interface pulls the encrypted file from the preset catalog; the name of the encrypted file is generated based on the configuration item code of the downstream system interface.
21. The apparatus of claim 13, further comprising a task management module to:
responding to clicking execution operation of the data synchronization flow, and executing the data synchronization flow; or (b)
Receiving a timing task configured for the data synchronization flow, and executing the data synchronization flow in response to an execution time point reaching the timing task;
the data synchronization process comprises a data access node, a data conversion node and a data synchronization node, wherein the data access node comprises one or more data access steps, the data conversion node comprises one or more data conversion steps, and the data synchronization node comprises a data synchronization step.
22. The apparatus of claim 13, further comprising a tenant management module to:
receiving upstream tenant information transmitted by an upstream system interface and receiving downstream tenant information transmitted by a downstream system interface;
receiving configuration operation of a mapping relation between upstream tenant information and downstream tenant information;
and in response to receiving the data of the upstream tenant, determining a downstream tenant having a mapping relationship with the upstream tenant, so as to push the data to the downstream tenant.
23. An electronic device, comprising:
one or more processors;
storage means for storing one or more programs,
when executed by the one or more processors, causes the one or more processors to implement the method of any of claims 1-12.
24. A computer readable medium, on which a computer program is stored, characterized in that the program, when being executed by a processor, implements the method according to any of claims 1-12.
25. A computer program product comprising a computer program which, when executed by a processor, implements the method according to any one of claims 1-12.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311240213.7A CN117271147A (en) | 2023-09-25 | 2023-09-25 | Data synchronous processing method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311240213.7A CN117271147A (en) | 2023-09-25 | 2023-09-25 | Data synchronous processing method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117271147A true CN117271147A (en) | 2023-12-22 |
Family
ID=89217278
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311240213.7A Pending CN117271147A (en) | 2023-09-25 | 2023-09-25 | Data synchronous processing method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117271147A (en) |
-
2023
- 2023-09-25 CN CN202311240213.7A patent/CN117271147A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112685385B (en) | Big data platform for smart city construction | |
| CN112001500B (en) | Model training method, device and storage medium based on longitudinal federated learning system | |
| CN111427561A (en) | Service code generation method and device, computer equipment and storage medium | |
| CN111382956A (en) | Enterprise group relationship mining method and device | |
| US11907390B2 (en) | Method and apparatus for visual construction of knowledge graph system | |
| CN104717197B (en) | Conversation management system, session management equipment and conversation managing method | |
| CN115334025B (en) | Decentralized instant messaging method, decentralized instant messaging device, decentralized instant messaging equipment and storage medium | |
| CN115510249A (en) | Knowledge graph construction method and device, electronic equipment and storage medium | |
| CN112860744A (en) | Business process processing method and device | |
| CN107909164B (en) | Operation and maintenance processing method, system, electronic equipment and computer readable medium | |
| CN116611411A (en) | Business system report generation method, device, equipment and storage medium | |
| CN105871998A (en) | Data displaying method and device | |
| CN110321252B (en) | Skill service resource scheduling method and device | |
| CN109299913B (en) | Employee salary scheme generation method and device | |
| US10505873B2 (en) | Streamlining end-to-end flow of business-to-business integration processes | |
| CN112765169A (en) | Data processing method, device, equipment and storage medium | |
| CN110852701A (en) | Product demand management method, device and system | |
| CN117271147A (en) | Data synchronous processing method and device | |
| CN108959309B (en) | Method and device for data analysis | |
| KR20220150847A (en) | Office system and work task management method and device | |
| US20220337569A1 (en) | Systems, methods, and devices for automation and integration of credentialing and authentication in workflows associated with computing platforms | |
| CN113691403A (en) | Topological node configuration method, related device and computer program product | |
| CN111786801A (en) | Method and device for charging based on data flow | |
| CN112527290A (en) | Method and device for building page based on biological characteristic information | |
| US11651030B2 (en) | Delta-based conflict-free replicated data type arrays using dot stores that map dots to dot stores |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |