Automatic guarantee method and system

Abstract

The invention provides an automatic guarantee method and system. The method comprises the following steps: determining an abnormal event of cloud card equipment; if the abnormal event belongs to the deterministic index, determining a first diagnosis result corresponding to the abnormal event, and executing a corresponding action according to the first diagnosis result based on a preset action engine rule; if the abnormal event does not belong to the deterministic index, a detection instruction is sent to the cloud card device, and the detection instruction is used for indicating the cloud card device to collect device state information; receiving equipment state information returned by the cloud card equipment for the detection instruction; determining a second diagnosis result corresponding to the equipment state information; and executing a corresponding action according to the second diagnosis result based on a preset action engine rule. According to the method and the device, various types of abnormal events can be automatically diagnosed and analyzed and processed according to the diagnosis result, the abnormity can be found in time, and high-quality services can be provided for a large number of online users while the dependence on manpower can be reduced.

Description

Technical Field

[0001] This application belongs to the field of control system technology, and in particular relates to an automated protection method and system. Background Technology

[0002] The cloud card allows the terminal to remotely and dynamically switch operators and plans without inserting a physical SIM card, thereby saving roaming fees, hardware costs, and other expenses, while enabling users to receive local networks.

[0003] During the use of the cloud SIM card, the device may appear to be able to connect to the network normally, but the network speed may be poor, resulting in a poor user experience, due to reasons such as the user moving into an area with weak signal coverage of the operator's network or network congestion. Furthermore, the device may experience speed throttling due to cloud SIM card data usage, and service may be temporarily interrupted after changing the SIM card.

[0004] The current solutions to these problems generally involve manual discovery and handling by operations and maintenance personnel. However, the limited manpower available to operations and maintenance personnel makes it impossible to provide users with high-quality service. Summary of the Invention

[0005] This application provides an automated maintenance method, system, electronic device, computer-readable storage medium, and computer program product, which can solve the problem that limited maintenance personnel cannot promptly and proactively detect equipment anomalies, resulting in the inability to provide high-quality services.

[0006] In a first aspect, embodiments of this application provide an automated protection method, including: Identify abnormal events in the cloud card device; If the abnormal event is a deterministic indicator, then the first diagnostic result corresponding to the abnormal event is determined, and the corresponding action is executed according to the first diagnostic result based on the preset action engine rules. If the abnormal event is not a deterministic indicator, a detection command is sent to the cloud card device, which is used to instruct the cloud card device to collect device status information; Receive the device status information returned by the cloud card device in response to the detection command; Determine the second diagnostic result corresponding to the device status information; Based on the preset action engine rules, the corresponding action is executed according to the second diagnostic result.

[0007] In some embodiments, sending a detection command to the cloud card device includes: If the abnormal event indicates card splitting or card replacement, a first speed measurement command is sent to the cloud card device. The first speed measurement command is used to instruct the cloud card device to perform a connectivity detection operation to collect the device status information. If the abnormal event characterization is abnormal, a second speed test command is sent to the cloud card device. The second speed test command is used to instruct the cloud card device to perform a throughput test operation to collect the device status information.

[0008] In some embodiments, the step of sending a second speed measurement command to the cloud card device if the abnormal event characterizes an abnormality includes: If the abnormal event indicates an abnormality, then after determining that the cloud card device is in standby mode, the second speed measurement command is sent to the cloud card device.

[0009] In some embodiments, the abnormal event includes at least one event that is not a deterministic indicator, the detection instruction is triggered by the first event that is not a deterministic indicator, and the reception time of each of the events that are not deterministic indicators is within the validity period of the detection instruction; The determination of the second diagnostic result corresponding to the device status information includes: Iterate through each of the events that do not belong to deterministic indicators, and determine the device status information as the detection result of each of the events that do not belong to deterministic indicators; Based on the device status information, the second diagnostic result is determined within the validity period of the detection instruction.

[0010] In some embodiments, the step of executing the corresponding action based on the first diagnostic result according to preset action engine rules includes: Obtain the user level of the cloud card device; Based on the preset action engine rules, execute the corresponding action according to the user level and the first diagnostic result; The step of executing the corresponding action based on the preset action engine rules and the second diagnostic result includes: Obtain the user level of the cloud card device; Based on the preset action engine rules, the corresponding action is executed according to the user level and the second diagnostic result.

[0011] In some embodiments, the method further includes: Record the device information and user information of the cloud card device, the abnormal event, the diagnosis result of the abnormal event, the diagnosis method of the abnormal event, the trigger time, the reception time of the abnormal event, and the operation and operation result triggered by the abnormal event.

[0012] Secondly, embodiments of this application provide an automated assurance system, including: a business system and a maintenance system; The aforementioned business system is used to determine abnormal events of cloud card devices; The maintenance system is used to determine the first diagnostic result corresponding to the abnormal event if the abnormal event is a deterministic indicator, and to perform the corresponding action based on the first diagnostic result according to the preset action engine rules. It is also used to send a detection command to the cloud card device if the abnormal event is not a deterministic indicator, and the detection command is used to instruct the cloud card device to collect device status information; It is also used to receive the device status information returned by the cloud card device in response to the detection command; It is also used to determine the second diagnostic result corresponding to the device status information; It is also used to perform corresponding actions based on the preset action engine rules and the second diagnostic result.

[0013] In some embodiments, the business system includes a business support module, a cloud card management and scheduling module, and an operation and maintenance monitoring module; The business support module is used to monitor business operations and identify abnormal business events. The cloud card management and scheduling module is used to monitor the lifecycle management and scheduling management of the cloud card, and to identify abnormal cloud card events. The operation and maintenance monitoring module is used to monitor online users and online devices, and to identify abnormal operation and maintenance events; The abnormal events include the business abnormal events, the cloud card abnormal events, and the operation and maintenance abnormal events.

[0014] Thirdly, embodiments of this application provide an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the method as described in any one of the first aspects above.

[0015] Fourthly, embodiments of this application provide a computer-readable storage medium storing a computer program that, when executed by a processor, implements the method as described in any one of the first aspects above.

[0016] Fifthly, embodiments of this application provide a computer program product that, when run on an electronic device, causes the electronic device to perform the method described in any one of the first aspects above.

[0017] The beneficial effects of the embodiments in this application compared with the prior art are: This application embodiment achieves real-time and timely notification of cloud card device anomalies by determining abnormal events of the cloud card device; Furthermore, if the abnormal event is a deterministic indicator, the corresponding action is executed based on the first diagnostic result of the abnormal event according to the preset action engine rules; if the abnormal event is not a deterministic indicator, a detection command is sent to the cloud card device; the device status information returned by the cloud card device is received; and the corresponding action is executed based on the second diagnostic result of the device status information according to the preset action engine rules. This achieves automated diagnosis and analysis of various types of abnormal events and processing based on the diagnostic results, enabling timely detection of abnormalities, reducing reliance on manpower while providing high-quality services to a large number of online users.

[0018] It is understood that the beneficial effects of the second to fifth aspects mentioned above can be found in the relevant descriptions in the first aspect mentioned above, and will not be repeated here. Attached Figure Description

[0019] To more clearly illustrate the technical solutions in the embodiments of this application, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0020] Figure 1 This is a flowchart illustrating an embodiment of the automated protection method provided in this application; Figure 2 This is a schematic diagram of the first structure of an automated protection system provided in an embodiment of this application; Figure 3 This is a schematic diagram of a second structure of an automated protection system provided in an embodiment of this application; Figure 4 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0021] In the following description, specific details such as particular system architectures and techniques are set forth for illustrative purposes and not for limitation, in order to provide a thorough understanding of the embodiments of this application. However, those skilled in the art will understand that this application may also be implemented in other embodiments without these specific details. In other instances, detailed descriptions of well-known systems, apparatuses, circuits, and methods have been omitted so as not to obscure the description of this application with unnecessary detail.

[0022] It should be understood that, when used in this application specification and the appended claims, the term "comprising" indicates the presence of the described features, integrals, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, integrals, steps, operations, elements, components and / or a collection thereof.

[0023] It should also be understood that the term “and / or” as used in this application specification and the appended claims means any combination of one or more of the associated listed items and all possible combinations, and includes such combinations.

[0024] As used in this application specification and the appended claims, the term "if" may be interpreted, depending on the context, as "when," "once," "in response to determination," or "in response to detection." Similarly, the phrase "if determined" or "if detected [the described condition or event]" may be interpreted, depending on the context, as meaning "once determined," "in response to determination," "once detected [the described condition or event]," or "in response to detection [the described condition or event]."

[0025] Furthermore, in the description of this application and the appended claims, the terms "first," "second," "third," etc., are used only to distinguish descriptions and should not be construed as indicating or implying relative importance.

[0026] References to "one embodiment" or "some embodiments" as described in this specification mean that one or more embodiments of this application include a specific feature, structure, or characteristic described in connection with that embodiment. Therefore, the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in still other embodiments," etc., appearing in different parts of this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized.

[0027] Please refer to Figure 1 , Figure 1 The method shown includes steps S11 to S16, which are described in detail below. The method is applied to an automated support system and includes: S11: Identify abnormal events in the cloud card device.

[0028] The automated assurance system interacts with the cloud SIM card device in real time to exchange business information. It analyzes this information and triggers corresponding exception events when anomalies are detected. The cloud SIM card device is a device equipped with a cloud SIM card.

[0029] As an example, business information includes user plan usage information, device status, etc. Abnormal events include insufficient data allowance, abnormal device network status, abnormal connection status, etc.

[0030] S12: If the abnormal event is a deterministic indicator, determine the first diagnostic result corresponding to the abnormal event, and execute the corresponding action based on the preset action engine rules.

[0031] When an abnormal event is a deterministic indicator, it can be objectively and directly determined that there is an anomaly in the current service. Actions can be directly triggered according to the preset action engine rules. Therefore, the anomaly in the current service can be directly diagnosed based on the abnormal event, and the corresponding action can be found in the preset action engine rules.

[0032] In some implementations, the preset action engine rules are AI engine rules. The AI ​​engine rules can preset different AI actions corresponding to different scenarios. The triggered AI actions are action sequences that are automatically generated, identified, or optimized by the artificial intelligence system. The action sequence includes at least one continuous operation.

[0033] As an example, abnormal events that fall under deterministic indicators include insufficient remaining data in a user's data plan and failure to be allocated a cloud SIM card.

[0034] If the diagnostic result indicates that the user's remaining data allowance is insufficient, the corresponding action is to send an SMS and / or email alert to the target user to remind them to recharge. The target user is the user's registered email address or registered mobile phone number associated with the cloud card device.

[0035] If the diagnostic result for "No Card Available" is "No Card", the corresponding action is to send an SMS and / or email alert to the operations and maintenance group to indicate that resources need to be replenished. The operations and maintenance group is the cloud card resource operations and maintenance email group.

[0036] S13: If the abnormal event is not a deterministic indicator, send a detection command to the cloud card device.

[0037] Among them, the detection command is used to instruct the cloud card device to collect device status information.

[0038] When an abnormal event is not a deterministic indicator and it is impossible to directly determine whether the current service is abnormal, further detection and analysis are required. Instructions are sent to the cloud card device to determine whether the current service of the cloud card device is abnormal.

[0039] As examples, abnormal events that are not considered deterministic indicators include persistent weak signals and persistently reported low traffic volumes.

[0040] In some embodiments, step S13 includes: S131: If the abnormal event indicates card splitting or card replacement, send the first speed measurement command to the cloud card device.

[0041] The first speed measurement command instructs the cloud card device to perform a connectivity detection operation to collect device status information. Connectivity detection can also be referred to as a simple test.

[0042] When a card is first issued to a cloud card device or a card is replaced during use, and a corresponding card issuance or replacement event is obtained, it is impossible to directly determine whether the cloud card can provide normal service. Therefore, a first speed test command is sent to the cloud card device so that subsequent speed test results can clearly indicate whether there is an anomaly.

[0043] In some implementations, connectivity detection operations involve performing a ping action and / or an HTTP download action to measure speed. The ping action corresponds to obtaining the ping result and latency, while the HTTP download action corresponds to obtaining the uplink and downlink speed measurement results. Device status information includes the ping result, latency, and / or uplink and downlink speed measurement results.

[0044] Among them, the ping result is "ping failed" and the latency exceeds the threshold. The uplink and downlink speed test results are "uplink and downlink data cannot be connected", indicating that the cloud card cannot provide normal service.

[0045] The ping result shows that the ping was successful and the latency did not exceed the threshold. The uplink and downlink speed test results show that the uplink and downlink data can be connected, indicating that the cloud card can provide services normally.

[0046] S132: If the abnormal event indicates an abnormality in usage, a second speed measurement command is sent to the cloud card device.

[0047] The second speed test command instructs the cloud card device to perform a throughput test to collect device status information. The throughput test can also be called a Speedtest.

[0048] If an abnormal event is received during use, and the corresponding usage abnormal event is obtained, it is not possible to directly determine whether the current service is abnormal. Therefore, a second speed test command is sent to the cloud card device so that the abnormality can be clearly determined based on the feedback rate result.

[0049] As examples, abnormal events that characterize usage anomalies include persistently low flow rates, persistently weak signals, etc.

[0050] In some implementations, the throughput test operation involves connecting to multiple speed test URLs, performing upload and download operations, and calculating the uplink and downlink network speeds of the current device in real time. The device status information includes the uplink and downlink speed results.

[0051] Among them, the failure of the uplink and downlink rates to reach the threshold indicates that there is an anomaly in the current service.

[0052] Reaching the threshold for uplink and downlink rates indicates that there are no anomalies in the current service.

[0053] The detection commands include a first speed measurement command and a second speed measurement command.

[0054] In some embodiments, during actual use, the cloud card device may change after an anomaly is reported, resulting in a high-traffic state. If it can be determined that the service has changed from abnormal to normal use, further processing can be discontinued. Therefore, further processing is only continued when it is confirmed that the cloud card device is still abnormal, reducing operations, minimizing the impact on service quality, and further improving the service experience.

[0055] Step S132 includes: If the abnormal event indicates an abnormality in usage, a second speed measurement command is sent to the cloud card device after determining that the cloud card device is in standby mode.

[0056] Upon receiving a relevant abnormal event during use, the system interacts with the cloud card device to determine that the cloud card device is continuously in a low-traffic or no-traffic state and is still experiencing abnormal usage. This leads to the determination that the cloud card device is in standby mode, and a second speed test command is sent to the cloud card device.

[0057] S14: Receive device status information returned by the cloud card device in response to the detection command.

[0058] S15: Determine the second diagnostic result corresponding to the equipment status information.

[0059] As an example, device status information includes ping failure, latency exceeding the threshold, and / or inability to transmit uplink and downlink data, with the corresponding diagnostic result being that the cloud card cannot provide normal service.

[0060] Device status information includes ping success, latency not exceeding the threshold, and / or uplink and downlink data connectivity. The corresponding diagnostic result is that the cloud card can provide services normally.

[0061] Device status information includes uplink and downlink rates not reaching the threshold, and the corresponding diagnostic result is that the current service is abnormal.

[0062] Device status information includes uplink and downlink rates reaching the threshold, and the corresponding diagnostic result is that there are no abnormalities in the current service.

[0063] S16: Based on the preset action engine rules, execute the corresponding action according to the second diagnostic result.

[0064] As an example, if the second diagnostic result is that the cloud card can provide services normally or that there are no abnormalities in the current service, no action will be taken.

[0065] When the second diagnostic result is that the cloud card cannot provide normal service, the corresponding action is to issue an instruction to switch operators so that the cloud card can provide normal service.

[0066] When the second diagnostic result indicates that the current service is abnormal, the corresponding action is to send an SMS and / or email alert to the operations and maintenance group, which is the operations and maintenance email group corresponding to the cloud card device.

[0067] In some embodiments, advanced users have a higher service level and need to ensure a good user experience. Some abnormal events need to be handled by advanced users.

[0068] Correspondingly, step S12 includes: S121: Obtain the user level of the cloud card device.

[0069] S122: Based on preset action engine rules, execute the corresponding action according to the user level and the first diagnostic result.

[0070] As an example, if the diagnostic result for device speed limiting is determined to be speed restriction, and the user level of the cloud card device is determined to be advanced user, the corresponding action is to remove the speed limit. If the user level of the cloud card device is determined to be ordinary user, the corresponding action is to do nothing.

[0071] Step S16 includes: S161: Obtain the user level of the cloud card device.

[0072] S162: Based on preset action engine rules, execute the corresponding action according to the user level and the second diagnostic result.

[0073] As an example, the diagnostic result for a persistently weak signal is "signal poor". If the user level of the cloud SIM card device is determined to be a high-level user, the corresponding action is a throughput test, and an instruction to switch carriers is issued upon confirming a service anomaly. If the user level of the cloud SIM card device is determined to be a regular user, the corresponding action is a connectivity probe, and an SMS and / or email alert is sent to the operations and maintenance team upon confirming a service anomaly.

[0074] In some implementations, a query command is sent to the cloud card device to obtain the identification information of the cloud card device, and then the user level of the cloud card device is determined based on the identification information.

[0075] The technical solution of this application embodiment achieves real-time and timely notification of cloud card device anomalies by determining abnormal events of the cloud card device; Furthermore, if the abnormal event is a deterministic indicator, the corresponding action is executed based on the first diagnostic result of the abnormal event according to the preset action engine rules; if the abnormal event is not a deterministic indicator, a detection command is sent to the cloud card device; the device status information returned by the cloud card device is received; and the corresponding action is executed based on the second diagnostic result of the device status information according to the preset action engine rules. This achieves automated diagnosis and analysis of various types of abnormal events and processing based on the diagnostic results, enabling timely detection of abnormalities, reducing reliance on manpower while providing high-quality services to a large number of online users.

[0076] Understandably, real-time acquisition of abnormal events from cloud card devices, combined with pre-defined action engine rules, can monitor various abnormal scenarios, automatically and promptly locate the triggering causes of abnormal events, and then handle them in a timely manner. This enables the maintenance of a large number of online users while providing high-quality service. It can solve the problem of low service quality caused by the limited monitoring of abnormal scenarios by manual operation and maintenance, and the problem of low service quality caused by users only discovering abnormal events and locating the causes of problems after they are reported. It also solves the problem of limited manpower making it impossible to maintain a large number of online users.

[0077] In some embodiments, the abnormal event includes at least one event that is not a deterministic indicator, the detection instruction is triggered by the first event that is not a deterministic indicator, and the reception time of each event that is not a deterministic indicator is within the validity period of the detection instruction.

[0078] In practice, multiple abnormal events may occur within a given time period. Responding to multiple abnormal events and triggering multiple detection commands can degrade service quality. To reduce the triggering of multiple detection commands, the first event that does not belong to a deterministic indicator triggers the detection command. This command is then labeled with its type and status, and an expiration period is set. Setting an expiration period prevents the generation of new detection commands within that period.

[0079] As an example, the command type is either the first speed measurement command or the second speed measurement command. The status is "Executing".

[0080] Step S15 includes: S151: Traverse each event that does not belong to a deterministic indicator and determine the equipment status information as the detection result of each event that does not belong to a deterministic indicator.

[0081] S152: Based on the equipment status information, determine the second diagnostic result within the validity period of the testing instruction.

[0082] The system obtains the device status information returned by the cloud card device in response to the detection command triggered by the first event that does not belong to the deterministic indicator. It then iterates through each event that does not belong to the deterministic indicator and sets the device status information to the detection result of each event that does not belong to the deterministic indicator. This enables the system to mark each event that does not belong to the deterministic indicator as a transaction, indicating that each event that does not belong to the deterministic indicator has been diagnosed and processed.

[0083] As an example, an event of continuous low traffic is detected, triggering a second detection command, which is then sent to the cloud card device, and its validity period is set. Within the validity period, three more events that are not deterministic indicators are detected. After receiving the device status information returned by the cloud card device, these three events within the validity period are iterated through, and the detection results of the three events are set as the device status information.

[0084] By setting the device status information to the detection results of all events that are not deterministic indicators received within the validity period, the number of simultaneous triggering of multiple detection operations in a short period of time is reduced, resource consumption is reduced, service quality is guaranteed, and user experience is improved.

[0085] In some embodiments, the method further includes: Record the device information, user information, abnormal events, diagnostic results of abnormal events, diagnostic methods of abnormal events, trigger time, reception time, and operation and result of abnormal events triggered by the cloud card device.

[0086] In some implementations, it can also be set as a scheduled task to record the above content periodically, reducing resource consumption and making it easier to view user usage trends within a time period. Scheduled tasks can also be set for users of particular interest.

[0087] As an example, user information includes user account, user level, etc. Device information includes device type, online region, cloud card information, etc.

[0088] By recording the events that occur during the inspection process, an inspection report is generated and sent to the target group to promptly inform them and address any issues in a timely manner. It also facilitates the querying of the online status records of cloud card devices, providing information on user usage and experience.

[0089] It should be understood that the sequence number of each step in the above embodiments does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application. Furthermore, the data collection in the above embodiments is compliant, and its use or implementation does not involve any infringement upon public interests.

[0090] For ease of explanation, only the parts related to the embodiments of this application are shown in the methods described in the above embodiments.

[0091] Please refer to Figure 2 ,like Figure 2 As shown, the system includes a business system 10 and a maintenance system 11.

[0092] Business System 10 is used to determine abnormal events of cloud card devices.

[0093] In some implementations, the business system interacts with the cloud SIM card device via an access module. The cloud SIM card device then reports its status in real time, such as traffic and network conditions, through the access system.

[0094] In some implementations, the business system sends abnormal events to the maintenance system via API calls or message notifications.

[0095] The maintenance system 11 is used to determine the first diagnostic result corresponding to the abnormal event if the abnormal event is a deterministic indicator, and to execute the corresponding action based on the first diagnostic result according to the preset action engine rules. It is also used to send a detection command to the cloud card device if the abnormal event is not a deterministic indicator. The detection command is used to instruct the cloud card device to collect device status information. It is also used to receive device status information returned by the cloud card device in response to the detection command; It is also used to determine the second diagnostic result corresponding to the device status information, and to execute the corresponding action based on the preset action engine rules.

[0096] The maintenance system diagnoses and analyzes various abnormal events, determines the user's current usage status, triggers corresponding actions for abnormal events involving users, devices, and cloud cards, and automatically takes appropriate measures to ensure normal device operation.

[0097] In some embodiments, the business system 10 includes a business support module 101, a cloud card management and scheduling module 102, and an operation and maintenance monitoring module 103; The business support module 101 is used to monitor business operations and identify abnormal business events.

[0098] The user lifecycle includes the introduction, growth, maturity, dormancy, and churn phases. The introduction phase includes scenarios such as SIM card issuance and activation; the growth phase includes scenarios such as first call and first data package activation; the maturity phase includes scenarios such as contract bundling and high-consumption activities; and the dormancy phase includes scenarios such as multiple consecutive days without data or voice calls. The device lifecycle includes procurement and warehousing, sales, online use, failure and maintenance, and retirement and recycling. Procurement and warehousing includes scenarios such as device purchase and asset code generation; sales include scenarios such as device sales; online use includes scenarios such as device network registration and online timekeeping; failure and maintenance includes scenarios such as user reports of faults and device returns to the factory; and retirement and recycling include scenarios such as account cancellation and contract expiration.

[0099] Product information includes product definitions, product combinations, etc.

[0100] Account information includes account balance, account plan, etc.

[0101] Order information includes order validity period, order relationship, etc.

[0102] Business anomalies include abnormal user lifecycle states (disabled, illegal, etc.) that prevent users from logging in, insufficient user account balance, and insufficient remaining data in user plans.

[0103] The cloud card management and scheduling module 102 is used to monitor the lifecycle management and scheduling management of the cloud card and to identify abnormal events of the cloud card.

[0104] The cloud SIM card lifecycle includes creation, allocation, activation, use, replacement, and release. Creation includes scenarios such as SIM card pool creation; allocation includes scenarios such as locking the cloud SIM card upon receiving a user order; activation includes scenarios such as the cloud SIM card entering normal business mode; use includes scenarios such as normal internet access and retaining the SIM card number; replacement includes scenarios such as allocating a new SIM card due to insufficient data or signal degradation; and release includes scenarios such as deactivating the SIM card and recycling the cloud SIM card.

[0105] Cloud SIM card anomalies include situations such as the current national SIM card resource being under strain, insufficient remaining cloud SIM card traffic triggering a card replacement leading to service interruption, initial card distribution, and card replacement.

[0106] The operation and maintenance monitoring module 103 is used to monitor online users and online devices and identify abnormal operation and maintenance events.

[0107] Operational anomalies include multiple short-term restarts of online devices, persistently weak signals from online devices, and continuous reporting of low traffic volumes by online devices.

[0108] Abnormal events include business abnormal events, cloud card abnormal events, and operation and maintenance abnormal events.

[0109] In some implementations, each business module can pre-set certain business thresholds to determine whether a business is abnormal.

[0110] For example: Cloud SIM card traffic threshold: If the remaining traffic on a cloud SIM card is lower than the cloud SIM card traffic threshold, the abnormal event is determined to be insufficient available remaining traffic, leading to SIM card replacement and service interruption. Load threshold: If the cloud SIM card load rate is lower than the load threshold, the abnormal event is determined to be low cloud SIM card load rate, resulting in no SIM cards available for replacement. Signal threshold: If the online device signal is lower than the signal threshold, the abnormal event is determined to be a weak signal.

[0111] In some embodiments, business modules can be divided according to scenario requirements. They are not limited to being divided into access modules, business support modules, cloud card management and scheduling modules, and operation and maintenance monitoring modules. They can also be divided into payment modules, marketing modules, etc., so as to make business classification more detailed and clear, set abnormal events as needed, improve automated maintenance, and reduce the scope of impact of system modifications.

[0112] In some embodiments, the maintenance system is specifically used to send a first speed measurement command to the cloud card device if the abnormal event indicates card splitting or card replacement. The first speed measurement command is used to instruct the cloud card device to perform a connectivity detection operation to collect device status information. Specifically, if an abnormal event indicates an abnormality in usage, a second speed test command is sent to the cloud card device. The second speed test command is used to instruct the cloud card device to perform a throughput test operation to collect device status information.

[0113] In some embodiments, the maintenance system is specifically configured to send a second speed measurement command to the cloud card device if the abnormal event indicates an abnormality in use, and if it is determined that the cloud card device is in a standby state.

[0114] In some embodiments, the abnormal event includes at least one event that is not a deterministic indicator, the detection instruction is triggered by the first event that is not a deterministic indicator, and the reception time of each event that is not a deterministic indicator is within the validity period of the detection instruction. The maintenance system is specifically used to traverse events that do not belong to deterministic indicators and determine the equipment status information as the detection result of each event that does not belong to deterministic indicators. Based on the equipment status, determine the second diagnostic result within the validity period of the testing instruction.

[0115] The maintenance system is specifically used to obtain the user level of the cloud card device; based on preset action engine rules, it executes corresponding actions according to the user level and the first diagnostic result; the maintenance system is specifically used to obtain the user level of the cloud card device; based on preset action engine rules, it executes corresponding actions according to the user level and the second diagnostic result.

[0116] In some embodiments, the maintenance system is also used to record device information, user information, abnormal events, diagnostic results of abnormal events, diagnostic methods of abnormal events, trigger time, reception time, and operation and result of abnormal events triggered by the cloud card device.

[0117] Figure 4 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Figure 4 As shown, the electronic device 2 of this embodiment includes: at least one processor 20 ( Figure 4 (Only one is shown in the diagram), memory 21, and computer program 22 stored in said memory 21 and executable on said at least one processor 20, wherein said processor 20 executes said computer program 22 to implement the steps in any of the above method embodiments.

[0118] The electronic device 2 can be a desktop computer, cloud server, or other computing device. The electronic device 2 may include, but is not limited to, a processor 20 and a memory 21. Those skilled in the art will understand that... Figure 4 This is merely an example of electronic device 2 and does not constitute a limitation on electronic device 2. It may include more or fewer components than shown in the figure, or combine certain components, or different components, such as input / output devices, network access devices, etc.

[0119] The processor 20 can be a Central Processing Unit (CPU), or it can be 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.

[0120] In some embodiments, the memory 21 may be an internal storage unit of the electronic device 2, such as a hard disk or memory of the electronic device 2. In other embodiments, the memory 21 may be an external storage device of the electronic device 2, such as a plug-in hard disk, smart media card (SMC), secure digital (SD) card, flash card, etc., equipped on the electronic device 2. Furthermore, the memory 21 may include both internal and external storage units of the electronic device 2. The memory 21 is used to store the operating system, applications, bootloader, data, and other programs, such as the program code of the computer program. The memory 21 can also be used to temporarily store data that has been output or will be output.

[0121] It should be noted that the information interaction and execution process between the above-mentioned devices / units are based on the same concept as the method embodiments of this application. For details on their specific functions and technical effects, please refer to the method embodiments section, and they will not be repeated here.

[0122] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the above-described division of functional units and modules is merely an example. In practical applications, the above functions can be assigned to different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiments can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit. Furthermore, the specific names of the functional units and modules are only for easy differentiation and are not intended to limit the scope of protection of this application. The specific working process of the units and modules in the above system can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0123] This application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, can implement the steps in the above-described method embodiments.

[0124] This application provides a computer program product that, when run on an electronic device, enables the electronic device to implement the steps described in the various method embodiments above.

[0125] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it 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 this application can be implemented by a computer program instructing related hardware. The computer program can be stored in a computer-readable storage medium, and when executed by a processor, it can implement the steps of the various method embodiments described above. The computer program includes computer program code, which can be in the form of source code, object code, executable files, or certain intermediate forms. The computer-readable medium can include at least: any entity or device capable of carrying the computer program code to a photographing device / terminal device, a recording medium, a computer memory, a read-only memory (ROM), a random access memory (RAM), an electrical carrier signal, a telecommunication signal, and a software distribution medium. Examples include USB flash drives, portable hard drives, magnetic disks, or optical disks. In some cases, the computer-readable medium cannot be an electrical carrier signal or a telecommunication signal.

[0126] In the above embodiments, the descriptions of each embodiment have different focuses. For parts that are not described in detail or recorded in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0127] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0128] In the embodiments provided in this application, it should be understood that the disclosed apparatus / network devices and methods can be implemented in other ways. For example, the apparatus / network device embodiments described above are merely illustrative. For instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.

[0129] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0130] The above-described embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application, and should all be included within the protection scope of this application.

Claims

1. An automated assurance method, characterized by, include: Identify abnormal events in the cloud card device; If the abnormal event is a deterministic indicator, then the first diagnostic result corresponding to the abnormal event is determined, and the corresponding action is executed according to the first diagnostic result based on the preset action engine rules. If the abnormal event is not a deterministic indicator, a detection command is sent to the cloud card device, which is used to instruct the cloud card device to collect device status information; Receive the device status information returned by the cloud card device in response to the detection command; Determine the second diagnostic result corresponding to the device status information; Based on the preset action engine rules, the corresponding action is executed according to the second diagnostic result.

2. The method of claim 1, wherein, Sending a detection command to the cloud card device, including: If the abnormal event indicates card splitting or card replacement, a first speed measurement command is sent to the cloud card device. The first speed measurement command is used to instruct the cloud card device to perform a connectivity detection operation to collect the device status information. If the abnormal event characterization is abnormal, a second speed test command is sent to the cloud card device. The second speed test command is used to instruct the cloud card device to perform a throughput test operation to collect the device status information.

3. The method of claim 2, wherein, If the abnormal event indicates an abnormality, a second speed measurement command is sent to the cloud card device, including: If the abnormal event indicates an abnormality, then after determining that the cloud card device is in standby mode, the second speed measurement command is sent to the cloud card device.

4. The method according to any one of claims 1 to 3, characterized in that, The abnormal event includes at least one event that does not belong to a deterministic indicator. The detection instruction is triggered by the first event that does not belong to a deterministic indicator. The reception time of each of the events that do not belong to a deterministic indicator is within the validity period of the detection instruction. The determination of the second diagnostic result corresponding to the device status information includes: Iterate through each of the events that do not belong to deterministic indicators, and determine the device status information as the detection result of each of the events that do not belong to deterministic indicators; Based on the device status information, the second diagnostic result is determined within the validity period of the detection instruction.

5. The method of claim 4, wherein, The step of executing corresponding actions based on the first diagnostic result according to preset action engine rules includes: Obtain the user level of the cloud card device; Based on the preset action engine rules, execute the corresponding action according to the user level and the first diagnostic result; The step of executing the corresponding action based on the preset action engine rules and the second diagnostic result includes: Obtain the user level of the cloud card device; Based on the preset action engine rules, the corresponding action is executed according to the user level and the second diagnostic result.

6. The method of claim 5, wherein, Also includes: Record the device information and user information of the cloud card device, the abnormal event, the diagnosis result of the abnormal event, the diagnosis method of the abnormal event, the trigger time, the reception time of the abnormal event, and the operation and operation result triggered by the abnormal event.

7. An automated assurance system, characterized by, include: Business systems and maintenance systems; The aforementioned business system is used to determine abnormal events of cloud card devices; The maintenance system is used to determine the first diagnostic result corresponding to the abnormal event if the abnormal event is a deterministic indicator, and to perform the corresponding action based on the first diagnostic result according to the preset action engine rules. It is also used to send a detection command to the cloud card device if the abnormal event is not a deterministic indicator, and the detection command is used to instruct the cloud card device to collect device status information; It is also used to receive the device status information returned by the cloud card device in response to the detection command; It is also used to determine the second diagnostic result corresponding to the device status information; It is also used to perform corresponding actions based on the preset action engine rules and the second diagnostic result.

8. The system of claim 7, wherein, The business system includes a business support module, a cloud card management and scheduling module, and an operation and maintenance monitoring module. The business support module is used to monitor business operations and identify abnormal business events. The cloud card management and scheduling module is used to monitor the lifecycle management and scheduling management of the cloud card, and to identify abnormal cloud card events. The operation and maintenance monitoring module is used to monitor online users and online devices, and to identify abnormal operation and maintenance events; The abnormal events include the business abnormal events, the cloud card abnormal events, and the operation and maintenance abnormal events.

9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the method as described in any one of claims 1 to 6.

10. A computer-readable storage medium storing a computer program, the computer program comprising instructions that, when executed by a computer, cause the computer to perform the method of any one of claims 1 to 9. When the computer program is executed by a processor, it implements the method as described in any one of claims 1 to 6.

Images