Highly reliable and traceable asynchronous data communication methods, devices and equipment
By employing a highly reliable and traceable asynchronous data communication method within the enterprise's internal LAN, the reliability and traceability issues of data interaction between systems were resolved, enabling reliable data transmission and traceability, reducing inter-system dependencies, and improving data transmission success rate and system availability.
Patent Information
- Application Number
- CN202611464834.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-09-20
- Publication Date
- 2026-11-17
AI Technical Summary
Within an enterprise's internal LAN, data traceability and highly reliable delivery cannot be guaranteed during inter-system data exchange, especially when business operations are disrupted and data cannot be directly resent.
This paper provides a highly reliable and traceable asynchronous data communication method. It receives and configures business data status through a data interaction system, generates a sending strategy, and pushes and resends data based on the number of target applications and registration information. It combines multi-node distributed deployment and Keepalive+Nginx technology to achieve hot switching, ensuring reliable data transmission and traceability.
It improves the reliability and traceability of data interaction between application systems, reduces dependence on the MQ system, and enhances system availability and data transmission success rate.
Smart Images

Figure CN123123416A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of information system office technology, and more specifically, to a highly reliable and traceable asynchronous data communication method, apparatus, and equipment. Background Technology
[0002] Within an enterprise's internal LAN, there are typically numerous independently deployed application systems, which often have business interactions and overlaps. When using open-source technologies or commercial products for data exchange between systems, it is often impossible to ensure data traceability and highly reliable delivery. In the event of an anomaly in the business process, data cannot be directly resent. Summary of the Invention
[0003] To address at least one deficiency or improvement need in existing technologies, this invention discloses a highly reliable application data interaction method involving data interaction between multiple information systems, including methods for application registration, data communication, data storage and forwarding, distribution, and resending. It can be widely applied to data interaction between application systems, solving the pain points of application data communication's strong dependence on the MQ system and synchronous / asynchronous communication relying on the application itself to maintain high reliability.
[0004] To achieve the above objectives, according to a first aspect of the present invention, a highly reliable and traceable asynchronous data communication method is provided, comprising: S01, the first application pushes business data and the target application's identification information to the data interaction system; S02, the interactive system receives the service data and configures the status of the service data to a first status; based on the identification information of the target application, it obtains the quantity information and registration information of the target application, and generates a first sending strategy for the service data based on the quantity information and registration information of the target application; S03, the interactive system pushes the service data to the target application based on the first sending strategy, and modifies the status of the service data to the second status according to the push result; S04, the interactive system retransmits the service data according to the second transmission strategy and the second state of the service data.
[0005] Furthermore, step S02 also includes: The interactive system obtains the number of target applications and their registration information based on the identification information of the target application. If the number of target applications is one and the registration information of the target application is "registered", then the first sending strategy of the generated business data is to push the business data to the target application. If there are multiple target applications, and all target applications are registered, then the first sending strategy for the generated business data is to push the business data to each target application. If there are multiple target applications, and the registration information of the target applications is incomplete, then the first sending strategy for the generated business data is to push the business data to the registered target applications.
[0006] Furthermore, the step of pushing the business data to each of the target applications also includes: The interactive system, based on a preset third sending strategy, pushes the business data to each of the target applications, or splits the business data and pushes the split data fragments to the corresponding target applications.
[0007] Furthermore, the step of pushing the business data to the registered target application also includes: The interactive system, based on a preset fourth sending strategy, pushes the service data to each registered target application; or, it splits the service data and pushes the split data fragments to the corresponding registered target applications; or, it splits the service data, wherein each target application corresponds to one data fragment, and periodically obtains the registration status of each target application and pushes the split data fragments to the corresponding registered target applications.
[0008] Furthermore, steps S03 and S04 also include: The business data is pushed to the target application. If the push is successful, the status of the business data is changed to finish. If the push fails, the status of the business data is changed to fail. The interactive system, following the second sending strategy, periodically and automatically retry sending service data with a data status of "fail" to the target application; after the number of attempts exceeds the limit, it will no longer retry.
[0009] Furthermore, it also includes: Users can perform a resend operation on the interactive system based on the status of the business data, manually pushing business data of any data status to the target application.
[0010] Furthermore, it also includes: The target application registers itself in the interactive system, and the registration information includes: a unique application identifier, an application service address, and a token for accessing the service.
[0011] According to a second aspect of the present invention, a highly reliable and traceable asynchronous data communication device is also provided, comprising: The business data push module is configured to push business data and the target application's identification information to the data interaction system from the first application. A business data receiving module is configured to receive the business data from the interactive system and configure the state of the business data as a first state; obtain the quantity information and registration information of the target application based on the identification information of the target application, and generate a first sending strategy for the business data based on the quantity information and registration information of the target application. The business data forwarding module is configured such that the interactive system pushes the business data to the target application based on the first sending strategy, and modifies the status of the business data to a second status according to the push result; The service data retransmission module is configured to allow the interactive system to retransmit the service data according to the second transmission strategy and the second state of the service data.
[0012] According to a third aspect of the present invention, a highly reliable and traceable asynchronous data communication device is also provided, comprising at least one processing unit and at least one storage unit, wherein the storage unit stores a computer program that, when executed by the processing unit, causes the processing unit to perform the steps of any of the methods described above.
[0013] According to a fourth aspect of the present invention, a computer program product is also provided, comprising a computer program / instructions, characterized in that, when the computer program / instructions are executed by a processor, they implement the steps of any of the methods described above.
[0014] In summary, compared with existing technologies, the technical solutions conceived in this invention achieve the following beneficial effects: The highly reliable and traceable asynchronous data communication method of this invention can be widely applied to data interaction between application systems, reducing the dependence of application data communication on the MQ system, reducing the dependence of synchronous and asynchronous communication on the application itself, and improving maintenance reliability. Furthermore, the interactive system stores the data it has interacted with locally for subsequent auditing, allowing users to query historical data interaction processes on the interactive system; based on a certain characteristic of the data, all flow processes can be traced, thereby ensuring data traceability. Attached Figure Description
[0015] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0016] Figure 1 A flowchart illustrating a highly reliable and traceable asynchronous data communication method provided in this application embodiment; Figure 2 This is a schematic diagram of point-to-point data communication provided in an embodiment of this application; Figure 3 This is a schematic diagram of data distribution communication provided for an embodiment of this application; Figure 4 This is a schematic diagram of a highly reliable and traceable asynchronous data communication device provided in an embodiment of this application. Detailed Implementation
[0017] To make the objectives, technical solutions, and advantages of this invention clearer, the invention will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the invention. Furthermore, the technical features involved in the various embodiments of this invention described below can be combined with each other as long as they do not conflict with each other.
[0018] The terms "first," "second," "third," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish different objects, not to describe a specific order. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products, or apparatuses.
[0019] According to a first aspect of the invention, in conjunction with the appendix Figure 1 As shown, a highly reliable and traceable asynchronous data communication method is provided, including: S01, the first application pushes business data and the target application's identification information to the data interaction system; it should be noted that the first application, such as application A, pushes business data to the data interaction system and specifies that the target of the data is the unique identifier registered by application B.
[0020] S02, the interactive system receives the service data and configures the status of the service data to a first state; it obtains the quantity information and registration information of the target application based on the identification information of the target application, and generates a first sending strategy for the service data based on the quantity information and registration information of the target application; it should be noted that the interactive system receives the data, stores it locally, and configures the data status of the service data to ready. Then, the interactive system analyzes the target application of the data, i.e., application B, queries the registration information, and if a match is found, pushes the data to the target application B according to the registration information of application B. The first sending strategy for the service data is generated based on the quantity information and registration information of the target application. Different quantities and registration information of the target applications correspond to different sending strategies for the service data, as detailed in subsequent embodiments, which will not be elaborated here.
[0021] S03, the interactive system pushes the service data to the target application based on the first sending strategy, and modifies the status of the service data to the second status according to the push result; it should be noted that the data is pushed to the target application B according to the registration information of application B; the data status is finished after successful push, and the data status is fail after failed push.
[0022] S04, the interactive system retransmits the service data according to the second sending strategy and the second status of the service data. It should be noted that the interactive system periodically retryes data with a "fail" status according to the second sending strategy; after the number of attempts exceeds the limit, it stops retrying. The purpose is to avoid failures caused by problems with the target application, thereby improving the success rate of service data transmission.
[0023] Further, step S02 also includes: different numbers of target applications and different registration information of the target applications correspond to different sending strategies for the service data, specifically including: the interactive system obtains the number information and registration information of the target applications based on the identification information of the target applications, and corresponding to different situations: Scenario 1: If the number of target applications is one, and the registration information of the target application is already registered; then the first sending strategy for the generated business data is: push the business data to the target application; it should be noted that, in conjunction with the appendix... Figure 2 As shown, this is a point-to-point data communication mode. Taking application A pushing data to application B as an example, the interactive system analyzes the target application of the data, queries the registration information, and after a match, pushes the data to the target application B based on the registration information of application B.
[0024] Scenario 2: If there are multiple target applications, and all target applications are registered, then the first sending strategy for the generated business data is to push the business data to each target application. It should be noted that, in conjunction with the appendix... Figure 3 As shown, this is a data distribution communication mode: taking application A pushing data to applications B, C, and D as an example; application A pushes business data to the data interaction system, specifying that the target of this data is the unique identifier registered by application B; the interaction system analyzes the target application of the data, queries the registration information, obtains the registration information of B, C, and D, and, combined with the registration information, copies the source data packet to form new point-to-point push data, while updating the data status of the source data to finish. Based on the new push data, the interaction system continues to execute the relevant logic of the above point-to-point data communication until the data push to target applications C and D is completed.
[0025] Scenario 3: If there are multiple target applications, and not all target applications are registered, then the first sending strategy for the generated business data is to push the business data to the registered target applications. It should be noted that this is a data distribution communication mode: taking application A pushing data to applications B, C, and D as an example; application A pushes business data to the data interaction system, specifying that the target of this data is the unique identifier registered by application B; the interaction system analyzes the target application of the data, queries the registration information, obtains the registration information of B, C, and D, and, combined with the registration information, copies the source data packet to form new point-to-point push data, while updating the data status of the source data to finished. Based on the new push data, the interaction system continues to execute the relevant logic of the above point-to-point data communication. Assuming that target application C has completed registration and target application D has not completed registration, the data push to target application C is completed. For target application D, the aforementioned periodic retry process is executed or the push is abandoned.
[0026] Furthermore, the step of pushing the business data to each of the target applications also includes: The interactive system, based on a preset third sending strategy, pushes the business data to each of the target applications individually, or splits the business data and pushes the split data fragments to the corresponding target applications. It should be noted that since the registration information of the target applications is fully registered, the preset third sending strategy can be either splitting the business data or sending the business data as a whole. The preset third sending strategy can be determined based on the application type of target application A, the registration type at the time of registration, or the type of business data and the push attributes; no limitation is made here. Specifically, if the preset third sending strategy is to send the business data as a whole, then the business data is pushed to each of the target applications individually; or, if the preset third sending strategy is to split the business data, then the business data is split, and the split data fragments are pushed to the corresponding target applications. The relationship between the splitting of business data and the correspondence with the target applications can be determined when configuring the above-mentioned third sending strategy.
[0027] Furthermore, the step of pushing the business data to the registered target application also includes: The interactive system, based on a preset fourth sending strategy, pushes the service data to each registered target application; or, it splits the service data and pushes the split data fragments to the corresponding registered target applications; or, it splits the service data, wherein each target application corresponds to one data fragment, and periodically obtains the registration status of each target application and pushes the split data fragments to the corresponding registered target applications. It should be noted that, since the registration information of the target application is not fully registered, the preset fourth sending strategy is either splitting the business data for sending or sending the business data as a whole. The sending target is either the registered target application or the target application that has been registered and subsequently registered. Specifically, taking application A pushing data to applications B, C, and D as an example: application A pushes business data to the data interaction system, specifying that the target of the data is the unique identifier registered by applications B, C, and D; the interaction system analyzes the target application of the data, queries the registration information, obtains the registration information of B, C, and D, and, in conjunction with the registration information, copies or splits the source data packet to form new point-to-point push data. For target applications that have been registered and have successfully sent data, the data status of the corresponding source data is updated to "finish". Assuming that target application C has completed registration and target application D has not completed registration, the data push to target application C continues, and the data status of the corresponding source data is updated to "finish". For target application D, the aforementioned periodic retry process is performed or the push is abandoned. The specific method of splitting data and establishing a correspondence with the target application is the same as in the previous embodiment, and will not be repeated here.
[0028] Furthermore, steps S03 and S04 also include: The business data is pushed to the target application. Upon successful push, the status of the business data is changed to "finish"; upon failed push, the status is changed to "fail". The interactive system, following a second sending strategy, periodically and automatically retry sending business data with a "fail" status to the target application. After the number of attempts exceeds a certain limit, no further retries are made. For example, data is pushed to target application B based on application B's registration information; upon successful push, the data status is "finish", and upon failed push, the data status is "fail". This avoids "fail" issues caused by problems with the target application.
[0029] Furthermore, it also includes: Users can manually push business data of any state to the target application by performing a retransmission operation on the interactive system based on the status of the business data. It should be noted that users can manually intervene and perform the retransmission operation on the interactive system to manually push data of any state to the target system, thereby improving the flexibility of data push.
[0030] Furthermore, it also includes: The target application registers itself in the interactive system. Registration information includes: a unique application identifier, an application service address, and a token for accessing the service. It should be noted that applications requiring access to the data interaction system must also register within the system, registering their unique identifier, application service address, token for accessing the service, and a description. This approach offers several advantages: First, data communication between applications can be completed without knowing the location information (IP + interface) of the other system. If an application's location changes, the caller does not need to make any modifications, significantly reducing inter-application dependencies. Second, the same interface service can be provided by applications registered on multiple nodes. If a node fails, the data interaction system automatically switches to another available node, ensuring the caller is not affected and improving the availability of the caller's own system.
[0031] Furthermore, prior to registration, it also includes: Data Interaction System Deployment: This invention employs a multi-node distributed deployment, and then uses Keepalive + Nginx technology to achieve hot switching. This ensures that in the event of a single point of failure, the node will automatically switch over to continue providing services, guaranteeing the high reliability and high availability of the data interaction system as a fundamental service.
[0032] According to a second aspect of the invention, in conjunction with the appendix Figure 4As shown, a highly reliable and traceable asynchronous data communication device is also provided, comprising: The business data push module is configured to push business data and the target application's identification information to the data interaction system from the first application. A business data receiving module is configured to receive the business data from the interactive system and configure the state of the business data as a first state; obtain the quantity information and registration information of the target application based on the identification information of the target application, and generate a first sending strategy for the business data based on the quantity information and registration information of the target application. The business data forwarding module is configured such that the interactive system pushes the business data to the target application based on the first sending strategy, and modifies the status of the business data to a second status according to the push result; The service data retransmission module is configured to allow the interactive system to retransmit the service data according to the second transmission strategy and the second state of the service data.
[0033] It should be noted that the highly reliable and traceable asynchronous data communication device of the present invention is implemented in accordance with the steps in the aforementioned highly reliable and traceable asynchronous data communication method, and will not be described in detail here.
[0034] According to a third aspect of the present invention, a highly reliable and traceable asynchronous data communication device is also provided, comprising at least one processing unit and at least one storage unit, wherein the storage unit stores a computer program that, when executed by the processing unit, causes the processing unit to perform the steps of any of the methods described above.
[0035] According to a fourth aspect of the present invention, a computer program product is also provided, comprising a computer program / instructions, characterized in that, when the computer program / instructions are executed by a processor, they implement the steps of any of the methods described above.
[0036] Overall, compared with the prior art, the above technical solutions conceived by this invention can achieve the following beneficial effects: the highly reliable and traceable asynchronous data communication method of this invention can be widely used in data interaction between application systems, reducing the dependence of application data communication on the MQ system, reducing the dependence of synchronous and asynchronous communication on the application itself, and improving the reliability of maintenance.
[0037] This application also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the above-described method. The computer-readable storage medium may include, but is not limited to, any type of disk, including floppy disks, optical disks, DVDs, CD-ROMs, microdrives, as well as magneto-optical disks, ROMs, RAMs, EPROMs, EEPROMs, DRAMs, VRAMs, flash memory devices, magnetic cards or optical cards, nanosystems (including molecular memory ICs), or any type of medium or device suitable for storing instructions and / or data.
[0038] It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that this application is not limited to the described order of actions, as some steps may be performed in other orders or simultaneously according to this application. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are preferred embodiments, and the actions and modules involved are not necessarily essential to this application.
[0039] In the above embodiments, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions in other embodiments.
[0040] In the several embodiments provided in this application, it should be understood that the disclosed apparatus can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some service interface; the indirect coupling or communication connection between devices or units may be electrical or other forms.
[0041] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.
[0042] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.
[0043] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage device (CMD). Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a memory and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned memory includes various media capable of storing program code, such as USB flash drives, read-only memory (ROM), random access memory (RAM), portable hard drives, magnetic disks, or optical disks.
[0044] Those skilled in the art will understand that all or part of the steps in the various methods of the above embodiments can be implemented by a program instructing related hardware. The program can be stored in a computer-readable storage medium, which may include: a flash drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, etc.
[0045] The foregoing description is merely an exemplary embodiment of this disclosure and should not be construed as limiting the scope of this disclosure. Any equivalent changes and modifications made in accordance with the teachings of this disclosure shall still fall within the scope of this disclosure. Those skilled in the art will readily conceive of embodiments of this disclosure upon considering the specification and practicing the disclosure herein. This application is intended to cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common knowledge or customary techniques in the art not described herein. The specification and embodiments are to be considered exemplary only, and the scope and spirit of this disclosure are defined by the claims.
[0046] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.
[0047] Those skilled in the art will readily understand that the above description is merely a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of the present invention should be included within the scope of protection of the present invention.
Claims
1. A highly reliable and traceable asynchronous data communication method, characterized in that, include: S01, the first application pushes business data and the target application's identification information to the data interaction system; S02, the interactive system receives the service data and configures the status of the service data to a first status; Based on the identification information of the target application, obtain the quantity information and registration information of the target application, and generate a first sending strategy for the service data based on the quantity information and registration information of the target application; S03, the interactive system pushes the service data to the target application based on the first sending strategy, and modifies the status of the service data to the second status according to the push result; S04, the interactive system retransmits the service data according to the second transmission strategy and the second state of the service data.
2. The asynchronous data communication method as described in claim 1, characterized in that, Step S02 further includes: The interactive system obtains the number of target applications and their registration information based on the identification information of the target application. If the number of target applications is one and the registration information of the target application is "registered", then the first sending strategy of the generated business data is to push the business data to the target application. If there are multiple target applications, and all target applications are registered, then the first sending strategy for the generated business data is to push the business data to each target application. If there are multiple target applications, and the registration information of the target applications is incomplete, then the first sending strategy for the generated business data is to push the business data to the registered target applications.
3. The asynchronous data communication method as described in claim 2, characterized in that, The step of pushing the business data to each of the target applications further includes: The interactive system, based on a preset third sending strategy, pushes the business data to each of the target applications, or splits the business data and pushes the split data fragments to the corresponding target applications.
4. The asynchronous data communication method as described in claim 2, characterized in that, The step of pushing the business data to the registered target application further includes: The interactive system, based on a preset fourth sending strategy, pushes the service data to each registered target application; or, it splits the service data and pushes the split data fragments to the corresponding registered target applications; or, it splits the service data, wherein each target application corresponds to one data fragment, and periodically obtains the registration status of each target application and pushes the split data fragments to the corresponding registered target applications.
5. The asynchronous data communication method according to any one of claims 1-4, characterized in that, Steps S03 and S04 further include: The business data is pushed to the target application. If the push is successful, the status of the business data is changed to finish. If the push fails, the status of the business data is changed to fail. The interactive system, following the second sending strategy, periodically and automatically retry sending service data with a data status of "fail" to the target application; after the number of attempts exceeds the limit, it will no longer retry.
6. The asynchronous data communication method as described in claim 5, characterized in that, Also includes: Users can perform a resend operation on the interactive system based on the status of the business data, manually pushing business data of any data status to the target application.
7. The asynchronous data communication method as described in claim 1, characterized in that, Also includes: The target application registers itself in the interactive system. The registration information includes: a unique application identifier, an application service address, and a token for accessing the application service.
8. A highly reliable and traceable asynchronous data communication device, characterized in that, include: The business data push module is configured to push business data and the target application's identification information to the data interaction system from the first application. A business data receiving module is configured to receive the business data from the interactive system and configure the state of the business data as a first state. Based on the identification information of the target application, obtain the quantity information and registration information of the target application, and generate a first sending strategy for the service data based on the quantity information and registration information of the target application; The business data forwarding module is configured such that the interactive system pushes the business data to the target application based on the first sending strategy, and modifies the status of the business data to a second status according to the push result; The service data retransmission module is configured to allow the interactive system to retransmit the service data according to the second transmission strategy and the second state of the service data.
9. A highly reliable and traceable asynchronous data communication device, characterized in that, The method includes at least one processing unit and at least one storage unit, wherein the storage unit stores a computer program that, when executed by the processing unit, causes the processing unit to perform the steps of the method according to any one of claims 1 to 7.
10. A computer program product comprising a computer program / instructions, characterized in that, When the computer program / instructions are executed by the processor, they implement the steps of the method according to any one of claims 1 to 7.
