Highway mobile payment active-active center system

Abstract

The invention provides an expressway mobile payment active-active center system, and relates to the technical field of computer systems, the system comprises two data centers arranged in a target area; the two data centers are respectively used for receiving different expressway mobile payment requests from the expressway lane system, carrying out business processing and forwarding the requests to a payment channel for payment; summarized data of the data center and the other data center are also stored; a cache layer is arranged in one data center and is used for storing respective state monitoring result data of the two data centers, so that when each data center determines that the state of the data center is abnormal currently according to the state monitoring result data, abnormity recovery processing or double-center automatic switching is carried out. According to the invention, the mobile payment active-active center can process real-time expressway transactions at the same time, automatic switching between the two centers can be realized, the efficiency and reliability of data processing after switching can be improved, and then the real-time performance and reliability of expressway mobile payment can be improved.

Description

Technical Field

[0001] The present application relates to the field of computer system technology, and in particular to a highway mobile payment dual-active center system. Background Art

[0002] Mobile payment on highways refers to installing smart POS (Point of Sales, multi-function terminal) devices at highway exit toll booths to replace cash payment. Car owners complete payment by selecting a third-party payment platform corresponding to a payment channel. In addition to installing smart POS devices on the lanes, a mobile payment system is also built to realize transaction records and payment processing functions. The specific payment process is as follows: Figure 1 As shown, the car owner presents the payment code to the smart POS at the toll booth, which calculates the fee and displays the amount. The QR code is then identified to send the corresponding payment request to the mobile payment system, which registers the order and forwards the request to the third-party payment platform, receives the corresponding payment result and updates the order status, and then sends a response result to the smart POS to display the payment success message to the car owner's mobile terminal and enable the toll booth to lift the barrier and release the vehicle, allowing the vehicle to leave the highway. As mobile payments account for an increasing proportion of highway payments, the requirements for the stability and reliability of highway mobile payments are also increasing. At present, the highway mobile payment system adopts a single-center deployment architecture, and load balancing technology is used within a single data center to achieve service distribution. The specific network architecture is as follows: Figure 2 As shown, the lane system, the mobile payment system and the payment channel (i.e., the third-party payment platform) are connected in sequence. The mobile payment system includes a service cluster and a database system based on load balancing, and the service cluster includes multiple servers.

[0003] However, traditional highway mobile payment systems have problems such as poor stability and reliability, and are unable to cope with problems such as power outages in the center and natural disasters. When problems occur in the center network or database, the entire mobile payment system will crash, seriously affecting highway traffic. Summary of the invention

[0004] In view of this, an embodiment of the present application provides a highway mobile payment dual-active center system to eliminate or improve one or more defects existing in the prior art.

[0005] One aspect of the present application provides a highway mobile payment dual-active center system, comprising: two simultaneously online data centers arranged in the same target area and communicating with each other; The two data centers are respectively used to receive different highway mobile payment requests from various highway lane systems in the target area, and each data center is used to perform business processing on the highway mobile payment requests received by itself according to various servers set up locally and forward them to external payment channels, so as to receive corresponding payment result data from the payment channel, and if the payment result data shows that the payment is successful, the payment result data is sent to the corresponding highway lane system; Each of the data centers stores summary data of itself and another data center, including the corresponding highway mobile payment request and the payment result data; A cache layer is provided in one of the data centers, which is used to store the status monitoring result data corresponding to each of the two data centers, so that when each data center determines that its current status is abnormal based on its own status monitoring result data stored in the cache layer, it can perform abnormal recovery processing or send its current highway mobile payment request received from the highway lane system to the other data center for processing.

[0006] In some embodiments of the present application, a business layer is provided in each of the data centers; The business layer is used to perform business processing on the highway mobile payment requests received by itself according to the various servers set up locally, so as to convert the order number in the highway mobile payment request into a payment order number that complies with the preset order coding rules of the target payment channel according to the target payment channel specified by the highway mobile payment request, and transmit the highway mobile payment request and the corresponding payment order number internally in the data center where it is located.

[0007] In some embodiments of the present application, each data center is further provided with an outbound layer; each outbound layer is communicatively connected with the business layer of the data center where it is located and various external payment channels; The outbound layer is used to receive the highway mobile payment request and the corresponding payment order number transmitted by the business layer, and forward the highway mobile payment request and the payment order number to the target payment channel for payment based on the preset core transmission area according to the various servers set up locally, and receive the payment result data for the highway mobile payment request returned by the target payment channel based on the preset isolation area, wherein the core transmission area and the isolation area are different partitions formed by pre-splitting the various transmission channels.

[0008] In some embodiments of the present application, a front layer is provided in each of the data centers; The front layer includes: a routing service unit; The routing service unit in each data center is respectively connected to each of the high-speed lane systems in the target area, the service layer in the data center where the routing service unit is located, the outbound layer in the data center where the routing service unit is located, and the service layer in another data center; The routing service unit is used to receive the highway mobile payment request sent by the highway lane system in the target area, and send the highway mobile payment request to the business layer in the data center where the routing service unit is located; The routing service unit is also used to perform the following: When or after the highway mobile payment request is sent to the business layer in the data center where the mobile payment request is located, asynchronously sending a response query request to the outbound layer in the data center where the mobile payment request is located; If the payment result data returned by the outgoing layer in the data center based on the response query request is received within a preset time period, the current payment status of the order corresponding to the highway mobile payment request shown in the payment result data is obtained; If the payment status is successful, forwarding the payment result data to the expressway lane system that issued the expressway mobile payment request; If the payment status is in payment, a response query request is sent again to the outbound layer in the data center where the device is located; If the payment status is payment failure, or if the payment result data returned by the outgoing layer in the data center based on the response query request is not received within a preset time period, the highway mobile payment request corresponding to the payment result data will be forwarded to the business layer in another data center for processing.

[0009] In some embodiments of the present application, the front layer further includes: a heartbeat monitoring unit; The heartbeat monitoring unit is in communication connection with the cache layer and the routing service unit of the data center where the heartbeat monitoring unit is located; The heartbeat monitoring unit is used to obtain the current status monitoring result data of the data center where the heartbeat monitoring unit is located from the cache layer. If it is determined that the data center where the heartbeat monitoring unit is located currently has an abnormal status according to the status monitoring result data, a corresponding abnormal notification message is generated and sent to the routing service unit in the data center where the heartbeat monitoring unit is located. Correspondingly, the routing service unit is also used to forward the currently received highway mobile payment request to the business layer in another data center for processing when receiving an abnormal notification message sent by the heartbeat monitoring unit in the data center where it is located.

[0010] In some embodiments of the present application, each of the data centers is provided with a data layer; The database in the data layer includes: a business database and a summary database; The business library is respectively connected to the business layer and the outbound layer in the data center where the business library is located, and the business library is used to obtain the one-to-one corresponding highway mobile payment request, the order number, the payment order number and the payment result data from the business layer and the outbound layer in the data center where the business library is located, and store the one-to-one corresponding highway mobile payment request, the order number, the payment order number and the payment result data as payment record data; The business libraries in the two data centers are used to synchronize the payment record data stored in the business libraries to the summary library in one data center based on a preset synchronization program; Correspondingly, the summary library in one of the data centers is used to receive the payment record data sent by the business libraries in the two data centers, store the payment record data as summary data, and periodically send the summary data to the summary library in the other data center for backup storage.

[0011] In some embodiments of the present application, each of the data centers is provided with a monitoring layer; the status monitoring result data includes: server status monitoring result data; The monitoring layer includes: a heartbeat service unit; The heartbeat service unit is respectively connected to the business layer, the outbound layer and the data layer in the data center where the heartbeat service unit is located, and the heartbeat service unit is also connected to the cache layer; The heartbeat service unit is used to perform real-time status monitoring on each server in the business layer, outbound layer and data layer in the data center where the heartbeat service unit is located, and send the corresponding server status monitoring result data to the cache layer for storage; The heartbeat service unit is used to determine whether the data of each of the servers currently in the available state in the data center where the heartbeat service unit is located is less than a preset quantity threshold when the server status monitoring result data shows that the server is abnormal; if not, execute the preset abnormal recovery processing steps; The abnormal recovery process includes: Sending an exception notification message including the unique number corresponding to the server with the exception to an external removal platform, so that the removal platform performs service removal processing on the server specified in the exception notification message based on the unique number corresponding to the server in the received exception notification message and based on the preset automatic removal configuration information, and sending a corresponding removal notification message including the unique number corresponding to the removed server to the heartbeat service unit; The heartbeat service unit is also used to send an exception recovery message with a unique number corresponding to the removed server to the cache layer when receiving the removal notification message, so that the cache layer updates the server status monitoring result data according to the exception recovery notification message.

[0012] In some embodiments of the present application, the monitoring layer further includes: a detection service unit; the status monitoring result data further includes: database connection status monitoring result data and external network connection status monitoring result data; The detection service unit is respectively connected to the outbound layer and the data layer in the data center where the detection service unit is located, and the detection service unit is also connected to the cache layer; The detection service unit is used to perform real-time external network connection status monitoring on the outbound layer in the data center where the detection service unit is located, and send the corresponding database connection status monitoring result data to the cache layer for storage; The detection service unit is used to perform real-time database connection status monitoring on the data layer in the data center where the detection service unit is located, and send the corresponding external network connection status monitoring result data to the cache layer for storage.

[0013] In some embodiments of the present application, the heartbeat service unit is also used to obtain the database connection status monitoring result data and the external network connection status monitoring result data stored by the detection service unit in the monitoring layer where the heartbeat service unit is located from the cache layer when it is determined that the data of each of the servers currently in an available state in the data center where the heartbeat service unit is located is less than a preset quantity threshold; if at least one of the database connection status monitoring result data and the external network connection status monitoring result data shows a connection abnormality, the abnormal recovery processing step is executed.

[0014] In some embodiments of the present application, one of the data centers provided with the cache layer is further used to receive a transaction query request from a clearing center corresponding to the target area, and generate query result data corresponding to the transaction query request according to the summary data stored locally, and return the query result data to the clearing center; The data center equipped with the cache layer is also used to receive refund requests from the clearing center, and perform business processing on the refund requests according to its own servers and forward them to an external payment channel, so as to receive corresponding refund result data from the payment channel. If the refund result data shows that the refund is successful, the refund result data is sent to the clearing center.

[0015] The highway mobile payment dual-active center system provided by the present application includes two simultaneously online data centers arranged in the same target area and communicating with each other; the two data centers are respectively used to receive different highway mobile payment requests from each highway lane system in the target area, and each of the data centers is used to perform business processing on the highway mobile payment requests received by itself according to each server arranged locally and forward them to an external payment channel, so as to receive corresponding payment result data from the payment channel, and if the payment result data shows that the payment is successful, the payment result data is sent to the corresponding highway lane system; each of the data centers stores summary data of itself and the other data center including the corresponding highway mobile payment request and the payment result data; a cache layer is provided in one of the data centers, and the cache layer is used to store the status monitoring result data corresponding to each of the two data centers, so that each of the data centers can perform abnormal recovery processing when it determines that its current state is abnormal according to its own status monitoring result data stored in the cache layer. The data center can process or send the highway mobile payment request currently received from the highway lane system to the other data center for processing. By processing orders online in both centers, the mobile payment dual-active centers can simultaneously process real-time transactions on highways, which can effectively meet the requirements of highway mobile payment scenarios for real-time and stability of data synchronization; by sharing aggregated data in the two centers, when the two centers switch to transfer payment requests, the data center that takes over the payment request can still process the transaction quickly and normally, and when the upper level or management system obtains the payment data of the target area, it only needs to communicate with one of the data centers, thereby improving the convenience and efficiency of payment data management; by designing a cache layer for storing real-time status monitoring results, the two centers can quickly perform abnormal recovery or automatic switching of the two centers when determining that they have abnormalities, which can realize automatic switching between the two centers and improve the efficiency and reliability of data processing after switching, thereby improving the real-time and reliability of highway mobile payments; at the same time, using dual data centers with the same architecture can effectively reduce the maintenance cost and upgrade difficulty of the dual data centers.

[0016] Additional advantages, purposes, and features of the present application will be partially described in the following description, and will become partially apparent to those skilled in the art after studying the following, or may be learned from the practice of the present application. The purposes and other advantages of the present application can be achieved and obtained by the structures specifically pointed out in the specification and the drawings.

[0017] Those skilled in the art will understand that the purposes and advantages that can be achieved by the present application are not limited to the above specific description, and the above and other purposes that can be achieved by the present application will be more clearly understood based on the following detailed description. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] The drawings described herein are used to provide a further understanding of the present application, constitute a part of the present application, and do not constitute a limitation of the present application. The components in the drawings are not drawn to scale, but are only for the purpose of illustrating the principles of the present application. In order to facilitate the illustration and description of some parts of the present application, the corresponding parts in the drawings may be enlarged, that is, they may become larger relative to other components in the exemplary device actually manufactured according to the present application. In the drawings: Figure 1 This is a schematic diagram of the high-speed mobile payment process.

[0019] Figure 2 This is a diagram of a single-center deployment architecture.

[0020] Figure 3 Schematic diagram of the active-standby dual-center mode.

[0021] Figure 4 Schematic diagram of the pseudo dual-center model.

[0022] Figure 5 This is a schematic diagram of the first architecture of the highway mobile payment active-active center system in one embodiment of the present application.

[0023] Figure 6 This is a schematic diagram of the second architecture of the highway mobile payment active-active center system in one embodiment of the present application.

[0024] Figure 7 A schematic diagram of an asynchronous query process executed by a routing service unit in an embodiment of the present application.

[0025] Figure 8 This is a schematic diagram of the third architecture of the highway mobile payment active-active center system in one embodiment of the present application.

[0026] Fig. 9 Schematic diagram of the architecture of the highway mobile payment dual-active system provided for the application example of this application.

[0027] Fig.10This is a schematic diagram of the architecture for deploying Redis in a cluster manner and providing API calls to other modules for the application example of this application.

[0028] Fig.11 A schematic diagram of the logical architecture of the data layer provided for this application example.

[0029] Fig.12 Schematic diagram of the execution logic of automatic removal of services provided for this application example.

[0030] Fig.13 A schematic diagram of the execution flow for obtaining the number of servers in normal status in each data center provided for the application example of this application.

[0031] Reference numerals: 10. Data center; 1. Cache layer; 2. Business layer; 3. Outer hair layer; 4. Pre-layer; 41. Routing service unit; 42. Heartbeat monitoring unit; 5. Data layer; 51. Business database; 52. Summary library; 6. Monitoring layer; 61. Heartbeat service unit; 62. Exploration service unit; 20. High-speed lane system; 30. Payment channel; 40. Clearing center. DETAILED DESCRIPTION

[0032] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the implementation modes and the accompanying drawings. Here, the illustrative implementation modes and descriptions of the present application are used to explain the present application, but are not intended to limit the present application.

[0033] It should also be noted here that in order to avoid obscuring the present application due to unnecessary details, only the structures and / or processing steps closely related to the scheme according to the present application are shown in the accompanying drawings, while other details that are not very relevant to the present application are omitted.

[0034] It should be emphasized that the term “include / comprises” when used herein refers to the presence of features, elements, steps or components, but does not exclude the presence or addition of one or more other features, elements, steps or components.

[0035] It should also be noted that, unless otherwise specified, the term “connection” herein may refer not only to a direct connection but also to an indirect connection involving an intermediate.

[0036] Hereinafter, embodiments of the present application will be described with reference to the accompanying drawings. In the accompanying drawings, the same reference numerals represent the same or similar components, or the same or similar steps.

[0037] It should be noted that mobile payment refers to a digital payment method made through mobile devices (such as smartphones and smart POS machines). It uses wireless communication technology and mobile Internet to realize transactions. Consumers can transfer funds from their bank accounts or other payment accounts to merchant accounts through mobile payment applications or other related technologies to complete payment. Scan payment is a mobile payment method, also known as payment code payment. Merchants complete payment by scanning the QR code generated by the user's virtual wallet.

[0038] Load balancing is a network technology that distributes network traffic to multiple servers to improve system performance, increase availability and fault tolerance. In simple terms, it is to distribute requests to multiple servers for processing to avoid overloading a single server and causing system paralysis or slow response. Load balancing can be implemented at different levels, such as hardware load balancer, software load balancer, etc. Common load balancing algorithms include polling, minimum number of connections, IP hash, etc. Load balancing is very common in Internet applications, especially for high-concurrency websites or applications, it is one of the indispensable technical means.

[0039] In order to solve the problems of poor stability and reliability of the single data center for highway mobile payment, inability to cope with power outages and natural disasters in the center, and downtime of the entire mobile payment system when problems occur in the center network or database, the designer of this application first considered applying the dual center of the pseudo dual center or active-standby dual center mode commonly used in cloud computing and large enterprise systems to the highway mobile payment scenario. Dual center refers to the establishment of two or more data centers in the same geographical area, and the deployment of applications and data to these data centers at the same time. These data centers are connected by high-speed networks and bear a certain amount of traffic load respectively to achieve the purpose of improving the availability, fault tolerance and disaster recovery capabilities of applications. When one of the data centers fails or the service stops, other data centers can take over its load to ensure the continuous and stable operation of the entire system. Dual center deployment usually requires data synchronization and load balancing to ensure data synchronization and balanced request distribution between each data center. In cloud computing and large enterprise systems, dual center deployment has become a common solution to provide higher reliability and availability.

[0040] Among them, the main center is responsible for the core business, and the backup center does not do real-time business, backs up the main center data, and handles some query business at the same time. The specific mode is as follows: Figure 3 As shown, the lane system is only connected to the main data center (i.e. Figure 3 The management system communicates only with the backup data center (i.e. Figure 3 The main data center and the backup data center both have service clusters and database systems based on load balancing, and the service clusters contain multiple servers. However, the reliability of this method is still poor. When the main data center is abnormal or fails, the backup data center needs to be started and the data of the main center needs to be synchronized to the backup center, which will lead to low efficiency and poor reliability of the highway mobile payment processing process.

[0041] The pseudo dual-center model is that the two data centers use different links and payment channels, and the two data centers are completely independent. Figure 4 As shown in the figure, the lane system communicates with a mobile payment system and a third-party system using different links and payment channels. The third-party payment system includes payment services, databases, and payment channels that are connected in sequence. However, this method has poor maintainability and high maintenance costs for dual centers in different modes. It is also difficult to upgrade, which means that a large number of modifications to the original system are required, and smooth upgrades cannot be achieved.

[0042] From the above, it can be seen that both the active-standby dual-center mode and the pseudo-dual-center mode cannot simultaneously meet the requirements of reliability, efficiency, and real-time performance of highway mobile payment. Therefore, the designer of the present application designed an active-active center, that is, two data centers using the same link and payment channel simultaneously provide highway mobile payment services. At this time, we have to face technical difficulties such as the high requirements of real-time and stability of data synchronization in the active-active center. Based on this, the embodiment of the present application provides a highway mobile payment active-active center system, which transforms the mobile payment system into an active-active center, upgrades the system to a highly reliable system, makes it universal and can overcome technical difficulties such as high requirements of real-time and stability of data synchronization, and can be applied to different high-speed mobile payment systems to achieve dual-center transformation of the system without invading the source system.

[0043] The details are described in detail through the following examples.

[0044] Based on this, the present application embodiment provides a highway mobile payment dual-active center system, see Figure 5 The highway mobile payment active-active center system specifically includes the following contents: Two simultaneously online data centers 10 are arranged in the same target area and are communicatively connected to each other.

[0045] In one or more embodiments of the present application, the target area refers to a geographical area range that can be preset manually, for example, it can be divided based on cities, administrative districts, etc. The online refers to a state of being accessible and communicable through an Internet connection. In this state, the data center 10 can access the Internet or communicate with other online devices.

[0046] The two data centers 10 are respectively used to receive different highway mobile payment requests from each highway lane system 20 in the target area, and each data center 10 is used to perform business processing on the highway mobile payment requests received by itself according to each server set up locally and forward them to the external payment channel 30, so as to receive corresponding payment result data from the payment channel 30. If the payment result data shows that the payment is successful, the payment result data is sent to the corresponding highway lane system 20.

[0047] It is understandable that the highway mobile payment request must at least include the order number, the unique identifier of the designated third-party payment platform and the payment amount calculated by the highway lane system 20, and may also include other data required for highway mobile payment such as the unique identifier of the vehicle and the unique identifier of the highway lane system 20.

[0048] In one or more embodiments of the present application, the highway lane system 20 refers to a terminal device installed at a toll booth of a highway exit lane, which may be referred to as a lane system. For example, the highway lane system 20 may use a smart POS device.

[0049] Each of the data centers 10 stores summary data of itself and another data center 10 including the corresponding highway mobile payment request and the payment result data.

[0050] A cache layer 1 is provided in one of the data centers 10, and the cache layer 1 is used to store the status monitoring result data corresponding to each of the two data centers 10, so that when each of the data centers 10 determines that its current status is abnormal based on its own status monitoring result data stored in the cache layer 1, it performs abnormal recovery processing or sends its current highway mobile payment request received from the highway lane system 20 to another data center 10 for processing.

[0051] In one or more embodiments of the present application, the expression of the layer refers to the division of functional modules, for example, the cache layer 1 refers to a functional module for caching data.

[0052] It is understandable that the status monitoring result data refers to the monitoring result data corresponding to the data center 10, such as server status (such as whether the server is operating normally and whether it communicates normally with other modules or other databases), database connection status (such as whether the database communicates normally with other modules or other databases), and external network connection status (such as whether it communicates normally with an external third-party payment platform). Normal operation means that the server can perform business processing on the received highway mobile payment request based on preset business processing rules. Normal communication can refer to the ability to transmit information by establishing an information transmission (transfer) channel (channel) between the source (starting end) and the destination (end) according to a consistent transmission protocol.

[0053] From the above description, it can be seen that the highway mobile payment dual-active center system provided by the embodiment of the present application can realize that the mobile payment dual-active centers can simultaneously process real-time transactions on highways by processing orders online in both centers, and can effectively meet the requirements of highway mobile payment scenarios for real-time and stability of data synchronization; by sharing aggregated data by the dual centers, it can be achieved that when the dual centers switch to transfer payment requests, the data center 10 that takes over the payment request can still process the transaction quickly and normally, and when the upper level or management system obtains the payment data of the target area, it only needs to communicate with one of the data centers 10, thereby improving the convenience and efficiency of payment data management; by designing a cache layer 1 for storing real-time status monitoring results, the dual centers can quickly perform abnormal recovery or automatic switching of the dual centers when determining that they have an abnormality, and can realize automatic switching between the dual centers and improve the efficiency and reliability of data processing after switching, thereby improving the real-time and reliability of highway mobile payments; at the same time, the use of dual data centers 10 with the same architecture can effectively reduce the maintenance cost and upgrade difficulty of the dual data centers 10.

[0054] In order to further improve the efficiency and reliability of highway mobile payment, in a highway mobile payment dual-active center system provided in the embodiment of the present application, see Figure 6 The highway mobile payment active-active center system specifically includes the following contents: Each of the data centers 10 is provided with a business layer 2 .

[0055] The business layer 2 is used to perform business processing on the highway mobile payment requests received by itself according to the various servers set up locally, so as to convert the order number in the highway mobile payment request into a payment order number that complies with the preset order coding rules of the target payment channel 30 according to the target payment channel 30 specified by the highway mobile payment request, and transmit the highway mobile payment request and the corresponding payment order number internally in the data center 10 where it is located.

[0056] It is understandable that the data center 10 can establish communication connections with multiple payment channels 30 (i.e., third-party payment platforms), and the highway lane system 20 will use a payment channel 30 specified by the car owner's mobile device as the target payment channel 30.

[0057] In order to further improve the reliability of outgoing payment requests during the highway mobile payment process, in a highway mobile payment dual-active center system provided in an embodiment of the present application, see Figure 6 The highway mobile payment active-active center system specifically includes the following contents: Each of the data centers 10 is also provided with an outbound layer 3; each of the outbound layers 3 is communicatively connected with the business layer 2 of the data center 10 where it is located and various external payment channels 30.

[0058] The outbound layer 3 is used to receive the highway mobile payment request and the corresponding payment order number transmitted by the business layer 2, and forward the highway mobile payment request and the payment order number to the target payment channel 30 for payment based on the preset core transmission area according to the various servers set up locally, and receive the payment result data for the highway mobile payment request returned by the target payment channel 30 based on the preset isolation area, wherein the core transmission area and the isolation area are different partitions formed by pre-splitting the various transmission channels.

[0059] In order to achieve high-availability routing and asynchronous query, and thus improve the payment efficiency of highway mobile payment and the reliability and timeliness of dual-center automatic switching, in a highway mobile payment dual-active center system provided in an embodiment of the present application, see Figure 6 The highway mobile payment active-active center system specifically includes the following contents: Each of the data centers 10 is provided with a front layer 4 .

[0060] The front layer 4 includes: a routing service unit 41.

[0061] The routing service unit 41 in each data center 10 is respectively connected to each of the high-speed lane systems 20 in the target area, the business layer 2 in its own data center 10, the outbound layer 3 in its own data center 10, and the business layer 2 in another data center 10.

[0062] The routing service unit 41 is used to receive the highway mobile payment request sent by the highway lane system 20 in the target area, and send the highway mobile payment request to the business layer 2 in the data center 10 where the routing service unit 41 is located; See also Figure 7 The routing service unit 41 is also used to execute the following asynchronous query process: Step 110: When or after the highway mobile payment request is sent to the business layer in the data center where the data center is located, a response query request is asynchronously sent to the outbound layer in the data center where the data center is located.

[0063] Step 120: If the payment result data returned by the outbound layer in the data center based on the response query request is received within a preset time period, the current payment status of the order corresponding to the highway mobile payment request shown in the payment result data is obtained, and then one of steps 140 to 160 is selected for execution according to the payment status.

[0064] Step 130: If the payment result data returned by the outbound layer in the data center based on the response query request is not received within a preset time period, the highway mobile payment request corresponding to the payment result data is forwarded to the business layer in another data center for processing.

[0065] Step 140: If the payment status is successful, the payment result data is forwarded to the highway lane system that issued the highway mobile payment request.

[0066] Step 150: If the payment status is in payment, a response query request is sent again to the outbound layer in the data center where the data center is located.

[0067] Step 160: If the payment status is payment failure, the highway mobile payment request corresponding to the payment result data is forwarded to the business layer in another data center for processing.

[0068] In order to further improve the timeliness of the automatic switching of the dual centers, and thus ensure the real-time and reliability of payment, in a highway mobile payment dual active center system provided in the embodiment of the present application, see Figure 6The highway mobile payment active-active center system specifically includes the following contents: The front layer 4 further includes a heartbeat monitoring unit 42 .

[0069] The heartbeat monitoring unit 42 is communicatively connected with the cache layer 1 and the routing service unit 41 of the data center 10 where the heartbeat monitoring unit 42 is located.

[0070] The heartbeat monitoring unit 42 is used to obtain the current status monitoring result data of the data center 10 where it is located from the cache layer 1. If it is determined based on the status monitoring result data that the data center 10 where it is located currently has a status abnormality, a corresponding abnormality notification message is generated and the abnormality notification message is sent to the routing service unit 41 in the data center 10 where it is located.

[0071] Correspondingly, the routing service unit 41 is also used to forward the currently received highway mobile payment request to the business layer 2 in another data center 10 for processing when receiving an abnormal notification message sent by the heartbeat monitoring unit 42 in the data center 10 where it is located.

[0072] In order to further ensure that the transaction can be processed normally during transfer and to improve the convenience and efficiency of the upper-level system in obtaining data in the same area, in a highway mobile payment active-active center system provided in the embodiment of the present application, see Figure 6 The highway mobile payment active-active center system specifically includes the following contents: Each of the data centers 10 is provided with a data layer 5 .

[0073] The database in the data layer 5 includes: a business database 51 and a summary database 52 .

[0074] The business library 51 is respectively communicated with the business layer 2 and the outbound layer 3 in the data center 10 where it is located. The business library 51 is used to obtain the one-to-one corresponding highway mobile payment request, the order number, the payment order number and the payment result data from the business layer 2 and the outbound layer 3 in the data center 10 where it is located, and store the one-to-one corresponding highway mobile payment request, the order number, the payment order number and the payment result data as payment record data.

[0075] The business libraries 51 in the two data centers 10 are used to synchronize the payment record data stored in each of the business libraries 51 to the summary library 52 in one of the data centers 10 based on a preset synchronization program.

[0076] Correspondingly, the summary library 52 in one of the data centers 10 is used to receive the payment record data sent by the business libraries 51 in the two data centers 10, store the payment record data as summary data, and periodically send the summary data to the summary library 52 in the other data center 10 for backup storage. In actual applications, in order to facilitate distinction, the summary library 52 in the other data center 10 can be called a summary backup library.

[0077] In order to further improve the efficiency and reliability of abnormal server processing, and thus ensure the real-time and reliability of payment, in a highway mobile payment active-active center system provided in an embodiment of the present application, see Figure 6 The highway mobile payment active-active center system specifically includes the following contents: Each of the data centers 10 is provided with a monitoring layer 6; the status monitoring result data includes: server status monitoring result data.

[0078] The monitoring layer 6 includes: a heartbeat service unit 61.

[0079] The heartbeat service unit 61 is respectively connected to the business layer 2 , the outbound layer 3 and the data layer 5 in the data center 10 where the heartbeat service unit 61 is located, and is also connected to the cache layer 1 .

[0080] The heartbeat service unit 61 is used to perform real-time status monitoring of each server in the business layer 2, the outbound layer 3 and the data layer 5 in the data center 10 where it is located, and send the corresponding server status monitoring result data to the cache layer 1 for storage.

[0081] The heartbeat service unit 61 is used to determine whether the data of each server currently in an available state in the data center 10 where it is located is less than a preset quantity threshold when the server status monitoring result data shows that the server is abnormal; if not, execute the preset abnormal recovery processing steps.

[0082] Among them, the abnormal recovery processing step specifically includes: sending an abnormal notification message containing the unique number corresponding to the server with the abnormality to an external removal platform, so that the removal platform performs service removal processing on the server specified in the abnormal notification message based on the unique number corresponding to the server in the received abnormal notification message and based on the preset automatic removal configuration information, and sends a corresponding removal notification message containing the unique number corresponding to the removed server to the heartbeat service unit 61.

[0083] The heartbeat service unit 61 is also used to send an exception recovery message with a unique number corresponding to the removed server to the cache layer 1 when receiving the removal notification message, so that the cache layer 1 updates the server status monitoring result data according to the exception recovery notification message.

[0084] In order to further improve the efficiency and reliability of network and database connection processing, and thus ensure the real-time and reliability of payment, in a highway mobile payment dual-active center system provided in an embodiment of the present application, see Figure 6 The highway mobile payment active-active center system specifically includes the following contents: The monitoring layer 6 further includes: a detection service unit 62; the status monitoring result data further includes: database connection status monitoring result data and external network connection status monitoring result data; The detection service unit 62 is respectively connected to the outbound layer 3 and the data layer 5 in the data center 10 where the detection service unit 62 is located, and the detection service unit 62 is also connected to the cache layer 1; The detection service unit 62 is used to perform real-time external network connection status monitoring on the outbound layer 3 in the data center 10 where the outbound layer 3 is located, and send the corresponding database connection status monitoring result data to the cache layer 1 for storage; The detection service unit 62 is used to perform real-time database connection status monitoring on the data layer 5 in the data center 10 where the detection service unit 62 is located, and send the corresponding external network connection status monitoring result data to the cache layer 1 for storage.

[0085] In order to determine whether the database connection and the network connection are abnormal through the detection service, if abnormal, the abnormal recovery processing steps are performed, in a highway mobile payment dual-active center system provided in an embodiment of the present application, the highway mobile payment dual-active center system specifically includes the following contents: The heartbeat service unit 61 is also used to obtain the database connection status monitoring result data and the external network connection status monitoring result data stored by the detection service unit 62 in the monitoring layer 6 where it is located from the cache layer 1 when it is determined that the data of each server currently in the available state in the data center 10 where it is located is less than a preset number threshold. If at least one of the database connection status monitoring result data and the external network connection status monitoring result data shows a connection abnormality, the abnormal recovery processing step is executed.

[0086] In order to further support the inquiry and refund of the clearing center 40, and thus ensure the real-time and reliability of payment, in a highway mobile payment dual-active center system provided in the embodiment of the present application, see Figure 8 The highway mobile payment active-active center system specifically includes the following contents: The data center 10 provided with the cache layer 1 is also used to receive a transaction query request from the clearing center 40 corresponding to the target area, and generate query result data corresponding to the transaction query request according to the summary data stored locally, and return the query result data to the clearing center 40; The data center 10 provided with the cache layer 1 is also used to receive a refund request from the clearing center 40, and perform business processing on the refund request according to its own servers and forward it to the external payment channel 30, so as to receive corresponding refund result data from the payment channel 30. If the refund result data shows that the refund is successful, the refund result data is sent to the clearing center 40.

[0087] It can be understood that the processing flow of processing refund requests in the highway mobile payment active-active center system is the same as that of processing highway mobile payment requests and the various functional modules involved. For details, please refer to the processing flow of processing different highway mobile payment requests received from the highway lane system 20 and the functional modules used, which will not be repeated here.

[0088] In addition, the processing of query requests in the highway mobile payment active-active center system requires the use of the front layer 4, business layer 2 and data layer 5 in the same data center 10. The routing service unit 41 in the front layer 4 forwards the query request to the business layer 2, so that the server in the business layer 2 extracts the unique identifier corresponding to the payment record data corresponding to the query request, and extracts the corresponding payment record data from the business library 51 or the summary library 52 in the data layer 5 based on the unique identifier, and returns the payment record data to the routing service unit 41 of the front layer 4. The routing service unit 41 of the front layer 4 then encodes and encrypts the payment record data and transmits it back to the clearing center 40, so that the clearing center 40 adopts a decoding and decryption algorithm corresponding to the rules or algorithms used for encoding and encryption by the routing service unit 41 of the front layer 4, and decodes and decrypts the received data packet to obtain the corresponding payment record data.

[0089] In order to further illustrate the above embodiment, the present application also provides a specific application example of a highway mobile payment dual-active center system, which is specifically described as follows: The mobile payment system is designed according to a single-center architecture. If the power supply, network, platform program, database, or hardware equipment of a single center fails, it will affect the network-wide availability of the front-end mobile payment function of the lane. As the proportion of mobile payment transactions increases year by year, mobile payment has become an important payment method for road networks. Front-end payment services require support for high concurrency, high availability, and 7×24-hour uninterrupted online services, and the requirements for the stability, risk resistance, and emergency support of related systems are getting higher and higher. According to the current operating status and business importance of the mobile payment system, this application example will optimize and upgrade the system to a dual-active center architecture to ensure the stability of the system operation and the continuity of the front-end business, and avoid the unavailability of the front-end mobile payment function due to single-point failures of the center-level system.

[0090] The dual mobile payment center is a second data center built in the same target area based on the existing first data center, ensuring that the normal use of mobile payment is not affected when a single center fails.

[0091] This application example mainly describes the construction and transformation of the software system under the dual-center mode. The goal is to build a highly stable and risk-resistant highway mobile payment dual-active system. Fig. 9 The highway mobile payment active-active system provided in the application example of this application can realize the mobile payment active-active center, so that the dual centers can process real-time transactions simultaneously; it can realize the dual-center data aggregation function and merge and aggregate the data of the dual centers; it has a high-availability routing system to realize the rapid distribution of transactions; it has a dual-center system monitoring system to monitor the dual-center status in real time and realize automatic switching.

[0092] The following is a description of the various functions that can be realized in the highway mobile payment dual-active center system designed in the application example of this application: (1) Front layer The front-end layer is deployed in the first data center and the second data center respectively, and can distribute the transactions requested by its own data center to the business layer of the first data center or the second data center according to certain routing rules. The functions implemented by the front-end layer include heartbeat monitoring and transaction forwarding. Specifically: Heartbeat monitoring: Monitor the dual-center status by obtaining the server status from the cache layer.

[0093] Transaction forwarding (i.e. routing service): Distribute the upstream requested transactions to the business layer of the corresponding center according to the routing rules. When a transaction fails in one data center, the front-end layer forwards the transaction to another data center.

[0094] It is understandable that the front-end layer can achieve load balancing and can collect statistics on indicators such as transaction duration, quantity, and success rate.

[0095] In one example, the setting parameters of the front-layer include: using the open source programming language Golang as the development language; using the cloud-native API gateway Apisix as load balancing; using the relational database management system MySQL to set the database of the front-layer, and using the remote dictionary service Redis to set the cache of the front-layer; using Docker containers for service deployment of the front-layer.

[0096] (2) Monitoring layer The monitoring layer is deployed in two data centers to monitor the server status of each center and the connection with the database or external network. The main functions of the monitoring layer are heartbeat service and detection service.

[0097] Heartbeat service: obtains the status of each server from the intelligent operation and maintenance platform, removes the machine when abnormality is detected, and sends the removal result to the cache layer. When the number of removals is less than the minimum number, it is necessary to use the detection service to determine whether the database connection and network connection are normal. Only when abnormality occurs can the removal continue.

[0098] Exploration service: obtain the connection status with the business library and the payment channel network. The connection conditions are consistent with the business module.

[0099] In one example, the setting parameters of the monitoring layer include: using Java (which can be modified on the original basis) as the development language; using the relational database management system MySQL to set the database of the monitoring layer, and using the remote dictionary service Redis to set the cache of the monitoring layer.

[0100] (3) Business layer The business layer can be optimized based on the existing model, with the main optimization points being unified order numbers and transaction logic optimization.

[0101] Unified order number: The order number sent by the system to the payment channel is changed from being generated by the system to being generated based on the merchant's order number and license plate number, ensuring that the same order corresponds to the payment channel one by one.

[0102] Transaction logic optimization: It can reduce unnecessary operations in the original center and shorten transaction response time.

[0103] In one example, the setting parameters of the business layer include: using Java as a development language; and using another relational database management system DB2 to set up a database of the business layer.

[0104] (4) Cache layer The cache layer caches information such as server status, allowing the two centers to share cache information.

[0105] Among them, see Fig.10, Redis is deployed in cluster mode and is called by other modules in the form of API.

[0106] In one example, the setting parameters of the front layer include: using the open source programming language Golang as the development language; and using the remote dictionary service Redis to set the cache of the cache layer.

[0107] (5) Data layer The data layer is divided into data storage and logic control. The data layer can achieve dual-center data independence and data backup.

[0108] The database construction adopts two pre-modes, namely, one summary mode and one backup mode. Fig.11 The front-end business database A stores the business data of the first data center, and the business database B stores the business data of the second data center. The synchronization program aggregates the data of the two centers into the aggregate database, and the aggregate database then synchronizes the data to the aggregate backup database.

[0109] The synchronization program synchronizes the data to the summary database regularly according to the update time, and registers the data of the two centers into the summary database after merging them.

[0110] In one example, the setting parameters of the data layer include: using Java as the development language; using another relational database management system DB2 to set the business library A, business library B, summary library and summary backup library of the data layer.

[0111] (6) External layer The outbound layer can solve the problem of agent instability. The original channel module is split, the transaction control is in the core area, and the channel outbound is in the isolation area (DMZ area).

[0112] In addition, based on the architecture of the above-mentioned highway mobile payment dual-active center system, this application example further provides the following optimizations: 1) Optimization of the scanned function The scanning function is optimized mainly from two aspects. One is that the payment mode is changed from synchronous to asynchronous. The other is the payment logic optimization to improve the TPS of the transaction.

[0113] Payment mode adjustment: adopt asynchronous mode, that is, when the channel payment is called for the first time, the payment system will directly return the payment result to the lane system. If it is in payment, the payment system will asynchronously query the payment result. After receiving the payment response, the lane determines the payment status. If it is in payment, it will initiate an active query to obtain the payment result. If it is other final states, it will be processed directly.

[0114] Business process optimization: Reduce module calls: merge processes that can be merged to avoid repeated calls.

[0115] Reduce unnecessary operations, such as product testing, merchant status checking, etc.

[0116] 2) Main scanning function optimization The existing model generates a static QR code for each lane, and the user scans the QR code, enters the amount and pays. The existing process cannot be bound to high-speed orders and has a low security factor.

[0117] This application example changes the main scan to a dynamic code method. The lane passes through the lane POS device to generate a QR code based on the order information. After the user scans the QR code, the order number, order amount and other information are displayed, and the payment method is selected. The main scan transaction is placed in the reconciliation file to be consistent with the scanned transaction.

[0118] 3) Added heartbeat detection function Added a new service heartbeat interface, which can obtain the service heartbeat status based on the server. Calling this interface can obtain whether the server and service are abnormal.

[0119] The heartbeat request parameter may be at least one of server IP, server status, service ID, service status, request time and the like.

[0120] In one example, the description of the heartbeat request parameters may be as shown in Table 1.

[0121] Table 1 In one example, the description of the corresponding parameters corresponding to the heartbeat request parameters can be shown in Table 2.

[0122] Table 2 4) Added automatic service removal function Mobile payment is deployed in clusters. The intelligent operation and maintenance platform monitors the clusters and notifies the operation and maintenance personnel of abnormal information via SMS. The operation and maintenance personnel need to manually remove the abnormal servers. This method takes a long time to repair the fault, so the automatic removal method is used to remove the abnormal services.

[0123] This application example builds a mobile payment monitoring and removal platform, which obtains monitoring information from the intelligent operation and maintenance platform, determines abnormal servers, and automatically removes them. The platform mainly implements the following functions: service monitoring and removal, server management, query, etc.

[0124] See also Fig.12 The system architecture of automatic service removal specifically includes the following contents: S1. The mobile payment system sends the transaction information to the intelligent operation and maintenance platform; S2. The operation and maintenance platform analyzes abnormal machines based on the information and registers them; S3. The monitoring system actively obtains abnormal machines from the operation and maintenance platform; S4, the monitoring system removes the server from the cluster according to the configuration information; S5. The monitoring system notifies the operation and maintenance personnel of abnormal information through text messages, internal communication software, etc.

[0125] 5) Added one-key restart function In order to ensure the stable operation of the mobile payment system, the server and services are restarted regularly every month. Currently, the operation and maintenance personnel need to manually log in to each machine to execute the restart script, which is a cumbersome and error-prone process. In order to solve this problem, a one-click restart function is designed. The one-click restart function is implemented using a continuous integration tool. It can be triggered by a trigger or started manually; then the mobile payment services are restarted in turn; and the execution results are notified to the operation and maintenance personnel.

[0126] 6) Added front-end routing module The front-end layer is deployed in two centers respectively, and can distribute the transactions requested by the first data center to the business layer of the corresponding center according to certain routing rules. The functions implemented by the front-end layer include heartbeat monitoring, transaction forwarding, recording interface success and failure / time consumption, etc.

[0127] 7) Add monitoring layer and cache layer The monitoring layer is deployed in two centers respectively. It monitors the server status of each center and the connection with the database or external network. The main functions of the monitoring layer are heartbeat service and detection service.

[0128] Heartbeat service: obtains the status of each server from the intelligent operation and maintenance platform, removes the machine when abnormality is detected, and sends the removal result to the cache layer. When the number of removals is less than the minimum number, it is necessary to use the detection service to determine whether the database connection and network connection are normal. Only when abnormality occurs can the removal continue.

[0129] Exploration service: obtain the connection status with the business database and payment channel network. The connection conditions are consistent with the business module.

[0130] The cache cluster can be deployed in cluster mode, with three masters and three slaves. The application uses two load balancing modes.

[0131] The application example of this application can also provide the monitoring layer with the function of updating the server status. When the monitoring layer monitors the server status change, it calls this interface to update.

[0132] The above interface can use the post method, which is an HTTP request method. Redis hash is used to store information, and the stored content can include server ID, server IP, server status, and data center ID. The corresponding request parameter description is shown in Table 3, and the response parameter is shown in Table 4.

[0133] Table 3 Table 4 Users can also obtain the status of all servers. The corresponding parameters for querying server status are shown in Table 5.

[0134] Table 5 Users can also obtain the number of servers in normal status in each data center. The specific process is as follows: Fig.13 The response parameters corresponding to the interface are shown in Table 6.

[0135] Table 6 8) Added data synchronization module The data of the two centers are independent. In order to realize data merging, a data synchronization module is developed. The central database stores the business data of each center. The synchronization program aggregates the data of the two centers into the summary library, and the summary library synchronizes the data to the summary backup library. The synchronization program synchronizes the data to the summary library regularly according to the update time, and merges the conflicting data of the two centers and registers them in the summary library.

[0136] Business data synchronization: The synchronization program reads business data regularly and writes it to the message queue; consumes data in the queue in real time and writes it to the summary library; when writing fails, the data is registered in the exception table.

[0137] Key information synchronization: When filling keys in existing devices, it involves two steps: obtaining the manufacturer key and obtaining the working key. Generally, key filling is performed in the first data center, and after the filling is completed, the program actively pushes it to the second data center for registration. Key filling refers to the process of importing the key file into the device.

[0138] 9) Added service outbound module The existing system uses a proxy to access the external network. In order to solve the problem of proxy instability, this application example builds a service outbound module to uniformly forward outbound transactions.

[0139] Transaction forwarding routing: Add a new forwarding interface, through which the business module calls the external payment channel for payment. The interface is designed with reference to the parameters provided by the payment channel.

[0140] Channel connection: The outbound module connects to various third-party payment platforms (such as WeChat, Alipay, and UnionPay, etc.) and selects the appropriate channel for payment based on the transaction channel code.

[0141] It is understandable that each server in the highway mobile payment active-active center system can also be set to be completed in the client device according to actual application requirements. The specific selection can be based on the processing power of the client device and the limitations of the user's usage scenario. This application is not limited to this. If all operations are completed in the client device, the client device may also include a processor for specific processing such as business processing, outbound processing, or data storage processing required in the highway mobile payment process.

[0142] The client device may have a communication module (i.e., a communication unit) that can communicate with a remote server to achieve data transmission with the server. The server may include a server on the task scheduling center side, and other implementation scenarios may also include a server on an intermediate platform, such as a server on a third-party server platform that has a communication link with the task scheduling center server. The server may include a single computer device, or a server cluster consisting of multiple servers, or a server structure of a distributed device.

[0143] The server and the client device may communicate with each other using any suitable network protocol, including network protocols that have not yet been developed on the date of filing this application. The network protocols may include, for example, TCP / IP, UDP / IP, HTTP, HTTPS, etc. Of course, the network protocols may also include, for example, RPC (Remote Procedure Call Protocol) and REST (Representational State Transfer) protocols used on top of the above protocols.

[0144] In one or more embodiments of the present application, the server used in the embodiments of the present application may include a processor, a memory, a receiver and a transmitter, and the processor is used to perform the business processing, outbound processing or data storage processing in the highway mobile payment process mentioned in the above embodiments, wherein the processor and the memory may be connected via a bus or other means, taking the bus connection as an example. The receiver may be connected to the processor and the memory via a wired or wireless manner.

[0145] The processor may be a central processing unit (CPU). The processor may also be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or a combination of the above chips.

[0146] As a non-volatile computer-readable storage medium, the memory can be used to store non-volatile software programs, non-volatile computer executable programs and modules. The processor executes various functional applications and data processing of the processor by running the non-volatile software programs, instructions and modules stored in the memory, that is, to realize the business processing, outbound processing or data storage processing in the highway mobile payment process in the above method embodiment.

[0147] The memory may include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application required for at least one function; the data storage area may store data created by the processor, etc. In addition, the memory may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other non-volatile solid-state storage device. In some embodiments, the memory may optionally include a memory remotely arranged relative to the processor, and these remote memories may be connected to the processor via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0148] It should be understood by those skilled in the art that the exemplary components, systems and methods described in conjunction with the embodiments disclosed herein can be implemented in hardware, software or a combination of the two. Whether it is performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application. When implemented in hardware, it can be, for example, an electronic circuit, an application-specific integrated circuit (ASIC), appropriate firmware, a plug-in, a function card, etc. When implemented in software, the elements of this application are programs or code segments used to perform the required tasks. The program or code segment can be stored in a machine-readable medium, or transmitted on a transmission medium or a communication link via a data signal carried in a carrier.

[0149] It should be clear that the present application is not limited to the specific configuration and processing described above and shown in the figures. For the sake of simplicity, a detailed description of the known method is omitted here. In the above embodiments, several specific steps are described and shown as examples. However, the method process of the present application is not limited to the specific steps described and shown, and those skilled in the art can make various changes, modifications and additions, or change the order between the steps after understanding the spirit of the present application.

[0150] In the present application, features described and / or illustrated for one embodiment may be used in the same manner or in a similar manner in one or more other embodiments, and / or combined with features of other embodiments or replace features of other embodiments.

[0151] The above description is only the preferred embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the embodiments of the present application may have various modifications and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included in the protection scope of the present application.

Claims

1. A highway mobile payment dual-active center system, characterized in that: include: Two simultaneously online data centers located in the same target area and communicating with each other; The two data centers are respectively used to receive different highway mobile payment requests from various highway lane systems in the target area, and each data center is used to perform business processing on the highway mobile payment requests received by itself according to various servers set up locally and forward them to external payment channels, so as to receive corresponding payment result data from the payment channel, and if the payment result data shows that the payment is successful, the payment result data is sent to the corresponding highway lane system; Each of the data centers stores summary data of itself and another data center, including the corresponding highway mobile payment request and the payment result data; A cache layer is provided in one of the data centers, which is used to store the status monitoring result data corresponding to each of the two data centers, so that when each data center determines that its current status is abnormal based on its own status monitoring result data stored in the cache layer, it can perform abnormal recovery processing or send its current highway mobile payment request received from the highway lane system to the other data center for processing.

2. The highway mobile payment dual-active center system according to claim 1 is characterized in that: A business layer is provided in each of the data centers; The business layer is used to perform business processing on the highway mobile payment requests received by itself according to the various servers set up locally, so as to convert the order number in the highway mobile payment request into a payment order number that complies with the preset order coding rules of the target payment channel according to the target payment channel specified by the highway mobile payment request, and transmit the highway mobile payment request and the corresponding payment order number internally in the data center where it is located.

3. The highway mobile payment dual-active center system according to claim 2 is characterized in that: Each of the data centers is also provided with an outbound layer; each of the outbound layers is connected to the business layer of the data center where it is located and to various external payment channels; The outbound layer is used to receive the highway mobile payment request and the corresponding payment order number transmitted by the business layer, and forward the highway mobile payment request and the payment order number to the target payment channel for payment based on the preset core transmission area according to the various servers set up locally, and receive the payment result data for the highway mobile payment request returned by the target payment channel based on the preset isolation area, wherein the core transmission area and the isolation area are different partitions formed by pre-splitting the various transmission channels.

4. The highway mobile payment dual-active center system according to claim 3 is characterized in that: A front layer is provided in each of the data centers; The front layer includes: a routing service unit; The routing service unit in each data center is respectively connected to each of the high-speed lane systems in the target area, the service layer in the data center where the routing service unit is located, the outbound layer in the data center where the routing service unit is located, and the service layer in another data center; The routing service unit is used to receive the highway mobile payment request sent by the highway lane system in the target area, and send the highway mobile payment request to the business layer in the data center where the routing service unit is located; The routing service unit is also used to perform the following: When or after the highway mobile payment request is sent to the business layer in the data center where the mobile payment request is located, asynchronously sending a response query request to the outbound layer in the data center where the mobile payment request is located; If the payment result data returned by the outgoing layer in the data center based on the response query request is received within a preset time period, the current payment status of the order corresponding to the highway mobile payment request shown in the payment result data is obtained; If the payment status is successful, forwarding the payment result data to the expressway lane system that issued the expressway mobile payment request; If the payment status is in payment, a response query request is sent again to the outbound layer in the data center where the device is located; If the payment status is payment failure, or if the payment result data returned by the outgoing layer in the data center based on the response query request is not received within a preset time period, the highway mobile payment request corresponding to the payment result data will be forwarded to the business layer in another data center for processing.

5. The highway mobile payment dual-active center system according to claim 4 is characterized in that: The front layer also includes: a heartbeat monitoring unit; The heartbeat monitoring unit is in communication connection with the cache layer and the routing service unit of the data center where the heartbeat monitoring unit is located; The heartbeat monitoring unit is used to obtain the current status monitoring result data of the data center where the heartbeat monitoring unit is located from the cache layer. If it is determined that the data center where the heartbeat monitoring unit is located currently has an abnormal status according to the status monitoring result data, a corresponding abnormal notification message is generated and sent to the routing service unit in the data center where the heartbeat monitoring unit is located. Correspondingly, the routing service unit is also used to forward the currently received highway mobile payment request to the business layer in another data center for processing when receiving an abnormal notification message sent by the heartbeat monitoring unit in the data center where it is located.

6. The highway mobile payment dual-active center system according to claim 5 is characterized in that: Each of said data centers is provided with a data layer; The database in the data layer includes: a business database and a summary database; The business library is respectively connected to the business layer and the outbound layer in the data center where the business library is located, and the business library is used to obtain the one-to-one corresponding highway mobile payment request, the order number, the payment order number and the payment result data from the business layer and the outbound layer in the data center where the business library is located, and store the one-to-one corresponding highway mobile payment request, the order number, the payment order number and the payment result data as payment record data; The business libraries in the two data centers are used to synchronize the payment record data stored in the business libraries to the summary library in one data center based on a preset synchronization program; Correspondingly, the summary library in one of the data centers is used to receive the payment record data sent by the business libraries in the two data centers, store the payment record data as summary data, and periodically send the summary data to the summary library in the other data center for backup storage.

7. The highway mobile payment dual-active center system according to claim 6 is characterized in that: Each of the data centers is provided with a monitoring layer; the status monitoring result data includes: server status monitoring result data; The monitoring layer includes: a heartbeat service unit; The heartbeat service unit is respectively connected to the business layer, the outbound layer and the data layer in the data center where the heartbeat service unit is located, and the heartbeat service unit is also connected to the cache layer; The heartbeat service unit is used to perform real-time status monitoring on each server in the business layer, outbound layer and data layer in the data center where the heartbeat service unit is located, and send the corresponding server status monitoring result data to the cache layer for storage; The heartbeat service unit is used to determine whether the data of each of the servers currently in the available state in the data center where the heartbeat service unit is located is less than a preset quantity threshold when the server status monitoring result data shows that the server is abnormal; if not, execute the preset abnormal recovery processing steps; The abnormal recovery process includes: Sending an exception notification message including the unique number corresponding to the server with the exception to an external removal platform, so that the removal platform performs service removal processing on the server specified in the exception notification message based on the unique number corresponding to the server in the received exception notification message and based on the preset automatic removal configuration information, and sending a corresponding removal notification message including the unique number corresponding to the removed server to the heartbeat service unit; The heartbeat service unit is also used to send an exception recovery message with a unique number corresponding to the removed server to the cache layer when receiving the removal notification message, so that the cache layer updates the server status monitoring result data according to the exception recovery notification message.

8. The highway mobile payment dual-active center system according to claim 7 is characterized in that: The monitoring layer further includes: a detection service unit; the status monitoring result data further includes: database connection status monitoring result data and external network connection status monitoring result data; The detection service unit is respectively connected to the outbound layer and the data layer in the data center where the detection service unit is located, and the detection service unit is also connected to the cache layer; The detection service unit is used to perform real-time external network connection status monitoring on the outbound layer in the data center where the detection service unit is located, and send the corresponding database connection status monitoring result data to the cache layer for storage; The detection service unit is used to perform real-time database connection status monitoring on the data layer in the data center where the detection service unit is located, and send the corresponding external network connection status monitoring result data to the cache layer for storage.

9. The highway mobile payment dual-active center system according to claim 8 is characterized in that: The heartbeat service unit is also used to obtain the database connection status monitoring result data and the external network connection status monitoring result data stored by the detection service unit in the monitoring layer where the heartbeat service unit is located from the cache layer when it is determined that the data of each server currently in an available state in the data center where the heartbeat service unit is located is less than a preset number threshold. If at least one of the database connection status monitoring result data and the external network connection status monitoring result data shows a connection abnormality, the abnormal recovery processing step is executed.

10. The highway mobile payment dual-active center system according to any one of claims 1 to 9, characterized in that: One of the data centers provided with the cache layer is further used to receive a transaction query request from a clearing center corresponding to the target area, and generate query result data corresponding to the transaction query request according to the summary data stored locally, and return the query result data to the clearing center; The data center equipped with the cache layer is also used to receive refund requests from the clearing center, and perform business processing on the refund requests according to its own servers and forward them to an external payment channel, so as to receive corresponding refund result data from the payment channel. If the refund result data shows that the refund is successful, the refund result data is sent to the clearing center.

Images