Data repair method and device, electronic equipment and storage medium

Abstract

The application discloses a data repairing method and device, electronic equipment and a storage medium. The application is applied to an interface monitoring module in a business system, the business system further comprises an interface layer module and a blockchain node, the interface monitoring module is in communication connection with the interface layer module and the blockchain node, and the method comprises the following steps: obtaining interaction data between different business systems cached by the interface layer module to obtain cached data; obtaining target data to be interacted by the interface layer module from the blockchain node to obtain blockchain data; comparing the cached data with the blockchain data to obtain a comparison result; and when the comparison result is that the cached data is inconsistent with the blockchain data, repairing the cached data according to the blockchain data. The data repairing method provided by the application can automatically repair the interaction data of interaction abnormities, thereby improving the technical effect of the repairing efficiency of the interaction data.

Description

Technical Field

[0001] This application relates to computer technology, specifically to a data recovery method, apparatus, electronic device, and storage medium. Background Technology

[0002] Currently, with the rapid development of computer network technology, various business systems have realized data interaction based on interfaces.

[0003] When business systems interact with each other through interfaces, logging services are added to monitor the running status of the interfaces. During the interface interaction process, abnormal situations often occur. Generally, the main way to handle such abnormalities is to use interface logs to analyze the problem and then repair the interface data.

[0004] Traditional API logging can monitor APIs by recording their running status. However, this method often only records the status of APIs that are relevant to the business system itself, and does not provide a complete tracing chain for the API interaction process. When data exchange is corrupted due to API issues, it is impossible to repair the abnormal data through API logs, which can significantly impact business processes. Summary of the Invention

[0005] This invention provides a data repair method, apparatus, electronic device, and storage medium to achieve the technical effect of automatically repairing problematic data when data transmission problems occur in the interface layer module.

[0006] The technical solution of this application is as follows:

[0007] Firstly, a data repair method is provided, applied to an interface monitoring module in a business system. The business system further includes an interface layer module and a blockchain node. The interface monitoring module is communicatively connected to both the interface layer module and the blockchain node. The data repair method includes:

[0008] Obtain the interaction data between different business systems cached by the interface layer module to get the cached data;

[0009] Obtain the target data to be interacted with by the interface layer module from the blockchain node to obtain the blockchain data;

[0010] The cached data is compared with the blockchain data to obtain the comparison results;

[0011] When the comparison result shows that the cached data and the blockchain data are inconsistent, the cached data is repaired based on the blockchain data.

[0012] Secondly, a data repair device is provided, applied to an interface monitoring module in a business system. The business system also includes an interface layer module and a blockchain node, with the interface monitoring module communicating with both the interface layer module and the blockchain node. The device includes:

[0013] The cached data acquisition module is used to acquire the interaction data between different business systems cached by the interface layer module, and obtain the cached data.

[0014] The blockchain data acquisition module is used to obtain the target data to be interacted with by the interface layer module from the blockchain node, thus obtaining the blockchain data;

[0015] The data comparison module is used to compare the cached data with the blockchain data to obtain the comparison result;

[0016] The data repair module is used to repair cached data based on blockchain data when the comparison result shows that cached data and blockchain data are inconsistent.

[0017] Thirdly, embodiments of this application provide an electronic device, which includes a processor, a memory, and a program or instructions stored in the memory and executable on the processor. When the program or instructions are executed by the processor, they implement the steps of the data repair method described in any one of the embodiments of the present invention.

[0018] Fourthly, embodiments of this application provide a computer storage medium storing computer program instructions, which, when executed by a processor, implement the steps of the data repair method described in any one of the embodiments of the present invention.

[0019] The technical solutions provided by the embodiments of this application bring at least the following beneficial effects:

[0020] Data interaction between business systems can be disrupted by interface issues, leading to data exchange anomalies. Since interface logs cannot fully record the entire data exchange process, it's impossible to promptly identify and repair these anomalies based on them. The data repair method provided in this application involves an interface monitoring module sending the data to be interacted to a blockchain node for storage before data interaction occurs at the interface layer. When business systems interact through the interface layer, the module caches the interaction data. The interface monitoring module retrieves the cached interaction data and obtains the blockchain data from the data stored on the blockchain node. The cached data and blockchain data are compared; if they are inconsistent, the cached data is repaired based on the blockchain data. This method enables automatic repair of abnormal interaction data, thereby improving the efficiency of data repair.

[0021] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and do not limit this application. Attached Figure Description

[0022] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application, and do not constitute an undue limitation of this application.

[0023] Figure 1 This is a flowchart illustrating a data repair method provided in an embodiment of this application. Figure 1 ;

[0024] Figure 2 This is a schematic diagram of a business system structure provided in an embodiment of this application;

[0025] Figure 3 This is a flowchart illustrating a data repair method provided in an embodiment of this application. Figure 2 ;

[0026] Figure 4 This is a schematic diagram of the structure of a data repair device provided in an embodiment of this application;

[0027] Figure 5 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0028] To enable those skilled in the art to better understand the technical solutions of this application, the technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. It should be understood that the specific embodiments described herein are merely intended to explain this application and not to limit it. For those skilled in the art, this application can be implemented without some of these specific details. The following description of the embodiments is merely to provide a better understanding of this application by illustrating examples.

[0029] It should be noted that the terms "first," "second," etc., used in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples consistent with some aspects of this application as detailed in the appended claims.

[0030] As the background technology indicates, during data interaction between business systems and interfaces, data corruption often occurs due to interface malfunctions. Common interface interaction anomalies include: 1. Network interruptions or system-specific issues causing interface timeouts and data loss. 2. Defective interface design leading to data processing errors and data corruption. 3. Problems with the business system or the data itself causing interface interaction anomalies, resulting in data errors or loss.

[0031] Traditional interface logging can be used to monitor the running status of interfaces. However, it does not provide a complete tracing chain for the interaction process between business systems. For example, if the interface interaction between two business systems is flawed due to design defects in the interface specification, it is difficult to trace the source of the design problem, find the error, and automatically correct it from the log records. By the time the error is discovered in the front-end application, it has already had a significant impact on the business process.

[0032] Furthermore, the inventors discovered through research that blockchain is essentially an immutable and traceable hash chain, whose characteristics can be applied to any scenario requiring traceable, tamper-proof, and forgery-proof data records. By deploying blockchain nodes in various business systems, data to be transmitted is uploaded to the blockchain nodes for storage before being transmitted via interfaces. This ensures that the blockchain nodes store complete, undamaged, and tamper-proof data for transmission. The data to be transmitted can be synchronized across the entire blockchain network. If problems occur with data transmitted through the business system's interface, the faulty data can be repaired based on the data stored in the blockchain nodes.

[0033] Based on this, embodiments of this application provide a data repair method, apparatus, electronic device, and storage medium, which can automatically repair data when problems occur during data interaction between different business systems, thereby improving the technical effect of improving the repair efficiency of interactive data.

[0034] The data repair method provided in the embodiments of this application will be described in detail below with reference to the accompanying drawings.

[0035] Figure 1 This illustration shows a flowchart of a data repair method provided in an embodiment of this application. The method can be applied to an interface monitoring module in a business system. The business system further includes an interface layer module and a blockchain node; the interface monitoring module is communicatively connected to both the interface layer module and the blockchain node. This embodiment of the invention uses the interface monitoring module as the executing entity to perform the steps of the data repair method provided in this embodiment. Figure 1 As shown, the method may include steps S110-S140.

[0036] Step S110: Obtain the interaction data between different business systems cached by the interface layer module to obtain the cached data.

[0037] Understandably, a business system is a system platform that undertakes a specific type of business function. It achieves data interaction through interfaces to realize the operation of comprehensive business functions. The interface layer module is a collection of traditional interfaces within the business system, which can be one or more interface methods such as Web Service interfaces, Socket interfaces, and Message Queues. Besides transmitting data to enable data interaction between different business systems, the interface layer module can also cache the data exchanged between different business systems. Specifically, this step involves the interface monitoring module establishing a communication connection with the interface layer module of the business system and retrieving the cached interaction data between different business systems from the interface layer module.

[0038] In one example, before obtaining the cached interaction data from the interface layer module, step S111 may be included.

[0039] Step S111: Push the target data to be interacted with by the interface layer module to the blockchain node for storage.

[0040] It is understandable that, such as Figure 2 As shown, blockchain nodes are set up in each business system. A network layer also connects the various business systems. The network layer is a unified network infrastructure that carries traditional interfaces and the blockchain peer-to-peer (P2P) network. To enable tracing of interface failures caused by network outages and self-healing of interactive data, the network structure and routing design used by the traditional interfaces and blockchain nodes must be consistent. The interface monitoring module in each business system communicates with the blockchain node. Specifically, before data interaction occurs in the interface layer module, the interface monitoring module sends the target data to be interacted to the blockchain node and saves the target data to be interacted to the blockchain data area in the blockchain node, thus achieving data on-chain. Simultaneously, the target data to be interacted is synchronized to other blockchain nodes through the P2P network.

[0041] In one example, pushing the target data to be interacted with by the interface layer module to the blockchain node for storage may include: steps S1111-S1112.

[0042] Step S1111: Filter the data to be interacted with in the interface layer module according to preset rules to obtain the target data.

[0043] It is understandable that the amount of data exchanged between various business systems is enormous. If all the data to be exchanged between systems is uploaded to the blockchain node for storage, it will increase the storage pressure on the blockchain node and be detrimental to the operation of the business system. Therefore, it is necessary to filter the data to be exchanged.

[0044] Specifically, this step involves the interface monitoring module filtering based on the function of each interface in the interface layer module. For example, interface A is used for data exchanged between business systems that is critical to the system's operation, such as customer information or key system operation data. Interface B is used for data exchanged between business systems that, even if problems occur during the exchange, will not affect the system's operation or the user, such as temporary directories. Since the data transmitted by interface A is critical to the user and system operation, the interface monitoring module will use the data exchanged through interface A as the target data, while the data exchanged through interface B will not be considered as the target data.

[0045] It can also filter based on the attributes of the data to be interacted with. Target attribute information such as target name and / or target size can be preset, and the interface monitoring module will use the data to be interacted with that matches the target attribute information as the target data.

[0046] Step S1112: Push the target data to the blockchain node for storage.

[0047] Specifically, this step can be as follows: After determining the target data from the data to be interacted with in the interface layer module, the interface monitoring module pushes the target data to the blockchain node in the same business system for storage.

[0048] Step S120: Obtain the target data to be interacted with by the interface layer module from the blockchain node to obtain the blockchain data.

[0049] This step can be specifically described as follows: Because the interface monitoring module communicates with the blockchain node, it obtains the target data to be interacted with by the interface layer module from the blockchain node, thus obtaining the blockchain data. Since the time required for the interface monitoring module to push the target data to the blockchain node for storage is relatively long, the interface monitoring module may not simultaneously obtain both cached data and blockchain data; therefore, an asynchronous acquisition method is used.

[0050] In one example, obtaining the target data to be interacted with by the interface layer module from the blockchain node to obtain blockchain data may include: steps S1201-S1202.

[0051] Step S1201: Obtain the target data quantity stored in the blockchain node at a preset time point.

[0052] This step can be specifically described as follows: The preset time point can be set to real-time or to a time point with a preset time interval. The preset time interval can be equal or unequal. The interface monitoring module monitors the status of the blockchain data area in the blockchain node according to the preset time point and obtains the amount of target data stored in the blockchain data area.

[0053] Step S1202: When the amount of target data acquired at the current time point is greater than the amount of target data acquired at the previous time point, acquire the target data and obtain the blockchain data.

[0054] This step can be specifically described as follows: The interface monitoring module compares the current target data quantity with the previous target data quantity. When the current target data quantity increases compared to the previous target data quantity, it determines that the blockchain data area in the blockchain node stores the new target data. The interface monitoring module then obtains the new target data, thereby acquiring the blockchain data.

[0055] In one example, obtaining the target data to be interacted with by the interface layer module from the blockchain node to obtain blockchain data may include step S1203.

[0056] Step S1203: Acquire target data at preset time points to obtain blockchain data.

[0057] This step can be specifically described as follows: Pre-set time points. These time points can be at equal or unequal intervals. For example, the time can be set from 8:00 AM to 8:00 PM, with half-hour intervals, i.e., 8:00, 8:30, 9:00... 7:30 PM and 8:00 PM. At these preset time points, the interface monitoring module periodically retrieves the target data from the blockchain data area of ​​the blockchain node, thus obtaining the blockchain data.

[0058] Step S130: Compare the cached data with the blockchain data to obtain the comparison result.

[0059] This step can be specifically described as follows: The interface monitoring module compares the acquired cached data with the blockchain data to determine whether they are consistent, thus obtaining the comparison result. When exchanging data, if no problems occur during the transmission through the interface layer module, the comparison result is that the two are consistent; if problems occur during the transmission of the exchanging data through the interface layer module, the comparison result is that the two are inconsistent.

[0060] In one example, after comparing the cached data with the blockchain data and obtaining the comparison result, steps S131-S132 may be included.

[0061] Step S131: When the comparison result shows that the cached data and the blockchain data are consistent, obtain the next cached data and the next blockchain data.

[0062] This step can be specifically described as follows: when the comparison result shows that the cached data is consistent with the blockchain data, it means that there is no need to repair the cached data. The interface monitoring module can continue to obtain the next cached data from the interface layer module and the next blockchain data from the blockchain node, thereby determining whether the next cached data needs to be repaired.

[0063] Step S132: Compare the next cached data with the next blockchain data to determine whether the next cached data needs to be repaired.

[0064] The next cached data is used as the current cached data obtained by the interface monitoring module. The next blockchain data is used as the current blockchain data obtained by the interface monitoring module. The current cached data is compared with the current blockchain data. If the comparison result is consistent, no repair is needed for the current cached data; if the comparison result is inconsistent, the current cached data is repaired based on the current blockchain data.

[0065] Step S140: When the comparison result shows that the cached data and the blockchain data are inconsistent, the cached data is repaired based on the blockchain data.

[0066] This step can be specifically described as follows: When the comparison result shows that the cached data and the blockchain data are inconsistent, it indicates that an anomaly occurred during the data interaction process. The blockchain data needs to repair the cached data to ensure consistency between the two. During the repair process, the cached data can be directly replaced with the blockchain data.

[0067] In one example, repairing cached data based on blockchain data may include steps S1401-S1402.

[0068] Step S1401: Determine the difference between cached data and blockchain data.

[0069] This step can be specifically described as follows: Compare the cached data with the blockchain data to identify the discrepancies between the cached and blockchain data. For example, the cached data includes data A and data B. The blockchain data includes data A, data B, and data C. Then data C is the discrepancy data. Similarly, if data A in the cached data differs from data A in the blockchain data, then data A is the discrepancy data.

[0070] Step S1402: Repair the cached data based on the blockchain data and the distinguishing data.

[0071] This step can be specifically described as follows: After identifying the distinguishing data, repair the cached data based on the blockchain data and the distinguishing data. For example, if the blockchain data contains data A, but the cached data does not contain data A, then data A is identified as the distinguishing data. Data A from the blockchain can be added to the cached data, thus repairing the cached data. If the cached data contains data B, but it differs from data B in the blockchain data, then data B in the cached data can be replaced with data B from the blockchain data, thereby repairing the cached data.

[0072] The data repair method provided in this invention is applied to an interface monitoring module in a business system. The business system further includes an interface layer module and a blockchain node. The interface monitoring module is communicatively connected to both the interface layer module and the blockchain node. Before data interaction occurs in the interface layer module, the interface monitoring module sends the data to be interacted to the blockchain node for storage. When business systems interact with each other through the interface layer module, the interface layer module caches the interaction data. Cached data is obtained by acquiring the interaction data between different business systems cached by the interface layer module. Blockchain data is obtained by acquiring the target data to be interacted by the interface layer module from the blockchain node. The cached data is compared with the blockchain data to obtain a comparison result. When the comparison result shows a discrepancy, the cached data is repaired based on the blockchain data. This method can automatically repair abnormal interaction data, thereby improving the efficiency of interaction data repair.

[0073] To facilitate understanding of the data repair method provided in the embodiments of the present invention, a specific example is described below.

[0074] like Figure 3 As shown, business system A and business system B have completed the development and deployment of traditional interfaces, realizing interface docking. Blockchain nodes have been deployed on business system A and business system B. The blockchain nodes realize the interconnection of P2P networks. The interface network interconnection between business system A and business system B and the blockchain node network interconnection are carried by the same network infrastructure.

[0075] Business system A and business system B begin data interaction due to business needs, temporarily storing the interaction data in the cache of the interface layer module. Business system A and business system B prepare to interact through the interface layer module. The interface monitoring modules of business systems A and B filter the data to be interacted from traditional interfaces, mirror the data from traditional interfaces, and push it to the blockchain node integrated within themselves. The blockchain node records the data to be interacted mirrored by the interface monitoring module as a linked list in the blockchain data area, realizing the on-chain data interaction and achieving full network synchronization of the blockchain through a P2P network.

[0076] Business System A and Business System B interact with each other through an interface layer module. Both systems query their own blockchain tables to compare the interaction data cached in the interface layer module, determining if the interaction data is in a normal state. If the comparison reveals that data successfully sent by Business System A via a traditional interface exists in Business System A's interface layer module and blockchain nodes, but is not present in Business System B's interface layer cache (though present in the blockchain nodes), then the interaction data is determined to be in an abnormal state. Business System B's interface monitoring module automatically retrieves this interaction data from the blockchain nodes and feeds it back to Business System B to fill in or overwrite any missing or incorrect interaction data.

[0077] The comparison results showed that the data successfully sent by business system A through the traditional interface existed in both the interface layer module and blockchain node of business system A, and also in the interface layer module and blockchain node of business system B, confirming that the interactive data was in a normal state. The interface monitoring module continued to monitor the operational status of the interface.

[0078] The data repair method provided in this invention addresses data interaction anomalies between business systems. When an interface malfunctions, data interaction errors occur. Since interface logs cannot fully record the data interaction process, it's impossible to promptly identify and repair these anomalies based on the interface logs. The data repair method provided in this application involves an interface monitoring module sending the data to be interacted to a blockchain node for storage before data interaction occurs between the interface layer modules. When business systems interact through the interface layer modules, these modules cache the interaction data. The interface monitoring module retrieves the cached interaction data and obtains the cached data, and then retrieves the interaction data stored in the blockchain node to obtain the blockchain data. The cached data and blockchain data are compared; if they are inconsistent, the cached data is repaired based on the blockchain data. This method enables automatic repair of abnormal interaction data, thereby improving the efficiency of data repair.

[0079] Based on the same inventive concept, this application also provides a data repair device.

[0080] Figure 4 This application illustrates a data repair apparatus provided in an embodiment, applied to an interface monitoring module in a business system. The business system further includes an interface layer module and a blockchain node; the interface monitoring module is communicatively connected to both the interface layer module and the blockchain node. Figure 4 As shown, the data repair device may include:

[0081] The cached data acquisition module 410 is used to acquire the interaction data between different business systems cached by the interface layer module, and obtain the cached data.

[0082] The blockchain data acquisition module 420 is used to acquire the target data to be interacted with by the interface layer module from the blockchain node, and obtain blockchain data;

[0083] The data comparison module 430 is used to compare the cached data with the blockchain data to obtain a comparison result;

[0084] The data repair module 440 is used to repair the cached data according to the blockchain data when the comparison result shows that the cached data and the blockchain data are inconsistent.

[0085] In some embodiments, the data repair apparatus may include:

[0086] The target data push module is used to push the target data to be interacted with by the interface layer module to the blockchain node for storage.

[0087] In some embodiments, the target data push module includes:

[0088] The data filtering unit is used to filter the data to be interacted with by the interface layer module according to preset rules to obtain target data;

[0089] A data storage unit is used to push the target data to the blockchain node for storage.

[0090] In some embodiments, the blockchain data acquisition module 420 may include:

[0091] The target data quantity acquisition unit is used to acquire the quantity of target data stored in the blockchain node at a preset time point;

[0092] The target data acquisition unit is used to acquire the target data and obtain blockchain data when the amount of target data acquired at the current time point is greater than the amount of target data acquired at the previous time point.

[0093] In some embodiments, the blockchain data acquisition module 420 may include:

[0094] The data acquisition unit is used to acquire the target data at preset time points to obtain blockchain data.

[0095] In some embodiments, the data repair apparatus may include:

[0096] The next data acquisition module is used to acquire the next cached data and the next blockchain data when the comparison result shows that the cached data and the blockchain data are consistent.

[0097] The data repair determination module is used to compare the next cached data and the next blockchain data to determine whether the next cached data needs to be repaired.

[0098] In some embodiments, the data repair module 440 may include:

[0099] A data differentiation determination unit is used to determine the data that differentiates the cached data from the blockchain data.

[0100] A cached data repair unit is used to repair the cached data based on the blockchain data and the difference data.

[0101] The data repair device provided in this application embodiment is applied to an interface monitoring module in a business system. The business system further includes an interface layer module and a blockchain node. The interface monitoring module is communicatively connected to both the interface layer module and the blockchain node. Before data interaction occurs in the interface layer module, the interface monitoring module sends the data to be interacted to the blockchain node for storage. When business systems interact with each other through the interface layer module, the interface layer module caches the interaction data. The cached data acquisition module obtains the interaction data between different business systems cached by the interface layer module, thus obtaining cached data. The blockchain data acquisition module obtains the target data to be interacted by the interface layer module from the blockchain node, thus obtaining blockchain data. The cached data is compared with the blockchain data by the data comparison module, and a comparison result is obtained. When the comparison result shows that the two are inconsistent, the data repair module repairs the cached data based on the blockchain data. This device can automatically repair abnormal interaction data, thereby improving the efficiency of interaction data repair.

[0102] Based on the same inventive concept, embodiments of this application also provide an electronic device.

[0103] Figure 5 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. For example... Figure 5 As shown, the electronic device may include a processor 501 and a memory 502 storing computer programs or instructions.

[0104] Specifically, the processor 501 may include a central processing unit (CPU), an application specific integrated circuit (ASIC), or one or more integrated circuits that can be configured to implement the embodiments of the present invention.

[0105] Memory 502 may include a large-capacity memory for data or instructions. For example, and not limitingly, memory 502 may include a hard disk drive (HDD), a floppy disk drive, flash memory, optical disk, magneto-optical disk, magnetic tape, or a Universal Serial Bus (USB) drive, or a combination of two or more of these. Where appropriate, memory 502 may include removable or non-removable (or fixed) media. Where appropriate, memory 502 may be internal or external to the integrated gateway disaster recovery device. In a particular embodiment, memory 502 is a non-volatile solid-state memory. In a particular embodiment, memory 502 includes read-only memory (ROM). Where appropriate, the ROM may be a mask-programmed ROM, a programmable ROM (PROM), an erasable PROM (EPROM), an electrically erasable PROM (EEPROM), an electrically rewritable ROM (EAROM), or flash memory, or a combination of two or more of these.

[0106] The processor 501 reads and executes computer program instructions stored in the memory 502 to implement any of the base station fault detection methods in the above embodiments.

[0107] In one example, the electronic device may also include a communication interface 503 and a bus 510. Wherein, as... Figure 5 As shown, the processor 501, memory 502, and communication interface 503 are connected through bus 510 and complete communication with each other.

[0108] The communication interface 503 is mainly used to realize communication between various modules, devices, units and / or devices in the embodiments of the present invention.

[0109] Bus 510 includes hardware, software, or both, that couples components of an electronic device together. For example, and not limitingly, the bus may include an Accelerated Graphics Port (AGP) or other graphics bus, an Enhanced Industry Standard Architecture (EISA) bus, a Front Side Bus (FSB), HyperTransport (HT) interconnect, an Industry Standard Architecture (ISA) bus, an Infinite Bandwidth Interconnect, a Low Pin Count (LPC) bus, a memory bus, a Microchannel Architecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, a PCI-Express (PCI-X) bus, a Serial Advanced Technology Attachment (SATA) bus, a Video Electronics Standards Association Local (VLB) bus, or other suitable buses, or combinations of two or more of these. Where appropriate, bus 510 may include one or more buses. Although specific buses are described and illustrated in embodiments of the invention, the invention contemplates any suitable bus or interconnect.

[0110] The electronic device can execute the video bitrate control method in the embodiments of the present invention, thereby achieving... Figure 1 Describe the data repair method.

[0111] Furthermore, in conjunction with the data repair methods described in the above embodiments, this invention can be implemented using a readable storage medium. This readable storage medium stores program instructions; when these program instructions are executed by a processor, they implement any of the data repair methods described in the above embodiments.

[0112] It should be clarified that the present invention is not limited to the specific configurations and processes described above and shown in the figures. For the sake of brevity, detailed descriptions of known methods are omitted here. In the above embodiments, several specific steps are described and shown as examples. However, the method process of the present invention is not limited to the specific steps described and shown. Those skilled in the art can make various changes, modifications, and additions, or change the order of steps, after understanding the spirit of the present invention.

[0113] The functional blocks shown in the above-described structural diagram can be implemented as hardware, software, firmware, or a combination thereof. When implemented in hardware, they can be, for example, electronic circuits, application-specific integrated circuits (ASICs), appropriate firmware, plug-ins, function cards, etc. When implemented in software, the elements of this invention are programs or code segments used to perform the required tasks. The programs or code segments can be stored on a machine-readable medium or transmitted over a transmission medium or communication link via data signals carried in a carrier wave. "Machine-readable medium" can include any medium capable of storing or transmitting information. Examples of machine-readable media include electronic circuits, semiconductor memory devices, ROM, flash memory, erasable ROM (EROM), floppy disks, CD-ROMs, optical disks, hard disks, fiber optic media, radio frequency (RF) links, etc. Code segments can be downloaded via computer networks such as the Internet, intranets, etc.

[0114] It should also be noted that the exemplary embodiments mentioned in this invention describe methods or systems based on a series of steps or apparatus. However, this invention is not limited to the order of the steps described above; that is, the steps can be performed in the order mentioned in the embodiments, or in a different order, or several steps can be performed simultaneously.

[0115] The above description is merely a specific embodiment of the present invention. Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, modules, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here. It should be understood that the protection scope of the present invention is not limited thereto. Any person skilled in the art can easily conceive of various equivalent modifications or substitutions within the technical scope disclosed in the present invention, and these modifications or substitutions should all be covered within the protection scope of the present invention.

Claims

1. A data repair method, characterized in that, An interface monitoring module is applied to a business system, the business system further including: an interface layer module and a blockchain node; the interface monitoring module is communicatively connected to both the interface layer module and the blockchain node; the method includes: The interface layer module retrieves interaction data between different business systems to obtain cached data; the blockchain node retrieves target data to be interacted with by the interface layer module to obtain blockchain data; and the cached data is compared with the blockchain data to obtain a comparison result. When the comparison result shows that the cached data is inconsistent with the blockchain data, the cached data is repaired according to the blockchain data. Before the interface layer module performs data interaction, the interface monitoring module sends the target data to be interacted to the blockchain node and saves the target data to be interacted to the blockchain data area in the blockchain node, thereby realizing data on-chain. The step of obtaining the target data to be interacted with by the interface layer module from the blockchain node to obtain blockchain data includes: The quantity of target data stored in the blockchain node is obtained at a preset time point; The interface monitoring module compares the number of target data points acquired at the current time with the number of target data points acquired at the previous time. If the amount of target data acquired at the current time point is greater than the amount of target data acquired at the previous time point, then acquire the target data to obtain blockchain data, or... The target data is acquired periodically according to preset time points to obtain blockchain data.

2. The method according to claim 1, characterized in that, Before obtaining the cached interaction data from the interface layer module, the method further includes: The target data to be interacted with by the interface layer module is pushed to the blockchain node for storage.

3. The method according to claim 2, characterized in that, The step of pushing the target data to be interacted with by the interface layer module to the blockchain node for storage includes: The data to be interacted with by the interface layer module is filtered according to preset rules to obtain target data; The target data is pushed to the blockchain node for storage.

4. The method according to claim 1, characterized in that, After comparing the cached data with the blockchain data to obtain the comparison result, the method further includes: When the comparison result shows that the cached data is consistent with the blockchain data, obtain the next cached data and the next blockchain data; The next cached data and the next blockchain data are compared to determine whether the next cached data needs to be repaired.

5. The method according to claim 1, characterized in that, Repairing the cached data based on the blockchain data includes: Determine the difference between the cached data and the blockchain data; The cached data is repaired based on the blockchain data and the distinguishing data.

6. A data repair device, characterized in that, An interface monitoring module is applied to a business system, the business system further including an interface layer module and a blockchain node, the interface monitoring module being communicatively connected to both the interface layer module and the blockchain node; the device includes: The cached data acquisition module is used to acquire the interaction data between different business systems cached by the interface layer module, and obtain the cached data. The blockchain data acquisition module is used to obtain the target data to be interacted with by the interface layer module from the blockchain node, and obtain the blockchain data. The cached data and the blockchain data are obtained by the interface monitoring module in an asynchronous manner. The data comparison module is used to compare the cached data with the blockchain data to obtain the comparison result; The data repair module is used to repair the cached data based on the blockchain data when the comparison result shows that the cached data and the blockchain data are inconsistent. The blockchain data acquisition module is also used to acquire the number of target data stored in the blockchain node at a preset time point; the interface monitoring module compares the number of target data acquired at the current time point with the number of target data acquired at the previous time point; when the number of target data acquired at the current time point is greater than the number of target data acquired at the previous time point, the target data is acquired to obtain blockchain data, or the target data is acquired periodically according to the preset time point to obtain blockchain data.

7. An electronic device, characterized in that, It includes a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the data repair method as described in any one of claims 1-5.

8. A computer storage medium, characterized in that, The computer storage medium stores computer program instructions, which, when executed by a processor, implement the data repair method as described in any one of claims 1-5.

Images