A multi-modal multi-receiver data transmission routing method

Abstract

A multi-modal multi-receiver data transmission routing method belongs to the technical field of medical software data transmission, and includes the following steps: step 01, obtaining source information; step 02, judging whether the source information is a legitimate source; step 03, obtaining the source information type, and obtaining the receiver group according to the message type; step 04, setting the number of circulators according to the number of receiver groups; step 05, judging whether the circulator has been reset to zero, and if so, ending the loop; step 06, reading a receiver, judging whether to send a message to the read receiver; step 07, if it is judged in step 06 that a message is sent to the read receiver, entering the sending logic; step 08, if it is judged in step 06 that a message is not sent to the read receiver, then reducing the number of circulators by one, and then continuing step 06. The present invention can realize the flexibility of data routing distribution and improve the stability of data transmission.

Description

Technical Field

[0001] The present invention relates to the technical field of medical software data transmission, and in particular to a multi-modal multi-receiver data transmission routing method. Background Art

[0002] Currently, most software or devices with data forwarding functions on the market only have a single path with multiple receivers or a single path with a single receiver.

[0003] Most traditional data routing devices only have a single transmission method. For example, the queue (MQ) in the middleware only has a single channel to send or receive data. Although it has a broadcast method to distribute the same data to different recipients, its single communication method is still a shortcoming. For example, the internal data forwarding interface developed by most companies mostly has a single communication and a single recipient. Summary of the invention

[0004] The present invention provides a multi-modal multi-receiver data transmission routing method to solve the shortcomings of the above-mentioned prior art. Data is sent to one sender and multiple receivers, and multiple data sending modes are provided to the same receiver to ensure data transmission stability. Different three parties can be connected in different ways to achieve flexibility in data export.

[0005] In order to achieve the purpose of the present invention, the following technologies are proposed:

[0006] A multi-modal multi-receiver data transmission routing method, comprising the steps of:

[0007] Step 01, obtain source information;

[0008] Step 02, determine whether the source information is from a legitimate source, so as to perform security verification and switching on the information to achieve the purpose of filtering data.

[0009] Step 03, obtain the source information type, and obtain the recipient group according to the message type;

[0010] Step 04, setting the number of circulators according to the number of receiver groups. The circulator refers to a circulator that can obtain each receiver in the receiver group, so as to facilitate the processing of data reception of a single receiver.

[0011] Step 05, determine whether the circulator has returned to zero, if so, end the loop;

[0012] Step 06, read out a recipient, and determine whether to send a message to the read recipient;

[0013] Step 07, if it is determined in step 06 that a message is to be sent to the read recipient, then the sending logic is entered;

[0014] Step 08: If it is determined in step 06 that the message is not to be sent to the read recipient, the number of circulators is reduced by one, and then step 06 is continued.

[0015] Furthermore, in step 07, the sending logic steps are:

[0016] Step 070, obtain the recipient's buffer pool, which is a temporary storage location for data judgment when the message is sent. It has the characteristics of efficient caching but short storage time.

[0017] Step 071, determine whether the receiving party has a receiving method, if it is determined that the receiving party has a receiving method, proceed to step 072;

[0018] Step 072, obtain the flag receiving mode in the receiver's buffer pool, where the flag refers to the location of the main receiving mode, which is also the location that can be directly obtained when obtaining the sending mode.

[0019] Step 073, sending data according to the receiving mode of the flag bit in the receiving side buffer pool;

[0020] Step 074, determine whether the data sent in step 073 is successful, if successful, jump out, if not, go to step 075;

[0021] Step 075, determine whether the receiver has a backup receiving mode, if the receiver does not have a backup receiving mode, jump to step 0750, if the receiver has a backup receiving mode, jump to step 076;

[0022] Step 0750, storing the error data obtained in step 075 and issuing a notification;

[0023] Step 076, remove the current receiving mode on the flag in the receiver buffer pool, and then initiate an asynchronous return movement and push an exception notification;

[0024] Step 077, extract one of the backup receiving modes in the receiver buffer pool, and place the extracted backup receiving mode on the flag bit in the receiver buffer pool, and then return to step 072.

[0025] Furthermore, since the problem of non-existence of receiving modes does not occur in the buffer pool under normal circumstances, in order to cope with abnormal situations, the following steps are performed:

[0026] Step 0710, in step 071, if it is determined that the receiving party does not have a receiving mode, then the receiving mode of the receiving party in the configuration is obtained;

[0027] Step 0711, store the receiving mode of the receiver in the configuration obtained in step 0710 into the cache pool, and then enter step 072.

[0028] Further:

[0029] In step 077, when extracting one of the backup receiving modes in the receiver buffer pool, the extraction is performed in the order of the backup receiving modes.

[0030] Furthermore, the steps of the regression movement in step 076 are:

[0031] Step 0760, manufacturing simulation parameters;

[0032] Step 0761, determining whether a regression movement is required, if the regression movement is required, proceeding to step 0762, if the regression movement is not required, ending the regression movement;

[0033] Step 0762, sending simulation parameters to the failed receiving method;

[0034] Step 0763, determine whether the simulation parameters are sent successfully, if not, go to step 07630, if sent successfully, go to step 0764;

[0035] Step 07630, after the time waiter waits for 5 seconds, jumps to step 0762 and continues to send simulation parameters to the failed receiving method;

[0036] Step 0764, placing the failed receiving mode of the successfully received simulation parameter in the waiting-for-return position of the receiving side buffer pool;

[0037] Step 0765, determine whether it is the main receiving mode of the receiver, if it is the main receiving mode of the receiver, go to step 0766, if it is not the main receiving mode of the receiver, go to step 07650;

[0038] Step 07650, returning the extracted backup receiving mode to its original position, and then ending;

[0039] Step 0766, determining whether the receiving mode of the flag bit in the receiving buffer pool is being used, if the receiving mode of the flag bit in the receiving buffer pool is being used, proceeding to step 07660, if the receiving mode of the flag bit in the receiving buffer pool is not being used, proceeding to step 0767;

[0040] Step 07660, the timer waits for 1 second and then enters step 0766 again;

[0041] Step 0767, put the backup receiving mode on the flag bit in the receiver buffer pool back to its original position;

[0042] Step 0768, placing the failed reception mode of the successfully received simulation parameter on the to-be-returned position in the receiver buffer pool in step 0764 on the flag position in the receiver buffer pool.

[0043] Furthermore, the multi-mode multi-route configuration logic steps are:

[0044] Step 090, set the type for the source information;

[0045] Step 091, setting a corresponding receiver group according to the source party information type in step 090;

[0046] Step 092, for the receiver group set in step 091, set the receiving mode group corresponding to the receiver, and set the corresponding receiving address for the receiving mode group;

[0047] Step 093, setting a priority for each receiving mode in the receiving mode group obtained in step 092.

[0048] Furthermore, the source information has a fixed message header.

[0049] Furthermore, in step 093, as the priority number of the receiving mode decreases, the usage level of the receiving mode increases.

[0050] Further, in step 093, one of the receiving modes is set as the main priority.

[0051] The advantages of the above technical solution are:

[0052] The present invention can perform multi-channel data distribution according to the routing configuration logic, and also has the characteristics of multiple sending modes during distribution, so that different receivers can receive data. It also has multiple backup receiving modes to avoid the problem of data loss due to the abnormality of a single transmission mode. When the receiving mode is abnormal, a new receiving mode can be quickly switched, and the abnormal receiving mode can also be monitored to achieve automatic return after the abnormality is recovered. The present invention can set a variety of different transmission modes (such as MQ, http, database, channel, etc.) for a receiver, and can send a message to multiple different receivers, which greatly guarantees the flexibility of the interface and the stability of data transmission. In summary, the present invention can achieve the flexibility of data routing distribution and improve the stability of data transmission. BRIEF DESCRIPTION OF THE DRAWINGS

[0053] In order to make the objectives, technical solutions and advantages of the present invention more clear, the present invention will be further described in detail below with reference to the accompanying drawings.

[0054] Figure 1 The overall cycle flow chart of the multi-modal multi-receiver data transmission routing method is shown.

[0055] Figure 2 A logical flow chart of multi-modal data transmission is shown.

[0056] Figure 3 A logic flow diagram of the regressive motion is shown.

[0057] Figure 4 A diagram showing the layout of the receiver buffer pool.

[0058] Figure 5 A multi-modal multi-routing configuration logic flow chart is shown. DETAILED DESCRIPTION

[0059] like Figure 1 As shown, a multi-modal multi-receiver data transmission routing method comprises the steps of:

[0060] Step 01, obtain source information.

[0061] Step 02, determine whether the source information is from a legitimate source, so as to perform security verification and switching on the information to achieve the purpose of filtering data.

[0062] Step 03, obtain the source information type, and obtain the recipient group based on the message type.

[0063] Step 04, setting the number of circulators according to the number of receiver groups. The circulator refers to a circulator that can obtain each receiver in the receiver group, so as to facilitate the processing of data reception of a single receiver.

[0064] Step 05, determine whether the circulator has returned to zero, and if so, end the loop.

[0065] Step 06, read out a recipient, and determine whether to send a message to the read recipient.

[0066] Step 07: If it is determined in step 06 that a message is to be sent to the read recipient, the sending logic is entered.

[0067] Step 08: If it is determined in step 06 that the message is not to be sent to the read recipient, the number of circulators is reduced by one, and then step 06 is continued.

[0068] Among them, Figure 2 As shown, in step 07, the sending logic steps are:

[0069] Step 070, obtain the receiver's buffer pool. The buffer pool is a temporary storage location for data judgment when the message is sent. It has the characteristics of efficient caching but short storage time. The layout of the receiver's buffer pool is as follows: Figure 4 shown.

[0070] Step 071, determine whether the receiving party has a receiving method. If it is determined that the receiving party has a receiving method, proceed to step 072.

[0071] Under normal circumstances, the problem of no receiving mode in the buffer pool will not occur. In order to deal with abnormal situations, the following steps are performed:

[0072] Step 0710, in step 071, if it is determined that the receiving party does not have a receiving method, the receiving method of the receiving party in the configuration is obtained.

[0073] Step 0711, store the receiving mode of the receiver in the configuration obtained in step 0710 into the cache pool, and then enter step 072.

[0074] Step 072, obtain the flag receiving mode in the receiver's buffer pool, where the flag refers to the location of the main receiving mode, which is also the location that can be directly obtained when obtaining the sending mode.

[0075] Step 073, sending data according to the receiving mode of the flag bit in the receiving party's buffer pool.

[0076] Step 074, determine whether the data sent in step 073 is successful, if successful, jump out, if not, enter step 075.

[0077] Step 075, determine whether the recipient has a backup receiving method. If the recipient does not have a backup receiving method, jump to step 0750. If the recipient has a backup receiving method, jump to step 076.

[0078] Step 0750, stores the error data obtained in step 075 and issues a notification.

[0079] Step 076, remove the current receiving mode on the flag in the receiver buffer pool, and then initiate an asynchronous return movement and push an exception notification. The above-mentioned asynchronous means that in order not to affect the operation of the main event, another event is started to avoid interfering with the operation of the main event.

[0080] Step 077, extract one of the backup receiving modes in the receiver buffer pool, and place the extracted backup receiving mode on the flag in the receiver buffer pool, and then return to step 072. When extracting one of the backup receiving modes in the receiver buffer pool, the extraction is performed in the order of the backup receiving modes.

[0081] Among them, Figure 3 As shown, the steps of the regression movement in step 076 are:

[0082] Step 0760, manufacture simulation parameters.

[0083] Step 0761, determine whether regression movement is required. If regression movement is required, proceed to step 0762. If regression movement is not required, end the regression movement.

[0084] Step 0762, sending simulation parameters to the failed receiving method.

[0085] Step 0763, determine whether the simulation parameters are sent successfully. If not, go to step 07630. If sent successfully, go to step 0764.

[0086] Step 07630, after the timer waits for 5 seconds, jumps to step 0762 and continues to send simulation parameters to the failed receiving method.

[0087] Step 0764, placing the failed reception mode of the successfully received simulation parameters in the waiting-for-return position of the receiver buffer pool.

[0088] Step 0765, determine whether it is the main receiving mode of the receiver. If it is the main receiving mode of the receiver, go to step 0766. If it is not the main receiving mode of the receiver, go to step 07650.

[0089] Step 07650, returns the extracted backup receiving mode to its original position, and then ends.

[0090] Step 0766, determine whether the receiving method of the flag bit in the receiving party's buffer pool is being used. If the receiving method of the flag bit in the receiving party's buffer pool is being used, go to step 07660; if the receiving method of the flag bit in the receiving party's buffer pool is not being used, go to step 0767.

[0091] Step 07660, after the timer waits for 1 second, enters step 0766 again.

[0092] Step 0767, put the backup receiving mode on the flag bit in the receiver's buffer pool back to its original position.

[0093] Step 0768, placing the failed reception mode of the successfully received simulation parameter on the to-be-returned position in the receiver buffer pool in step 0764 on the flag position in the receiver buffer pool.

[0094] like Figure 5 As shown, the steps for multi-mode multi-route configuration logic are:

[0095] Step 090, setting a type for the source information, the source information has a fixed message header.

[0096] Step 091, setting the corresponding receiver group according to the source information type in step 090.

[0097] Step 092, for the recipient group set in step 091, set the receiving mode group corresponding to the recipient, and set the corresponding receiving address for the receiving mode group.

[0098] Step 093, setting a priority for each receiving mode in the receiving mode group obtained in step 092. As the number of priorities of the receiving modes decreases, the use level of the receiving modes increases. And one of the receiving modes needs to be set as the main priority.

[0099] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Obviously, those skilled in the art can make various changes and modifications to the present invention without departing from the spirit and scope of the present invention. Thus, if these modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to include these modifications and variations.

Claims

1. A multi-modal multi-receiver data transmission routing method, characterized in that: Includes steps: Step 01, obtain source information; Step 02, determine whether the source information is from a legitimate source, if it is legitimate, proceed to step 03, if not, end; Step 03, obtain the source party information type, and obtain the recipient party group according to the information type; Step 04, set the number of circulators according to the number of receiver groups; Step 05, determine whether the circulator has returned to zero, if so, end the loop; Step 06, read out a recipient, and determine whether to send a message to the read recipient; Step 07: If it is determined in step 06 that a message is to be sent to the read recipient, the sending logic is entered; In step 07, the sending logic steps are: Step 070, obtaining the receiver's buffer pool; Step 071, determine whether the receiving party has a receiving method, if it is determined that the receiving party has a receiving method, proceed to step 072; Step 072, obtaining the flag receiving mode in the receiver buffer pool; Step 073, sending data according to the receiving mode of the flag bit in the receiving side buffer pool; Step 074, determine whether the data sent in step 073 is successful, if successful, jump out, if not, go to step 075; Step 075, determine whether the receiver has a backup receiving mode, if the receiver does not have a backup receiving mode, jump to step 0750, if the receiver has a backup receiving mode, jump to step 076; Step 0750, storing the error data obtained in step 075 and issuing a notification; Step 076, remove the current receiving mode on the flag in the receiver buffer pool, and then initiate an asynchronous return movement and push an exception notification; Step 077, extract one of the backup receiving modes in the receiving side buffer pool, and place the extracted backup receiving mode on the flag bit in the receiving side buffer pool, and then return to step 072; Step 08: If it is determined in step 06 that the message is not to be sent to the read recipient, the number of circulators is reduced by one, and then step 06 is continued.

2. The multi-modal multi-receiver data transmission routing method according to claim 1, characterized in that: The method further includes step 0710. In step 071, if it is determined that the receiving party does not have a receiving mode, the receiving mode of the receiving party in the configuration is obtained; Step 0711, store the receiving mode of the receiver in the configuration obtained in step 0710 into the cache pool, and then enter step 072.

3. The multi-modal multi-receiver data transmission routing method according to claim 1, characterized in that: In step 077, when extracting one of the backup receiving modes in the receiver buffer pool, the extraction is performed in the order of the backup receiving modes.

4. The multi-modal multi-receiver data transmission routing method according to claim 1, characterized in that: The steps of the regression movement in step 076 are: Step 0760, manufacturing simulation parameters; Step 0761, determining whether a regression movement is required, if the regression movement is required, proceeding to step 0762, if the regression movement is not required, ending the regression movement; Step 0762, sending simulation parameters to the failed receiving method; Step 0763, determine whether the simulation parameters are sent successfully, if not, go to step 07630, if sent successfully, go to step 0764; Step 07630, after the time waiter waits for 5 seconds, jumps to step 0762 and continues to send simulation parameters to the failed receiving method; Step 0764, placing the failed receiving mode of the successfully received simulation parameter in the waiting-for-return position of the receiving side buffer pool; Step 0765, determine whether it is the main receiving mode of the receiver, if it is the main receiving mode of the receiver, go to step 0766, if it is not the main receiving mode of the receiver, go to step 07650; Step 07650, returning the extracted backup receiving mode to its original position, and then ending; Step 0766, determining whether the receiving mode of the flag bit in the receiving buffer pool is being used, if the receiving mode of the flag bit in the receiving buffer pool is being used, proceeding to step 07660, if the receiving mode of the flag bit in the receiving buffer pool is not being used, proceeding to step 0767; Step 07660, the timer waits for 1 second and then enters step 0766 again; Step 0767, put the backup receiving mode on the flag bit in the receiver buffer pool back to its original position; Step 0768, placing the failed reception mode of the successfully received simulation parameter on the to-be-returned position in the receiver buffer pool in step 0764 on the flag position in the receiver buffer pool.

5. The multi-modal multi-receiver data transmission routing method according to claim 1, characterized in that: If it is a multi-mode multi-route configuration, the following logical steps are adopted: Step 090, set the type for the source information; Step 091, setting a corresponding receiver group according to the source party information type in step 090; Step 092, for the receiver group set in step 091, set the receiving mode group corresponding to the receiver, and set the corresponding receiving address for the receiving mode group; Step 093, setting a priority for each receiving mode in the receiving mode group obtained in step 092.

6. The multi-modal multi-receiver data transmission routing method according to claim 5, characterized in that: The source message has a fixed message header.

7. The multi-modal multi-receiver data transmission routing method according to claim 5, characterized in that: In step 093, as the priority number of the receiving mode decreases, the usage level of the receiving mode increases.

8. The multi-modal multi-receiver data transmission routing method according to claim 5, characterized in that: In step 093, one of the receiving modes is set as the main priority.

Images