Data interaction system and data interaction method

Abstract

The embodiment of the present specification provides a data interaction system and a data interaction method. The data exchange system comprises a master system and at least two slave systems, and the master system is configured with first check information of the at least two slave systems; the master system is configured to read the first check information corresponding to a target slave system and target data; first signature information is generated according to the first check information and the target data; the first signature information and the target data are sent to the target slave system, wherein the target slave system is any one of the at least two slave systems; the target slave system is configured to receive the first signature information and the target data; second signature information is generated based on the target data and second check information, and the target data is processed based on the check result according to the second signature information and the first signature information, wherein the second check information is obtained by reading from the local storage of the target slave system. The system avoids repeated development and reduces the development difficulty.

Description

Technical Field

[0001] The embodiments of this specification relate to the field of data technology, and more particularly to a data interaction system, two data interaction methods, a computing device, and a computer-readable storage medium. Background Art

[0002] Heterogeneous systems often rely on complex and lengthy authentication and authorization processes to exchange data and interact. The logic and implementation of authentication and authorization vary across these systems. For example, common standard authentication methods include those based on JWT tokens, those based on cookies, and even information systems with custom authentication algorithms. Furthermore, the input and output parameters for authentication and authorization vary across systems, making it difficult to generalize. Consequently, information exchange between information systems is challenging and requires significant development time.

[0003] Therefore, a data interaction system is urgently needed to solve this problem. Summary of the Invention

[0004] In view of this, the embodiments of this specification provide a data interaction system. One or more embodiments of this specification also involve two data interaction methods, a computing device, a computer-readable storage medium, and a computer program to solve the technical defects in the prior art.

[0005] According to a first aspect of an embodiment of this specification, a data exchange system is provided, the data exchange system comprising a master system and at least two slave systems, the master system being configured with first verification information of the at least two slave systems;

[0006] The master system is configured to read first verification information and target data corresponding to a target slave system; generate first signature information based on the first verification information and the target data; and send the first signature information and the target data to the target slave system, wherein the target slave system is any one of the at least two slave systems;

[0007] The target slave system is configured to receive the first signature information and the target data; generate second signature information based on the target data and second verification information, perform verification based on the second signature information and the first signature information, and process the target data based on the verification result, wherein the second verification information is obtained by the target slave system reading from local storage.

[0008] In one or more embodiments of the present disclosure, the main system further includes a configuration module.

[0009] The configuration module is configured to receive a registration instruction for the slave system, register the slave system according to the registration instruction, determine first verification information corresponding to the slave system, and store the first verification information corresponding to the slave system.

[0010] In one or more embodiments of the present disclosure, the master system further comprises a caller,

[0011] The caller is configured to receive a system docking instruction, and target a slave system from the at least two slave systems according to the docking instruction.

[0012] In one or more embodiments of the present disclosure, the master system further comprises a data storage module and a configuration module.

[0013] The reading of the target data from the data storage module and the first verification information of the target slave system from the configuration module comprises:

[0014] The reading of the target data from the data storage module and the first verification information of the target slave system from the configuration module comprises:

[0015] The reading of the target data from the data storage module and the first verification information of the target slave system from the configuration module comprises:

[0016] In one or more embodiments of the present disclosure, the generation of the first signature information according to the first verification information and the target data comprises:

[0017] The encryption of the target data according to a preset encryption algorithm;

[0018] The digital signature operation on the first verification information and the encrypted target data to obtain the first signature information.

[0019] In one or more embodiments of the present disclosure, the digital signature operation on the first verification information and the encrypted target data comprises:

[0020] The processing of the first verification information and the target data by a hash function to generate a digital digest corresponding to the target data;

[0021] The encryption operation on the digital digest by a private key to generate the first signature information.

[0022] In one or more embodiments of the present disclosure, the generation of the verification result according to the second signature information and the first signature information comprises:

[0023] The comparison of the first signature information and the second signature information to determine whether they are consistent;

[0024] If consistent, the verification result is determined to be successful;

[0025] If not consistent, the verification result is determined to be failed.

[0026] In one or more embodiments of the present disclosure, the responding to the data processing request based on the verification result comprises:

[0027] If the verification result is success, the target data is stored to a corresponding storage space to execute specific task logic.

[0028] If the verification result is failure, a corresponding failure processing strategy is taken to process the target data.

[0029] In one or more embodiments of the present disclosure, the master system is configured with address information of the at least two slave systems.

[0030] The master system is further configured to read the address information corresponding to the target slave system, and send the data processing request to the target slave system corresponding to the address information.

[0031] According to a second aspect of the embodiments of the present disclosure, a data interaction method is provided, applied to a master system of a data interaction system, comprising:

[0032] reading first verification information and target data corresponding to a target slave system;

[0033] generating first signature information according to the first verification information and the target data;

[0034] sending the first signature information and the target data to the target slave system, wherein the target slave system is any one of the at least two slave systems, and the first signature information and the target data are used to verify whether the target slave system is a slave system connected to the master system.

[0035] According to a third aspect of the embodiments of the present disclosure, a data interaction method is provided, applied to a slave system of a data interaction system, comprising:

[0036] receiving the first signature information and the target data, wherein the first signature information is generated according to the first verification information and the target data;

[0037] generating second signature information based on the target data and second verification information, and performing verification according to the second signature information and the first signature information;

[0038] processing the target data based on the verification result, wherein the second verification information is obtained by reading from a local storage of the target slave system.

[0039] According to a fourth aspect of the embodiments of the present disclosure, a computing device is provided, comprising:

[0040] The memory and the processor;

[0041] The memory is configured to store computer executable instructions, and the processor is configured to execute the computer executable instructions, and the computer executable instructions, when executed by the processor, implement the steps of the two data interaction methods.

[0042] According to a fourth aspect of an embodiment of the present specification, a computer readable storage medium is provided, which stores computer executable instructions, and the instructions, when executed by a processor, implement the steps of the two data interaction methods.

[0043] According to a fifth aspect of an embodiment of the present specification, a computer program is provided, and when the computer program is executed in a computer, the computer program causes the computer to execute the steps of the data interaction method.

[0044] The master system in the data interaction system of one embodiment of the present specification can configure the verification information of the plurality of slave systems, when the target data interested by the slave system is needed, the master system reads the first verification information corresponding to the slave system and the target data, generates the first signature information according to the first verification information and the target data, and sends the first signature information and the target data to the corresponding slave system, the slave system generates the second signature information according to the second verification information stored locally and the target data received, and performs verification according to the first signature information and the second signature information to determine whether the successful interaction of the data is completed. The system not only realizes the verification of the validity of the data, but also ensures that the master system sending the data and the slave system receiving the data are both systems for docking with each other, realizes the docking of the master system with different slave systems, avoids repeated development and repeated authentication and authorization processes with a plurality of slave systems, and reduces the development difficulty. BRIEF DESCRIPTION OF DRAWINGS

[0045] Figure 1 is a system structure schematic diagram of a data interaction system provided by one embodiment of the present specification;

[0046] Figure 2 is a system structure schematic diagram of another data interaction system provided by one embodiment of the present specification;

[0047] Figure 3 is a processing process flowchart of a data interaction method provided by one embodiment of the present specification;

[0048] Figure 4 is a processing process flowchart of another data interaction method provided by one embodiment of the present specification;

[0049] Figure 5 is a structure block diagram of a computing device provided by one embodiment of the present specification. DETAILED DESCRIPTION

[0050] In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present description. However, the present description can be practiced without the specific details. In other instances, well-known methods, procedures, components, and circuits have not been described in detail so as not to obscure the present description. The present description can be practiced with the specific details presented.

[0051] The terminology used in this description is for the purpose of describing particular embodiments only and is not intended to be limiting of one or more embodiments of the present description. As used in this description and the appended claims, the singular forms "a," "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term "and / or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.

[0052] It will be understood that, although the terms first, second, etc. can be used herein to describe various information, these terms are not intended to denote a temporal or chronological order. Rather, these terms are used solely to distinguish one from another only. For example, a first item could be termed a second item, and, similarly, a second item could be termed a first item without departing from the scope of one or more embodiments of the present description. As used herein, the term "if' can be construed to mean "when" or "upon" or "in response to determining" terms that indicate a logical relationship between an act and a condition or an event.

[0053] In addition, it should be noted that the user information (including but not limited to user equipment information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, displayed data, etc.) involved in one or more embodiments of the present description are all information and data authorized by the user or authorized by all parties, and the collection, use and processing of relevant data need to comply with relevant laws, regulations and standards of relevant countries and regions, and provide corresponding operation portal for user to choose authorization or refusal.

[0054] Data exchange and interaction between heterogeneous systems usually requires a series of complex and time-consuming authentication and authorization processes to ensure the security and correctness of data, due to the differences in design philosophy, architecture, standards and security mechanisms of each system. The authentication logic between different systems may involve different identity recognition technologies, such as traditional authentication based on username / password, or identity verification based on certificates, biometrics, or JWT Token, or based on Cookie; the authorization process is also different, which may implement access control of resources according to role permission model, access control list, etc. Therefore, to efficiently and securely implement data exchange between heterogeneous systems, it is often necessary to design and develop unified standard interfaces, protocols, or use middleware, API gateway and other technical means to adapt and convert various authentication and authorization methods to overcome the interoperability challenges caused by system differences.

[0055] However, the input and output parameters of the above-mentioned unified standard interface, protocol, or middleware, API gateway technical means are not the same, and a lot of time and effort is needed for design and development. And every time a new system needs to be connected, repeated development is needed.

[0056] For example: system A is the main system, whenever a system (such as system B) wants to get some data information it is interested in from system A, system B needs to design and develop an interface to receive data and provide it to A, system A uses the interface developed by system B to push data information to system B, at this time, system A and system B both need to develop code. And system A also needs to perform complex authentication and authorization with system B to ensure that the data they pass to each other is trustworthy, and the above-mentioned developed interface and authentication and authorization process can only be limited to system A and system B, if there is a new system C that wants to be connected to system A, it needs to develop a new system C for connection again.

[0057] Therefore, the data interaction system provided by the embodiments of the present specification pre-configures the related information of at least two slave systems in the master system in advance, and actively pushes data to the corresponding slave system according to the information, and the slave system verifies it, thereby realizing the connection of the master system and different slave systems, avoiding repeated development and repeated authentication and authorization processes with multiple slave systems, and reducing the development difficulty.

[0058] In the present specification, a data interaction system is provided, the present specification also relates to two data interaction methods, a computing device, and a computer readable storage medium, which are described in detail one by one in the following embodiments.

[0059] Reference is made to Figure 1 , Figure 1A system structure schematic diagram of a data interaction system according to one embodiment of the present specification is shown.

[0060] Figure 1 The data interaction system 100 comprises a master system 102 and at least two slave systems 104, wherein the master system 102 is configured with first verification information of the at least two slave systems 104;

[0061] Specifically, the master system 102 is configured to read the first verification information and target data corresponding to a target slave system 104; generate first signature information according to the first verification information and the target data; and send the first signature information and the target data to the target slave system 104, wherein the target slave system 104 is any one of the at least two slave systems 104.

[0062] The target slave system 104 is configured to receive the first signature information and the target data; generate second signature information based on the target data and second verification information, and perform verification according to the second signature information and the first signature information, and process the target data based on the verification result, wherein the second verification information is obtained by reading from a local storage of the target slave system 104.

[0063] The master system 102 can be understood as a system for pushing data, which is a data provider. The master system is used to push data by providing a data interface to a slave system having relevant information, and pushing target data and first signature information to the corresponding slave system through the interface.

[0064] The slave system 104 can be understood as a system for receiving data, which is a data receiver. The slave system 104 receives target data and first signature information from the master system 102, generates second signature information according to the target data and second verification information stored in the local storage of the slave system, and then verifies the first signature information using the second signature information to verify the authenticity between the two systems. In specific implementation, the slave system 104 can be any number of subsystems, and the target slave system can be one or more. That is, the master system can push data to one target slave system or multiple target slave systems, and the type of data can be set according to the demand of the target slave system.

[0065] Further, the master system further comprises a configuration module;

[0066] Specifically, the configuration module is configured to receive a registration instruction for a slave system; register the slave system according to the registration instruction, determine the first verification information corresponding to the slave system; and store the first verification information corresponding to the slave system.

[0067] The configuration module is a key component in the data interaction system, and its main responsibility is to manage and maintain various subsystems in the system, including registration, verification, and storage of relevant information.

[0068] In practical applications, the configuration module can provide an interface for receiving user instructions for registering other slave systems. These instructions usually include basic information about the slave system, such as system ID, name, type, address information, function description, or first verification information, to identify and describe the slave system applying for registration. After receiving the registration instruction, the configuration module will follow the pre-set registration process to register the slave system. This process may include a preliminary legality check of the submitted information, such as confirming the uniqueness of the system ID and checking the validity of the address.

[0069] During the registration process, the configuration module generates or obtains the first verification information associated with the slave system. This verification information may be a unique identifier or hash value generated based on certain characteristics of the slave system, or it may be some form of identification or key information provided by the slave system during the registration process, or it may be a session coordination text pre-coordinated by the user during the registration process for subsequent identity verification and data security protection.

[0070] After the generation or confirmation of the verification information, the configuration module saves this information in the local database or other storage medium, associated with other basic information of the slave system. In this way, during subsequent communication or interaction, the master system can quickly obtain the verification information of the slave system by querying the configuration module, and then perform identity verification, permission allocation, data encryption and decryption, etc., to ensure the security and accuracy of data exchange within the entire system.

[0071] In summary, the configuration module plays a core role in managing slave systems in the data interaction system. By receiving and processing registration instructions, generating and storing verification information, it achieves standardized management and security control of multiple slave systems.

[0072] Further, the master system further comprises a caller;

[0073] Specifically, the caller is configured to receive a system docking instruction and target a slave system from the at least two slave systems according to the system docking instruction.

[0074] The caller plays a role in coordinating and scheduling the functions of different slave systems in the master system. The caller listens to and receives docking instructions from the master system or other components. The system docking instruction can be triggered by the user or triggered by the master system when it receives external notifications or messages. The docking instruction at least contains the information of the slave system that needs to interact with the master system or the data exchange requirement.

[0075] According to the content of the system docking instruction, the invoker determines one of the at least two candidate slave systems as a target slave system for the current data interaction according to the information of the slave system in the system docking instruction, based on the slave system identifier (such as an ID, a name, or an IP address of the slave system) specified in the docking instruction.

[0076] In addition, after determining the target slave system, the invoker can also read the first verification information corresponding to the target slave system and the target data, generate first signature information according to the first verification information and the target data, and send the first signature information and the target data to the target slave system, wherein the target slave system is any one of the at least two slave systems, so as to ensure that the interaction between the master system and the target slave system proceeds smoothly.

[0077] In combination with the function of the configuration module, we can understand that the master system uses the configuration module to register and manage the information of the slave system, and the invoker dynamically docks with the slave system and performs specific data interaction according to the information, and the two together constitute the basic structure of the master system to flexibly and efficiently interact with multiple slave systems.

[0078] Further, the master system further comprises a data storage module,

[0079] Specifically, the reading of the first verification information corresponding to the target slave system and the target data comprises:

[0080] reading the target data from the data storage module;

[0081] reading the first verification information from the configuration module.

[0082] The data storage module stores the target data, and in the master system, the data storage module is responsible for persistently storing the data received or generated from each slave system. When the data interested by the target slave system needs to be read, the master system reads the data storage module, retrieves and reads the target data from the data storage module according to the data required by the target slave system included in the pre-configured information or the registration information. Of course, in addition to obtaining the target data from the data storage module, the target data can also be obtained from other nodes, and the target data can be an event, a message, or other content interested by the slave system, which is not limited in the present application. Different business systems will have different business logics, and those skilled in the art can determine according to the actual business needs.

[0083] The configuration module stores the registration information of each slave system, including the first verification information corresponding to each slave system, such as the session coordination text coordinated with the slave system, and the like, which are used to verify the data source and integrity. While reading the target slave system data from the data storage module, the master system reads the pre-archived first verification information corresponding to the target slave system from the configuration module.

[0084] When the master system performs data interaction, it takes out the target data from the data storage module and obtains the verification information from the configuration module. The authenticity and integrity of the read target data are verified through the verification information, thereby ensuring the safety and reliability of data exchange between the master system and other slave systems.

[0085] Further, the master system is configured with address information of the at least two slave systems;

[0086] The master system is further configured to read the address information corresponding to the target slave system and send the data processing request to the target slave system corresponding to the address information.

[0087] The address information can be stored in the configuration module of the master system, and the registration instruction can contain the address information of the slave system, and the address information is stored corresponding to the slave system.

[0088] Further, the first signature information is generated according to the first verification information and the target data, including:

[0089] The target data is encrypted according to a preset encryption algorithm; the first verification information and the encrypted target data are digitally signed to obtain the first signature information.

[0090] Specifically, the target data is encrypted using a preset encryption algorithm, which is usually to ensure the privacy and security of the data. The encryption process can use symmetric encryption, asymmetric encryption or hash function technology to ensure that even if the data is intercepted during transmission, its original content cannot be easily read.

[0091] After completing the encryption of the target data, the encrypted target data is combined with the first verification information. Then, a digital signature operation is performed using a specific entity (such as the private key of the master system).

[0092] This operation usually involves calculating a one-way hash function on a specific value that combines the first verification information and the encrypted target data, and then encrypting the hash value using the private key to finally generate a non-forgery first signature information.

[0093] Further, the digital signature operation on the first verification information and the encrypted target data includes:

[0094] The first verification information and the target data are processed by using a hash function to generate a digital digest corresponding to the target data; and the digital digest is encrypted by using a private key to generate first signature information.

[0095] The first signature information not only contains a proof of the integrity of the target data, but also can verify the identity of the signer through the public key system, ensuring the integrity and non-repudiation of the data in the transmission and storage process. In the subsequent verification phase, the receiver can decrypt the signature and check the original data in the same way to confirm that the data has not been tampered with and indeed comes from the claimed sender, i.e., the main system.

[0096] Further, the generating of the verification result according to the second signature information and the first signature information comprises:

[0097] Comparing whether the first signature information and the second signature information are consistent; if consistent, determining that the verification result is successful; if inconsistent, determining that the verification result is failed.

[0098] Among them, the signature information is obtained: two signature information to be verified, i.e., the first signature information and the second signature information, are obtained. The two signature information generally correspond to the same target data or the same set of processed target data, and are generated by signing the data through the same digital signature operation.

[0099] The signature is compared: the first signature information and the second signature information are compared bit by bit or as a whole to determine whether they are exactly the same. This step is the core verification link, because if the signature is generated by a trusted source according to the same algorithm and key for the same data, they should be exactly the same in theory.

[0100] The verification result is determined: if it is found that the first signature information and the second signature information are exactly the same after comparison, it means that no change has occurred in the process from data generation to signature, so the verification result can be determined to be successful, which means that the integrity of the data is effectively verified, and the identity of the data source is also trusted. If the first signature information and the second signature information are inconsistent, it means that the target data has been changed in the transmission process, or the signature process has a problem, such as using a different private key or other security mechanisms failing. In this case, the verification result will be determined to be failed, which means that the integrity and / or authenticity of the data cannot be guaranteed.

[0101] Therefore, the responding to the data processing request based on the verification result comprises:

[0102] If the verification result is successful, the target data is stored in the corresponding storage space to execute specific task logic;

[0103] If the verification result is failure, the corresponding failure handling strategy is taken to handle the target data.

[0104] The response mechanism based on the above verification result is as follows:

[0105] Verification success response: When the verification result shows success, it means that the target data has not been tampered with during transmission, and its integrity and source are effectively confirmed. At this time, the system will perform the operation of safely storing the target data to the corresponding storage space set in advance and execute specific task logic. This operation may involve database writing, file system saving, cloud storage uploading, etc. specific implementation methods, to ensure that the data can be saved for a long time and remain in its original state in subsequent use. After storage is completed, the target data can be calculated, such as displaying the target data, or calculating the target data to obtain a calculation result and displaying the calculation result, or analyzing the target data to generate a visual table, etc.

[0106] Verification failure response: If the verification result shows failure, it indicates that the target data may have been tampered with, forged signature, or untrusted source, etc. In this case, the system will take appropriate failure handling strategies. These strategies may include but are not limited to:

[0107] Reject storage: directly discard or ignore the target data, do not store it in the formal storage space, to prevent false or malicious data from polluting the entire data set.

[0108] Record exception: record the event of verification failure in the log for later analysis and audit.

[0109] Alarm notification: trigger the alarm system to notify relevant operation and maintenance personnel or security team to promptly investigate the source and cause of the problem.

[0110] Backup and isolation: in necessary cases, the problematic target data may be backed up (for investigation and evidence) first, and then isolated to avoid affecting other normal business processes.

[0111] Retry or repair: if the verification failure is caused by temporary error, the system may also try to reacquire the target data with correct signature, or require the data sender to resend the data verified to be correct.

[0112] In summary, the main system in the data interaction system can configure the check information of multiple slave systems. When target data of interest of a slave system is needed, the main system reads the first check information and the target data corresponding to the slave system, generates first signature information according to the first check information and the target data, and sends the first signature information and the target data to the corresponding slave system. The slave system generates second signature information according to the locally stored second check information and the received target data, and performs check according to the first signature information and the second signature information to determine whether the successful interaction of data is completed. Through the system, not only the validity of the data is verified, but also it is ensured that the main system sending data and the slave system receiving data are both systems of mutual connection, the main system is connected with different slave systems, repeated development and repeated authentication and authorization process with multiple slave systems are avoided, and the development difficulty is reduced.

[0113] Figure 2 A system structure schematic diagram of another data interaction system provided by one embodiment of the present specification is shown.

[0114] Figure 2 The data interaction system 200 includes a main system 210 and at least two slave systems 220, wherein the main system 210 is configured with first check information of the at least two slave systems 220; the main system 210 further includes a caller 212, a data storage module 216, a configuration module 214, and the slave system 220 includes a request processor 222 and a storage space 224.

[0115] Specifically, the caller 212 is configured to read the first check information corresponding to the target slave system 220 and the address information corresponding to the target slave system 220 from the configuration module 214; read the target data from the data storage module 216; generate first signature information according to the target data and the first check information; and send the first signature information and the target data to the target slave system 220 corresponding to the address information.

[0116] The request processor 222 is configured to receive the first signature information and the target data sent by the caller 212, generate second signature information based on the target data and the second check information, and perform check according to the second signature information and the first signature information. If the check is successful, the target data is stored in the corresponding storage space 224; if the check fails, the target data is processed by a corresponding failure processing strategy.

[0117] The above is a schematic scheme of another data interaction system of the embodiment. It should be noted that the technical scheme of the data interaction system belongs to the same concept as the technical scheme of the data interaction system described above, and the details of the technical scheme of the data interaction system that are not described in detail can be seen from the description of the technical scheme of the data interaction system described above. The present application will not be repeated here.

[0118] Referring to Figure 3 , Figure 3 A processing process flowchart of a data interaction method according to an embodiment of the present specification is shown.

[0119] Specifically, the data interaction method is applied to a master system of a data interaction system, and includes:

[0120] Step 302: reading first verification information corresponding to a target slave system and target data.

[0121] Step 304: generating first signature information according to the first verification information and the target data.

[0122] Step 306: sending the first signature information and the target data to the target slave system, wherein the target slave system is any one of the at least two slave systems, and the first signature information and the target data are used to verify whether the target slave system is a slave system docked with the master system.

[0123] The above is a schematic scheme of a data interaction method of the embodiment. It should be noted that the technical scheme of the data interaction method belongs to the same concept as the technical scheme of the data interaction system described above, and the details of the technical scheme of the data interaction method that are not described in detail can be seen from the description of the technical scheme of the data interaction system described above. The present application will not be repeated here.

[0124] Referring to Figure 4 , Figure 4 A processing process flowchart of another data interaction method according to an embodiment of the present specification is shown.

[0125] Specifically, the data interaction method is applied to a slave system of a data interaction system, and includes:

[0126] Step 402: receiving the first signature information and the target data, wherein the first signature information is generated according to the first verification information and the target data.

[0127] Step 404: generating second signature information based on the target data and second verification information, and verifying according to the second signature information and the first signature information.

[0128] Step 406: processing the target data based on the check result, wherein the second check information is obtained by reading from a local storage.

[0129] The above is a schematic scheme of the data interaction method of the embodiment. It should be noted that the technical scheme of the data interaction method and the technical scheme of the data interaction system described above belong to the same concept. The details of the technical scheme of the data interaction method that are not described in detail can be referred to the description of the technical scheme of the data interaction system. The present application will not be repeated here.

[0130] Figure 5 A structural block diagram of a computing device 500 according to one embodiment of the present specification is shown. The components of the computing device 500 include but are not limited to a memory 510 and a processor 520. The processor 520 is connected to the memory 510 through a bus 530, and a database 550 is used to save data.

[0131] The computing device 500 also includes an access device 540, which enables the computing device 500 to communicate via one or more networks 560. Examples of these networks include a public switched telephone network (PSTN), a local area network (LAN), a wide area network (WAN), a personal area network (PAN), or a combination of communication networks such as the Internet. The access device 540 can include one or more of any type of network interface (e.g., a network interface card (NIC)), such as an IEEE 802.11 wireless local area network (WLAN) wireless interface, a worldwide interoperability for microwave access (Wi-MAX) interface, an Ethernet interface, a universal serial bus (USB) interface, a cellular network interface, a Bluetooth interface, near field communication (NFC).

[0132] In one embodiment of the present specification, the above-mentioned components of the computing device 500 and other components not shown in the Figure 5 components can be connected to each other, for example, through a bus. It should be understood that Figure 5The illustrated computing device architecture diagram is merely for the purpose of example, and is not a limitation on the scope of the present specification. Other components can be added or replaced as needed by those skilled in the art.

[0133] The computing device 500 can be any type of stationary or mobile computing device, including a mobile computer or mobile computing device (e.g., a tablet computer, a personal digital assistant, a laptop computer, a notebook computer, a netbook, etc.), a mobile phone (e.g., a smartphone), a wearable computing device (e.g., a smart watch, smart glasses, etc.), or other type of mobile device, or a stationary computing device such as a desktop computer or a personal computer (PC). The computing device 500 can also be a mobile or stationary server.

[0134] The processor 520 is configured to execute computer-executable instructions, which, when executed by the processor, implement the steps of the data interaction method described above.

[0135] The above is a schematic scheme of the computing device of the embodiment. It should be noted that the technical scheme of the computing device and the technical scheme of the data interaction method described above belong to the same concept, and the details of the technical scheme of the computing device that are not described in detail can be referred to the description of the technical scheme of the data interaction method.

[0136] An embodiment of the present specification also provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, implement the steps of the data interaction method described above.

[0137] The above is a schematic scheme of the computer-readable storage medium of the embodiment. It should be noted that the technical scheme of the storage medium and the technical scheme of the data interaction method described above belong to the same concept, and the details of the technical scheme of the storage medium that are not described in detail can be referred to the description of the technical scheme of the data interaction method.

[0138] An embodiment of the present specification also provides a computer program, which, when executed in a computer, causes the computer to perform the steps of the data interaction method described above.

[0139] The above is a schematic scheme of the computer program of the embodiment. It should be noted that the technical scheme of the computer program and the technical scheme of the data interaction method described above belong to the same concept, and the details of the technical scheme of the computer program that are not described in detail can be referred to the description of the technical scheme of the data interaction method.

[0140] The above-described embodiments of the application have several aspects, no single one of which is solely responsible for the application's desirable attributes. Without limiting the scope of the application as expressed by the claims which follow, some further embodiments make these aspects even more useful. Other embodiments can result in less desirable attributes.

[0141] The computer readable medium can include any entity or apparatus capable of carrying the computer program code, recording medium, U disk, mobile hard disk, magnetic disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electrical carrier signal, telecommunication signal, software distribution medium, etc. It should be noted that the computer readable medium can include appropriate contents according to the requirements of patent practice, for example, according to the patent practice in some regions, the computer readable medium does not include electrical carrier signals and telecommunication signals.

[0142] It should be noted that for the foregoing method embodiments, the purposes of brief description are to express them as a combination of a series of acts, but those skilled in the art should know that the embodiments of the present specification are not limited by the order of the described acts, because according to the embodiments of the present specification, some steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should know that the embodiments described in the specification are all preferred embodiments, and the acts and modules involved are not necessarily all the embodiments of the present specification.

[0143] In the above embodiments, the description of each embodiment has its own focus, and the parts not described in detail in a certain embodiment can be referred to the related description of other embodiments.

[0144] The preferred embodiments of the present specification disclosed above are only used to help explain the present specification. The alternative embodiments do not describe all the details and limit the application to the specific embodiments described. Obviously, according to the content of the embodiments of the present specification, many modifications and changes can be made. The present specification selects and specifically describes these embodiments in order to better explain the principles and practical applications of the embodiments of the present specification, so that those skilled in the art can well understand and use the present specification. The present specification is limited by the claims and their entire scope and equivalents.

Claims

1. A data interaction system, characterized in that: The data interaction system includes a master system in a heterogeneous system and at least two slave systems in the heterogeneous system. The master system is configured with first verification information of the at least two slave systems. The master system includes a caller and a configuration module. The master system is a system that pushes data and is a data provider. The slave system includes a request processor and is a system that receives data and is a data receiver. The caller is configured to receive a system docking instruction and select one of the at least two slave systems as a target slave system according to the docking instruction; The master system is further configured to receive a registration instruction of the slave system through the configuration module, the registration instruction including first verification information of the slave system; register the slave system according to the registration instruction and save the first verification information; The master system is configured to use the caller to read the first verification information and target data corresponding to the target slave system; generating first signature information according to the first verification information and the target data; Sending the first signature information and the target data to the target slave system, wherein the target slave system is any one of the at least two slave systems; The target slave system is configured to receive the first signature information and the target data using the request processor; generate second signature information based on the target data and second verification information, and perform verification based on the second signature information and the first signature information, determine the docking result between the master system and the target slave system based on the verification result, and process the target data, wherein the second verification information is obtained by the target slave system reading from local storage, and the request processor is deployed in the slave system.

2. The data interaction system according to claim 1, characterized in that: The main system also includes a data storage module and a configuration module. The reading of the first verification information and target data corresponding to the target slave system includes: Read the target data from the data storage module; The first verification information is read from the configuration module.

3. The data interaction system according to claim 1, characterized in that: The generating first signature information according to the first verification information and the target data includes: Encrypting the target data according to a preset encryption algorithm; A digital signature operation is performed on the first verification information and the encrypted target data to obtain first signature information.

4. The data interaction system according to claim 3, characterized in that: The performing a digital signature operation on the first verification information and the encrypted target data includes: Processing the first verification information and target data using a hash function to generate a digital digest corresponding to the target data; The digital summary is encrypted using a private key to generate first signature information.

5. The data interaction system according to claim 1, characterized in that: The verifying according to the second signature information and the first signature information includes: Comparing the first signature information and the second signature information to see if they are consistent; If they are consistent, the verification result is determined to be successful; If they are inconsistent, the verification result is determined to be failed.

6. The data interaction system according to claim 5, characterized in that: The processing of the target data based on the verification result includes: If the verification result is successful, the target data is stored in the corresponding storage space and specific business logic is executed; If the verification result is failure, a corresponding failure processing strategy is adopted to process the target data.

7. A data interaction method, applied to a master system and a slave system in a heterogeneous data interaction system, wherein the master system is configured with first verification information of at least two slave systems, includes a caller and a configuration module, and the slave system includes a request processor. The slave system is the system that receives data and is the data receiver, and the master system is the system that pushes data and is the data provider. The method is characterized in that: include: The caller is configured to receive a system docking instruction and select one of the at least two slave systems as a target slave system according to the docking instruction; receiving, through a configuration module, a registration instruction of a slave system, wherein the registration instruction includes first verification information of the slave system; registering the slave system according to the registration instruction and saving the first verification information; Using the caller to read the first verification information and target data corresponding to the target slave system; generating first signature information according to the first verification information and the target data; Sending the first signature information and the target data to the target slave system, wherein the target slave system is any one of the at least two slave systems, and the first signature information and the target data are used to verify whether the target slave system is a slave system to be docked with the master system, thereby achieving docking between the master system and the target slave system; The target slave system utilizes a request processor to receive the first signature information and the target data, wherein the first signature information is generated based on the first verification information and the target data; Generate second signature information based on the target data and the second verification information, and perform verification based on the second signature information and the first signature information; The docking result between the master system and the target slave system is determined based on the verification result, and the target data is processed, wherein the second verification information is obtained by the target slave system reading from local storage.

8. A computing device, characterized in that include: memory and processor; The memory is used to store computer-executable instructions, and the processor is used to execute the computer-executable instructions. When the computer-executable instructions are executed by the processor, the steps of the data interaction method according to claim 7 are implemented.

9. A computer-readable storage medium, characterized in that It stores computer-executable instructions, which, when executed by a processor, implement the steps of the data interaction method according to claim 7.

Images