Message scheduling method, device and equipment during parallel period of new and old systems and medium

Abstract

This disclosure provides a method for scheduling messages during the parallel operation of old and new systems, relating to the field of information processing technology and applicable to the financial sector. The method includes: matching the target business application to which the received message belongs with a list of business applications to obtain a first matching result; if the first matching result indicates that the target business application belongs to the list of business applications, matching the message content of the message with the message processing specifications of the new system to obtain a second matching result; if the second matching result indicates that the message content conforms to the message processing specifications, matching the information of all participants in the message's transmission path with the information of participants who have deployed the new system and activated the target business application in the new system during the current time period to obtain a third matching result; and when the third matching result indicates that all participants have successfully matched, scheduling the message to the new system. This disclosure also provides a device, equipment, storage medium, and program product for scheduling messages during the parallel operation of old and new systems.

Description

Technical Field

[0001] This disclosure relates to the field of information processing, and can be used in the financial field. More specifically, it relates to a method, apparatus, device, medium, and program product for scheduling messages during the parallel operation of old and new systems. Background Technology

[0002] Currently, as enterprises undergo digital transformation and their demand for independent intellectual property rights intensifies, it is common for them to build new systems to replace old ones. When an enterprise has a complex organizational structure (e.g., involving branches distributed globally) or a wide variety of complex business operations, the replacement of the old system with a new one cannot be completed quickly. Furthermore, after the new system is built, sufficient traffic is needed to monitor its operation. If the implementation of a business requires the cooperation of multiple independently operating enterprises or organizations, and the new system can only interface with the new system, and the old system can only interface with the old system, then message routing during the parallel operation of the new and old systems will present many difficulties.

[0003] Interbank transactions by large commercial banks (e.g., large-value real-time payments, small-value batch payments) are typical examples of this type of transaction. Currently, the completion of interbank transactions involves at least two banks involved in the transaction, as well as a third-party institution (referred to as the "clearing intermediary" in this article) that supervises and clears interbank transactions. When upgrading existing systems for interbank transactions, large commercial banks face two challenges: firstly, with numerous internal branches, the construction of new internal systems needs to be gradual; secondly, since interbank transactions often involve multiple parties, the distribution of interbank messages during the parallel operation of new and old systems must consider not only the construction and operation of the new system within the bank itself, but also the construction and operation of the counterparty's new system. Therefore, the distribution of interbank messages during the parallel operation of new and old systems is extremely complex. Summary of the Invention

[0004] In view of the above problems, this disclosure provides a method, apparatus, device, medium and program product for scheduling messages during the parallel operation of new and old systems, to support the parallel operation of new and old systems, and to intelligently divert messages to the new system while ensuring that the system transformation does not affect the business scenarios and customer functions, so as to effectively support the transformation of new and old systems.

[0005] According to a first aspect of this disclosure, a method for scheduling messages during the parallel operation of old and new systems is provided. The method includes: receiving a message; matching the target service application to which the message belongs with a list of service applications to obtain a first matching result; if the first matching result indicates that the target service application belongs to the list of service applications, matching the message content of the message with the message processing specifications of the new system to obtain a second matching result; if the second matching result indicates that the message content conforms to the message processing specifications, matching the information of all participants in the transmission path of the message with the information of participants who have deployed the new system and have activated the target service application in the new system during the current time period to obtain a third matching result; and when the third matching result indicates that all participants have successfully matched, scheduling the message to the new system.

[0006] According to the method of this disclosure, the method further includes: setting the message processing specification; updating the message processing specification when receiving an update notification of the message processing specification; and sending a notification to the terminal device that the message processing function of the updated message processing specification is deployed in both the new system and the old system.

[0007] According to the method of this disclosure embodiment, the method further includes: scheduling the message to the old system if the second matching result indicates that the message content does not conform to the message processing specification; and scheduling the message to the old system if the second matching result indicates that the message content conforms to the message processing specification, but at least one participant in the third matching result fails to match.

[0008] According to embodiments of this disclosure, the process of matching all participants in the transmission path of the message with the information of participants who have deployed the new system and activated the target service application in the new system during the current time period to obtain a third matching result includes: matching all participants with a whitelist of participants who have deployed the new system; if all participants belong to the whitelist, checking the service application activated by each participant in the new system and the activation time period; and when it is determined that the service application activated by each participant in the new system includes the target service application, and the activation time period of the target service application of each participant in the new system includes the current time, it is determined that all participants have been successfully matched.

[0009] According to an embodiment of this disclosure, before receiving the message, the method further includes: obtaining information about the participants deploying the new system to obtain a whitelist; and obtaining the business applications and activation time periods activated by each participant in the whitelist in the new system.

[0010] According to embodiments of this disclosure, obtaining the business applications and activation time periods activated by each participant in the whitelist in the new system further includes: updating the activation time periods of first business applications activated by at least one first participant in the whitelist in the new system according to a preset strategy. The method further includes: controlling the first participant to run the first business application in the new system according to the updated activation time periods.

[0011] According to an embodiment of this disclosure, updating the activation time period of the first business application activated by at least one first participant in the whitelist in the new system according to a preset strategy includes: repeatedly performing the following operations until the grayscale percentage of the activation time period of the first business application of the first participant in the new system reaches 100%: obtaining the operation report data of the first business application activated by the first participant in the new system; and when the operation report data meets the operation upgrade conditions, extending the activation time period of the first business application in the first participant.

[0012] According to embodiments of this disclosure, obtaining information about the participants deploying the new system and obtaining a whitelist further includes: if the operational status data of a second business application opened by at least one second participant in the whitelist in the new system meets stability requirements, selecting at least one third participant from the participants to be deployed with a business feature that has a correlation with the business feature of the second participant that meets a preset condition; sending instruction information to the terminal device to the third participant to deploy the new system; and in response to the information that the third participant has completed the deployment of the new system, adding the information of the third participant to the whitelist to update the whitelist.

[0013] A second aspect of this disclosure provides a packet scheduling apparatus during the parallel operation of old and new systems. The apparatus includes a receiving module, a first matching module, a second matching module, a third matching module, and a scheduling module. The receiving module receives packets. The first matching module matches the target service application to which the packet belongs with a list of service applications to obtain a first matching result. The second matching module, if the first matching result indicates that the target service application belongs to the list of service applications, matches the packet content with the packet processing specifications of the new system to obtain a second matching result. The third matching module, if the second matching result indicates that the packet content conforms to the packet processing specifications, matches all participants in the packet's transmission path with information about participants who have deployed the new system and activated the target service application in the new system during the current time period to obtain a third matching result. The scheduling module, when the third matching result indicates that all participants are successfully matched, schedules the packet to the new system.

[0014] According to an embodiment of this disclosure, the scheduling module is further configured to: schedule the message to the old system if the second matching result indicates that the message content does not conform to the message processing specification; and schedule the message to the old system if the second matching result indicates that the message content conforms to the message processing specification, but at least one participant in the third matching result fails to match.

[0015] According to an embodiment of this disclosure, the third matching module is further configured to: match all participants with a whitelist that has deployed the new system; if all participants belong to the whitelist, check the business applications and activation time periods activated by each participant in the new system; and when the check determines that the business applications activated by each participant in the new system include the target business application, and the activation time period of the target business application of each participant in the new system includes the current time, determine that all participants have been successfully matched.

[0016] A third aspect of this disclosure provides an electronic device. The electronic device includes one or more processors and a memory. The memory is used to store one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors perform the methods described above.

[0017] A fourth aspect of this disclosure also provides a computer-readable storage medium having executable instructions stored thereon, which, when executed by a processor, cause the processor to perform the methods described above.

[0018] A fifth aspect of this disclosure also provides a computer program product, including a computer program that, when executed by a processor, implements the above-described method.

[0019] The above-described one or more embodiments have the following advantages or beneficial effects: By matching the application to which the message belongs, matching the message content with the message processing specifications, and analyzing the participants in the message transmission path, this disclosure can, while ensuring normal business functions, allow as much traffic as possible to pass through the new system, effectively supporting the parallel operation of the old and new systems, and providing sufficient traffic data for observing the operation of the new system. Attached Figure Description

[0020] The foregoing contents, as well as other objects, features, and advantages of this disclosure, will become clearer from the following description of embodiments with reference to the accompanying drawings, in which:

[0021] Figure 1 The illustration schematically shows the transmission path of a cross-industry message according to an embodiment of the present disclosure;

[0022] Figure 2 The flowchart illustrates a method for scheduling messages during parallel operation of old and new systems according to an embodiment of the present disclosure.

[0023] Figure 3 This illustration shows a flowchart illustrating information about the participants in the transmission path of the matching message and the participants who have currently activated the target service application in the new system, according to an embodiment of this disclosure.

[0024] Figure 4 This illustration schematically shows the method flow for obtaining a whitelist and the service activation time periods of each participating party in another embodiment of the present disclosure;

[0025] Figure 5 This illustration schematically shows a method flow for obtaining the first service activation time period in the first participating party in one embodiment of the present disclosure;

[0026] Figure 6 This illustration schematically shows a method flow for obtaining a whitelist in one embodiment of the present disclosure;

[0027] Figure 7 A flowchart illustrating a method for scheduling cross-industry business messages during parallel operation of a new and old system, according to another embodiment of this disclosure, is shown schematically.

[0028] Figure 8 This schematically illustrates a structural block diagram of a message scheduling apparatus for parallel operation of old and new systems according to embodiments of the present disclosure; and

[0029] Figure 9 A block diagram of an electronic device suitable for implementing a message scheduling method during parallel operation of new and old systems according to embodiments of the present disclosure is shown schematically. Detailed Implementation

[0030] The embodiments of the present disclosure will now be described with reference to the accompanying drawings. However, it should be understood that these descriptions are exemplary only and are not intended to limit the scope of the disclosure. In the following detailed description, numerous specific details are set forth to provide a thorough understanding of the embodiments of the present disclosure for ease of explanation. However, it will be apparent that one or more embodiments may be practiced without these specific details. Furthermore, descriptions of well-known structures and techniques are omitted in the following description to avoid unnecessarily obscuring the concepts of the present disclosure.

[0031] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit this disclosure. The terms “comprising,” “including,” etc., as used herein indicate the presence of the stated features, steps, operations, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, or components.

[0032] All terms used herein (including technical and scientific terms) have the meanings commonly understood by those skilled in the art, unless otherwise defined. It should be noted that the terms used herein are to be interpreted in a manner consistent with the context of this specification, and not in an idealized or overly rigid way.

[0033] When expressions such as "at least one of A, B, and C" are used, they should generally be interpreted in accordance with the meaning commonly understood by those skilled in the art (e.g., "a system having at least one of A, B, and C" should include, but is not limited to, systems having only A, only B, only C, A and B, A and C, B and C, and / or systems having A, B, and C, etc.). The terms "first," "second," etc., used herein are for distinction only and have no limiting meaning, and the number of any elements in the accompanying drawings is for illustrative purposes only and not for limitation.

[0034] Figure 1 The illustration shows the transmission path of cross-industry messages according to an embodiment of the present disclosure.

[0035] Combination Figure 1 Interbank transactions involve not only the two banks involved in the transaction but also the clearing intermediaries that supervise and clear interbank transactions. The transmission of an interbank transaction message must pass through at least the commercial bank's own system (head office or a branch), the central switching system deployed or controlled by the clearing intermediary (e.g., the clearing system controlled by the clearing intermediary), and the counterparty's system deployed at other banks (head office or a branch). Furthermore, when interbank transaction messages are routed, the transmission path is from new system to new system, and from old system to old system.

[0036] Commercial banks often have numerous branches. When upgrading their own systems to replace old ones with new ones, they typically start by deploying the new system in specific areas (e.g., certain branches) and only expand to more branches after the new system is in stable operation. The process for upgrading other banks' systems is similar.

[0037] The clearing intermediary's transfer hub system also has a corresponding system that interfaces with the old and new systems of commercial banks.

[0038] The message scheduling method, apparatus, device, medium, and program products provided in this disclosure for parallel operation of old and new systems can be applied to... Figure 1 The processing of cross-industry business messages shown can effectively and automatically divert cross-industry business messages received by commercial banks during the parallel operation of the old and new cross-industry business systems. This ensures that the new system has as much traffic as possible after it is put into production, while minimizing the impact of system transformation on the use of cross-industry business functions.

[0039] It should be noted that, Figure 1 The application scenario of cross-industry business messages shown is merely an example. The message scheduling method, apparatus, device, medium, and program products provided in this disclosure for parallel operation of old and new systems can be used in the financial field, as well as in any field other than the financial field. This disclosure does not limit the application field.

[0040] The following will be based on Figure 1 Taking the processing of cross-industry business messages as an example, through... Figures 2-7 The message scheduling method for parallel operation of old and new systems according to embodiments of this disclosure will be described in detail. It should be noted that the sequence numbers of each operation in the following methods are for descriptive purposes only and should not be considered as indicating the execution order of the operations. Unless explicitly stated otherwise, the method does not need to be executed in the exact order shown.

[0041] Figure 2 The flowchart illustrates a method for scheduling messages during parallel operation of a new and old system according to an embodiment of the present disclosure.

[0042] like Figure 2 As shown, the method may include operations S210 to S280.

[0043] First, operate S210 to receive messages.

[0044] Then, in operation S220, the target business application to which the message belongs is matched with the list of business applications to obtain the first matching result.

[0045] In one embodiment, when this disclosure is applied to inter-industry business, the business application list includes the applications where the inter-industry business is located, including but not limited to: interbank clearing interconnection front-end, interbank clearing interconnection front-end interbank online banking interconnection access and outgoing service group, interbank clearing interconnection front-end cross-border currency service group, interbank clearing interconnection front-end interbank accounting service group, interbank clearing interconnection front-end interbank accounting service group, interbank clearing interconnection front-end interbank large and small value service group, domestic interbank clearing, domestic interbank clearing interbank intelligent routing service group, domestic interbank clearing large and small value business service group, domestic interbank clearing online banking interconnection business service group, and domestic interbank clearing online banking interconnection business service group.

[0046] In operation S230, if the first matching result indicates that the target business application belongs to the business application list, the message content of the matching message is matched with the message processing specifications of the new system to obtain the second matching result.

[0047] This business application list is used to filter out messages that need to be separated between the old and new systems. The filtered messages are then parsed to obtain their content. Finally, the message content is checked against the new system's message processing specifications to determine if the message content is suitable for the new system to handle.

[0048] In one embodiment, for cross-industry business messages, the parsed message content includes, but is not limited to: data partition code, sending institution code, payment detail sequence number, periodic debit / credit batch number, message entrustment date, sending bank code, receiving bank code, sending agent bank, receiving agent bank, sending agent clearing bank, receiving agent clearing bank, intermediary bank code, third-party bank code, message amount, message business type, message type, business type code, message status, message communication status, message receipt status, message status appendix, and message status appendix. Add rejection code, entrustment date, type of clearing service, netting date, netting session, clearing intermediary clearing date, closing mark, reporting date, reporting mark, previous reporting mark, unique ID, debit account / card number, credit account / card number, debit account name, credit account name, transaction code, major transaction number, minor transaction number, reporting date, reporting time, receipt date, receipt time, status last update date, last adjustment date, last adjustment time, closing date, summary, timestamp, service interface or terminal number.

[0049] Message processing specifications may include requirements for at least one of the message contents listed above. For example, a message processing specification may require that the message type be: a version or several versions of a message in a High Value Payment System (HVPS), or a version or several versions of a message in a Bulk Electronic Payment System (BEPS).

[0050] In operation S240, it is determined whether the message content in the second matching result conforms to the message processing specification. If yes, execution continues; if no, in operation S280, the message is scheduled to the old system.

[0051] In one embodiment, the message processing specifications used in the above operations can be pre-set and continuously updated.

[0052] Specifically, in one embodiment, the message processing specifications of the new system can be set according to the processing requirements of the new system. Then, when an update notification of the message processing specifications is received, the message processing specifications are updated, and a notification is sent to the terminal device instructing the enterprise to deploy the message processing functions of the updated message processing specifications in both the new and old systems.

[0053] In embodiments of this disclosure, when adding updated message processing functions to a new system, the updated message processing functions are also added to the old system simultaneously.

[0054] Specifically, when a new system replaces an old system, it often doesn't completely replicate the functionality of the old system. Sometimes, considering the long operating history of the old system, it may have accumulated some redundant or complex settings. When deploying the new system, adjustments to some functions may be made without affecting business requirements. This can lead to differences in message processing specifications between the new and old systems. Furthermore, to meet constantly changing business scenarios and needs, and to adapt to new internal and external operating environments, the new system may also include business functions not present in the old system. Simultaneously, to ensure the normal operation of business when the new and old systems run in parallel, business functions not present in the old system may also be added as a backup solution.

[0055] In cross-industry transactions, notifications of message processing specification updates typically originate from clearing intermediaries. Upon receiving these updates, commercial banks will modify the message processing specifications in their new systems accordingly and update the message processing functions of the new systems accordingly. Simultaneously, to ensure that messages can still pass through the old system even when the new system cannot process them (e.g., if the counterparty has not yet activated the new system), the business functions of the old system will also be updated accordingly.

[0056] In operation S250, if the second matching result indicates that the message content conforms to the message processing specification, the information of all participants in the transmission path of the matched message and the participants who have deployed the new system and opened the target business application in the new system during the current time period is used to obtain the third matching result.

[0057] The participants in the message transmission path can be obtained from the parsed message content. For example, from the data partition code, sending organization code, sending bank number, receiving bank number, sending agent bank, receiving agent bank, sending agent clearing bank, receiving agent clearing bank, intermediary bank number, third-party bank number, and clearing intermediary institution's clearing date in the message content of the example above, it can be deduced that the message transmission path includes the sending bank, sending agent bank, sending agent clearing bank, receiving agent clearing bank, intermediary bank, third-party bank, receiving bank, and clearing intermediary institution, and information on each participant can be obtained. Figure 1 The participants in the cross-bank message transmission path shown can be: the head office or a branch of this bank system as shown below, the clearing intermediary, and the head office or a branch of the counterparty bank system as shown below.

[0058] Next, in operation S260, determine whether all participants in the third matching result have been successfully matched. If yes, then execute operation S270; otherwise, execute operation S280.

[0059] In operation S270, when the third matching result indicates that all participants have successfully matched, the scheduling message is sent to the new system.

[0060] In operation S280, if the second matching result indicates that the message content does not conform to the message processing specification, the message is scheduled to the old system; and if the second matching result indicates that the message content conforms to the message processing specification, but at least one participant in the third matching result fails to match, the message is scheduled to the old system.

[0061] As can be seen, in this embodiment of the disclosure, determining whether a message can pass through the new system requires at least three aspects: 1) determining whether the message involves services in the transformation between the old and new systems through the business application list; 2) the message must conform to the message processing specifications of the new system; 3) the message must be able to pass through the new system, that is, all participants in the message transmission path have deployed the new system and activated the target business application, and the target business application is currently running in the new systems of all participants. In this way, this embodiment of the disclosure can intelligently enable as much traffic as possible to pass through the new system while ensuring normal business functions, effectively supporting the parallel operation of the old and new systems, and providing sufficient traffic data for the operation observation of the new system.

[0062] Figure 3 This illustration shows a flowchart illustrating the information of the participants in the transmission path of the matching message in operation S250 and the participants who have currently activated the target service application in the new system, according to an embodiment of this disclosure.

[0063] like Figure 3 As shown, according to this embodiment, operation S250 may include operations S251 to S257.

[0064] In operation S251, all participants in the message transmission path are matched with the whitelist of those who have deployed the new system.

[0065] Then, in operation S252, determine whether each of the aforementioned participants belongs to the whitelist. If yes, then execute operation S253; otherwise, execute operation S257.

[0066] When operating S253, if all participants are on the whitelist, check the business applications and activation periods that each participant has enabled in the new system.

[0067] In operation S254, check whether the business applications activated by each participant in the new system include the target business application. If yes, proceed to operation S255; otherwise, proceed to operation S257.

[0068] In operation S255, if each participant among all the aforementioned participants activates a business application in the new system that includes the target business application, check whether the activation time period of each participant's target business application in the new system includes the current time. If yes, proceed to operation S256; otherwise, proceed to operation S257.

[0069] In some embodiments, after a participant deploys a new system or a business application within a new system, there is a period of time required for observation and use of the new system. This allows the participant to gradually increase the usage of the business application in the new system through a canary rollout approach, ensuring a smooth transition in providing services to customers. Therefore, it is necessary to check whether the activation period for each participant's target business application in the new system includes the current time.

[0070] For example, in inter-industry transactions, the opening hours for large-value and small-value transactions are not entirely consistent. Large-value transactions (such as large inter-bank transactions) are typically targeted at institutional clients and are usually only available during specific time periods on weekdays. Small-value transactions, on the other hand, are generally available without time restrictions. For transactions involving large values, it is essential to check whether the customer's application for the large-value transaction was made within the permitted transaction period.

[0071] In operation S256, it is confirmed that all the aforementioned participants have successfully matched, meaning that all participants in the message transmission path have deployed the new system, and these participants have also activated the target service application in the new system during the current time period. Accordingly, the message can be processed through the new system.

[0072] In operation S257, if the third matching result is determined to be a match failure, then in operation S280, the message can be scheduled to the old system.

[0073] This disclosure addresses intelligent packet routing in complex scenarios where old and new systems operate in parallel. It addresses situations where the launch of a business application in the new system might restrict its runtime. This routing ensures that the service delivery of business functions remains normal while aligning with the gradual rollout of the new system's gray-scale testing in complex scenarios.

[0074] Figure 4 The illustration schematically shows the method flow for obtaining a whitelist and the service activation time periods of each participant in another embodiment of the present disclosure.

[0075] like Figure 4 As shown, combined with Figure 2 The method of this disclosure embodiment may also include operations S410 and S420 at least before operation S250.

[0076] By operating the S410, information about the participants in deploying the new system is obtained, and a whitelist is generated.

[0077] When operating S420, obtain the business applications and activation time periods that each participant in the whitelist has activated in the new system.

[0078] In some embodiments, the business applications and activation periods that each participant activates in the new system can be pre-registered manually.

[0079] In other embodiments, after initially recording the business applications and activation time periods activated by each participant in the new system, the activation time periods of the first business applications activated by at least one first participant in the whitelist in the new system can be automatically updated according to a preset strategy (e.g., user operation, or based on the operation status), while controlling the first participant to run the first business applications in the new system according to the updated activation time periods.

[0080] Figure 5 The illustration schematically shows the method flow for obtaining the first service activation time period of the first participant in operation S420 of an embodiment of the present disclosure.

[0081] like Figure 5 As shown, according to this embodiment, operation S420 may include operations S421 to S424.

[0082] First, in operation S421, obtain the operation report data of the first participant opening the first business application in the new system.

[0083] Then, in operation S422, when the operation report data meets the conditions for operation upgrade, the activation period of the first business application in the first participant is extended. For example, if the operation report data shows that the average traffic of the first business application in the new system reaches a certain percentage (e.g., 80%) of the traffic of that business within a certain period of time (e.g., one month) and the operation is stable, the activation period of the first business application in the first participant can be automatically extended.

[0084] Next, in operation S423, it is determined whether the gray-scale ratio of the first business application of the first participant in the new system during the activation period reaches 100%. If not, operations S421 to S423 are executed in a loop. If yes, the loop is broken and operation S424 is executed.

[0085] In operation S424, it is determined that the activation time period of the first business application of the first participant in the new system will no longer change.

[0086] This approach enables gray-scale control and a smooth transition during the first service activation period for the first participating party. Furthermore, in this embodiment, by checking the corresponding service activation period of the participating parties in the message transmission path within the new system, the message routing can be matched with the gray-scale time control of the new system.

[0087] Figure 6 The illustration schematically shows the method flow of obtaining a whitelist by operation S410 in one embodiment of the present disclosure.

[0088] like Figure 6 As shown, according to this embodiment, operation S410 may include operations S411 to S413.

[0089] In operation S411, if the running status data of the second business application opened by at least one second participant in the whitelist in the new system meets the stability requirements, at least one third participant whose business characteristics are correlated with the business characteristics of the second participant and meet the preset conditions is selected from the participants to be deployed in the new system.

[0090] The business characteristics of each participant can be measured based on one or more business metrics. The correlation meets the preset conditions, which can be achieved by calculating the correlation coefficient between business characteristics, or by ranking the participants from one or more dimensions of business metrics and selecting the Top N participants.

[0091] Then, by operating S412, instructions are sent to the terminal devices of the maintenance personnel to deploy the new system to the third party.

[0092] In operation S413, in response to information that a third party has completed the deployment of a new system, the third party is added to the whitelist to update the whitelist.

[0093] This disclosure embodiment can collect traffic data of corresponding functions in the new system, perform automatic analysis and processing, intelligent learning and judgment, summarize and analyze the data diversion within a certain time period, and automatically provide information on the participants for the next production launch based on the correlation of business characteristics, gradually expand the scope of production launch, and provide direction for the expansion of the new system's production launch.

[0094] Furthermore, by continuously updating the whitelist, the packet routing in this embodiment can be matched with the gradual expansion of the new system.

[0095] Figure 7 A flowchart illustrating a method for scheduling cross-industry business messages during parallel operation of a new and old system, according to another embodiment of this disclosure, is shown schematically. Those skilled in the art will understand that... Figure 7 The examples shown are merely illustrative and do not constitute a limitation of this disclosure.

[0096] like Figure 7 As shown, the main shunt switch in this scheduling method is divided into two types: "0-off" and "1-shunt". Among them, the "0-off" switch has a higher priority than the "1-shunt" switch.

[0097] "0-Off": This means that no traffic splitting between the old and new systems is performed. For example, if you manually set it to turn off automatic traffic splitting, all received packets will go through the old system.

[0098] "1-Diversion": This means that by intelligently analyzing the received packets, it is determined whether to schedule the packets to the new system or the old system.

[0099] When "1-Diversion" is enabled, received packets can be intelligently diverted between the new and old systems. Specifically, in Figure 7 The example illustrates five traffic splitting rules. Rule 1, "split traffic according to switch settings," is based on the previously mentioned... Figures 2-6 The implementation plan is determined based on the method shown. Rule 2, "distributing according to the original message," mainly targets the return message of a single message, achieving the goal of returning the message along its original path by tracing the original message. Rules 3, 4, and 5 are mainly supplementary distribution rules. For example, when a notification is received requesting the suspension of a new system function, Rule 4 can be activated to distribute all messages to the existing system; another example is when the new system completely replaces the old system, it is no longer necessary to judge the message every time, and Rule 5 can be activated to directly distribute the received message to the new system; yet another example is when the operating traffic is high and both the old and new systems can handle the messages, Rule 3 can be activated to distribute the messages to the new or old system according to the load balancing mechanism, which can achieve the purpose of system expansion.

[0100] Under the following rules, according to the embodiments of this disclosure, intelligent routing analysis and automated switching rule judgment are performed, including: obtaining the traffic splitting parameters of the new and old systems, parsing the packet content through a program, and then performing matching. Matching is divided into multiple levels: First, if the packet content does not match the traffic splitting parameters of the new system, the old system is used; otherwise, the grayscale switch configuration is retrieved to proceed to the next grayscale step judgment. The next grayscale judgment considers that some functions have not been implemented in the new system, or have limited activation times, etc., requiring further verification. This can be done by matching the service type encoding field and the service activation period. If no match is found, the old system is used. If a match is found, the next step is to determine whether each participant in the transmission path has deployed the new system and activated the corresponding function process. For example, whitelist information is obtained, which may include information about each participant within the bank (head office, branches, and agent banks), and may also include information about counterpart banks. Next, the whitelist and grayscale time are matched. If all participants match the whitelist and the grayscale time, the traffic is split to the new system; otherwise, the old system is used.

[0101] Rule 2 automatically compares the routing paths of the reverse transmission message and the original message based on the accounting records of the diverted data in the old and new systems, ensuring that the reverse transmission message returns along the original transmission path of the original message.

[0102] For a typical interbank large-value remittance message, the items that need to be checked according to the rules set in Rule 1 can be exemplified as follows: 3.1 Check the legality of the large-value ordinary credit instruction; 3.2 Check the receiving region's permission to open large-value payment services; 3.3 Check the receiving institution's permission to open interbank payment services; 3.4 Check if the business type / category supports large-value ordinary credit instructions; 3.5 Check the initiating bank's system permission to open large-value payment services; 3.6 Check the receiving bank's system permission to open large-value payment services; 3.7 Check the initiating bank's system permission to open large-value payment services. 3.8 Check the system permissions of the receiving bank to open the large-value payment business system; 3.9 Check whether the receiving bank has joined the new system; 3.10 Check the direct connection permissions between the initiating bank and the receiving bank; 3.11 Check the participation status of the receiving bank in the large-value payment business system; 3.12 Register the large-value ordinary credit instruction; 3.13 Check the branch's liquidity limit; 3.14 Generate a large-value ordinary interbank remittance message for the large-value ordinary credit instruction; 3.15 Format the message and send it; 3.16 Update the reporting status of the large-value ordinary credit instruction; 3.17 Accumulate the branch's liquidity limit.

[0103] Rule 1 also allows for setting exception handling procedures, including: 3.1T, when the instruction check is invalid, display the message "Instruction check failed"; 3.2T, when the large-value payment business permission check fails, display the message "Large-value payment business is not available in this region"; 3.3T, when the receiving institution's interbank payment business permission check fails, display the message "Interbank payment business is not available at this branch in this region"; 3.4T, when the business type / business category supports large-value ordinary credit instruction check fails, display the message "This business type cannot be used for this transaction"; 3.5T, initiating... When the verification of the large-value payment system access for the initiating bank fails, the message "The initiating bank has not joined the large-value payment system" will be displayed (3.6T). Similarly, when the verification of the large-value payment system access for the receiving bank fails, the message "The receiving bank has not joined the large-value payment system" will be displayed (3.7T). When the verification of the large-value payment system access for the initiating bank and the clearing bank fails, the message "The initiating bank and the clearing bank have not joined the large-value payment system" will be displayed (3.8T). Finally, when the verification of the large-value payment system access for the receiving bank and the clearing bank fails, the message "The receiving bank and the clearing bank have not joined the large-value payment system" will be displayed (3.8T). In the "Large-Value Payment System," at 3.9T, when the receiving bank has not joined the new system, the system prompts "The receiving bank has no permission to receive this message." At 3.10T, when the sending bank checks and finds no direct connection permission to the receiving bank, the system prompts "The initiating bank has no permission to initiate or the receiving bank has no permission to receive this message." At 3.11T, when checking and finding that the receiving bank has not enabled interbank payment services, the system prompts "The receiving party has not enabled interbank payment services." At 3.12T, when an anomaly occurs in saving large-value ordinary credit instruction information, an anomaly message is printed and reported to monitoring. At 3.13T, when the liquidity check fails or is unknown, a registration is made. Liquidity management pending release instruction, 3.14T: Message sending failure is generated, error message is printed, reported to monitoring, and the status of the large-amount ordinary credit instruction packet record and the large-amount ordinary credit instruction record is updated to "sending failed". 3.15T: Message sending failure is generated, error message is printed, reported to monitoring, and the status of the large-amount ordinary credit instruction packet record and the large-amount ordinary credit instruction record is updated to "sending failed". 3.16T: An error occurred in the large-amount ordinary credit instruction record, error message is printed, reported to monitoring, 3.17T: Accumulated branch liquidity quota failed and needs to be retried. This disclosed embodiment can also analyze and process abnormal situations to determine the next solution.

[0104] This disclosed embodiment takes into account that during the parallel operation of the old and new systems, the old and new systems need to run synchronously for a period of time and simultaneously support message data diversion and corresponding accounting processing. Through data analysis and automated switching strategy design, data diversion is completed and problems are ensured, which complements and does not conflict with the distribution strategy of completely replacing the old system. It can support automatic message sorting for cross-bank large and small value transactions between the old and new systems, and modify the functions corresponding to large and small value messages. By using technical identification methods, the sorting process is automatically completed, improving the original technology's inflexible rule configuration and automatic processing functions, saving time costs, and improving the business processing efficiency of operators.

[0105] Based on the packet scheduling methods for parallel operation of old and new systems as described in the above embodiments, this disclosure also provides a packet scheduling apparatus for parallel operation of old and new systems. The following will be combined with... Figure 8 The device is described in detail.

[0106] Figure 8 The schematic diagram illustrates a structural block diagram of a message scheduling device 800 during parallel operation of old and new systems according to an embodiment of the present disclosure.

[0107] like Figure 8 As shown, according to embodiments of this disclosure, the device 800 may include a receiving module 810, a first matching module 820, a second matching module 830, a third matching module 840, and a scheduling module 850. According to other embodiments of this disclosure, the device 800 may further include a message processing specification management module 860, a whitelist acquisition module 870, and / or an activation time grayscale management module 880. According to embodiments of this disclosure, the device 800 can implement the aforementioned... Figures 2-6 The scheduling method described.

[0108] The receiving module 810 is used to receive messages. In one embodiment, the receiving module 810 can perform the operation S210 described above.

[0109] The first matching module 820 is used to match the target service application to which the message belongs with the service application list to obtain the first matching result. In one embodiment, the first matching module 820 can perform the operation S220 described above.

[0110] The second matching module 830 is used to match the message content of the message with the message processing specifications of the new system if the first matching result indicates that the target business application belongs to the business application list, and obtain the second matching result. In one embodiment, the second matching module 830 can perform the operation S230 described above.

[0111] The third matching module 840 is used to match the information of all participants in the transmission path of the message with the participants who have deployed the new system and activated the target business application in the new system during the current time period, if the second matching result indicates that the message content conforms to the message processing specification, to obtain the third matching result. In one embodiment, the third matching module 840 can perform the operation S250 described above.

[0112] The scheduling module 850 is used to schedule the message to the new system when the third matching result indicates that all participants have successfully matched. In one embodiment, the scheduling module 850 can perform the operation S270 described above.

[0113] According to embodiments of this disclosure, the scheduling module 850 is further configured to: schedule the message to the old system if the second matching result indicates that the message content does not conform to the message processing specification; and schedule the message to the old system if the second matching result indicates that the message content conforms to the message processing specification, but at least one participant in the third matching result fails to match. In one embodiment, the scheduling module 850 may perform the operation S280 described above.

[0114] The third matching module 840 is further configured to: match all participants with a whitelist of participants that have deployed the new system; if all participants are on the whitelist, check the business applications and activation periods activated by each participant in the new system; and when the check determines that the business applications activated by each participant in the new system include the target business application, and the activation period of the target business application of each participant in the new system includes the current time, determine that all participants have successfully matched. In one embodiment, the third matching module 840 may execute operations S251 to S257 as described above.

[0115] The whitelist acquisition module 870 is used to acquire the participants in deploying the new system and obtain the whitelist.

[0116] In some embodiments, the whitelist acquisition module 870 is further configured to: if the running status data of the second business application opened by at least one second participant in the whitelist in the new system meets the stability requirements, select at least one third participant from the participants to be deployed in the new system whose business characteristics are correlated with the business characteristics of the second participant according to a preset condition; send instruction information to the terminal device to the third participant to deploy the new system; and in response to the information that the third participant has completed the deployment of the new system, add the third participant to the whitelist to update the whitelist. In one embodiment, the whitelist acquisition module 870 may perform operations S411 to S413 as described above.

[0117] The activation time grayscale management module 880 is used to obtain the business applications and activation time periods activated by each participant in the whitelist in the new system.

[0118] In some embodiments, the activation time grayscale management module 880 is further configured to: update the activation time period of the first business application activated by at least one first participant in the whitelist in the new system according to a preset strategy, and control the first participant to run the first business application in the new system according to the updated activation time period.

[0119] In other embodiments, the activation time grayscale management module 880 is also used to repeatedly perform the following operations until the grayscale ratio of the activation time period of the first business application of the first participant in the new system reaches 100%: obtaining the operation report data of the first participant activating the first business application in the new system; and when the operation report data meets the operation upgrade conditions, extending the activation time period of the first business application in the first participant. In one embodiment, the activation time grayscale management module 880 can perform the operations S421 to S424 described above.

[0120] The message processing specification management module 860 is used to: set message processing specifications; update message processing specifications when an update notification is received; and send a notification to the terminal device that the message processing function with the updated message processing specifications is deployed in both the new and old systems.

[0121] According to embodiments of this disclosure, any and multiple modules among the receiving module 810, the first matching module 820, the second matching module 830, the third matching module 840, the scheduling module 850, the message processing specification management module 860, the whitelist acquisition module 870, and the activation time grayscale management module 880 can be combined into one module, or any one of these modules can be split into multiple modules. Alternatively, at least some of the functions of one or more of these modules can be combined with at least some of the functions of other modules and implemented in one module. According to embodiments of this disclosure, at least one of the receiving module 810, the first matching module 820, the second matching module 830, the third matching module 840, the scheduling module 850, the message processing specification management module 860, the whitelist acquisition module 870, and the activation time grayscale management module 880 can be at least partially implemented as hardware circuits, such as field-programmable gate arrays (FPGAs), programmable logic arrays (PLAs), systems-on-a-chip, systems-on-a-substrate, systems-on-package, application-specific integrated circuits (ASICs), or any other reasonable means of integrating or packaging circuits, or implemented in software, hardware, or firmware, or in any appropriate combination of any of these three implementation methods. Alternatively, at least one of the receiving module 810, the first matching module 820, the second matching module 830, the third matching module 840, the scheduling module 850, the message processing specification management module 860, the whitelist acquisition module 870, and the activation time grayscale management module 880 can be at least partially implemented as a computer program module, which can perform corresponding functions when the computer program module is run.

[0122] Figure 9 A block diagram of an electronic device 900 suitable for implementing a message scheduling method during parallel operation of new and old systems according to embodiments of the present disclosure is shown schematically.

[0123] like Figure 9 As shown, an electronic device 900 according to an embodiment of the present disclosure includes a processor 901, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 902 or a program loaded from a storage portion 908 into a random access memory (RAM) 903. The processor 901 may include, for example, a general-purpose microprocessor (e.g., a CPU), an instruction set processor and / or an associated chipset and / or a special-purpose microprocessor (e.g., an application-specific integrated circuit (ASIC)), etc. The processor 901 may also include onboard memory for caching purposes. The processor 901 may include a single processing unit or multiple processing units for performing different actions of the method flow according to an embodiment of the present disclosure.

[0124] RAM 903 stores various programs and data required for the operation of electronic device 900. Processor 901, ROM 902, and RAM 903 are interconnected via bus 904. Processor 901 performs various operations of the method flow according to embodiments of the present disclosure by executing programs in ROM 902 and / or RAM 903. It should be noted that the programs may also be stored in one or more memories other than ROM 902 and RAM 903. Processor 901 may also perform various operations of the method flow according to embodiments of the present disclosure by executing programs stored in said one or more memories.

[0125] According to embodiments of this disclosure, the electronic device 900 may further include an input / output (I / O) interface 905, which is also connected to a bus 904. The electronic device 900 may also include one or more of the following components connected to the I / O interface 905: an input section 906 including a keyboard, mouse, etc.; an output section 907 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 908 including a hard disk, etc.; and a communication section 909 including a network interface card such as a LAN card, modem, etc. The communication section 909 performs communication processing via a network such as the Internet. A drive 910 is also connected to the I / O interface 905 as needed. A removable medium 911, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed on the drive 910 as needed so that computer programs read from it can be installed into the storage section 908 as needed.

[0126] This disclosure also provides a computer-readable storage medium, which may be included in the device / apparatus / system described in the above embodiments; or it may exist independently and not assembled into the device / apparatus / system. The computer-readable storage medium carries one or more programs that, when executed, implement the method according to the embodiments of this disclosure.

[0127] According to embodiments of this disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium, such as including, but not limited to: portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this disclosure, the computer-readable storage medium may be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. For example, according to embodiments of this disclosure, the computer-readable storage medium may include ROM 902 and / or RAM 903 and / or one or more memories other than ROM 902 and RAM 903 described above.

[0128] Embodiments of this disclosure also include a computer program product comprising a computer program containing program code for performing the methods shown in the flowchart. When the computer program product is run on a computer system, the program code is used to cause the computer system to implement the methods provided in the embodiments of this disclosure.

[0129] When the computer program is executed by the processor 901, it performs the functions defined in the system / apparatus of this disclosure embodiments. According to embodiments of this disclosure, the systems, apparatuses, modules, units, etc., described above can be implemented by computer program modules.

[0130] In one embodiment, the computer program may rely on a tangible storage medium such as an optical storage device or a magnetic storage device. In another embodiment, the computer program may also be transmitted and distributed in the form of signals over a network medium, and downloaded and installed via the communication section 909, and / or installed from a removable medium 911. The program code contained in the computer program can be transmitted using any suitable network medium, including but not limited to: wireless, wired, etc., or any suitable combination thereof.

[0131] In such an embodiment, the computer program can be downloaded and installed from a network via the communication section 909, and / or installed from the removable medium 911. When the computer program is executed by the processor 901, it performs the functions defined in the system of this disclosure embodiment. According to embodiments of this disclosure, the systems, devices, apparatuses, modules, units, etc., described above can be implemented by computer program modules.

[0132] According to embodiments of this disclosure, program code for executing the computer programs provided in embodiments of this disclosure can be written in any combination of one or more programming languages. Specifically, these computational programs can be implemented using high-level procedural and / or object-oriented programming languages, and / or assembly / machine languages. Programming languages ​​include, but are not limited to, languages ​​such as Java, C++, Python, "C", or similar programming languages. The program code can execute entirely on a user's computing device, partially on a user's device, partially on a remote computing device, or entirely on a remote computing device or server. In cases involving remote computing devices, the remote computing device can be connected to the user's computing device via any type of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computing device (e.g., via the Internet using an Internet service provider).

[0133] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0134] Those skilled in the art will understand that the features described in the various embodiments and / or claims of this disclosure can be combined and / or combined in various ways, even if such combinations or combinations are not explicitly described in this disclosure. In particular, the features described in the various embodiments and / or claims of this disclosure can be combined and / or combined in various ways without departing from the spirit and teachings of this disclosure. All such combinations and / or combinations fall within the scope of this disclosure.

[0135] The embodiments of this disclosure have been described above. However, these embodiments are for illustrative purposes only and are not intended to limit the scope of this disclosure. Although various embodiments have been described above, this does not mean that the measures in the various embodiments cannot be used advantageously in combination. The scope of this disclosure is defined by the appended claims and their equivalents. Various substitutions and modifications can be made by those skilled in the art without departing from the scope of this disclosure, and all such substitutions and modifications should fall within the scope of this disclosure.

Claims

1. A method for scheduling messages during parallel operation of old and new systems, comprising: Receive message; Match the target service application to which the message belongs with the list of service applications to obtain the first matching result; If the first matching result indicates that the target business application belongs to the business application list, the message content of the message is matched with the message processing specifications of the new system to obtain the second matching result; If the second matching result indicates that the message content conforms to the message processing specification, the information of all participants in the transmission path of the message is matched with the information of the participants who have deployed the new system and opened the target business application in the new system during the current time period to obtain the third matching result; as well as When the third matching result indicates that all participants have successfully matched, the message is scheduled to the new system; The third matching result, obtained by matching all participants in the transmission path of the message with the participants who deployed the new system and activated the target service application in the new system during the current time period, includes: Match all participating parties with the whitelist that has deployed the new system; If all participating parties are on the whitelist, check the business applications and activation periods activated by each participating party in the new system; and When the check determines that the business application activated by each of the participating parties in the new system includes the target business application, and the activation time period of the target business application in the new system by each participating party includes the current time, it is determined that all participating parties have successfully matched.

2. The method of claim 1, wherein, The method further includes: Configure the message processing specifications; When an update notification of the message processing specification is received, the message processing specification is updated; and Send a notification to the terminal device that the message processing function of the updated message processing specification has been deployed in both the new system and the old system.

3. The method of claim 2, wherein, The method further includes: If the second matching result indicates that the message content does not conform to the message processing specification, the message is scheduled to the old system; and If the second matching result indicates that the message content conforms to the message processing specification, but at least one participant in the third matching result fails to match, the message is scheduled to the old system.

4. The method of claim 1, wherein, Before receiving the message, the method further includes: Obtain information about the participants deploying the new system to obtain a whitelist; and Obtain the business applications and activation time periods activated by each participant in the whitelist in the new system.

5. The method according to claim 4, wherein, The step of obtaining the business applications and activation time periods activated by each participant in the whitelist in the new system further includes: updating the activation time periods of the first business applications activated by at least one first participant in the whitelist in the new system according to a preset strategy; and The method further includes controlling the first participant to run the first business application in the new system according to the updated activation time period.

6. The method of claim 5, wherein, The step of updating the activation time period of the first business application activated by at least one first participant in the whitelist in the new system according to the preset strategy includes: repeatedly performing the following operation until the gray-scale ratio of the activation time period of the first business application of the first participant in the new system reaches 100%: Obtain the operation report data of the first participating party in activating the first service application in the new system; and When the operation report data meets the operation upgrade conditions, the activation time period of the first business application in the first participant is extended.

7. The method of claim 4, wherein, The process of obtaining information about the participants deploying the new system and obtaining the whitelist also includes: If the running status data of the second business application opened by at least one second participant in the whitelist in the new system meets the stability requirements, at least one third participant whose business characteristics are correlated with the business characteristics of the second participant in the new system to be deployed is selected from the participants. Sending instructions to the terminal device to the third party to deploy the new system; and In response to the information that the third party has completed the deployment of the new system, the information of the third party is added to the whitelist to update the whitelist.

8. A message scheduling device during parallel operation of old and new systems, comprising: The receiving module is used to receive messages; The first matching module is used to match the target business application to which the message belongs with the business application list to obtain the first matching result; The second matching module is used to match the message content of the message with the message processing specifications of the new system if the first matching result indicates that the target business application belongs to the business application list, and obtain the second matching result. The third matching module is used to match the information of all participants in the transmission path of the message with the participants who have deployed the new system and opened the target business application in the new system during the current time period if the second matching result indicates that the message content conforms to the message processing specification, so as to obtain the third matching result. as well as The scheduling module is used to schedule the message to the new system when the third matching result indicates that all participants have successfully matched. Specifically, the third matching module is used for: Match all participating parties with the whitelist that has deployed the new system; If all the participants belong to the whitelist, check the business applications and activation periods that each participant has activated in the new system. as well as When the check determines that the business application activated by each of the participating parties in the new system includes the target business application, and the activation time period of the target business application in the new system by each participating party includes the current time, it is determined that all participating parties have successfully matched.

9. An electronic device, comprising: One or more processors; Memory, used to store one or more programs. When the one or more programs are executed by the one or more processors, the one or more processors perform the method according to any one of claims 1 to 7.

10. A computer-readable storage medium having stored thereon computer program instructions that, when executed by a processor, implement the method of any one of claims 1 to 7.

11. A computer program product comprising computer program instructions that, when executed by a processor, implement the method of any one of claims 1 to 7.

Images