CN112258166A - Transaction request processing method and device - Google Patents

Transaction request processing method and device Download PDF

Info

Publication number
CN112258166A
CN112258166A CN202011193623.7A CN202011193623A CN112258166A CN 112258166 A CN112258166 A CN 112258166A CN 202011193623 A CN202011193623 A CN 202011193623A CN 112258166 A CN112258166 A CN 112258166A
Authority
CN
China
Prior art keywords
transaction
white list
customer
application
transaction request
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202011193623.7A
Other languages
Chinese (zh)
Inventor
栾博
李承文
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
China Construction Bank Corp
Original Assignee
China Construction Bank Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by China Construction Bank Corp filed Critical China Construction Bank Corp
Priority to CN202011193623.7A priority Critical patent/CN112258166A/en
Publication of CN112258166A publication Critical patent/CN112258166A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/02Payment architectures, schemes or protocols involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
    • G06Q20/027Payment architectures, schemes or protocols involving a neutral party, e.g. certification authority, notary or trusted third party [TTP] involving a payment switch or gateway
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/38Payment protocols; Details thereof
    • G06Q20/40Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • G06Q20/401Transaction verification
    • G06Q20/4014Identity check for transactions

Landscapes

  • Business, Economics & Management (AREA)
  • Engineering & Computer Science (AREA)
  • Accounting & Taxation (AREA)
  • Computer Security & Cryptography (AREA)
  • Strategic Management (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Finance (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

The application provides a transaction request processing method and a transaction request processing device, wherein the method comprises the following steps: acquiring a transaction request to be processed, wherein the transaction request to be processed carries a transaction type and a customer identity; acquiring a preset transaction white list and a client white list; determining whether the transaction type is in a transaction white list; if the transaction type is in the transaction white list, determining whether a customer identity is in a customer white list; if the customer identity is identified in the customer white list, the global routing routes the pending transaction request to a transaction application of the first system platform for processing. By the scheme, the technical problem that the existing transaction system cannot run in a parallel track mode is solved, and the technical effect of simply and efficiently running in a parallel track mode stably is achieved.

Description

Transaction request processing method and device
Technical Field
The present application belongs to the technical field of data processing, and in particular, to a transaction request processing method and apparatus.
Background
At present, transaction systems of banks generally run on servers based on an X86 architecture, and if the servers of the X86 architecture are out of service, no servers capable of running the systems exist. Considering that the transaction system may be run in parallel in a server of the X86 architecture and a server of another architecture (e.g., a server of the ARM architecture), some attempts may be made to transfer some transaction systems to run on the server of the ARM architecture.
However, considering that if these transaction systems are directly transferred to the server of the ARM architecture to be operated, the reliability and stability of the transaction systems are not guaranteed, a gradual transition is required, and thus, there is a need for parallel operation.
An effective solution is not proposed at present for how to enable the transaction system to run on the x86 architecture server and the ARM architecture server at the same time in parallel and ensure the continuity and stability of the transaction.
Disclosure of Invention
The application aims to provide a transaction request processing method and device, which can realize the parallel operation of transaction applications.
The application provides a transaction request processing method and a device, which are realized as follows:
in one aspect, a transaction request processing method is provided, the method including:
acquiring a transaction request to be processed, wherein the transaction request to be processed carries a transaction type and a customer identity;
acquiring a preset transaction white list and a client white list;
determining whether the transaction type is in a transaction white list;
if the transaction type is in the transaction white list, determining whether a customer identity is in a customer white list;
if the customer identity is identified in the customer white list, the global routing routes the pending transaction request to a transaction application of the first system platform for processing.
In one embodiment, after determining whether the transaction type is on a transaction white list, further comprising:
if the transaction type is not in the transaction white list, global routing routes the pending transaction request to a transaction application process of a second system platform, wherein the transaction application of the second system platform is a transaction application on a server based on an X86 architecture, and the transaction application of the first system platform is a transaction application on a server based on a non-X86 architecture.
In one embodiment, after determining whether the client identifier is in the client white list, the method further comprises:
if the customer identity is not in the customer white list, the global routing routes the pending transaction request to a transaction application of the second system platform for processing.
In one embodiment, further comprising:
the global routing establishes a transaction white list according to the dependence of a configuration center client;
the global routing synchronizes the transaction white list to a local cache;
and when the transaction white list changes, updating the transaction white list by triggering a monitoring mechanism.
In one embodiment, further comprising:
and storing the client white list in a redis cluster in a fragmentation mode.
In one embodiment, obtaining a preset transaction white list includes:
and acquiring the transaction white list from a zookeeper configuration center.
In another aspect, a transaction request processing apparatus is provided, including:
the system comprises a first acquisition module, a second acquisition module and a third acquisition module, wherein the first acquisition module is used for acquiring a transaction request to be processed, and the transaction request to be processed carries a transaction type and a customer identity;
the second acquisition module is used for acquiring a preset transaction white list and a client white list;
a first determination module to determine whether the transaction type is in a transaction white list;
a second determination module for determining whether the customer identification is in a customer white list if the transaction type is in the transaction white list;
and the first routing module is used for routing the transaction request to be processed to the transaction application processing of the first system platform by global routing under the condition that the customer identity is in the customer white list.
In one embodiment, the above apparatus further comprises:
a second routing module, configured to, in a case that the transaction type is not in the transaction white list, globally route the pending transaction request to a transaction application of a second system platform for processing, where the transaction application of the second system platform is a transaction application on a server based on an X86 architecture, and the transaction application of the first system platform is a transaction application on a server based on a non-X86 architecture.
In yet another aspect, a server device is provided, which includes a processor and a memory for storing processor-executable instructions, and when the processor executes the instructions, the steps of the method are implemented as follows:
acquiring a transaction request to be processed, wherein the transaction request to be processed carries a transaction type and a customer identity;
acquiring a preset transaction white list and a client white list;
determining whether the transaction type is in a transaction white list;
if the transaction type is in the transaction white list, determining whether a customer identity is in a customer white list;
if the customer identity is identified in the customer white list, the global routing routes the pending transaction request to a transaction application of the first system platform for processing.
In yet another aspect, a computer-readable storage medium is provided having computer instructions stored thereon which, when executed, implement the steps of the method of:
acquiring a transaction request to be processed, wherein the transaction request to be processed carries a transaction type and a customer identity;
acquiring a preset transaction white list and a client white list;
determining whether the transaction type is in a transaction white list;
if the transaction type is in the transaction white list, determining whether a customer identity is in a customer white list;
if the customer identity is identified in the customer white list, the global routing routes the pending transaction request to a transaction application of the first system platform for processing.
According to the transaction request processing method, after a to-be-processed transaction request carrying a transaction type and a customer identity is obtained, whether the transaction type is in a transaction white list or not is determined, whether the customer identity is in the customer white list or not is determined, and the to-be-processed transaction request is routed to a transaction application of a first system platform for processing under the condition that the transaction type and the customer identity are both determined to be in the white list. The technical problem that the existing trading system cannot run in parallel is solved through the scheme, and the technical effect of simply and efficiently stably running in parallel is achieved.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, it is obvious that the drawings in the following description are only some embodiments described in the present application, and for those skilled in the art, other drawings can be obtained according to the drawings without any creative effort.
FIG. 1 is a method flow diagram of one embodiment of a transaction request processing method provided herein;
FIG. 2 is a schematic diagram of the configuration and updating of a transaction white list provided herein;
FIG. 3 is a flow chart of a transaction for a white list customer as provided herein;
FIG. 4 is an architecture diagram of a server terminal provided herein;
fig. 5 is a block diagram of a transaction request processing apparatus according to the present application.
Detailed Description
In order to make those skilled in the art better understand the technical solutions in the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
FIG. 1 is a method flow diagram of one embodiment of a transaction request processing method described herein. Although the present application provides method operational steps or apparatus configurations as illustrated in the following examples or figures, more or fewer operational steps or modular units may be included in the methods or apparatus based on conventional or non-inventive efforts. In the case of steps or structures which do not logically have the necessary cause and effect relationship, the execution sequence of the steps or the module structure of the apparatus is not limited to the execution sequence or the module structure described in the embodiments and shown in the drawings of the present application. When the described method or module structure is applied in an actual device or end product, the method or module structure according to the embodiments or shown in the drawings can be executed sequentially or executed in parallel (for example, in a parallel processor or multi-thread processing environment, or even in a distributed processing environment).
Specifically, as shown in fig. 1, a transaction request processing method provided in an embodiment of the present application may include:
step 101: acquiring a transaction request to be processed, wherein the transaction request to be processed carries a transaction type and a customer identity;
i.e. the transaction type from which the transaction request is obtained, and the identity of the customer, in case the transaction request is pending. And a transaction white list and a customer white list are set for the first system platform, only the transaction requests which are positioned in the transaction white list and in the customer white list are routed to the first system platform for processing, otherwise, the transaction requests are routed to the second system platform for processing, or else, the transaction requests cannot be processed in the first system platform.
Step 102: acquiring a preset transaction white list and a client white list;
the transaction white list and the client white list can be preset, and only need to be called when in use.
Step 103: determining whether the transaction type is in a transaction white list;
step 104: if the transaction type is in the transaction white list, determining whether a customer identity is in a customer white list;
step 105: if the customer identity is identified in the customer white list, the global routing routes the pending transaction request to a transaction application of the first system platform for processing.
In the above example, after the pending transaction request carrying the transaction type and the customer identity is obtained, it is determined whether the transaction type is in the transaction white list, and it is determined whether the customer identity is in the customer white list, and the pending transaction request is routed to the transaction application of the first system platform for processing only when it is determined that both the transaction type and the customer identity are in the white list. The technical problem that the existing trading system cannot run in parallel is solved through the scheme, and the technical effect of simply and efficiently stably running in parallel is achieved.
Specifically, after determining whether the transaction type is in a transaction white list, if the transaction type is not in the transaction white list, the global routing routes the pending transaction request to a transaction application of a second system platform for processing, wherein the transaction application of the second system platform is a transaction application on a server based on an X86 architecture, and the transaction application of the first system platform is a transaction application on a server based on a non-X86 architecture.
That is, the transaction application of the first system platform is a transaction application on a server based on a non-X86 architecture, and for example, may be a transaction application on a server based on an ARM architecture.
Further, after determining whether the customer identification is in the customer white list, if the customer identification is not in the customer white list, the global routing routes the pending transaction request to a transaction application of the second system platform for processing. That is, it is preferably determined whether the transaction type is on the transaction whitelist, and if not, it is routed to the transaction application on the X86 architecture based server, and if the transaction type is on the transaction whitelist, but the customer identification is not on the customer whitelist, it is also routed to the transaction application on the X86 architecture based server.
Specifically, the above-mentioned transaction white list may be created by the global routing according to the client dependency of the configuration center, and then the global routing synchronizes the transaction white list to the local cache, and when the transaction white list changes, the update of the transaction white list is triggered by the monitoring mechanism. When a preset transaction white list is obtained, the transaction white list can be obtained from a zookeeper configuration center.
For the client white list, the client white list may be stored in a redis cluster in a shard form.
The above method is described below with reference to a specific example, however, it should be noted that the specific example is only for better describing the present application and is not to be construed as limiting the present application.
In order to avoid all trading systems running on servers of the X86 architecture, if a server of the X86 architecture becomes down, then there will be no server on which the system can run. Considering that the transaction system can be operated in parallel in a server of an X86 architecture and a server of another architecture (for example, a server of an ARM architecture), different transactions and clients are shunted into the two systems by means of a white list, thereby ensuring the stability and high availability of the operation of the two systems.
Specifically, a client white list strategy and a transaction white list strategy can be set, so that transaction routing can be performed in two system platforms, a system cluster consisting of the two systems provides a consistent bank service function outwards to ensure the parallel stable operation of the two systems, and the function and performance of the system of the other platform can be effectively verified on the premise of ensuring the high availability and stability of the whole financial transaction system. The white list routing means that a white list strategy is established for data such as banking business transaction and customer information, and the data is distributed to the dual systems through the white list strategy routing, so that high availability of the whole system for providing services to the outside is guaranteed.
The double-system parallel operation scheme is designed by using a transaction white list and a customer white list and combining with global routing service, a set of complete double-track operation scheme facing finance and based on a white list strategy is provided, and the database gradually becomes the bottleneck of system performance in a high-concurrency information system, so that the reading speed of data and the system concurrency capability can be improved by using a cache mode, and the pressure of the system database is relieved.
Specifically, as shown in fig. 2, a transaction white list service may be provided by using a combination of zookeeper and nginx, where zookeeper is an open-source distributed application coordination service, and provides a consistent service framework for a distributed cluster. zookeeper can provide a watch mechanism to monitor changes in node data to implement functions of a transaction configuration center, with transaction white list information stored in data nodes of zookeeper. Nginx monitors the transaction data information of the transaction white list by using a watch mechanism of zookeeper and caches the transaction white list to the local. zookeeper and nginx are both deployed in a clustered fashion, thereby ensuring high availability of the transaction white list function.
Based on this, the operation can be performed as follows:
s1: the transaction routing establishes a transaction white list watch for monitoring through configuring the dependence of a central client;
s2: initializing synchronous transaction white list data to a local cache by a transaction route;
s3: when the transaction white list data changes, the watch monitoring triggers an updating mechanism to enable a transaction route to actively initiate the operation of updating the transaction white list;
s4: the transaction routing actively triggers the white list updating operation through the transaction.
In this example, a white list client information storage scheme based on a cache center is proposed, and the cache center provides relevant key-value pair information, such as: customer number, card number, etc. The client white list cache realizes a cache center by adopting redis, which is an open-source distributed NoSQL database system and supports various data storage formats. The white list client information is stored in a Redis cluster in a fragmentation mode by adopting a Redis cluster mode, and the Redis cluster is a distributed solution of Redis, so that the high availability and the memory storage performance of the cache center cluster are improved. And realizing a dual-system parallel operation scheme by a dual white list scheme of a transaction white list and a client white list. Specifically, the white list based customer transaction process may be as shown in fig. 3, and includes the following steps:
s1: the channel initiates white list transaction of the white list client to the global routing module;
s2: the global routing module acquires white list transaction information from a zookeeper configuration center;
s3: the global routing module inquires whether the client is a white list client or not in the redis white list cache and judges that the transaction is a white list client transaction;
s4: the global routing module acquires a routing strategy of the transaction from a zookeeper configuration center;
s5: the global routing module routes the transactions of the white-list customers to the AP of the domestic financial transaction platform.
For a non-white list customer transaction flow, the following steps may be included:
s1: the channel initiates white list transaction of non-white list clients to the global routing module;
s2: the global routing module acquires white list transaction information from a zookeeper configuration center;
s3: the global routing module inquires whether the client is a white list client or not in the redis white list cache, and judges that the transaction is a non-white list client transaction;
s4: the global routing module acquires a routing strategy of the transaction from a zookeeper configuration center;
s5: the global routing module routes the white-listed customers' transactions to the APs of the traditional x86 financial transaction platform.
In the above example, a scheme that an ARM platform and a conventional X86 platform operate in parallel is adopted, a white list caching policy is routed to a transaction dual system based on a redis client, and a white list transaction and a transaction routing policy are acquired through a zookeeper, so that ARM system transaction and X86 system transaction can be simultaneously supported. By providing a complete white list transaction strategy scheme, the method can be widely applied to system construction of financial industry and other industries, and has little influence on the operation of the existing system.
The method embodiments provided by the above embodiments of the present application may be executed in a server terminal, a computer terminal, or a similar computing device. Taking the example of the operation on the server terminal, fig. 4 is a hardware structure block diagram of a computer terminal of a transaction request processing method according to an embodiment of the present invention. As shown in fig. 4, the server terminal 10 may include one or more (only one shown) processors 102 (the processors 102 may include, but are not limited to, a processing device such as a microprocessor MCU or a programmable logic device FPGA, etc.), a memory 104 for storing data, and a transmission module 106 for communication functions. It will be understood by those skilled in the art that the structure shown in fig. 4 is only an illustration and is not intended to limit the structure of the electronic device. For example, the server terminal 10 may also include more or fewer components than shown in FIG. 4, or have a different configuration than shown in FIG. 4.
The memory 104 may be used to store software programs and modules of application software, such as program instructions/modules corresponding to the transaction request processing method in the embodiment of the present invention, and the processor 102 executes various functional applications and data processing by running the software programs and modules stored in the memory 104, that is, implements the transaction request processing method of the application program. The memory 104 may include high speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 104 may further include memory located remotely from the processor 102, which may be connected to the computer terminal 10 via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The transmission module 106 is used to receive or transmit data via a network. Specific examples of the network described above may include a wireless network provided by a communication provider of the computer terminal 10. In one example, the transmission module 106 includes a Network adapter (NIC) that can be connected to other Network devices through a base station to communicate with the internet. In one example, the transmission module 106 may be a Radio Frequency (RF) module, which is used for communicating with the internet in a wireless manner.
On the software level, the above apparatus may be as shown in fig. 5, and may include:
a first obtaining module 501, configured to obtain a pending transaction request, where the pending transaction request carries a transaction type and a client identity;
a second obtaining module 502, configured to obtain a preset transaction white list and a client white list;
a first determining module 503, configured to determine whether the transaction type is in a transaction white list;
a second determining module 504, configured to determine whether the customer identity is in a customer white list if the transaction type is in the transaction white list;
and a first routing module 505, configured to, in a case that the customer identity is in a customer white list, route the pending transaction request to a transaction application of the first system platform for processing by global routing.
In one embodiment, the apparatus may further include: a second routing module, configured to, in a case that the transaction type is not in the transaction white list, globally route the pending transaction request to a transaction application of a second system platform for processing, where the transaction application of the second system platform is a transaction application on a server based on an X86 architecture, and the transaction application of the first system platform is a transaction application on a server based on a non-X86 architecture.
In one embodiment, after determining whether the customer id is in the customer white list, the transaction request processing device routes the pending transaction request to a transaction application of the second system platform for processing by global routing if the customer id is not in the customer white list.
In an embodiment, the transaction request processing apparatus may be further configured to control the global routing to establish a transaction white list according to a configuration center client dependency; the global routing synchronizes the transaction white list to a local cache; and when the transaction white list changes, updating the transaction white list by triggering a monitoring mechanism.
In one embodiment, the transaction request processing device may be further configured to store the client white list in a redis cluster in a form of a segment.
In one embodiment, the second obtaining module 502 may obtain the transaction white list from a zookeeper configuration center.
An embodiment of the present application further provides a specific implementation manner of an electronic device, which is capable of implementing all steps in the transaction request processing method in the foregoing embodiment, where the electronic device specifically includes the following contents: a processor (processor), a memory (memory), a communication Interface (Communications Interface), and a bus; the processor, the memory and the communication interface complete mutual communication through the bus; the processor is configured to call a computer program in the memory, and the processor implements all the steps of the transaction request processing method in the above embodiments when executing the computer program, for example, the processor implements the following steps when executing the computer program:
step 1: acquiring a transaction request to be processed, wherein the transaction request to be processed carries a transaction type and a customer identity;
step 2: acquiring a preset transaction white list and a client white list;
and step 3: determining whether the transaction type is in a transaction white list;
and 4, step 4: if the transaction type is in the transaction white list, determining whether a customer identity is in a customer white list;
and 5: if the customer identity is identified in the customer white list, the global routing routes the pending transaction request to a transaction application of the first system platform for processing.
As can be seen from the above description, in the embodiment of the present application, after the pending transaction request carrying the transaction type and the customer identity is obtained, it is determined whether the transaction type is in the transaction white list, and it is determined whether the customer identity is in the customer white list, and the pending transaction request is routed to the transaction application of the first system platform for processing only when it is determined that both the transaction type and the customer identity are in the white list. The technical problem that the existing trading system cannot run in parallel is solved through the scheme, and the technical effect of simply and efficiently stably running in parallel is achieved.
Embodiments of the present application further provide a computer-readable storage medium capable of implementing all steps in the transaction request processing method in the above embodiments, where the computer-readable storage medium stores thereon a computer program, and when the computer program is executed by a processor, the computer program implements all steps of the transaction request processing method in the above embodiments, for example, when the processor executes the computer program, the processor implements the following steps:
step 1: acquiring a transaction request to be processed, wherein the transaction request to be processed carries a transaction type and a customer identity;
step 2: acquiring a preset transaction white list and a client white list;
and step 3: determining whether the transaction type is in a transaction white list;
and 4, step 4: if the transaction type is in the transaction white list, determining whether a customer identity is in a customer white list;
and 5: if the customer identity is identified in the customer white list, the global routing routes the pending transaction request to a transaction application of the first system platform for processing.
As can be seen from the above description, in the embodiment of the present application, after the pending transaction request carrying the transaction type and the customer identity is obtained, it is determined whether the transaction type is in the transaction white list, and it is determined whether the customer identity is in the customer white list, and the pending transaction request is routed to the transaction application of the first system platform for processing only when it is determined that both the transaction type and the customer identity are in the white list. The technical problem that the existing trading system cannot run in parallel is solved through the scheme, and the technical effect of simply and efficiently stably running in parallel is achieved.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the hardware + program class embodiment, since it is substantially similar to the method embodiment, the description is simple, and the relevant points can be referred to the partial description of the method embodiment.
The foregoing description has been directed to specific embodiments of this disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.
Although the present application provides method steps as described in an embodiment or flowchart, additional or fewer steps may be included based on conventional or non-inventive efforts. The order of steps recited in the embodiments is merely one manner of performing the steps in a multitude of orders and does not represent the only order of execution. When an actual apparatus or client product executes, it may execute sequentially or in parallel (e.g., in the context of parallel processors or multi-threaded processing) according to the embodiments or methods shown in the figures.
The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. One typical implementation device is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a vehicle-mounted human-computer interaction device, a cellular telephone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.
Although embodiments of the present description provide method steps as described in embodiments or flowcharts, more or fewer steps may be included based on conventional or non-inventive means. The order of steps recited in the embodiments is merely one manner of performing the steps in a multitude of orders and does not represent the only order of execution. When an actual apparatus or end product executes, it may execute sequentially or in parallel (e.g., parallel processors or multi-threaded environments, or even distributed data processing environments) according to the method shown in the embodiment or the figures. The terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, the presence of additional identical or equivalent elements in a process, method, article, or apparatus that comprises the recited elements is not excluded.
For convenience of description, the above devices are described as being divided into various modules by functions, and are described separately. Of course, in implementing the embodiments of the present description, the functions of each module may be implemented in one or more software and/or hardware, or a module implementing the same function may be implemented by a combination of multiple sub-modules or sub-units, and the like. The above-described embodiments of the apparatus are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
Those skilled in the art will also appreciate that, in addition to implementing the controller as pure computer readable program code, the same functionality can be implemented by logically programming method steps such that the controller is in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers and the like. Such a controller may therefore be considered as a hardware component, and the means included therein for performing the various functions may also be considered as a structure within the hardware component. Or even means for performing the functions may be regarded as being both a software module for performing the method and a structure within a hardware component.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.
Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.
As will be appreciated by one skilled in the art, embodiments of the present description may be provided as a method, system, or computer program product. Accordingly, embodiments of the present description may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, embodiments of the present description may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and so forth) having computer-usable program code embodied therein.
The embodiments of this specification may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The described embodiments may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the system embodiment, since it is substantially similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment. In the description herein, references to the description of the term "one embodiment," "some embodiments," "an example," "a specific example," or "some examples," etc., mean that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of an embodiment of the specification. In this specification, the schematic representations of the terms used above are not necessarily intended to refer to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples. Furthermore, various embodiments or examples and features of different embodiments or examples described in this specification can be combined and combined by one skilled in the art without contradiction.
The above description is only an example of the embodiments of the present disclosure, and is not intended to limit the embodiments of the present disclosure. Various modifications and variations to the embodiments described herein will be apparent to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the embodiments of the present specification should be included in the scope of the claims of the embodiments of the present specification.

Claims (10)

1. A transaction request processing method, the method comprising:
acquiring a transaction request to be processed, wherein the transaction request to be processed carries a transaction type and a customer identity;
acquiring a preset transaction white list and a client white list;
determining whether the transaction type is in a transaction white list;
if the transaction type is in the transaction white list, determining whether a customer identity is in a customer white list;
if the customer identity is identified in the customer white list, the global routing routes the pending transaction request to a transaction application of the first system platform for processing.
2. The method of claim 1, after determining whether the transaction type is on a transaction white list, further comprising:
if the transaction type is not in the transaction white list, global routing routes the pending transaction request to a transaction application process of a second system platform, wherein the transaction application of the second system platform is a transaction application on a server based on an X86 architecture, and the transaction application of the first system platform is a transaction application on a server based on a non-X86 architecture.
3. The method of claim 2, after determining whether the customer identification is in a customer white list, further comprising:
if the customer identity is not in the customer white list, the global routing routes the pending transaction request to a transaction application of the second system platform for processing.
4. The method of claim 1, further comprising:
the global routing establishes a transaction white list according to the dependence of a configuration center client;
the global routing synchronizes the transaction white list to a local cache;
and when the transaction white list changes, updating the transaction white list by triggering a monitoring mechanism.
5. The method of claim 1, further comprising:
and storing the client white list in a redis cluster in a fragmentation mode.
6. The method of claim 1, wherein obtaining a pre-defined white list of transactions comprises:
and acquiring the transaction white list from a zookeeper configuration center.
7. A transaction request processing apparatus, comprising:
the system comprises a first acquisition module, a second acquisition module and a third acquisition module, wherein the first acquisition module is used for acquiring a transaction request to be processed, and the transaction request to be processed carries a transaction type and a customer identity;
the second acquisition module is used for acquiring a preset transaction white list and a client white list;
a first determination module to determine whether the transaction type is in a transaction white list;
a second determination module for determining whether the customer identification is in a customer white list if the transaction type is in the transaction white list;
and the first routing module is used for routing the transaction request to be processed to the transaction application processing of the first system platform by global routing under the condition that the customer identity is in the customer white list.
8. The apparatus of claim 7, further comprising:
a second routing module, configured to, in a case that the transaction type is not in the transaction white list, globally route the pending transaction request to a transaction application of a second system platform for processing, where the transaction application of the second system platform is a transaction application on a server based on an X86 architecture, and the transaction application of the first system platform is a transaction application on a server based on a non-X86 architecture.
9. A server device comprising a processor and a memory for storing processor-executable instructions, the instructions when executed by the processor implementing the steps of the method of:
acquiring a transaction request to be processed, wherein the transaction request to be processed carries a transaction type and a customer identity;
acquiring a preset transaction white list and a client white list;
determining whether the transaction type is in a transaction white list;
if the transaction type is in the transaction white list, determining whether a customer identity is in a customer white list;
if the customer identity is identified in the customer white list, the global routing routes the pending transaction request to a transaction application of the first system platform for processing.
10. A computer readable storage medium having stored thereon computer instructions which, when executed, implement the steps of a method comprising:
acquiring a transaction request to be processed, wherein the transaction request to be processed carries a transaction type and a customer identity;
acquiring a preset transaction white list and a client white list;
determining whether the transaction type is in a transaction white list;
if the transaction type is in the transaction white list, determining whether a customer identity is in a customer white list;
if the customer identity is identified in the customer white list, the global routing routes the pending transaction request to a transaction application of the first system platform for processing.
CN202011193623.7A 2020-10-30 2020-10-30 Transaction request processing method and device Pending CN112258166A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202011193623.7A CN112258166A (en) 2020-10-30 2020-10-30 Transaction request processing method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202011193623.7A CN112258166A (en) 2020-10-30 2020-10-30 Transaction request processing method and device

Publications (1)

Publication Number Publication Date
CN112258166A true CN112258166A (en) 2021-01-22

Family

ID=74267866

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202011193623.7A Pending CN112258166A (en) 2020-10-30 2020-10-30 Transaction request processing method and device

Country Status (1)

Country Link
CN (1) CN112258166A (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113469669A (en) * 2021-07-16 2021-10-01 中国银行股份有限公司 Method for querying client information across instances, related device and computer storage medium

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110390529A (en) * 2019-07-23 2019-10-29 中国工商银行股份有限公司 Transaction method for intelligently routing, device, equipment and storage medium
CN110443593A (en) * 2019-08-07 2019-11-12 网联清算有限公司 Transaction processing method and device, transaction processing system and computer system
CN110955469A (en) * 2019-11-25 2020-04-03 中国银行股份有限公司 Method and device for online transaction by X86 platform distributed batch call

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110390529A (en) * 2019-07-23 2019-10-29 中国工商银行股份有限公司 Transaction method for intelligently routing, device, equipment and storage medium
CN110443593A (en) * 2019-08-07 2019-11-12 网联清算有限公司 Transaction processing method and device, transaction processing system and computer system
CN110955469A (en) * 2019-11-25 2020-04-03 中国银行股份有限公司 Method and device for online transaction by X86 platform distributed batch call

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113469669A (en) * 2021-07-16 2021-10-01 中国银行股份有限公司 Method for querying client information across instances, related device and computer storage medium

Similar Documents

Publication Publication Date Title
US20200328984A1 (en) Method and apparatus for allocating resource
CN112152926B (en) Method and device for managing network slices of application
US20210219004A1 (en) Method and apparatus for an enhanced data pipeline
KR20210119504A (en) Communication method and apparatus, entity and computer readable storage medium
US20130227547A1 (en) Adaptable middleware layer
CN111355816A (en) Server selection method, device, equipment and distributed service system
US11102284B2 (en) Service processing methods and systems based on a consortium blockchain network
CN110765165A (en) Method, device and system for synchronously processing cross-system data
CN112202829A (en) Social robot scheduling system and scheduling method based on micro-service
US20210073850A1 (en) Redemption code distribution
US11822983B2 (en) Controller for off-cluster operations
CN114020444B (en) Calling system and method for resource service application in enterprise digital middle station
CN104580506A (en) Offline map data obtaining method, cloud server and client-side
CN109828830B (en) Method and apparatus for managing containers
CN109343970B (en) Application program-based operation method and device, electronic equipment and computer medium
CN112258166A (en) Transaction request processing method and device
CN111245940B (en) Method and device for processing mobile communication signal data in communication module of Internet of things
CN111831448A (en) Request processing method and device and electronic equipment
US10901972B2 (en) Table partition configuration method, apparatus and system for database system
CN110620734A (en) TCP link data processing method and device
US11429593B2 (en) Maintaining a shared state among networked computing devices using a shared data store
CN116841720A (en) Resource allocation method, apparatus, computer device, storage medium and program product
CN111200608B (en) Link information processing method and device
CN113391882A (en) Virtual machine memory management method and device, storage medium and electronic equipment
CN105824712A (en) Method and device for executing business logic

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination