Method and apparatus for identifying cause of mobile service usage failure

Abstract

The application provides a mobile service use failure cause identification method and device. The method comprises the following steps: acquiring each service rule corresponding to the name of a mobile service from a preset mobile service rule library according to the name; matching each service rule with at least one basic data of a target user number which fails to use the mobile service, and determining each matching result; and generating a multi-dimensional cause identification list according to each matching result. The mobile service use failure cause identification method provided by the application can improve the accuracy of the identified mobile service use failure cause.

Description

Technical Field

[0001] This application relates to the field of data analysis technology, specifically to a method and apparatus for identifying the causes of mobile service usage failures. Background Technology

[0002] Currently, when a user's terminal fails to use mobile services, it is necessary to collect the reasons for the failure in order to carry out wireless optimization and user experience improvement work for the identified user based on the reasons for the failure.

[0003] In existing technologies, identifying the causes of mobile service failures typically involves collecting signaling reported by the terminal and using the terminal capability fields within the signaling to determine the reasons for the failure. However, this approach only identifies the causes at the mobile terminal level, lacking a comprehensive analysis of mobile service failure scenarios. It fails to identify which other aspects might be causing the failure, resulting in inaccurate identification of the causes and impacting subsequent wireless optimization. Summary of the Invention

[0004] This application provides a method and apparatus for identifying the causes of mobile service usage failures, thereby improving the accuracy of identifying the causes of mobile service usage failures.

[0005] In a first aspect, embodiments of this application provide a method for identifying the cause of mobile service usage failure, including:

[0006] Based on the name of the mobile service, retrieve the service rules corresponding to the name from the preset mobile service rule base;

[0007] Each of the aforementioned business rules is matched with at least one set of basic data of the target user number that failed to use the mobile service, and the matching results are determined.

[0008] Based on the matching results, a multidimensional cause identification list is generated;

[0009] The basic data includes signaling data, contract data, and configuration data;

[0010] Each of the aforementioned business rules includes terminal capability rules for identifying terminal capabilities, terminal configuration rules for identifying terminal configurations, and network data configuration rules for identifying network data configurations.

[0011] In one embodiment, each of the business rules is matched with at least one set of basic data of the target user number whose use of the mobile service has failed, and the matching results are determined, including:

[0012] The terminal capabilities set in the terminal capability rules are matched with the first signaling field representing the terminal capabilities in the signaling data to determine the first matching result, and the IMEI identifier set in the terminal capability rules is matched with the IMEI in the signaling data to determine the second matching result.

[0013] In one embodiment, it also includes:

[0014] The terminal configuration rule is matched with the second signaling field representing the terminal configuration in the signaling data to obtain a third matching result.

[0015] In one embodiment, it also includes:

[0016] The network data configuration rules are matched with the contracted data to determine the fourth matching result, and the network data configuration rules are matched with the configuration data to determine the fifth matching result.

[0017] In one embodiment, a multidimensional cause identification list is generated based on each of the matching results, including:

[0018] For each of the matching results, a corresponding cause identification table is generated;

[0019] The various cause identification tables are combined to generate the multidimensional cause identification list.

[0020] In one embodiment, the target user number is any one of the user numbers that failed to use the mobile service.

[0021] In one embodiment, it also includes:

[0022] Generate a multidimensional user identification list based on the multidimensional reason identification list of each user number;

[0023] The multidimensional user identification list records the matching results corresponding to any of the user numbers.

[0024] Secondly, embodiments of this application provide a device for identifying the cause of mobile service failure, comprising:

[0025] The rule acquisition module is used to acquire the service rules corresponding to the name from a preset mobile service rule library based on the name of the mobile service.

[0026] The rule matching module is used to match each of the business rules with at least one basic data of the target user number that failed to use the mobile service, and determine each matching result;

[0027] The cause identification module is used to generate a multidimensional cause identification list based on the matching results.

[0028] The basic data includes signaling data, contract data, and configuration data;

[0029] Each of the aforementioned business rules includes terminal capability rules for identifying terminal capabilities, terminal configuration rules for identifying terminal configurations, and network data configuration rules for identifying network data configurations.

[0030] Thirdly, embodiments of this application provide an electronic device, including a processor and a memory storing a computer program, wherein the processor executes the program to implement the steps of the method for identifying the cause of mobile service usage failure described in the first aspect.

[0031] Fourthly, embodiments of this application provide a computer program product, including a computer program that, when executed by a processor, implements the steps of the method for identifying the cause of mobile service usage failure as described in the first aspect.

[0032] The method and apparatus for identifying reasons for mobile service usage failure provided in this application match the basic data of the user number through multiple dimensions of business rules, so as to identify the reasons for the failure of the terminal corresponding to the user number to use mobile services from multiple dimensions of business rules, thereby enabling a more comprehensive analysis of the mobile service usage failure situation and improving the accuracy of the identified reasons for mobile service usage failure. Attached Figure Description

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

[0034] Figure 1 This is one of the flowcharts illustrating the method for identifying the cause of mobile service usage failure provided in an embodiment of the present invention;

[0035] Figure 2 This is a second flowchart illustrating the method for identifying the cause of mobile service usage failure provided in this embodiment of the invention.

[0036] Figure 3 This is a schematic diagram of the structure of the mobile service usage failure identification device provided by the present invention;

[0037] Figure 4 This is a schematic diagram of the structure of the electronic device provided by the present invention. Detailed Implementation

[0038] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions of this application will be clearly and completely described below with reference to the accompanying drawings of the embodiments. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0039] The following will provide a detailed description and explanation of the method for identifying the cause of mobile service usage failure provided in this application through several specific embodiments.

[0040] like Figure 1 As shown, in one embodiment, a method for identifying the cause of mobile service failure is provided. This embodiment mainly illustrates the application of this method to computer equipment or servers.

[0041] Reference Figure 1 The method for identifying the cause of mobile service failure provided in this embodiment includes:

[0042] Step 101: Based on the name of the mobile service, retrieve the service rules corresponding to the name from the preset mobile service rule base;

[0043] Step 102: Match each of the aforementioned business rules with at least one set of basic data of the target user number that failed to use the mobile service, and determine each matching result;

[0044] Step 103: Generate a multidimensional cause identification list based on the matching results.

[0045] The basic data includes signaling data, contract data, and configuration data;

[0046] Each of the aforementioned business rules includes terminal capability rules for identifying terminal capabilities, terminal configuration rules for identifying terminal configurations, and network data configuration rules for identifying network data configurations.

[0047] By matching the basic data of user numbers with business rules from multiple dimensions, the reasons for the failure of mobile services to be used by the corresponding terminal of the user number can be identified from multiple dimensions of business rules. This enables a more comprehensive analysis of mobile service failures and improves the accuracy of identifying the reasons for mobile service failures.

[0048] In one embodiment, the name of the mobile service is its official name, used to identify the mobile service. The name of the mobile service is unique.

[0049] In one embodiment, the service rules include terminal capability rules, terminal configuration rules, and network data configuration rules.

[0050] The terminal capability rules include:

[0051] (1) Mobile service terminal hardware support rules, which are the terminal hardware requirements of the mobile service and the terminal hardware identifiers that support the service, such as IMEI identifier, terminal brand, terminal model, etc.

[0052] (2) Mobile service terminal software support rules: The mobile service has requirements for terminal software, including: operating system type, software version, terminal brand and other identifiers.

[0053] Terminal configuration rules are the terminal settings requirements needed for mobile services, including terminal service on / off, service number configuration, etc., such as 5G service on / off, SMS center number configuration, data service APN name configuration, etc.

[0054] Network data configuration rules include:

[0055] (1) User subscription data rules are the subscription data that the mobile service needs to complete for the user's number, including business system subscription (customer service, BOSS), network data subscription (HLR / HSS / UDM / VOLTE AS), etc., such as VOLTE HD voice service subscription data, 4G Internet access subscription data, SMS MMS subscription data, etc.

[0056] (2) User network configuration data rules are the configuration data that the mobile service needs to complete for the user number on the network access device, including MSISDN number analysis data, IMSI number analysis data, blacklist and whitelist configuration data, number access priority data, etc.

[0057] In one embodiment, in addition to the aforementioned business rules, the preset mobile service rule base may also include other business rules, which may vary depending on the mobile service situation.

[0058] In one embodiment, the target user number is any one of the user numbers that failed to use the mobile service.

[0059] Among them, the user numbers that failed to use the mobile service can be any of the following: user numbers that have not activated the service, user numbers that have activated but have not used the service, or user numbers that failed to use the service. Each user number that failed to use the mobile service is recorded in the list of users who failed to use the mobile service.

[0060] In one embodiment, the user number of a certain mobile service that has failed to be used can be obtained through a signaling acquisition system, or by exporting user numbers that have not activated the service or have no call details for the mobile service from a customer service system, or by obtaining user numbers of complaints related to the mobile service from a complaint channel.

[0061] In one embodiment, after obtaining any user number that has failed to use mobile services as the target number, each service rule is matched sequentially with the basic data corresponding to the target user number to determine the matching results.

[0062] The basic data includes signaling data such as IMEI, S1AP interface messages, BSSAP interface messages, 5GRegistration messages, and VoLTE invite / registration messages; subscription data such as voice service data, 2G / 3G / 4G / 5G internet data service data, VoLTE HD voice data, and intelligent network supplementary service data; and configuration data such as MSISDN number analysis data, IMSI number analysis data, blacklist / whitelist configuration data, and number access priority data.

[0063] For example, such as Figure 2 As shown, the process involves extracting the target user's number from the list of users who have failed to use mobile services. Then, from the signaling database, the first signaling field and IMEI (terminal identification data) of the target user's number are obtained and matched with the terminal capability rules in the preset mobile service rule base to determine the matching results of the signaling field and IMEI with the terminal capability rules. Next, the second signaling field and IMEI of the target user's number are matched with the terminal configuration rules to obtain the matching results of the signaling field and IMEI with the terminal configuration rules. Finally, the subscription data of the target user's number read from the user subscription database and the configuration data of the target user's number read from the network configuration database are matched with the network data configuration rules to obtain the matching results of the subscription data and configuration data with the network data configuration rules.

[0064] After obtaining all the matching results, a multidimensional cause identification list can be formed from all the matching results.

[0065] In one embodiment, the matching process between terminal capability rules and basic data includes:

[0066] The terminal capabilities set in the terminal capability rules are matched with the first signaling field representing the terminal capabilities in the signaling data to determine the first matching result, and the IMEI identifier set in the terminal capability rules is matched with the IMEI in the signaling data to determine the second matching result.

[0067] In one embodiment, after reading the terminal capability rule from a preset service rule base according to the name of the mobile service, and then reading the signaling data of the target user number from the user signaling database according to the terminal capability rule, the terminal capability rule is matched with a first signaling field related to terminal capabilities in the signaling data, such as the UE networkcapability field of the S1AP interface ATTACH message. If the first signaling field matches the terminal capability rule, the first matching result is marked as true; otherwise, it is marked as false.

[0068] At the same time, based on the IMEI in the signaling data, information such as the terminal hardware brand, terminal model, and software version of the IMEI is obtained from the terminal identifier database. This information is then matched with the mobile service terminal hardware support rules and the mobile service terminal software support rules in the terminal capability rules. If both the hardware support rules and the software support rules are met, the second matching result is marked as true; otherwise, it is marked as false.

[0069] If the matching result is marked as true, it means that the basic data is not the reason for the failure of mobile service use; if the matching result is marked as false, it means that the basic data is one of the reasons for the failure of mobile service use.

[0070] After obtaining the first and second matching results, if both the first and second matching results are marked as true, the target user number, the first matching result, and the second matching result are recorded in the "Terminal Capability Identification Matching Table"; otherwise, the target user number, the first matching result, and the second matching result are recorded in the "Terminal Capability Identification Mismatching Table", thereby facilitating the determination of the reason for the failure of mobile service use.

[0071] In one embodiment, the process of matching terminal configuration rules with basic data includes:

[0072] The terminal configuration rule is matched with the second signaling field representing the terminal configuration in the signaling data to obtain a third matching result.

[0073] In one embodiment, after reading the terminal configuration rule from a preset service rule base according to the name of the mobile service, the signaling data related to the terminal configuration of the target user number is read from the user signaling database according to the terminal configuration involved in the terminal configuration rule. Then, the terminal configuration rule is matched with a second signaling field related to the terminal configuration, such as the Voice Domain Preference and UE's Usage Setting field in the S1AP interface ATTACH message, or the Access Point Name field in the NAS message PDNconnectivity request. If the second signaling field matches the terminal configuration rule, the third matching result is marked as true; otherwise, it is marked as false.

[0074] After obtaining the third matching result, if the third matching result is marked as true, the target user number and the third matching result are recorded in the "Terminal Configuration Identification Match Table"; otherwise, the target user number and the third matching result are recorded in the "Terminal Configuration Identification Mismatch Table", so as to facilitate the determination of the reason for the failure of mobile service use.

[0075] In one embodiment, the process of matching network data configuration rules with basic data includes:

[0076] The network data configuration rules are matched with the contracted data to determine the fourth matching result, and the network data configuration rules are matched with the configuration data to determine the fifth matching result.

[0077] In one embodiment, after reading the network data configuration rule from a preset service rule base according to the name of the mobile service, the subscription data of the target user number is read from the user subscription database according to the subscription data involved in the network data configuration rule, and then the network data configuration rule is matched with the subscription data. If the subscription data conforms to the network data configuration rule, the fourth matching result is marked as true; otherwise, it is marked as false.

[0078] The user subscription database can be a network device, such as HLR / HSS / UDM / PCRF / VOLTE AS, or an external database used to store subscription data from the network device.

[0079] Simultaneously, based on the configuration data involved in the network data configuration rules, the configuration data of the target user number is read from the network configuration database and then matched against the network data configuration rules. If the configuration data of the target user number conforms to the network data configuration rules, the fifth matching result is marked as true; otherwise, it is marked as false.

[0080] The network configuration database can be a network device, such as MME / MSC SERVER / CSCF / SBC / VOLTEAS / DRA / PCRF, etc.; or it can be an external database used to store configuration data from network devices.

[0081] In one embodiment, after obtaining each matching result, a record can be directly formed based on each matching result. A record data is formed by the target user number and its corresponding matching results, such as target user number A - first matching result true / false - second matching result true / false - third matching result true / false - fourth matching result true / false - fifth matching result true / false, and the record data is formed into a multi-dimensional cause identification list.

[0082] Considering that different mobile service failure reasons may need to be assigned to different staff members for processing, in order to facilitate staff members in identifying the mobile service failure reasons they need to handle, in one embodiment, after obtaining each matching result, a multi-dimensional reason identification list is generated based on each matching result, including:

[0083] For each of the matching results, a corresponding cause identification table is generated;

[0084] The various cause identification tables are combined to generate the multidimensional cause identification list.

[0085] In one embodiment, after obtaining the first matching result and the second matching result, if both the first matching result and the second matching result are marked as true, the target user number and the first matching result and the second matching result are recorded in the cause identification table - "Terminal Capability Identification Compliance Table"; otherwise, the target user number and the first matching result and the second matching result are recorded in the cause identification table - "Terminal Capability Identification Non-compliance Table", thereby facilitating the determination of the reason for the failure of mobile service use.

[0086] In one embodiment, after obtaining the third matching result, if the third matching result is marked as true, the target user number and the third matching result are recorded in the cause identification table - "Terminal Configuration Identification Match Table"; otherwise, the target user number and the third matching result are recorded in the cause identification table - "Terminal Configuration Identification Non-match Table", thereby facilitating the determination of the reason for the failure of mobile service use.

[0087] In one embodiment, after obtaining the fourth and fifth matching results, if both the fourth and fifth matching results are marked as true, the target user number and the fourth and fifth matching results are recorded in the cause identification table - "Network Data Configuration Identification Compliance Table"; otherwise, the target user number and the fourth and fifth matching results are recorded in the cause identification table - "Network Data Configuration Identification Non-compliance Table", thereby facilitating the determination of the reason for the failure of mobile service use.

[0088] After each cause identification table is formed, the set of cause identification tables composed of all the cause identification tables is used as a multidimensional cause identification list. This allows staff to obtain the cause identification table they need to process from the multidimensional cause identification list, reducing the amount of data that the staff's corresponding terminal needs to obtain.

[0089] In this embodiment, after obtaining the multidimensional cause identification list of the target user number, the method further includes:

[0090] Generate a multidimensional user identification list based on the multidimensional reason identification list of each user number;

[0091] The multidimensional user identification list records the matching results corresponding to any of the user numbers.

[0092] In one embodiment, after obtaining the multidimensional cause identification list for each user number whose mobile service usage failed, the corresponding cause identification tables in each user number's multidimensional cause identification list are integrated. For example, the cause identification tables for each user number are integrated to form a total cause identification table that records any user number and its first and second matching results. Then, the set of total cause identification tables, composed of all the total cause identification tables, is used as a multidimensional user identification list, thereby completing a comprehensive analysis of the reasons for the failure of all user numbers whose mobile service usage failed.

[0093] The following describes the device for identifying the cause of mobile service failure provided by the present invention. The device for identifying the cause of mobile service failure described below can be referred to in correspondence with the method for identifying the cause of mobile service failure described above.

[0094] In one embodiment, such as Figure 3 As shown, a device for identifying the cause of mobile service failure is provided, comprising:

[0095] The rule acquisition module 210 is used to acquire each service rule corresponding to the name from a preset mobile service rule library according to the name of the mobile service;

[0096] The rule matching module 220 is used to match each of the business rules with at least one basic data of the target user number that failed to use the mobile service, and determine each matching result;

[0097] The cause identification module 230 is used to generate a multi-dimensional cause identification list based on the matching results.

[0098] The basic data includes signaling data, contract data, and configuration data;

[0099] Each of the aforementioned business rules includes terminal capability rules for identifying terminal capabilities, terminal configuration rules for identifying terminal configurations, and network data configuration rules for identifying network data configurations.

[0100] In one embodiment, the rule matching module 220 is specifically used for:

[0101] The terminal capabilities set in the terminal capability rules are matched with the first signaling field representing the terminal capabilities in the signaling data to determine the first matching result, and the IMEI identifier set in the terminal capability rules is matched with the IMEI in the signaling data to determine the second matching result.

[0102] In one embodiment, the rule matching module 220 is further configured to:

[0103] The terminal configuration rule is matched with the second signaling field representing the terminal configuration in the signaling data to obtain a third matching result.

[0104] In one embodiment, the rule matching module 220 is further configured to:

[0105] The network data configuration rules are matched with the contracted data to determine the fourth matching result, and the network data configuration rules are matched with the configuration data to determine the fifth matching result.

[0106] In one embodiment, the cause identification module 230 is specifically used for:

[0107] For each of the matching results, a corresponding cause identification table is generated;

[0108] The various cause identification tables are combined to generate the multidimensional cause identification list.

[0109] In one embodiment, the target user number is any one of the user numbers that failed to use the mobile service.

[0110] In one embodiment, the cause identification module 230 is further configured to:

[0111] Generate a multidimensional user identification list based on the multidimensional reason identification list of each user number;

[0112] The multidimensional user identification list records the matching results corresponding to any of the user numbers.

[0113] Figure 4 An example is a schematic diagram of the physical structure of an electronic device, such as... Figure 4 As shown, the electronic device may include: a processor 810, a communication interface 820, a memory 830, and a communication bus 840, wherein the processor 810, the communication interface 820, and the memory 830 communicate with each other via the communication bus 840. The processor 810 may call a computer program in the memory 830 to execute steps of a method for identifying the cause of mobile service usage failure, such as including:

[0114] Based on the name of the mobile service, retrieve the service rules corresponding to the name from the preset mobile service rule base;

[0115] Each of the aforementioned business rules is matched with at least one set of basic data of the target user number that failed to use the mobile service, and the matching results are determined.

[0116] Based on the matching results, a multidimensional cause identification list is generated;

[0117] The basic data includes signaling data, contract data, and configuration data;

[0118] Each of the aforementioned business rules includes terminal capability rules for identifying terminal capabilities, terminal configuration rules for identifying terminal configurations, and network data configuration rules for identifying network data configurations.

[0119] Furthermore, the logical instructions in the aforementioned memory 830 can be implemented as software functional units and, when sold or used as independent products, can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0120] On the other hand, this application also provides a computer program product, which includes a computer program that can be stored on a non-transitory computer-readable storage medium. When the computer program is executed by a processor, the computer can perform the steps of the mobile service usage failure identification method provided in the above embodiments, such as including:

[0121] Based on the name of the mobile service, retrieve the service rules corresponding to the name from the preset mobile service rule base;

[0122] Each of the aforementioned business rules is matched with at least one set of basic data of the target user number that failed to use the mobile service, and the matching results are determined.

[0123] Based on the matching results, a multidimensional cause identification list is generated;

[0124] The basic data includes signaling data, contract data, and configuration data;

[0125] Each of the aforementioned business rules includes terminal capability rules for identifying terminal capabilities, terminal configuration rules for identifying terminal configurations, and network data configuration rules for identifying network data configurations.

[0126] On the other hand, embodiments of this application also provide a processor-readable storage medium storing a computer program for causing a processor to perform the steps of the methods provided in the above embodiments, such as including:

[0127] Based on the name of the mobile service, retrieve the service rules corresponding to the name from the preset mobile service rule base;

[0128] Each of the aforementioned business rules is matched with at least one set of basic data of the target user number that failed to use the mobile service, and the matching results are determined.

[0129] Based on the matching results, a multidimensional cause identification list is generated;

[0130] The basic data includes signaling data, contract data, and configuration data;

[0131] Each of the aforementioned business rules includes terminal capability rules for identifying terminal capabilities, terminal configuration rules for identifying terminal configurations, and network data configuration rules for identifying network data configurations.

[0132] The processor-readable storage medium can be any available medium or data storage device that the processor can access, including but not limited to magnetic memory (e.g., floppy disk, hard disk, magnetic tape, magneto-optical disk (MO)), optical memory (e.g., CD, DVD, BD, HVD), and semiconductor memory (e.g., ROM, EPROM, EEPROM, non-volatile memory (NAND FLASH), solid-state drive (SSD)).

[0133] The device embodiments described above are merely illustrative. 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 modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without any creative effort.

[0134] Through the above description of the embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus necessary general-purpose hardware platforms, and of course, it can also be implemented by hardware. Based on this understanding, the above technical solutions, in essence or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in the various embodiments or some parts of the embodiments.

[0135] Finally, it should be noted that the above 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.

Claims

1. A method for identifying the cause of mobile service failure, characterized in that, include: Based on the name of the mobile service, retrieve the service rules corresponding to the name from the preset mobile service rule base; Each of the aforementioned business rules is matched with at least one set of basic data of the target user number whose mobile service failed to be used, and the matching results are determined. The matching includes: matching terminal capability rules with terminal capability fields and IMEI in signaling data to identify the terminal hardware / software supported capabilities; matching terminal configuration rules with terminal configuration fields in signaling data to identify the terminal service on / off or parameter configuration; and matching network data configuration rules with subscription data and configuration data to identify network-side data configuration problems. Based on the matching results, a multidimensional cause identification list is generated; The basic data includes signaling data, contract data, and configuration data; Each of the aforementioned business rules includes terminal capability rules for identifying terminal capabilities, terminal configuration rules for identifying terminal configurations, and network data configuration rules for identifying network data configurations.

2. The method for identifying the cause of mobile service failure according to claim 1, characterized in that, Each of the aforementioned business rules is matched with at least one set of basic data for the target user number whose use of the mobile service has failed, and the matching results are determined, including: The terminal capabilities set in the terminal capability rules are matched with the first signaling field representing the terminal capabilities in the signaling data to determine the first matching result, and the IMEI identifier set in the terminal capability rules is matched with the IMEI in the signaling data to determine the second matching result.

3. The method for identifying the cause of mobile service failure according to claim 2, characterized in that, Also includes: The terminal configuration rule is matched with the second signaling field representing the terminal configuration in the signaling data to obtain a third matching result.

4. The method for identifying the cause of mobile service usage failure according to claim 2 or 3, characterized in that, Also includes: The network data configuration rules are matched with the contracted data to determine the fourth matching result, and the network data configuration rules are matched with the configuration data to determine the fifth matching result.

5. The method for identifying the cause of mobile service usage failure according to claim 1, characterized in that, Based on the matching results, a multidimensional cause identification list is generated, including: For each of the matching results, a corresponding cause identification table is generated; The various cause identification tables are combined to generate the multidimensional cause identification list.

6. The method for identifying the cause of mobile service failure according to claim 1, characterized in that, The target user number is any one of the user numbers that failed to use the mobile service.

7. The method for identifying the cause of mobile service failure according to claim 6, characterized in that, Also includes: Generate a multidimensional user identification list based on the multidimensional reason identification list of each user number; The multidimensional user identification list records the matching results corresponding to any of the user numbers.

8. A device for identifying the cause of mobile service failure, comprising: The rule acquisition module is used to acquire the service rules corresponding to the name from a preset mobile service rule library based on the name of the mobile service. The rule matching module is used to match each of the aforementioned business rules with at least one set of basic data of the target user number whose mobile service failed to be used, and to determine the matching results. The matching includes: matching terminal capability rules with terminal capability fields and IMEI in signaling data to identify the terminal's hardware / software supported capabilities; matching terminal configuration rules with terminal configuration fields in signaling data to identify the terminal's service on / off or parameter configuration; and matching network data configuration rules with subscription data and configuration data to identify network-side data configuration problems. The cause identification module is used to generate a multidimensional cause identification list based on the matching results. The basic data includes signaling data, contract data, and configuration data; Each of the aforementioned business rules includes terminal capability rules for identifying terminal capabilities, terminal configuration rules for identifying terminal configurations, and network data configuration rules for identifying network data configurations.

9. An electronic device comprising a processor and a memory storing a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method for identifying the cause of mobile service usage failure as described in any one of claims 1 to 7.

10. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by the processor, it implements the steps of the method for identifying the cause of mobile service usage failure as described in any one of claims 1 to 7.

Images