Intelligent system and method based on user recharge flow

Abstract

The invention discloses an intelligent system and method based on user recharge flow, and belongs to the technical field of mobile communication and electronic commerce crossing. The system comprises a user identification module, a package management module, a rule engine module and a page generation module, and further comprises a balance management module and a member management module which are used for collaboration. The method depends on the system, and the whole process of obtaining ICCID analysis equipment characteristics of a user, matching a package, verifying a multi-dimensional rule and generating a personalized dynamic interface is executed in sequence. By constructing a multi-dimensional package system and combining dynamic rule management and control, ICCID-driven differential adaptation and a cross-system linkage mechanism, the problems of package homogenization, marketing risk control deficiency, interface static solidification and the like of an existing flow recharging system are solved; the technical effects of improving the flow recharging service conversion rate, accurately preventing and controlling the marketing risk, and optimizing the user experience and the operation refinement level are achieved.

Description

TECHNICAL FIELD

[0001] The present application belongs to the technical field of mobile communication and electronic commerce, and particularly relates to an intelligent system and method based on user traffic recharge. BACKGROUND

[0002] With the deep integration of mobile communication technology and electronic commerce, traffic, as a core communication resource of users, its recharge service has become a key business module of operators and Internet platforms. Although the traffic recharge system in the current market can meet the basic traffic purchase needs of users, there are still significant technical defects in user personalized services, marketing risk control, interface dynamic adaptation, and cross-scene experience collaboration, which are difficult to adapt to the current needs of fine operation and user experience upgrade. The specific problems are as follows:

[0003] Firstly, the package is seriously homogenized and cannot match the differentiated needs of users. The existing traffic recharge system only provides general traffic packages and does not design them differently for user types (such as new registered users, campus users, and high-value member users) and use scenarios (such as regional exclusive needs and night traffic needs), resulting in insufficient first-time charging attraction for new users and lack of targeted options for old user renewal, which cannot distinguish between new user first-time charging needs and old user renewal needs, and also cannot achieve precise user stratified operation.

[0004] Secondly, the rule control mechanism is missing, which easily leads to marketing risks and resource waste. The existing system lacks dynamic control ability for package purchase behavior, which cannot limit the number of package purchases (such as repeatedly purchasing a special package for the same device), nor can it limit payment methods (such as requiring a specific payment channel for a special package) and sales time periods (such as time-limited listing of holiday exclusive packages), which makes marketing activities vulnerable to malicious scalping. At the same time, due to the lack of a dynamic rules engine, it cannot intercept irregular operations such as "multiple purchases of a special package for the same device" in real time, resulting in a large amount of marketing resources being wasted.

[0005] Thirdly, the page display is static and fixed, and cannot be dynamically adapted based on device characteristics. The existing traffic recharge page content is fixed and only displays package lists in a single form to all users, without adjusting the display content based on user device characteristics (such as device home location, user type, and operator network information). Since the device identifier is not used to analyze the home location and user type, the accuracy of regional package recommendations is low, and it is not possible to provide a "thousand faces for a thousand people" recharge interface for different regions and different types of users, which not only affects user selection efficiency but also restricts the improvement of conversion effect.

[0006] Finally, the member system is disconnected with the balance prepayment function, and the user experience is poor. In the existing system, the member level is not directly related to the traffic recharge discount, and the high-level member cannot enjoy the exclusive package benefits. At the same time, the user's pre-stored account balance cannot directly offset the traffic package cost, and needs to be realized through multi-step jump or additional operation to use the balance, resulting in that the value of member benefits is not fully played, the practicality of the balance prepayment function is reduced, the experience fault of "member, recharge, balance" is formed, and the overall use of the user is affected.

[0007] In summary, the technical defects of the existing traffic recharge system in the four core dimensions of "personalized service, risk control, dynamic adaptation, and experience synergy" have become the key bottleneck restricting the improvement of traffic recharge business conversion rate, marketing risk prevention and control, and user experience optimization. An intelligent traffic recharge scheme with precise user identification, dynamic rule control and cross-system collaboration capability is needed to solve the above technical problems. SUMMARY

[0008] In view of the deficiencies of the existing related prior art, the present application provides an intelligent system and method based on user recharge traffic, aiming to solve the core deficiencies of the existing traffic recharge system, such as the inability of package homogenization to adapt to user differentiation needs, the lack of rule control leading to marketing risks and resource waste, the difficulty of page static solidification to achieve accurate recommendation, the disconnection of member system and balance prepayment function leading to poor user experience, and ultimately achieving the overall effect of improving traffic recharge business conversion rate, effectively preventing marketing activity risks, improving regional package recommendation accuracy, optimizing user experience, and enhancing the level of operation refinement.

[0009] To achieve the above purpose, the first aspect of the present application provides an intelligent system based on user recharge traffic, comprising: a user identification module for receiving user equipment ICCID information and access context carried by the user when initiating a traffic recharge request, analyzing the ICCID information to obtain user equipment features, and generating a user equipment feature portrait;

[0010] A package management module is in communication connection with the user identification module, for receiving the user equipment feature portrait, matching the adaptive traffic package according to the preset package strategy matrix, and generating a personalized package candidate list;

[0011] A rule engine module is in communication connection with the package management module and the user operation terminal respectively, for receiving the personalized package candidate list and the user's current operation information, performing rule verification on each package in the personalized package candidate list, and outputting the personalized package list that passes the verification;

[0012] A page generation module, in communication with the rule engine module and the user operation terminal respectively, is configured to receive the list of personalized packages and the user equipment characteristic profile, and generate and output a traffic recharge interface adapted to the dynamic template;

[0013] The access context includes at least current time and geographic location information, and the user equipment characteristic includes at least equipment home location, user type and operator network information, and the user current operation information includes at least a request package ID, a proposed payment method and user identity information.

[0014] Further, the traffic package matched by the package management module includes a general package, a first recharge package, a preferential package, a gift package and an experience package, and the package strategy matrix defines the adaptation relationship and priority of different equipment characteristics and various types of traffic packages.

[0015] Further, the rule verification performed by the rule engine module includes at least purchase limit verification, payment verification, time limit verification and user state verification; the purchase limit verification checks the historical purchase times of the target package by the user or the associated equipment and account, the payment verification checks whether the proposed payment method of the user meets the payment requirements of the target package, the time limit verification checks whether the current time is within the sales period of the target package, and the user state verification checks whether the user membership level and account status meet the use requirements of the target package.

[0016] Further, when the user identification module analyzes the ICCID information, the user equipment characteristic is obtained through a built-in rule library or by calling a third-party operator information interface;

[0017] When the page generation module generates the traffic recharge interface, the interface display form is adapted according to the user equipment type, and the user equipment type includes at least a mobile terminal App, a mini program and an H5 page; the traffic recharge interface is integrated with user account balance display, balance deduction options and membership level benefit information.

[0018] Further, it further includes a balance management module in communication with the page generation module and the package management module, configured to store user pre-stored balance information, support deduction of the pre-stored balance for traffic package fees, and push the user pre-stored balance information to the page generation module;

[0019] It further includes a membership management module in communication with the rule engine module and the page generation module, configured to store user membership level information, provide the user membership level to the rule engine module to perform user state verification, and push user membership level benefit information to the page generation module.

[0020] Further, the rule engine module is constructed in a manner of combining a rule-based decision model with real-time event stream processing technology, and the verification rules stored in the rule engine module are configured in a declarative or DSL form, and dynamic addition, deletion and modification are supported.

[0021] The second aspect of the application provides an intelligent method based on user traffic top-up, which is implemented by using the intelligent system based on user traffic top-up as described above, and includes the following steps:

[0022] Receiving a traffic top-up request initiated by a user, obtaining user equipment ICCID information and access context carried in the traffic top-up request;

[0023] Analyzing the ICCID information by the user identification module to obtain user equipment characteristics, and generating a user equipment characteristic portrait based on the user equipment characteristics;

[0024] Using the package management module, combining a preset package strategy matrix and the user equipment characteristic portrait, matching an adaptive traffic package, and generating a personalized package candidate list;

[0025] Receiving user current operation information by the rule engine module, performing rule verification on each traffic package in the personalized package candidate list, and obtaining a personalized package list that passes the verification;

[0026] Generating and outputting an adaptive traffic top-up interface by means of the page generation module, combining the personalized package list that passes the verification and the user equipment characteristic portrait;

[0027] The access context at least includes current time and geographic location information, the user equipment characteristics at least include device home location, user type and operator network information, and the user current operation information at least includes request package ID, proposed payment method and user identity information.

[0028] Further, in the step of combining the preset package strategy matrix and the user equipment characteristic portrait, matching an adaptive traffic package, and generating a personalized package candidate list, the matched traffic package includes a general package, a first top-up package, a preferential package, a gift package and an experience package, and the package strategy matrix defines the adaptive relationship and priority of different user equipment characteristics and each type of traffic package.

[0029] Further, the step of performing rule verification on each traffic package in the personalized package candidate list at least includes the following operations:

[0030] Purchase limit verification, in which the rule engine module checks the historical purchase times of the target traffic package by the user or associated equipment and account;

[0031] Payment verification, whether the user's selected payment method meets the payment requirements of the target traffic package is checked by the rule engine module;

[0032] Time verification, whether the current time is in the sales period of the target traffic package is checked by the rule engine module;

[0033] User state verification, whether the user's membership level and account status meet the use requirements of the target traffic package is checked by the rule engine module.

[0034] Further, the step of analyzing the ICCID information to obtain user equipment characteristics is to analyze the ICCID information through a built-in rule library or to call a third-party operator information interface to analyze the ICCID information to obtain user equipment characteristics.

[0035] In the step of generating and outputting the adapted traffic recharge interface, the page generation module adapts the display form of the traffic recharge interface according to the user equipment type, and the user equipment type at least includes a mobile terminal App, a small program, and an H5 page; and the traffic recharge interface is integrated with user account balance display, balance deduction options, and membership level benefit information.

[0036] Further, before generating and outputting the adapted traffic recharge interface, it further includes:

[0037] The balance management module stores user pre-stored balance information, performs deduction on traffic package costs based on the pre-stored balance information, and pushes the user pre-stored balance information to the page generation module.

[0038] Further, before the step of performing rule verification on each traffic package in the personalized package candidate list, it further includes:

[0039] The membership management module stores user membership level information, performs user state verification based on the user membership level information, and pushes user membership level benefit information to the page generation module.

[0040] Further, when performing rule verification, the rule engine module adopts a combination of a rule-based decision model and real-time event stream processing technology, and the verification rules are configured in a declarative or domain-specific language (DSL) form, supporting dynamic addition, deletion, and modification.

[0041] The above technical scheme is adopted in the present application, and the specific beneficial effects are as follows:

[0042] The application constructs a multi-dimensional traffic package system comprising a general package, a first charging package, a preferential package, a gift package and an experience package, defines the adaptation relationship and priority of different device features and various traffic packages relying on a preset package strategy matrix, and combines the user device feature portrait generated by a user identification module, so that the package management module can accurately match the differentiated traffic recharge needs of new registered user first charging, old user top-up and member exclusive, realize user stratified operation, and improve the traffic recharge business conversion rate.

[0043] The application performs four types of dynamic verification, including purchase limit verification, payment verification, time limit verification and user state verification, by means of a rule engine module: the purchase limit verification checks the historical purchase times of a user or associated device and account for a target package; the payment verification checks whether the payment method selected by the user meets the payment requirements of the target package; the time limit verification checks whether the current time is within the sales period of the target package; and the user state verification checks whether the user membership level and account state meet the use requirements of the target package. At the same time, the rule engine module is constructed in a manner combining a rule-based decision model and real-time event stream processing technology, the verification rules are configured in a declarative or domain-specific language (DSL) form and support dynamic addition, deletion and modification, can real-time intercept irregular operations such as multiple purchases of preferential packages by the same device, accurately prevent and control marketing activity risks, reduce invalid consumption of marketing resources, and improve the flexibility and accuracy of marketing control.

[0044] The application analyzes user device attribution, user type, operator network and other information based on ICCID device feature recognition technology, and combines the ability of the page generation module to adapt the traffic recharge interface display form according to different user device types such as mobile terminal App, program, H5 page, etc., to push personalized package lists and recharge interfaces that match the characteristics of different regional and different type users, significantly improve the accuracy of regional package recommendation, improve the efficiency of user selection of traffic packages, and optimize user experience.

[0045] The application stores user pre-stored balance information by the balance management module and supports direct deduction of pre-stored balance for traffic package fees, stores user membership level information by the member management module, realizes the association of membership level and traffic recharge discount, and pushes user membership level benefit information to the page generation module, eliminates the experience fault between "membership, recharge, balance", fully plays the practicality of membership benefit value and balance pre-stored function, forms a collaborative sales ecosystem, further optimizes user experience, and enhances the level of operation refinement. BRIEF DESCRIPTION OF DRAWINGS

[0046] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings needed to be used in the embodiments or prior art description. Obviously, the drawings in the following description only represent some of the embodiments of the present application, and for those skilled in the art, other drawings can also be obtained from these drawings without any creative effort.

[0047] Figure 1 The system overall architecture of the present application is shown in the figure.

[0048] Figure 2 The rule engine configuration diagram of the present application is shown in the figure.

[0049] Figure 3 The ICCID identification flowchart of the present application is shown in the figure.

[0050] Figure 4 The dynamic page comparison diagram of the present application is shown in the figure.

[0051] Figure 5 The rule verification flowchart of the present application for traffic package purchase is shown in the figure.

[0052] Figure 6 The complete data interaction and logic flow of the present application for traffic package purchase is shown in the figure.

[0053] Figure 7 The flowchart of the present application for realizing regionalized package matching and personalized page generation based on ICCID is shown in the figure. DETAILED DESCRIPTION

[0054] The exemplary embodiments will be described in detail herein with reference to the attached drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the present application. Instead, they are merely examples of apparatuses and methods consistent with some aspects of the present application as detailed in the appended claims.

[0055] Referring to Figure 1 The present embodiment provides an intelligent system based on user traffic recharge, comprising: a user identification module, configured to receive user equipment ICCID information and access context carried by a user when initiating a traffic recharge request, analyze the ICCID information to obtain user equipment characteristics, and generate a user equipment characteristic portrait;

[0056] A package management module, in communication connection with the user identification module, configured to receive the user equipment characteristic portrait, match an adaptive traffic package in combination with a preset package strategy matrix, and generate a personalized package candidate list;

[0057] The rule engine module is connected to the package management module and the user operation terminal respectively. It is used to receive the personalized package candidate list and the user's current operation information, perform rule verification on each package in the personalized package candidate list, and output the personalized package list that has passed the verification.

[0058] The page generation module is connected to the rule engine module and the user operation terminal respectively. It is used to receive the verified personalized package list and the user device feature profile, and generate and output the adapted data recharge interface in combination with the dynamic template.

[0059] The access context includes at least the current time and geographic location information; the user device characteristics include at least the device's location, user type, and operator network information; and the user's current operation information includes at least the requested package ID, the proposed payment method, and the user's identity information.

[0060] like Figure 1 As shown, Figure 1 This is a schematic diagram of the module architecture of the intelligent system based on user recharge traffic in this embodiment, clearly showing the connection relationship and data interaction logic between the modules: The package management module "provides package data" to the rule engine module; the rule engine module and the dynamic page generator (the core functional carrier of the page generation module) transmit verification rules through "rule binding"; the user identification module obtains data from the device information database through "ICCID query" to generate "user characteristics"; the dynamic page generator finally outputs the interface to the "user terminal"; at the same time, the package management module manages specific package types such as "general package, first recharge package, special offer package, gift package, trial package", and the rule engine module manages rule types such as "purchase frequency rules, payment method rules, and time period control rules", and the modules work together to form a complete architecture.

[0061] Package Management Module: This module is the core manager of package resources. On the one hand, it provides package data to the rule engine module, providing basic package information for subsequent rule verification. On the other hand, it classifies and manages package types such as "general packages, first recharge packages, special offer packages, gift packages, and trial packages," clarifying the package types for different scenarios (new user first recharge, old user renewal, member exclusive, etc.).

[0062] The rules engine module is the core carrier of marketing rules. It receives "package data" from the package management module and transmits rules to the dynamic page generator through "rule binding". At the same time, it centrally manages rule types such as "purchase frequency rules, payment method rules, and time period control rules", providing a basis for compliance verification of package purchase behavior (such as purchase limit, payment channel, and sales period).

[0063] User identification module: responsible for user feature analysis function, access the device information database through "ICCID query" operation, extract the user's device's home, operator network data, generate "user features", provide the basis for user dimension for subsequent "precise matching package, interface adaptation".

[0064] Dynamic page generator: the output core of personalized interface, on the one hand, it receives the verification rules passed by the rule engine module through "rule binding", on the other hand, it combines the "user features" generated by the user identification module, and finally outputs the adapted traffic recharge interface to the user terminal (mobile terminal App, small program, H5 page, etc.), realizes the "thousand people with different faces" display effect.

[0065] The traffic package matched by the package management module in the embodiment includes general package, first charge package, preferential package, gift package and experience package, and the package strategy matrix defines the adaptation relationship and priority of different device features and each type of traffic package.

[0066] Please refer to Figure 2 , Figure 2 The binding relationship logic of package type and rule set is shown. The embodiment constructs a multi-dimensional package system, which specifically includes the following types and corresponding rules:

[0067] The first charge package is designed for new users, which is controlled through rule set 1: limit "only one time", realize the binding of new user device ID, ensure the exclusive benefit of the first recharge of each device; At the same time, limit "only support WeChat payment", clear the payment channel range of this package. For example, it can be configured as "9.8 yuan first charge 300G traffic, only visible and purchased when the device first charges, and only supports WeChat payment".

[0068] The preferential package focuses on the limited time preferential scene, and the rule set 2 is used to regulate the delivery logic: "open from 9:00 to 12:00 every day", associate the time period control rule, limit the display and purchase period of the package; "limit purchase 3 times", limit the purchase frequency of the same subject (device or account), prevent excessive single brushing. For example, it can be configured as "'National Day carnival 10G traffic package', only available in the National Day holiday period from 9:00 AM to 11:00 PM, and limited to purchase 1 time per day for the same device".

[0069] The experience package is used for new users to try, and the rule set 3 is used to guarantee the accuracy and compliance of delivery: "real name authentication is required", require the user to complete the real name authentication process of mobile phone number + ID card; "new user exclusive", limit the new user who has not participated in traffic recharge to receive. For example, it can be configured as "'new user free experience 1500G*3 days', which can be received after completing the real name authentication of mobile phone number + ID card, and each real name information is limited to 1 time".

[0070] In addition, the multi-dimension package system of the embodiment also includes a general package (as a standard traffic package, without special restrictions, applicable to all users) and a gift package (triggered to be issued according to the membership level, for example, “VIP 3-level members automatically obtain a free 5G traffic gift coupon in the account after logging in each month”), which together with the first charge, the preferential and the experience packages form a traffic package matrix covering the whole user life cycle and multiple scene requirements.

[0071] The rule verification performed by the rule engine module in the embodiment at least includes purchase limit verification, payment verification, time limit verification and user state verification; the purchase limit verification is to check the historical purchase times of the target package by the user or the associated device and account, the payment verification is to check whether the payment method selected by the user meets the payment requirements of the target package, the time limit verification is to check whether the current time is within the sales period of the target package, and the user state verification is to check whether the membership level and the account state of the user meet the use requirements of the target package.

[0072] When the user identification module parses the ICCID information in the embodiment, the user device features are obtained through a built-in rule library or by calling a third-party operator information interface;

[0073] When the page generation module generates the traffic recharge interface, the interface display form is adapted according to the user device type, and the user device type at least includes a mobile terminal App, a mini program and an H5 page; the traffic recharge interface is integrated with user account balance display, balance deduction options and membership level benefit information.

[0074] The embodiment also includes a balance management module, which is in communication connection with the page generation module and the package management module, is used to store user pre-stored balance information, supports deduction of the pre-stored balance to the traffic package fee, and pushes the user pre-stored balance information to the page generation module;

[0075] The embodiment also includes a membership management module, which is in communication connection with the rule engine module and the page generation module, is used to store user membership level information, provides the user membership level to the rule engine module to perform user state verification, and pushes the user membership level benefit information to the page generation module.

[0076] The rule engine module in the embodiment is constructed in a manner combining a rule-based decision model with real-time event stream processing technology, the verification rules stored in the rule engine module are configured in a declarative or DSL form, and dynamic addition, deletion and modification are supported.

[0077] The intelligent system based on user traffic top-up of the embodiment accurately analyzes user equipment characteristics through a user identification module, differentiates and matches a package through a package management module, dynamically executes multi-dimensional verification through a rule engine module, and generates a personalized interface through a page generation module, in combination with the collaborative support of a balance management module and a member management module, to form an intelligent solution covering the whole process of "user identification-package matching-rule control-interface presentation-benefit collaboration", effectively solving the deficiencies of the existing traffic top-up system in personalized service, risk control, dynamic adaptation and experience collaboration, and providing technical support for improving traffic top-up business conversion rate, preventing and controlling marketing risks and optimizing user experience.

[0078] The second aspect of the present application provides an intelligent method based on user traffic top-up, which is realized by using the intelligent system based on user traffic top-up as described above, and includes the following steps:

[0079] Receiving a traffic top-up request initiated by a user, and obtaining user equipment ICCID information and access context carried in the traffic top-up request;

[0080] Analyzing the ICCID information through the user identification module to obtain user equipment characteristics, and generating a user equipment characteristic portrait based on the user equipment characteristics;

[0081] Using the package management module, combining a preset package strategy matrix and the user equipment characteristic portrait, matching an adaptive traffic package, and generating a personalized package candidate list;

[0082] Receiving user current operation information through the rule engine module, performing rule verification on each traffic package in the personalized package candidate list, and obtaining a personalized package list that passes the verification;

[0083] Generating and outputting an adaptive traffic top-up interface by means of the page generation module, in combination with the personalized package list that passes the verification and the user equipment characteristic portrait;

[0084] The access context at least includes current time and geographic location information, the user equipment characteristics at least include equipment home location, user type and operator network information, and the user current operation information at least includes request package ID, proposed payment method and user identity information.

[0085] As an implementation manner, as described above, Figure 2 In the step of combining the preset package strategy matrix and the user equipment characteristic portrait, matching an adaptive traffic package, and generating a personalized package candidate list, the matched traffic package includes a general package, a first-charging package, a preferential package, a gift package and an experience package, and the package strategy matrix defines the adaptive relationship and priority of different user equipment characteristics and each type of traffic package.

[0086] As an implementation, the step of performing rule verification on each traffic package in the personalized package candidate list in the embodiment includes at least the following operations:

[0087] Limit purchase verification, the rule engine module checks the historical purchase times of the target traffic package of the user or associated equipment and account;

[0088] Payment verification, the rule engine module checks whether the payment method selected by the user meets the payment requirements of the target traffic package;

[0089] Time limit verification, the rule engine module checks whether the current time is within the sales period of the target traffic package;

[0090] User state verification, the rule engine module checks whether the user membership level and account state meet the use requirements of the target traffic package.

[0091] As an implementation, the step of analyzing the ICCID information to obtain the user equipment characteristics in the embodiment is to analyze the ICCID information through a built-in rule library, or to call a third-party operator information interface to analyze the ICCID information to obtain the user equipment characteristics.

[0092] In the step of generating and outputting the adapted traffic recharge interface, the page generation module adapts the display form of the traffic recharge interface according to the user equipment type, and the user equipment type at least includes a mobile terminal App, a small program and an H5 page. The traffic recharge interface is integrated with user account balance display, balance deduction options and membership level benefit information.

[0093] As shown in Figure 3 , the complete process logic from obtaining the user ICCID to generating the traffic recharge interface is shown, which is as follows:

[0094] The process starts with "obtaining user ICCID", that is, the system receives the equipment integrated circuit card identification code (ICCID) carried by the user when initiating a traffic recharge request; then enters the "device information query" link to determine whether the device information associated with the ICCID can be successfully called:

[0095] If the query fails, "call default package" is executed, and a general traffic package is directly displayed to the user to ensure the availability of basic recharge services;

[0096] If the query is successful, the "analyze device characteristics" link is entered, and two types of core characteristics are extracted from the device information: one is "get home location", which clearly indicates the geographical location of the user equipment; the other is "confirm user level", which identifies the level of the user in the membership system.

[0097] Based on the parsed "location" and "user level," the system performs "matching regional packages," combining exclusive packages for the user's region (such as regional special offers from local operators) with membership-exclusive packages corresponding to the user's level (such as high-value data packages for VIP users). Next, it "combines personalized solutions," integrating regional packages and membership benefit packages to form a list of exclusive packages that match the user's characteristics. Then, it "generates a dynamic page," adapting the interface display format according to the user's device type (mobile app, mini-program, H5 page, etc.), and finally outputs a data recharge interface containing the personalized package list, thus ending the process.

[0098] In summary, this process, centered on ICCID, achieves personalized recharge interface push through the links of "device information query, feature parsing, differentiated package matching, and dynamic page generation"; at the same time, it ensures service continuity in abnormal scenarios by using "recalling the default package if the query fails" as a backup.

[0099] like Figure 4 The above describes the logic behind achieving a personalized data recharge interface based on the user's ICCID, as detailed below:

[0100] The system uses the "User Feature Analysis" module to analyze user device and account information associated with different ICCIDs (such as "ICCID123" and "ICCID456" in the example), extracts core user features, and then dynamically generates differentiated data recharge interfaces.

[0101] When parsing ICCID123, the system obtains "New user characteristics: Beijing location, ordinary membership level". Based on this, the system generates a new user interface (interface 1), which highlights "first recharge package" and "trial package" and matches "Beijing local recommendation" marketing content (such as "120% discount on first recharge" and "free trial package") to accurately reach the new user's first recharge and trial needs.

[0102] When parsing ICCID456, the system obtains "VIP user characteristics: Shanghai location, Gold membership level". Based on this, the system generates a VIP user interface (interface 2), which highlights "Member Exclusive Packages", "Balance Recharge Area" and "International Data Packages", and matches it with marketing content of "High-Value Package Combinations" (such as "Instant Discount on Balance Recharge" and "Special Offers on Overseas Data"), which fully meets the high-level data consumption and membership benefits needs of VIP users.

[0103] By analyzing the user characteristics associated with ICCID, the system can differentiate and adapt to different groups such as "new users" and "VIP users" in terms of "package display priority" and "regional recommended content", ultimately achieving a "personalized" data recharge interface effect, effectively improving user experience and business conversion efficiency.

[0104] As one implementation method, this embodiment further includes the following steps before generating and outputting the adapted data recharge interface:

[0105] The balance management module stores the user's prepaid balance information, performs deduction of data plan fees based on the prepaid balance information, and pushes the user's prepaid balance information to the page generation module.

[0106] Furthermore, before performing rule verification on each data plan in the personalized plan candidate list, the method further includes:

[0107] The membership management module stores user membership level information, performs user status verification based on the user membership level information, and pushes user membership level benefits information to the page generation module.

[0108] As one implementation method, in this embodiment, when performing rule verification, the rule engine module adopts a combination of rule-based decision model and real-time event stream processing technology, and the verification rules are configured in declarative or domain-specific language (DSL) form, supporting dynamic addition, deletion and modification.

[0109] like Figure 5 The diagram shown illustrates the rule verification process for purchasing data plans. It fully demonstrates the rule verification logic throughout the entire process, from when a user submits a purchase request to when the order is completed or the request is blocked. The specific steps and logic are as follows:

[0110] Request reception and basic information acquisition

[0111] After the user "selects a package and submits the purchase", the system first "receives and parses the request", and then performs two operations in parallel:

[0112] "Get Package Association Rules": Retrieves the pre-configured purchase limit rules, payment method rules, and time period control rules for this data package;

[0113] "Get User ID / Device ID Information": Collects user / device identification information used to count the number of historical purchases of the package.

[0114] After executing the "Read Purchase Limit Count" check, the first round of control is performed by determining whether "Purchase Count COUNT (User Purchases) ≤ max_purchase?" (i.e., whether the user or associated device's historical purchase count for this package has not exceeded the maximum limit).

[0115] If the result is "No" (purchase limit reached), then "the process will be terminated" and the user will be "retained and informed of the reason for the failure (personal purchase limit reached)".

[0116] If the result is "yes" (purchase limit not reached), proceed to the next round of verification.

[0117] Payment method rule verification

[0118] Determine if the payment method is within the allowed_methods range (i.e., whether the user's chosen payment method is within the range of payment channels allowed by the plan):

[0119] If the result is "No" (payment method not supported), then "Terminate the process" and "Retain and prompt the user with the reason for the failure (payment method not supported)";

[0120] If the result is "yes" (payment method supported), proceed to the final round of verification.

[0121] Time period control rule verification

[0122] Determine if "current time ∈ time interval [start_time, end_time]?" (i.e., whether the current time is within the sales period for the package):

[0123] If the result is "No" (not within the valid time period), then "Terminate the process" and "Retain and prompt the user with the reason for the failure (not within the valid time period)";

[0124] If the result is "yes" (within the valid period), then "PASS" (all rules have passed the verification), and then "create order" will be executed, and finally "complete the purchase process".

[0125] The rules engine combines a rule-based decision model with real-time event stream processing technology. Rules are stored in the rule base using declarative or DSL configuration, supporting dynamic addition, deletion, and modification. Rules can include logical judgments (IF condition THEN action), counting aggregations (COUNT, WITHIN), and complex combinations (AND, OR, NOT). The overall logic achieves dynamic rule control over data plan purchase behavior through sequential verification of three dimensions: purchase limit, payment method, and time period control. If any dimension fails verification, the request is blocked and the reason for failure is clearly displayed; the purchase is only allowed when all dimensions pass verification. This mechanism ensures the rule-based nature of marketing activities (such as purchase limits and time limits) while guiding users to purchase in compliance with regulations, avoiding the ineffective waste of marketing resources.

[0126] like Figure 6 As shown, a new cross-system rule type is defined in the rule base: Membership Level Restriction (require_membership_level): This restricts purchases to members of a specific level (such as Gold / VIP).

[0127] Balance usage rules (allow_balance_deduction, deduction_percentage): Allow deductions and set deduction percentages / caps. Benefit combination requirements (require_available_coupon, integrate_points): Requires holding specific types of coupons / points to combine and use benefits. Associate these rules with specific data plans. Rule configurations must declare their dependent external data interfaces (e.g., "get user membership level interface" and "query user available balance interface").

[0128] Figure 6 The document demonstrates the complete data interaction and logic process from user action to multi-system data synchronization and result feedback when purchasing a data plan, as detailed below:

[0129] I. User Operations and Basic Data Collection

[0130] Users perform three core operations on the front end: "Select Package" (selecting the target data plan), "Select Payment Method" (selecting the payment channel to be used, including cross-system methods such as balance payment), and "Select Coupon / Points" (selecting coupons or points in the account that can participate in the discount); at the same time, the system obtains four key data from the "User Information and Assets Module": "User ID" (used for unique identity identification), "Membership Level" (used for membership benefit verification), "Available Balance" (used for balance deduction rule verification), and "Coupon / Points" (used for benefit combination condition verification), and transmits these operations and data to the "Cross-System Rule Verification Module".

[0131] II. Cross-system rule validation

[0132] The "Cross-System Rule Validation Module" retrieves three types of pre-configured rules from the "Rule Base" and collaborates with external system interfaces to complete multi-dimensional validation.

[0133] Membership Level Rules (require_membership_level): Call the "Membership System Interface" to verify whether the user's "Membership Level" meets the rules (e.g., whether they are a VIP member and can purchase exclusive packages);

[0134] Balance usage rules (allow_balance_deduction + deduction_percentage): Call the "balance system interface" to verify whether the "available balance" is allowed to be deducted (allow_balance_deduction), and the deduction ratio / maximum (deduction_percentage);

[0135] Benefit combination rule (require_available_coupon+integrate_points): Call the "coupon / points system interface" to verify whether you hold the coupon specified by require_available_coupon or meet the points requirement of integrate_points.

[0136] If any verification fails, the process terminates and the reason for the failure is reported (such as "insufficient membership level" or "insufficient balance for deduction"); if all verifications pass, the process proceeds to the "order processing" stage.

[0137] III. Order Creation and Amount Calculation

[0138] After successful verification, the system executes "order creation" and calculates the final payment amount based on the three types of data:

[0139] Based on the result of "selecting a package", determine the original price of the package;

[0140] Calculate the amount to be deducted based on the "available balance" and the deduction_percentage;

[0141] Calculate the coupon / points discount amount based on the "coupon / points" combination rules and benefits;

[0142] The final amount payable by the user is calculated as "original package price - balance deduction amount - coupon / points discount amount".

[0143] IV. Multi-system data synchronization

[0144] After the order payment is completed, the system synchronizes data with three external systems to ensure data consistency across multiple systems:

[0145] Synchronize the rights and benefits redemption records to the "Membership System" (e.g., rights marked as "VIP Exclusive Package" have been used);

[0146] Synchronize the balance deduction record to the "Balance System" (record the details of the balance deduction in this order);

[0147] Synchronize coupon / points usage records to the "Coupon / Points System" (mark used coupons or points and update the user's remaining available benefits).

[0148] V. Package Distribution and Result Feedback

[0149] After the data synchronization between multiple systems is completed, the system will "issue a data package" to the user and "feedback the purchase result" through the front-end interface: if there are no abnormalities throughout the process, it will provide feedback of "purchase successful" and package information; if the intermediate verification fails, it will provide feedback on the specific reason for failure (such as "insufficient membership level, unable to purchase this package").

[0150] Through the above end-to-end process, cross-system linkage of user operation, rule verification, order processing, multi-system synchronization, and result feedback is achieved, which not only ensures the accurate execution of marketing rules, but also guarantees the consistency of data from multiple systems such as members, balances, and benefits.

[0151] Please see Figure 7 , Figure 7 This demonstrates the process of matching regional plans and generating personalized pages based on ICCID. The specific steps are as follows:

[0152] When the system receives a data top-up request from a user, it first obtains the integrated circuit card identification code (ICCID) of the user's device. This ICCID serves as the core index for subsequent parsing of device information.

[0153] The device information is parsed, and based on the ICCID, two key types of information about the user equipment are extracted:

[0154] Location / Attribution: Clearly defines the geographical location of the user's device (such as regional information like province and city);

[0155] Confirm user level: Identify the user's tier within the membership system (such as regular user, VIP user, and other identity-related information).

[0156] The system matches regionalized data plans by combining "location / followering area" and "user level" information, filtering and matching suitable regionalized plans from a multi-dimensional data plan system (including general plans, first-time recharge plans, special offer plans, gift plans, trial plans, etc.). For example, if a user's device is located in Beijing and they are a new user, the "Beijing New User First-Time Recharge Special Offer Plan" will be matched first; if the user is a VIP member in Shanghai, the "Shanghai VIP Exclusive High-Value Data Package" will be matched.

[0157] Generate a personalized page. Based on the matched regional package and the user's device type (such as mobile app, mini program, H5 page, etc.), call the dynamic page generator to generate a personalized data recharge interface that includes a list of exclusive packages and regional discount descriptions, and push it to the user's terminal.

[0158] Although embodiments of the present invention have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting the present invention. Those skilled in the art can make changes, modifications, substitutions and variations to the above embodiments within the scope of the present invention.

Claims

1. An intelligent system based on user recharge traffic, characterized in that: include: The user identification module is used to receive the user device ICCID information and access context carried by the user when initiating a data traffic recharge request, parse the ICCID information to obtain user device characteristics, and generate a user device characteristic profile. The package management module is communicatively connected to the user identification module. It is used to receive the user device feature profile, match the appropriate data packages with the preset package strategy matrix, and generate a personalized package candidate list. The rule engine module is connected to the package management module and the user operation terminal respectively. It is used to receive the personalized package candidate list and the user's current operation information, perform rule verification on each package in the personalized package candidate list, and output the personalized package list that has passed the verification. The page generation module is connected to the rule engine module and the user operation terminal respectively. It is used to receive the verified personalized package list and the user device feature profile, and generate and output the adapted data recharge interface in combination with the dynamic template. The access context includes at least the current time and geographic location information; the user device characteristics include at least the device's location, user type, and operator network information; and the user's current operation information includes at least the requested package ID, the proposed payment method, and the user's identity information.

2. The intelligent system based on user recharge traffic according to claim 1, characterized in that: The data plans matched by the data plan management module include general plans, first-time recharge plans, special offer plans, gift plans, and trial plans. The data plan strategy matrix defines the compatibility and priority between different device characteristics and various types of data plans.

3. The intelligent system based on user recharge traffic according to claim 1, characterized in that: The rule verification performed by the rule engine module includes at least purchase limit verification, payment verification, timeliness verification, and user status verification. The purchase limit verification checks the number of times a user or associated device or account has purchased the target package in the past. The payment verification checks whether the user's proposed payment method meets the payment requirements of the target package. The timeliness verification checks whether the current time is within the sales period of the target package. The user status verification checks whether the user's membership level and account status meet the usage requirements of the target package.

4. The intelligent system based on user recharge traffic according to claim 1, characterized in that: When the user identification module parses the ICCID information, it obtains the user equipment characteristics through a built-in rule base or by calling a third-party operator information interface. When the page generation module generates the data recharge interface, it adapts the interface display format according to the user's device type. The user device type includes at least a mobile app, a mini-program, and an H5 page. The data recharge interface integrates user account balance display, balance deduction options, and membership level benefits information.

5. The intelligent system based on user recharge traffic according to claim 1, characterized in that: It also includes a balance management module, which is communicatively connected to the page generation module and the package management module. It is used to store the user's prepaid balance information, support the prepaid balance to offset the data package fee, and push the user's prepaid balance information to the page generation module. It also includes a membership management module, which is communicatively connected to the rule engine module and the page generation module. This module stores user membership level information, provides user membership levels to the rule engine module to perform user status verification, and pushes user membership level benefits information to the page generation module.

6. The intelligent system based on user recharge traffic according to claim 3, characterized in that: The rule engine module is built by combining a rule-based decision model with real-time event stream processing technology. The verification rules stored in the rule engine module are configured in a declarative or DSL format and support dynamic addition, deletion and modification.

7. A smart method based on user recharge traffic, characterized in that: The system is implemented using any one of the intelligent systems based on user recharge traffic as described in any one of claims 1 to 6, and includes the following steps: Receive a data top-up request initiated by a user, and obtain the user device ICCID information and access context carried in the data top-up request; The user identification module parses the ICCID information to obtain user equipment characteristics, and generates a user equipment feature profile based on the user equipment characteristics; Using the package management module, combined with the preset package strategy matrix and the user device feature profile, a suitable data package is matched to generate a personalized package candidate list. The rule engine module receives the user's current operation information and performs rule verification on each data plan in the personalized plan candidate list to obtain a list of verified personalized plans. Using the page generation module, combined with the verified personalized package list and the user device feature profile, a suitable data recharge interface is generated and output. The access context includes at least the current time and geographic location information; the user device characteristics include at least the device's location, user type, and operator network information; and the user's current operation information includes at least the requested package ID, the proposed payment method, and the user's identity information.

8. The intelligent method based on user recharge traffic according to claim 7, characterized in that: In the step of combining the preset package strategy matrix with the user device feature profile to match suitable data packages and generate a personalized package candidate list, the matched data packages include general packages, first recharge packages, special offer packages, gift packages and trial packages. The package strategy matrix defines the matching relationship and priority between different user device features and various types of data packages.

9. The intelligent method based on user recharge traffic according to claim 8, characterized in that: The step of performing rule verification on each data plan in the personalized plan candidate list includes at least the following operations: Purchase limit verification is performed by the rule engine module, which checks the number of historical purchases made by the user or associated device / account for the target data plan. Payment verification is performed by the rules engine module to check whether the user's chosen payment method meets the payment requirements of the target data plan; Timeliness verification is performed by the rules engine module to check whether the current time falls within the sales period of the target data plan; User status verification is performed by the rules engine module to check whether the user's membership level and account status meet the usage requirements of the target data plan.

10. The intelligent method based on user recharge traffic according to claim 9, characterized in that: The step of parsing the ICCID information to obtain user equipment characteristics is to parse the ICCID information through a built-in rule base or to call a third-party operator information interface to parse the ICCID information to obtain user equipment characteristics. In the step of generating and outputting the adapted data recharge interface, the page generation module adapts the display format of the data recharge interface according to the user device type. The user device type includes at least mobile app, mini program, and H5 page. The data recharge interface integrates user account balance display, balance deduction options, and membership level benefits information.

11. The intelligent method based on user recharge traffic according to claim 10, characterized in that: Before generating and outputting the adapted data recharge interface, the following is also included: The system stores users' prepaid balance information through the balance management module, performs deductions for data plan fees based on the prepaid balance information, and pushes the users' prepaid balance information to the page generation module. Before performing rule verification on each data plan in the personalized plan candidate list, the method further includes: The membership management module stores user membership level information, performs user status verification based on the user membership level information, and pushes user membership level benefits information to the page generation module. When performing rule verification, the rule engine module adopts a combination of rule-based decision model and real-time event stream processing technology, and the verification rules are configured in declarative or domain-specific language (DSL) form, supporting dynamic addition, deletion and modification.

Images