Third-party mobile phone recharging service system and method
Through a multi-dimensional link analysis model and a dual verification mechanism, the problem of misjudgment of link switching caused by interception of detection packets in the third-party mobile phone recharge service system was solved, achieving more accurate fault detection and link status judgment, and improving the stability and security of the system.
Patent Information
- Application Number
- CN202510787574.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-06-13
- Publication Date
- 2025-09-16
- Estimated Expiration
- 2045-06-13
AI Technical Summary
Existing third-party mobile phone recharge service systems have the problem of misjudging link failures when detecting link failures due to firewalls or intermediate devices intercepting detection packets, resulting in unnecessary link switching and introducing additional delays.
A multi-dimensional analysis model based on current link delay tests is used to generate a normal assessment coefficient. Through a dual verification mechanism of connectivity coefficient and timing coefficient, combined with the BFD protocol and CPU utilization, the link status can be accurately determined, and link switching can be performed when necessary.
It significantly improves the accuracy and reliability of fault detection, reduces misjudgments, enhances system stability and security, and ensures the normal transmission of business traffic.
Smart Images

Figure CN120659026A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of data communication technology, and in particular to a third-party mobile phone recharge service system and method. Background Art
[0002] With the popularization of mobile Internet and the development of communication technology, third-party mobile phone recharge services have become a core hub connecting users, operators and payment platforms. However, this field faces the following problems in practical application:
[0003] In the process of real-time detection of link connectivity and latency, a preset number of probe packets are sent to the peer node at a preset time interval. If there is no response three times in a row, the detection mechanism will determine that the link is faulty and a link switch will be performed;
[0004] However, the actual situation is that the detection protocol is blocked by the access control list of the firewall or intermediate device, but the business traffic can still be transmitted normally. If the link is switched at this time, additional delay may be introduced.
[0005] Therefore, a solution based on communication protocol integration, intelligent fault detection, full-link encryption and big data drive is needed, namely a third-party mobile phone recharge service system and method, to improve the stability, security and operational efficiency of the system to address the above-mentioned problems. Summary of the Invention
[0006] The purpose of the present invention is to provide a third-party mobile phone recharge service system and method in order to solve the above problems.
[0007] In order to achieve the above object, the present invention adopts the following technical solutions:
[0008] A third-party mobile phone recharge service system, comprising:
[0009] Communication module: Triggers link fault detection based on the latency test results of the current link, performs multi-dimensional analysis of the link to generate a normal evaluation coefficient, determines the link fault condition based on the normal evaluation coefficient, and performs corresponding link switching operations; based on the determined link, communicates with the operator and payment channel;
[0010] User interaction module: users interact with the front-end to realize the recharge operation entrance and information feedback;
[0011] Business processing module: handles recharge business and coordinates various modules to complete order life cycle management;
[0012] Data management and analysis module: stores data and provides analysis support to assist operational decision-making.
[0013] Preferably, triggering link fault detection based on the delay test result of the current link is specifically:
[0014] The probe packet is sent to the peer node at a preset time interval. If there is no response for k consecutive times, the link is considered to be faulty.
[0015] Preferably, the multi-dimensional analysis of the link to generate a normal evaluation coefficient specifically includes:
[0016] The connectivity coefficient is obtained by analyzing the detection packet and business traffic transmission information;
[0017] The timing coefficient is obtained by analyzing the decoupling information of BFD session and routing protocol status;
[0018] The normal assessment coefficient is obtained by comprehensively processing the connectivity coefficient and the timing coefficient;
[0019] A normal evaluation coefficient threshold is preset, and the normal evaluation coefficient is compared with the normal evaluation coefficient threshold. If the normal evaluation coefficient is less than the normal evaluation coefficient threshold, it is determined that a link failure occurs, and a link switching is performed;
[0020] If the normal evaluation coefficient is greater than the normal evaluation coefficient threshold, the link is determined to be normal.
[0021] Preferably, the process of obtaining the connectivity coefficient includes:
[0022] After the sender sends a probe packet as a probe packet test, the sender and the receiver simultaneously capture data packets. If the receiver successfully extracts information indicating that the probe packet is received but no response is returned, a service traffic connectivity test is triggered, including: checking the service traffic packet loss rate of the target link and checking whether the HTTP response content is correct through the network monitoring platform, presetting a packet loss rate threshold, and comparing the packet loss rate with the packet loss rate threshold. If the packet loss rate is less than the packet loss rate threshold and the HTTP response content is correct, the probe packet test is recorded as a connectivity test and the probe packet test is recorded.
[0023] Perform a probe packet test a preset number of times, count the number of connectivity tests, and divide the number of connectivity tests by the number of probe packet tests to obtain the connectivity degree.
[0024] Obtain the duration of a single TCP connection corresponding to the connectivity test, preset a duration threshold, subtract the duration threshold from the duration, remove values less than 0 from the obtained value, and record the remaining value as the duration difference;
[0025] Arrange the duration differences in descending order according to their values, and extract the three largest duration differences, which are recorded as the first duration difference, the second duration difference, and the third duration difference respectively;
[0026] The time difference between the first continuous time difference and the second continuous time difference is recorded as the first time difference;
[0027] The time difference between the second continuous time difference and the third continuous time difference is recorded as the second time difference;
[0028] The time difference between the first continuous time difference and the third continuous time difference is recorded as the third time difference;
[0029] The first and second time differences are respectively used as the two right-angled sides of a right triangle, and the remaining side is connected to obtain a complete right triangle. The third time difference is used as the height of the right triangle, and a triangular pyramid model is established. The volume of the triangular pyramid model is calculated and recorded as the quantized time value.
[0030] The connectivity coefficient is obtained by comprehensively processing the connectivity and quantized time values.
[0031] Preferably, the process of obtaining the timing coefficient includes:
[0032] Obtain BFD packet statistics for each monitored link, including send and receive counts. Subtract the receive count from the send count to obtain the number of lost packets.
[0033] Preset a loss number threshold, compare the loss number with the loss number threshold, and record the loss number greater than the loss number threshold as a marked loss number;
[0034] Obtain the device CPU usage corresponding to the number of mark loss events, preset a CPU usage threshold, compare the CPU usage with the CPU usage threshold, and if the CPU usage is greater than the CPU usage threshold, record the number of mark loss events as the secondary mark number.
[0035] Obtain the total time required for the service traffic data packet corresponding to the secondary mark number to travel from the sender to the receiver and back, which is recorded as the round-trip time; preset a round-trip time threshold, subtract the round-trip time threshold from the round-trip time, remove values greater than 0, and take the absolute value of values less than 0 as the round-trip time difference;
[0036] Arrange all the round-trip time differences in descending order according to their numerical values, and extract the largest round-trip time difference, which is recorded as the maximum round-trip time difference;
[0037] Obtain the ingress and egress bandwidth utilization of the target link through the network monitoring platform; divide the ingress bandwidth utilization by the egress bandwidth utilization to obtain the bandwidth utilization;
[0038] Presetting an allowable fluctuation range of bandwidth utilization, matching the bandwidth utilization with the allowable fluctuation range of bandwidth utilization, and recording the bandwidth utilization within the allowable fluctuation range of bandwidth utilization as normal bandwidth utilization;
[0039] A bandwidth utilization threshold is preset, and the difference between normal bandwidth utilization and the bandwidth utilization threshold is calculated to obtain a utilization difference;
[0040] Obtain each utilization difference in turn, and calculate the average of the utilization differences to obtain the utilization difference average;
[0041] The timing coefficient is obtained by comprehensively processing the maximum round-trip difference and the mean utilization difference.
[0042] Preferably, the user interaction module specifically includes:
[0043] Supports multi-terminal access via APP, WeChat mini-programs, and web pages, and provides diversified service entrances such as phone recharge, data package purchase, and package upgrade;
[0044] Users can select different operators and regions, manually enter or select a preset top-up amount, and complete transactions through mainstream payment methods such as Alipay, WeChat Pay, and UnionPay;
[0045] Built-in order management function, supporting historical recharge record query, order details viewing and abnormal appeal;
[0046] The user center integrates account real-name authentication, wallet balance management, and coupon / points usage functions, and provides online customer service and intelligent robot Q&A to achieve convenient interaction and service support for the entire recharge process.
[0047] Preferably, the business processing module specifically includes:
[0048] The order processing engine generates a unique order number, completes number verification, balance verification, and anti-fraud mechanism pre-verification, and intelligently selects the optimal channel for routing distribution based on the recharge type;
[0049] The account management function is responsible for recording fund flows, account calculations, and automatic reconciliation to ensure the accuracy of financial data;
[0050] For payment timeouts and interface error exceptions, the module has built-in automatic retry and manual intervention mechanisms, and supports refunds of failed orders through the original route, ensuring the stability and reliability of business processes and achieving full life cycle management from order generation to completion.
[0051] Preferably, the data management and analysis module specifically includes:
[0052] Adopting an architecture that combines relational and non-relational databases to achieve efficient storage and backup of user information, order data, and interface log data;
[0053] The data analysis function builds user portraits based on user recharge behavior and business report data, and generates visualization reports on recharge trends and channel conversion rates, providing decision-making basis for precision marketing and process optimization;
[0054] At the same time, data mining technology is used to identify abnormal recharge behaviors, implement risk warnings, and improve operational safety.
[0055] A third-party mobile phone recharge service method, comprising:
[0056] Communication Analysis: Triggering link fault detection based on the current link delay test results. Performing multi-dimensional analysis of the link to generate a normal evaluation coefficient. Based on the normal evaluation coefficient, the link fault condition is determined and the corresponding link switching operation is performed. Based on the determined link, communication with the operator and payment channel is connected.
[0057] User interaction: Users interact with the front-end to implement recharge operation entry and information feedback;
[0058] Business processing: handle recharge business and coordinate various modules to complete order life cycle management;
[0059] Data management and analysis: Store data and provide analytical support to assist operational decision-making.
[0060] In summary, due to the adoption of the above technical solution, the beneficial effects of the present invention are:
[0061] 1. This invention significantly improves the accuracy and reliability of fault detection through a multi-dimensional link analysis model. It achieves in-depth perception of link status through a dual verification mechanism of connectivity coefficient and timing coefficient. It converts abstract parameters such as network delay and bandwidth fluctuation into computable geometric indicators, and combines them with weight factors to achieve a comprehensive assessment of link health. The correlation analysis between the BFD protocol and CPU utilization effectively distinguishes between insufficient device resources and actual link failures, further improving the accuracy of fault location and reducing misjudgment scenarios caused by device performance bottlenecks.
[0062] 2. The present invention effectively addresses risks such as data leakage and illegal access by building a security system covering the entire chain of communication, storage, and interaction. At the communication layer, RSA encryption technology is used to provide end-to-end protection for payment data, and the HTTPS protocol is used to ensure transmission security, complying with compliance requirements such as PCI-DSS. At the user authentication level, multiple mechanisms such as SMS verification codes, fingerprint recognition, and dynamic tokens are integrated to reduce the probability of illegal account logins. At the same time, the business processing module achieves efficient processing of high-concurrency recharge requests through intelligent routing distribution and anti-swiping mechanisms. BRIEF DESCRIPTION OF THE DRAWINGS
[0063] Further details, features and advantages of the present application are disclosed in the following description of exemplary embodiments in conjunction with the accompanying drawings, in which:
[0064] Figure 1 Flowchart of the present invention. DETAILED DESCRIPTION
[0065] Several embodiments of the present application will be described in more detail below with reference to the accompanying drawings so that those skilled in the art can implement the present application. The present application can be embodied in many different forms and for many different purposes and should not be limited to the embodiments described herein. These embodiments are provided to make the present application comprehensive and complete and to fully convey the scope of the present application to those skilled in the art. The embodiments do not limit the present application.
[0066] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by those skilled in the art to which this application belongs. It will be further understood that terms such as those defined in commonly used dictionaries should be interpreted as having a meaning consistent with their meaning in the relevant art and / or the context of this specification, and will not be interpreted in an idealized or overly formal sense unless explicitly defined as such herein.
[0067] See also Figure 1 As shown, the present invention provides a technical solution:
[0068] A third-party mobile phone recharge service system, comprising:
[0069] Communication module: Based on the delay test results of the current link, it triggers link fault detection, performs multi-dimensional analysis of the link to generate a normal assessment coefficient, determines the fault condition of the link based on the normal assessment coefficient, and performs corresponding link switching operations; based on the determined link, it communicates with operators and payment channels; including connecting to the recharge interfaces of operators such as China Mobile, China Unicom, and China Telecom, parsing different instruction formats and verifying the validity of numbers; integrating third-party payment gateways such as Alipay and WeChat Pay, and using RSA encryption technology to ensure the secure transmission of payment data; at the same time, through the SMS gateway and APP push service, it realizes the real-time delivery of recharge notifications, verification codes and other information;
[0070] Trigger link fault detection based on the current link delay test results, specifically:
[0071] The node sends a probe packet to the peer node at a preset time interval (e.g., every 500ms). If there is no response for k consecutive times, the link is considered faulty. k is set by the administrator according to the actual situation, usually 3 times.
[0072] Once a link failure is determined, a multi-dimensional analysis of the link is triggered;
[0073] Perform multi-dimensional analysis of the link to generate a normal assessment coefficient, including:
[0074] The connectivity coefficient is obtained by analyzing the detection packet and business traffic transmission information;
[0075] include:
[0076] After the sender sends a probe packet as a probe packet test, the sender and the receiver simultaneously capture data packets. If the receiver successfully extracts information about receiving the probe packet but not returning a response, a service traffic connectivity test is triggered, including: checking the service traffic packet loss rate of the target link and checking whether the HTTP response content is correct through a network monitoring platform (such as Zabbix, Prometheus) or the device's built-in statistics function, presetting a packet loss rate threshold, and comparing the packet loss rate with the packet loss rate threshold. If the packet loss rate is less than the packet loss rate threshold and the HTTP response content is correct, the probe packet test is recorded as a connectivity test and the probe packet test is recorded.
[0077] Perform a probe packet test a preset number of times, count the number of connectivity tests, and divide the number of connectivity tests by the number of probe packet tests to obtain the connectivity degree.
[0078] Obtain the duration of a single TCP connection corresponding to the connectivity test, preset a duration threshold, subtract the duration threshold from the duration, remove values less than 0 from the obtained value, and record the remaining value as the duration difference;
[0079] Arrange the duration differences in descending order according to their values, and extract the three largest duration differences, which are recorded as the first duration difference, the second duration difference, and the third duration difference respectively;
[0080] The time difference between the first continuous time difference and the second continuous time difference is recorded as the first time difference;
[0081] The time difference between the second continuous time difference and the third continuous time difference is recorded as the second time difference;
[0082] The time difference between the first continuous time difference and the third continuous time difference is recorded as the third time difference;
[0083] The first and second time differences are respectively used as the two right-angled sides of a right triangle, and the remaining side is connected to obtain a complete right triangle. The third time difference is used as the height of the right triangle, and a triangular pyramid model is established. The volume of the triangular pyramid model is calculated and recorded as the quantized time value.
[0084] The connectivity coefficient is obtained by comprehensively processing the connectivity and quantized time values;
[0085] Preset weight factors for connectivity and quantized time values, calculate the product of connectivity and quantized time values with their corresponding weight factors, and sum them to obtain a connectivity coefficient;
[0086] The timing coefficient is obtained by analyzing the decoupling information of BFD session and routing protocol status;
[0087] include:
[0088] Obtain BFD packet statistics for each monitored link, including send and receive counts. Subtract the receive count from the send count to obtain the number of lost packets.
[0089] Preset a loss number threshold, compare the loss number with the loss number threshold, and record the loss number greater than the loss number threshold as a marked loss number;
[0090] Obtain the device CPU usage corresponding to the number of mark loss events, preset a CPU usage threshold, compare the CPU usage with the CPU usage threshold, and if the CPU usage is greater than the CPU usage threshold, record the number of mark loss events as the secondary mark number.
[0091] Obtain the total time required for the service traffic data packet corresponding to the secondary mark number to travel from the sender to the receiver and back, which is recorded as the round-trip time; preset a round-trip time threshold, subtract the round-trip time threshold from the round-trip time, remove values greater than 0, and take the absolute value of values less than 0 as the round-trip time difference;
[0092] Arrange all the round-trip time differences in descending order according to their numerical values, and extract the largest round-trip time difference, which is recorded as the maximum round-trip time difference;
[0093] Obtain the ingress and egress bandwidth utilization of the target link through the network monitoring platform; divide the ingress bandwidth utilization by the egress bandwidth utilization to obtain the bandwidth utilization;
[0094] Presetting an allowable fluctuation range of bandwidth utilization, matching the bandwidth utilization with the allowable fluctuation range of bandwidth utilization, and recording the bandwidth utilization within the allowable fluctuation range of bandwidth utilization as normal bandwidth utilization;
[0095] A bandwidth utilization threshold is preset, and the difference between normal bandwidth utilization and the bandwidth utilization threshold is calculated to obtain a utilization difference;
[0096] Obtain each utilization difference in turn, and calculate the average of the utilization differences to obtain the utilization difference average;
[0097] The timing coefficient is obtained by comprehensively processing the maximum round trip difference and the mean utilization difference;
[0098] After normalizing the maximum round-trip difference and the mean utilization difference, the maximum round-trip difference and the mean utilization difference are used as the major and minor semi-axis of the ellipse model respectively, and the ellipse model is established. The area of the ellipse model is calculated and recorded as the time coefficient.
[0099] The normal assessment coefficient is obtained by comprehensively processing the connectivity coefficient and the timing coefficient;
[0100] Preset the weight factors of the connectivity coefficient and the timing coefficient, and calculate the products of the connectivity coefficient and the timing coefficient with their corresponding weight factors and then sum them to obtain the normal assessment coefficient;
[0101] A normal evaluation coefficient threshold is preset, and the normal evaluation coefficient is compared with the normal evaluation coefficient threshold. If the normal evaluation coefficient is less than the normal evaluation coefficient threshold, it is determined that a link failure occurs, and a link switching is performed;
[0102] If the normal evaluation coefficient is greater than the normal evaluation coefficient threshold, the link is judged to be normal;
[0103] User interaction module: users interact with the front-end to realize the recharge operation entrance and information feedback;
[0104] Supports multi-terminal access via APP, WeChat mini-programs, and web pages, and provides diversified service entrances such as phone recharge, data package purchase, and package upgrade;
[0105] Users can select different operators and regions, manually enter or select a preset top-up amount, and complete transactions through mainstream payment methods such as Alipay, WeChat Pay, and UnionPay;
[0106] Built-in order management function, supporting historical recharge record query, order details viewing and abnormal appeal;
[0107] The user center integrates account real-name authentication, wallet balance management, and coupon / points usage functions, and provides online customer service and intelligent robot Q&A, enabling convenient interaction and service support throughout the entire recharge process;
[0108] Business processing module: handles recharge business and coordinates various modules to complete order life cycle management;
[0109] Specifically include:
[0110] The order processing engine generates a unique order number, completes number verification, balance verification, and anti-fraud mechanism pre-verification, and intelligently selects the optimal channel for routing distribution based on the recharge type;
[0111] The account management function is responsible for recording fund flows, account calculations, and automatic reconciliation to ensure the accuracy of financial data;
[0112] The module has built-in automatic retry and manual intervention mechanisms for payment timeouts and interface errors. It also supports refunds for failed orders, ensuring the stability and reliability of business processes and enabling full lifecycle management from order generation to completion.
[0113] Data management and analysis module: stores data and provides analysis support to assist operational decision-making;
[0114] Specifically include:
[0115] Adopting an architecture that combines relational and non-relational databases to achieve efficient storage and backup of user information, order data, and interface log data;
[0116] The data analysis function builds user portraits based on user recharge behavior and business report data, and generates visualization reports on recharge trends and channel conversion rates, providing decision-making basis for precision marketing and process optimization;
[0117] At the same time, data mining technology is used to identify abnormal recharge behaviors, implement risk warnings, and improve operational safety;
[0118] System management module: It is the core hub to ensure the stable and efficient operation of the system. It adopts a role-based permission management mechanism to assign differentiated operation permissions to personnel in different positions such as operations, customer service, and technology, and realizes behavior tracing through the operation log audit function to ensure the standardization and security of internal management; it supports dynamic adjustment of key business parameters such as recharge channel parameters and promotion rules, and can flexibly respond to changes in operational needs without code release; at the same time, it integrates a complete monitoring and operation and maintenance system to monitor system performance indicators in real time, and quickly responds to abnormal situations such as interface delays and excessive server loads through the threshold alarm mechanism. Combined with the centralized log management and retrieval function, it greatly improves the efficiency of fault location. In addition, this module also has the ability to hot deploy and grayscale release to minimize the impact of system upgrades on users and achieve continuous optimization and stable operation of the system;
[0119] Security Module: Ensures system security from three aspects: data security, identity authentication, and network protection. Encrypted storage is used for sensitive user information, and the HTTPS protocol is used during transmission. User login supports multiple authentication methods such as SMS verification codes and fingerprint recognition, and backend management uses dynamic tokens or USB key strong authentication. Firewalls and defense systems are deployed, and vulnerability scanning and penetration testing are conducted regularly to ensure that the system complies with GDPR and the Personal Information Protection Act, comprehensively protecting user privacy and system security.
[0120] A third-party mobile phone recharge service method, comprising:
[0121] Communication Analysis: Triggering link fault detection based on the current link delay test results. Performing multi-dimensional analysis of the link to generate a normal evaluation coefficient. Based on the normal evaluation coefficient, the link fault condition is determined and the corresponding link switching operation is performed. Based on the determined link, communication with the operator and payment channel is connected.
[0122] User interaction: Users interact with the front-end to implement recharge operation entry and information feedback;
[0123] Business processing: handle recharge business and coordinate various modules to complete order life cycle management;
[0124] Data management and analysis: store data and provide analytical support to assist operational decision-making;
[0125] System management: A role-based permission management mechanism assigns differentiated operation permissions to personnel in different positions, and enables behavior traceability through the operation log audit function to ensure the standardization and security of internal management;
[0126] Security management: Ensure system security from three aspects: data security, identity authentication and network protection; use encrypted storage for user sensitive information.
[0127] The above formulas are obtained by collecting a large amount of data and performing software simulation, and a formula close to the actual value is selected. The influencing weight factors and specific coefficient values in the formula are set by technical personnel in this field according to actual conditions, and can be adjusted and modified later.
[0128] The above description of the embodiments is intended to enable one skilled in the art to implement or use the present invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present invention. Therefore, the present invention is not limited to the embodiments shown herein but is intended to conform to the widest scope consistent with the principles and novel features disclosed herein.
Claims
1. A third-party mobile phone recharge service system, characterized in that: include: Communication module: Triggers link fault detection based on the latency test results of the current link, performs multi-dimensional analysis of the link to generate a normal evaluation coefficient, determines the link fault condition based on the normal evaluation coefficient, and performs corresponding link switching operations; based on the determined link, communicates with the operator and payment channel; User interaction module: users interact with the front-end to realize the recharge operation entrance and information feedback; Business processing module: handles recharge business and coordinates various modules to complete order life cycle management; Data management and analysis module: stores data and provides analysis support to assist operational decision-making.
2. A third-party mobile phone recharge service system according to claim 1, characterized in that: The delay test result based on the current link is used to trigger the fault detection of the link, specifically: The probe packet is sent to the peer node at a preset time interval. If there is no response for k consecutive times, the link is considered to be faulty.
3. A third-party mobile phone recharge service system according to claim 2, characterized in that: Perform multi-dimensional analysis of the link to generate a normal assessment coefficient, including: The connectivity coefficient is obtained by analyzing the detection packet and business traffic transmission information; The timing coefficient is obtained by analyzing the decoupling information of BFD session and routing protocol status; The normal assessment coefficient is obtained by comprehensively processing the connectivity coefficient and the timing coefficient; A normal evaluation coefficient threshold is preset, and the normal evaluation coefficient is compared with the normal evaluation coefficient threshold. If the normal evaluation coefficient is less than the normal evaluation coefficient threshold, it is determined that a link failure occurs, and a link switching is performed; If the normal evaluation coefficient is greater than the normal evaluation coefficient threshold, the link is determined to be normal.
4. A third-party mobile phone recharge service system according to claim 3, characterized in that: The process of obtaining the connectivity coefficient includes: After the sender sends a probe packet as a probe packet test, the sender and the receiver simultaneously capture data packets. If the receiver successfully extracts information indicating that the probe packet is received but no response is returned, a service traffic connectivity test is triggered, including: checking the service traffic packet loss rate of the target link and checking whether the HTTP response content is correct through the network monitoring platform, presetting a packet loss rate threshold, and comparing the packet loss rate with the packet loss rate threshold. If the packet loss rate is less than the packet loss rate threshold and the HTTP response content is correct, the probe packet test is recorded as a connectivity test and the probe packet test is recorded. Perform a probe packet test a preset number of times, count the number of connectivity tests, and divide the number of connectivity tests by the number of probe packet tests to obtain the connectivity degree. Obtain the duration of a single TCP connection corresponding to the connectivity test, preset a duration threshold, subtract the duration threshold from the duration, remove values less than 0 from the obtained value, and record the remaining value as the duration difference; Arrange the duration differences in descending order according to their values, and extract the three largest duration differences, which are recorded as the first duration difference, the second duration difference, and the third duration difference respectively; The time difference between the first continuous time difference and the second continuous time difference is recorded as the first time difference; The time difference between the second continuous time difference and the third continuous time difference is recorded as the second time difference; The time difference between the first continuous time difference and the third continuous time difference is recorded as the third time difference; The first and second time differences are respectively used as the two right-angled sides of a right triangle, and the remaining side is connected to obtain a complete right triangle. The third time difference is used as the height of the right triangle, and a triangular pyramid model is established. The volume of the triangular pyramid model is calculated and recorded as the quantized time value. The connectivity coefficient is obtained by comprehensively processing the connectivity and quantized time values.
5. A third-party mobile phone recharge service system according to claim 4, characterized in that: The process of obtaining the timing coefficient includes: Obtain BFD packet statistics for each monitored link, including send and receive counts. Subtract the receive count from the send count to obtain the number of lost packets. Preset a loss number threshold, compare the loss number with the loss number threshold, and record the loss number greater than the loss number threshold as a marked loss number; Obtain the device CPU usage corresponding to the number of mark loss events, preset a CPU usage threshold, compare the CPU usage with the CPU usage threshold, and if the CPU usage is greater than the CPU usage threshold, record the number of mark loss events as the secondary mark number. Obtain the total time required for the service traffic data packet corresponding to the secondary marking number to travel from the sending end to the receiving end and back, which is recorded as the round-trip time; preset a round-trip time threshold, subtract the round-trip time threshold from the round-trip time, remove values greater than 0, and take the absolute value of values less than 0 as the round-trip time difference; Arrange all the round-trip time differences in descending order according to their numerical values, and extract the largest round-trip time difference, which is recorded as the maximum round-trip time difference; Obtain the ingress and egress bandwidth utilization of the target link through the network monitoring platform; divide the ingress bandwidth utilization by the egress bandwidth utilization to obtain the bandwidth utilization; Presetting an allowable fluctuation range of bandwidth utilization, matching the bandwidth utilization with the allowable fluctuation range of bandwidth utilization, and recording the bandwidth utilization within the allowable fluctuation range of bandwidth utilization as normal bandwidth utilization; A bandwidth utilization threshold is preset, and the difference between normal bandwidth utilization and the bandwidth utilization threshold is calculated to obtain a utilization difference; Obtain each utilization difference in turn, and calculate the average of the utilization differences to obtain the utilization difference average; The timing coefficient is obtained by comprehensively processing the maximum round-trip difference and the mean utilization difference.
6. A third-party mobile phone recharge service system according to claim 1, characterized in that: The user interaction module specifically includes: Supports multi-terminal access via APP, WeChat mini-programs, and web pages, and provides diversified service entrances such as phone recharge, data package purchase, and package upgrade; Users can select different operators and regions, manually enter or select a preset top-up amount, and complete transactions through mainstream payment methods such as Alipay, WeChat Pay, and UnionPay; Built-in order management function, supporting historical recharge record query, order details viewing and abnormal appeal; The user center integrates account real-name authentication, wallet balance management, and coupon / points usage functions, and provides online customer service and intelligent robot Q&A to achieve convenient interaction and service support for the entire recharge process.
7. A third-party mobile phone recharge service system according to claim 1, characterized in that: The business processing module specifically includes: The order processing engine generates a unique order number, completes number verification, balance verification, and anti-fraud mechanism pre-verification, and intelligently selects the optimal channel for routing distribution based on the recharge type; The account management function is responsible for recording fund flows, account calculations, and automatic reconciliation to ensure the accuracy of financial data; For payment timeouts and interface error exceptions, the module has built-in automatic retry and manual intervention mechanisms, and supports refunds of failed orders through the original route, ensuring the stability and reliability of business processes and achieving full life cycle management from order generation to completion.
8. A third-party mobile phone recharge service system according to claim 1, characterized in that: The data management and analysis module specifically includes: Adopting an architecture that combines relational and non-relational databases to achieve efficient storage and backup of user information, order data, and interface log data; The data analysis function builds user portraits based on user recharge behavior and business report data, and generates visualization reports on recharge trends and channel conversion rates, providing decision-making basis for precision marketing and process optimization; At the same time, data mining technology is used to identify abnormal recharge behaviors, implement risk warnings, and improve operational safety.
9. A third-party mobile phone recharge service method, according to a third-party mobile phone recharge service system according to any one of claims 1-8, characterized in that: include: Communication Analysis: Triggering link fault detection based on the current link delay test results. Performing multi-dimensional analysis of the link to generate a normal evaluation coefficient. Based on the normal evaluation coefficient, the link fault condition is determined and the corresponding link switching operation is performed. Based on the determined link, communication with the operator and payment channel is connected. User interaction: Users interact with the front-end to implement recharge operation entry and information feedback; Business processing: handle recharge business and coordinate various modules to complete order life cycle management; Data management and analysis: Store data and provide analytical support to assist operational decision-making.
Citation Information
Patent Citations
Multi-channel network integrated payment system and multi-channel network integrated payment method
CN104240072A
Network payment technology channel management system for Unicom subscribers, merchants and third party payment channels
CN106529918A
All-path detection method, device and system
CN107800579A
Fault determination method and device of transaction link, equipment and storage medium
CN117834400A
Cross-border payment path optimization system and method based on multi-dimensional data analysis
CN120106854A