A method, apparatus and system for data transfer

Abstract

The application provides a data transmission method, device and system, and the method comprises the following steps: classifying received product application messages of a fixed format according to product application names; calling message receiving services provided by each product application according to the product application names and pushing the message receiving services to each product application; and starting a thread according to the product application messages to initiate a transaction and hand over the transaction to a product application system for execution. The application decouples characteristic information from a sending message by extracting the characteristic information from a characteristic product application message, realizes data transmission of the characteristic product application message and the like characteristic information, solves the problem of coupling of the characteristic information and an irrelevant application system, reduces the coupling between applications, and maintains the independence of the system.

Description

Technical Field

[0001] This application belongs to the field of information and data transmission technology, specifically, it relates to a data transmission method, apparatus and system. Background Technology

[0002] In banking systems, a single transaction often involves multiple application systems, which communicate with each other via messages. When the front end needs to pass certain specific information to downstream application systems, these specific message details need to be added to the communication areas of each interface of the application system on the link between the message initiating and receiving application systems. This specific information is then passed to the target application through the communication areas of the upstream and downstream applications.

[0003] Application systems along the link need to add unique message information, but this information is unrelated to the applications on the link, leading to coupling between applications and contradicting the architectural design principle of "high cohesion and loose coupling." When there are many such requirements, frequent changes to application services cause system instability and pose security risks to the application systems. At the same time, it is necessary to coordinate the transformation of applications along the link, making it difficult to support rapid response to business needs. Summary of the Invention

[0004] This application provides a data transmission method and apparatus to at least solve the problem of coupling between applications caused by the lack of correlation between the special message information between current application systems and the applications on the link.

[0005] According to one aspect of this application, a data transmission system is provided, comprising: a channel application system and a message transmission system;

[0006] Communication connection between the channel application system and the message transmission system;

[0007] The message transmission system includes a message receiving subsystem, a message reply subsystem, and a message sending subsystem, and these subsystems are interconnected.

[0008] According to a second aspect of this application, based on the above system, a data transmission method is also provided, comprising:

[0009] The received fixed-format product application messages are categorized by product application name;

[0010] Call the message receiving service provided by each product application according to the product application name and push it to each product application;

[0011] The product application message initiates a transaction by starting a thread and then the product application system executes the transaction.

[0012] In one embodiment, received fixed-format product application messages are categorized by product application name, including:

[0013] Extract the product application name from the product application message;

[0014] The startup thread distinguishes the application system to which the instruction needs to be sent based on the product application name and notifies the subsystem to send the message.

[0015] In one embodiment, invoking the message receiving service provided by each product application according to the product application name and pushing the message to each product application includes:

[0016] Call the message receiving service provided by each product application by product application name;

[0017] Push the message to each product application in a preset message format;

[0018] The received product application messages are temporarily stored.

[0019] In one embodiment, initiating a transaction based on a product application message and having the product application system execute the transaction includes:

[0020] Start the thread based on the product application message;

[0021] The transaction messages are transmitted to each product application system sequentially according to the transaction process;

[0022] The product application system executes transactions.

[0023] In one embodiment, the product application system executes a transaction, including:

[0024] When a transaction is executed to the corresponding product application system, each product application retrieves the product application message pushed in the previous stage based on the associated event number in the product application message and performs business operations.

[0025] In one embodiment, the data transmission method further includes:

[0026] The received product application messages are converted into a fixed format, which includes: associated event number, target application, and message information.

[0027] According to a third aspect of this application, a data transmission apparatus is also provided, comprising:

[0028] The classification unit is used to classify the received fixed-format product application messages according to the product application name;

[0029] The service call push unit is used to call the message receiving service provided by each product application according to the product application name and push it to each product application.

[0030] The thread-initiated transaction execution unit is used to initiate a transaction based on the product application message and hand it over to the product application system for execution.

[0031] In one embodiment, the classification unit includes:

[0032] The name extraction module is used to extract the product application name from the product application message;

[0033] The differentiation and sending module is used to start a thread to differentiate the application system to which the instruction needs to be sent based on the product application name and to notify the message sending subsystem.

[0034] In one embodiment, the service call push unit includes:

[0035] The calling module is used to invoke the message receiving service provided by each product application according to the product application name;

[0036] The push module is used to push messages to various product applications in a preset message format;

[0037] The temporary storage module is used to temporarily store received product application messages.

[0038] In one embodiment, the thread-initiated transaction execution unit includes:

[0039] The thread startup module is used to start threads based on product application messages;

[0040] The message delivery module is used to sequentially deliver transaction messages to each product application system according to the transaction process.

[0041] The transaction execution module is used by the product application system to execute transactions.

[0042] In one embodiment, the transaction execution module includes:

[0043] The message number acquisition module is used to retrieve the product application message pushed in the previous stage and perform business operations based on the associated event number in the product application message when the transaction is executed to the corresponding product application system.

[0044] In one embodiment, the data transmission apparatus further includes:

[0045] The format conversion module is used to convert received product application messages into a fixed format, which includes: associated event number, target application, and message information.

[0046] This application extracts unique information from the application messages of special products and decouples it from the sent messages, thereby realizing the data transmission of unique information such as application messages of special products. This solves the problem of coupling between unique information and unrelated application systems, reduces the coupling between applications, and maintains the independence of the system. Attached Figure Description

[0047] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0048] Figure 1 This application provides a data transmission system.

[0049] Figure 2 A message transmission system provided for this application.

[0050] Figure 3 This is the message receiving subsystem in the embodiments of this application.

[0051] Figure 4 This is a flowchart of the message receiving subsystem in an embodiment of this application.

[0052] Figure 5 This is the message response subsystem in the embodiments of this application.

[0053] Figure 6 This is a flowchart of the message response subsystem in an embodiment of this application.

[0054] Figure 7 This is the message sending subsystem in the embodiments of this application.

[0055] Figure 8 This is a flowchart of the message sending subsystem in this application embodiment.

[0056] Figure 9 This is a flowchart of a method applied to the system in an embodiment of this application.

[0057] Figure 10 In this embodiment of the application, the received fixed-format product application messages are classified according to the product application name.

[0058] Figure 11 In this embodiment of the application, the message receiving service provided by each product application is invoked according to the product application name and pushed to each product application.

[0059] Figure 12 In this embodiment of the application, a transaction is initiated by starting a thread based on the product application message and the transaction process is executed by the product application system.

[0060] Figure 13 This application provides a data transmission apparatus.

[0061] Figure 14 This is a structural block diagram of the classification unit in the embodiments of this application.

[0062] Figure 15 This is a structural block diagram of the service call push unit in the embodiments of this application.

[0063] Figure 16 This is a structural block diagram of the thread-initiated transaction execution unit in an embodiment of this application.

[0064] Figure 17 This is a specific implementation of an electronic device in the embodiments of this application. Detailed Implementation

[0065] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0066] To address the problems existing in the background art, this application provides a data transmission system, such as... Figure 1 The system shown includes: channel application system and message transmission system;

[0067] Communication connection between the channel application system and the message transmission system;

[0068] The message transmission system includes a message receiving subsystem, a message reply subsystem, and a message sending subsystem, and these subsystems are interconnected.

[0069] like Figure 2 As shown, the message transmission system 10 consists of three subsystems, including a message receiving subsystem 11, a message acknowledgment subsystem 12, and a message sending subsystem 13.

[0070] like Figure 3 As shown, the message receiving subsystem 11 consists of four modules: a message receiving module 111, a message identification module 112, a message sorting module 113, and a message notification module 114. The message receiving subsystem flow is as follows: Figure 4 As shown, the background thread receives messages pushed by the channel application system, identifies and sorts the messages according to the agreed message format, and then notifies the message response subsystem. The specific implementation methods of each module are as follows:

[0071] The message receiving module 111 is responsible for receiving messages sent by the channel application system. This module uses a background thread to continuously listen for messages. When a new message is detected, it will be pushed to the message recognition module.

[0072] The message identification module 112 is responsible for determining whether received messages meet the requirements. This module identifies whether received messages meet the requirements based on the pre-agreed message format "associated event number + target application + message information". Messages that meet the requirements are pushed to the message sorting module for sorting, while messages that do not meet the requirements are pushed to the message response module, which notifies the channel application system that the message does not meet the requirements.

[0073] The message sorting module 113 is responsible for sorting the target application to which the message belongs. Based on the pre-agreed message format "Associated Event Number + Target Application + Message Information", this module retrieves the target application and checks whether it has requested permission from the message delivery system. If permission has been requested, the message is placed in the pending delivery queue. If permission has not been requested, the message is pushed to the message response module, which notifies the channel application system that the target application of the message has not requested permission.

[0074] The message notification module 114 is responsible for pushing the information that the message identification module 112 and the message sorting module 113 need to respond to to the message response subsystem.

[0075] like Figure 5 As shown, the message response subsystem 12 consists of two modules: a notification receiving module 121 and a response information sending module 122. The message response subsystem flow is as follows: Figure 6 As shown, the background thread scans for notifications pushed by the message receiving subsystem and the message sending subsystem, and pushes response information to the product application system according to the notification type. The specific implementation methods of each module are as follows:

[0076] The notification receiving module 121 is responsible for receiving various notifications from the message transmission system, including notifications pushed by the message receiving subsystem message notification module 114 and notifications pushed by the message sending subsystem message result notification module 132. The notification receiving module 121 then pushes the notification information to the response message sending module.

[0077] The message sending and response module 122 is responsible for responding to the channel product application, feeding back the message processing results sent by the channel product application. This includes whether the message meets the requirements and whether the product application has received the message.

[0078] like Figure 7 As shown, the message sending subsystem 13 consists of two modules: a message sending queue management module 131 and a message sending result notification module 132. The message sending subsystem flow is as follows: Figure 8As shown, the background thread monitors whether new tasks have entered the queue. If a new task is added, it starts a new thread to call the service provided by the product application to push application messages according to the queue task order, supporting retries on failure. The product application returns a result to the message response subsystem, which then returns the result to the channel product application. The specific implementation methods of each module are as follows:

[0079] The message sending queue management module 131 is responsible for managing messages to be sent. This mainly includes monitoring the queue's status, checking for blockages, sending messages to the product application, and supporting retries on failure. When a queue is blocked, the module notifies maintenance personnel via SMS.

[0080] The message sending result notification module 132 is responsible for receiving the results returned from the product application and notifying the message response subsystem of the results.

[0081] Based on the aforementioned data transmission system, this application also provides a method applied to that system, such as... Figure 9 As shown, it includes:

[0082] S901: Classify received fixed-format product application messages by product application name.

[0083] S902: Call the message receiving service provided by each product application according to the product application name and push it to each product application.

[0084] S903: Initiate a transaction by starting a thread based on the product application message and hand it over to the product application system for execution.

[0085] In one specific embodiment, the channel application system categorizes sent messages into two types: transaction messages and featured product application messages. Transaction messages refer to the message information used in the main process of the transaction; featured product application messages refer to the message information of a specific business required by a particular application system for the transaction. A transaction is split into two steps: first, a featured product application message is sent, then the transaction message is sent. The association between the two messages is established through an associated event number, thereby achieving the purpose of transmitting complete messages.

[0086] First, the application messages of featured products are pushed to the message delivery system in a fixed format of "related event number + target application + message information". After processing, the message delivery system sends them to the product application system. Then, the message delivery system summarizes the response results returned by each product application and pushes the results to each channel application system.

[0087] In one embodiment, received fixed-format product application messages are categorized by product application name, such as... Figure 10 As shown, it includes:

[0088] S1001: Extract the product application name from the product application message.

[0089] S1002: Start the thread to distinguish the application system to which the instruction needs to be sent based on the product application name and notify the message sending subsystem.

[0090] In one specific embodiment, the message receiving subsystem 11 starts a background thread to receive message information sent by the channel application system and notifies the message response subsystem 12. The message response subsystem 12 starts a thread to distinguish the application system to which the instruction needs to be sent based on the product application name and notifies the message sending subsystem 13.

[0091] In one embodiment, the message receiving service provided by each product application is invoked according to the product application name and pushed to each product application, such as... Figure 11 As shown, it includes:

[0092] S1101: Call the message receiving service provided by each product application according to the product application name.

[0093] S1102: Pushes messages to various product applications in a preset message format.

[0094] S1103: Temporarily store the received product application message.

[0095] In one specific embodiment, the message sending subsystem 13, based on the information provided by the message response subsystem 12, calls the message receiving service provided by each product application according to the application, and then pushes it to each product application with the associated event number + product application message format. The product application receiving the message temporarily stores the received special product application message.

[0096] In one embodiment, a thread is started based on the product application message to initiate a transaction and the product application system executes the transaction, such as... Figure 12 As shown, it includes:

[0097] S1201: Start a thread based on the product application message.

[0098] S1202: Transmit transaction messages to each product application system in sequence according to the transaction process.

[0099] S1203: The product application system executes transactions.

[0100] In one specific embodiment, the channel application system initiates a new thread to launch a transaction and sequentially transmits the transaction message to product application system 1, product application system 2, and product application system n according to the transaction process. When the transaction is executed to the corresponding product application system, each product application obtains the featured product application message pushed in the previous stage based on the associated event number and performs the relevant business operations.

[0101] In one embodiment, the product application system executes a transaction, including:

[0102] When a transaction is executed to the corresponding product application system, each product application retrieves the product application message pushed in the previous stage based on the associated event number in the product application message and performs business operations.

[0103] In one embodiment, the data transmission method further includes:

[0104] The received product application messages are converted into a fixed format, which includes: associated event number, target application, and message information.

[0105] like Figure 1 As shown, the specific process of the above method in the embodiment is as follows:

[0106] ① The channel application first initiates a thread to push the featured product application message to the message delivery system 10 in the format of "associated event number + target application + message information". The message delivery system 10 consists of 3 subsystems, as follows: Figure 2 As shown, it includes a message receiving subsystem 11, a message response subsystem 12, and a message sending subsystem 13.

[0107] ② The message receiving subsystem 11 starts a background thread to receive message information sent by the channel application system and notifies the message response subsystem 12.

[0108] ③ The message response subsystem 12 starts a thread, distinguishes the application system to which the instruction needs to be sent according to the product application name, and notifies the message sending subsystem 13.

[0109] ④ Based on the information provided by the message response subsystem 12, the message sending subsystem 13 calls the message receiving service provided by each product application according to the application, and pushes it to each product application in the format of associated event number + product application message. The product application receiving the message will temporarily store the received special product application message.

[0110] ⑤ The message response subsystem 12 summarizes the response results returned by each product application in the message sending subsystem 13 and pushes the results to each channel application system.

[0111] ⑥ The channel application system starts a new thread to initiate a transaction, and transmits the transaction message to product application system 1, product application system 2, and product application system n in sequence according to the transaction process.

[0112] ⑦ When a transaction is executed to the corresponding product application system, each product application retrieves the featured product application message pushed from the previous stage based on the associated event number and performs relevant business operations. By decoupling the transaction message from the featured product application message, the goal of transmitting data and decoupling between applications is achieved.

[0113] Based on the same inventive concept, this application also provides a data transmission apparatus, which can be used to implement the method described in the above embodiments, as described in the following embodiments. Since the principle of this data transmission apparatus in solving the problem is similar to that of the data transmission method, the implementation of the data transmission apparatus can refer to the implementation of the data transmission method, and repeated details will not be elaborated further. As used below, the terms "unit" or "module" can refer to a combination of software and / or hardware that implements a predetermined function. Although the system described in the following embodiments is preferably implemented in software, hardware implementation, or a combination of software and hardware, is also possible and contemplated.

[0114] According to another aspect of this application, a data transmission apparatus is also provided, such as... Figure 13 As shown, it includes:

[0115] Classification unit 1301 is used to classify received fixed-format product application messages according to product application name;

[0116] The service call push unit 1302 is used to call the message receiving service provided by each product application according to the product application name and push it to each product application.

[0117] The thread-initiated transaction execution unit 1303 is used to initiate a transaction based on the product application message and hand it over to the product application system for execution.

[0118] In one embodiment, such as Figure 14 As shown, classification unit 1301 includes:

[0119] The name extraction module 1401 is used to extract the product application name from the product application message.

[0120] The differentiation and sending module 1402 is used to start a thread to differentiate the application system to which the instruction needs to be sent based on the product application name and to notify the message sending subsystem.

[0121] In one embodiment, such as Figure 15 As shown, the service call push unit 1302 includes:

[0122] Module 1501 is invoked to call the message receiving service provided by each product application according to the product application name.

[0123] The push module 1502 is used to push messages to various product applications in a preset message format;

[0124] The temporary storage module 1503 is used to temporarily store the received product application messages.

[0125] In one embodiment, such as Figure 16 As shown, the thread-initiated transaction execution unit 1303 includes:

[0126] The thread startup module 1601 is used to start threads based on product application messages.

[0127] The message transmission module 1602 is used to transmit transaction messages to each product application system sequentially according to the transaction process.

[0128] The transaction execution module 1603 is used by the product application system to execute transactions.

[0129] In one embodiment, the transaction execution module includes:

[0130] The message number acquisition module is used to retrieve the product application message pushed in the previous stage and perform business operations based on the associated event number in the product application message when the transaction is executed to the corresponding product application system.

[0131] In one embodiment, the data transmission apparatus further includes:

[0132] The format conversion module is used to convert received product application messages into a fixed format, which includes: associated event number, target application, and message information.

[0133] This application extracts unique information from the application messages of special products and decouples it from the sent messages, thereby realizing the data transmission of unique information such as application messages of special products. This solves the problem of coupling between unique information and unrelated application systems, reduces the coupling between applications, and maintains the independence of the system.

[0134] Those skilled in the art will understand that embodiments of the present invention can be provided as methods, systems, or computer program products. Therefore, the present invention can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0135] This invention is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1A device that provides the functions specified in one or more boxes.

[0136] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0137] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0138] Specific embodiments have been used to illustrate the principles and implementation methods of this invention. The descriptions of the embodiments above are only for the purpose of helping to understand the method and core ideas of this invention. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of this invention. Therefore, the content of this specification should not be construed as a limitation of this invention.

[0139] This application also provides a specific implementation of an electronic device capable of implementing all the steps in the methods described above. See [link to implementation details]. Figure 17 The electronic device specifically includes the following:

[0140] Processor 1701, memory 1702, communications interface 1703, bus 1704, and non-volatile memory 1705;

[0141] The processor 1701, memory 1702, and communication interface 1703 communicate with each other through the bus 1704.

[0142] The processor 1701 is used to call a computer program stored in the memory 1702 and the non-volatile memory 1705. When the processor executes the computer program, it implements all the steps in the method described in the above embodiments. For example, when the processor executes the computer program, it implements the following steps:

[0143] S901: Classify received fixed-format product application messages by product application name.

[0144] S902: Call the message receiving service provided by each product application according to the product application name and push it to each product application.

[0145] S903: Initiate a transaction by starting a thread based on the product application message and hand it over to the product application system for execution.

[0146] Embodiments of this application also provide a computer-readable storage medium capable of implementing all steps of the methods in the above embodiments. The computer-readable storage medium stores a computer program that, when executed by a processor, implements all steps of the methods in the above embodiments. For example, when the processor executes the computer program, it implements the following steps:

[0147] S901: Classify received fixed-format product application messages by product application name.

[0148] S902: Call the message receiving service provided by each product application according to the product application name and push it to each product application.

[0149] S903: Initiate a transaction by starting a thread based on the product application message and hand it over to the product application system for execution.

[0150] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on its differences from other embodiments. In particular, for hardware + program embodiments, since they are basically similar to method embodiments, the description is relatively simple; relevant parts can be referred to the descriptions in the method embodiments. Although the embodiments in this specification provide the method operation steps as shown in the embodiments or flowcharts, more or fewer operation steps may be included based on conventional or non-inventive means. The order of steps listed in the embodiments is merely one possible execution order among many steps and does not represent the only execution order. In actual device or terminal product execution, the methods can be executed in the order shown in the embodiments or drawings or in parallel (e.g., in a parallel processor or multi-threaded processing environment, or even a distributed data processing environment). The terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, product, or apparatus that includes a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, product, or apparatus. Without further limitations, the presence of other identical or equivalent elements in the process, method, product, or apparatus that includes said elements is not excluded. For ease of description, the above devices are described in terms of function, divided into various modules. Of course, in implementing the embodiments of this specification, the functions of each module can be implemented in one or more software and / or hardware, or the module implementing the same function can be implemented by a combination of multiple sub-modules or sub-units, etc. The device embodiments described above are merely illustrative. For example, the division of units is only a logical functional division; 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 interfaces; the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms. This invention is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing device to produce a machine, such that the instructions, which are executable by the processor of the computer or other programmable data processing device, produce instructions for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0151] Those skilled in the art will understand that the embodiments of this specification can be provided as methods, systems, or computer program products. Therefore, the embodiments of this specification can take the form of entirely hardware embodiments, entirely software embodiments, or embodiments combining software and hardware aspects. Furthermore, the embodiments of this specification can take the form of computer program products implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code. The various embodiments in this specification are described in a progressive manner, and similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, for system embodiments, since they are basically similar to method embodiments, the description is relatively simple, and relevant parts can be referred to the description of the method embodiments. In the description of this specification, the reference to the terms "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., means that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of the embodiments of this specification.

[0152] In this specification, the illustrative expressions of the terms used do not necessarily refer to the same embodiments or examples. Furthermore, those skilled in the art can combine and integrate different embodiments or examples described in this specification, as well as features of different embodiments or examples, without contradiction. The above descriptions are merely embodiments of this specification and are not intended to limit the embodiments of this specification. Various modifications and variations can be made to the embodiments of this specification by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principle of the embodiments of this specification should be included within the scope of the claims of the embodiments of this specification.

Claims

1. A data transmission method, applied to a channel application system and a message transmission system, characterized in that, include: The message transmission system categorizes the received fixed-format product application messages by product application name. The message delivery system calls the message receiving service provided by each product application according to the product application name and pushes it to each product application. The channel application system initiates a transaction by starting a thread based on the product application message and then hands the transaction over to the product application system for execution. The channel application system and the message transmission system are connected in communication. The message transmission system includes a message receiving subsystem, a message response subsystem, and a message sending subsystem, and these subsystems are connected in communication. The channel application system classifies the sent messages into transaction messages and product application messages. The product application message refers to the message information of the specific business required by the application system in the transaction. The step of initiating a transaction based on the product application message and having the product application system execute the transaction includes: Start the thread according to the product application message; The transaction messages are transmitted to each product application system sequentially according to the transaction process; The product application system executes transactions.

2. The data transmission method according to claim 1, characterized in that, The step of classifying received fixed-format product application messages by product application name includes: Extract the product application name from the product application message; The startup thread distinguishes the application system to which the instruction needs to be sent based on the product application name and notifies the message sending subsystem.

3. The data transmission method according to claim 1, characterized in that, The step of calling the message receiving service provided by each product application according to the product application name and pushing it to each product application includes: Invoke the message receiving service provided by each product application according to the product application name; Push the message to each product application in a preset message format; The received product application messages are temporarily stored.

4. The data transmission method according to claim 1, characterized in that, The product application system executes transactions, including: When a transaction is executed to the corresponding product application system, each product application retrieves the product application message pushed in the previous stage based on the associated event number in the product application message and performs business operations.

5. The data transmission method according to claim 1, characterized in that, Also includes: The received product application messages are converted into a fixed format, which includes: associated event number, target application, and message information.

6. A data transmission device, applied to a channel application system and a message transmission system, characterized in that, include: A classification unit is used by the message transmission system to classify received fixed-format product application messages according to the product application name. The service call push unit is used by the message transmission system to call the message receiving service provided by each product application according to the product application name and push it to each product application. A thread-initiated transaction execution unit is used by the channel application system to initiate a transaction based on the product application message and hand it over to the product application system for execution. The channel application system and the message transmission system are connected in communication. The message transmission system includes a message receiving subsystem, a message response subsystem, and a message sending subsystem, and these subsystems are connected in communication. The channel application system classifies the sent messages into transaction messages and product application messages. The product application message refers to the message information of the specific business required by the application system in the transaction. The thread-initiated transaction execution unit includes: A thread startup module is used to start a thread based on the product application message. The message delivery module is used to sequentially deliver transaction messages to each product application system according to the transaction process. The transaction execution module is used by the product application system to execute transactions.

7. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the program, it implements the steps of the data transfer method according to any one of claims 1 to 5.

8. A computer-readable storage medium having a computer program stored thereon, characterized in that, When executed by a processor, the computer program implements the steps of the data transfer method according to any one of claims 1 to 5.

Images