Cross-business system approval data synchronization method, device, equipment, medium and product

Abstract

The invention provides a cross-business system approval data synchronization method, device and equipment, a medium and a product, which can be applied to the technical field of financial science and technology. The method comprises the following steps: using a message center as a center of each service system to broadcast a process change message to each service system, enabling the service system to carry out data identification on the received process change message to obtain a relevance identifier, and responding to the relevance between the service system and the relevance identifier, and establishing a system interconnection link for the single service system and the linkable system to update the change data of the flow information change event to a local database of the linkable system based on the system interconnection link, so that each service system updates the local service flow data of the service system according to the latest change data in the local database. And under the condition that the service system receives the service approval request, performing service approval according to the latest local service flow data to obtain an approval result.

Description

Technical Field

[0001] This application relates to the field of financial technology, specifically to a method, apparatus, equipment, medium, and product for synchronizing approval data across business systems. Background Technology

[0002] Corporate clients often face multiple approval processes when conducting financial transactions through electronic channels of financial institutions. In today's digital transformation of the financial industry, multiple underlying business systems exist, such as cash management systems, payment and settlement systems, and credit management systems. These systems are developed and operate independently, leading to difficulties in business process collaboration and data exchange. For example, process sharing is challenging due to significant differences in process logic across different systems, hindering collaboration and sharing. Furthermore, clients need to set up separate approval processes for cash management, payment collection and disbursement, international settlement, and credit transactions, with substantial differences in process logic, making it difficult to provide a consistent user experience. Moreover, different approval processes are required for different transactions, and changes in personnel structure necessitate maintaining separate approval processes, severely impacting efficiency and increasing the risk of inconsistencies. Additionally, with the diversification of business and increasingly stringent risk control and regulatory requirements, transaction limits for clients conducting transactions through electronic banking channels need to be consistent across multiple related systems to ensure unified management of client funds and transaction security.

[0003] However, the business approval process in related technologies is fragmented, and the approval processes of different business systems lack effective integration and sharing. For example, after a business system undergoes a business change, the data of related business systems lags behind, causing the old data to still be used for approval when the business system makes a data request, resulting in the approval being rejected. Then, a second approval is required using the updated data from another business system, which leads to data synchronization delays and low business approval efficiency. Summary of the Invention

[0004] In view of the above problems, this application provides a method, apparatus, device, medium and product for synchronizing approval data across business systems.

[0005] According to the first aspect of this application, a method for synchronizing approval data across business systems is provided, comprising: in response to receiving an approval instruction from a single business system, acquiring a process information change event, transmitting process change information about the process information change event to a preset message center, so that the message center acts as the central hub for each business system to broadcast process change messages to each business system; having the business system perform data identification on the received process change message to obtain a correlation identifier, and in response to the business system being associated with the correlation identifier, enabling the business system to open its own online permissions, forming a linkable system; establishing a system interconnection link between the single business system and the linkable system, updating the change data of the process information change event to the local database of the linkable system based on the system interconnection link, and closing the online permissions after the change data update is completed; enabling each business system to update its local business flow data according to the latest change data in its local database, and when a business system receives a business approval request, performing business approval according to the latest local business flow data to obtain an approval result.

[0006] According to an embodiment of this application, obtaining a process information change event includes: obtaining business data flow information corresponding to the approval instruction; extracting data from the business data flow information to obtain the approval change type and change data, wherein the approval change type includes adding data, modifying data, and deleting data; compressing the approval change type and change data into a change data package, and adding change information to the change data package to obtain a process information change event, wherein the change information includes the system identifier of the business system to which the approval instruction belongs, the business number of the business data flow information, and the event number of the process information change event.

[0007] According to an embodiment of this application, obtaining process change information includes: parsing the change data packet of the process change event to obtain the business data involved in the business data flow information; determining the various business systems associated with the business data to obtain system-related data; selecting an identifier corresponding to the system-related data as an association identifier in a preset system identifier mapping table; and adding the association identifier, system identifier, business number, and event number to a preset information template to obtain process change information.

[0008] According to embodiments of this application, a default pre-operation is also included, which includes: establishing a communication link between each business system and the message center; based on the communication link, enabling the business system as a subscriber to the message center to poll the message center at a preset time interval; in response to the business system polling a newly added process change message, storing the process change message in the business system's own cache database, so as to perform data identification of the process change message in the cache database through the business system's identifier recognition engine.

[0009] According to an embodiment of this application, in response to the business system being unrelated to the association identifier, the process change message is deleted from the cache database.

[0010] According to embodiments of this application, targeted pre-operations are also included, which include: identifying customers of interest in the business system; establishing a subscription channel between the business system and the message center regarding the customers of interest; in response to a process change message being related to the customers of interest, causing the message center to broadcast the process change message to the business system based on the subscription channel; and in response to a process change message being unrelated to the customers of interest, the business system maintaining a message rejection state.

[0011] According to an embodiment of this application, updating the change data of a process information change event to the local database of a linkable system includes: extracting keywords from the process information change event to obtain key event fields and key event data; retrieving process description information related to the process information change event based on the system identifier and business number in the process information change event, extracting keywords from the process description information to obtain process description fields and process description data, and performing data change review based on the process description fields, process description data, key event fields, and key event data to obtain a review result; wherein, the process description information is used to characterize the business process nodes and node operation data of the business system before approval, and the business process nodes and node operation data of the business system after approval; in response to the review result indicating that the data change is correct, the change data is written to the local database of the linkable system.

[0012] According to an embodiment of this application, updating the local business flow data of a business system based on the latest change data in the local database includes: calling a preset process matching engine based on the approval change type corresponding to the change data; using the process matching engine to fill the change data into a process template corresponding to the approval change type to obtain an updated template; obtaining the latest process template corresponding to the approval change type stored in the local database, and performing a composite replacement between the process template and the updated template to obtain an updated process template; and extracting business flow data based on the updated process template to obtain updated local business flow data.

[0013] The second aspect of this application provides a cross-business system approval data synchronization device, comprising: a change triggering module, used to, in response to receiving an approval instruction from a single business system, acquire a process information change event, and transmit process change information about the process information change event to a preset message center, so that the message center acts as the central hub for each business system to broadcast process change messages to each business system; an identification response module, used to enable the business system to perform data identification on the received process change message, obtain a correlation identifier, and, in response to the business system being associated with the correlation identifier, enable the business system to open its own online permissions, forming a linkable system; a data sharing module, used to establish a system interconnection link between the single business system and the linkable system, so as to update the change data of the process information change event to the local database of the linkable system based on the system interconnection link, and close the online permissions after the change data update is completed; and a data update module, used to enable each business system to update its local business flow data according to the latest change data in its local database, and, when the business system receives a business approval request, to perform business approval according to the latest local business flow data to obtain the approval result.

[0014] A third aspect of this application provides an electronic device comprising: one or more processors; and a memory for storing 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 method described above.

[0015] A fourth aspect of this application 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.

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

[0017] According to the cross-business system approval data synchronization method, apparatus, equipment, medium, and product provided in this application, in response to receiving an approval instruction from a single business system, a process information change event is obtained. A message center acts as the central hub to broadcast a process change message regarding the information change event, thereby facilitating data identification by all business systems and improving data synchronization efficiency. A system interconnection link is established between a single business system and a linked system, enabling multiple business systems to simultaneously synchronize and update data, improving data synchronization efficiency and overall business system management efficiency. When a business system receives a business approval request, it performs business approval based on the latest local business flow data to obtain the approval result, avoiding approval rejections due to data lag, and improving business approval efficiency and pass rate. Therefore, based on this, the overall management efficiency and data synchronization efficiency of each business system are improved, as well as the business approval efficiency and pass rate. Attached Figure Description

[0018] The above-mentioned contents, other objects, features and advantages of this application will become clearer from the following description of embodiments with reference to the accompanying drawings, in which:

[0019] Figure 1 The illustration schematically depicts an application scenario of a cross-business system approval data synchronization method, apparatus, device, medium, and program product according to embodiments of this application;

[0020] Figure 2 A flowchart illustrating a cross-business system approval data synchronization method according to an embodiment of this application is shown schematically.

[0021] Figure 3 This illustration schematically shows the association between the business systems and the message center involved in the cross-business system approval data synchronization method according to an embodiment of this application;

[0022] Figure 4 This illustration shows the data flow diagram of the cross-business system approval data synchronization method for obtaining correlation identifiers according to an embodiment of this application;

[0023] Figure 5 This schematic diagram illustrates the structural block diagram of a cross-business system approval data synchronization device according to an embodiment of this application;

[0024] Figure 6 A block diagram schematically illustrates an electronic device suitable for implementing a cross-business system approval data synchronization method according to an embodiment of this application. Detailed Implementation

[0025] The embodiments of this application 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 this application. In the following detailed description, numerous specific details are set forth to provide a thorough understanding of the embodiments of this application for ease of explanation. However, it will be apparent that one or more embodiments may be implemented without these specific details. Furthermore, descriptions of well-known structures and technologies are omitted in the following description to avoid unnecessarily obscuring the concepts of this application.

[0026] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the scope of this application. 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.

[0027] 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.

[0028] When using expressions such as "at least one of A, B and C", they should generally be interpreted in accordance with the meaning that is 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, a system having A alone, a system having B alone, a system having C alone, a system having A and B, a system having A and C, a system having B and C, and / or a system having A, B and C, etc.).

[0029] It should be noted that in the embodiments of this application, certain software, components, models and other existing solutions in the industry may be mentioned. These should be regarded as exemplary and are only intended to illustrate the feasibility of implementing the technical solution of this application. However, it does not mean that the applicant has used or necessarily used the solution.

[0030] In the technical solution of this application, the collection, storage, use, processing, transmission, provision, disclosure and application of user personal information all comply with the provisions of relevant laws and regulations and do not violate public order and good morals.

[0031] In the technical solution of this application, the acquisition, collection, storage, use, processing, transmission, provision, disclosure and application of data all comply with the provisions of relevant laws and regulations and do not violate public order and good morals.

[0032] Figure 1 The diagram illustrates an application scenario of the cross-business system approval data synchronization method according to an embodiment of this application.

[0033] like Figure 1 As shown, application scenario 100 according to this embodiment may include terminal devices 101, 102, and 103, network 104, and server 105. Network 104 is used as a medium to provide a communication link between terminal devices 101, 102, and 103 and server 105. Network 104 may include various connection types, such as wired or wireless communication links or fiber optic cables, etc.

[0034] Users can use terminal devices 101, 102, and 103 to interact with server 105 via network 104 to receive or send messages, etc. Various communication client applications can be installed on terminal devices 101, 102, and 103, such as shopping applications, web browser applications, search applications, instant messaging tools, email clients, social media platform software, etc. (for example only).

[0035] Terminal devices 101, 102, and 103 can be various electronic devices with displays and web browsing capabilities, including but not limited to smartphones, tablets, laptops, and desktop computers.

[0036] Server 105 can be a server that provides various services, such as a backend management server that supports websites browsed by users using terminal devices 101, 102, and 103 (for example only). The backend management server can analyze and process data such as received user requests, and feed back the processing results (such as web pages, information, or data obtained or generated according to user requests) to the terminal devices.

[0037] It should be noted that the cross-business system approval data synchronization method provided in this application embodiment can generally be executed by server 105. Correspondingly, the cross-business system approval data synchronization device provided in this application embodiment can generally be located in server 105. The cross-business system approval data synchronization method provided in this application embodiment can also be executed by a server or server cluster that is different from server 105 and capable of communicating with terminal devices 101, 102, 103 and / or server 105. Correspondingly, the cross-business system approval data synchronization device provided in this application embodiment can also be located in a server or server cluster that is different from server 105 and capable of communicating with terminal devices 101, 102, 103 and / or server 105.

[0038] It should be understood that Figure 1 The number of terminal devices, networks, and servers shown is merely illustrative. Depending on implementation needs, any number of terminal devices, networks, and servers can be included.

[0039] The following will be based on Figure 1 The described scene, through Figures 2-4The cross-business system approval data synchronization method of the application embodiment is described in detail.

[0040] Figure 2 A flowchart illustrating a cross-business system approval data synchronization method according to an embodiment of this application is shown.

[0041] like Figure 2 As shown, the cross-business system approval data synchronization method of this embodiment includes operations S210 to S240.

[0042] In operation S210, in response to receiving an approval instruction from a single business system, a process information change event is obtained, and the process change information regarding the process information change event is transmitted to a preset message center, so that the message center acts as the central hub for each business system to broadcast the process change message to each business system. In operation S220, the business system performs data identification on the received process change message to obtain a correlation identifier. In response to the business system being associated with the correlation identifier, the business system enables its own online access permission, forming a linkable system. In operation S230, a system interconnection link is established between the single business system and the linkable system, so that the change data of the process information change event is updated to the local database of the linkable system based on the system interconnection link, and the online access permission is closed after the change data update is completed. In operation S240, each business system updates its local business flow data according to the latest change data in its local database. When a business system receives a business approval request, it performs business approval according to the latest local business flow data to obtain the approval result.

[0043] Figure 3 This illustration shows a schematic diagram of the association between the business systems and the message center involved in the cross-business system approval data synchronization method according to an embodiment of this application.

[0044] exist Figure 3In the example shown, each business system is associated with the message center. The association between the message center and the business systems is pre-defined. For example, a "process service component" can be built as a common service component for approval process information to uniformly save and maintain the process description information used by customers in various business systems of the financial institution. The specific type of business system is not limited and can be a cash management business system, a collection and payment business system, an international settlement business system, a loan business system, a product transaction business system, etc. For each business system, various types of business process description information and transaction limit information are defined. The definition of business process description information and transaction limit information is part of the business flow information. The business flow information comprehensively records the event number and message message of process or transaction limit changes. The process change message event number is associated with the association identifier of each business system. The process description information specifically includes the business type and key business elements, as well as the number of approval nodes and which users can process each node.

[0045] In other words, each business system can subscribe to messages sent by the message center. If any single business system has a new approved instruction, it receives a process information change event and transmits the process change information to the preset message center. The message center acts as the central hub for broadcasting process change messages to all business systems. Simultaneously, business systems associated with the message center receive these process change messages. Each business system can then directly identify the received process change messages and obtain associated identifiers. Specifically, for example, when a customer submits a new approval instruction through corporate online banking or other electronic banking channels... When adding, modifying, or deleting information, the process service component, acting as the event creator and publisher, triggers a process information change event, generates an event number, generates a corresponding notification message, and publishes it to the message center. The process update message includes the following information: customer e-banking contract number, process definition template number, update type (e.g., add, modify, delete), and may also include: update timestamp, global event tracking number of online transactions, etc. The message center needs to perform transaction control when publishing messages. If message publishing fails, it will roll back to the stage of obtaining process information change events, ensuring that the process status master is always consistent with the one published to the message center, so that all business systems communicating with the message center can capture the changed data in a timely manner.

[0046] This association identifier serves as the basis for each business system to determine whether the process change message is related to itself. If it is related to the process change message, a connection is established between that individual business system and all linked systems related to the association identifier, thereby enabling data sharing and data synchronization updates among multiple business systems. This improves data synchronization efficiency and overall business system management efficiency. Subsequently, each business system updates its local business flow data based on the latest change data in its local database. When a business system receives a business approval request, it performs business approval according to the latest local business flow data to obtain the approval result. This avoids approval rejections due to data lag, shortens the total approval time, and improves business approval efficiency and pass rate.

[0047] Based on this, a message center is used as the central hub to broadcast process change messages, facilitating data identification by all business systems and improving data synchronization efficiency. System interconnection links are established between individual business systems and linkable systems. These interconnection links, or online links, are essentially connections between the servers of various linkable systems and individual business systems. This enables multi-system interconnection between multiple linkable systems and the changed business system, achieving data sharing and allowing multiple business systems to simultaneously synchronize and update data, improving data synchronization efficiency and overall business system management efficiency. When a business system receives a business approval request, it processes the approval based on the latest local business flow data to obtain the approval result, avoiding rejections due to data lag and improving approval efficiency and pass rate. Thus, the overall management efficiency and data synchronization efficiency of each business system are improved, as well as the approval efficiency and pass rate.

[0048] Figure 4 The illustration shows a schematic diagram of the data flow for obtaining the association identifier in the cross-business system approval data synchronization method according to an embodiment of this application.

[0049] exist Figure 4 In the illustrated embodiment, obtaining process information change events includes: obtaining business data flow information corresponding to the approval instruction; extracting data from the business data flow information to obtain the approval change type and change data, where the approval change type includes adding data, modifying data, and deleting data; compressing the approval change type and change data into a change data package, and adding change information to the change data package to obtain the process information change event, where the change information includes the system identifier of the business system to which the approval instruction belongs, the business number of the business data flow information, and the event number of the process information change event.

[0050] As an example, this business data flow information includes information on all approval flow nodes involved in the business approval process to which the approval instruction belongs, as well as information on the relevant data corresponding to the approval flow nodes. By extracting data from this business data flow information, the specific change type to which the changed data belongs can be obtained. This change type is the approval change type, including but not limited to CRUD operations, unification, rejection, etc. Then, the extracted approval change type and change data are extracted and compressed into a change data package, and information is labeled on the change data package to obtain the process information change event.

[0051] The information marked includes, but is not limited to, the system label, i.e., the label of the individual business system that has changed, the business number of the business data flow information, i.e., the business number to which the changed business data flow belongs, and the event number of the process information change event. Based on this, the data within the individual business system itself can be summarized and numbered to facilitate the comprehensive processing, management and archiving of the changed business data flow information, and to provide a data call index for subsequent linked systems, so that subsequent linked systems can call the data.

[0052] In this embodiment, obtaining process change information includes: parsing the change data packet of the process change event to obtain the business data involved in the business data flow information; determining the various business systems associated with the business data to obtain system-related data; selecting the identifier corresponding to the system-related data as the association identifier in the preset system identifier mapping table; and adding the association identifier, system identifier, business number, and event number to the preset information template to obtain process change information.

[0053] As an example, this process change information is obtained based on the aforementioned process change event. This process change event encompasses all approval flow nodes and their corresponding data in the business data flow information. The process change information describes the business systems / data associated with the approval flow node and its corresponding data. When obtaining this information, it is first necessary to obtain the business data involved in the business data flow information, i.e., the data corresponding to the approval flow nodes, and then determine the various business systems related to this business data, thereby obtaining the system-related data. This system-related data is used to characterize the type of the business data within the associated business system. For example, if the business data belongs to a specific business system... The business data is the deposit value. In the loan business system, its system-related data is the loan influencing factor value. In the financial product recommendation system, its system-related data is the purchasing power reference value. The system-related data in these different business systems are all marked with corresponding correlation identifiers in the preset system identifier mapping table. After obtaining the system-related data, the correlation identifier corresponding to the system-related data, along with the system number, business number, and event number, are added to the preset information template to obtain the process change information. Encapsulating the process change information in the preset message instruction will generate a process change message about the process change information.

[0054] Based on this, the system-related data is first determined according to the business data. Then, the association identifiers corresponding to each associated business system are obtained from the system-related data. This allows for subsequent access to link permissions based on the association identifiers to achieve data sharing, improve data sharing efficiency, and ultimately improve the overall approval efficiency across business systems.

[0055] In one embodiment, a default pre-operation is also included, which includes: establishing a communication link between each business system and the message center; enabling the business system, as a subscriber to the message center, to poll the message center at preset time intervals based on the communication link; and storing the process change message in the business system's own cache database in response to the business system polling a newly added process change message, so as to perform data identification of the process change message in the cache database through the business system's identification engine.

[0056] As an example, this default operation is the first step in establishing the connection between all business systems and the message center. First, it is necessary to establish a communication link between each business system and the message center. This communication link can be created based on API (Application Programming Interface) or can be implemented through network sharing, as long as the application system can receive process change messages sent by the message center.

[0057] In a more specific example, each business system, as a subscriber to process change messages and also a downstream event application of the aforementioned single business system with changed data, can subscribe to process change messages based on event numbers and poll for updates at preset time intervals, such as 30 seconds. When a new message for a specific event number appears in the message center, the business system actively retrieves the new process change message from the message center. The message center modifies the status of the message for the specific subscriber, removes it from the message queue, and stores the process change message in its own cache database. The business system's identification engine then uses the cache database to perform data identification on the process change message to confirm whether it is related to itself.

[0058] Based on this, each business system periodically captures process change messages to facilitate timely data synchronization, improves the timeliness of change data synchronization, and first stores the process change message in a cache database to reduce the amount of online data processing, improves the efficiency of determining whether a business system is related to the correlation identifier, and thus improves the processing efficiency and timeliness of cross-business system business approval.

[0059] In this embodiment, in response to the business system being unrelated to the association identifier, the process change message is deleted from the cache database.

[0060] As an example, when a business system is associated with an association identifier, the business system is given online access to form a linkable system. When the business system is not associated with the association identifier, the process change message is deleted from the cache database. Based on this, the process change message is deleted in a timely manner in this case so as to release cache space in the cache database in a timely manner.

[0061] In another embodiment, targeted pre-operations are also included, which include: identifying customers of interest for the business system; establishing a subscription channel between the business system and the message center regarding the customers of interest; in response to a process change message being related to the customers of interest, causing the message center to broadcast the process change message to the business system based on the subscription channel; and in response to a process change message being unrelated to the customers of interest, the business system maintaining a message rejection state.

[0062] As an example, to reduce the data computation load of the business system and decrease the frequency of receiving irrelevant messages, this example pre-establishes subscription channels related to customers who are being followed. This ensures that the business system only receives process change messages related to these customers, while rejecting process change messages for irrelevant customers, thus reducing the computational load. In a more specific example, customers often need to sign up for relevant business products before processing transactions through the bank's electronic channels. This signing information is stored in each business system. Each business system can subscribe only to messages from customers who have signed up for its product contracts, designating them as "followed customers." If new customers sign up for product contracts later, these customers can be added to the subscription list. The system can directly query whether a customer already has a shared process by calling the customer channel process service component query interface based on the customer's ID, such as the e-banking contract number. By associating the process with the customer's business product contract, that is, by determining which customers' process change messages the business system needs to process through the direct binding relationship between the product contract and the customer's identity, the business system can determine which customers' process change messages it needs to process. When the business system receives the process change message of the target customer, it can query the online transaction by calling the process description information published by the customer channel process service system to obtain the complete process description information of the customer and apply it to the business approval process of the business system. This can reduce the number of messages subscribed and consumed by each business system and improve the overall performance of process description information synchronization.

[0063] In this way, the business system only needs to respond to process change messages related to customers it cares about, while not receiving such messages for customers it doesn't care about. This improves data synchronization efficiency while reducing the system's computational load.

[0064] In this embodiment, updating the change data of the process information change event to the local database of the linkable system includes: extracting keywords from the process information change event to obtain key event fields and key event data; retrieving process description information related to the process information change event based on the system identifier and business number in the process information change event, extracting keywords from the process description information to obtain process description fields and process description data, and performing data change review based on the process description fields, process description data, key event fields, and key event data to obtain a review result; wherein, the process description information is used to characterize the business process nodes and node operation data of the business system before approval, and the business process nodes and node operation data of the business system after approval; in response to the review result indicating that the data change is correct, the change data is written to the local database of the linkable system.

[0065] Based on the correlation identifier, process description information is queried from the customer channel process service system to the local data of the business system via online transactions. There are three update types in the process update message: add, modify, and delete. For deletion scenarios, no online transaction is needed; simply delete the local data. If the business system fails to query process description information via online transaction, it needs to retry until successful. After obtaining the process description information, each business system maps and saves it locally according to the agreed unified specifications and the data structure requirements of its own architecture. Then, keyword extraction is performed on the process description information to obtain process description fields and process description data. Finally, based on the process description fields, process description data, and the process description... The process involves reviewing changes to key fields and key data of events to obtain a review result. This result determines whether the process description fields and key event fields are consistent, and whether the process description data and key event data are consistent. If they are consistent, the review result is "review passed." This process description information is used to represent the business process nodes and node operation data before and after approval in the business system. In other words, this process description information describes the information of the changed data and the approval change type information corresponding to the changed data. When the review result is "review passed," it indicates that the data change is correct, and the changed data is then written to the local database of the connectable system. It should be noted that for business systems that are using process description information for the first time or for customers who have newly signed up for the business system's product, when a customer initiates a related business transaction for the first time, the system should first query the customer channel process service system based on the customer number, such as the e-banking contract number, to see if the customer has already set up a common process. If a common process exists, subsequent changes can be directly replaced by comparison. A common process is a process shared by all connectable systems / business systems.

[0066] Based on this, we conduct a change review of the modified data to reduce the error rate of data synchronization and improve the accuracy of data synchronization.

[0067] In this embodiment, updating the local business flow data of the business system based on the latest change data in the local database includes: calling a preset process matching engine according to the approval change type corresponding to the change data; using the process matching engine to fill the change data into the process template corresponding to the approval change type to obtain an updated template; obtaining the latest process template corresponding to the approval change type stored in the local database, and performing a composite replacement between the process template and the updated template to obtain an updated process template; and extracting business flow data based on the updated process template to obtain updated local business flow data.

[0068] As an example, after each business system obtains the changed data into its local system, it updates the local business flow data of the business system according to the latest changed data in the local database. In a specific embodiment, for example, when a transaction is initiated in the business system through a bank's electronic channel, the process matching engine provided by the customer channel process service component matches the process template used by the customer in the business system, and generates a process business document according to the process template, which is then transferred to the corresponding review user to complete the approval process. In this process, the changed data is filled into the process template corresponding to the approval change type using the process matching engine to obtain the updated template. Then, the latest process template corresponding to the approval change type stored in the local database is obtained, and the process template and the updated template are replaced to obtain the updated process template. Business flow data is extracted according to the process template to obtain the updated local business flow data. When approving the customer's transaction in the future, the approval data flow in the updated process template is used for layer-by-layer approval.

[0069] In a more specific example, the process matching engine rules are as follows: Before matching process templates, check the accuracy of the submitted process function number and sub-function number. Use the submitted labels, tags, and identifiers as query conditions to check if there is a record for the latest process template. If no record is found, return an error. The process template matching elements include the following parts, such as customer number, i.e., customer e-banking contract number, approval node fields submitted for order creation transactions or querying the list of selectable persons for lower-level tasks, corresponding to the fields in the database; business type, such as business data submitted for order creation transactions or querying the list of selectable persons for lower-level tasks, corresponding to the same-name fields in the database table, etc. When matching process templates, the business type must support matching the superior general process in order. The matching priority order is as follows: personalized process with sub-function number, general process with function number, general process of business category, non-public process blacklist business and corporate online banking public process. Public process blacklist business indicates that this type of business cannot match the public process. It is configured in the preset nodes. If any node has a configuration record, it is considered a public process blacklist business.

[0070] Based on this, the local business flow data of the business system is updated according to the latest change data in the local database. In this way, a composite replacement between process templates is performed first, and then the updated local business flow data is obtained based on the updated process template, which improves the rigor and accuracy of the change data replacement and update, and reduces the error rate.

[0071] Subsequently, when the business system receives a business approval request, it performs business approval according to the latest local business flow data to obtain the approval result. That is, it creates a document according to the local business flow data in the updated process template. During the document creation process, only process definitions in the effective state can be matched. During the document creation process, based on the command sent by the document creation transaction or the command sent by the query of the selectable person list transaction for the lower-level task, the command may have multiple fields in the database table. When there is only one record in the data table for multiple fields, it means that the document can be created. The field sent by the document creation transaction or the query of the selectable person list transaction for the lower-level task and the field with the same name in the corresponding database table are not mandatory conditions. One or more elements can be sent. If the document creation transaction or the query of the selectable person list transaction for the lower-level task is not sent, the matching condition is ignored. If it is sent, the process is matched in the following priority order, such as matching the process in which the field value in the table is consistent with the field value sent by the transaction, matching the process in which the field in the table has an empty value, etc.

[0072] In a specific example, taking limit approval as an example, some business systems, such as cash management and payment collection, involve daily cumulative limit logic to provide customers with more comprehensive fund security control. These systems often require electronic channels to use a unified limit. By defining daily cumulative limit information in the process description, the limit value can be accumulated during the approval stage, and the transaction can be blocked if it exceeds the limit, thus preventing risky transactions. Furthermore, the limit information, along with the process description, is synchronized between multiple business systems via a publish-subscribe model based on event channels through a message center. This ensures the timeliness and accuracy of transaction limit synchronization, guarantees consistency of transaction limit data across different business systems, effectively reduces transaction risks caused by asynchronous limit information, and protects customer fund security. After the limit information is synchronized, each business system implements the control of the cumulative transaction limit for relevant transaction days through the following collaborative methods. For example, the customer channel process service system, as the central management system for the cumulative transaction amount of the process, adds a data structure for recording the cumulative amount of the process day. Through transaction interceptors, transaction interceptors are added to all electronic channel accounting transactions. When a customer initiates a relevant business on the bank's electronic channel, the logic of querying and cumulatively updating the current customer's cumulative amount of the process day is triggered. Cash management, collection and payment, and other business systems add a cumulative limit field for the process day to the related inter-connected transaction request fields. The response message adds a cumulative limit flag for the process day; no return indicates that no accumulation is required. Based on this, each business system can flexibly add limits only to business transactions with risk control requirements according to its own business needs. Daily cumulative limit verification is performed, while other transactions are not affected by the daily cumulative limit. When a customer initiates a relevant business transaction through the bank's electronic channels, the customer channel process service system obtains the customer's current daily cumulative transaction amount through the electronic channels and sends it to each business system. Each business system, in conjunction with the customer's daily cumulative limit value obtained through the process description subscribed to by the message center and the current transaction amount, determines whether the current transaction has exceeded the limit and needs to block the approval process or allow the transaction. If the transaction has not exceeded the daily cumulative limit, the transaction is successfully completed. At the same time, the customer channel process service system obtains the transaction success information through the transaction return interceptor and adds this transaction to the current customer's daily cumulative amount, updating the cumulative amount information in a timely manner so that the relevant limit information can be accurately synchronized when other business systems have transactions in the future.

[0073] As described above, the cross-business system approval data synchronization method provided in this application, in response to receiving an approval instruction from a single business system, acquires a process information change event. Because the message center acts as the central hub to broadcast process change messages regarding the information change event, it facilitates data identification by all business systems, improving the data synchronization efficiency of each business system. By establishing system interconnection links between a single business system and linked systems, multiple business systems can simultaneously perform data synchronization updates, improving data synchronization efficiency and overall business system management efficiency. Furthermore, when a business system receives a business approval request, it performs business approval based on the latest local business flow data to obtain the approval result, avoiding approval rejections due to data lag, thus improving business approval efficiency and pass rate. Therefore, based on this, it improves the overall management efficiency and data synchronization efficiency of each business system, and ultimately, the business approval efficiency and pass rate.

[0074] Based on the above-mentioned method for synchronizing approval data across business systems, this application also provides a device for synchronizing approval data across business systems. The following will combine... Figure 5 The device is described in detail.

[0075] Figure 5 A schematic block diagram of a cross-business system approval data synchronization device according to an embodiment of this application is shown.

[0076] like Figure 5 As shown, the cross-business system approval data synchronization device 500 of this embodiment includes a change triggering module 510, an identification response module 520, a data sharing module 530, and a data update module 540.

[0077] The change triggering module 510 executes operation S210, responding to the receipt of an approval instruction from a single business system, acquiring a process information change event, and transmitting the process change information regarding the process information change event to a preset message center, so that the message center acts as the central hub for each business system to broadcast process change messages to each business system; the identification response module 520 executes operation S220, causing the business system to perform data identification on the received process change message, obtain an association identifier, and responding to the business system being associated with the association identifier, enabling the business system to open its own online permissions, forming a linkable system; the data sharing module 530 executes operation S230, establishing a system interconnection link between a single business system and a linkable system, updating the change data of the process information change event to the local database of the linkable system based on the system interconnection link, and closing the online permissions after the change data update is completed; the data update module 540 executes operation S240, causing each business system to update its local business flow data according to the latest change data in its local database, and when a business system receives a business approval request, it performs business approval according to the latest local business flow data to obtain the approval result.

[0078] In this embodiment, the change triggering module 510 acquires process information change events by: acquiring business data flow information corresponding to the approval instruction; extracting data from the business data flow information to obtain the approval change type and change data, where the approval change type includes adding data, modifying data, and deleting data; compressing the approval change type and change data into a change data packet, and adding change information to the change data packet to obtain the process information change event, where the change information includes the system identifier of the business system to which the approval instruction belongs, the business number of the business data flow information, and the event number of the process information change event; the change triggering module 510 acquires process change information by: parsing the change data packet of the process change event to obtain the business data involved in the business data flow information; determining the various business systems associated with the business data to obtain system-associated data; selecting an identifier corresponding to the system-associated data as an association identifier in a preset system identifier mapping table; and adding the association identifier, system identifier, business number, and event number to a preset information template to obtain process change information.

[0079] It also includes a pre-operation module, which performs default pre-operations, including: establishing communication links between each business system and the message center; enabling the business system, as a subscriber to the message center, to poll the message center at preset time intervals based on the communication links; and storing the process change message in the business system's own cache database when the business system polls for a new process change message, so that the business system's identifier recognition engine can identify the process change message in the cache database; wherein, if the business system is not related to the association identifier, the process change message is deleted from the cache database; or the pre-operation module performs targeted pre-operations, including: identifying the business system's target customers; establishing a subscription channel between the business system and the message center for the target customers; broadcasting the process change message to the business system through the subscription channel if the process change message is related to the target customer; and keeping the business system in a message-rejecting state if the process change message is not related to the target customer.

[0080] The data sharing module 530 updates the change data of the process information change event to the local database of the linkable system, including: extracting keywords from the process information change event to obtain key event fields and key event data; retrieving the process description information related to the process information change event based on the system identifier and business number in the process information change event, extracting keywords from the process description information to obtain process description fields and process description data, and performing data change review based on the process description fields, process description data, key event fields, and key event data to obtain the review result; wherein, the process description information is used to represent the business process nodes and node operation data of the business system before approval, and the business process nodes and node operation data of the business system after approval; in response to the review result indicating that the data change is correct, the changed data is written to the local database of the linkable system.

[0081] The data update module 540 updates the local business flow data of the business system based on the latest change data in the local database, including: calling a preset process matching engine according to the approval change type corresponding to the change data; using the process matching engine to fill the change data into the process template corresponding to the approval change type to obtain the updated template; obtaining the latest process template corresponding to the approval change type stored in the local database, and performing a composite replacement between the process template and the updated template to obtain the updated process template; and extracting business flow data based on the updated process template to obtain the updated local business flow data.

[0082] According to embodiments of this application, any multiple modules among the change trigger module 510, identification response module 520, data sharing module 530, and data update module 540 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 application, at least one of the change trigger module 510, identification response module 520, data sharing module 530, and data update module 540 can be at least partially implemented as hardware circuitry, such as a field-programmable gate array (FPGA), a programmable logic array (PLA), a system-on-a-chip, a system-on-a-substrate, a system-on-package, an application-specific integrated circuit (ASIC), or implemented in hardware or firmware by any other reasonable means of integrating or packaging the circuitry, or implemented in any one of the three implementation methods of software, hardware, and firmware, or in a suitable combination of any of these. Alternatively, at least one of the change triggering module 510, the identification response module 520, the data sharing module 530, and the data update module 540 may be implemented at least partially as a computer program module, which can perform corresponding functions when the computer program module is run.

[0083] Figure 6 A block diagram schematically illustrates an electronic device suitable for implementing a cross-business system approval data synchronization method according to an embodiment of this application.

[0084] like Figure 6 As shown, an electronic device 600 according to an embodiment of this application includes a processor 601, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 602 or a program loaded from a storage portion 608 into a random access memory (RAM) 603. The processor 601 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 601 may also include onboard memory for caching purposes. The processor 601 may include a single processing unit or multiple processing units for performing different actions of the method flow according to an embodiment of this application.

[0085] RAM 603 stores various programs and data required for the operation of electronic device 600. Processor 601, ROM 602, and RAM 603 are interconnected via bus 604. Processor 601 executes various operations of the method flow according to embodiments of this application by executing programs in ROM 602 and / or RAM 603. It should be noted that the programs may also be stored in one or more memories other than ROM 602 and RAM 603. Processor 601 may also execute various operations of the method flow according to embodiments of this application by executing programs stored in said one or more memories.

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

[0087] This application 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, which, when executed, implement the method according to the embodiments of this application.

[0088] According to embodiments of this application, the computer-readable storage medium can 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 application, the computer-readable storage medium can be any tangible medium containing or storing 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 application, the computer-readable storage medium may include ROM 602 and / or RAM 603 and / or one or more memories other than ROM 602 and RAM 603 described above.

[0089] Embodiments of this application 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 enable the computer system to implement the item recommendation method provided in the embodiments of this application.

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

[0091] 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 609, and / or installed from the removable medium 611. 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.

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

[0093] According to embodiments of this application, program code for executing the computer programs provided in the embodiments of this application 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 be executed entirely on the user's computing device, partially on the 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).

[0094] 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 application. 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.

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

[0096] The embodiments of this application have been described above. However, these embodiments are merely illustrative and not intended to limit the scope of this application. 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 application 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 application, and all such substitutions and modifications should fall within the scope of this application.

Claims

1. A method for synchronizing approval data across business systems, characterized in that, include: In response to receiving an approval instruction from a single business system, a process information change event is obtained, and process change information about the process information change event is transmitted to a preset message center, so that the message center acts as the central hub for each business system to broadcast process change messages to each business system. The business system performs data identification on the received process change message to obtain a correlation identifier. In response to the business system being associated with the correlation identifier, the business system enables its own online permissions to form a linkable system. Establish a system interconnection link between the individual business system and the connectable system, so as to update the change data of the process information change event to the local database of the connectable system based on the system interconnection link, and close the online permission after the change data update is completed; Each business system updates its local business flow data based on the latest change data in the local database. When a business system receives a business approval request, it performs the business approval according to the latest local business flow data to obtain the approval result.

2. The method for synchronizing approval data across business systems according to claim 1, characterized in that, The events that allow obtaining process information change events include: Obtain the business data flow information corresponding to the approval instruction; Data extraction is performed on business data flow information to obtain approval change types and change data, wherein the approval change types include adding data, modifying data, and deleting data; The approval change type and change data are compressed into a change data package, and change information is added to the change data package to obtain a process information change event. The change information includes the system number of the business system to which the approval instruction belongs, the business number of the business data flow information, and the event number of the process information change event.

3. The method for synchronizing approval data across business systems according to claim 2, characterized in that, Obtaining the process change information includes: The change data packet of the process change event is parsed to obtain the business data involved in the business data flow information; Identify the various business systems associated with the business data to obtain system-related data; Select an identifier corresponding to the system-related data from a preset system identifier mapping table as the association identifier; Add the association identifier, the system identifier, the business number, and the event number to a preset information template to obtain process change information.

4. The method for synchronizing approval data across business systems according to claim 1, characterized in that, It also includes default pre-operations, which include: Establish communication links between each business system and the message center; Based on the communication link, the business system, as a subscriber to the message center, polls the message center at preset time intervals. In response to the business system receiving a new process change message, the process change message is stored in the business system's own cache database, so that the business system's identifier recognition engine can perform data recognition on the process change message in the cache database.

5. The method for synchronizing approval data across business systems according to claim 4, characterized in that, In response to the business system being unrelated to the association identifier, the process change message is deleted from the cache database.

6. The method for synchronizing approval data across business systems according to claim 1, characterized in that, It also includes targeted pre-operations, which include: Identify the customers that the business system focuses on; Establish a subscription channel between the business system and the message center regarding the followed customers; If the process change message is related to the customer being followed, the message center broadcasts the process change message to the business system based on the subscription channel; if the process change message is unrelated to the customer being followed, the business system remains in a state of refusing to receive the message.

7. The method for synchronizing approval data across business systems according to claim 2, characterized in that, Updating the change data of the process information change event to the local database of the linkable system includes: Keyword extraction is performed on the process information change events to obtain key event fields and key event data; Based on the system identifier and business number in the process information change event, the process description information related to the process information change event is retrieved. Keyword extraction is performed on the process description information to obtain process description fields and process description data. Data change review is then performed based on the process description fields, process description data, event key fields, and event key data to obtain the review result. The process description information is used to represent the business process nodes and node operation data of the business system before approval, as well as the business process nodes and node operation data of the business system after approval. In response to the verification result indicating that the data change is correct, the changed data is written to the local database of the linkable system.

8. The method for synchronizing approval data across business systems according to claim 1, characterized in that, Update the local business flow data of the business system according to the latest change data in the local database, including: The preset process matching engine is invoked based on the approval change type corresponding to the changed data; The change data is populated into the process template corresponding to the approval change type using the process matching engine to obtain the updated template; Obtain the latest process template corresponding to the approval change type stored in the local database, and perform a composite replacement on the process template and the updated template to obtain the updated process template; Business flow data is extracted based on the updated process template to obtain updated local business flow data.

9. A cross-business system approval data synchronization device, comprising: The change triggering module is used to respond to receiving an approval instruction from a single business system, obtain a process information change event, and transmit the process change information about the process information change event to a preset message center, so that the message center acts as the central hub of each business system to broadcast process change messages to each business system. The identification response module is used to enable the business system to perform data identification on the received process change message, obtain the correlation identifier, and respond to the business system being related to the correlation identifier, so that the business system opens its own online permission and forms a linkable system. The data sharing module is used to establish a system interconnection link between the single business system and the connectable system, so as to update the change data of the process information change event to the local database of the connectable system based on the system interconnection link, and close the connection permission after the change data update is completed; The data update module is used to enable each business system to update its local business flow data according to the latest change data in the local database. When a business system receives a business approval request, it performs business approval according to the latest local business flow data to obtain the approval result.

10. An electronic device, comprising: One or more processors; Storage device for storing 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 method according to any one of claims 1 to 8.

11. A computer-readable storage medium having stored thereon executable instructions that, when executed by a processor, cause the processor to perform the method according to any one of claims 1 to 8.

12. A computer program product comprising a computer program that, when executed by a processor, implements the method according to any one of claims 1 to 8.

Images