Traffic control management method, device, equipment, storage medium and program product

Abstract

This invention discloses a credit control management method, apparatus, device, storage medium, and program product. It acquires credit control execution results for all user accounts in a business system according to a preset cycle. Each user account is associated with at least one main product, and each main product is pre-configured with a corresponding credit control lifecycle stage and associated credit control rules for each stage. Based on the credit control execution results, target user accounts in abnormal scenarios are selected. Based on the credit control rules of the main product to which the target user account belongs, an audit query is performed on the target user account. The audit query results are summarized, and a credit control verification report is generated based on the audit query results. Using this invention, scattered credit control rules can be effectively organized, product-level credit control lifecycle management can be established, automated and intelligent monitoring can be achieved, and management efficiency and user experience can be improved.

Description

Technical Field

[0001] This invention relates to the field of digital intelligence, and in particular to an information control management method, apparatus, equipment, storage medium, and program product. Background Technology

[0002] Credit control refers to a management method in the telecommunications field where operators formulate rules based on user balances, outstanding payments, and other data to conduct credit assessments and status management (such as early warnings, service suspension, and service activation) of user accounts. The aim is to balance user rights with operator risks. Current credit control methods primarily rely on credit control systems. These systems calculate the difference between the account's relevant balance and outstanding payments as the credit control balance, and then compare this balance with a preset credit control value to determine the account's status.

[0003] However, with the development of 5G networks, the scale of networks and the complexity of services have surged. Local credit control rules are scattered and independent. Credit control rules are specific standards formulated by operators to determine whether user accounts need to be alerted, suspended, or activated. A single rule may correspond to multiple main products or multiple customer levels. It is impossible to accurately query whether a certain main product has been configured with credit control rules, and it is also difficult to clarify which rules are specifically associated with the product. This leads to confusion in the matching relationship between rules and products and customers. Staff need to manually check the products and customers corresponding to each rule and check whether the account control status meets the rule requirements. This not only consumes a lot of manpower and resources, but also has problems such as verification delays and judgment errors, resulting in account anomalies. This affects the operator's accurate control of account risks and reduces user experience due to improper handling of account status. Summary of the Invention

[0004] The purpose of this invention is to provide a credit control management method, device, equipment, storage medium, and program product that can effectively organize scattered credit control rules, establish product-level credit control lifecycle management, realize automated and intelligent monitoring, and improve control efficiency and user experience.

[0005] To achieve the above objectives, embodiments of the present invention provide a credit control management method, comprising: The system retrieves the credit control execution results corresponding to all user accounts in the business system according to a preset cycle; each user account is associated with at least one main product, and each main product is pre-configured with the corresponding credit control lifecycle stage and the credit control rules associated with each stage; Based on the results of the credit control execution, target user accounts in abnormal scenarios are selected; Based on the credit control rules of the main product to which the target user account belongs, an audit query is performed on the target user account; Summarize the audit query results and generate an credit control verification report based on the audit query results.

[0006] As an improvement to the above solution, the step of filtering out target user accounts in abnormal scenarios based on the credit control execution results includes: Based on the consistency between the credit control execution result and the credit control lifecycle stage, user accounts with inconsistent comparison results are selected as target user accounts in abnormal scenarios.

[0007] As an improvement to the above solution, the abnormal scenarios include at least one of the following: scenarios with no credit control rules, scenarios where the account should have been suspended but was not, scenarios where the account should have been opened but was not, scenarios where the account was suspended but not closed, and scenarios where the credit status remains unchanged.

[0008] As an improvement to the above solution, before periodically checking the credit control execution results of all user accounts corresponding to the main products in the business system, the method further includes: Synchronize the existing credit control rules data in the business system as the monitoring basis data; When the business system performs an update operation on the credit control rules, it controls the monitoring basic data to be updated synchronously. Based on the aforementioned monitoring data, configure the corresponding credit control lifecycle stages and associated credit control rules for all main products in the business system.

[0009] As an improvement to the above solution, when the abnormal scenario is a scenario where a shutdown should have been stopped but was not, or a scenario where an activation should have been made but was not, the step of auditing and querying the target user account based on the credit control rules of the main product to which the target user account belongs includes: If the target user account's main product is configured with credit control rules, then according to the credit control lifecycle stage corresponding to the credit control rules, check whether the target user account meets the triggering conditions of the credit control rules; If the triggering condition is not met, the preset matching conditions of the credit control rule are compared with the actual data of the target user account to determine the cause of the abnormality of the target user account.

[0010] As an improvement to the above solution, when the abnormal scenario is a scenario where a shutdown should have been initiated but was not, after verifying whether the target user account meets the triggering conditions of the credit control rule, the method further includes: If the triggering condition is met, obtain the shutdown condition of the target user account; The cause of the abnormality of the target user account is determined based on the aforementioned shutdown conditions.

[0011] As an improvement to the above solution, when the abnormal scenario is a scenario where an account should have been opened but was not, after checking whether the target user account meets the triggering conditions of the credit control rule, the method further includes: If the triggering condition is met, obtain the power-on conditions of the target user account; The cause of the abnormality of the target user account is determined based on the aforementioned boot conditions.

[0012] To achieve the above objectives, embodiments of the present invention also provide an information control management device, comprising: The credit control execution result acquisition module is used to acquire the credit control execution results corresponding to all user accounts in the business system according to a preset period. Each user account is associated with at least one main product, and each main product is pre-configured with the corresponding credit control lifecycle stage and the credit control rules associated with each stage. The target user account filtering module is used to filter out target user accounts in abnormal scenarios based on the credit control execution results; The audit query module is used to perform audit queries on the target user account based on the credit control rules of the main product to which the target user account belongs; The credit control verification report generation module is used to summarize the audit query results and generate a credit control verification report based on the audit query results.

[0013] To achieve the above objectives, embodiments of the present invention also provide a signal control management device, including a processor, a memory, and a computer program stored in the memory and configured to be executed by the processor. When the processor executes the computer program, it implements the signal control management method as described in any of the above embodiments.

[0014] To achieve the above objectives, embodiments of the present invention also provide a computer-readable storage medium, the computer-readable storage medium including a stored computer program, wherein, when the computer program is executed, it controls the device where the computer-readable storage medium is located to perform the signal control management method as described in any of the above embodiments.

[0015] To achieve the above objectives, embodiments of the present invention also provide a computer program product, including computer instructions, which, when executed by a processor, implement the signal control management method as described in any of the above embodiments.

[0016] Compared to existing technologies, the credit control management method, device, equipment, storage medium, and program products disclosed in this invention solve the problems of fragmented and independent credit control rules and chaotic matching relationships with products / customers in existing technologies by establishing a binding relationship between the main product, the credit control lifecycle stage, and the credit control rules. It supports standardized rule maintenance across multiple dimensions, accurately queries the rule configuration of any main product, reduces the manpower cost of rule management, and achieves systematic and clear control of credit control rules. Furthermore, it automatically acquires the credit control execution results of all users at preset cycles, replacing the traditional manual audit mode. This avoids the lag and judgment errors of manual verification, improves the efficiency and coverage of credit control execution verification, and ensures no abnormal scenarios are missed. Moreover, through a hierarchical audit logic that clearly defines abnormal scenarios and guides rules, it can locate the cause of abnormalities, providing a clear basis for abnormal handling and ensuring the accuracy and timeliness of user account suspension and restart operations. This strengthens the operator's precise control over account risks and reduces user experience degradation caused by improper account status handling. Attached Figure Description

[0017] Figure 1 This is a flowchart of the information control rule configuration and data synchronization in the information control management method provided in this embodiment of the invention; Figure 2 This is the first flowchart of the credit control lifecycle management provided in the embodiments of the present invention; Figure 3 This is the second flowchart of the credit control lifecycle management provided in this embodiment of the invention; Figure 4 This is the third flowchart of the credit control lifecycle management provided in this embodiment of the invention; Figure 5 This is a flowchart of a credit control management method provided in an embodiment of the present invention; Figure 6 This is a structural block diagram of an information control management device provided in an embodiment of the present invention; Figure 7 This is a structural block diagram of an information control management device provided in an embodiment of the present invention. Detailed Implementation

[0018] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0019] The credit control management method described in this embodiment of the invention can be implemented by a credit control lifecycle management system. The credit control lifecycle management system is built on a cloud-native architecture. This system can achieve data interoperability and collaborative linkage with business systems in the communication network, such as NGBOSS (Next Generation Business & Operation Support System), CRM (Customer Relationship Management), BRM (Billing and Revenue Management), and work order scheduling platform. It has full-process functional modules such as credit control rule synchronization, lifecycle configuration, anomaly monitoring and auditing, and report generation and push.

[0020] The credit control lifecycle management system supports real-time synchronization of existing credit control rule data in the NGBOSS system. When the NGBOSS system performs add, delete, or modify operations on credit control rules, it synchronously updates the local monitoring basic data, and the synchronization process does not affect the normal operation of existing credit control services. The credit control lifecycle management system provides multi-dimensional credit control lifecycle and associated rule configuration functions based on main product, business type (value-added products), user type (individual users, group users, integrated users), payment method (cash, deduction, collection), and credit control mode (real-time credit control, monthly settlement credit control). It supports query, add, modify, delete, batch delete, and export operations. The credit control lifecycle management system has built-in credit control anomaly monitoring rules, which can periodically check the credit control execution results of all user accounts, accurately identify abnormal scenarios such as no credit control rules, failure to stop when required, failure to open when required, failure to close when suspended, and credit status stagnation. For target user accounts in abnormal scenarios, it performs layered verification of the anomaly causes based on the credit control rules of their respective main products, including rule configuration verification, trigger condition matching, execution status verification, and work order tracing. The credit control lifecycle management system periodically summarizes the audit query results of the previous cycle, generates a credit control audit report containing product credit control configuration information and audit result details, and pushes it to designated personnel via email, supporting configuration by multiple interface personnel.

[0021] See Figure 1 , Figure 1 This is a flowchart of the information control rule configuration and data synchronization in the information control management method provided in the embodiment of the present invention. Before executing step S1, the information control management method includes steps S101 to S103.

[0022] S101. Synchronize the existing credit control rule data in the business system as the monitoring base data.

[0023] For example, monitoring foundation data refers to a standardized dataset extracted and organized from business systems such as NGBOSS, covering all existing credit control rule information. This includes key information such as the unique identifier of the credit control rule, the scope of applicable products, user type restrictions (individual users, group users, integrated users), payment method matching conditions (cash, deduction, direct debit), trigger thresholds (e.g., balance threshold, overdue payment duration threshold), corresponding control actions (early warning, shutdown, startup, etc.), and rule effective / expiration time. Existing credit control rules are scattered across various business systems, with inconsistent data formats and a lack of centralized management. Synchronizing standardized monitoring foundation data can solve the problems of fragmented and independent credit control rules, making unified verification difficult, and providing a unified data benchmark for subsequent rule configuration and anomaly auditing. Furthermore, credit control management is based on existing business rules for full-process control, directly reusing existing credit control rule data from business systems without building a rule system from scratch. This reduces system construction costs, ensures consistency between credit control management and existing business logic, avoids control errors caused by rule conflicts, and provides reliable data support for upper-level rule configuration and anomaly monitoring functions.

[0024] S102. When the business system performs an update operation on the credit control rule, it controls the monitoring basic data to be updated synchronously.

[0025] For example, update operations refer to various operations in the business system such as adding, modifying, deleting, enabling, and disabling credit control rules. Examples include adding credit control rules adapted to 5G-specific packages, modifying the arrears suspension threshold for a certain main product, deleting credit control rules corresponding to discontinued old products, or temporarily disabling credit control rules for a certain type of user due to business adjustments. Synchronous updates are necessary to ensure the timeliness and accuracy of basic monitoring data, ensuring that credit control management is always based on the latest business rules. If the basic monitoring data and business system rules are not synchronized, the problem of auditing new business using old rules will arise, leading to misjudgments or omissions in abnormal scenarios. For example, if the business system has adjusted the suspension threshold for a certain group user from arrears of A yuan to B yuan, but the basic monitoring data is not updated synchronously and audits are still based on the A yuan threshold, this will cause such users to be incorrectly judged as failing to suspend services when they should, or to be unrecognized when the new threshold has actually been reached, affecting the accuracy of credit control management. It will also cause data disconnect between the business system and the credit control management system, reducing the overall consistency of business management.

[0026] S103. Based on the monitoring data, configure the corresponding credit control lifecycle stage and the associated credit control rules for each stage for all main products in the business system.

[0027] For example, a primary product refers to a product unit in mobile communication services that possesses independent business attributes and can provide communication services to users independently. Examples include inter-provincial dedicated lines, intra-provincial group networks, individual mobile phone packages, and converged broadband packages. Each primary product corresponds to a unique product identifier and product name, which can be located by product ID or name. The credit control rules associated with each stage refer to specific standards customized based on monitoring data and multiple dimensions such as primary product, user type, payment method, and credit control mode (e.g., real-time credit control, monthly billing credit control). These standards are used to determine whether a user has entered a certain credit control lifecycle stage and what control actions need to be performed at that stage. The credit control lifecycle stage refers to the complete management stage of a user account from normal use to abnormal control and then to restoration to normal or termination of service. Combined with the business characteristics of the telecommunications industry, it can be divided into stages such as activation, deduction, warning, pending suspension 1, pending suspension 2, and suspension. In some scenarios, it can also extend to the post-suspension account cancellation stage. Each stage progresses sequentially, clearly defining the user account status under different risk levels.

[0028] Furthermore, the meanings of each stage in the information control lifecycle are as follows: 1) During the power-on phase, the user account is in normal use status. The account balance, outstanding fees, etc. meet the conditions for using communication services. The user can make and receive calls and use various value-added services normally. The service can also be automatically or manually restored after the service is suspended if the restoration conditions are met (such as paying the outstanding fees). 2) The early warning stage is a pre-emptive reminder that the account is about to be in arrears. It is triggered when the account balance is lower than the preset early warning threshold. The system will remind the user to recharge in time through SMS, APP push and other means to avoid the subsequent impact on communication services due to arrears, and provide a risk buffer for users and operators. 3) The deduction phase is a special phase set up for users who have signed up for the automatic payment agreement. It means that the system automatically deducts communication fees from the user's linked payment account according to a preset cycle (such as the monthly billing date) or trigger conditions. 4) The first stage of waiting for suspension is the first buffer state after the user's account is in arrears but has not reached the conditions for forced suspension. The system will give a short buffer period and send an arrears reminder again. During this period, the core communication services can still be used normally, but there may be restrictions on non-core business, so as to give the user time to pay. 5) The second stage of the suspension period is the final warning state before the suspension. If the user still fails to pay the outstanding fees after the buffer period ends, the system will increase the frequency of the outstanding fees reminders, while restricting some functions such as making outgoing calls, and only retaining basic services such as answering calls and receiving SMS messages. The system will also pre-generate a suspension work order to prepare for the subsequent suspension. 6) The suspension phase is the management status after the account is in arrears. It is triggered when the user's arrears duration or arrears amount reaches a preset threshold. The system will suspend all communication services, such as suspending outgoing and incoming calls, Internet access, value-added services, etc. The user needs to pay all arrears and meet the conditions for restarting the service in order to restore normal use. This is to manage the risk of operator arrears. 7) The post-shutdown account cancellation stage is the final management stage of the credit control life cycle. It refers to the stage when a user account has been in a suspended state for a long time and meets the cancellation conditions. The stage involves clearing up outstanding fees and canceling the account in accordance with the rules to avoid invalid accounts occupying resources.

[0029] It should be noted that the order, meaning, and form of the above stages are merely examples. In actual application, these can be flexibly adjusted according to the operator's business scenario requirements, user types, payment methods, credit control models, and the characteristics of the main products. The credit control rules associated with each stage refer to the specific standards set for each lifecycle stage to determine whether a user has entered that stage and what control actions need to be performed in that stage. These rules originate from standardized rules in the monitoring basic data.

[0030] See Figure 2 , Figure 2 This is the first flowchart of the credit control lifecycle management provided in this embodiment of the invention. The operator initiates a configuration operation, and the credit control lifecycle management system loads the configuration interface. The interface includes a multi-dimensional filtering condition area, a lifecycle stage list area, and a rule configuration area. The multi-dimensional filtering condition area supports locating the configuration object by key dimensions such as the main product, user type, credit control mode, and payment method, and additional filtering fields can be flexibly added. The lifecycle stage list area displays the full credit control lifecycle stages of different main products. The rule configuration area provides function buttons such as confirm modification, delete, and details to support the complete execution of the configuration process and subsequent adjustments.

[0031] See Figure 3 , Figure 3 This is the second flowchart of the credit control lifecycle management provided in this embodiment of the invention, to... Figure 2 Taking the main product of 9601 as an example, the operator can select... Figure 2 Clicking the "Details" button on the 9601 main product will redirect the system to the product's details display interface. This interface shows the pre-configured credit control lifecycle stages, including the power-on stage, warning stage, standby shutdown stage 1, standby shutdown stage 2, and shutdown stage, as well as the corresponding credit control rules for each stage. For example, the warning stage rule is that the warning stage is entered when "ZY < 10". In the diagram, ZY, WW, and ZZ represent business variables. For instance, ZY represents the available account balance, WW represents the number of days in arrears, and ZZ represents the total amount in arrears. "ZY < 0 && WW < 0" indicates arrears and arrears duration exceeding the target.

[0032] See Figure 4 , Figure 4 This is the third flowchart of the credit control lifecycle management provided in this embodiment of the invention, targeting... Figure 3 On the detailed display interface of the 9601 main product, operators can reconfigure the credit control lifecycle stages of the 9601 main product. Operators can click the corresponding modify button for each stage on the details interface, or select the add stage or delete stage function to start the secondary configuration. During the process, operators can adjust existing stage rules, such as modifying the balance threshold of the power-on stage, extending the waiting period for shutdown, adding stages adapted to business needs, such as the account cancellation stage after shutdown, or deleting redundant stages. After configuration, the system automatically checks for rule conflicts to ensure logical consistency. After confirming that the operation is correct, submit the changes. The system synchronously updates the basic monitoring data and related business systems such as NGBOSS and CRM, and generates a configuration change log for traceability. The entire process supports flexible iteration of the credit control rules of the main product, adapts to changes in business scenarios and user needs, and is simple and efficient.

[0033] After completing the information control rule configuration and data synchronization operations in steps S101-S103 above, the process of verifying the information control execution results and handling anomalies will begin. (See also...) Figure 5 , Figure 5 This is a flowchart of a credit control management method provided in an embodiment of the present invention, wherein the credit control management method includes steps S1 to S4.

[0034] S1. Obtain the credit control execution results corresponding to all user accounts in the business system according to the preset cycle; wherein, each user account is associated with at least one main product, and each main product is pre-configured with the corresponding credit control lifecycle stage and the credit control rules associated with each stage.

[0035] For example, the credit control execution result refers to the actual credit control status data of user accounts in the business system, including the current lifecycle stage of the account, balance information (dedicated balance, general balance, etc.), arrears duration, service usage status, rule trigger records, etc., which can be synchronously obtained from business systems such as NGBOSS, CRM, and BRM.

[0036] S2. Based on the credit control execution results, filter out target user accounts in abnormal scenarios; wherein, the abnormal scenarios include at least one of the following: no credit control rules, failure to stop when it should be stopped, failure to open when it should be opened, failure to close when the account is suspended, and credit status stagnation.

[0037] For example, a scenario with no credit control rules refers to a user account whose associated product has no configured credit control lifecycle stages and corresponding rules. A scenario where an account should be suspended but is not, refers to a user account that meets the suspension rules but is still in normal service. A scenario where an account should be opened but is not, refers to a user account that meets the opening rules but has not been restored to normal service. A scenario where an account is suspended but not closed, refers to a user account that has been suspended for a long time and meets the closure conditions but has not been closed. A scenario where credit status remains suspended, refers to a user account that is neither in normal use nor completely suspended, and this status continues for more than a preset time limit (e.g., 30 days).

[0038] Further, step S2 specifically includes: comparing the consistency between the credit control execution result and the credit control lifecycle stage, and filtering out user accounts with inconsistent comparison results as target user accounts in abnormal scenarios.

[0039] For example, the system compares the user's actual credit control execution result (such as current status, balance, and arrears duration) with the pre-configured lifecycle stage rules of the associated product. If the actual status does not match the required stage, such as failing to suspend service despite meeting the suspension rules, it is judged as abnormal and marked as a target user account. For instance, user account User0001 is associated with product 9600, and the actual credit control execution result is "9 days of arrears, service normal," while the pre-configured rules of product 9601 require "service suspension if arrears exceed 8 days." The two comparison results are inconsistent, and the system judges this user account as a target user account in the scenario of failure to suspend service when it should have. As another example, user account User0002 is associated with a personal mobile phone plan, but there are no associated credit control rules. After comparison, it is judged as a scenario without credit control rules.

[0040] S3. Based on the credit control rules of the main product to which the target user account belongs, conduct an audit query on the target user account.

[0041] For example, for a target user account, the system retrieves the pre-configured credit control rules of its associated main product and combines this with account details data from the business system, such as recharge records, arrears details, and rule trigger logs, to investigate the specific reasons for the anomaly. This includes whether there are rule configuration conflicts, whether data synchronization is delayed, and whether the account has any special exemption conditions. For instance, for user account User0001 that should have been suspended but was not, the system first retrieves the suspension rules for that product. If the rule is that a dedicated balance of less than 0 yuan and arrears exceeding 8 days will trigger suspension, the system then queries the business system records for user account User0001 to verify whether the balance calculation is accurate, whether the arrears duration statistics are correct, and whether a suspension work order has been generated. If, after verification, it is determined that the balance calculation is accurate, the arrears duration statistics are correct, and the suspension work order has not been generated, the cause is further traced back to the data synchronization delay between the NGBOSS system and the credit control management system.

[0042] S4. Summarize the audit query results and generate an credit control verification report based on the audit query results.

[0043] For example, information such as the anomaly type, audit reason, involved main product, and user type of all target user accounts is integrated. Statistical data is categorized by anomaly scenario, such as the number and percentage of target users in each scenario. The issues requiring rectification and the corresponding responsible modules are clearly marked, and a standardized credit control verification report is generated to support subsequent rectification and rule optimization decisions. The report will clearly record "User account User0001, associated with product 9601, anomaly type: failed to stop when required, audit reason: NGBOSS data synchronization delay, recommended to complete data synchronization and trigger a shutdown work order within n hours," while also marking the scope of the anomaly, the person responsible for rectification, and the completion deadline, providing a clear basis for subsequent rectification.

[0044] In this embodiment of the invention, by establishing a binding relationship between the main product, the credit control lifecycle stage, and the credit control rules, the problems of fragmented and independent credit control rules and chaotic matching relationships with products / customers in the prior art are solved. It supports standardized rule maintenance according to multiple dimensions, allows accurate querying of the rule configuration of any main product, reduces the manpower cost of rule management, and achieves systematic and clear control of credit control rules. Furthermore, by automatically acquiring the credit control execution results of all users at a preset cycle, replacing the traditional manual audit mode, it avoids the lag and judgment errors of manual verification, and improves the efficiency and coverage of credit control execution verification, ensuring no abnormal scenarios are missed. Moreover, by clearly defining abnormal scenarios and using a rule-oriented hierarchical audit logic, the causes of abnormalities can be accurately located, providing a clear basis for abnormal handling, ensuring the accuracy and timeliness of user account suspension and activation operations, strengthening the operator's ability to control account risks, and reducing user experience degradation caused by improper account status handling.

[0045] Furthermore, when the abnormal scenario is a scenario where it should have stopped but did not, or a scenario where it should have started but did not, step S3 specifically includes steps S31 to S32.

[0046] S31. If the target user account's main product is configured with credit control rules, then according to the credit control lifecycle stage corresponding to the credit control rules, check whether the target user account has met the triggering conditions of the credit control rules.

[0047] For example, firstly, confirm that the main product associated with the target user account has completed the credit control rule configuration, and clarify the full credit control lifecycle stage corresponding to the main product and the credit control rules bound to each stage. Then, retrieve the credit control rules for the specific lifecycle stage (suspension stage or activation stage) corresponding to the current abnormal scenario (failure to stop when it should have been stopped or failure to activate when it should have been activated), extract the preset triggering conditions in the rules, such as balance threshold, overdue payment duration threshold, user attribute restrictions, etc., and systematically verify them with the actual credit control data of the target user account to determine whether the user's actual status meets the conditions for triggering the rules.

[0048] S32. If the triggering condition is not met, the preset matching condition of the credit control rule is compared with the actual data of the target user account to determine the reason for the abnormality of the target user account.

[0049] For example, when it is confirmed that the target user account has not met the triggering conditions of the corresponding credit control rule, the system further breaks down all the preset matching conditions included in the credit control rule, including but not limited to multi-dimensional limiting conditions such as user type, payment method, credit control mode, and product attributes. These preset matching conditions are compared item by item with the actual data of the target user account in the business system (such as user registration information, contract type, account attribute records, etc.) to locate the specific dimensions where the preset conditions do not match the actual data, thereby clarifying the root cause of the abnormal scenario where the target user account is not stopped when it should be stopped or not opened when it should be opened.

[0050] Furthermore, when the abnormal scenario is a scenario where the system should have stopped but did not, after executing step S31, the method further includes: if the triggering condition is met, obtaining the shutdown condition of the target user account; and determining the abnormal reason of the target user account based on the shutdown condition.

[0051] For example, when it is confirmed that the target user account has met the shutdown rule triggering conditions of the corresponding main product, but the shutdown operation has not been executed, the system of preset complete shutdown conditions of the main product is further retrieved, including execution restriction conditions and business constraint conditions in addition to the triggering conditions. Combined with the user's work order flow record, account special identifier, system configuration parameters and other data in the business system, the nodes and reasons for the shutdown process not being executed normally are checked layer by layer to ensure the comprehensiveness and accuracy of anomaly tracing.

[0052] Specifically, this invention provides an example of signal control shutdown monitoring: ① Conditions: The current user status is normal; simulate outstanding charges after account cancellation; specify the number of months of outstanding charges, user type, etc. ② Check as follows: a. Based on the main product associated with the target user account, first check whether the corresponding shutdown information control rules have been configured; if no shutdown-related information control rules or lifecycle stage binding relationships have been configured, mark the abnormality as "no shutdown information control rules"; b. If a suspension credit control rule has been configured, further verify whether the user's actual data (such as the amount of arrears after simulated cancellation, the duration of arrears, user attributes, etc.) matches the preset trigger conditions in the rule; if they do not match, analyze the specific mismatch dimensions. Possible reasons for the anomaly include: the credit control level does not match the user's current credit level, the customer classification does not meet the rule's defined range, the account fee data does not meet the fee expression set in the rule (such as the combination of dedicated balance and general balance not meeting the standard), and the credit control status is in a stagnation state (i.e., the current user's credit control status is neither in use nor completely suspended, and this stagnation state lasts for more than 30 days). c. If the user's actual data matches the triggering conditions of the suspension credit control rules, continue to check whether the suspension conditions are met; if not, the abnormal reason may be: the user is in the process of deduction or collection (automatic payment process not completed), the user belongs to the red list protection object (enjoying the privilege of no suspension), the number of real-time suspensions on the day has reached the system preset limit, the monthly settlement suspension volume exceeds the configured threshold, the current period is in the implementation period of the holiday no suspension policy, and other business constraint scenarios. d. If the shutdown conditions have been met, trace the status of the shutdown work order; if the work order is in progress or has failed, mark the reason for the abnormality as the work order is in progress or has failed, and simultaneously indicate the current work order's stage (such as NGBOSS, BRM, CRM or other dedicated business platforms) to facilitate the location of process blockage nodes. e. If the shutdown conditions have been met and the shutdown work order has been successfully executed, but the user is still in a normal state, check whether there have been any subsequent intervention operations. The abnormal reason may be that the system was forcibly restarted after the work order was executed, such as manual background operation or system failure causing the status to roll back.

[0053] Furthermore, when the abnormal scenario is a scenario where the device should be turned on but is not, after executing step S31, the method further includes: if the triggering condition is met, obtaining the power-on condition of the target user account; and determining the abnormal reason of the target user account based on the power-on condition.

[0054] For example, when it is confirmed that the target user account has met the activation rules triggering conditions of the corresponding main product (such as balance reaching the target, overdue payment being settled, etc.), but is still in a suspended state and has not resumed service, the system of preset activation conditions of the main product is further retrieved, including execution constraints and business process conditions in addition to the triggering conditions. Combined with the user's activation work order flow record, account special status identifier, system configuration parameters and other real data in the business system, the nodes and root causes of the activation process not being implemented normally are checked layer by layer to ensure the comprehensiveness of the traceability of the abnormal cause, and the entire verification process does not interfere with the normal operation of the existing credit control business.

[0055] Specifically, this invention provides an example of signal control power-on monitoring: ①Conditions: The current user is offline, there is a balance after simulated account cancellation, and the user type is specified.

[0056] ② Check as follows: a. Check whether the main product has configured signal control rules. If no signal control rules are configured, mark the abnormality as "no power-on signal control rules". b. If credit control rules have been configured, check whether the conditions of the credit control rules have been met. If the conditions of the credit control rules are not matched, the reasons may be that the credit control level is not matched, the customer classification is not matched, the cost expression is not met, or the credit control status is stuck. c. If the conditions for starting the machine are met but the construction has not been completed or has failed, the reason may be that the work order is in progress or the work order has failed, and the current work order belongs to a certain stage (BOSS, BRM, XXX system, etc.). d. If the conditions for starting up have been met and the work order has been successfully completed, the reason may be forced shutdown.

[0057] It should be noted that simulated account cancellation, rather than actual account cancellation, is used in the credit control shutdown / startup monitoring. This is to avoid interfering with the user's actual account status and the operator's billing records, ensuring the security and independence of business operations. Simulated account cancellation refers to virtual accounting based on the user's actual account data in the business system (such as account balance, bill amount, outstanding fees, etc.) and following the real account cancellation logic (such as fee deduction order, balance calculation rules). It is only used to verify whether the user meets the credit control rule triggering conditions (such as shutdown threshold, startup balance requirements). The entire process does not modify the user's actual account balance, does not generate real account cancellation records, and does not affect subsequent billing and settlement; it is a read-only accounting process.

[0058] Furthermore, this invention is not merely for simulating scenarios, but rather for monitoring and auditing real-world credit control anomalies within business systems. Whether it's a scenario with no credit control rules, a scenario where service should have been suspended but wasn't, a scenario where service should have been activated but wasn't, a scenario where service was suspended but not cancelled, or a scenario where credit status remains inactive, these are all actual mismatches between the status and rules occurring in systems like NGBOSS and CRM. Simulated account cancellation is only to provide a basis for anomaly detection, not to fabricate anomaly scenarios. This section only provides detailed examples of the anomaly cause analysis for scenarios with no credit control rules, a scenario where service should have been suspended but wasn't, and a scenario where service should have been activated but wasn't. For scenarios where service was suspended but not cancelled and credit status remains inactive, the anomaly cause verification logic can refer to the verification framework of the above scenarios, combined with the corresponding credit control rules and business processes. For example, in the scenario where service was suspended but not cancelled, the verification first confirms whether the user meets the preset cancellation conditions (such as suspension time exceeding 90 days, no outstanding fees, etc.). If the conditions are met but the account is not cancelled, further investigation is needed to trace the anomaly cause, which may include the cancellation rules not being configured or ineffective, or the account having unfinished business (such as not unsubscribing from value-added services). Examples of issues include: failure to generate a cancellation work order or failure to complete the cancellation process; manual intervention to suspend the cancellation process; and the current system stage to which the account belongs. When the credit status is stagnant, the first step in the verification is to confirm whether the user's credit control status is neither in use nor completely suspended, and whether the stagnant period exceeds 30 days. If this characteristic is met, further analysis of the abnormal reasons is needed. These may include missing credit control status flow rules, failure of work order execution in the preceding stage leading to status stagnation, system data synchronization delay causing untimely status updates, and special business constraints of the user preventing normal status flow. The root cause can be located by retrieving the credit control status change log and work order flow records.

[0059] See Figure 6 , Figure 6 This is a structural block diagram of a signal control management device 100 provided in an embodiment of the present invention. The signal control management device 100 includes: The credit control execution result acquisition module 11 is used to acquire the credit control execution results corresponding to all user accounts in the business system according to a preset period; wherein, each user account is associated with at least one main product, and each main product is pre-configured with the corresponding credit control lifecycle stage and the credit control rules associated with each stage; The target user account filtering module 12 is used to filter out target user accounts in abnormal scenarios based on the credit control execution results. Audit query module 13 is used to perform audit queries on the target user account based on the credit control rules of the main product to which the target user account belongs; The credit control verification report generation module 14 is used to summarize the audit query results and generate a credit control verification report based on the audit query results.

[0060] Furthermore, the signal control management device 100 also includes: The data synchronization module is used to synchronize the existing credit control rule data in the business system as monitoring base data; when the business system performs an update operation on the credit control rule, it controls the monitoring base data to be updated synchronously. The pre-configuration module is used to configure the corresponding credit control lifecycle stages and associated credit control rules for all main products in the business system based on the monitoring basic data.

[0061] It is worth noting that the working process of each module in the signal control management device 100 described in the embodiments of the present invention can refer to the working process of the signal control management method described in the above embodiments, and will not be repeated here.

[0062] See Figure 7 , Figure 7 This is a structural block diagram of a signal control management device 200 provided in an embodiment of the present invention. The signal control management device 200 includes a processor 21, a memory 22, and a computer program stored in the memory 22 and executable on the processor 21. When the processor 21 executes the computer program, it implements the steps in the various signal control management method embodiments described above.

[0063] For example, the computer program can be divided into one or more modules / units, which are stored in the memory 22 and executed by the processor 21 to complete the present invention. The one or more modules / units can be a series of computer program instruction segments capable of performing specific functions, which describe the execution process of the computer program in the signal control management device 200.

[0064] The signal control management device 200 may include, but is not limited to, a processor 21 and a memory 22. Those skilled in the art will understand that the schematic diagram is merely an example of the signal control management device 200 and does not constitute a limitation on the device. It may include more or fewer components than illustrated, or combine certain components, or use different components. For example, the signal control management device 200 may also include input / output devices, network access devices, buses, etc.

[0065] The processor 21 can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or any conventional processor. The processor 21 is the control center of the signal control management device 200, connecting all parts of the signal control management device 200 via various interfaces and lines.

[0066] The memory 22 can be used to store the computer programs and / or modules. The processor 21 implements various functions of the signal control management device 200 by running or executing the computer programs and / or modules stored in the memory 22 and calling the data stored in the memory 22. The memory 22 may mainly include a program storage area and a data storage area. The program storage area may store the operating system, at least one application program required for a function (such as sound playback function, image playback function, etc.), etc.; the data storage area may store data created according to the use of the mobile phone (such as audio data, phonebook, etc.). In addition, the memory 22 may include high-speed random access memory, and may also include non-volatile memory, such as hard disk, memory, plug-in hard disk, smart media card (SMC), secure digital (SD) card, flash card, at least one disk storage device, flash memory device, or other volatile solid-state storage device.

[0067] Wherein, if the modules / units integrated in the signal control management device 200 are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, all or part of the processes in the methods of the above embodiments of the present invention can also be implemented by a computer program instructing related hardware. The computer program can be stored in a computer-readable storage medium, and when the computer program is executed by the processor 21, it can implement the steps of the various method embodiments described above. Wherein, the computer program includes computer program code, which can be in the form of source code, object code, executable file, or some intermediate form, etc. The computer-readable medium can include: any entity or device capable of carrying the computer program code, recording medium, USB flash drive, portable hard drive, magnetic disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electrical carrier signal, telecommunication signal, and software distribution medium, etc.

[0068] Furthermore, the present invention also provides a computer program product, including a computer program / instruction, which, when executed by a processor, implements the signal control management method as described in any of the above embodiments.

[0069] The above description represents the preferred embodiments of the present invention. It should be noted that those skilled in the art can make various improvements and modifications without departing from the principles of the present invention, and these improvements and modifications are also considered to be within the scope of protection of the present invention.

Claims

1. A credit control management method, characterized in that, include: The system retrieves the credit control execution results corresponding to all user accounts in the business system according to a preset cycle; each user account is associated with at least one main product, and each main product is pre-configured with the corresponding credit control lifecycle stage and the credit control rules associated with each stage; Based on the results of the credit control execution, target user accounts in abnormal scenarios are selected; Based on the credit control rules of the main product to which the target user account belongs, an audit query is performed on the target user account; Summarize the audit query results and generate an credit control verification report based on the audit query results.

2. The credit control management method as described in claim 1, characterized in that, The process of filtering out target user accounts in abnormal scenarios based on the credit control execution results includes: Based on the consistency between the credit control execution result and the credit control lifecycle stage, user accounts with inconsistent comparison results are selected as target user accounts in abnormal scenarios.

3. The information control management method as described in claim 1 or 2, characterized in that, The abnormal scenarios include at least one of the following: scenarios with no credit control rules, scenarios where service should be suspended but is not, scenarios where service should be opened but is not, scenarios where service is suspended but account is not closed, and scenarios where credit status remains unchanged.

4. The information control management method as described in claim 1, characterized in that, Before periodically checking the credit control execution results of all user accounts corresponding to the main products in the business system, the method further includes: Synchronize the existing credit control rules data in the business system as the monitoring basis data; When the business system performs an update operation on the credit control rules, it controls the monitoring basic data to be updated synchronously. Based on the aforementioned monitoring data, configure the corresponding credit control lifecycle stages and associated credit control rules for all main products in the business system.

5. The information control management method as described in claim 3, characterized in that, When the abnormal scenario is a scenario where a shutdown should have been suspended but was not, or a scenario where an activation should have been made but was not, the audit query of the target user account based on the credit control rules of the main product to which the target user account belongs includes: If the target user account's main product is configured with credit control rules, then according to the credit control lifecycle stage corresponding to the credit control rules, check whether the target user account meets the triggering conditions of the credit control rules; If the triggering condition is not met, the preset matching conditions of the credit control rule are compared with the actual data of the target user account to determine the cause of the abnormality of the target user account.

6. The information control management method as described in claim 5, characterized in that, When the abnormal scenario is a scenario where a suspension should have been initiated but was not, after verifying whether the target user account meets the triggering conditions of the credit control rule, the method further includes: If the triggering condition is met, obtain the shutdown condition of the target user account; The cause of the abnormality of the target user account is determined based on the aforementioned shutdown conditions.

7. The information control management method as described in claim 5, characterized in that, When the abnormal scenario is a scenario where an account should have been opened but was not, after verifying whether the target user account meets the triggering conditions of the credit control rule, the method further includes: If the triggering condition is met, obtain the power-on conditions of the target user account; The cause of the abnormality of the target user account is determined based on the aforementioned boot conditions.

8. A signal control management device, characterized in that, include: The credit control execution result acquisition module is used to acquire the credit control execution results corresponding to all user accounts in the business system according to a preset period. Each user account is associated with at least one main product, and each main product is pre-configured with the corresponding credit control lifecycle stage and the credit control rules associated with each stage. The target user account filtering module is used to filter out target user accounts in abnormal scenarios based on the credit control execution results; The audit query module is used to perform audit queries on the target user account based on the credit control rules of the main product to which the target user account belongs; The credit control verification report generation module is used to summarize the audit query results and generate a credit control verification report based on the audit query results.

9. A signal control management device, characterized in that, It includes a processor, a memory, and a computer program stored in the memory and configured to be executed by the processor, wherein the processor, when executing the computer program, implements the information control management method as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes a stored computer program, wherein, when the computer program is executed, it controls the device where the computer-readable storage medium is located to perform the information control management method as described in any one of claims 1 to 7.

11. A computer program product, characterized in that, It includes computer instructions, which, when executed by a processor, implement the information control management method as described in any one of claims 1 to 7.

Images