A method and system for a bus-based unified order center

Abstract

This invention provides a method and system for a unified order center based on a bus, including setting information to be calibrated and data calibration rules; obtaining a request message, using the data calibration rules to perform data matching on the information to be calibrated, and generating calibration information; determining whether the request message includes an order number; the order number supports idempotency; persisting the transaction data in the request message according to the request message; placing the calibration information with the order number in a global common message header and transmitting it to downstream business systems; the downstream business system obtaining the order number, generating a unique association with a sub-order of the business system, and returning a response message; obtaining the response message, matching the information to be calibrated according to the data calibration rules, and persisting the data. This invention solves the problems of increased difficulty and cost in business operation analysis and the creation of information silos caused by traditional order design methods where each business system provides an independent design.

Description

Technical Field

[0001] This invention belongs to the field of financial transaction technology, specifically relating to a method and system for a unified order center based on a bus. Background Technology

[0002] In the daily development of business systems, orders are a crucial parameter used to identify related transactions. However, the role of orders is limited to their respective systems, becoming a unique identifier for each business system. With the rapid development of IT infrastructure in domestic commercial banks, the number of business orders is constantly increasing, leading to greater complexity in information exchange between bank application systems and the formation of information silos. This has resulted in numerous inconsistent designs and complex relationships, causing increased difficulty and cost in business operations analysis.

[0003] Currently, commercial banks' order information is generated by various business systems and then aggregated into a data warehouse for unified processing. The order designs across these systems vary widely, ranging from 32-bit to 64-bit and even 128-bit, resulting in inconsistent designs and meanings. Furthermore, different order information often only has a specific function within a single business system, failing to provide a complete picture of a user's transaction journey within the bank or to build a standardized view of user behavior. Therefore, achieving the aggregation and integration of internal information requires design adjustments and collaborative transformation across multiple systems, a task akin to finding a needle in a haystack. In conclusion, traditional order design methods, with each business system providing its own independent design, lead to increased difficulty and cost in business operations analysis, and the creation of information silos. Summary of the Invention

[0004] The purpose of this invention is to solve the problems of current order design separation, which requires manual association, high complexity, and information silos.

[0005] To achieve the above objectives, the technical solution adopted by the present invention includes:

[0006] A bus-based unified order center method includes:

[0007] S1. Set the information and data standards to be implemented;

[0008] S2. Obtain the request message, use the data standardization rules to perform data matching on the information that needs to be standardized, and generate standardization information;

[0009] S3. Determine whether the request message includes an order number;

[0010] If the request message includes an order number, then no order number is generated;

[0011] If the request message does not include an order number, then an order number is generated;

[0012] The order number supports idempotency;

[0013] S4. Based on the request message, persist the transaction data in the request message;

[0014] S5. Place the standardization information with the order number in the global public message header and transmit it to the downstream business system;

[0015] S6. The downstream business system obtains the order number, generates a unique association with the sub-order in the business system, and returns a response message;

[0016] S7. Obtain the response message, match the information to be calibrated according to the data standardization rules, and persist the data.

[0017] Furthermore, in S2, the data standardization rules are used to perform data matching on the information that needs to be standardized. The data matching is performed according to the priority order of the requester and the interface code, the interface code, and the requester.

[0018] Furthermore, S2 also includes performing a credential stuffing test on the request message.

[0019] Furthermore, the information to be standardized in S2 includes partner organizations, channels, business products, transaction scenarios, and customer numbers; the data standardization rules include no binding, binding with request fields, binding with response fields, and fixed values.

[0020] The present invention also relates to a computer-readable storage medium, characterized in that the storage medium stores a computer program, which, when executed by a processor, implements the above-described method.

[0021] The present invention also relates to an electronic device, characterized in that it includes a memory and a processor;

[0022] The memory is used to store information that needs to be implemented, data implementation rules, request messages, implementation information, global public messages, and response messages;

[0023] The processor is used to execute computer programs stored in the memory and perform the methods described above.

[0024] The beneficial effects of this invention are as follows:

[0025] Using the bus-based unified order center method described in this invention, all business transactions can be centrally operated and managed, thereby reducing the complexity and risk of business collaboration. Simultaneously, the unified acquiring method can automatically link external channels and partner information, as well as internal business systems and product information. When a customer reports a transaction at the bank, providing an order number allows for rapid identification of the user's transaction journey. Finally, by leveraging the product and channel information linked to the order center, customer groups can be effectively identified, enabling precise product targeting. Attached Figure Description

[0026] Figure 1 This is a flowchart of a bus-based unified order center method according to the present invention.

[0027] Figure 2 This is a schematic diagram of the system architecture of a bus-based unified order center according to the present invention. Detailed Implementation

[0028] The embodiments of this application are described in detail below. Examples of these embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and are only used to explain this application, and should not be construed as limiting the invention.

[0029] Those skilled in the art will understand that, unless specifically stated otherwise, the singular forms “a,” “an,” “the,” and “the” used herein may also include the plural forms. It should be further understood that the term “comprising” as used in this application means the presence of the stated features, integers, steps, operations, elements, and / or components, but does not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof. It should be understood that when we say an element is “connected” or “coupled” to another element, it can be directly connected or coupled to the other element, or there may be intermediate elements. Furthermore, “connected” or “coupled” as used herein can include wireless connections or wireless coupling. The term “and / or” as used herein includes all or any units and all combinations of one or more associated listed items.

[0030] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be described in further detail below with reference to the accompanying drawings.

[0031] The technical solution of this application and how the technical solution of this application solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will be described below with reference to the accompanying drawings.

[0032] The first aspect of this invention relates to a method for a bus-based unified order center, the process of which is as follows: Figure 1 As shown, it includes:

[0033] Step 1: Set the information and data to be standardized and the corresponding standards rules;

[0034] Specifically, parameters associated with a business request are pre-set, i.e., the information to be standardized, such as partner organization information, channel information, business provider product information, transaction scenario information, and customer ID. There are four rules for data standardization matching: no binding, binding to request field values, binding to response field values. This application embodiment provides an example of standardization settings for a partner business request, as shown in the table below:

[0035]

[0036] Step 2: Obtain the request message, use the data standardization rules to perform data matching on the information that needs to be standardized, and generate standardization information;

[0037] Using the data standardization rules, the data matching of the information that needs to be standardized is mainly to complete the data filling operation of all fields that need to be standardized according to the agreed data standardization rules, and to perform operations such as storing the filled complete data in the database and transmitting it downstream.

[0038] Specifically, data matching is performed according to the priority order of requester and API code, API code, and requester.

[0039] Step 3: Determine whether the request message includes an order number;

[0040] If the request message includes an order number, then no order number is generated;

[0041] If the request message does not include an order number, then an order number is generated;

[0042] The order number supports idempotency;

[0043] In this embodiment, when data flows to the order center, the request message is first parsed. Optionally, the request message is verified for credentials, and a credential stuffing test is performed on the request message containing standardization information to ensure the legality and rationality of the transaction. For messages that pass verification, an order number is generated. It is determined whether the request message contains an order number. If the request message already contains order number information, such as in a query business, the original order number of the partner is used as the order credential, and a new order number is not generated. Otherwise, an order number is generated. Optionally, if the request message does not contain order number information, the snowflake algorithm is used to generate the order number.

[0044] Order numbers support idempotency. Specifically, idempotency control for order numbers is achieved using a unique database index. That is, when a business transaction number is duplicated, the global transaction number and order number remain unchanged, ensuring their uniqueness in the database. Downstream business systems then perform idempotency processing based on the global transaction number and order number, guaranteeing business continuity and accuracy. In this embodiment, the partner sends a request, generates a business transaction number, the access layer records the call log, generates a new global transaction number and sub-transaction number, the order center generates an order number and records the global transaction number and order number, sending them to the business system. If the partner sends a duplicate request, the access layer records the call log, queries the global transaction number and sub-transaction number of the previous transaction based on the business transaction number, uses them as the global transaction number and sub-transaction number for this transaction, the order center obtains the original order number idempotently based on the original global transaction number, and the downstream business system performs idempotency processing based on the original global transaction number and sub-transaction number.

[0045] Step 4: Based on the request message, persist the transaction data in the request message;

[0046] In this embodiment of the application, the credential storage operation is performed. In one optional method of this embodiment, the credential storage adopts Redis (synchronous) and DB (asynchronous) mechanisms to ensure high performance, high availability and high reliability of transactions.

[0047] Step 5: Place the standardization information with the order number in the global public message header and transmit it to the downstream business system;

[0048] In this embodiment of the application, when requesting data from downstream systems, the standardization information with the order number is placed in the global common message header and transmitted to the downstream business system through the data bus.

[0049] The data bus standardizes the data exchange methods between the order center and downstream business systems, as well as between business systems, providing a universal approach to data transmission and control logic for each component. In one optional embodiment of this application, data bus control is implemented using a globally common message header.

[0050] Step Six: The downstream business system obtains the order number, generates a unique association with the sub-order in the business system, and returns a response message;

[0051] S7. Obtain the response message, match the information to be calibrated according to the data standardization rules, and persist the data.

[0052] In this embodiment of the application, some information that needs to be calibrated needs to be set after the downstream returns a message. Therefore, after parsing the response message, it is matched according to the data calibration rules in step two, and the data is persisted to ensure the high performance, high availability and high reliability of the transaction.

[0053] The second aspect of the present invention relates to a structure as follows Figure 2 The system shown is a bus-based unified order center system, comprising:

[0054] The settings module is used to set the information and data standards that need to be implemented;

[0055] The acquisition module is used to acquire request and response messages;

[0056] The matching module is used to perform data matching on the information to be standardized using the data standardization rules;

[0057] The judgment module is used to determine whether the request message contains an order number;

[0058] The generation module is used to generate order numbers;

[0059] The storage module is used to store information that needs to be implemented, data implementation rules, request messages, implementation information, global public messages, and response messages.

[0060] This system enables the implementation of the aforementioned methods, allowing for centralized operation and management of all business transactions, thereby reducing the complexity and risk of business collaboration. Simultaneously, the unified acquiring method automatically links external channels and partner information, as well as internal business systems and product information. When a customer reports a transaction at the bank, providing an order number allows for rapid identification of the user's transaction journey. Finally, by leveraging the product and channel information linked to the order center, customer groups can be effectively identified, enabling precise product targeting.

[0061] The above description is merely a preferred embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in the present invention should be included within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

1. A method for a bus-based unified order center, characterized in that, include: S1. Set the information and data standards to be implemented; S2. Obtain the request message, use the data standardization rules to perform data matching on the information that needs to be standardized, and generate standardization information; S3. Determine whether the request message includes an order number; If the request message includes an order number, then no order number is generated; If the request message does not include an order number, the snowflake algorithm is used to generate the order number. The order number supports idempotency, wherein the idempotency of the order number is controlled by a unique index in the database; S4. Based on the request message, persist the transaction data in the request message; S5. Place the standardization information with the order number in the global public message header and transmit it to the downstream business system; S6. The downstream business system obtains the order number, generates a unique association with the sub-order in the business system, and returns a response message; S7. Obtain the response message, match the information to be calibrated according to the data standardization rules, and persist the data. In step S2, the data standardization rules are used to perform data matching on the information that needs to be standardized. The data matching is performed according to the priority order of requester and interface code, interface code, and requester.

2. The method as described in claim 1, characterized in that, S2 also includes performing a credential stuffing test on the request message.

3. The method as described in claim 2, characterized in that, The information that needs to be standardized in S2 includes partner organizations, channels, business products, transaction scenarios, and customer numbers; the data standardization rules include no binding, binding to request fields, binding to response fields, and fixed values.

4. A bus-based unified order center system, characterized in that, A method for performing any of the methods of claims 1-3, comprising: The settings module is used to set the information and data standards that need to be implemented; The acquisition module is used to acquire request and response messages; The matching module is used to perform data matching on the information to be standardized using the data standardization rules; The judgment module is used to determine whether the request message contains an order number; The generation module is used to generate order numbers; The storage module is used to store information that needs to be implemented, data implementation rules, request messages, implementation information, global public messages, and response messages.

5. A computer-readable storage medium, characterized in that, The storage medium stores a computer program, which, when executed by a processor, implements the method of any one of claims 1 to 3.

6. An electronic device, characterized in that, Including processor and memory; The memory is used to store information that needs to be implemented, data implementation rules, request messages, implementation information, global public messages, and response messages; The processor is configured to execute a computer program stored in a memory, performing the method according to any one of claims 1 to 3.

Images