Highway Mobile Payment Dual-Active Center System

Abstract

The present application provides a dual-active center system for highway mobile payment, which relates to the technical field of computer systems. The system includes two data centers arranged in the target area. The two data centers are respectively used to receive different highway mobile payment requests from the highway lane system, perform service processing, and forward them to the payment channel for payment. They also store the summary data of themselves and the other data center. A cache layer is provided in one data center, which is used to store the status monitoring result data of the two data centers respectively, so that when each data center determines that its current state is abnormal according to the status monitoring result data, it can perform abnormal recovery processing or automatic switching between the two centers. The present application can enable the dual-active centers of mobile payment to simultaneously process real-time highway transactions, and can realize automatic switching between the two centers and improve the efficiency and reliability of data processing after switching, thereby improving the real-time performance and reliability of highway mobile payment.

Description

Technical Field

[0001] This application relates to the technical field of computer systems, and particularly to a dual-active center system for highway mobile payment. Background Art

[0002] Highway mobile payment refers to installing intelligent POS (Point of sales, multifunctional terminal) devices at highway exit toll stations to replace cash payment. Vehicle owners can complete the payment by selecting a third-party payment platform corresponding to a payment channel. In addition to installing intelligent POS devices in the lanes, a mobile payment system has also been built to implement functions such as transaction recording and payment processing. The specific payment process is as Figure 1 shown. The vehicle owner shows the payment code to the intelligent POS at the toll station, which calculates the fee and displays the amount, and then identifies the QR code to send the corresponding payment request to the mobile payment system. The system 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 intelligent POS to display a payment success message on the vehicle owner's mobile terminal and cause the toll station to raise the barrier for release, allowing the vehicle to leave the highway. As the proportion of mobile payment in highway payment increases, the requirements for the stability and reliability of highway mobile payment are also getting higher and higher. Currently, the highway mobile payment system adopts a single-center deployment architecture, and load balancing technology is used inside a single data center to achieve service distribution. The specific network architecture is as Figure 2 shown. The lane system, the mobile payment system, and the payment channel (i.e., the third-party payment platform) are sequentially communicatively connected. The mobile payment system includes a service cluster based on load balancing and a database system, and the service cluster includes multiple servers.

[0003] However, the traditional highway mobile payment system has problems such as poor stability and reliability, and cannot cope with problems such as central power failure and natural disasters. When problems occur in the central network or database, etc., the entire mobile payment system will crash, seriously affecting highway traffic. Summary of the Invention

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

[0005] One aspect of this application provides a dual-active center system for highway mobile payment, including: two simultaneously online data centers that are set in the same target area and are communicatively connected to each other;

[0006] 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 data center is used to process the highway mobile payment requests received by itself according to each server set locally and forward them to an external payment channel, so as to receive corresponding payment result data from the payment channel. If the payment result data shows successful payment, the payment result data will be sent to the corresponding highway lane system;

[0007] Each data center stores summary data of itself and the other data center, including the corresponding highway mobile payment requests and the payment result data;

[0008] 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 when each data center determines that its current state is abnormal according to its own status monitoring result data stored in the cache layer, it performs abnormal recovery processing or sends the highway mobile payment request currently received from the highway lane system to the other data center for processing.

[0009] In some embodiments of the present application, a service layer is provided in each data center;

[0010] The service layer is used to process the highway mobile payment requests received by itself according to each server set locally, so as to convert the order number in the highway mobile payment request into a payment order number that conforms to the preset order coding rule of the target payment channel according to the target payment channel specified in the highway mobile payment request, and perform internal transmission of the highway mobile payment request and the corresponding payment order number in the data center where it is located.

[0011] In some embodiments of the present application, an external sending layer is further provided in each data center; each external sending layer is communicatively connected between the service layer of the data center where it is located and each external payment channel;

[0012] The external sending layer is used to receive the highway mobile payment request and the corresponding payment order number transmitted by the service layer, and based on each server set locally, forward the highway mobile payment request and the payment order number to the target payment channel for payment based on a preset core transmission area, and receive the payment result data for the highway mobile payment request returned by the target payment channel based on a preset isolation area, where the core transmission area and the isolation area are different partitions formed by splitting each transmission channel in advance.

[0013] In some embodiments of the present application, a front-end layer is provided in each of the data centers;

[0014] The front-end layer includes: a routing service unit;

[0015] The routing service units in each of the data centers are respectively connected to each of the highway lane systems in the target area, the service layer in its own data center, the outbound layer in its own data center, and the service layer in the other data center;

[0016] The routing service unit is configured 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 service layer in its own data center;

[0017] The routing service unit is further configured to perform the following:

[0018] When or after sending the highway mobile payment request to the service layer in its own data center, asynchronously send a response query request to the outbound layer in its own data center;

[0019] If the payment result data returned by the outbound layer in its own data center based on the response query request is received within a preset time period, obtain the current payment status of the order corresponding to the highway mobile payment request shown in the payment result data;

[0020] If the payment status is payment success, forward the payment result data to the highway lane system that sent the highway mobile payment request;

[0021] If the payment status is in payment, send a response query request to the outbound layer in its own data center again;

[0022] If the payment status is payment failure, or if the payment result data returned by the outbound layer in its own data center based on the response query request is not received within a preset time period, forward the highway mobile payment request corresponding to the payment result data to the service layer in the other data center for processing.

[0023] In some embodiments of the present application, the front-end layer further includes: a heartbeat monitoring unit;

[0024] The heartbeat monitoring unit is communicatively connected between the cache layer and the routing service unit of its own data center;

[0025] The heartbeat monitoring unit is used to obtain the current status monitoring result data of the data center where it is located from the cache layer. If it is determined according to the status monitoring result data that there is an abnormal status in the data center where it is located, it generates a corresponding abnormal notification message and sends the abnormal notification message to the routing service unit in the data center where it is located;

[0026] Correspondingly, the routing service unit is further used to forward the currently received highway mobile payment request to the service layer in another data center for processing when receiving the abnormal notification message sent by the heartbeat monitoring unit in the data center where it is located.

[0027] In some embodiments of the present application, each data center is provided with a data layer;

[0028] The database in the data layer includes: a business database and a summary database;

[0029] The business database is communicatively connected between the service layer and the external sending layer in the data center where it is located. The business database is used to obtain the corresponding highway mobile payment request, order number, payment order number, and payment result data from the service layer and the external sending layer in the data center where it is located, and stores the corresponding highway mobile payment request, order number, payment order number, and payment result data as payment record data;

[0030] The business databases in the two data centers are both used to synchronize the respective payment record data stored by them to the summary database in one data center based on a preset synchronization program;

[0031] Correspondingly, the summary database in one data center is used to receive the respective payment record data sent by the business databases in the two data centers, store the respective payment record data as summary data, and periodically send the summary data to the summary database in another data center for backup storage.

[0032] In some embodiments of the present application, each data center is provided with a monitoring layer; the status monitoring result data includes: server status monitoring result data;

[0033] The monitoring layer includes: a heartbeat service unit;

[0034] The heartbeat service unit is communicatively connected between the service layer, the external sending layer, and the data layer in the data center where it is located, and the heartbeat service unit is also communicatively connected to the cache layer;

[0035] The heartbeat service unit is used to perform real-time status monitoring on each server in the service layer, the outbound layer, and the data layer within the data center where it is located, and send the corresponding server status monitoring result data to the cache layer for storage;

[0036] When the server status monitoring result data indicates that a server is abnormal, the heartbeat service unit is used to determine whether the data of each server that is currently in an available state within the data center where it is located is less than a preset quantity threshold; if not, it executes a preset abnormal recovery processing step;

[0037] Among them, the abnormal recovery processing step includes:

[0038] Sending an abnormal notification message containing the unique identifier corresponding to the server with an 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 identifier corresponding to the server in the received abnormal notification message according to preset automatic removal configuration information, and sends a removal notification message corresponding to the unique identifier of the removed server to the heartbeat service unit;

[0039] The heartbeat service unit is further used to, when receiving the removal notification message, send an abnormal recovery message for the unique identifier corresponding to the removed server to the cache layer, so that the cache layer updates the server status monitoring result data according to the abnormal recovery notification message.

[0040] In some embodiments of the present application, the monitoring layer further includes: a probing service unit; the status monitoring result data further includes: database connection status monitoring result data and external network connection status monitoring result data;

[0041] The probing service unit is communicatively connected between the outbound layer and the data layer within the data center where it is located, and the probing service unit is also communicatively connected to the cache layer;

[0042] The probing service unit is used to perform real-time external network connection status monitoring on the outbound layer within the data center where it is located, and send the corresponding database connection status monitoring result data to the cache layer for storage;

[0043] The probing service unit is used to perform real-time database connection status monitoring on the data layer within the data center where it is located, and send the corresponding external network connection status monitoring result data to the cache layer for storage.

[0044] In some embodiments of the present application, the heartbeat service unit is further configured to, when it is determined that the number of servers currently in an available state in the data center where it is located is less than a preset quantity threshold, obtain, from the cache layer, the database connection status monitoring result data and the external network connection status monitoring result data stored by the exploration service unit in the monitoring layer where it is located. If at least one of the database connection status monitoring result data and the external network connection status monitoring result data indicates an abnormal connection, the abnormal recovery processing step is executed.

[0045] In some embodiments of the present application, a data center provided with the cache layer is further configured to receive a transaction query request from the clearing center corresponding to the target area, 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;

[0046] A data center provided with the cache layer is further configured to receive a refund request from the clearing center, perform business processing on the refund request according to each of its servers, and forward it to an external payment channel, so as to receive corresponding refund result data from the payment channel. If the refund result data indicates a successful refund, the refund result data is sent to the clearing center.

[0047] The dual-active center system for highway mobile payment provided by this application includes two data centers that are set in the same target area and are communicatively connected to each other and are both online at the same time; 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 data center is used to process the highway mobile payment requests received by itself according to each server set locally and forward them to an external payment channel to receive corresponding payment result data from the payment channel. If the payment result data shows successful payment, the payment result data will be sent to the corresponding highway lane system; each data center stores the summary data of itself and the other data center, which includes the corresponding highway mobile payment requests and the payment result data; a cache layer is provided in one of the data centers, and this cache layer 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 state is abnormal according to its own status monitoring result data stored in this cache layer, it will perform abnormal recovery processing or send the highway mobile payment request currently received from the highway lane system to the other data center for processing. By processing orders with both centers online, it is possible to achieve simultaneous processing of real-time highway transactions by the dual-active centers for mobile payment, which can effectively meet the requirements of data synchronization real-time performance and stability in the highway mobile payment scenario; by sharing the summary data between the two centers, when switching between the two centers to transfer payment requests, the data center that takes over the payment requests can still process transactions quickly and normally, and only need to communicate with one of the data centers when the upper-level or management system obtains the payment data of the target area, thereby improving the convenience and efficiency of payment data management; by designing a cache layer for storing real-time status monitoring results, when the two centers determine that they are abnormal, they can quickly perform abnormal recovery or automatic switching between the two centers, which can achieve automatic switching between the two centers and improve the efficiency and reliability of data processing after switching, thereby improving the real-time performance and reliability of highway mobile payment; 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.

[0048] Additional advantages, objects, and features of this application will be partially described below and will become partially apparent to those of ordinary skill in the art after studying the following text, or may be learned from the practice of this application. The objects and other advantages of this application can be realized and obtained by the structure specifically pointed out in the specification and the drawings.

[0049] Those skilled in the art will understand that the objects and advantages that can be achieved by this application are not limited to the above specific descriptions, and the above and other objects that can be achieved by this application will be more clearly understood according to the following detailed description. Brief Description of the Drawings

[0050] The drawings described herein are provided to further understand the present application, form a part of the present application, and do not limit the present application. The components in the drawings are not drawn to scale, but are only for showing the principles of the present application. For the convenience of showing and describing some parts of the present application, the corresponding parts in the drawings may be enlarged, that is, may become larger relative to other components in the exemplary device actually manufactured according to the present application. In the drawings:

[0051] Figure 1 It is a schematic diagram of the high-speed mobile payment process.

[0052] Figure 2 It is a schematic diagram of the single-center deployment architecture.

[0053] Figure 3 It is a schematic diagram of the primary and standby dual-center mode.

[0054] Figure 4 It is a schematic diagram of the pseudo-dual-center mode.

[0055] Figure 5 It is a schematic diagram of the first architecture of the highway mobile payment dual-active center system in an embodiment of the present application.

[0056] Figure 6 It is a schematic diagram of the second architecture of the highway mobile payment dual-active center system in an embodiment of the present application.

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

[0058] Figure 8 It is a schematic diagram of the third architecture of the highway mobile payment dual-active center system in an embodiment of the present application.

[0059] Figure 9 It is a schematic diagram of the architecture of the highway mobile payment dual-active system provided by the application example of the present application.

[0060] Figure 10 It is a schematic diagram of the architecture for deploying Redis in a cluster mode and providing it for other modules to call in the form of an API in the application example of the present application.

[0061] Figure 11 It is a schematic diagram of the logical architecture of the data layer provided by the application example of the present application.

[0062] Figure 12 It is a schematic diagram of the execution logic of service automatic removal provided by the application example of the present application.

[0063] Figure 13Schematic diagram of the execution process for obtaining the number of servers in a normal state in each data center provided for the application example of this application.

[0064] Reference numerals:

[0065] 10. Data center;

[0066] 1. Cache layer;

[0067] 2. Business layer;

[0068] 3. Outgoing layer;

[0069] 4. Front-end layer;

[0070] 41. Routing service unit;

[0071] 42. Heartbeat monitoring unit;

[0072] 5. Data layer;

[0073] 51. Business database;

[0074] 52. Summary database;

[0075] 6. Monitoring layer;

[0076] 61. Heartbeat service unit;

[0077] 62. Exploration service unit;

[0078] 20. High-speed lane system;

[0079] 30. Payment channel;

[0080] 40. Clearing center. Detailed implementation manners

[0081] To make the objectives, technical solutions and advantages of this application more clear and understandable, the following further details this application in combination with the implementation manners and the drawings. Herein, the illustrative implementation manners of this application and their descriptions are used to explain this application, but do not limit this application.

[0082] Herein, it also needs to be noted that in order to avoid obscuring this application due to unnecessary details, only the structures and / or processing steps closely related to the solution of this application are shown in the drawings, while other details less related to this application are omitted.

[0083] It should be emphasized that the term "including / containing" 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.

[0084] Here, it should also be noted that, unless otherwise specified, the term "connection" in this text can not only refer to direct connection, but also indirect connection with intermediaries.

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

[0086] It should be noted that mobile payment refers to a digital payment method carried out through mobile devices (such as smart phones, smart POS machines). It uses wireless communication technology and mobile Internet to complete transactions. Consumers can transfer funds from their bank accounts or other payment accounts to the merchant's account through mobile payment applications or other related technologies to complete the payment behavior. And the scanned payment is a mobile payment method, also known as the collection code payment. The merchant scans the QR code generated by the user's virtual wallet, etc. to complete the payment.

[0087] Load balancing is a network technology that distributes network traffic to multiple servers to improve system performance, increase availability and fault tolerance. Simply put, it is to disperse requests to multiple servers for processing to avoid system paralysis or slow response speed caused by overloading a single server. Load balancing can be achieved at different levels, such as hardware load balancers, software load balancers, etc. Common load balancing algorithms include round-robin, least connections, IP hashing, etc. Load balancing is very common in Internet applications, especially for high-concurrency websites or applications, and it is one of the essential technical means.

[0088] In order to solve the problems existing in the solution of highway mobile payment with a single data center, such as poor stability and reliability, inability to cope with central power outages and natural disasters, and the entire mobile payment system will crash when problems occur in the central network or database, etc., the designer of the present application first considered applying the dual-center of the pseudo-dual-center or primary-backup dual-center mode commonly used in cloud computing and large enterprise systems to the highway mobile payment scenario. The dual-center means that within the same geographical area, two or more data centers are established, and application programs and data are deployed to these data centers at the same time. These data centers are connected by a high-speed network and each undertakes a certain traffic load to improve the availability, fault tolerance and disaster recovery ability of the application program. 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 among data centers. In cloud computing and large enterprise systems, dual-center deployment has become a common solution to provide higher reliability and availability.

[0089] Among them, in the primary and standby dual - center mode, the primary center undertakes the core business, and the standby center does not perform real - time services. It backs up the data of the primary center and simultaneously processes some query services. The specific mode is as follows Figure 3 shown. The lane system only communicates with the primary data center (i.e., Figure 3 "Mobile Payment System - Primary" in Figure 3 ), and the management system only communicates with the backup data center (i.e.,

[0090] "Mobile Payment System - Standby" in Figure 4 ). Both the primary data center and the backup data center are equipped with 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 primary data center is abnormal or fails, it is necessary to start the backup data center and synchronize the data of the primary center to the backup center, which will lead to low efficiency and poor reliability in the process of highway mobile payment processing.

[0091] In the pseudo - dual - center mode, the two data centers use different links and payment channels, and the two data centers are completely independent. The specific mode is as follows Figure 4 shown. The lane system communicates and connects with a mobile payment system and a third - party system that use different links and payment channels respectively. The third - party payment system contains a payment service, a database, and a payment channel that are sequentially communicatively connected. However, the maintainability of this method is poor, and the maintenance cost of different dual - center modes is high; moreover, the upgrade difficulty is high, that is, a large number of transformations need to be carried out on the original system, and smooth upgrade cannot be achieved.

[0091] As can be seen from the above, both the primary and 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 this application designs a dual - active center, that is, two data centers using the same link and payment channel simultaneously provide highway mobile payment services. At this time, it is necessary to face technical difficulties such as high requirements for data synchronization real - time performance and stability. Based on this, the embodiments of this application provide a highway mobile payment dual - active center system, which transforms the mobile payment system into a dual - active center, upgrades the system to a highly reliable system, makes it general - purpose and can overcome technical difficulties such as high requirements for data synchronization real - time performance and stability, and can be applied to different high - speed mobile payment systems. Without invading the source system, the dual - center transformation of the system is realized.

[0092] Specifically, it is described in detail through the following embodiments.

[0093] Based on this, the embodiments of this application provide a highway mobile payment dual - active center system. Refer to Figure 5 , the highway mobile payment dual - active center system specifically includes the following content:

[0094] Two data centers 10 that are set in the same target area and are communicatively connected to each other and are both online at the same time.

[0095] In one or more embodiments of the present application, the target area refers to a geographical area range that can be preset artificially. For example, it can be divided with reference to cities, administrative regions, etc. The term "online" means being in a state where it can be accessed and communicate through an Internet connection. In this state, the data center 10 can access the Internet or communicate with other online devices.

[0096] 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 process the highway mobile payment requests received by itself according to each server set locally and forward them to an external payment channel 30, so as to receive corresponding payment result data from the payment channel 30. If the payment result data shows successful payment, the payment result data will be sent to the corresponding highway lane system 20.

[0097] It can be understood that the highway mobile payment request should at least include an order number, a unique identifier of a specified third-party payment platform, and a payment amount calculated by the highway lane system 20. It may also include other data required for highway mobile payment, such as a unique identifier of a vehicle and a unique identifier of the highway lane system 20.

[0098] In one or more embodiments of the present application, the highway lane system 20 refers to terminal equipment installed at the toll station of the highway exit lane, which can be simply referred to as the lane system. For example, the highway lane system 20 can adopt an intelligent POS device.

[0099] Each data center 10 stores summary data of itself and the other data center 10, which includes the corresponding highway mobile payment request and the payment result data.

[0100] A cache layer 1 is provided in one data center 10. The cache layer 1 is used to store the status monitoring result data corresponding to the two data centers 10 respectively, so that when each data center 10 determines that its current state is abnormal according to its own status monitoring result data stored in the cache layer 1, it will perform abnormal recovery processing or send the highway mobile payment request currently received from the highway lane system 20 to the other data center 10 for processing.

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

[0102] It can be understood that the state monitoring result data refers to the monitoring result data of the corresponding server status (such as whether the server is running normally and whether it is communicating normally with other modules or other databases), database connection status (such as whether the database is communicating normally with other modules or other databases), and external network connection status (such as whether it is communicating normally with an external third-party payment platform), etc. of the data center 10. The normal operation here means that the server can process the received highway mobile payment request based on a preset business processing rule. The normal communication can refer to the ability to establish an information transmission (transfer) channel (channel) between the source (beginning end) and the destination (ending end) according to a consistent transmission protocol to transfer information.

[0103] As can be seen from the above description, in the highway mobile payment dual-active center system provided by the embodiment of the present application, by processing orders online in both centers, it can realize the simultaneous processing of highway real-time transactions by the mobile payment dual-active centers, and can effectively meet the requirements of the highway mobile payment scenario for data synchronization real-time performance and stability; by sharing the summary data in both centers, when switching between the two centers for payment request transfer, the data center 10 that takes over the payment request can still process transactions 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 the cache layer 1 for storing real-time status monitoring results, when both centers determine that there is an abnormality, they can quickly perform abnormal recovery or automatic switching between the two centers, and can realize the automatic switching between the two centers and improve the efficiency and reliability of data processing after switching, thereby improving the real-time performance and reliability of highway mobile payment; at the same time, using two data centers 10 with the same architecture can effectively reduce the maintenance cost and upgrade difficulty of the two data centers 10.

[0104] In order to further improve the efficiency and reliability of highway mobile payment, in a highway mobile payment dual-active center system provided by the embodiment of the present application, refer to Figure 6 , the highway mobile payment dual-active center system specifically includes the following content:

[0105] A service layer 2 is provided in each of the data centers 10.

[0106] The service layer 2 is used to process the highway mobile payment requests received by itself according to each server set locally, so as to convert the order number in the highway mobile payment request into a payment order number that conforms to the preset order coding rule of the target payment channel 30 according to the target payment channel 30 specified in the highway mobile payment request, and perform internal transmission of the highway mobile payment request and the corresponding payment order number in the data center 10 where it is located.

[0107] It can be understood 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 specify one payment channel 30 designated by the vehicle owner's mobile device as the target payment channel 30.

[0108] In order to further improve the reliability of the payment request outgoing 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 dual-active center system specifically includes the following contents:

[0109] An outgoing layer 3 is also provided in each data center 10; each outgoing layer 3 is communicatively connected to the service layer 2 of the data center 10 where it is located and each external payment channel 30.

[0110] The outgoing layer 3 is used to receive the highway mobile payment request and the corresponding payment order number transmitted by the service layer 2, and based on each server set locally, forward the highway mobile payment request and the payment order number to the target payment channel 30 for payment based on a preset core transmission area, and receive, based on a preset isolation area, the payment result data returned by the target payment channel 30 for the highway mobile payment request, where the core transmission area and the isolation area are different partitions formed by splitting each transmission channel in advance.

[0111] In order to implement 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 dual-active center system specifically includes the following contents:

[0112] A front-end layer 4 is provided in each data center 10.

[0113] The front-end layer 4 includes: a routing service unit 41.

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

[0115] The routing service unit 41 is configured to receive the highway mobile payment request sent by the high-speed lane system 20 in the target area, and send the highway mobile payment request to the service layer 2 within its own data center 10.

[0116] See Figure 7 , the routing service unit 41 is further configured to execute the following asynchronous query process:

[0117] Step 110: Asynchronously send a response query request to the outbound layer within its own data center when or after sending the highway mobile payment request to the service layer within its own data center.

[0118] Step 120: If the payment result data returned by the outbound layer within its own data center based on the response query request is received within a preset time period, obtain the current payment status of the order corresponding to the highway mobile payment request displayed by the payment result data, and then select one of Steps 140 to 160 to execute according to the payment status.

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

[0120] Step 140: If the payment status is payment successful, forward the payment result data to the high-speed lane system that sent the highway mobile payment request.

[0121] Step 150: If the payment status is in payment, send a response query request to the outbound layer within its own data center again.

[0122] Step 160: If the payment status is payment failed, forward the highway mobile payment request corresponding to the payment result data to the service layer in another data center for processing.

[0123] In order to further improve the timeliness of dual - center automatic switching, and thus ensure the real - time and reliability of payment, in a dual - active center system for highway mobile payment provided by an embodiment of the present application, refer to Figure 6 The dual - active center system for highway mobile payment specifically includes the following content:

[0124] The front - end layer 4 further includes: a heartbeat monitoring unit 42.

[0125] The heartbeat monitoring unit 42 is communicatively connected between the cache layer 1 and the routing service unit 41 of its own data center 10.

[0126] The heartbeat monitoring unit 42 is used to obtain the current status monitoring result data of its own data center 10 from the cache layer 1. If it is determined according to the status monitoring result data that there is an abnormal status in its own data center 10 currently, it generates a corresponding abnormal notification message and sends the abnormal notification message to the routing service unit 41 within its own data center 10.

[0127] Correspondingly, the routing service unit 41 is further used to forward the currently received highway mobile payment request to the service layer 2 in the other data center 10 for processing when receiving the abnormal notification message sent by the heartbeat monitoring unit 42 within its own data center 10.

[0128] In order to further ensure that transactions can still be processed normally during transaction transfer and improve the convenience and efficiency of the upper - level system to obtain data in the same area, in a dual - active center system for highway mobile payment provided by an embodiment of the present application, refer to Figure 6 The dual - active center system for highway mobile payment specifically includes the following content:

[0129] Each data center 10 is provided with a data layer 5.

[0130] The databases in the data layer 5 include: a business database 51 and a summary database 52.

[0131] The business database 51 is communicatively connected between the service layer 2 and the external - sending layer 3 within its own data center 10 respectively. The business database 51 is used to obtain the corresponding highway mobile payment request, order number, payment order number, and payment result data from the service layer 2 and the external - sending layer 3 within its own data center 10, and store the corresponding highway mobile payment request, order number, payment order number, and payment result data as payment record data.

[0132] The business databases 51 in both of the data centers 10 are used to synchronize each of the payment record data stored therein to the summary database 52 in one of the data centers 10 based on a preset synchronization program.

[0133] Correspondingly, the summary database 52 in one of the data centers 10 is used to receive each of the payment record data sent by the business databases 51 in both of the data centers 10, store each of the payment record data as summary data, and periodically send the summary data to the summary database 52 in the other data center 10 for backup storage. In practical applications, for the convenience of distinction, the summary database 52 in the other data center 10 can be referred to as the summary backup database.

[0134] In order to further improve the efficiency and reliability of abnormal server processing, and thus ensure the real-time performance and reliability of payments, in a highway mobile payment dual-active center system provided in an embodiment of the present application, refer to Figure 6 , the highway mobile payment dual-active center system specifically includes the following content:

[0135] Each of the data centers 10 is provided with a monitoring layer 6; the status monitoring result data includes: server status monitoring result data.

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

[0137] The heartbeat service unit 61 is respectively communicatively connected to the service layer 2, the external sending layer 3, and the data layer 5 in the data center 10 where it is located, and the heartbeat service unit 61 is also communicatively connected to the cache layer 1.

[0138] The heartbeat service unit 61 is used to perform real-time status monitoring on each server in the service layer 2, the external sending 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.

[0139] The heartbeat service unit 61 is used to determine whether the data of each server that is 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 indicates that a server has an abnormality; if not, then execute a preset abnormal recovery processing step.

[0140] Among them, the abnormal recovery processing steps specifically include: sending an abnormal notification message containing the unique number corresponding to the server with an 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 according to preset automatic removal configuration information, and sending a corresponding removal notification message containing the unique number corresponding to the removed server to the heartbeat service unit 61.

[0141] The heartbeat service unit 61 is further configured to send an abnormal recovery message for the 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 abnormal recovery notification message.

[0142] In order to further improve the efficiency and reliability of network and database connection processing, and thus ensure payment real-time performance and reliability, in a highway mobile payment dual-active center system provided in an embodiment of the present application, see Figure 6 , the highway mobile payment dual-active center system specifically includes the following content:

[0143] The monitoring layer 6 further includes: a probing service unit 62; the status monitoring result data further includes: database connection status monitoring result data and external network connection status monitoring result data;

[0144] The probing service unit 62 is respectively communicatively connected to the external sending layer 3 and the data layer 5 within the data center 10 where it is located, and the probing service unit 62 is also communicatively connected to the cache layer 1;

[0145] The probing service unit 62 is configured to perform real-time external network connection status monitoring on the external sending layer 3 within the data center 10 where it is located, and send the corresponding database connection status monitoring result data to the cache layer 1 for storage;

[0146] The probing service unit 62 is configured to perform real-time database connection status monitoring on the data layer 5 within the data center 10 where it is located, and send the corresponding external network connection status monitoring result data to the cache layer 1 for storage.

[0147] In order to determine whether the database connection and network connection are abnormal through the probing service, and if so, execute the abnormal recovery processing steps, 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 content:

[0148] The heartbeat service unit 61 is further configured to, when it is determined that 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, obtain from the cache layer 1 the database connection status monitoring result data and the external network connection status monitoring result data stored by the exploration service unit 62 in the monitoring layer 6 where it is located. If at least one of the database connection status monitoring result data and the external network connection status monitoring result data indicates an abnormal connection, the abnormal recovery processing step is executed.

[0149] To further support the query and refund of the clearing center 40, and thus ensure the real-time performance and reliability of payment, in a highway mobile payment dual-active center system provided in an embodiment of the present application, see Figure 8 , the highway mobile payment dual-active center system specifically includes the following:

[0150] One data center 10 provided with the cache layer 1 is further configured to receive a transaction query request from the clearing center 40 corresponding to the target area, 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;

[0151] One data center 10 provided with the cache layer 1 is further configured to receive a refund request from the clearing center 40, perform business processing on the refund request according to each of its 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 indicates a successful refund, the refund result data is sent to the clearing center 40.

[0152] It can be understood that the processing flow of the refund request and the processing flow of the highway mobile payment request in the highway mobile payment dual-active center system, as well as the involved functional modules, are the same. Specifically, reference can be made to the processing flow of receiving different highway mobile payment requests from the highway lane system 20 and the functional modules used, which will not be elaborated herein.

[0153] In addition, when processing query requests in the highway mobile payment dual-active center system, the front-end layer 4, business layer 2, and data layer 5 in the same data center 10 are required. The routing service unit 41 in the front-end 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 of the query request, and based on this unique identifier, extracts the corresponding payment record data from the business database 51 or summary database 52 in the data layer 5, and returns the payment record data to the routing service unit 41 of the front-end layer 4. The routing service unit 41 of the front-end layer 4 then encodes and encrypts the payment record data and sends it back to the clearing center 40, so that the clearing center 40 uses a decoding and decryption algorithm corresponding to the rule or algorithm used for encoding and encrypting by the routing service unit 41 of the front-end layer 4 to decode and decrypt the received data packet to obtain the corresponding payment record data.

[0154] To further illustrate the above embodiments, the present application also provides a specific application example of the highway mobile payment dual-active center system, which is specifically described as follows:

[0155] If the system design of the mobile payment system is based on a single-center architecture, if a failure occurs in the power supply, network, platform program, database, or hardware device of the single center, it will affect the network-wide availability of the mobile payment function at the lane front end. As the proportion of mobile payment transactions increases year by year, mobile payment has become an important payment method for the road network. The front-end payment service requires support for high concurrency, high availability, and 7×24-hour uninterrupted online service, and the requirements for the stability, risk resistance, and emergency guarantee of related systems are getting higher and higher. According to the operation status and business importance of the mobile payment system, the application example of the present application optimizes and upgrades the system to a dual-active center architecture to ensure the stability of system operation and the continuity of front-end services, and to avoid the situation where the front-end mobile payment function cannot be used due to a single-point failure of the center-level system.

[0156] The mobile payment dual center is based on the existing first data center to build a second data in the same target area to ensure that the normal use of mobile payment is not affected in case of a single-center failure.

[0157] The application example of the present application mainly describes the construction and transformation of the software system in the dual-center mode. The goal is to build a highly stable and risk-resistant highway mobile payment dual-active system. Refer to Figure 9 , the highway mobile payment dual-active system provided by the application example of the present application can realize the mobile payment dual-active center, enabling the dual centers to process real-time transactions simultaneously; it can realize the dual-center data aggregation function to merge and aggregate the data of the dual centers; it is equipped with a highly available routing system to achieve fast distribution of transactions; it is equipped with a dual-center system monitoring system to monitor the status of the dual centers in real time and can achieve automatic switching.

[0158] The following describes each function that can be implemented in the highway mobile payment dual-active center system designed in the application example of the present application:

[0159] (1) Front-end layer

[0160] The front-end layer is deployed in the first data center and the second data center respectively, and can distribute the transactions requested by the data center where it is located 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:

[0161] Heartbeat monitoring: Monitor the status of the dual centers by obtaining the server status from the cache layer.

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

[0163] It can be understood that the front-end layer can achieve load balancing and can count indicators such as the time-consuming, quantity, and success rate of transactions.

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

[0165] (2) Monitoring layer

[0166] The monitoring layer is deployed in the two data centers respectively, and is used to monitor the server status of each center and the connection with the database or external network. The main functions of the monitoring layer include heartbeat service and probing service.

[0167] Heartbeat service: Obtain the status of each server from the intelligent operation and maintenance platform, remove the machine when an abnormality is detected, and send the removal result to the cache layer. When the number of removals is less than the minimum number, it is necessary to judge whether the database connection and network connection are normal through the probing service, and only when it is abnormal can the removal continue.

[0168] Probing service: Obtain the connection with the business database and the network connection of the payment channel, and the connection conditions are consistent with the business module.

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

[0170] (3) Business layer

[0171] The business layer can be optimized on the existing mode, and the main optimization points are the unified order number and the optimization of the transaction logic.

[0172] 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 order number and the license plate number, ensuring that the same order corresponds one-to-one with the payment channel.

[0173] Optimization of transaction logic: It can reduce unnecessary operations in the original center and reduce the transaction response time.

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

[0175] (4) Cache layer

[0176] The cache layer realizes the caching of information such as the server status, enabling the sharing of cache information between the two centers.

[0177] Among them, see Figure 10 , deploy Redis in a cluster mode and provide it for other modules to call in the way of API.

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

[0179] (5) Data layer

[0180] The data layer is divided into data storage and logic control. The data layer can realize the independence and backup of data in the two centers.

[0181] The database construction adopts a two-front-end mode, that is, a summary and a backup mode. See Figure 11 , the front-end business library A stores the business data of the first data center, and the business library B stores the business data of the second data center. The synchronization program summarizes the data of the two centers into the summary library, and the summary library then synchronizes the data to the summary backup library.

[0182] The synchronization program regularly synchronizes the data to the summary library according to the update time, and merges the data of the two centers and registers it in the summary library.

[0183] 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 up business libraries A and B, summary library, and summary backup library of the data layer.

[0184] (6)Outbound layer

[0185] The outbound layer can solve the problem of unstable proxy. The original channel module is split, and transactions are controlled in the core area, while channel outbound is in the isolation area (i.e., the DMZ area).

[0186] In addition, based on the architecture of the above-mentioned dual-active center system for highway mobile payment, the application example of this application further provides the following optimizations:

[0187] 1) Optimization of the scanned function

[0188] The scanned function is mainly optimized from two aspects. One is to change the payment from synchronous mode to asynchronous mode, and the other is to optimize the payment logic to improve the TPS of transactions.

[0189] Adjustment of payment mode: Adopt the asynchronous method. That is, when the channel payment is called for the first time, the payment system directly returns the payment result to the lane system. If the payment is in progress, the payment system will asynchronously query the payment result. After receiving the payment response, the lane judges the payment status. If the payment is in progress, it initiates an active query to obtain the payment result. If it is in other final states, it directly proceeds with the processing.

[0190] Optimization of business process:

[0191] Reduce module calls: Merge the processes that can be combined to avoid repeated calls.

[0192] Reduce unnecessary operations, such as product detection, merchant status check, etc.

[0193] 2) Optimization of the main-scanned function

[0194] The existing mode generates a static QR code for each lane. The user scans the QR code, enters the amount, and makes a payment. The existing process cannot be bound to the highway order, and the security factor is low.

[0195] The application example of this application changes the main-scanned mode to the dynamic code method. The lane generates a QR code according to the order information through the lane pos device. After the user scans the QR code, information such as the order number and order amount is displayed, and the user selects a payment method to make a payment. The main-scanned transaction is put into the reconciliation file to be consistent with the scanned.

[0196] 3) Add heartbeat detection function

[0197] Add a service heartbeat interface. The added service heartbeat interface can obtain the service heartbeat status according to the server. Invoking this interface can obtain whether the server and the service are abnormal.

[0198] The heartbeat request parameters can include at least one of the following information: server IP, server status, service ID, service status, and request time.

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

[0200] Table 1

[0201]

[0202] In one example, the description of the corresponding parameters for the heartbeat request parameters can be as shown in Table 2.

[0203] Table 2

[0204]

[0205] 4) New function of automatically removing services

[0206] Mobile payment is deployed in a cluster mode. The intelligent operation and maintenance platform monitors the cluster and notifies the operation and maintenance personnel of the abnormal information via SMS. The operation and maintenance personnel need to manually remove the abnormal server. This method has a long fault repair time, so an automatic removal method is adopted to remove the abnormal service.

[0207] The application example of this application builds a mobile payment monitoring and removal platform. By obtaining the monitoring information of the intelligent operation and maintenance platform, it judges the abnormal servers and realizes automatic removal. The main functions of this platform include: service monitoring and removal, server management, query and other functions.

[0208] See Figure 12 , the system architecture of service automatic removal specifically includes the following content:

[0209] S1. The mobile payment system sends the transaction information to the intelligent operation and maintenance platform;

[0210] S2. The operation and maintenance platform analyzes the abnormal machines according to the information and registers them;

[0211] S3. The monitoring system actively obtains the abnormal machines from the operation and maintenance platform;

[0212] S4. The monitoring system removes the server from the cluster according to the configuration information;

[0213] S5. The monitoring system notifies the operation and maintenance personnel of the abnormal information via SMS, internal communication software, etc.

[0214] 5) New function of one-key restart

[0215] 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 process and prone to errors. To solve this problem, a one-key restart function is designed. The one-key restart function is implemented using a continuous integration tool. Specifically, it can be triggered by a trigger or manually started; then the mobile payment service is restarted in sequence; and the execution result is notified to the operation and maintenance personnel.

[0216] 6) Add a front-end routing module

[0217] 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 the success / failure / time consumption of interfaces, etc.

[0218] 7) Add a monitoring layer and a cache layer

[0219] 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 include heartbeat service and probing service.

[0220] Heartbeat service: Obtain the status of each server from the intelligent operation and maintenance platform, remove the machine when an abnormality is detected, and send the removal result to the cache layer. When the number of removed machines is less than the minimum number, it is necessary to use the probing service to judge whether the database connection and network connection are normal, and continue to remove only when there is an abnormality.

[0221] Probing service: Obtain the connection with the business database and the payment channel network connection status, and the connection conditions are consistent with the business module.

[0222] The cache cluster can be deployed in a cluster mode, with three masters and three slaves. The application adopts a two-load-balancing mode.

[0223] The application instance of this application can also provide a function to update the server status for the monitoring layer. When the monitoring layer monitors a change in the server status, it calls this interface to update.

[0224] The above interface can use the post method. The POST method is an HTTP request method. The Redis hash is used to store information, and the stored content can include server ID, server IP, server status, and data center ID, etc. Descriptions of the corresponding request parameters are shown in Table 3 for example, and the response parameters are shown in Table 4.

[0225] Table 3

[0226]

[0227] Table 4

[0228]

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

[0230] Table 5

[0231]

[0232] Users can also obtain the number of servers in the normal state in each data center. The specific process is as Figure 13 shown, and the corresponding response parameters of the interface are shown in Table 6.

[0233] Table 6

[0234]

[0235] 8) New data synchronization module

[0236] The data of the two centers are independent. To achieve data merging, a data synchronization module is developed. The central database stores the business data of their respective centers. The synchronization program aggregates the data of the two centers into the summary database, and the summary database then synchronizes the data to the summary backup database. The synchronization program regularly synchronizes the data to the summary database according to the update time, and merges the conflicting data of the two centers and registers them in the summary database.

[0237] Business data synchronization: The synchronization program periodically reads business data and writes it into the message queue; it consumes the data in the queue in real time and writes it into the summary database; when the writing fails, the data is registered in the exception table.

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

[0239] 9) New service outsourcing module

[0240] The existing system accesses the external network through the proxy method. To solve the problem of unstable proxy, the application instance of this application builds a service outsourcing module to uniformly forward the outsourcing transactions.

[0241] Transaction forwarding routing: A new forwarding interface is added, and the business module calls the external payment channel for payment through this interface. The interface is designed with reference to the parameters provided by the payment channel.

[0242] Channel docking: The outsourcing module realizes the docking with multiple third-party payment platforms (such as WeChat, Alipay, and UnionPay, etc.). Select the appropriate channel for payment according to the channel code of the transaction.

[0243] It can be understood that each server in the highway mobile payment dual-active center system can also be set to be completed in the client device according to actual application requirements. Specifically, it can be selected according to the processing capacity of the client device and the limitations of the user usage scenario, etc. This application does not make any limitations in this regard. If all operations are completed in the client device, the client device may further include a processor for performing specific processing such as service processing, external processing, or data storage processing required during the highway mobile payment process.

[0244] The above-mentioned client device may have a communication module (i.e., communication unit), which 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 in other implementation scenarios, it may also include a server of an intermediate platform, such as a server of a third-party server platform having a communication link with the task scheduling center server. The server may include a single computer device, or may include a server cluster composed of multiple servers, or a server structure of a distributed device.

[0245] Any suitable network protocol can be used for communication between the above-mentioned server and the client device, including network protocols that have not been developed as of the filing date of this application. The network protocol may, for example, include TCP / IP protocol, UDP / IP protocol, HTTP protocol, HTTPS protocol, etc. Of course, the network protocol may also, for example, include RPC protocol (Remote Procedure Call Protocol) and REST protocol (Representational State Transfer) used on top of the above-mentioned protocols.

[0246] In one or more embodiments of this application, the server adopted in the embodiments of this application may include a processor, a memory, a receiver, and a transmitter. The processor is used to execute the service processing, external processing, or data storage processing, etc. mentioned in the above embodiments during the highway mobile payment process. Among them, the processor and the memory may be connected through a bus or other means. Taking the connection through the bus as an example, the receiver can be connected to the processor and the memory in a wired or wireless manner.

[0247] The processor may be a Central Processing Unit (CPU). The processor may also be other general-purpose processors, Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Field-Programmable Gate Arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc., such as chips, or combinations of the above types of chips.

[0248] As a non-transitory computer-readable storage medium, the memory can be used to store non-transitory software programs, non-transitory computer-executable programs, and modules. The processor executes various functional applications and data processing of the processor by running the non-transitory software programs, instructions, and modules stored in the memory, that is, to implement the service processing, external processing, or data storage processing, etc. in the highway mobile payment process in the above method embodiments.

[0249] The memory may include a program storage area and a data storage area. Among them, the program storage area can store an operating system and application programs required for at least one function; the data storage area can store data created by the processor, etc. In addition, the memory may include high-speed random access memory, and may also include non-transitory memory, such as at least one magnetic disk storage device, a flash memory device, or other non-transitory solid-state storage devices. In some embodiments, the memory may optionally include a memory remotely provided with respect to the processor, and these remote memories can be connected to the processor through a network. Examples of the above networks include but are not limited to the Internet, enterprise intranets, local area networks, mobile communication networks, and combinations thereof.

[0250] Those of ordinary skill in the art should understand that the various exemplary components, systems, and methods described in conjunction with the embodiments disclosed herein can be implemented in hardware, software, or a combination of both. Specifically, whether to execute in hardware or software depends on the specific application and design constraints of the technical solution. Professional technicians can use different methods for each specific application to implement the described functions, but such implementation should not be considered to exceed 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 functional 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 through a data signal carried in a carrier wave on a transmission medium or a communication link.

[0251] It should be clear that the present application is not limited to the specific configurations and processes described above and shown in the figures. For the sake of brevity, detailed descriptions of known methods are 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 steps after understanding the spirit of the present application.

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

[0253] The above are only the preferred embodiments of the present application and are not used to limit the present application. For those skilled in the art, various changes and variations can be made to the embodiments of the present application. Any modifications, equivalent replacements, improvements, 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 dual-active center system for mobile payment on expressways, characterized in that Including: Two simultaneously online data centers that are set within the same target area and communicate 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 data center is used to process the highway mobile payment requests received by itself according to each server set locally and forward them to an external payment channel to receive corresponding payment result data from the payment channel. If the payment result data shows successful payment, the payment result data will be sent to the corresponding highway lane system; Each data center stores summary data of itself and the other data center, including the corresponding highway mobile payment requests and the payment result data; A cache layer is provided in one of the data centers. The cache layer 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 state is abnormal according to its own status monitoring result data stored in the cache layer, it performs abnormal recovery processing or sends the highway mobile payment request currently received from the highway lane system to the other data center for processing; A business layer is provided in each data center; The business layer is used to process the highway mobile payment requests received by itself according to each server set locally, and convert the order number in the highway mobile payment request into a payment order number that conforms to the preset order coding rule of the target payment channel according to the target payment channel specified in the highway mobile payment request, and perform internal transmission of the highway mobile payment request and the corresponding payment order number in the data center where it is located; An outbound layer is also provided in each data center; each outbound layer is communicatively connected between the business layer of the data center where it is located and each external payment channel; 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 each server set locally and a preset core transmission area, and receive the payment result data for the highway mobile payment request returned by the target payment channel based on a preset isolation area, where the core transmission area and the isolation area are different partitions formed by splitting each transmission channel in advance.

2. The dual-active center system for highway mobile payment according to claim 1, characterized in that, A front-end layer is provided in each data center; The front-end layer includes: a routing service unit; The routing service units in each data center are respectively connected to each highway lane system in the target area, the business layer in the data center where it is located, the outbound layer in the data center where it is located, and the business layer in the other 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 service layer in the data center where it is located; The routing service unit is further used to perform the following: When or after sending the highway mobile payment request to the service layer in the data center where it is located, asynchronously send a response query request to the outbound layer in the data center where it is located; If the payment result data returned by the outbound layer in the data center where it is located based on the response query request is received within a preset time period, obtain the current payment status of the order corresponding to the highway mobile payment request shown in the payment result data; If the payment status is payment success, forward the payment result data to the highway lane system that sent the highway mobile payment request; If the payment status is payment in progress, send a response query request to the outbound layer in the data center where it is located again; If the payment status is payment failure, or if the payment result data returned by the outbound layer in the data center where it is located based on the response query request is not received within a preset time period, forward the highway mobile payment request corresponding to the payment result data to the service layer in another data center for processing.

3. The dual-active center system for highway mobile payment according to claim 2, wherein The front-end layer further includes: a heartbeat monitoring unit; The heartbeat monitoring unit is communicatively connected between the cache layer and the routing service unit of the data center where it is located; The heartbeat monitoring unit is used to obtain the current status monitoring result data of the data center where it is located from the cache layer. If it is determined according to the status monitoring result data that there is a status anomaly in the data center where it is located, generate a corresponding anomaly notification message, and send the anomaly notification message to the routing service unit in the data center where it is located; Correspondingly, the routing service unit is further used to forward the currently received highway mobile payment request to the service layer in another data center for processing when receiving the anomaly notification message sent by the heartbeat monitoring unit in the data center where it is located.

4. The dual-active center system for highway mobile payment according to claim 3, wherein Each data center is provided with a data layer; The database in the data layer includes: a business database and a summary database; The business database is communicatively connected between the service layer and the outbound layer in the data center where it is located respectively. The business database is used to obtain the corresponding highway mobile payment request, order number, payment order number, and payment result data from the service layer and the outbound layer in the data center where it is located respectively, and store the corresponding highway mobile payment request, order number, payment order number, and payment result data as payment record data; The business libraries in the two data centers are both used to synchronize each of the payment record data stored therein to the summary library in one of the data centers based on a preset synchronization program; Correspondingly, the summary library in one of the data centers is used to receive each of the payment record data sent by the business libraries in the two data centers, store each of 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.

5. The dual-active center system for highway mobile payment according to claim 4, wherein Each data center 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 communicatively connected to the service layer, the outbound layer, and the data layer in the data center where it is located, and the heartbeat service unit is also communicatively connected to the cache layer; The heartbeat service unit is used to perform real-time status monitoring on each server in the service layer, the outbound layer, and the data layer in the data center where it 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 server that is currently in an available state in the data center where it is located is less than a preset quantity threshold when the server status monitoring result data indicates that there is an abnormal server; if not, execute a preset abnormal recovery processing step; Among them, the abnormal recovery processing step includes: Sending an abnormal notification message containing the unique number corresponding to the abnormal server 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 according to 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; The heartbeat service unit is also used to send an abnormal recovery message for the 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 abnormal recovery notification message.

6. The highway mobile payment dual-active center system according to claim 5, wherein, The monitoring layer further includes: a probing service unit; the status monitoring result data further includes: database connection status monitoring result data and external network connection status monitoring result data; The probing service unit is respectively communicatively connected to the outbound layer and the data layer in the data center where it is located, and the probing service unit is also communicatively connected to the cache layer; The probing service unit is used to perform real-time external network connection status monitoring on the outbound layer in the data center where it is located, and send the corresponding database connection status monitoring result data to the cache layer for storage; The exploration service unit is used to perform real-time monitoring of the database connection status of the data layer in the data center where it is located, and send the corresponding monitoring result data of the external network connection status to the cache layer for storage.

7. The dual-active center system for highway mobile payment according to claim 6, wherein The heartbeat service unit is further configured to, when it is determined that the data of each server that is currently in an available state in the data center where it is located is less than a preset quantity threshold, obtain from the cache layer the monitoring result data of the database connection status and the monitoring result data of the external network connection status stored by the exploration service unit in the monitoring layer where it is located. If at least one of the monitoring result data of the database connection status and the monitoring result data of the external network connection status indicates an abnormal connection, the abnormal recovery processing step is executed.

8. The highway mobile payment dual-active center system according to any one of claims 1 to 7, characterized in that, One data center provided with the cache layer is further configured to receive a transaction query request from the clearing center corresponding to the target area, 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; One data center provided with the cache layer is further configured to receive a refund request from the clearing center, perform business processing on the refund request according to each of its servers and forward it to an external payment channel, so as to receive corresponding refund result data from the payment channel. If the refund result data indicates a successful refund, the refund result data is sent to the clearing center.

Images