CN114663226A - Transaction request processing method and device and transaction transfer system - Google Patents

Transaction request processing method and device and transaction transfer system Download PDF

Info

Publication number
CN114663226A
CN114663226A CN202011528696.7A CN202011528696A CN114663226A CN 114663226 A CN114663226 A CN 114663226A CN 202011528696 A CN202011528696 A CN 202011528696A CN 114663226 A CN114663226 A CN 114663226A
Authority
CN
China
Prior art keywords
transaction
identifier
policy
transaction request
identification
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
CN202011528696.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.)
NetsUnion Clearing Corp
Original Assignee
NetsUnion Clearing 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 NetsUnion Clearing Corp filed Critical NetsUnion Clearing Corp
Priority to CN202011528696.7A priority Critical patent/CN114663226A/en
Priority to PCT/CN2021/136569 priority patent/WO2022135158A1/en
Publication of CN114663226A publication Critical patent/CN114663226A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION 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
    • G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/04—Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/48—Program initiating; Program switching, e.g. by interrupt
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • Accounting & Taxation (AREA)
  • Finance (AREA)
  • Software Systems (AREA)
  • General Physics & Mathematics (AREA)
  • Development Economics (AREA)
  • Technology Law (AREA)
  • General Business, Economics & Management (AREA)
  • Strategic Management (AREA)
  • Marketing (AREA)
  • Economics (AREA)
  • General Engineering & Computer Science (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
  • Debugging And Monitoring (AREA)

Abstract

The application discloses a transaction request processing method, a transaction request processing device and a transaction transfer system, wherein the method is applied to each transaction transfer server in the transaction transfer system and comprises the following steps: acquiring a system policy identifier, wherein the system policy identifier is a policy identifier effective to the transaction transfer system; updating local policy identifications according to the system policy identifications, wherein the local policy identifications are the policy identifications which take effect on each transaction transfer server; processing the received transaction request according to the updated local policy identifier; and determining the reported information according to the transaction request processing result. According to the method and the system, the uniform system strategy identification is set for the whole transaction transfer system, so that each transaction transfer server in the transaction transfer system can acquire the same local strategy identification, and compared with the existing local automatic degradation mechanism, the system degradation mechanism ensures the consistency of processing the same transaction request, and avoids the problems that the transaction request cannot be processed in an idempotent way and the like.

Description

Transaction request processing method and device and transaction transfer system
Technical Field
The present application relates to the field of financial technologies, and in particular, to a transaction request processing method, an apparatus and a transaction forwarding system.
Background
When an existing clearing platform processes a transaction request, the following modes are mainly adopted: firstly, after a server in a target data center receives a transaction request, a transaction switching system in the server determines the business logic of the transaction according to the message number of the transaction request; then, the data of the transaction request is sent to a transaction verification system for validity and business logic verification, the transaction request which is not verified is rejected, the transaction data can be forwarded to a bank front-end module of the data center for the transaction request which is verified to be passed, and the bank front-end module encrypts and assembles the message and sends the message to a target bank; and after receiving the assembled message, the target bank analyzes the message to obtain message information, and finally checks and accounts-in and accounts-out processing is carried out according to the transaction information and the business logic in the message.
However, the conventional transaction request processing method has the problems that the transaction request cannot be processed in an idempotent manner, the transaction loss rate is high, and the like.
Disclosure of Invention
The embodiment of the application provides a transaction request processing method, a transaction request processing device and a transaction transfer system, so that the transaction loss rate and the transaction risk are reduced.
The embodiment of the application adopts the following technical scheme:
in a first aspect, an embodiment of the present application provides a method for processing a transaction request, which is applied to each transaction forwarding server in a transaction forwarding system, where the method includes:
acquiring a system policy identifier, wherein the system policy identifier is a policy identifier effective to the transaction transfer system;
updating local policy identifications according to the system policy identifications, wherein the local policy identifications are the policy identifications effective to the transaction transfer servers;
processing the received transaction request according to the updated local policy identifier;
and determining the reported information according to the transaction request processing result.
Optionally, the transaction forwarding system further includes a preset Redis database, where the system policy identifier is stored in the Redis database, and the obtaining the system policy identifier includes:
determining a Redis state identifier of the Redis database;
and under the condition that the Redis state identifier indicates that the Redis database is normal, requesting the Redis database to acquire the system policy identifier.
Optionally, the method further comprises:
determining the number of times of request failure according to the result of the request to the Redis database;
and if the number of times of the request failure reaches a first threshold value within preset time, updating the Redis state identifier into a Redis fault identifier, wherein the Redis fault identifier is used for indicating the Redis database fault.
Optionally, the method further comprises:
reporting the reporting information to the Redis database so that the Redis database can update the system policy identifier according to the reporting information;
determining the number of times of reporting failure according to the reporting result;
and if the reporting failure times reach a second threshold value, updating the Redis state identifier to a Redis fault identifier.
Optionally, the system policy identifier includes a degradation identifier, the degradation identifier includes a system abnormal degradation identifier, and updating the local policy identifier according to the system policy identifier includes:
if the system strategy identification is the system abnormal degradation identification, updating the local strategy identification to be the system abnormal degradation identification;
the processing the received transaction request according to the transaction request processing policy corresponding to the updated local policy identifier includes:
and according to the system abnormal degradation identifier, releasing the received transaction request to a transaction processing system for transaction processing.
Optionally, the transaction request carries an organization identifier, and before the received transaction request is released to a transaction processing system for transaction processing according to the system abnormal degradation identifier, the method further includes:
determining whether the mechanism identification carried in the transaction request is in a blacklist list;
if so, directly rejecting the transaction request;
if not, the transaction request is passed to the transaction processing system.
Optionally, the system policy identifier includes a downgrade identifier, the downgrade identifier includes a service rejection downgrade identifier, and updating the local policy identifier according to the system policy identifier includes:
if the system strategy identification is the service degradation rejection identification, updating the local strategy identification to be the service degradation rejection identification;
the processing the received transaction request according to the transaction request processing policy corresponding to the updated local policy identifier includes:
and directly rejecting the transaction request according to the service rejection degradation identifier.
Optionally, the system policy identifier includes an un-downgraded identifier, and the updating the local policy identifier according to the system policy identifier includes:
if the system policy identifier is the non-degradation identifier, updating the local policy identifier to the non-degradation identifier;
the processing the received transaction request according to the transaction request processing policy corresponding to the updated local policy identifier comprises:
and forwarding the received transaction request to a transaction verification system for verification according to the non-degradation identifier.
Optionally, the determining, according to the transaction request processing result, that the information is reported includes:
receiving a transaction verification result returned by the transaction verification system, wherein the types of the transaction verification result comprise transaction verification passing, transaction verification system abnormity and service rejection;
counting system abnormal times and service refusal times according to the transaction verification result, and counting interface access times according to the received transaction request;
and taking at least one of the system abnormal times, the service refusing times and the interface access times as the reported information.
Optionally, the method further comprises:
and if the system policy identifier cannot be acquired, determining the local policy identifier directly according to the reported information.
Optionally, the reporting information includes system abnormal times, service refusal times and interface access times, and if the system policy identifier cannot be obtained, determining the local policy identifier directly according to the reporting information includes:
calculating a first failure rate of the transaction request according to the system abnormal times and the interface access times;
and if the system abnormal times trigger a system abnormal times threshold value and the first failure rate triggers a first failure rate threshold value, updating the local strategy identifier as the system abnormal degradation identifier.
Optionally, if the system policy identifier cannot be obtained, directly determining, according to the report information, that the local policy identifier includes:
calculating a second failure rate of the transaction request according to the service rejection times and the interface access times;
and if the service rejection times trigger a service rejection times threshold and the second failure rate triggers a second failure rate threshold, updating the local policy identifier as the service rejection degradation identifier.
In a second aspect, an embodiment of the present application provides a transaction request processing apparatus, which is applied to each transaction forwarding server in a transaction forwarding system, wherein the apparatus is configured to implement any one of the foregoing methods.
In a third aspect, an embodiment of the present application provides a transaction forwarding system, including a plurality of transaction forwarding servers, where the transaction forwarding servers include:
a processor; and
a memory arranged to store computer executable instructions that, when executed, cause the processor to perform any of the methods described above.
In a fourth aspect, an embodiment of the present application provides a transaction system, including: a transaction switching system, a transaction verification system and a transaction processing system,
the transaction transfer system comprises a plurality of transaction transfer servers, and each transaction transfer server comprises the device.
In a fifth aspect, embodiments of the present application provide a computer-readable storage medium storing one or more programs which, when executed by a transaction forwarding server comprising a plurality of application programs, cause the transaction forwarding server to perform any of the methods described above.
The embodiment of the application adopts at least one technical scheme which can achieve the following beneficial effects: the transaction request processing method is applied to each transaction transfer server in a transaction transfer system, and when the transaction request is processed, a system policy identifier is obtained first, wherein the system policy identifier is a policy identifier which takes effect in the transaction transfer system; then updating local strategy identification according to the system strategy identification, wherein the local strategy identification is the strategy identification which takes effect on each transaction transfer server; then, processing the received transaction request according to the updated local policy identifier; and finally, determining the reported information according to the transaction request processing result. According to the method and the system, the uniform system strategy identification is set for the whole transaction transfer system, so that each transaction transfer server in the transaction transfer system can acquire the same local strategy identification, and compared with the existing local automatic degradation mechanism, the system degradation mechanism can reduce the transaction loss rate to a certain extent, ensure the consistency of processing the same transaction request, and avoid the problems that the transaction request cannot be processed in idempotent and the like.
Drawings
The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the application and together with the description serve to explain the application and not to limit the application. In the drawings:
fig. 1 is a schematic structural diagram of a transaction system according to an embodiment of the present application;
FIG. 2 is a logical block diagram of a local auto-downgrade mechanism in the prior art;
FIG. 3 is a flow chart illustrating a method for processing a transaction request according to an embodiment of the present disclosure;
FIG. 4 is a schematic diagram of a transaction forwarding system according to an embodiment of the present application;
FIG. 5 is a logic block diagram of processing a transaction request according to an embodiment of the present application;
FIG. 6 is a schematic structural diagram of a transaction request processing device according to an embodiment of the present application;
fig. 7 is a schematic structural diagram of another transaction forwarding system according to an embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the technical solutions of the present application will be described in detail and completely with reference to the following specific embodiments of the present application and the accompanying drawings. It should be apparent that the described embodiments are only some 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.
The technical solutions provided by the embodiments of the present application are described in detail below with reference to the accompanying drawings.
As shown in fig. 1, a schematic structural diagram of a transaction system according to an embodiment of the present application is provided, which mainly relates to the following three subsystems: the system comprises a transaction switching system, a transaction verification system and a transaction processing system, wherein the transaction switching system is mainly used for receiving a transaction request sent by a user side and forwarding the transaction request to the transaction verification system for verification; the transaction verification system is mainly used for verifying the legality, the service type, the service logic and the like of the content of the transaction request, for example, whether the sum of the transaction request exceeds the maximum limit, whether the service type of the transaction request meets the requirements and the like; the transaction processing system is mainly used for carrying out specific business processing on the request verified by the transaction verification system. In the embodiment of the present application, the transaction forwarding system and the transaction verification system are mainly referred to.
In an actual business scenario, when the transaction forwarding system calls the transaction verification system, if a plurality of transaction requests are overtime or rejected, the transaction forwarding system may cause the transaction to be lost. In order to reduce the transaction loss rate, a local automatic degradation mechanism is introduced to process the transaction request.
As shown in fig. 2, a logic block diagram of a local automatic degradation mechanism is provided, which first determines a degradation identifier of a local transaction forwarding server, if the degradation identifier is a degradation identifier, compares an organization identifier carried in a transaction request with a blacklist, if the degradation identifier is not in the blacklist, directly releases the transaction request, and if the degradation identifier is in the blacklist, directly rejects the transaction request. If the transaction request is the non-degradation identifier, the transaction request is sent to the transaction verification system, then the response of the transaction verification system is synchronously waited, if the transaction verification system is abnormal or the transaction is rejected, the total times of the abnormality of the transaction verification system or the rejection of the transaction can be counted, when the total times reaches a time threshold value, the automatic degradation of the local transaction forwarding server is automatically triggered, and finally the degradation identifier of the local transaction forwarding server is updated. For the abnormal condition of the transaction verification system, a bottom-in-pocket strategy can be further adopted for judgment, the bottom-in-pocket strategy can be understood as a processing rule which is agreed in advance according to mechanisms, transaction types and the like, and for the transaction request under the abnormal condition of the transaction verification system, whether the transaction request is released or rejected can be determined through the bottom-in-pocket strategy.
However, the above scheme may have the following problems:
1) the existing automatic degradation is in the range of a single transaction transfer server (generally, hundreds of servers are arranged in a machine room where a transaction transfer system is located), and the situation that the transaction transfer system continuously loses transactions within a period of time is easy to occur, so that the transaction loss rate is high, because the lost transactions can be distributed on each transaction transfer server and the automatic degradation of the single transaction transfer server is not triggered;
2) the automatic degradation mechanism is locally effective in each transaction transfer server, which may cause inconsistent degradation states of transaction transfer applications on different servers in the same machine room, so that transaction requests cannot be processed in an idempotent manner, and meanwhile, difficulty is caused to operation and maintenance;
3) the current transaction request processing method simultaneously counts service refusal (namely the condition that the transaction verification system definitely responds to refusal) and transaction verification system abnormity (such as communication abnormity and the like), and with the gradual improvement and stabilization of the transaction verification system, the transaction request is released possibly because of automatic degradation caused by normal service refusal, and further some really risky transactions are possibly missed.
Based on this, the embodiment of the present application provides a transaction request processing method, which is executed by a transaction forwarding server in a transaction forwarding system, where as shown in fig. 3, the method includes steps S310 to S340 as follows:
step S310, a system policy identifier is obtained, wherein the system policy identifier is a policy identifier effective in the transaction forwarding system.
As shown in fig. 4, the transaction forwarding system of the embodiment of the present application includes a plurality of transaction forwarding servers, and each transaction forwarding server may be configured to execute the transaction request processing method of the embodiment of the present application. These transaction diversion servers may be deployed in the same room, taking into account the access overhead incurred in processing transaction requests across rooms.
For any one of the above transaction forwarding servers, after receiving the transaction request, the system policy identifier of the transaction forwarding system in which the transaction forwarding server is located may be obtained first, where the system policy identifier may be understood as a processing policy identifier that is adopted by the whole transaction forwarding system for the received transaction request, that is, an object to which the system policy identifier is directed is all transaction forwarding servers in one machine room, that is, a dimension of the whole machine room.
Step S320, updating a local policy identifier according to the system policy identifier, where the local policy identifier is a policy identifier effective in each transaction forwarding server.
Each transaction transfer server corresponds to its own local policy identifier, where the local policy identifier may be understood as a processing policy identifier that any transaction transfer server adopts for a transaction request received by the transaction transfer server, that is, an object to which the local policy identifier is oriented is a certain transaction transfer server, that is, a single machine dimension.
In an actual service scenario, due to network delay or failure, a situation that a user side initiates multiple transaction requests for the same transaction may occur, and the transaction requests initiated each time may reach different transaction forwarding servers, and if local policy identifiers of the transaction forwarding servers are not consistent, different processing results may occur for the same transaction request. Therefore, in order to avoid the above problems, for any one of the transaction transit servers, after the system policy identifier of the transaction transit system is obtained, the local policy identifier needs to be updated according to the system policy identifier, so that the local policy identifiers of all the transaction transit servers in one machine room can be kept consistent, and thereby the idempotent processing of the same transaction request is ensured.
And step S330, processing the received transaction request according to the updated local policy identifier.
Each transaction transfer server can perform various processing on the received transaction request, for example, the transaction request is forwarded to a transaction verification system for verification, or the transaction request is directly sent to the transaction processing system for specific service processing, or the transaction request is directly rejected, which processing mode is specifically adopted can be determined according to the updated local policy identifier.
Step S340, determining the reported information according to the transaction request processing result.
The system policy identifier of the embodiment of the application can be updated according to the processing result of the transaction request by each transaction transfer server, so as to meet the processing requirements for the transaction request under different service scenes. The transaction request processing result herein may include a result of transaction request passing, a result of transaction request rejection, or an ambiguous processing result. In an actual business scenario, the current transaction loss rate of the transaction forwarding system is high due to reasons such as abnormality of the transaction forwarding system, so that the reported information of the transaction request processing result can be reported, and whether the system policy identifier of the transaction forwarding system needs to be updated or not is determined according to the reported information, so that the processing policy of the transaction request is adjusted, and the transaction loss rate is reduced.
According to the method and the system, the uniform system strategy identification is set for the whole transaction transfer system, so that each transaction transfer server in the transaction transfer system can acquire the same local strategy identification, and compared with the existing local automatic degradation mechanism, the system degradation mechanism ensures the consistency of processing the same transaction request, and avoids the problems that the transaction request cannot be processed in an idempotent way and the like.
In an actual service scenario, the system policy identifier of the transaction forwarding system may be obtained by executing an asynchronous task, for example, executing the asynchronous task once per second, so as to ensure that other processes are not affected.
In an embodiment of the present application, the transaction forwarding system further includes a preset Redis database, where the system policy identifier is stored in the Redis database, and the obtaining the system policy identifier includes: determining a Redis state identifier of the Redis database; and under the condition that the Redis state identifier indicates that the Redis database is normal, requesting the Redis database to acquire the system policy identifier.
As shown in fig. 4, the transaction forwarding system of the embodiment of the present application further includes a preset Redis database (a key value database), where the Redis database may be connected to each transaction forwarding server in the transaction forwarding system, and is mainly used to receive and process information reported by each transaction forwarding server, and individually manage and update a system policy identifier of the transaction forwarding system.
In an actual service scenario, a Redis database cannot be used temporarily due to database failure or other reasons, and therefore, when a system policy identifier stored in the Redis database is acquired, a Redis state identifier of the Redis database may be determined first, where the Redis state identifier is mainly used to represent a current state of the Redis database, such as a normal state or a failure state. And then determining the current state of the Redis database according to the Redis state identification of the Redis database, and if the Redis database is currently in a normal state, sending a request to the Redis database to acquire the system policy identification.
In one embodiment of the present application, the method further comprises: determining the number of times of request failure according to the result of the request to the Redis database; and if the number of times of the request failure reaches a first threshold value within preset time, updating the Redis state identifier into a Redis fault identifier, wherein the Redis fault identifier is used for indicating the Redis database fault.
The result of the request to the Redis database may include a result that the request is successful, that is, the system policy identifier of the transaction forwarding system is successfully acquired, or may include a result that the request is failed, that is, the system policy identifier of the transaction forwarding system is not acquired. The reason for the request failure may be caused by a failure of the transaction transfer server or the Redis database itself, or may be caused by an abnormal network connection, so to determine whether the result of the request failure is related to the failure of the Redis database itself, so as to reduce the possibility of misjudgment, the number of times of the request failure in a period of time may be counted, and if the number of times of the request failure to the Redis database in the period of time reaches the first threshold, it indicates that the request failure is likely to be caused by the failure of the Redis database itself, so at this time, the Redis status identifier may be updated to be a Redis failure identifier, indicating that the Redis database fails.
In one embodiment of the present application, the method further comprises: reporting the reporting information to the Redis database so that the Redis database can update the system policy identifier according to the reporting information; determining the number of times of reporting failure according to the reporting result; and if the reporting failure times reach a second threshold value, updating the Redis state identifier into a Redis fault identifier.
As described above, the Redis database is mainly used for individually managing and updating the system policy identifier, so that after the report information is obtained according to the transaction request processing result, the report information can be reported to the Redis database, and then the Redis database further analyzes whether the system policy identifier needs to be updated.
However, since the reporting process also involves data transmission between the transaction forwarding server and the Redis database, a reporting failure may occur, that is, the reporting information is not successfully written into the Redis database. Similarly, the reason for the reporting failure may also be caused by a failure of the transaction transit server, a failure of the Redis database, or an abnormal network connection, and therefore, in order to determine whether the result of the reporting failure is related to the failure of the Redis database itself to reduce the possibility of erroneous determination, the number of times of the reporting failure may be counted, and if the number of times of the reporting failure reaches the second threshold, it indicates that the reporting failure is likely to be caused by the failure of the Redis database itself, so the Redis status identifier may also be updated to be the Redis fault identifier.
It should be noted that, the size of the "first threshold" and the size of the "second threshold" in the foregoing embodiment may be flexibly set according to an actual service requirement, and certainly, only one threshold may be set, so as to uniformly determine the sum of the number of times of request failure and the number of times of report failure.
In an embodiment of the present application, the system policy identifier includes a degradation identifier, the degradation identifier includes a system abnormal degradation identifier, and updating the local policy identifier according to the system policy identifier includes: if the system strategy identification is the system abnormal degradation identification, updating the local strategy identification to be the system abnormal degradation identification; the processing the received transaction request according to the transaction request processing policy corresponding to the updated local policy identifier includes: and according to the system abnormal degradation identifier, the received transaction request is released to a transaction processing system for transaction processing.
Normally, the transaction switching system receives the transaction request and forwards the transaction request to the transaction verification system for verification of transaction validity, business logic and the like, but due to the occurrence of some abnormal conditions, the transaction request cannot be responded in time or is rejected for many times, further, the transaction is lost, which results in a high transaction loss rate of the whole transaction forwarding system, therefore, in order to reduce the transaction loss rate, the transaction forwarding application can be handled in a downgrading mode, a specific downgrading object is the transaction forwarding application deployed on each transaction forwarding server, whether the transaction forwarding application is downgraded or not can be determined through a corresponding downgrading identifier or not, and the downgrading identifier is further subdivided into a system abnormal downgrading identifier obtained due to the fact that a transaction verification system is abnormal and a service rejection downgrading identifier obtained due to the fact that a transaction request is rejected.
Of course, it should be noted that the above-mentioned process of degrading the transaction transfer application is only temporary, and in order to ensure the security of the transaction, after the degradation is triggered, the operation and maintenance personnel may be notified to perform troubleshooting in time to recover the normal transaction verification process.
The transaction transit system comprises a transaction transit server, a transaction processing system and a local policy identifier, wherein the transaction transit server is connected with the transaction processing system, the transaction processing system is connected with the local policy identifier, the local policy identifier is used for updating the local policy identifier to be the system abnormal degradation identifier, the local policy identifier is used for updating the system abnormal degradation identifier, and the local policy identifier is used for updating the system abnormal degradation identifier.
In an embodiment of the present application, the transaction request carries an organization identifier, and before the received transaction request is passed to a transaction processing system for transaction processing according to the system abnormal degradation identifier, the method further includes: determining whether the mechanism identification carried in the transaction request is in a blacklist list; if yes, directly rejecting the transaction request; if not, the transaction request is passed to the transaction processing system.
As previously mentioned, in general, if the local policy identification has been updated to the system abnormal downgrade identification, the processing strategy of passing directly to the transaction processing system is adopted for the subsequently received transaction request, but in consideration of the security of the transaction, the occurrence of significant transaction loss is avoided, before subsequently received transaction requests are released to the transaction processing system for transaction processing, the validity of the transaction requests and the like can be verified by utilizing a blacklist, wherein a list of institutions which are not allowed to perform transactions is usually stored in the blacklist, if the institution identification carried in the received transaction request is in the blacklist, the transaction request is directly rejected and can be processed by manual intervention subsequently, if not, the transaction request can be released to the transaction processing system for specific business processing.
In an embodiment of the present application, the system policy identifier includes a downgrade identifier, the downgrade identifier includes a service rejection downgrade identifier, and updating the local policy identifier according to the system policy identifier includes: if the system strategy identification is the service degradation rejection identification, updating the local strategy identification to be the service degradation rejection identification; the processing the received transaction request according to the transaction request processing policy corresponding to the updated local policy identifier includes: and directly rejecting the transaction request according to the service rejection degradation identifier.
If the system policy identifier of the transaction transit system obtained in the embodiment of the application is the service degradation rejection identifier, it indicates that the transaction verification system has clearly rejected the transaction request for many times, and in order to avoid that the subsequent transaction verification system receives the same transaction request again, the local policy identifier can be updated to the service degradation rejection identifier, and the local policy identifiers of all the transaction transit servers in the transaction transit system are synchronously updated to the service degradation rejection identifier, so that each transaction transit server adopts a directly rejected processing policy for the subsequently received transaction request, and the consistency of the processing results of the same transaction request is further ensured.
In an embodiment of the present application, the system policy identifier includes an un-downgraded identifier, and the updating the local policy identifier according to the system policy identifier includes: if the system policy identifier is the non-degradation identifier, updating the local policy identifier to the non-degradation identifier; the processing the received transaction request according to the transaction request processing policy corresponding to the updated local policy identifier includes: and forwarding the received transaction request to a transaction verification system for verification according to the non-degradation identifier.
And if the acquired system strategy identifier of the transaction transfer system is the non-degraded identifier, updating the local strategy identifier to be the non-degraded identifier, and normally forwarding the subsequently received transaction request to a transaction verification system for verification.
In an embodiment of the present application, the determining to report information according to the transaction request processing result includes: receiving a transaction verification result returned by the transaction verification system, wherein the types of the transaction verification result comprise transaction verification passing, transaction verification system abnormity and service rejection; counting system abnormal times and service refusing times according to the transaction verification result, and counting interface access times according to the received transaction request; and taking at least one of the system abnormal times, the service refusing times and the interface access times as the reported information.
The verification result returned by the transaction verification system can comprise three conditions of transaction verification passing, transaction verification system abnormity and service rejection. The transaction verification can carry out subsequent service processing by showing that the transaction request meets the requirements of legality, service logic and the like; the abnormity of the transaction verification system indicates that the transaction verification system has a fault, so that the transaction request cannot be responded in time. The service rejection shows that after the transaction verification system verifies the legality, the service logic and the like of the transaction request, if the transaction request is considered to be not in accordance with the requirements of the legality, the service logic and the like, the transaction request is directly rejected, and subsequent service processing can not be performed temporarily.
When the transaction verification system is abnormal or the transaction is rejected, the transaction is not successful, namely, the transaction loss occurs, so that in order to reduce the transaction loss rate and improve the transaction volume of the transaction, the system abnormal times and the service rejection times can be counted according to the verification result returned by the transaction verification system and according to a certain time, such as every minute, meanwhile, the interface access times are counted according to the received transaction request, and then the three indexes of the system abnormal times, the service rejection times and the interface access times are reported to a Redis database in the transaction verification system as report information, so that the Redis database determines whether to adjust the system strategy identification after analyzing and processing the report information to reduce the transaction loss rate.
If the update of the system policy identifier by the Redis database fails, the update compensation needs to be successful as much as possible, for example, a retry mechanism may be invoked, and the retry is performed twice after the first update failure, so that the update compensation is successful as much as possible. If the retry mechanism is not successful, an alarm is triggered and processed by human intervention.
In one embodiment of the present application, the method further comprises: and if the system policy identifier cannot be acquired, determining the local policy identifier directly according to the reported information.
As in the foregoing embodiment, the system policy identifier may be stored in a Redis database for management, and if the Redis database fails, the system policy identifier cannot be acquired from the Redis database, at this time, a local automatic downgrading mechanism may be invoked to process the transaction request, where the local automatic downgrading mechanism is for a single transaction transit server, and although the local automatic downgrading mechanism may have the problems that the transaction request cannot be processed in an idempotent manner due to inconsistent downgrading identifiers of different transaction transit servers, and the like, here, in consideration of reducing a transaction loss rate, the local automatic downgrading mechanism may be adopted under an abnormal condition such as a Redis database failure, and a strong dependence on the system downgrading mechanism is avoided.
The local automatic demotion mechanism is lower in priority than the system demotion mechanism by default, namely the system demotion mechanism is called preferentially, and the local automatic demotion mechanism is called only when the system demotion mechanism is abnormal, such as a Redis database fails.
In an embodiment of the present application, the reporting information includes system abnormal times, service denial times, and interface access times, and if the system policy identifier cannot be obtained, determining the local policy identifier directly according to the reporting information includes: calculating a first failure rate of the transaction request according to the system abnormal times and the interface access times; and if the system abnormal times trigger a system abnormal times threshold value and the first failure rate triggers a first failure rate threshold value, updating the local strategy identifier as the system abnormal degradation identifier.
Specifically, if a case of transaction verification system abnormality occurs, which indicates that the transaction has failed, it may be determined whether to update the local policy identifier as the system abnormality degradation identifier according to the system abnormality number and a ratio of the system abnormality number to the interface access number, that is, a first failure rate.
The reason why the local policy identifier is determined comprehensively by using the two indexes of the system abnormal times and the first failure rate is mainly due to the following two considerations: 1) because the system abnormal times are only statistics of a certain time period such as every minute, if the judgment is carried out only through the system abnormal times, if only one or a few transaction requests fail to transact due to the abnormality of the transaction verification system every minute, but the system abnormal times threshold is not triggered, the continuous transaction loss can be caused; 2) when the number of transaction requests in one minute is small, as long as one or a few transaction requests fail to transact due to the abnormality of the transaction verification system, a high first failure rate may be caused, and therefore, if the determination is made only by the first failure rate, a situation in which the local automatic degradation mechanism is frequently triggered may occur.
Therefore, in order to avoid the above problem, when the local policy identifier is updated under the condition that the transaction verification system is abnormal, the local policy identifier can be determined comprehensively by using two indexes, namely the system abnormal frequency and the first failure rate. Specifically, if the system anomaly number triggers a system anomaly number threshold and the first failure rate also triggers the first failure rate threshold, the local policy identification is updated to the system anomaly degradation identification.
In an embodiment of the present application, if the system policy identifier cannot be obtained, directly determining the local policy identifier according to the report information includes: calculating a second failure rate of the transaction request according to the service rejection times and the interface access times; and if the service rejection times trigger a service rejection times threshold and the second failure rate triggers a second failure rate threshold, updating the local policy identifier as the service rejection degradation identifier.
Specifically, if a service rejection occurs, the transaction is also described as failed, in order to avoid the above-mentioned situation of continuous transaction loss or frequent triggering of the local automatic degradation mechanism, when the local policy identifier is updated under the condition of service rejection, it may be determined whether to update the local policy identifier as the service rejection degradation identifier according to the number of service rejections and the ratio of the number of service rejections to the number of interface accesses, that is, the second failure rate. If the service rejection number triggers a service rejection number threshold and the second failure rate also triggers a second failure rate threshold, the local policy identity may be updated to a service rejection downgrade identity.
The existing local automatic degradation scheme does not distinguish two conditions of transaction verification system abnormity and service rejection, but determines whether to call a local automatic degradation mechanism according to whether the sum of the system abnormity frequency and the service rejection frequency triggers a threshold value. The problem exists in that the system abnormal times and the service rejection times can affect each other during statistics, and if the sum of the two triggers a threshold value due to the higher service rejection times, the problem of releasing the transaction request which should be rejected occurs, so that the real transaction risk is omitted. In the embodiment, the local automatic degradation mechanism distinguishes two conditions of abnormal transaction verification system and service rejection, and sets corresponding threshold values for judgment respectively, so that real transaction risk can be avoided being overlooked.
As shown in FIG. 5, a block diagram of processing logic for a transaction request is provided. For any transaction transfer server, starting an asynchronous task, acquiring a Redis state identifier of a Redis database, and requesting the Redis database to acquire a system policy identifier if the Redis state identifier is in a normal state; if the system strategy identification can be normally obtained, updating the local strategy identification according to the obtained system strategy identification; processing the received transaction request according to a transaction request processing strategy corresponding to the updated local strategy identifier, wherein if the system strategy identifier is a degradation identifier, the asynchronous task is directly ended, if the system strategy identifier is a non-degradation identifier, the system abnormal times, the service refusal times and the interface access times are obtained, reporting information such as the system abnormal times, the service refusal times and the interface access times is reported to a Redis database, whether a threshold corresponding to a system degradation mechanism is triggered or not is calculated and analyzed by the Redis database, and if the threshold is triggered, the system strategy identifier is updated to be the degradation identifier.
In the process, if the system policy identifier cannot be acquired from the Redis database or the report information cannot be reported to the Redis database, the abnormal times of the Redis database are counted, and if the abnormal times trigger a corresponding abnormal time threshold, the Redis state identifier is updated to be a Redis fault identifier.
If the acquired Redis state identifier is a Redis fault identifier, a local automatic degradation mechanism can be called to process the transaction request, then system abnormal times, service rejection times and interface access times are directly acquired, whether a threshold corresponding to the local automatic degradation mechanism is triggered or not is determined according to the system abnormal times, the service rejection times and the interface access times, if the threshold is triggered, the local policy identifier is updated to be a degradation identifier, whether an mechanism identifier carried in the received transaction request is in a blacklist list or not is determined, and if the mechanism identifier carried in the received transaction request is in the blacklist list, the transaction request is directly rejected; if the threshold corresponding to the local automatic degradation mechanism is not triggered, the transaction verification system is called to verify the received transaction request to obtain the transaction verification passing, the service refusal or the ambiguous processing result, and the system abnormal times, the service refusal times and the interface access times are updated according to the transaction verification passing, the service refusal or the ambiguous processing result.
The embodiment of the present application further provides a transaction request processing apparatus 600, which is applied to each transaction forwarding server in a transaction forwarding system, where as shown in fig. 6, the apparatus 600 includes:
an obtaining unit 610, configured to obtain a system policy identifier, where the system policy identifier is a policy identifier that takes effect in the transaction forwarding system;
a first updating unit 620, configured to update a local policy identifier according to the system policy identifier, where the local policy identifier is a policy identifier that takes effect in each transaction forwarding server;
a transaction request processing unit 630, configured to process the received transaction request according to the updated local policy identifier;
the first determining unit 640 is configured to determine reporting information according to a transaction request processing result.
In an embodiment of the present application, the transaction forwarding system further includes a preset Redis database, where the system policy identifier is stored in the Redis database, and the obtaining unit 610 is specifically configured to: determining a Redis state identifier of the Redis database; and under the condition that the Redis state identifier indicates that the Redis database is normal, requesting the Redis database to acquire the system policy identifier.
In one embodiment of the present application, the apparatus further comprises: a second determining unit, configured to determine, according to a result of the request to the Redis database, a number of times of request failure; and the second updating unit is used for updating the Redis state identifier into a Redis fault identifier if the number of times of the request failure reaches a first threshold value within preset time, wherein the Redis fault identifier is used for indicating the Redis database fault.
In one embodiment of the present application, the apparatus further comprises: a reporting unit, configured to report the reporting information to the Redis database, so that the Redis database can update the system policy identifier according to the reporting information; a third determining unit, configured to determine, according to the reporting result, the number of times of reporting failure; and a third updating unit, configured to update the Redis state identifier to a Redis fault identifier if the number of reporting failures reaches a second threshold.
In an embodiment of the application, the system policy identifier includes a degradation identifier, the degradation identifier includes a system abnormal degradation identifier, and the first updating unit 620 is specifically configured to: if the system strategy identification is the system abnormal degradation identification, updating the local strategy identification to be the system abnormal degradation identification; the transaction request processing unit 630 is specifically configured to: and according to the system abnormal degradation identifier, releasing the received transaction request to a transaction processing system for transaction processing.
In an embodiment of the present application, the transaction request carries an organization identifier, and before passing the received transaction request to a transaction processing system for transaction processing according to the system abnormal degradation identifier, the apparatus further includes: a fourth determining unit, configured to determine whether the mechanism identifier carried in the transaction request is in a blacklist; the rejection unit is used for directly rejecting the transaction request if the transaction request is received; and the releasing unit is used for releasing the transaction request to the transaction processing system if the transaction request is not in the transaction processing system.
In an embodiment of the present application, the system policy identifier includes a degradation identifier, the degradation identifier includes a service rejection degradation identifier, and the first updating unit 620 is specifically configured to: if the system strategy identification is the service degradation rejection identification, updating the local strategy identification to be the service degradation rejection identification; the transaction request processing unit 630 is specifically configured to: and directly rejecting the transaction request according to the service rejection degradation identifier.
In an embodiment of the present application, the system policy identifier includes an un-downgrading identifier, and the first updating unit 620 is specifically configured to: if the system policy identifier is the non-degradation identifier, updating the local policy identifier to the non-degradation identifier; the transaction request processing unit 630 is specifically configured to: and forwarding the received transaction request to a transaction verification system for verification according to the non-degradation identifier.
In an embodiment of the present application, the first determining unit 630 is specifically configured to: receiving a transaction verification result returned by the transaction verification system, wherein the types of the transaction verification result comprise transaction verification passing, transaction verification system abnormity and service rejection; counting system abnormal times and service refusing times according to the transaction verification result, and counting interface access times according to the received transaction request; and taking at least one of the system abnormal times, the service refusing times and the interface access times as the reported information.
In one embodiment of the present application, the apparatus further comprises: and a fifth determining unit, configured to determine the local policy identifier directly according to the report information if the system policy identifier cannot be obtained.
In an embodiment of the present application, the report information includes system exception times, service rejection times, and interface access times, and the fifth determining unit is specifically configured to: calculating a first failure rate of the transaction request according to the system abnormal times and the interface access times; and if the system abnormal times trigger a system abnormal times threshold value and the first failure rate triggers a first failure rate threshold value, updating the local strategy identifier as the system abnormal degradation identifier.
In an embodiment of the application, the fifth determining unit is specifically configured to: calculating a second failure rate of the transaction request according to the service rejection times and the interface access times; and if the service rejection times trigger a service rejection times threshold and the second failure rate triggers a second failure rate threshold, updating the local strategy identifier as the service rejection degradation identifier.
It can be understood that the processing device for the transaction request can implement the steps of the processing method for the transaction request executed by the transaction forwarding server provided in the foregoing embodiment, and the related explanations regarding the processing method for the transaction request are applicable to the processing device for the transaction request, and are not described herein again.
Fig. 7 is a schematic diagram of a transaction forwarding system according to another embodiment of the present application. Referring to fig. 7, the transaction forwarding system includes a plurality of transaction forwarding servers, and each transaction forwarding server includes a processor, and optionally an internal bus, a network interface, and a memory. The Memory may include a Memory, such as a Random-Access Memory (RAM), and may further include a non-volatile Memory, such as at least 1 disk Memory. Of course, the electronic device may also include hardware required for other services.
The processor, the network interface, and the memory may be connected to each other via an internal bus, which may be an ISA (Industry Standard Architecture) bus, a PCI (Peripheral Component Interconnect) bus, an EISA (Extended Industry Standard Architecture) bus, or the like. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one double-headed arrow is shown in FIG. 7, but this does not indicate only one bus or one type of bus.
And the memory is used for storing programs. In particular, the program may include program code comprising computer operating instructions. The memory may include both memory and non-volatile storage and provides instructions and data to the processor.
The processor reads the corresponding computer program from the nonvolatile memory into the memory and then runs the computer program to form the transaction reconciliation device on the logic level. The processor is used for executing the program stored in the memory and is specifically used for executing the following operations:
acquiring a system policy identifier, wherein the system policy identifier is a policy identifier effective to the transaction transfer system;
updating local policy identifications according to the system policy identifications, wherein the local policy identifications are the policy identifications which take effect on each transaction transfer server;
processing the received transaction request according to the updated local policy identifier;
and determining the reported information according to the transaction request processing result.
The method executed by the processing device of the transaction request disclosed in the embodiment of fig. 6 of the present application may be applied to or implemented by a processor. The processor may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method may be performed by integrated logic circuits of hardware in a processor or by instructions in the form of software. The Processor may be a general-purpose Processor, including a Central Processing Unit (CPU), a Network Processor (NP), and the like; but also Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) or other Programmable logic devices, discrete Gate or transistor logic devices, discrete hardware components. The various methods, steps, and logic blocks disclosed in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in a memory, and a processor reads information in the memory and completes the steps of the method in combination with hardware of the processor.
The transaction forwarding system may also execute the method executed by the transaction request processing device in fig. 6, and implement the functions of the transaction request processing device in the embodiment shown in fig. 6, which are not described herein again in this embodiment of the present application.
An embodiment of the present application further provides a computer-readable storage medium storing one or more programs, where the one or more programs include instructions, which when executed by a transaction forwarding server including a plurality of application programs, can cause the transaction forwarding server to perform the method performed by the processing device of the transaction request in the embodiment shown in fig. 6, and is specifically configured to perform:
acquiring a system policy identifier, wherein the system policy identifier is a policy identifier effective to the transaction transfer system;
updating local policy identifications according to the system policy identifications, wherein the local policy identifications are the policy identifications which take effect on each transaction transfer server;
processing the received transaction request according to the updated local policy identifier;
and determining the reported information according to the transaction request processing result.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention 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 the like) having computer-usable program code embodied therein.
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.
It should also be noted that 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, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application 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 the like) having computer-usable program code embodied therein.
The above description is only an example of the present application and is not intended to limit the present application. Various modifications and changes may occur to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.

Claims (16)

1. A processing method of transaction requests is applied to each transaction forwarding server in a transaction forwarding system, wherein the method comprises the following steps:
acquiring a system policy identifier, wherein the system policy identifier is a policy identifier effective to the transaction transfer system;
updating local policy identifications according to the system policy identifications, wherein the local policy identifications are the policy identifications which take effect on each transaction transfer server;
processing the received transaction request according to the updated local policy identifier;
and determining the reported information according to the transaction request processing result.
2. The method of claim 1, wherein the transaction transit system further comprises a preset Redis database, the system policy identifier is stored in the Redis database, and the obtaining the system policy identifier comprises:
determining a Redis state identifier of the Redis database;
and under the condition that the Redis state identifier indicates that the Redis database is normal, requesting the Redis database to acquire the system policy identifier.
3. The method of claim 2, wherein the method further comprises:
determining the number of times of request failure according to the result of the request to the Redis database;
and if the number of times of the request failure reaches a first threshold value within preset time, updating the Redis state identifier into a Redis fault identifier, wherein the Redis fault identifier is used for indicating the Redis database fault.
4. The method of claim 2, wherein the method further comprises:
reporting the reporting information to the Redis database so that the Redis database can update the system policy identifier according to the reporting information;
determining the number of times of reporting failure according to the reporting result;
and if the reporting failure times reach a second threshold value, updating the Redis state identifier into a Redis fault identifier.
5. The method of claim 1, wherein the system policy identification comprises a downgrade identification, the downgrade identification comprises a system abnormal downgrade identification, and updating the local policy identification in accordance with the system policy identification comprises:
if the system strategy identification is the system abnormal degradation identification, updating the local strategy identification to be the system abnormal degradation identification;
the processing the received transaction request according to the transaction request processing policy corresponding to the updated local policy identifier includes:
and according to the system abnormal degradation identifier, the received transaction request is released to a transaction processing system for transaction processing.
6. The method as claimed in claim 5, wherein the transaction request carries an institution identifier, and before passing the received transaction request to a transaction processing system for transaction processing according to the system abnormal degradation identifier, the method further comprises:
determining whether the mechanism identification carried in the transaction request is in a blacklist list;
if so, directly rejecting the transaction request;
if not, the transaction request is passed to the transaction processing system.
7. The method of claim 1, wherein the system policy identification comprises a downgrade identification, the downgrade identification comprises a traffic rejection downgrade identification, and updating the local policy identification according to the system policy identification comprises:
if the system strategy identification is the service degradation rejection identification, updating the local strategy identification to be the service degradation rejection identification;
the processing the received transaction request according to the transaction request processing policy corresponding to the updated local policy identifier includes:
and directly rejecting the transaction request according to the service rejection degradation identifier.
8. The method of claim 1, wherein the system policy identification comprises an undegraded identification, and wherein updating the local policy identification in accordance with the system policy identification comprises:
if the system policy identifier is the non-degradation identifier, updating the local policy identifier to the non-degradation identifier;
the processing the received transaction request according to the transaction request processing policy corresponding to the updated local policy identifier includes:
and forwarding the received transaction request to a transaction verification system for verification according to the non-degradation identifier.
9. The method of claim 8, wherein determining reporting information based on transaction request processing results comprises:
receiving a transaction verification result returned by the transaction verification system, wherein the types of the transaction verification result comprise transaction verification passing, transaction verification system abnormity and service rejection;
counting system abnormal times and service refusal times according to the transaction verification result, and counting interface access times according to the received transaction request;
and taking at least one of the system abnormal times, the service refusing times and the interface access times as the reported information.
10. The method of claim 1, wherein the method further comprises:
and if the system policy identifier cannot be acquired, determining the local policy identifier directly according to the reported information.
11. The method according to claim 10, wherein the reported information includes system abnormal times, service rejection times and interface access times, and if the system policy identifier cannot be obtained, determining the local policy identifier directly according to the reported information includes:
calculating a first failure rate of the transaction request according to the system abnormal times and the interface access times;
and if the system abnormal times trigger a system abnormal times threshold value and the first failure rate triggers a first failure rate threshold value, updating the local strategy identifier as the system abnormal degradation identifier.
12. The method of claim 11, wherein, if the system policy identifier cannot be obtained, determining the local policy identifier directly according to the reported information comprises:
calculating a second failure rate of the transaction request according to the service rejection times and the interface access times;
and if the service rejection times trigger a service rejection times threshold and the second failure rate triggers a second failure rate threshold, updating the local policy identifier as the service rejection degradation identifier.
13. A transaction request processing device applied to each transaction transfer server in a transaction transfer system, wherein the device is used for implementing the method of any one of claims 1 to 12.
14. A transaction diversion system comprising a plurality of transaction diversion servers, the transaction diversion servers comprising:
a processor; and
a memory arranged to store computer executable instructions which, when executed, cause the processor to perform the method of any of claims 1 to 12.
15. A transaction system, comprising: a transaction forwarding system, a transaction verification system and a transaction processing system, said transaction forwarding system comprising a plurality of transaction forwarding servers, each transaction forwarding server comprising the apparatus of claim 13.
16. A computer readable storage medium storing one or more programs which, when executed by a transaction forwarding server comprising a plurality of application programs, cause the transaction forwarding server to perform the method of any of claims 1 to 12.
CN202011528696.7A 2020-12-22 2020-12-22 Transaction request processing method and device and transaction transfer system Pending CN114663226A (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202011528696.7A CN114663226A (en) 2020-12-22 2020-12-22 Transaction request processing method and device and transaction transfer system
PCT/CN2021/136569 WO2022135158A1 (en) 2020-12-22 2021-12-08 Transaction request processing method and apparatus, and transaction transfer system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202011528696.7A CN114663226A (en) 2020-12-22 2020-12-22 Transaction request processing method and device and transaction transfer system

Publications (1)

Publication Number Publication Date
CN114663226A true CN114663226A (en) 2022-06-24

Family

ID=82025082

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202011528696.7A Pending CN114663226A (en) 2020-12-22 2020-12-22 Transaction request processing method and device and transaction transfer system

Country Status (2)

Country Link
CN (1) CN114663226A (en)
WO (1) WO2022135158A1 (en)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116957807B (en) * 2023-09-21 2023-12-08 成都天用唯勤科技股份有限公司 Transaction degradation method and system for high-concurrency multi-dimensional distributed transaction system
CN117172925B (en) * 2023-11-03 2024-02-20 建信金融科技有限责任公司 Transaction processing method, device, equipment and medium
CN117252676B (en) * 2023-11-20 2024-02-02 成都新希望金融信息有限公司 Service processing method, device, electronic equipment and index policy system

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102377603B (en) * 2011-10-26 2014-10-29 国家广播电影电视总局广播科学研究院 Policy processing method and policy processing devices
WO2016199052A1 (en) * 2015-06-11 2016-12-15 Kelkar Vibhav Madhusudan A system and method for enabling a transaction by extraction of transaction data
CN110069337B (en) * 2018-01-24 2024-07-16 北京京东尚科信息技术有限公司 Disaster recovery degradation method and device
CN109257294B (en) * 2018-09-07 2022-04-12 武汉斗鱼网络科技有限公司 Service dynamic degradation method, device, server and storage medium based on redis
CN111241112B (en) * 2019-12-27 2023-05-23 山大地纬软件股份有限公司 Micro-service call supervision system and method for ensuring idempotent

Also Published As

Publication number Publication date
WO2022135158A1 (en) 2022-06-30

Similar Documents

Publication Publication Date Title
CN114663226A (en) Transaction request processing method and device and transaction transfer system
CN110516928B (en) Decision method, device, equipment and computer readable medium for business private line
CN109377236A (en) A kind of risk control method, equipment and storage medium based on fusing mechanism
CN111090658B (en) Abnormal transaction processing method, system and equipment
CN112561506B (en) Live broadcast data processing method, system, equipment and medium based on virtual currency
CN114268957B (en) Abnormal business data processing method, device, server and storage medium
CN111581055A (en) Business system control method and device, electronic equipment and readable storage medium
CN106612263B (en) Method and equipment for processing application access request
CN111324477A (en) Processing method and device for distributed fusing
CN107239370B (en) Data writing method, transaction processing method and device
CN111680293A (en) Information monitoring management method and device based on Internet and server
WO2021083503A1 (en) Sim swap fraud detection
CN113905092B (en) Method, device, terminal and storage medium for determining reusable agent queue
CN115271694A (en) Order payment method and system
CN110490737B (en) Transaction channel control method and device and electronic equipment
CN116128505A (en) Method and device for consensus of block chain network and electronic equipment
CN114020559A (en) Application system management method and system based on micro service component
CN113485930A (en) Business process verification method, device, computer system and readable storage medium
CN113568781A (en) Database error processing method and device and database cluster access system
CN113285811A (en) Method and apparatus for verifying data transmission, system and computer readable storage medium
CN113811022A (en) Abnormal terminal rejection method, system, device and storage medium
CN111984484A (en) Non-invasive micro-service access method and system
CN111354174A (en) Alarm method, device, server and readable storage medium
CN116263696A (en) Machine room task notification processing method, device and task notification processing system
CN113835621B (en) IP arbitration process quantity management and control method, system, terminal and storage medium

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