Asynchronous notification routing method and system

By identifying and routing payment asynchronous notifications in the pre-application of the DMZ domain, the Nginx reverse proxy server is used to realize efficient sending of asynchronous notifications, which solves the problems of large workload and inefficiency in the development and operation and maintenance workload in the existing technology, and improves the payment asynchronous results The sending efficiency of notifications and the scalability of the system.

CN116137610BActive Publication Date: 2024-11-26中移信息技术有限公司 +1
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202111363677.8
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2021-11-17
Publication Date
2024-11-26
Estimated Expiration
2041-11-17

AI Technical Summary

Technical Problem

In an environment where public networks and dedicated networks are isolated, the prior art solutions are used to send payment asynchronous results notifications, which have defects in development and operation and maintenance workload, inefficient efficiency, and traffic collection judgment, which affects the normal process and scalability of notifications.

Method used

The pre-application deployed in the DMZ domain recognizes the callback address of the transaction request packet in the asynchronous notification, and sends the asynchronous notification to the corresponding merchant system based on the identification results, and uses the Nginx reverse proxy server to map the intranet address and Path recognition enables efficient routing of asynchronous notifications.

Benefits of technology

It improves the efficiency of sending asynchronous notifications, reduces the workload of development and operation and maintenance, simplifies configuration and maintenance, reduces the scope of failure impact, and supports uninterrupted changes and expansion of business.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN116137610B_ABST
    Figure CN116137610B_ABST
Patent Text Reader

Abstract

The present invention provides an asynchronous notification routing method and system, the method comprising: identifying the callback address of the transaction request message in the asynchronous notification according to the front-end application deployed in the DMZ domain; and sending the asynchronous notification to the corresponding merchant system according to the identification result. The system is used to execute the above method. The present invention uses the front-end application deployed in the DMZ domain to identify the callback address of the transaction request message (such as the payment request message) in the asynchronous notification (such as the asynchronous result notification sent by the payment collection system), and according to the identification result, the asynchronous notification is sent to the corresponding merchant system, thereby improving the efficiency of sending the asynchronous notification (for example, the payment collection system can be more efficient in sending the asynchronous result notification).
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to an asynchronous notification routing method and system. Background Art

[0002] With the development of online payment, more and more merchant systems are connected to the payment network. Due to the large number of third-party payment institutions, the interfaces are different. If each merchant system is directly connected to the payment institution, it will take a lot of manpower and time. The payment aggregation system has interfaces to access almost all payment institutions, and can provide unified payment interface services to more merchant systems, greatly reducing the cost of merchant systems accessing the payment network.

[0003] Most payment transactions are for ordinary mass users, so the entry point for transaction initiation is in the public network. The entire process of payment transactions involves the portal system, merchant system, payment collection system, and third-party payment institution. The payment collection system receives payment requests redirected from the merchant system or user, and then sends them to the third-party payment institution. After successful processing, the third-party payment institution will send an asynchronous result notification to the payment collection system. The payment collection system stores the payment, changes the transaction status, and then sends the asynchronous result notification to the merchant system. The merchant system settles on a daily or monthly basis according to the payment result. In order to accurately send the asynchronous result notification to the merchant system that initiated the transaction among many merchant systems, the payment request message sent by each merchant system to the payment collection system carries the callback address feedbackUrl of the asynchronous result notification, indicating the receiving path sent by the payment collection system to the merchant system after receiving the asynchronous result notification from the payment institution.

[0004] In large-scale group companies, almost every merchant system and the payment collection system also have a dedicated network. In order to reduce the exposure to the public network and strengthen the security of the transmission process, some merchant systems and the payment collection system use internal dedicated lines for payment requests and asynchronous result notifications. Some merchant system payment requests use the public network, but the asynchronous result notifications from the payment collection system to the merchant system use the internal dedicated line. This results in the situation where most of the asynchronous result notification requests sent by the payment collection system to external merchants use the public network, and a small part uses the dedicated line. There are various risks of being attacked on the public network. For security reasons, most of the current Internet data centers (IDCs) have strict network division and isolation. Machines in the DMZ (Demilitarized Zone) domain can access the public network, but cannot directly access the dedicated line. Machines in the dedicated line domain can access the dedicated line, but cannot directly access the public network. That is, there is no situation where a machine can directly access the dedicated line and the public network at the same time. As a result, the payment aggregation system front-end application deployed in the DMZ domain to send asynchronous result notifications to the merchant system can directly access the merchant system on the public network, but cannot directly access the merchant system on the internal dedicated line, and the system cannot operate normally.

[0005] In this case, in order to ensure that all asynchronous result notification processes from the payment aggregation system to the merchant system proceed normally, there are the following common methods: (1) Application transformation. When processing the core domain of the previous step of sending the asynchronous result notification, add a check on whether each callback address is a dedicated line address. If it is a dedicated line address, it is sent to the application deployed in the dedicated line interface domain, and the dedicated line domain application sends the asynchronous result notification to the merchant system. Otherwise, it is sent to the DMZ domain application, and the DMZ domain application sends the asynchronous result notification to the merchant system on the public network. (2) Application system split deployment. The payment aggregation system is split into two independent subsystems with the same functions: the public network domain subsystem and the dedicated line domain subsystem. They process requests with callback addresses of the public network and dedicated line respectively. An Nginx cluster is added to the request entry to parse the message to complete the diversion. If the feedbackUrl is a dedicated line address, it is sent to the dedicated line domain subsystem for processing. Otherwise, it is sent to the DMZ domain subsystem for processing. (3) Two-level proxy solution (such as Figure 1 As shown in the figure), use Squid two-level proxy to collect system asynchronous results and notify the application cluster in the DMZ domain, and deploy a forward proxy in the DMZ domain and the dedicated line domain respectively. The proxy in the DMZ domain is a child proxy, and its proxy rule is that if the destination address is a bearer network address, it is forwarded to the parent proxy in the dedicated line domain, otherwise the child proxy directly accesses the public network address; the parent proxy in the dedicated line domain is simple to configure and can directly access the dedicated line address.

[0006] In an environment where the public network and the dedicated network are securely isolated, existing solutions for sending payment asynchronous result notifications to merchant systems on the public network and the dedicated network, such as application transformation, application system split deployment, and two-level proxy solutions, all have defects such as large development and operation workload, low efficiency in sending payment asynchronous result notifications, and traffic aggregation to determine whether the destination address is the public network or the dedicated network before forwarding. If an abnormality occurs at the traffic aggregation point, it will affect both the asynchronous result notifications sent to the dedicated network and the asynchronous result notifications sent to the public network, and the change and scalability are poor. Summary of the invention

[0007] The asynchronous notification routing method and system provided by the present invention are used to solve at least one of the above-mentioned problems existing in the prior art. The front-end application deployed in the DMZ domain is used to identify the callback address of the transaction request message (such as the payment request message) in the asynchronous notification (such as the asynchronous result notification sent by the payment aggregation system). According to the identification result, the asynchronous notification is sent to the corresponding merchant system, thereby improving the efficiency of sending the asynchronous notification (for example, the payment aggregation system can be made more efficient in sending the asynchronous result notification).

[0008] The present invention provides an asynchronous notification routing method, comprising:

[0009] According to the front-end application deployed in the DMZ domain, the callback address of the transaction request message in the asynchronous notification is identified;

[0010] According to the recognition result, the asynchronous notification is sent to the corresponding merchant system.

[0011] According to an asynchronous notification routing method provided by the present invention, sending the asynchronous notification to a corresponding merchant system according to the identification result includes:

[0012] If the identification result indicates that the callback address is a public network address, sending the asynchronous notification to a first merchant system connected to the public network;

[0013] If the identification result indicates that the callback address is an intranet address of a proxy server deployed in a private network domain, the asynchronous notification is forwarded to the proxy server, and the proxy server sends the asynchronous notification to a second merchant system connected to the private network;

[0014] Wherein, the intranet address is mapped to the private network address.

[0015] According to an asynchronous notification routing method provided by the present invention, the identifying of the callback address of the transaction request message in the asynchronous notification includes:

[0016] The host address and the path address in the callback address are identified respectively.

[0017] According to an asynchronous notification routing method provided by the present invention, the identifying of the host address and the path address in the callback address respectively includes:

[0018] Identify the host address to determine whether the first IP address and the first port number in the host address are consistent with the second IP address and the second port number in the intranet address;

[0019] The path address is identified to determine whether a first path in the path address is consistent with a second path in the intranet address.

[0020] According to an asynchronous notification routing method provided by the present invention, the determining whether the first path in the path address is consistent with the second path in the intranet address includes:

[0021] It is determined whether the first path includes a preset identifier, and if so, the first path is consistent with the second path.

[0022] According to an asynchronous notification routing method provided by the present invention, the preset identifier at least includes:

[0023] A preset identifier and a merchant identification of the second merchant system.

[0024] The present invention also provides an asynchronous notification routing system, comprising: an identification module and a sending module;

[0025] The identification module is used to identify the callback address of the transaction request message in the asynchronous notification according to the front-end application deployed in the DMZ domain;

[0026] The sending module is used to send the asynchronous notification to the corresponding merchant system according to the recognition result.

[0027] The present invention also provides an electronic device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the program, the steps of any of the above-mentioned asynchronous notification routing methods are implemented.

[0028] The present invention also provides a non-transitory computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor, the steps of any of the above-mentioned asynchronous notification routing methods are implemented.

[0029] The present invention also provides a computer program product, comprising a computer program, wherein when the computer program is executed by a processor, the steps of any of the above-mentioned asynchronous notification routing methods are implemented.

[0030] The asynchronous notification routing method and system provided by the present invention utilize a front-end application deployed in a DMZ domain to identify the callback address of a transaction request message (e.g., a payment request message) in an asynchronous notification (e.g., an asynchronous result notification sent by a payment aggregation system), and based on the identification result, send the asynchronous notification to a corresponding merchant system, thereby improving the efficiency of sending the asynchronous notification (e.g., making the payment aggregation system more efficient in sending asynchronous result notifications). BRIEF DESCRIPTION OF THE DRAWINGS

[0031] In order to more clearly illustrate the technical solutions in the present invention or the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0032] Figure 1 It is a flow chart of a two-level proxy solution provided by the prior art;

[0033] Figure 2 This is one of the flow charts of the asynchronous notification routing method provided by the present invention;

[0034] Figure 3 This is the second flow chart of the asynchronous notification routing method provided by the present invention;

[0035] Figure 4 It is a structural schematic diagram of the asynchronous notification routing system provided by the present invention;

[0036] Figure 5 It is a schematic diagram of the physical structure of the electronic device provided by the present invention. DETAILED DESCRIPTION

[0037] In order to make the purpose, technical solution and advantages of the present invention clearer, the technical solution of the present invention will be clearly and completely described below in conjunction with the drawings of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0038] In view of the existing solutions such as application transformation, application system split deployment and two-level proxy solutions, there are defects such as large development and operation and maintenance workload, low efficiency in sending payment asynchronous result notifications, and traffic aggregation to determine whether the destination address is a public network or a private network before forwarding. The present invention provides an asynchronous notification routing method, which does not require any transformation of the application system, and only requires adding a layer of soft load balancer (as a proxy server) in the private network domain, which can be Nginx or HaProxy, with an intranet address (IP address: port) and a private network address (IP address: port). If only one external merchant system needs to send the asynchronous result notification (i.e., asynchronous notification) through the private network, it is only necessary to tell this external merchant system to replace the private network address of the callback address feedbackUrl attribute in its transaction request message with the intranet address of the load balancer (such as Nginx), and then set proxy_pas in the reverse proxy of Nginx to forward it to its private network address, so that the asynchronous result notification can be sent to the correct receiving address of the external merchant system.

[0039] If more than one external merchant needs to send asynchronous result notifications through a dedicated line, notify these external merchant systems to change the URL value of their callback address attribute in the transaction request message (such as the payment request message) to the Nginx IP of the payment aggregation system: port + " / preset identifier + / path address (path).

[0040] In the upstream part of the Nginx configuration file of the payment aggregation system intranet located in the core domain, the private network address of each merchant system is placed under the upstream of merchant-{merchant identifier (such as merchant code)}. In the location part, the matching filter condition is based on the / preset identifier, and its reverse proxy proxy_pass is configured as http: / / merchant-{merchant code} / , so that Nginx accesses the merchant's asynchronous result notification receiving address and just overwrites the / preset identifier in the callback address feedbackUrl, and accesses the correct receiving address private network address + path of the external merchant. In this way, the modified address of the asynchronous result notification in the external merchant system request message is mapped one by one with its real receiving address in the Nginx configuration file.

[0041] Compared with other methods, the proposal of the present invention has very obvious advantages: 1. The impact on other merchants and their businesses that transmit asynchronous result notifications through the public network is 0, and there is no process for judging whether all addresses are public network addresses or dedicated line addresses. 2. The configuration is simple to implement. Only one Nginx is added to the interface domain. There is no need to deploy any components of the aggregation system in the interface domain. Maintenance is simple. Even if Nginx has an abnormality, it will only affect the part of the asynchronous notification request that goes through the dedicated network. 3. The scope of impact of the change is smaller. For example, if there are new external merchants who need to make requests through the public network and send asynchronous result notifications through the dedicated line. You only need to modify the Nginx configuration file, add the corresponding upstream and location configuration items, and then reload the configuration file to achieve uninterrupted business changes. The specific implementation is as follows:

[0042] Figure 2 This is one of the flow charts of the asynchronous notification routing method provided by the present invention, such as Figure 2 As shown, the method includes:

[0043] S1. Identify the callback address of the transaction request message in the asynchronous notification according to the front-end application deployed in the DMZ domain;

[0044] S2. Send an asynchronous notification to the corresponding merchant system based on the recognition result.

[0045] It should be noted that the execution subject of the above method may be a computer device.

[0046] Optionally, the callback address of the transaction request message in the asynchronous notification is identified according to the front-end application deployed in the DMZ domain. For example, the payment aggregation system in the core domain sends the asynchronous result notification to the front-end application deployed in the DMZ domain through the core application, and maps the IP at the public network. In this way, the front-end application can directly send the asynchronous result notification to the merchant system (Merchant 1 to Merchant N) on the public network according to the public network callback address in the asynchronous result notification object. Because most of the asynchronous result notifications to the merchant system go through the public network, a small part of the asynchronous result notifications need to go through a dedicated line. Such a deployment can make the payment aggregation system more efficient in sending asynchronous result notifications.

[0047] By identifying the callback address of the transaction request message in the asynchronous notification, it is determined whether to send the asynchronous notification to the merchant system connected to the public network or the merchant system connected to the private network (Merchant A to Merchant Z) based on the identification result.

[0048] The asynchronous notification routing method provided by the present invention utilizes a front-end application deployed in a DMZ domain to identify the callback address of a transaction request message (such as a payment request message) in an asynchronous notification (such as an asynchronous result notification sent by a payment aggregation system), and sends the asynchronous notification to a corresponding merchant system based on the identification result, thereby improving the efficiency of sending the asynchronous notification (for example, the payment aggregation system can be made more efficient in sending the asynchronous result notification).

[0049] Furthermore, in one embodiment, step S2 may specifically include:

[0050] S21. If the identification result indicates that the callback address is a public network address, an asynchronous notification is sent to a first merchant system connected to the public network;

[0051] S22. If the identification result indicates that the callback address is an intranet address of a proxy server deployed in the private network domain, the asynchronous notification is forwarded to the proxy server, and the proxy server sends the asynchronous notification to a second merchant system connected to the private network;

[0052] Among them, the intranet address is mapped to the private network address.

[0053] Optionally, by deploying a load balancer Nginx as a reverse proxy server in the private network domain, providing an intranet IP such as 192.168.XX.XX:8090, and mapping the private network IP, Nginx can access the merchant system interface whose asynchronous notification address belongs to the private network. Assume that the merchant code of merchant system A is 0001, and its asynchronous notification address is http: / / IP1:port1 / path1, the merchant code of merchant system B is 0002, and its dedicated line result notification address is http: / / IP2:port2 / path2, and the merchant code of merchant system Z is XXXX, and its dedicated line result notification address is http: / / IPN:portN / pathN. The reverse proxy configuration of Nginx is shown in Table 1 below. Each row of configuration corresponds to a second merchant system. The number of rows of configuration is the same as the number of second merchant systems that need to use dedicated lines for asynchronous notifications.

[0054] Table 1

[0055]

[0056] Negotiate with the second merchant system that needs to use a dedicated line for asynchronous notification, and request to change the value of the callback address attribute in its payment request message, replace its host address (first IP address: first port number) with the Nginx intranet interface 192.168.XX.XX:8090 (second IP address: second port number) deployed in the dedicated line domain, and add the merchant system's preset identifier, such as the preset identifier + merchant identifier, before the original path address path part in the callback address in the payment request message, such as the conversion identifier string - " / transform-" + {merchant code}: For example, the value of the callback address attribute of merchant system A is http: / / IP1:port1 / path1, which needs to be changed to http: / / 192.168.XX.XX:8090 / transform-0001 / path1, that is, the original bearer network IP + port needs to be replaced with the Nginx intranet interface deployed in the dedicated line domain, and " / transform-" + {merchant code} needs to be added before the original path. Code} prefix string (second path address), "transform" can also be replaced with other strings with identification meanings. The mapping example of the callback address attribute value change of the external merchant system payment request message is shown in Table 2. In this way, the front-end application deployed in the DMZ domain will send the asynchronous notification to the Nginx in the dedicated line domain through the intranet according to the replaced callback address. The location module of Nginx will match the replaced path prefix string--" / transform-0001", and will use the proxy path http: / / group-0001 / . Nginx will automatically remove the matched " / transform-0001" part in the path and send it to http: / / group-001 / path1. Since there is only one backend server member IP:port1 in group-001, the URL actually sent to is http: / / IP1:port1 / path1, which happens to be the URL where the merchant system A actually receives asynchronous notifications.

[0057] Table 2

[0058] Merchant Code Merchant asynchronous notification URL Change to the reverse proxy address of the payment collection system intranet 0001 IP1:port1 / path1 192.168.XX.XX:8090 / transform-0001 / path1 0002 IP2:port2 / path2 192.168.XX.XX:8090 / transform-0002 / path2 ... XXXX IP3:port3 / pathX 192.168.XX.XX:8090 / transform-0003 / pathX

[0059] Introduce the second merchant system asynchronous notification address change mapping table, so that the private network host address in the callback address of the suggestion request message sent by the second merchant system is replaced with the intranet address of the payment aggregation system, and the path part in the callback address is added with the conversion identification string related to the second merchant system code + {merchant code} prefix. In this way, Nginx can distinguish the merchant system according to the request path with at least one service port. If the merchant conversion identification string is not added to the payment request message of the second merchant system, the second merchant system can only be distinguished by the Nginx IP and port number. In this case, multiple port services need to be started. As many Nginx ports need to be started as the number of second merchant systems using the private network.

[0060] Using the merchant conversion identification string + {merchant code} as the prefix of the callback address path can enable the reverse proxy server Nginx to identify the target merchant system to which the asynchronous notification belongs at the fastest speed, and send the asynchronous notification to the mapped private network address without the conversion identification string prefix, avoiding traversing the entire path of each URL, thereby improving the speed and throughput of the system sending asynchronous result notifications to the private network merchant system.

[0061] The asynchronous notification can be sent to the corresponding merchant system through the identification result of the callback address of the transaction request message (such as the payment request message) as mentioned above.

[0062] When the merchant system changes the dedicated line request address or adds a new merchant request address, the present invention can achieve zero interruption of system business by utilizing the Nginx reload mechanism; if the business volume increases, the number of requests for sending asynchronous result notifications through the dedicated line is very large, and an Nginx instance can be added to the local machine or other machines in the dedicated line domain, and adjustment planning can be made according to the business volume of the external merchant system, so that the number of requests sent to each Nginx instance is relatively balanced, and expansion and change are simple.

[0063] The asynchronous notification routing method provided by the present invention deploys a front-end application in a DMZ domain in a payment aggregation system in which a public network and a private network are isolated, and an Nginx reverse proxy server is deployed in a private network domain. Most of the asynchronous notifications going through the public network are directly accessed by the front-end application server to the merchant system of the public network, and a small number of asynchronous notifications going through the private line are automatically routed by the front-end application to the reverse proxy server in the private line domain by identifying the callback address in the transaction request message, and the merchant system of the private network is indirectly accessed by the reverse proxy server, thereby achieving the characteristics of special processing for only a small number of asynchronous notifications whose target addresses are the private lines, and no change, filtering or interception for most of the asynchronous notifications whose target addresses are the public network, thereby reducing the introduction of changes and risks.

[0064] Furthermore, in one embodiment, step S1 may specifically include:

[0065] S11. Respectively identify the host address and the path address in the callback address.

[0066] Optionally, the asynchronous notification routing method provided by the present invention only needs to deploy a set of Nginx applications (which can be a single Nginx or a set of keepalived+Nginx highly available applications) in a private network domain with less traffic, and deploy a front-end application for sending asynchronous notifications in a public network domain with a larger request volume. The front-end application accesses the dedicated merchant system with a smaller request volume indirectly through the Nginx reverse proxy, and identifies the host address and path address of the callback address in the asynchronous notification. If it is a public network address, the front-end application deployed in the DMZ domain directly sends the asynchronous notification to the first merchant system connected to the public network; if it is an intranet address, the IP address in the intranet address is mapped to the private network IP address, and the asynchronous notification is sent to the proxy server deployed in the private network domain, and the proxy server sends the asynchronous notification to the second merchant system connected to the private network.

[0067] The asynchronous notification routing method provided by the present invention adopts a technical means that the public network merchant directly asynchronously uses the DMZ domain front-end application, adds an identifier to the private network merchant URL and automatically routes it to the private network domain for URL rewriting and cross-domain access, which solves the technical problem of high coupling between the public network merchant and the private network merchant message asynchronous system in the current payment integration system.

[0068] Furthermore, in one embodiment, step S11 may specifically include:

[0069] S111, identifying the host address to determine whether the first IP address and the first port number in the host address are consistent with the second IP address and the second port number in the intranet address;

[0070] S112: Identify the path address to determine whether the first path in the path address is consistent with the second path in the intranet address.

[0071] Furthermore, in one embodiment, step S111 may specifically include:

[0072] S1111. Determine whether the first path includes a preset identifier. If so, the first path is consistent with the second path.

[0073] Alternatively, if Figure 3As shown, in order to simply and efficiently send asynchronous notifications to merchant systems on the public network and the private network, first, a front-end application for sending asynchronous result notifications is deployed in the DMZ domain so that it can directly access the first merchant system on the public network. Then, a load balancer Nginx is deployed in the private network domain as a reverse proxy server. The second merchant system that requires asynchronous notification to go through the private network modifies the callback address host address in the transaction request message (such as the payment request message) to the intranet address of Nginx, and adds a preset identifier (such as a conversion identifier string prefix) that can identify the second merchant system to the first path address: path part. The asynchronous notification going through the dedicated line will be sent from the front-end application in the DMZ domain to the dedicated line domain Nginx through the intranet. Nginx then identifies the first path address: path part in the intranet address of the payment request message, determines whether the first path address contains the prefix of the preset identifier (conversion identifier + {merchant code}), and identifies which second merchant system the asynchronous notification is from, and sends it to the corresponding second merchant system according to the location and proxy path.

[0074] The preset identification at least includes a preset identifier (such as a transformation identifier transform) and a merchant identification (such as a merchant code) of the second merchant system.

[0075] The asynchronous notification routing method provided by the present invention can reduce the aggregated network traffic, not only making the payment aggregation system send asynchronous notifications with a smaller delay and higher efficiency, but also reducing the business scope affected by the failure. Different from the two-level forward proxy solution in which all traffic must pass through, only the asynchronous notifications on the dedicated line with a smaller network traffic will be aggregated to the proxy Nginx, and most of the other asynchronous notifications on the public network will be directly sent to the merchant system on the public network through numerous front-end applications. Even if the proxy Nginx has an abnormality, it will only affect a small part of the business on the dedicated line, and the vast majority of the business on the public network will not be affected at all.

[0076] The asynchronous notification routing system provided by the present invention is described below. The asynchronous notification routing system described below and the asynchronous notification routing method described above can be referred to each other.

[0077] Figure 4 Schematic diagram of the structure of the asynchronous notification routing system provided by the present invention. Figure 4 As shown, it includes: an identification module 410 and a sending module 411;

[0078] The identification module 410 is used to identify the callback address of the transaction request message in the asynchronous notification according to the front-end application deployed in the DMZ domain;

[0079] The sending module 411 is used to send an asynchronous notification to the corresponding merchant system according to the recognition result.

[0080] The asynchronous notification routing system provided by the present invention utilizes a front-end application deployed in a DMZ domain to identify the callback address of a transaction request message (such as a payment request message) in an asynchronous notification (such as an asynchronous result notification sent by a payment aggregation system), and sends the asynchronous notification to a corresponding merchant system based on the identification result, thereby improving the efficiency of sending the asynchronous notification (for example, the payment aggregation system can be made more efficient in sending the asynchronous result notification).

[0081] Furthermore, in one embodiment, the sending module 411 may also be specifically configured to:

[0082] If the identification result indicates that the callback address is a public network address, an asynchronous notification is sent to the first merchant system connected to the public network;

[0083] If the identification result indicates that the callback address is the intranet address of a proxy server deployed in the private network domain, the asynchronous notification is forwarded to the proxy server, and the proxy server sends the asynchronous notification to the second merchant system connected to the private network;

[0084] Among them, the intranet address is mapped to the private network address.

[0085] The asynchronous notification routing system provided by the present invention deploys a front-end application in a DMZ domain in a payment aggregation system in which a public network and a private network are isolated, and an Nginx reverse proxy server is deployed in a private network domain. Most of the asynchronous notifications going through the public network are directly accessed by the front-end application server to the merchant system of the public network, and a small number of asynchronous notifications going through the private line are automatically routed by the front-end application to the reverse proxy server in the private line domain by identifying the callback address in the transaction request message, and the merchant system of the private network is indirectly accessed by the reverse proxy server, thereby achieving the characteristics of special processing for only a small number of asynchronous notifications whose target addresses are the private lines, and no change, filtering or interception for most of the asynchronous notifications whose target addresses are the public network, thereby reducing the introduction of changes and risks.

[0086] Furthermore, in one embodiment, the identification module 410 may also be specifically used for:

[0087] The host address and path address in the callback address are identified respectively.

[0088] The asynchronous notification routing system provided by the present invention adopts a technical means that public network merchants directly use DMZ domain front-end applications to be asynchronous, private network merchant URLs are marked and automatically routed to the private network domain for URL rewriting and cross-domain access, which solves the technical problem of high coupling between the public network merchant and private network merchant message asynchronous systems in the current payment integration system.

[0089] Furthermore, in one embodiment, the identification module 410 may also be specifically used for:

[0090] Identify the host address to determine whether the first IP address and the first port number in the host address are consistent with the second IP address and the second port number in the intranet address;

[0091] The path address is identified to determine whether a first path in the path address is consistent with a second path in the intranet address.

[0092] Determine whether the first path contains a preset identifier, if so, the first path is consistent with the second path;

[0093] The preset identification at least includes a preset identifier and a merchant identification of the second merchant system.

[0094] The asynchronous notification routing system provided by the present invention can reduce the aggregated network traffic, not only making the payment aggregation system send asynchronous notifications with a smaller delay and higher efficiency, but also reducing the business scope affected by failures. Different from the two-level forward proxy solution in which all traffic must pass through, only the asynchronous notifications on the dedicated line with a smaller network traffic will be aggregated to the proxy Nginx, and most of the other asynchronous notifications on the public network will be directly sent to the merchant system on the public network through numerous front-end applications. Even if the proxy Nginx has an abnormality, it will only affect a small part of the business on the dedicated line, and the vast majority of the business on the public network will not be affected at all.

[0095] Figure 5 is a schematic diagram of the physical structure of an electronic device provided by the present invention, such as Figure 5 As shown, the electronic device may include: a processor 510, a communication interface 511, a memory 512 and a bus 513, wherein the processor 510, the communication interface 511 and the memory 512 communicate with each other through the bus 513. The processor 510 may call the logic instructions in the memory 512 to execute the following method:

[0096] According to the front-end application deployed in the DMZ domain, the callback address of the transaction request message in the asynchronous notification is identified;

[0097] Based on the recognition results, an asynchronous notification is sent to the corresponding merchant system.

[0098] In addition, the logic instructions in the above-mentioned memory can be implemented in the form of software functional units and can be stored in a computer-readable storage medium when sold or used as an independent product. Based on such an understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art or the part of the technical solution, can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for enabling a computer power screen (which can be a personal computer, a server, or a network power screen, etc.) to perform all or part of the steps of the method described in each embodiment of the present invention. The aforementioned storage medium includes: various media that can store program codes, such as a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a disk or an optical disk.

[0099] Furthermore, the present invention discloses a computer program product, the computer program product comprising a computer program stored on a non-transitory computer-readable storage medium, the computer program comprising program instructions, when the program instructions are executed by a computer, the computer can execute the asynchronous notification routing method provided by the above-mentioned method embodiments, for example, comprising:

[0100] According to the front-end application deployed in the DMZ domain, the callback address of the transaction request message in the asynchronous notification is identified;

[0101] Based on the recognition results, an asynchronous notification is sent to the corresponding merchant system.

[0102] On the other hand, the present invention further provides a non-transitory computer-readable storage medium having a computer program stored thereon, which is implemented when the computer program is executed by a processor to execute the asynchronous notification routing method provided in the above embodiments, for example, including:

[0103] According to the front-end application deployed in the DMZ domain, the callback address of the transaction request message in the asynchronous notification is identified;

[0104] Based on the recognition results, an asynchronous notification is sent to the corresponding merchant system.

[0105] The system embodiment described above is merely illustrative, wherein the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment. Those of ordinary skill in the art may understand and implement it without creative work.

[0106] Through the description of the above implementation methods, those skilled in the art can clearly understand that each implementation method can be implemented by means of software plus a necessary general hardware platform, and of course, it can also be implemented by hardware. Based on this understanding, the above technical solution is essentially or the part that contributes to the prior art can be embodied in the form of a software product, and the computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, a disk, an optical disk, etc., including a number of instructions for a computer power screen (which can be a personal computer, a server, or a network power screen, etc.) to execute the methods described in each embodiment or some parts of the embodiments.

[0107] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. An asynchronous notification routing method, characterized in that: include: According to the front-end application deployed in the DMZ domain, the callback address of the transaction request message in the asynchronous notification is identified; According to the recognition result, the asynchronous notification is sent to the corresponding merchant system; The step of sending the asynchronous notification to a corresponding merchant system according to the recognition result includes: If the identification result indicates that the callback address is a public network address, sending the asynchronous notification to a first merchant system connected to the public network; If the identification result indicates that the callback address is an intranet address of a proxy server deployed in a private network domain, the asynchronous notification is forwarded to the proxy server, and the proxy server sends the asynchronous notification to a second merchant system connected to the private network; Wherein, the intranet address is mapped to the private network address.

2. The asynchronous notification routing method according to claim 1, characterized in that: The identifying of the callback address of the transaction request message in the asynchronous notification includes: The host address and the path address in the callback address are identified respectively.

3. The asynchronous notification routing method according to claim 2, characterized in that: The identifying the host address and the path address in the callback address respectively includes: Identify the host address to determine whether the first IP address and the first port number in the host address are consistent with the second IP address and the second port number in the intranet address; The path address is identified to determine whether a first path in the path address is consistent with a second path in the intranet address.

4. The asynchronous notification routing method according to claim 3, characterized in that: The determining whether the first path in the path address is consistent with the second path in the intranet address includes: It is determined whether the first path includes a preset identifier, and if so, the first path is consistent with the second path.

5. The asynchronous notification routing method according to claim 4, characterized in that: The preset identification includes at least: A preset identifier and a merchant identification of the second merchant system.

6. An asynchronous notification routing system, characterized in that: include: Identification module and sending module; The identification module is used to identify the callback address of the transaction request message in the asynchronous notification according to the front-end application deployed in the DMZ domain; The sending module is used to send the asynchronous notification to the corresponding merchant system according to the recognition result; The sending module is further used for: If the identification result indicates that the callback address is a public network address, sending the asynchronous notification to a first merchant system connected to the public network; If the identification result indicates that the callback address is an intranet address of a proxy server deployed in a private network domain, the asynchronous notification is forwarded to the proxy server, and the proxy server sends the asynchronous notification to a second merchant system connected to the private network; Wherein, the intranet address is mapped to the private network address.

7. An electronic device comprising a processor and a memory storing a computer program, characterized in that: When the processor executes the computer program, the steps of the asynchronous notification routing method according to any one of claims 1 to 5 are implemented.

8. A processor-readable storage medium, characterized in that: The processor-readable storage medium stores a computer program, and the computer program is used to enable the processor to execute the steps of the asynchronous notification routing method according to any one of claims 1 to 5.

9. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the asynchronous notification routing method according to any one of claims 1 to 5 are implemented.