Channel account management methods and systems for distributed traffic platforms

Abstract

This invention discloses a channel account management method and system for a distributed traffic platform. The method configures corresponding discounts based on the amount range of each recharge after the channel account is topped up, enabling differentiated discounts for different recharge amounts within the same channel and achieving flexible control over channel discount configuration. Furthermore, it deducts funds from the channel account according to the first-to-recharge, calculating the deduction amount based on the discount corresponding to each recharge record, which encourages channels to increase recharge amounts. Simultaneously, it periodically synchronizes the remaining funds in the cache service to the database, triggering an alarm when the remaining balance of a channel account falls below a preset threshold to prevent insufficient account balance issues. This distributed traffic platform channel account management method effectively ensures the real-time performance, security, and flexible control of channel funds accounts.

Description

Technical Field

[0001] This invention relates to the field of channel account management technology, and in particular, to a channel account management method and system for a distributed traffic platform. Background Technology

[0002] The targeted traffic platform's channel accounts operate on a post-billing payment model, requiring channels to pre-deposit funds to ensure sufficient funds for payment. Billing occurs in real-time when a targeted traffic package is sold, and the corresponding amount is deducted from the channel's account. To accurately reflect changes in the fund account and ensure the accuracy of the channel's account balance, it is necessary to record the fund top-ups and usage processes in the channel account for fund account management. As business grows, a platform will generate more and more different types of business, necessitating the application of an account fund management system during operation.

[0003] Currently, conventional channel account management systems employ channel management and discount management. Channel management maintains channel information, while discount management stores discount tables. These tables contain discount IDs and discount rates, typically with several pre-configured fixed discount tiers. The discount tables are then linked to the channel information via discount IDs to configure channel discounts. Simultaneously, at the system implementation level, account data is stored in a relational database. When a charge is made, the remaining balance in the channel account is read from the relational database. If the account balance is sufficient to cover the charge, the user is topped up with data. After successful top-up, the amount is deducted from the account balance, and the account balance field in the relational database is updated.

[0004] Therefore, existing channel account management systems have the following drawbacks:

[0005] 1) The system's fund allocation management method is simplistic, and the discount strategy configuration is fixed;

[0006] 2) In a distributed environment, relational databases cannot accurately locate the number being recharged. If the channel initiates recharge repeatedly, it may activate targeted traffic for the same user repeatedly, resulting in duplicate deductions from the channel's account.

[0007] 3) By querying the channel account balance from the relational database and determining whether there is a remaining amount, the account limit cannot be shut down in real time. In a distributed concurrent scenario, when the channel account balance is insufficient, the channel account limit may become negative. Summary of the Invention

[0008] This invention provides a channel account management method and system for a distributed traffic platform to solve the technical problem of fixed discount strategy configuration in existing technologies.

[0009] According to one aspect of the present invention, a method for channel account management of a distributed traffic platform is provided, comprising the following:

[0010] Register a channel account on a targeted traffic platform;

[0011] Recharge channel accounts, save each recharge to the cache service of the targeted traffic platform and save the recharge record, and configure the corresponding discount according to the amount range of each recharge amount;

[0012] The channel provides users with targeted traffic subscription services, and the targeted traffic platform deducts money from the channel account according to the principle of first recharge and first consumption, and calculates the amount to be deducted based on the discount corresponding to each recharge when deducting money;

[0013] The system periodically updates the latest remaining amount of channel accounts in the cache service to the database. If the latest remaining amount is less than a preset threshold, an alarm is triggered.

[0014] Furthermore, the process of saving each recharge amount to the cache service of the targeted traffic platform and storing the recharge record specifically includes the following:

[0015] Enter the channel recharge amount in the targeted traffic platform and save it to the database, and change the recharge status to the entered status;

[0016] Review the entered data, and update the recharge status field to "reviewed" after the review is approved;

[0017] The database is scanned periodically. When the recharge status field of the scanned data is "approved" and the cache status is "not cached", the data is saved to the cache service.

[0018] Once the caching is successful, feedback will be provided on the recharge completion result.

[0019] Furthermore, the process by which channels provide targeted traffic subscription services to users includes the following:

[0020] When a user enters the channel's ordering page to purchase a targeted data package, the user pays the purchase fee to the channel. If the user successfully completes the payment, the channel's backend service receives the payment success notification and sends a request to the targeted data platform to order the targeted data package for the user.

[0021] After receiving an order request from a channel, the targeted traffic platform parses the request parameters, obtains the channel code, product code, and user mobile phone number, and calls the interface authentication service for authentication.

[0022] The targeted traffic platform uses the interface authentication service to determine whether the caller's IP is among the whitelisted IPs. If it is, it decrypts the data in the request parameters using the channel's key, obtains the timestamp in the parameters, and determines whether the timestamp meets the requirements. After successful authentication, it returns the authentication result and the decrypted data.

[0023] The traffic ordering service of the targeted traffic platform judges the authentication result. If the authentication is successful, it deducts the payment from the channel account through the account deduction service, and then calls the business support platform to activate the targeted traffic package for the user and receive the returned result. In the process of activating the targeted traffic package, the user's mobile phone number is used as a distributed transaction lock. The lock is acquired when the ordering begins and released after the recharge is completed.

[0024] The targeted traffic platform's traffic subscription service determines the subscription result and saves the subscription trajectory. If the subscription is successfully generated, the subscription relationship and subscription log are generated in the targeted traffic platform.

[0025] The targeted traffic platform's traffic subscription service returns the subscription results to the channel platform, which then returns the subscription results to the user.

[0026] Furthermore, the process of deducting funds from the channel account through the account deduction service is specifically as follows:

[0027] The traffic subscription service of the targeted traffic platform initiates a quota usage request to the account deduction service. After receiving the request, the account deduction service directly deducts the amount to be deducted from the total amount of the channel account, and returns the usage result to the traffic subscription service after the quota usage is completed.

[0028] Furthermore, the calculation method for the amount to be deducted this time is as follows:

[0029] The user's recharge record is retrieved from the cache service based on the channel code and product code. The earliest remaining recharge record is selected according to the principle of first-come, first-served. The amount to be deducted is calculated based on the discount corresponding to the recharge record. If the calculated amount to be deducted does not exceed the remaining amount of the earliest recharge record, the amount to be deducted is deducted directly. Otherwise, the next recharge record is consumed, and the amount to be deducted is recalculated based on the discount corresponding to the next recharge record.

[0030] Furthermore, after deducting the amount due for this transaction, it is determined whether the remaining amount in the current recharge record is less than a preset threshold. If so, the next recharge record is consumed. If all recharge records have been consumed, the channel account is promptly shut down and the channel platform is notified to recharge.

[0031] Furthermore, if subsequent data subscriptions fail, the following will also apply:

[0032] After receiving a failed subscription result, the traffic subscription service of the targeted traffic platform initiates an account recovery request to the account recovery service. Upon receiving the request, the account recovery service restores the amount that should have been deducted to the channel account, updates the channel account amount in the cache service, and sends the recovery result back to the channel platform.

[0033] Furthermore, the following is included before deducting funds from the channel account:

[0034] The system queries the channel account balance based on the channel code, determines whether the balance is sufficient to cover the deduction, and if insufficient, shuts down the channel account and reports this to the channel platform. During the account balance query process, the system uses the user's mobile phone number as a distributed transaction lock and releases the lock after the query is complete.

[0035] Furthermore, the process of periodically updating the latest remaining amount of the channel account in the cache service to the database, and triggering an alarm if the latest remaining amount is less than a preset threshold, specifically involves:

[0036] The scheduled task service of the targeted traffic platform queries the latest remaining amount of each recharge record from the cache service every few minutes and updates it to the database. It determines the remaining amount of each recharge record. If it is determined to be the last recharge record and the remaining amount is less than a preset threshold, an alarm is triggered and the warning information is fed back to the operation and management personnel of the targeted traffic platform and the management personnel of the channel account.

[0037] In addition, the present invention also provides a channel account management system for a distributed traffic platform, comprising:

[0038] The account registration module is used to register channel accounts on targeted traffic platforms.

[0039] The account recharge module is used to recharge channel accounts. It saves each recharge to the cache service of the targeted traffic platform and stores the recharge record. It also configures the corresponding discount based on the amount range of each recharge.

[0040] The traffic subscription module is used to provide targeted traffic subscription services to users through channels. The targeted traffic platform deducts money from the channel account according to the principle of first recharge and first consumption, and calculates the amount to be deducted based on the discount corresponding to each recharge when deducting money.

[0041] The account alert module is used to periodically update the latest remaining amount of channel accounts in the cache service to the database. If the latest remaining amount is less than a preset threshold, an alert is triggered.

[0042] The present invention has the following effects:

[0043] The channel account management method of the distributed traffic platform of this invention saves each recharge to the cache service of the targeted traffic platform after the channel account is recharged, and maintains the recharge record. It configures corresponding discounts based on the amount range of each recharge, enabling differentiated discount methods for different recharge amounts from the same channel, and achieving flexible control over channel discount configuration. Furthermore, during the traffic subscription service, the channel account is deducted according to the first-come, first-served principle, and the amount to be deducted is calculated based on the discount corresponding to each recharge record, which encourages channels to increase recharge amounts. Simultaneously, the remaining amount in the cache service is periodically synchronized to the database. When the remaining balance of a channel account is found to be less than a preset threshold, an alarm is triggered to prevent insufficient account balance. The channel account management method of the distributed traffic platform of this invention can effectively ensure the real-time performance, security, and flexible control of channel funds accounts.

[0044] In addition, the channel account management system of the distributed traffic platform of the present invention also has the above-mentioned advantages.

[0045] In addition to the objectives, features, and advantages described above, the present invention has other objectives, features, and advantages. The invention will now be described in further detail with reference to the figures. Attached Figure Description

[0046] The accompanying drawings, which form part of this application, are used to provide a further understanding of the invention. The illustrative embodiments of the invention and their descriptions are used to explain the invention and do not constitute an undue limitation of the invention. In the drawings:

[0047] Figure 1 This is a flowchart illustrating the channel account management method of a distributed traffic platform according to a preferred embodiment of the present invention.

[0048] Figure 2 yes Figure 1 A schematic diagram of the sub-process of step S2.

[0049] Figure 3 This is a schematic diagram of the business process for recharging channel accounts in a preferred embodiment of the present invention.

[0050] Figure 4 yes Figure 1 A schematic diagram of the sub-process of step S4.

[0051] Figure 5 This is a schematic diagram of the business process for providing traffic subscription services to users through a channel in a preferred embodiment of the present invention.

[0052] Figure 6 This is a schematic diagram of the business process for verifying the balance of a channel account in a preferred embodiment of the present invention.

[0053] Figure 7 This is a schematic diagram of the business process for deducting funds from a channel account in a preferred embodiment of the present invention.

[0054] Figure 8 This is a schematic diagram of the business process for restoring the credit limit of a channel account after a traffic subscription failure, as described in a preferred embodiment of the present invention.

[0055] Figure 9 This is a schematic diagram of the business process for providing balance warnings for channel accounts in a preferred embodiment of the present invention.

[0056] Figure 10 This is a schematic diagram of the module structure of the channel account management system of the distributed traffic platform according to another embodiment of the present invention. Detailed Implementation

[0057] The embodiments of the present invention will be described in detail below with reference to the accompanying drawings. However, the present invention can be implemented in many different ways as defined and covered below.

[0058] like Figure 1 As shown, a preferred embodiment of the present invention provides a channel account management method for a distributed traffic platform, including the following:

[0059] Step S1: Register a channel account on the targeted traffic platform;

[0060] Step S2: Top up the channel account, save each top-up to the cache service of the targeted traffic platform and save the top-up record, and configure the corresponding discount according to the amount range of each top-up amount;

[0061] Step S3: The channel provides users with targeted traffic subscription services, and the targeted traffic platform deducts money from the channel account according to the principle of first recharge first consumption, and calculates the amount to be deducted based on the discount corresponding to each recharge when deducting money;

[0062] Step S4: Periodically update the latest remaining amount of the channel account in the cache service to the database. If the latest remaining amount is less than the preset threshold, trigger an alarm.

[0063] It is understood that the channel account management method of the distributed traffic platform in this embodiment saves each recharge to the cache service of the targeted traffic platform after the channel account is recharged, and stores the recharge record. It also configures corresponding discounts based on the amount range of each recharge, enabling differentiated discount methods for different recharge amounts from the same channel, thus achieving flexible control over channel discount configuration. Furthermore, during the traffic subscription service, the channel account is deducted according to the principle of first-come, first-served, and the amount to be deducted is calculated based on the discount corresponding to each recharge record, which encourages channels to increase their recharge amounts. Simultaneously, the remaining amount in the cache service is periodically synchronized to the database. When the remaining balance of a channel account is found to be less than a preset threshold, an alarm is triggered to prevent insufficient account balance. The channel account management method of the distributed traffic platform of this invention can effectively ensure the real-time performance, security, and flexible control of channel funds accounts.

[0064] It is understood that in step S1, when a channel accesses the targeted traffic platform, it needs to register by entering its information on the platform. After the channel information undergoes two levels of review, the channel's status is updated to "enabled," indicating successful registration. Only channels in the "enabled" state can call the traffic package recharge interface. The channel account registry is shown in Table 1.

[0065] Table 1. Channel Account Registration Form

[0066]

[0067] It is understood that in step S2, when the channel account balance is insufficient, the channel platform needs to replenish the channel account. For example, Figure 2 As shown, the process of saving each recharge amount to the cache service of the targeted traffic platform and saving the recharge record specifically includes the following:

[0068] Step S21: Enter the channel recharge amount in the targeted traffic platform and save it to the database, and change the recharge status to the entry status;

[0069] Step S22: Review the entered data. Once the review is approved, update the recharge status field to "Reviewed".

[0070] Step S23: Periodically scan the database. When the recharge status field of the scanned data is "approved" and the cache status is "not cached", save the data to the cache service.

[0071] Step S24: After successful caching, provide feedback on the recharge completion result.

[0072] Specifically, such as Figure 3As shown, the operations and management personnel of the targeted traffic platform enter the channel recharge amount into the targeted traffic management platform. The entered channel recharge amount is saved to the database, and the recharge status is at this time "entered". Then, after review, the recharge status field is updated to "reviewed". The scheduled task system of the targeted traffic platform scans the database at regular intervals. When the recharge status field of a certain recharge data is "reviewed" and the cache status is "not cached data", the scheduled task system saves the read data to the cache service and receives the result synchronized to the cache service. After receiving the result of successful caching, the scheduled task system sends the recharge completion result to the operations and management personnel and channel management personnel via SMS.

[0073] Understandably, after successful caching, the targeted traffic platform will save recharge records to record the type and amount of each channel recharge. The channel recharge types include two categories: top-up and credit extension. The specific account recharge record table is shown in Table 2.

[0074] Table 2. Channel Account Recharge Record Table

[0075]

[0076]

[0077] It is understood that in step S3, as Figure 4 As shown, the process by which a channel provides targeted traffic subscription services to users includes the following:

[0078] Step S41: The user enters the channel's order page to purchase a targeted traffic package. The user pays the purchase fee to the channel. If the user successfully completes the payment, the channel's backend service receives the payment success notification and sends a request to the targeted traffic platform to order the targeted traffic package for the user.

[0079] Step S42: After receiving the order request from the channel, the targeted traffic platform parses the request parameters, obtains the channel code, product code and user mobile phone number, and calls the interface authentication service to perform authentication;

[0080] Step S43: The targeted traffic platform uses the interface authentication service to determine whether the caller's IP is among the IPs reported in the whitelist. If so, it decrypts the data in the request parameters using the key of that channel, obtains the timestamp in the parameters, and determines whether the timestamp meets the requirements. After successful authentication, it returns the authentication result and the decrypted data.

[0081] Step S44: The traffic ordering service of the targeted traffic platform judges the authentication result. If the authentication is successful, the channel account is deducted through the account deduction service. Then, the business support platform is called to activate the targeted traffic package for the user and receive the return result. In the process of activating the targeted traffic package, the user's mobile phone number is used as a distributed transaction lock. The lock is acquired when the ordering starts and released after the recharge is completed.

[0082] Step S45: The traffic ordering service of the targeted traffic platform judges the ordering result and saves the ordering trajectory. If the order is successfully generated, the ordering relationship and ordering log are generated in the targeted traffic platform.

[0083] Step S46: The traffic ordering service of the targeted traffic platform returns the ordering results to the channel platform, and the channel platform returns the ordering results to the user.

[0084] Specifically, such as Figure 5 As shown, the user first enters the channel's order page to purchase a targeted data package. The user pays the purchase fee to the channel. If the user successfully completes the payment, the channel's backend service will receive a payment success notification. The channel's backend service sends an API service request to the targeted data platform to order the targeted data package for the user. After receiving the order request from the channel, the targeted data platform's data ordering service parses the request parameters, obtains relevant information, including the channel code, product code, and user's mobile phone number, and calls the API authentication service for authentication. The API authentication service determines whether the caller's IP is among the whitelisted IPs. If it is, it decrypts the request parameter data using the channel's key, obtains the timestamp in the parameters, and determines whether the timestamp meets the requirements. After successful authentication, it returns the authentication result and the decrypted data to the data ordering service. The data ordering service checks the authentication result. If authentication is successful, it pre-deducts payment from the channel account. After pre-deduction, it calls the China Unicom business support system to activate the targeted data package for the user and receives the data recharge result returned by the China Unicom business support system. In the process of activating targeted data packages, the user's mobile phone number is used as a distributed transaction lock. The lock is acquired at the start of the subscription and released after the payment is completed, effectively preventing duplicate charges caused by repeated data package subscriptions submitted by the channel. The targeted data platform's data subscription service determines the subscription result and saves the subscription history. If the subscription is successful, a subscription relationship and subscription log are generated in the targeted data platform, and the subscription result is returned to the channel interface. The channel platform then feeds back the data package payment result to the user.

[0085] Understandably, the following steps are included before deducting funds from the channel account:

[0086] The system queries the channel account balance based on the channel code, determines whether the balance is sufficient to cover the deduction, and if insufficient, shuts down the channel account and reports this to the channel platform. During the account balance query process, the system uses the user's mobile phone number as a distributed transaction lock and releases the lock after the query is complete.

[0087] Specifically, such as Figure 6 As shown, after a user enters the channel's front-end page to purchase a targeted data package and pays the purchase fee to the channel, if the user successfully completes the payment, the channel's back-end service will receive a payment success notification. Then, the channel's interface service sends a request to the targeted data platform to order the targeted data package. Upon receiving the order request from the channel, the targeted data platform's data ordering service parses the parameters in the request to obtain relevant information, including the channel code, product code, and user's mobile phone number. After saving the collected information as a recharge call detail record, it calls the credit limit authentication service. Upon receiving the request, the credit limit authentication service queries the channel account balance in the data cache service based on the channel code. After reading the account balance, it determines whether it is sufficient to pay for the current deduction. If it is insufficient, the channel account is closed and feedback is sent to the channel platform; if it is sufficient, the pre-deduction is performed directly. Furthermore, during the account balance query process, the user's mobile phone number is used as a distributed transaction lock for locking. After the query is completed, the lock is released to prevent the account balance from being updated out of time. The credit limit authentication service feeds back the authentication result to the data subscription service. If the data subscription service determines that the channel account has sufficient balance, it initiates a data top-up request to the China Unicom business support system and returns the top-up result to the channel platform. By authenticating the channel account's credit limit usage in real time before data top-up, if the threshold is exceeded, the credit limit is promptly controlled and restricted, preventing the channel from topping up any more data packages.

[0088] It is understood that the process of deducting funds from the channel account through the account deduction service specifically involves:

[0089] The traffic subscription service of the targeted traffic platform initiates a quota usage request to the account deduction service. After receiving the request, the account deduction service directly deducts the amount to be deducted from the total amount of the channel account, and returns the usage result to the traffic subscription service after the quota usage is completed.

[0090] Specifically, such as Figure 7As shown, after a user enters the channel's front-end page to purchase a targeted data package and pays the purchase fee to the channel, if the user successfully completes the payment, the channel's back-end service will receive a payment success notification. Then, the channel's interface service sends a request to the targeted data platform to order the targeted data package. Upon receiving the order request from the channel, the targeted data platform's data ordering service parses the parameters in the request to obtain relevant information, including the channel code, product code, and user's mobile phone number. After completing account credit limit authentication, the targeted data platform's data ordering service initiates a credit limit occupancy request to the account deduction service. Upon receiving the request, the account deduction service directly deducts the amount due from the channel's total account balance to complete the credit limit occupancy. After successful deduction, it saves the occupancy information and returns the occupancy result to the data ordering service. The data ordering service then initiates a data ordering request to the China Unicom business support platform and receives the ordering result.

[0091] The calculation method for the amount to be deducted this time is as follows:

[0092] The user's recharge record is retrieved from the cache service based on the channel code and product code. The earliest remaining recharge record is selected according to the principle of first-come, first-served. The amount to be deducted is calculated based on the discount corresponding to the recharge record. If the calculated amount to be deducted does not exceed the remaining amount of the earliest recharge record, the amount to be deducted is deducted directly. Otherwise, the next recharge record is consumed, and the amount to be deducted is recalculated based on the discount corresponding to the next recharge record.

[0093] Optionally, after deducting the amount due for this transaction, it is determined whether the remaining amount in the current recharge record is less than a preset threshold. If so, the next recharge record is consumed. If all recharge records have been consumed, the channel account is closed in a timely manner and the channel platform is notified to recharge.

[0094] Optionally, if subsequent data subscriptions fail, the following may also be included:

[0095] After receiving a failed subscription result, the traffic subscription service of the targeted traffic platform initiates an account recovery request to the account recovery service. Upon receiving the request, the account recovery service restores the amount that should have been deducted to the channel account, updates the channel account amount in the cache service, and sends the recovery result back to the channel platform.

[0096] Specifically, such as Figure 8 As shown, when the traffic subscription service receives a subscription failure result, it initiates an account recovery request to the account recovery service to refund the deduction to the channel account. Upon receiving the request, the account recovery service restores the amount due to the channel account, updates the channel account amount in the cache service, and sends the recovery result back to the channel platform.

[0097] It can be understood that in step S4, the process of periodically updating the latest remaining amount of the channel account in the cache service to the database, and triggering an alarm if the latest remaining amount is less than a preset threshold, specifically involves:

[0098] The scheduled task service of the targeted traffic platform queries the latest remaining amount of each recharge record from the cache service every few minutes and updates it to the database. It determines the remaining amount of each recharge record. If it is determined to be the last recharge record and the remaining amount is less than a preset threshold, an alarm is triggered and the warning information is fed back to the operation and management personnel of the targeted traffic platform and the management personnel of the channel account.

[0099] Specifically, such as Figure 9 As shown, the scheduled task service of the targeted traffic platform queries the latest remaining amount of each recharge record from the cache service every few minutes and updates it to the database. It judges the remaining amount of each recharge record. If it is determined to be the last recharge record and the remaining amount is less than the preset threshold, an alarm is triggered. The scheduled task service also feeds back the warning information to the operation and management personnel of the targeted traffic platform and the management personnel of the channel account to complete the balance warning and prevent insufficient account balance.

[0100] In addition, such as Figure 10 As shown, another embodiment of the present invention also provides a channel account management system for a distributed traffic platform, preferably employing the channel account management method described above. The system includes:

[0101] The account registration module is used to register channel accounts on targeted traffic platforms.

[0102] The account recharge module is used to recharge channel accounts. It saves each recharge to the cache service of the targeted traffic platform and stores the recharge record. It also configures the corresponding discount based on the amount range of each recharge.

[0103] The traffic subscription module is used to provide targeted traffic subscription services to users through channels. The targeted traffic platform deducts money from the channel account according to the principle of first recharge and first consumption, and calculates the amount to be deducted based on the discount corresponding to each recharge when deducting money.

[0104] The account alert module is used to periodically update the latest remaining amount of channel accounts in the cache service to the database. If the latest remaining amount is less than a preset threshold, an alert is triggered.

[0105] It is understood that the channel account management system of the distributed traffic platform in this embodiment saves each recharge to the cache service of the targeted traffic platform after the channel account is recharged, and stores the recharge record. It also configures corresponding discounts based on the amount range of each recharge, enabling differentiated discount methods for different recharge amounts from the same channel, thus achieving flexible control over channel discount configuration. Furthermore, during the traffic subscription service, the channel account is deducted according to the principle of first-come, first-served, and the amount to be deducted is calculated based on the discount corresponding to each recharge record, which encourages channels to increase their recharge amounts. Simultaneously, the remaining amount in the cache service is periodically synchronized to the database. When the remaining balance of a channel account is found to be less than a preset threshold, an alarm is triggered to prevent insufficient account balance. The channel account management method of the distributed traffic platform of this invention can effectively ensure the real-time performance, security, and flexible control of channel funds accounts.

[0106] It is understood that each module in the system of this embodiment corresponds to each step in the above method embodiment. Therefore, the specific working principle of each module will not be repeated here. Please refer to the steps of the above method embodiment.

[0107] The above description is merely a preferred embodiment of the present invention and is not intended to limit the invention. Various modifications and variations can be made to the present invention by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the scope of protection of the present invention.

[0108] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code. The solutions in the embodiments of this application can be implemented in various computer languages, such as the object-oriented programming language Java and the interpreted scripting language JavaScript.

[0109] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0110] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0111] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0112] Although preferred embodiments of this application have been described, those skilled in the art, upon learning the basic inventive concept, can make other changes and modifications to these embodiments. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments as well as all changes and modifications falling within the scope of this application.

[0113] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the spirit and scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

Claims

1. A method for managing channel accounts of a distributed traffic platform, characterized in that, Includes the following: Register a channel account on a targeted traffic platform; Recharge channel accounts, save each recharge to the cache service of the targeted traffic platform and save the recharge record, and configure the corresponding discount according to the amount range of each recharge amount; The channel provides users with targeted traffic subscription services, and the targeted traffic platform deducts money from the channel account according to the principle of first recharge and first consumption, and calculates the amount to be deducted based on the discount corresponding to each recharge when deducting money; The system periodically updates the latest remaining amount of channel accounts in the cache service to the database. If the latest remaining amount is less than a preset threshold, an alarm is triggered. The process by which a channel provides targeted traffic subscription services to users includes the following: When a user enters the channel's ordering page to purchase a targeted data package, the user pays the purchase fee to the channel. If the user successfully completes the payment, the channel's backend service receives the payment success notification and sends a request to the targeted data platform to order the targeted data package for the user. After receiving an order request from a channel, the targeted traffic platform parses the request parameters, obtains the channel code, product code, and user mobile phone number, and calls the interface authentication service for authentication. The targeted traffic platform uses the interface authentication service to determine whether the caller's IP is among the whitelisted IPs. If it is, it decrypts the data in the request parameters using the channel's key, obtains the timestamp in the parameters, and determines whether the timestamp meets the requirements. After successful authentication, it returns the authentication result and the decrypted data. The traffic ordering service of the targeted traffic platform judges the authentication result. If the authentication is successful, it deducts the payment from the channel account through the account deduction service, and then calls the business support platform to activate the targeted traffic package for the user and receive the returned result. In the process of activating the targeted traffic package, the user's mobile phone number is used as a distributed transaction lock. The lock is acquired when the ordering begins and released after the recharge is completed. The targeted traffic platform's traffic subscription service determines the subscription result and saves the subscription trajectory. If the subscription is successfully generated, the subscription relationship and subscription log are generated in the targeted traffic platform. The targeted traffic platform's traffic subscription service returns the subscription results to the channel platform, which then returns the subscription results to the user.

2. The channel account management method for a distributed traffic platform as described in claim 1, characterized in that, The process of saving each recharge to the cache service of the targeted traffic platform and storing the recharge record specifically includes the following: Enter the channel recharge amount in the targeted traffic platform and save it to the database, and change the recharge status to the entered status; Review the entered data, and update the recharge status field to "reviewed" after the review is approved; The database is scanned periodically. When the recharge status field of the scanned data is "approved" and the cache status is "not cached", the data is saved to the cache service. Once the caching is successful, feedback will be provided on the recharge completion result.

3. The channel account management method for a distributed traffic platform as described in claim 1, characterized in that, The process of deducting funds from the channel account through the account deduction service is as follows: The traffic subscription service of the targeted traffic platform initiates a quota usage request to the account deduction service. After receiving the request, the account deduction service directly deducts the amount to be deducted from the total amount of the channel account, and returns the usage result to the traffic subscription service after the quota usage is completed.

4. The channel account management method for a distributed traffic platform as described in claim 3, characterized in that, The calculation method for the amount to be deducted this time is as follows: The user's recharge record is retrieved from the cache service based on the channel code and product code. The earliest remaining recharge record is selected according to the principle of first-come, first-served. The amount to be deducted is calculated based on the discount corresponding to the recharge record. If the calculated amount to be deducted does not exceed the remaining amount of the earliest recharge record, the amount to be deducted is deducted directly. Otherwise, the next recharge record is consumed, and the amount to be deducted is recalculated based on the discount corresponding to the next recharge record.

5. The channel account management method for a distributed traffic platform as described in claim 4, characterized in that, After deducting the amount due for this transaction, determine whether the remaining amount in the current recharge record is less than a preset threshold. If so, consume the next recharge record. If all recharge records have been consumed, promptly close the channel account and notify the channel platform to recharge.

6. The channel account management method for a distributed traffic platform as described in claim 3, characterized in that, If subsequent data subscriptions fail, the following will also apply: After receiving a failed subscription result, the traffic subscription service of the targeted traffic platform initiates an account recovery request to the account recovery service. Upon receiving the request, the account recovery service restores the amount that should have been deducted to the channel account, updates the channel account amount in the cache service, and sends the recovery result back to the channel platform.

7. The channel account management method for a distributed traffic platform as described in claim 3, characterized in that, The following also applies before deducting funds from the channel account: The system queries the channel account balance based on the channel code, determines whether the balance is sufficient to cover the deduction, and if insufficient, shuts down the channel account and reports this to the channel platform. During the account balance query process, the system uses the user's mobile phone number as a distributed transaction lock and releases the lock after the query is complete.

8. The channel account management method for a distributed traffic platform as described in claim 1, characterized in that, The process of periodically updating the latest remaining amount of the channel account in the cache service to the database, and triggering an alarm if the latest remaining amount is less than a preset threshold, is as follows: The scheduled task service of the targeted traffic platform queries the latest remaining amount of each recharge record from the cache service every few minutes and updates it to the database. It determines the remaining amount of each recharge record. If it is determined to be the last recharge record and the remaining amount is less than a preset threshold, an alarm is triggered and the warning information is fed back to the operation and management personnel of the targeted traffic platform and the management personnel of the channel account.

9. A channel account management system for a distributed traffic platform, employing the channel account management method for a distributed traffic platform as described in any one of claims 1 to 8, characterized in that, include: The account registration module is used to register channel accounts on targeted traffic platforms. The account recharge module is used to recharge channel accounts. It saves each recharge to the cache service of the targeted traffic platform and stores the recharge record. It also configures the corresponding discount based on the amount range of each recharge. The traffic subscription module is used to provide targeted traffic subscription services to users through channels. The targeted traffic platform deducts money from the channel account according to the principle of first recharge and first consumption, and calculates the amount to be deducted based on the discount corresponding to each recharge when deducting money. The account alert module is used to periodically update the latest remaining amount of channel accounts in the cache service to the database. If the latest remaining amount is less than a preset threshold, an alert is triggered.

Images