Account recharging method, device and system

Abstract

The present application discloses an account recharge method, device and system to at least solve the problem that the continuity of account recharge service cannot be guaranteed in the prior art. The system includes: a recharge access node, an authentication node and a recharge node; the recharge access node is used to monitor the working status of the recharge node, and when receiving the first recharge request of the target account and the recharge node is abnormal, send an authentication request to the authentication node based on the first recharge request, and when the authentication result returned by the authentication node indicates that the target account is normal and the recharge node has returned to normal, send a second recharge request to the recharge node; the authentication node is used to respond to the authentication request, authenticate the target account based on the preset account status data and return the obtained authentication result to the recharge access node; the recharge node is used to respond to the second recharge request and recharge the target account.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to an account recharging method, device and system. Background Art

[0002] Currently, as the billing system is further x86-based or cloud-based, the number of devices has increased exponentially and the network complexity has further increased, which has greatly increased the probability of failure in the billing system and the billing system and recharge access network.

[0003] Since the current account recharge mode adopts a real-time processing mode, when the billing system or the billing system and the recharge access network fail, the account recharge service will be unavailable, resulting in recharge failure, and the continuity of the account recharge service cannot be guaranteed. Summary of the invention

[0004] The embodiments of the present application provide an account recharge method, device and system to at least solve the problem in the prior art that the continuity of the account recharge service cannot be guaranteed.

[0005] In order to solve the above technical problems, the embodiments of the present application adopt the following technical solutions:

[0006] In a first aspect, an embodiment of the present application provides an account recharge system, including: a recharge access node, an authentication node, and a recharge node;

[0007] The recharge access node is used to monitor the working status of the recharge node, and when receiving a first recharge request of a target account and the recharge node is abnormal, send an authentication request to the authentication node based on the first recharge request, and when the authentication result returned by the authentication node indicates that the target account is normal and the recharge node has recovered to normal, send a second recharge request to the recharge node, wherein the first recharge request and the second recharge request are used to request recharging of the target account, and the authentication request is used to request authentication of the target account;

[0008] The authentication node is used to respond to the authentication request, authenticate the target account based on preset account status data and return the obtained authentication result to the recharge access node;

[0009] The recharge node is used to recharge the target account in response to the second recharge request.

[0010] Optionally, the account recharge system further includes an account management node;

[0011] The recharge access node is used to send a recharge data query request to the account management node, and determine whether the recharge node is abnormal based on the historical recharge data of the recharge node returned by the account management node, wherein the recharge data query request is used to request to obtain the historical recharge data of the recharge node, and the historical recharge data includes the number of historical recharges and the recharge result of each recharge;

[0012] The account management node is used to respond to the recharge data query request, obtain the historical recharge data of the recharge node and return it to the recharge access node.

[0013] Optionally, the recharge access node is further configured to, when the authentication result returned by the authentication node indicates that the target account is normal and the recharge node has not returned to normal within a predetermined time after the recharge access node receives the first recharge request, send a signal control status query request to the account management node to obtain the signal control status of the target account, and when the signal control status of the target account returned by the account management node is a non-power-on state, send a service activation request to the account management node to request activation of a specified service for the target account;

[0014] The account management node is further configured to, in response to the information control status query request, obtain the information control status of the target account and return it to the recharge access node, and, in response to the service activation request, activate the target account and activate the designated service.

[0015] Optionally, the recharge node is further configured to return a recharge result to the recharge access node after recharging the target account;

[0016] The recharge access node is further configured to send a service closing request to the account management node to request the account management node to close the designated service for the target account if the recharge result indicates that the target account is successfully recharged;

[0017] The account management node is further configured to close the designated service for the target account in response to the closing request.

[0018] Optionally, the recharge node is further configured to send a recharge result to the account management node after recharging the target account;

[0019] The account management node is further configured to update the account balance of the target account based on the recharge result, return the power-on processing result to the recharge access node after powering on the target account, and restore the target account to a non-powered state based on a signal control state restoration request of the recharge access node;

[0020] The recharge access node is further configured to query the account management node for the account balance of the target account when the power-on processing result indicates that the target account is powered on successfully, and to send a signal control state recovery request to the account management node when the account balance of the target account is less than a set amount, so as to request that the signal control state of the target account be restored to a non-power-on state.

[0021] Optionally, the account management node is further used to monitor the credit control status of the target account and send information about the credit control status of the target account to the authentication node;

[0022] The authentication node is further used to update the preset account status data based on the information of the credit control status of the target account.

[0023] In a second aspect, an embodiment of the present application provides an account recharge method, which is applied to a recharge access node, and the method includes:

[0024] Monitoring the working status of the recharge node;

[0025] When a first recharge request of a target account is received and the recharge node is abnormal, an authentication request is sent to an authentication node based on the first recharge request, wherein the first recharge request is used to request recharging of the target account, and the authentication request is used to request the authentication node to authenticate the target account;

[0026] Receiving the authentication result of the target account returned by the authentication node;

[0027] When the authentication result indicates that the target account is normal and the recharging node is restored to normal, a second recharging request is sent to the recharging node to request the recharging node to recharge the target account.

[0028] In a third aspect, an embodiment of the present application provides an account recharge method, which is applied to an authentication node, and the method includes:

[0029] receiving an authentication request from a recharge access node, the authentication request being used to request authentication of a target account, the authentication request being sent by the recharge access node to the authentication node when receiving a first recharge request of the target account and detecting an abnormality in the recharge node;

[0030] authenticating the target account based on preset account status data to obtain an authentication result indicating whether the target account is normal;

[0031] The authentication result is returned to the recharge access node, so that the recharge access node requests the recharge node to recharge the target account when the authentication result indicates that the target account is normal.

[0032] In a fourth aspect, an embodiment of the present application provides an account recharge device, which is applied to a recharge access node, and the device includes:

[0033] A monitoring module, used to monitor the working status of the recharge node;

[0034] an authentication request module, configured to, when receiving a first recharge request of a target account and the recharge node is abnormal, send an authentication request to the authentication node based on the first recharge request, wherein the first recharge request is used to request recharging of the target account, and the authentication request is used to request the authentication node to authenticate the target account;

[0035] An authentication result receiving module, used to receive the authentication result of the target account returned by the authentication node;

[0036] The recharge request module is used to send a second recharge request to the recharge node to request the recharge node to recharge the target account when the authentication result indicates that the target account is normal and the recharge node has recovered to normal.

[0037] In a fifth aspect, an embodiment of the present application provides an account recharge device, which is applied to an authentication node, and the device includes:

[0038] An authentication request receiving module, used to receive an authentication request from a recharge access node, wherein the authentication request is used to request authentication of a target account, and the authentication request is sent by the recharge access node to the authentication node when the recharge access node receives a first recharge request from the target account and detects an abnormality in the recharge node;

[0039] an authentication module, configured to authenticate the target account based on preset account status data to obtain an authentication result indicating whether the target account is normal;

[0040] The authentication result sending module is used to return the authentication result to the recharge access node, so that the recharge access node requests the recharge node to recharge the target account when the authentication result indicates that the target account is normal.

[0041] At least one of the above technical solutions adopted in the embodiments of the present application can achieve the following beneficial effects:

[0042] In the account recharge system provided in the embodiment of the present application, the working status of the recharge node can be monitored through the recharge access node to identify whether the recharge service is available, and when the first recharge request of the target account is received and the recharge node is abnormal, the asynchronous recharge process is automatically started. When waiting for the recharge node to return to normal, the target account is recharged through the recharge node. Compared with the real-time recharge method in the prior art, the recharge service can be prevented from being interrupted due to the failure of the recharge node, thereby ensuring the continuity of the recharge service and improving the user experience; at the same time, the target account can be authenticated through the authentication node. When the target account is normal, the asynchronous recharge process is started to ensure the security of the entire account recharge system. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0044] Figure 1 A schematic diagram of the structure of an account recharge system provided in an embodiment of the present application;

[0045] Figure 2 A schematic diagram of a result of recharging an access node provided in an embodiment of the present application;

[0046] Figure 3 A schematic diagram of the structure of an authentication node provided in an embodiment of the present application;

[0047] Figure 4 A flowchart of an account recharge method provided in an embodiment of the present application, wherein the method is applied to recharge access nodes;

[0048] Figure 5 A flowchart of an account recharge method provided in an embodiment of the present application, wherein the method is applied to an authentication node;

[0049] Figure 6 A schematic diagram of the structure of an account recharge device provided in an embodiment of the present application, wherein the method is applied to a recharge access node;

[0050] Figure 7 A schematic diagram of the structure of an account recharging device provided in an embodiment of the present application, wherein the method is applied to an authentication node;

[0051] Figure 8 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

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

[0053] The technical solutions provided by various embodiments of the present application are described in detail below in conjunction with the accompanying drawings.

[0054] In order to solve the problem in the existing account recharge method that the account recharge service is unavailable when a failure occurs in the billing system or between the billing system and the recharge access network, resulting in the inability to ensure the continuity of the account recharge service, the embodiments of the present application provide an account recharge method, device and system.

[0055] The following first introduces an account recharging system provided in an embodiment of the present application.

[0056] like Figure 1 As shown, as an example, the account recharge system provided in the embodiment of the present application may include a recharge access node 1, an authentication node 2 and a recharge node 3, wherein the recharge access node 1 is connected to the authentication node 2 and the recharge node 3 respectively.

[0057] Optionally, Figure 1 The account recharge system shown may further include an operation node 4 , which is connected to the recharge access node 1 .

[0058] Among them, the recharge access node 1 can also be regarded as an intermediate server between the operation node 4 and the recharge node 3, which is used to realize indirect communication or data interaction between the operation node 4 and the recharge node 3. The recharge access node 1 can communicate directly with the operation node 4, and the recharge access node 1 can also communicate directly with the recharge node 3.

[0059] Among them, the recharge demander A has a demand for recharging the account, and the recharge demander can recharge the account through a variety of recharge channels. For example, the recharge channels may include but are not limited to external e-commerce platforms, internal electronic channel platforms provided by mobile operators, O2O (Online to Online, offline mode) platforms provided by O2O recharge service agents, etc. The operation node 4 can manage the recharge requests from different recharge channels and uniformly access the recharge access node 1.

[0060] Specifically, the operation node 4 may include a server for managing recharge requests from different recharge channel platforms, for example, a unified payment server for aggregating recharge requests from external e-commerce platforms, a business hub server for forwarding the aggregated recharge requests to the recharge access node 1, an ECOP (Electronic Channel Operation Platform) for receiving recharge requests from internal electronic channel platforms and forwarding them to the recharge access node 1, etc. Based on this, the recharge demander A can perform recharge operations on the target account to be recharged through different recharge channels according to actual needs.

[0061] The recharge access node 1 may be a server of a mobile operator service provider, which can not only provide account recharge services, but also monitor the working status of the recharge node. Specifically, the recharge access node 1 may include a WAS (Web Application Server) cluster and an asynchronous recharge database for storing relevant information of unprocessed recharge requests. A group of application servers are deployed in the WAS cluster, such as Figure 2 As shown, the WAS cluster may include an O2O recharge server for processing recharge requests from the O2O platform, a provincial electronic recharge server for processing recharge requests from ECOP, a unified payment recharge server for processing recharge requests from the business hub platform, an asynchronous recharge server for asynchronous recharge processing, a recharge emergency processing server for recharge emergency processing, etc.

[0062] The authentication node 2 may be a server of a mobile operator service provider, which may authenticate an account. Figure 3 As shown, the authentication node 2 may include an authentication server for performing authentication, an authentication database for storing account status data, and the like.

[0063] The recharge node 3 may be a server of a mobile operator service provider, which may provide a recharge service for an account. Specifically, the recharge node 3 may include servers deployed in different cities, for example, Figure 1 As shown, the recharge node 3 may include BDS (Billing Data Service) servers deployed in different cities. The BDS servers deployed in each city may provide recharge and account entry services for the accounts in the respective city.

[0064] In a detailed embodiment, if the recharge demander A wants to recharge the target account, he can choose any recharge channel to perform the recharge operation. For example, taking the O2O platform as an example, the recharge demander A can enter the account information of the target account and the amount to be recharged. Based on the recharge operation of the recharge demander A, the O2O platform generates a first recharge request and sends it to the recharge access node 1. Among them, the first recharge request carries the account information of the target account (such as account identification) and recharge information (such as recharge amount).

[0065] The recharge access node 1 can be used to monitor the working status of the recharge node 3, and when receiving the first recharge request of the target account and the recharge node 3 is abnormal, it sends an authentication request to the authentication node 2 based on the first recharge request to request the authentication node 2 to authenticate the target account. The authentication request carries the account information of the target account.

[0066] Specifically, if Figure 2 As shown, taking recharging through the O2O channel as an example, after receiving the first recharge request from the O2O recharge platform, the O2O recharge server in the recharge access node 1 carries the account information of the target account in the authentication request based on the account information of the target account carried in the first recharge request and sends it to the authentication node 2, and receives the authentication result of the target account returned by the authentication node 2.

[0067] The authentication node 2 may be used to receive the authentication request sent by the recharge access node 1, and in response to the authentication request, authenticate the target account based on the preset account status data and return the obtained authentication result to the recharge access node 1. The authentication result is used to indicate whether the target account is normal.

[0068] Specifically, if Figure 3 As shown, the authentication database in the authentication node 2 stores account status data of different accounts, and the account status data is used to indicate the account status of the account (such as whether the account is normal or abnormal). After receiving the authentication request, the authentication server can query the account status data of the target account from the query authentication library based on the account information of the target account carried in the authentication request, and further determine whether the target account is normal based on the account status data to obtain the authentication result of the target account. The authentication server returns the obtained authentication result to the recharge access node 1.

[0069] The recharge access node 1 can also be used to send a second recharge request to the recharge node 3 to request the recharge node 3 to recharge the target account when the authentication result returned by the authentication node 2 indicates that the target account is normal and the recharge node has recovered to normal. The second recharge request carries the account information and recharge information of the target account.

[0070] Still Figure 2Taking the O2O channel recharge as an example, when the authentication result returned by the authentication node 2 indicates that the target account is normal, the O2O recharge server writes the account information and recharge information of the target account into the asynchronous recharge database and marks the recharge status of the target account as unprocessed. After the recharge node 3 returns to normal, the asynchronous recharge server reads the account information and recharge information of the unprocessed target account from the asynchronous recharge database, generates a second recharge request based on the account information and recharge information of the target account, and sends the second recharge request to the BDS server deployed in the recharge node 3 in the city where the target account belongs, so as to request the BDS server to recharge the target account.

[0071] The recharge node 3 may be used to recharge the target account in response to the second recharge request from the recharge access node 1 .

[0072] Specifically, if Figure 1 As shown, after receiving the second recharge request, the BDS server deployed in the city where the target account belongs in the recharge node 3 recharges the target account based on the account information and recharge information of the target account carried in the second recharge request.

[0073] It can be understood that in the account recharge system provided in the embodiment of the present application, the working status of the recharge node can be monitored through the recharge access node to identify whether the recharge service is available, and when the first recharge request of the target account is received and the recharge node is abnormal, the asynchronous recharge process is automatically started. When waiting for the recharge node to return to normal, the target account is recharged through the recharge node. Compared with the real-time recharge method in the prior art, the recharge service can be prevented from being interrupted due to recharge node failure, thereby ensuring the continuity of the recharge service and improving the user experience; at the same time, the target account can be authenticated through the authentication node. When the target account is normal, the asynchronous recharge process is started to ensure the security of the entire account recharge system.

[0074] Alternatively, if Figure 1 As shown, the account recharge system provided in the embodiment of the present application may further include an account management node 5, and the account management node 5 is connected to the recharge node 3 and the authentication node 2 respectively.

[0075] The account management node 5 may be a server of a mobile operator service provider, which can provide account reconciliation services. Specifically, the account management node 5 may include HSC (Home Subscriber Center, information management center) servers, CRM (Customer Relationship Management, customer relationship management) servers deployed in different cities, and a report database for storing historical recharge data of each account, etc. The HSC server can provide reconciliation services, and the CRM can provide power on and off services.

[0076] In a detailed embodiment, the account management node 5 stores historical recharge data of the recharge node 3 , wherein the historical recharge data may include the number of historical recharges and the recharge result of each recharge.

[0077] The recharge access node 1 may also be used to send a recharge data query request to the account management node 5 , so as to request the account management node 5 to obtain the historical recharge data of the recharge node 3 .

[0078] The account management node 5 may be used to respond to a recharge data query request from the recharge access node 1 , obtain historical recharge data of the recharge node 3 and return the data to the recharge access node 1 .

[0079] The recharge access node 1 may also determine whether the recharge node is abnormal based on the historical recharge data of the recharge node 3.

[0080] Specifically, if Figure 1 As shown, in an optional solution, the WAS cluster in the recharge access node 1 can send a recharge data query request to the CRM server in the account management node 5 in real time, and the CRM server responds to the recharge data query request and returns the historical recharge data of the BDS server to the WAS cluster. After receiving the historical recharge data, the WAS cluster can classify and integrate the historical recharge data according to the recharge channel to obtain the number of recharges corresponding to each recharge channel and the recharge result of each recharge; further, for each recharge channel, based on the number of recharges corresponding to the recharge channel and the recharge result of each recharge, the recharge success rate of the recharge channel can be determined; if the recharge success rate of any recharge channel is lower than the first set value, it can be determined that the recharge node 3 is abnormal.

[0081] In another optional solution, the WAS cluster in the recharge access node 1 can periodically send a recharge data query request to the CRM server in the account management node 5, and the CRM server responds to the recharge data query request and returns the historical recharge data of the BDS server to the WAS cluster. The WAS cluster can determine the recharge success rate of each cycle based on the number of recharges in each cycle and the recharge result of each recharge, and further determine the year-on-year or month-on-month difference between the recharge success rate of the current cycle and the recharge success rate of the previous cycle. If the year-on-year or month-on-month difference exceeds the second set value, it can be determined that the recharge node 3 is abnormal.

[0082] Of course, in some other optional solutions, the recharge access node 1 can also monitor other nodes in the account recharge system, and start the asynchronous recharge process when any node is monitored to be abnormal.

[0083] It can be understood that through the above scheme, the recharge access node obtains the historical recharge data of the recharge node from the account management system, and identifies whether the recharge node is abnormal based on the historical recharge data of the recharge node. Since the historical recharge data of the recharge node can accurately reflect the situation of the recharge node providing account recharge services, this method can accurately and reliably monitor the working status of the recharge node, and the implementation method is simple.

[0084] Optionally, the recharge access node 1 can also be used to send a signal control status query request to the account management node 5 to request to obtain the signal control status of the target account when the authentication result returned by the authentication node 2 indicates that the target account is normal and the recharge node 3 has not returned to normal within a predetermined time after the recharge access node 1 receives the first recharge request.

[0085] The account management node 5 is further configured to respond to the information control status query request from the recharge access node 1 , obtain the information control status of the target account and return it to the recharge access node 1 .

[0086] The recharge access node 1 is further used to send a service activation request to the account management node 5 to request activation of a specified service for the target account when the signal control state of the target account returned by the account management node 5 is a non-activated state.

[0087] The account management node 5 is further configured to respond to a service activation request from the recharge access node 1 , perform activation processing on the target account and activate a designated service.

[0088] The credit control status of the account may include, for example, but is not limited to: power-on status, semi-shutdown status due to arrears, shutdown status due to arrears, semi-shutdown status, etc. The scheduled duration may be customized according to actual needs, for example, the scheduled duration may be 5 minutes, etc. The embodiment of the present application does not specifically limit the value of the set duration.

[0089] Specifically, if Figure 2 As shown, the recharge emergency processing server in the WAS cluster can query the CRM server for the signal control status of the target account when the authentication result returned by the authentication node 2 indicates that the target account is normal, and the recharge node 3 has not returned to normal within the predetermined time after the recharge access node 1 receives the first recharge request. If the signal control status of the target account is a non-on state (such as a light pink shutdown state, arrears semi-shutdown state, etc.), you can request the CRM server to start the target account and start the specified service, and request the BDS server to add the target account to the recharge disaster recovery red list to ensure that the target account can use the specified service normally.

[0090] It can be understood that through the above scheme, when the target account is normal and the recharge access node has not returned to normal within a predetermined time from the time the recharge access node receives the first recharge request, the recharge access node initiates the emergency processing process and requests the account management node to power on the target account and start the designated service to temporarily allow the target account to use the designated service normally, thereby avoiding the problem that the target account cannot use related services normally due to the account recharge system not responding to the recharge request of the target account for a long time, thereby reducing the risk of complaints about the account recharge service.

[0091] Furthermore, the recharge node 3 may also be used to return the recharge result to the recharge access node 1 after recharging the target account.

[0092] The recharge access node 1 may also be used to send a service closing request to the account management node 5 when the recharge result indicates that the target account is successfully recharged, so as to request the account management node to close a specified service for the target account.

[0093] The account management node is also used to close a specified service for a target account in response to a closing request.

[0094] Specifically, after recharging the target account, the BDS server returns the recharge result to the recharge emergency processing server in the WAS cluster. When the recharge result indicates that the recharge of the target account is successful, the recharge emergency processing server requests the CRM server to close the specified service for the target account, and requests the BDS server to delete the target account from the recharge disaster recovery red list, so that the target account can only use the specified service in the billing mode.

[0095] Optionally, the recharge node 3 may also be used to send the recharge result to the account management node 5 after recharging the target account.

[0096] The account management node 5 can also be used to update the account balance of the target account based on the recharge result, and after the target account is powered on, return the power-on processing result to the recharge access node 1, and restore the target account to a non-powered state based on the signal control state recovery request of the recharge access node 1.

[0097] The recharge access node 1 is also used to query the account balance of the target account from the account management node when the startup processing result indicates that the target account is successfully started, and to send a signal control state recovery request to the account management node 5 when the account balance of the target account is less than a set amount, so as to request to restore the signal control state of the target account to a non-startup state.

[0098] Specifically, if Figure 1 and 2As shown, after recharging the target account, the BDS server can send the recharge result to the HSC server. The HSC server generates a corresponding reconciliation file based on the recharge result and updates the account balance of the target account based on the reconciliation file. The HSC server also requests the CRM server to start the target account. After starting the target account, the CRM server returns the start-up processing result to the HSC server, which is fed back to the asynchronous recharge server by the HSC server.

[0099] When the startup result indicates that the target account has been successfully started, the asynchronous recharge server queries the account management node for the account balance of the target account, and when the account balance of the target account is less than the set amount, the asynchronous recharge server sends a signal control status recovery request to the HSC server, and the HSC server forwards the signal control status recovery request to the CRM to request the CRM to restore the signal control status of the target account to the non-startup state before the recharge is successful.

[0100] It can be understood that through the above scheme, when the target account is successfully powered on but the account balance of the target account after recharging is still less than the set balance, the recharge access node requests the account management node to restore the signal control state of the target account to the non-powered state before recharging. This can prevent the target account from using related services normally when it is in arrears, thereby improving the reliability of the account recharge system and ensuring the normal business operation of the mobile operation service provider.

[0101] Optionally, the account management node 5 may also be used to monitor the credit control status of the target account and send information on the credit control status of the target account to the authentication node 2 .

[0102] The authentication node 2 may also be used to update preset account status data based on the information of the credit control status of the target account.

[0103] Specifically, if Figure 1 and Figure 2 As shown, the HSC server can obtain the credit control status of the target account from the CRM server, and send the credit control status information of the target account to the authentication database in the authentication node to update the account status data in the authentication database.

[0104] It can be understood that through the above solution, the account management node monitors the credit control status of the target account and updates the preset account status data based on the monitoring results, which can improve the accuracy and reliability of subsequent authentication of the target account and further improve the security of the account recharge system.

[0105] It should be noted that in the account recharge system provided in the embodiment of the present application, when recharging the target account, if the recharge fails, the recharge node 3 can perform multiple recharge processes again. If the number of recharge failures reaches a set number, a recharge result indicating that the recharge of the target account has failed is sent to the account management node 5.

[0106] Secondly, the account management node 5 can also generate corresponding reconciliation information based on the recharge result of the target account and send it to the operation node 4 and the O2O platform respectively, so that the operation node 4 and the O2O platform can perform recharge reconciliation operations.

[0107] In addition, the account recharge system provided in the embodiment of the present application also has an account reversal function. Specifically, the operation node 4 can forward the first reversal request from each recharge channel platform to the recharge access node 1, and the recharge access node 1 responds to the first reversal request and sends a second reversal request to the recharge node 3. The recharge node 3 responds to the second reversal request, performs reversal processing on the target account, and sends the reversal processing result to the account management node 5, which further performs reconciliation processing. Among them, both the first reversal request and the second reversal request carry the account information and reversal information (such as the reversal amount) of the target account.

[0108] See also Figure 4 The present application also provides an account recharge method, which can be applied to Figure 1 The recharge access node 1 in the account recharge system shown in FIG. Figure 4 As shown, the method may include:

[0109] S42, monitor the working status of the recharge node.

[0110] S44: When a first recharge request of the target account is received and the recharge node is abnormal, an authentication request is sent to the authentication node based on the first recharge request.

[0111] The first recharge request is used to request recharging of the target account, and the authentication request is used to request the authentication node to authenticate the target account.

[0112] S46, receiving the authentication result of the target account returned by the authentication node.

[0113] S48, when the authentication result indicates that the target account is normal and the recharging node has recovered to normal, sending a second recharging request to the recharging node to request the recharging node to recharge the target account.

[0114] It should be noted that the specific implementation of the above steps can refer to the specific description of the recharge access node 1 in the account recharge system, which will not be repeated here.

[0115] Through the account recharge method provided in the embodiment of the present application, the working status of the recharge node can be monitored through the recharge access node to identify whether the recharge service is available, and when the first recharge request of the target account is received and the recharge node is abnormal, the asynchronous recharge process is automatically started. When waiting for the recharge node to return to normal, the target account is recharged through the recharge node. Compared with the real-time recharge method in the prior art, the recharge service can be prevented from being interrupted due to the failure of the recharge node, thereby ensuring the continuity of the recharge service and improving the user experience; at the same time, the target account can be authenticated through the authentication node. When the target account is normal, the asynchronous recharge process is started to ensure the security of the entire account recharge system.

[0116] For the above step S42, in an optional solution, the recharge access node can monitor the working status of the recharge node in the following manner: send a recharge data query request to the account management node, and determine whether the recharge node is abnormal based on the historical recharge data of the recharge node returned by the account management node. The recharge data query request is used to request to obtain the historical recharge data of the recharge node, and the historical recharge data includes the historical recharge times and the recharge results of each recharge.

[0117] It can be understood that through the above scheme, the recharge access node obtains the historical recharge data of the recharge node from the account management system, and identifies whether the recharge node is abnormal based on the historical recharge data of the recharge node. Since the historical recharge data of the recharge node can accurately reflect the situation of the recharge node providing account recharge services, this method can accurately and reliably monitor the working status of the recharge node, and the implementation method is simple.

[0118] In another embodiment, after the above step S46, the account recharge method provided in the embodiment of the present application may further include: when the authentication result returned by the authentication node indicates that the target account is normal and the recharge node has not returned to normal within a predetermined time after the recharge access node receives the first recharge request, sending a signal control status query request to the account management node to obtain the signal control status of the target account; when the signal control status of the target account returned by the account management node is a non-power-on state, sending a service activation request to the account management node to request to activate a specified service for the target account.

[0119] It can be understood that through the above scheme, when the target account is normal and the recharge access node has not returned to normal within a predetermined time from the time the recharge access node receives the first recharge request, the recharge access node initiates the emergency processing process and requests the account management node to power on the target account and start the designated service to temporarily allow the target account to use the designated service normally, thereby avoiding the problem that the target account cannot use related services normally due to the account recharge system not responding to the recharge request of the target account for a long time, thereby reducing the risk of complaints about the account recharge service.

[0120] In another embodiment, after the above step S48, the account recharge method provided in the embodiment of the present application may further include: receiving the recharge result of the target account returned by the recharge node; when the recharge result indicates that the recharge of the target account is successful, sending a service closing request to the account management node to request the account management node to close the specified service for the target account.

[0121] In another embodiment, after the above step S48, the account recharge method provided in the embodiment of the present application may further include: obtaining a power-on processing result of the target account provided by the account management node; when the power-on processing result indicates that the target account is successfully powered on, querying the account balance of the target account from the account management node; and when the account balance of the target account is less than a set amount, sending a signal control state recovery request to the account management node to request that the signal control state of the target account be restored to a non-powered state.

[0122] It can be understood that through the above scheme, when the target account is successfully powered on but the account balance of the target account after recharging is still less than the set balance, the recharge access node requests the account management node to restore the signal control state of the target account to the non-powered state before recharging. This can prevent the target account from using related services normally when it is in arrears, thereby improving the reliability of the account recharge system and ensuring the normal business operation of the mobile operation service provider.

[0123] See also Figure 5 The present application also provides an account recharge method, which can be applied to Figure 1 The authentication node 2 in the account recharge system shown. Figure 5 As shown, the method may include:

[0124] S52, receiving an authentication request from a recharge access node.

[0125] The authentication request is used to request authentication of the target account, and the authentication request is sent by the recharge access node to the authentication node when the recharge access node receives the first recharge request of the target account and detects that the recharge node is abnormal.

[0126] S54, authenticating the target account based on the preset account status data to obtain an authentication result indicating whether the target account is normal.

[0127] S56, returning the authentication result to the recharge access node, so that the recharge access node requests the recharge node to recharge the target account when the authentication result indicates that the target account is normal.

[0128] It should be noted that the specific implementation methods of the above steps can refer to the specific description of the authentication node 2 in the account recharging system, which will not be repeated here.

[0129] Through the account recharge method provided in the embodiment of the present application, the working status of the recharge node can be monitored through the recharge access node to identify whether the recharge service is available, and when the first recharge request of the target account is received and the recharge node is abnormal, the asynchronous recharge process is automatically started. When waiting for the recharge node to return to normal, the target account is recharged through the recharge node. Compared with the real-time recharge method in the prior art, the recharge service can be prevented from being interrupted due to the failure of the recharge node, thereby ensuring the continuity of the recharge service and improving the user experience; at the same time, the target account can be authenticated through the authentication node. When the target account is normal, the asynchronous recharge process is started to ensure the security of the entire account recharge system.

[0130] In another embodiment, after the above step S56, the account recharge method provided in the embodiment of the present application may further include: obtaining information on the credit control status of the target account provided by the account management node; and updating preset account status data based on the information on the credit control status of the target account.

[0131] It can be understood that in the above scheme, by obtaining the information of the credit control status of the target account provided by the account management node to update the preset account status data, the accuracy and reliability of subsequent authentication of the target account can be improved, and the security of the account recharge system can be further improved.

[0132] The above is a description of a specific embodiment of the specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0133] See also Figure 6 The present application also provides an account recharge device, which can be applied to Figure 1 The recharge access node 1 in the account recharge system shown in FIG. Figure 6As shown, the apparatus 600 may include:

[0134] A monitoring module 610, used to monitor the working status of the recharge node;

[0135] An authentication request module 620 is configured to, when receiving a first recharge request of a target account and the recharge node is abnormal, send an authentication request to the authentication node based on the first recharge request, wherein the first recharge request is used to request recharging of the target account, and the authentication request is used to request the authentication node to authenticate the target account;

[0136] An authentication result receiving module 630 is used to receive the authentication result of the target account returned by the authentication node;

[0137] The recharge request module 640 is configured to send a second recharge request to the recharge node to request the recharge node to recharge the target account when the authentication result indicates that the target account is normal and the recharge node has recovered to normal.

[0138] Optionally, the monitoring module 610 is specifically used for:

[0139] Send a recharge data query request to the account management node, and determine whether the recharge node is abnormal based on the historical recharge data of the recharge node returned by the account management node. The recharge data query request is used to request to obtain the historical recharge data of the recharge node, and the historical recharge data includes the historical recharge times and the recharge results of each recharge.

[0140] Optionally, the device 600 further includes:

[0141] The information control status request module is used to send a information control status query request to the account management node to obtain the information control status of the target account when the authentication result returned by the authentication node indicates that the target account is normal and the recharge node has not returned to normal within a predetermined time after the recharge access node receives the first recharge request.

[0142] The service activation request module is used to send a service activation request to the account management node to request activation of a specified service for the target account when the information control state of the target account returned by the account management node is a non-activated state.

[0143] Optionally, the device 600 further includes:

[0144] The recharge result receiving module is used to receive the recharge result of the target account returned by the recharge node.

[0145] The service closing request module is used to send a service closing request to the account management node to request the account management node to close a specified service for the target account when the recharge result indicates that the recharge of the target account is successful.

[0146] Optionally, the device 600 further includes:

[0147] The startup processing result acquisition module is used to obtain the startup processing result of the target account provided by the account management node.

[0148] The account balance query module is used to query the account balance of the target account from the account management node when the startup processing result indicates that the target account is successfully started.

[0149] The credit control state recovery request module is used to send a credit control state recovery request to the account management node when the account balance of the target account is less than the set amount, so as to request to restore the credit control state of the target account to the non-powered state.

[0150] See also Figure 7 The present application also provides an account recharge device, which can be applied to Figure 1 The authentication node 2 in the account recharge system shown. Figure 7 As shown, the apparatus 700 may include:

[0151] The authentication request receiving module 710 is used to receive an authentication request from a recharge access node, where the authentication request is used to request authentication of a target account. The authentication request is sent by the recharge access node to the authentication node when the recharge access node receives a first recharge request from the target account and detects an abnormality in the recharge node.

[0152] The authentication module 720 is used to authenticate the target account based on preset account status data to obtain an authentication result indicating whether the target account is normal.

[0153] The authentication result sending module 730 is used to return the authentication result to the recharge access node, so that the recharge access node requests the recharge node to recharge the target account when the authentication result indicates that the target account is normal.

[0154] Optionally, the device 700 further includes:

[0155] The credit control status acquisition module is used to obtain the credit control status information of the target account provided by the account management node.

[0156] The update module is used to update the preset account status data based on the information of the credit control status of the target account.

[0157] Figure 8 This is a schematic diagram of the structure of an electronic device according to an embodiment of the present application. Figure 8 At the hardware level, the electronic device includes a processor, and optionally also includes an internal bus, a network interface, and a memory. The memory may include a memory, such as a high-speed random access memory (RAM), and may also include a non-volatile memory (non-volatile memory), such as at least one disk storage. Of course, the electronic device may also include hardware required for other services.

[0158] The processor, network interface and memory can be interconnected through an internal bus, which can be an ISA (Industry Standard Architecture) bus, a PCI (Peripheral Component Interconnect) bus or an EISA (Extended Industry Standard Architecture) bus. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 8 Only one bidirectional arrow is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0159] The memory is used to store the program. Specifically, the program may include a program code, and the program code includes a computer operation instruction. The memory may include a memory and a non-volatile memory, and provides instructions and data to the processor.

[0160] The processor reads the corresponding computer program from the non-volatile memory into the memory and then runs it, forming an account recharge device at the logical level. The processor executes the program stored in the memory and is specifically used to perform the following operations:

[0161] Monitoring the working status of the recharge node;

[0162] When a first recharge request of a target account is received and the recharge node is abnormal, an authentication request is sent to an authentication node based on the first recharge request, wherein the first recharge request is used to request recharging of the target account, and the authentication request is used to request the authentication node to authenticate the target account;

[0163] Receiving the authentication result of the target account returned by the authentication node;

[0164] When the authentication result indicates that the target account is normal and the recharging node is restored to normal, a second recharging request is sent to the recharging node to request the recharging node to recharge the target account.

[0165] Alternatively, do the following:

[0166] receiving an authentication request from a recharge access node, the authentication request being used to request authentication of a target account, the authentication request being sent by the recharge access node to the authentication node when receiving a first recharge request of the target account and detecting an abnormality in the recharge node;

[0167] authenticating the target account based on preset account status data to obtain an authentication result indicating whether the target account is normal;

[0168] The authentication result is returned to the recharge access node, so that the recharge access node requests the recharge node to recharge the target account when the authentication result indicates that the target account is normal.

[0169] The above application Figure 4 or Figure 5The method performed by the account recharge device disclosed in the illustrated embodiment can be applied to a processor or implemented by a processor. The processor may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by an integrated logic circuit of hardware in the processor or an instruction in software form. The above processor can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor, etc. The steps of the method disclosed in the embodiments of the present application can be directly embodied as a hardware decoding processor for execution, or a combination of hardware and software modules in the decoding processor for execution. The software module can be located in a storage medium mature in the art such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, or an electrically erasable programmable memory, a register, etc. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

[0170] The electronic device may also perform Figure 4 or Figure 5 The method and the account recharge device are implemented in Figure 4 , Figure 5 The functions of the illustrated embodiment will not be described in detail in the embodiments of the present application.

[0171] Of course, in addition to software implementation methods, the electronic device of the present application does not exclude other implementation methods, such as logic devices or a combination of software and hardware, etc. That is to say, the execution subject of the following processing flow is not limited to each logic unit, but can also be hardware or logic devices.

[0172] The embodiment of the present application also provides a computer-readable storage medium, which stores one or more programs, wherein the one or more programs include instructions, which, when executed by a portable electronic device including a plurality of application programs, enable the portable electronic device to execute Figure 4 The method of the embodiment shown is specifically used to perform the following operations:

[0173] Monitoring the working status of the recharge node;

[0174] When a first recharge request of a target account is received and the recharge node is abnormal, an authentication request is sent to an authentication node based on the first recharge request, wherein the first recharge request is used to request recharging of the target account, and the authentication request is used to request the authentication node to authenticate the target account;

[0175] Receiving the authentication result of the target account returned by the authentication node;

[0176] When the authentication result indicates that the target account is normal and the recharging node is restored to normal, a second recharging request is sent to the recharging node to request the recharging node to recharge the target account.

[0177] Alternatively, the portable electronic device can be caused to execute Figure 5 The method of the embodiment shown is specifically used to perform the following operations:

[0178] receiving an authentication request from a recharge access node, the authentication request being used to request authentication of a target account, the authentication request being sent by the recharge access node to the authentication node when receiving a first recharge request of the target account and detecting an abnormality in the recharge node;

[0179] authenticating the target account based on preset account status data to obtain an authentication result indicating whether the target account is normal;

[0180] The authentication result is returned to the recharge access node, so that the recharge access node requests the recharge node to recharge the target account when the authentication result indicates that the target account is normal.

[0181] In short, the above description is only a preferred embodiment of the present application and is not intended to limit the protection scope of the present application. 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.

[0182] The systems, devices, modules or units described in the above embodiments may be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, the computer may be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

[0183] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0184] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0185] Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

Claims

1. An account recharge system, characterized in that: include: Recharge access nodes, authentication nodes and recharge nodes; The recharge access node is used to monitor the working status of the recharge node, and when receiving a first recharge request of a target account and the recharge node is abnormal, send an authentication request to the authentication node based on the first recharge request, and when the authentication result returned by the authentication node indicates that the target account is normal and the recharge node has recovered to normal, send a second recharge request to the recharge node, wherein the first recharge request and the second recharge request are used to request recharging of the target account, and the authentication request is used to request authentication of the target account; The authentication node is used to respond to the authentication request, authenticate the target account based on preset account status data and return the obtained authentication result to the recharge access node; The recharge node is configured to recharge the target account in response to the second recharge request; The recharge access node is further configured to, when the authentication result returned by the authentication node indicates that the target account is normal and the recharge node has not returned to normal within a predetermined time period after the recharge access node receives the first recharge request, send a signal control status query request to the account management node to obtain the signal control status of the target account, and when the signal control status of the target account returned by the account management node is a non-power-on state, send a service activation request to the account management node to request activation of a specified service for the target account; The account management node is configured to, in response to the information control status query request, obtain the information control status of the target account and return it to the recharge access node, and, in response to the service activation request, activate the target account and activate the specified service; The recharge node is further configured to send the recharge result to the account management node after recharging the target account; The account management node is further configured to update the account balance of the target account based on the recharge result, return the power-on processing result to the recharge access node after powering on the target account, and restore the target account to a non-powered state based on a signal control state restoration request of the recharge access node; The recharge access node is further configured to query the account management node for the account balance of the target account when the power-on processing result indicates that the target account is powered on successfully, and to send a signal control state recovery request to the account management node when the account balance of the target account is less than a set amount, so as to request that the signal control state of the target account be restored to a non-power-on state.

2. The account recharge system according to claim 1, characterized in that: The account recharge system also includes an account management node; The recharge access node is used to send a recharge data query request to the account management node, and determine whether the recharge node is abnormal based on the historical recharge data of the recharge node returned by the account management node, wherein the recharge data query request is used to request to obtain the historical recharge data of the recharge node, and the historical recharge data includes the number of historical recharges and the recharge result of each recharge; The account management node is used to respond to the recharge data query request, obtain the historical recharge data of the recharge node and return it to the recharge access node.

3. The account recharge system according to claim 1, characterized in that: The recharge node is further configured to return the recharge result to the recharge access node after recharging the target account; The recharge access node is further configured to send a service closing request to the account management node to request the account management node to close the designated service for the target account if the recharge result indicates that the target account is successfully recharged; The account management node is further configured to close the designated service for the target account in response to the closing request.

4. The account recharge system according to claim 1, characterized in that: The account management node is further used to monitor the credit control status of the target account and send information about the credit control status of the target account to the authentication node; The authentication node is further used to update the preset account status data based on the information of the credit control status of the target account.

5. An account recharge method, characterized in that: Applied to an account recharge system, the account recharge system includes a recharge access node, an authentication node and a recharge node, and the method includes: The recharge access node monitors the working status of the recharge node; When a first recharge request of a target account is received and the recharge node is abnormal, an authentication request is sent to an authentication node based on the first recharge request, wherein the first recharge request is used to request recharging of the target account, and the authentication request is used to request the authentication node to authenticate the target account; The authentication node authenticates the target account based on preset account status data in response to the authentication request and returns the obtained authentication result to the recharge access node; The recharge access node receives the authentication result of the target account returned by the authentication node; When the authentication result indicates that the target account is normal and the recharging node has recovered to normal, sending a second recharging request to the recharging node to request the recharging node to recharge the target account; The recharge node recharges the target account in response to the second recharge request; the recharge access node sends a signal control status query request to the account management node to obtain the signal control status of the target account when the authentication result returned by the authentication node indicates that the target account is normal and the recharge node does not return to normal within a predetermined time after the recharge access node receives the first recharge request, and sends a service start request to the account management node to request to start a specified service for the target account when the signal control status of the target account returned by the account management node is a non-startup state; Obtaining a startup processing result of a target account provided by the account management node; When the startup processing result indicates that the target account is successfully started, the account balance of the target account is queried from the account management node, and when the account balance of the target account is less than a set amount, a letter control state recovery request is sent to the account management node to request that the letter control state of the target account be restored to a non-startup state.

6. An account recharging device, characterized in that: The device comprises: Monitoring module, used to monitor the working status of the recharge node; an authentication request module, configured to, when receiving a first recharge request of a target account and the recharge node is abnormal, send an authentication request to the authentication node based on the first recharge request, wherein the first recharge request is used to request recharging of the target account, and the authentication request is used to request the authentication node to authenticate the target account; The authentication node includes an authentication request receiving module, an authentication module, and an authentication result sending module; The authentication request receiving module is used to receive an authentication request from a recharge access node; The authentication module is used to authenticate the target account based on preset account status data to obtain an authentication result indicating whether the target account is normal; An authentication result receiving module, used to receive the authentication result of the target account returned by the authentication module; a recharge request module, configured to send a second recharge request to the recharge node to request the recharge node to recharge the target account if the authentication result indicates that the target account is normal and the recharge node has recovered to normal; a recharge module, configured to recharge the target account in response to the second recharge request; A letter control status request module, configured to send a letter control status query request to the account management node to obtain the letter control status of the target account when the authentication result returned by the authentication node indicates that the target account is normal and the recharge node does not return to normal within a predetermined time after the recharge access node receives the first recharge request; A service activation request module, used to send a service activation request to the account management node to request activation of a specified service for the target account when the information control status of the target account returned by the account management node is a non-enabled state; A startup processing result acquisition module is used to obtain the startup processing result of the target account provided by the account management node; An account balance query module, used to query the account balance of the target account from the account management node when the startup processing result indicates that the target account is successfully started; The credit control state recovery request module is used to send a credit control state recovery request to the account management node when the account balance of the target account is less than the set amount, so as to request to restore the credit control state of the target account to the non-powered state.

Images