A method, device and storage medium for locating VoLTE complaint problems
By establishing a call detail record (CDR) rule base and multi-interface CDR synthesis, and combining abnormal scenario rule entries, abnormal signaling in the VoLTE service interaction process is automatically analyzed, which solves the difficulty of accurately locating VoLTE complaint issues, improves location efficiency and accuracy, and achieves automation and reusability.
Patent Information
- Application Number
- CN202010635668.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2020-07-03
- Publication Date
- 2024-11-22
- Estimated Expiration
- 2040-07-03
AI Technical Summary
Existing methods for locating VoLTE complaints are difficult to pinpoint accurately, manual analysis is time-consuming and labor-intensive, and poor communication between multiple professionals leads to long processing times, making automation and reusability impossible.
Establish a call detail record (CDR) rule base, and automatically analyze abnormal signaling during VoLTE service interaction through multi-interface CDR synthesis and abnormal scenario rule entries to accurately locate VoLTE service complaint issues.
It improved the accuracy and efficiency of locating VoLTE service complaints, reduced the time and resource consumption of manual analysis, and enabled information sharing and automated processing among multiple disciplines.
Smart Images

Figure CN113891372B_ABST
Abstract
Description
[Technical field]
[0001] The present application relates to the field of communication technology, and in particular to a method, device and storage medium for locating VoLTE complaint issues. [Background technology]
[0002] VoLTE (Voice over LTE) technology is to separate voice services from traditional 2G / 3G networks and implement them on the 4G LTE (Long Term Evolution) network like data services. By carrying data services and voice services on the same network, VoLTE technology not only enables data services and voice services to be carried out simultaneously, but also provides users with higher-quality voice and video call effects, improving user experience. With the promotion of VoLTE technology, the number of users continues to rise, and at the same time, the number of complaints has also increased significantly.
[0003] At present, the diagnosis of VoLTE complaint problems is mainly based on the XDR (X Data Recording) of a single interface and the signaling backtracking of key processes, with manual analysis as the main method. On the one hand, in the actual business interaction process, a business process involves multiple interfaces, and the abnormal signaling / error code changes during the transmission of the signaling process or due to different network element types, equipment manufacturers, etc., and the problem location judgment through the XDR call list of a single interface may not be able to find the initial source and cause of the abnormal signaling, resulting in poor accuracy in problem demarcation and location, and cannot provide strong support for existing production; on the other hand, the VoLTE network involves multiple fields, and there are bottlenecks such as information asymmetry and untimely communication between various fields. Although the current manual analysis can provide a relatively strict guarantee for the accuracy of problem investigation and handling, the focus of each profession is different, and multiple professions cannot form a joint diagnosis, and the problem handling time becomes longer, which directly affects the user's service experience. In addition, the personal experience of the manual analysis method cannot be solidified and shared, and it is not reusable and automatic. Similar problems must also be repeatedly investigated and handled, which is time-consuming and labor-intensive. [Summary of the invention]
[0004] The embodiments of the present application provide a method, device and storage medium for locating VoLTE complaint problems, so as to accurately locate abnormal signaling during VoLTE service interaction and automatically analyze the causes of VoLTE service complaint problems.
[0005] In the first aspect, an embodiment of the present application provides a method for locating a VoLTE complaint problem, including: establishing a call bill rule base, the call bill rule base containing multi-interface call bills generated based on single-interface call bills of VoLTE services, the multi-interface call bills containing signaling interaction data of VoLTE services; in response to received service complaint information, retrieving the multi-interface call bill corresponding to the service complaint information from the call bill rule base; and locating the cause of the service anomaly corresponding to the service complaint information based on the signaling interaction data in the retrieved multi-interface call bills.
[0006] In one possible implementation, before retrieving the multi-interface call record corresponding to the service complaint information from the call record rule library, the method also includes: determining whether the service complaint information is generated due to at least one of user data abnormality, wireless environment abnormality, and hardware equipment abnormality; if the judgment results are all no, retrieving the multi-interface call record corresponding to the service complaint information from the call record rule library.
[0007] In one possible implementation method, the step of generating a multi-interface call bill based on a single-interface call bill of a VoLTE service includes: decoding the code stream of each interface involved in the VoLTE service to obtain a single-interface call bill corresponding to each interface; and merging the call bill data contained in the single-interface call bill corresponding to each interface into a multi-interface call bill for the VoLTE service.
[0008] In one possible implementation, in response to the received service complaint information, a multi-interface call bill corresponding to the service complaint information is retrieved from the call bill rule library, including: obtaining the complaint number and complaint time point of the service complaint information based on the received service complaint information; and retrieving the multi-interface call bill corresponding to the service complaint information from the call bill rule library based on the complaint number and complaint time point.
[0009] In one possible implementation, the call bill rule library also includes: abnormal scenario rule entries; locating the cause of the service abnormality corresponding to the service complaint information based on the signaling interaction data in the retrieved multi-interface call bill, including: extracting the network element information and first-tear condition information in the multi-interface call bill signaling interaction data; calling the abnormal scenario rule entries in the call bill rule library; retrieving the abnormal scenario rules corresponding to the network element information and the first-tear condition information from the abnormal scenario rule entries; and locating the cause of the service abnormality corresponding to the service complaint information based on the abnormal scenario rules.
[0010] In the second aspect, an embodiment of the present application provides a device for locating VoLTE complaint problems, including: a storage module, used to establish a call bill rule base, the call bill rule base contains multi-interface call bills generated based on single-interface call bills of VoLTE services, and the multi-interface call bills contain signaling interaction data of VoLTE services; a processing module, used to respond to received service complaint information, retrieve the multi-interface call bill corresponding to the service complaint information from the call bill rule base; and locate the cause of the service anomaly corresponding to the service complaint information based on the signaling interaction data in the retrieved multi-interface call bill.
[0011] In one possible implementation method, the processing module is also used to: before retrieving the multi-interface call record corresponding to the service complaint information from the call record rule library, determine whether the service complaint information is caused by at least one of user data abnormality, wireless environment abnormality, and hardware equipment abnormality; if the judgment results are all no, then retrieve the multi-interface call record corresponding to the service complaint information from the call record rule library.
[0012] In one possible implementation method, the processing module is specifically used to: decode the code stream of each interface involved in the VoLTE service to obtain the single-interface call bill corresponding to each interface; and merge the call bill data contained in the single-interface call bill corresponding to each interface into a multi-interface call bill for the VoLTE service.
[0013] In a third aspect, an embodiment of the present application provides an electronic device, comprising: at least one processor; and at least one memory communicatively connected to the processor, wherein: the memory stores program instructions executable by the processor, and the processor calls the program instructions to execute the method described above.
[0014] In a fourth aspect, an embodiment of the present application provides a non-transitory computer-readable storage medium, wherein the non-transitory computer-readable storage medium stores computer instructions, and the computer instructions enable the computer to execute the method as described above.
[0015] In the above technical scheme, a call bill rule base is established, and the call bill rule base contains multi-interface call bills generated according to the single-interface call bills of the VoLTE service, and the multi-interface call bills contain signaling interaction data of the VoLTE service; in response to the received service complaint information, the multi-interface call bills corresponding to the service complaint information are retrieved from the call bill rule base; the cause of the service anomaly corresponding to the service complaint information is located according to the signaling interaction data in the retrieved multi-interface call bills, thereby achieving accurate positioning of abnormal signaling in the VoLTE service interaction process and automatically finding the cause of the VoLTE service complaint problem.
Brief Description of the Drawings
[0016] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.
[0017] Figure 1 A schematic diagram of an embodiment of a SIP response code in a method for locating a VoLTE complaint problem in this application;
[0018] Figure 2 A schematic diagram of an embodiment of a key field of a SIP response code in a method for locating a VoLTE complaint problem in this application;
[0019] Figure 3 A schematic diagram of an embodiment of signaling transmission between various interfaces in a service process in a method for locating a VoLTE complaint problem of this application;
[0020] Figure 4 A flowchart of an embodiment of a method for locating a VoLTE complaint problem in this application;
[0021] Figure 5 This is a schematic diagram of an embodiment of using Flink to synthesize multi-interface call records in the method for locating VoLTE complaint issues in this application;
[0022] Figure 6 A flowchart of another embodiment of the method for locating VoLTE complaint issues of the present application;
[0023] Figure 7 This is a flowchart of another embodiment of using Flink to synthesize multi-interface call records in the method for locating VoLTE complaint issues in this application;
[0024] Figure 8 A schematic diagram of an embodiment of the analysis process of four types of VoLTE problem complaints in the method for locating VoLTE complaint problems of this application;
[0025] Fig. 9 A schematic diagram of an embodiment of an abnormal scenario rule entry in the method for locating a VoLTE complaint problem in this application;
[0026] Fig.10 A structural diagram of an embodiment of a positioning device for VoLTE complaint issues in this application;
[0027] Fig.11 A structural diagram of another embodiment of a positioning device for VoLTE complaint issues in this application;
[0028] Fig.12This is a schematic diagram of the structure of an embodiment of the electronic device of the present application. [Specific implementation method]
[0029] In order to better understand the technical solution of the present application, the embodiments of the present application are described in detail below with reference to the accompanying drawings.
[0030] It should be clear that the described embodiments are only part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in the field without creative work are within the scope of protection of the present application.
[0031] The terms used in the embodiments of the present application are only for the purpose of describing specific embodiments, and are not intended to limit the present application. The singular forms "a", "said" and "the" used in the embodiments of the present application and the appended claims are also intended to include plural forms, unless the context clearly indicates other meanings.
[0032] Signaling data record (X Data Recording, XDR), that is, the call record in the embodiment of the present application, is a basic process record generated based on the processing of the full amount of signaling data. In the network interaction process, one signaling interaction forms a call record, taking the user signaling interaction as the unit. A corresponding response code will be generated when the network signaling interaction is completed. Among them, the response code generated by the network interaction signaling that is not completed normally is expressed as an error code, and the error code information recorded in the call record is the basic data for abnormal business process analysis. In this application, the response code in the long-term evolution voice bearer network (Voice over LTE, VoLTE) is the session initiation protocol response code (Session Initiation Protocol, SIP).
[0033] Figure 1 This is a schematic diagram of an embodiment of the SIP response code in the method for locating the VoLTE complaint problem of this application. Figure 1 As shown in the figure, there are 6 different types of SIP response codes, each of which contains multiple specific values. Take the 1XX type as an example. This type of response code is an information response, indicating that the message has been received and is being processed; the 4XX type of response code is an error code, indicating that the request message contains a syntax error or the SIP server cannot complete the processing of the request message.
[0034] Figure 2 This is a schematic diagram of an embodiment of the key fields of the SIP response code in the method for locating the VoLTE complaint problem of this application. Figure 2As shown, the information carried by the SIP error code includes: status code (Status-Code), reason (Reason), and warning (Warning). The above information carried by the error code can indicate the preliminary cause of the fault.
[0035] Figure 3 This is a schematic diagram of an embodiment of signaling transmission between various interfaces in a business process in the method for locating VoLTE complaint issues in this application.
[0036] It should be noted that, in the signaling interaction process, the network element that first generates an error code is called the first-disassembly network element, and the interface that first generates an error code is called the first-disassembly interface.
[0037] like Figure 3 As shown in FIG. 1 , the first network element in the signaling interaction process is the CSCF2 network element, the first interface is the Mw interface, and the status code generated at the Mw interface is 503, but when the status code is transmitted to the ISC interface, it becomes 500. Figure 3 For example, the embodiment of the present invention associates the MW interface, ISC interface, and S1-U interface to synthesize a multi-interface call sheet, and performs abnormal signaling tracing based on the multi-interface call sheet, thereby avoiding Figure 3 Errors that may occur when analyzing call records of a single interface.
[0038] Figure 4 This is a flowchart of an embodiment of a method for locating a VoLTE complaint problem in this application, such as Figure 4 As shown, the method for locating the VoLTE complaint problem in the embodiment of the present invention may include:
[0039] Step 401: Establish a call record rule base.
[0040] The call record rule base of this embodiment includes multi-interface call records generated according to single-interface call records of VoLTE services.
[0041] This embodiment synthesizes a multi-interface call list by associating the key interfaces of a business process. Specifically, the call business process is associated with four key interfaces, Mw, ISC, Mg, and S1-U, and the registration business process is associated with five key interfaces, Mw, ISC, S1-U, Sh, and Cx. The synthesized multi-interface call list can more accurately find the first-disconnected interface and the first-disconnected network element.
[0042] The call bill rule library of this embodiment also includes abnormal scenario rule entries.
[0043] The abnormal scenario rule entries can be deployed in advance and can be called at any time when analyzing abnormal signaling in multi-interface call records.
[0044] In the specific implementation, the maintenance personnel can sort out the abnormal scenario diagnosis rules based on the complaint handling experience and on-site diagnosis, and generate abnormal scenario rule entries. Subsequently, the abnormal scenario rule entries are associated with the multi-interface call records, so as to locate the corresponding abnormal scenario rules according to the first disconnection condition information in the multi-interface call records.
[0045] The embodiment of the present invention can avoid repeated investigation and handling of historical problems by deploying abnormal scenario rule items, thereby solidifying experience. The abnormal scenario rule items can be stored together with multi-interface call records in the call record rule library, or can be stored separately to form an abnormal scenario rule library.
[0046] Furthermore, exception scenario rule entries can be added and modified at any time.
[0047] Step 402: In response to the received service complaint information, retrieve a multi-interface call record corresponding to the service complaint information from a call record rule library.
[0048] Specifically, this embodiment takes the call service as an example.
[0049] When complaint information about a call service is received, the complaint number and abnormal time are obtained from the complaint information, and the abnormal time in the complaint information is used as the complaint time point. Based on the obtained complaint number and complaint time point, the multi-interface call sheet of the call service in the call sheet rule base is retrieved for the multi-interface call sheet of the complaint number at the complaint time point. The multi-interface call sheets in the call sheet rule base may be stored according to different service classifications or may not be classified, which is not limited in this embodiment.
[0050] Step 403: locate the cause of the service anomaly corresponding to the service complaint information based on the signaling interaction data in the retrieved multi-interface call log.
[0051] In this embodiment, after retrieving the multi-interface call sheet corresponding to the above-mentioned call service complaint information, the network element information and the first disconnection condition information are extracted from the signaling interaction data of the multi-interface call sheet, and the target network element, the first disconnection network element, the first disconnection interface, the first disconnection status code, and the warning value of the call service are found. Then, the abnormal scenario rule entry in the call sheet rule library is called, and the abnormal scenario rule corresponding to the above-mentioned network element information and the first disconnection condition information is retrieved from the abnormal scenario rule entry to locate the cause of the service abnormality corresponding to the above-mentioned call service complaint information.
[0052] In the embodiment of the present invention, the process of generating a multi-interface call record according to a single-interface call record of the VoLTE service in step 401 can be completed by using the open source stream processing technology Flink.
[0053] Figure 5 This is a schematic diagram of an embodiment of using Flink to synthesize multi-interface call records in the method for locating VoLTE complaint issues in this application.
[0054] like Figure 5 As shown in the figure, single-interface bill 1, single-interface bill 2, and single-interface bill 3 are multiple single-interface bills involved in a business process. When bill synthesis is performed, each single-interface bill is passed to Flink, which reads the data of each single-interface bill, synthesizes the multi-interface bill, and stores it in the bill rule library for invocation.
[0055] Figure 6 This is a flowchart of another embodiment of the method for locating VoLTE complaint issues in this application. Figure 6 As shown, this application Figure 4 In step 402 of the illustrated embodiment, before retrieving the multi-interface call record corresponding to the service complaint information from the call record rule library, the following may also be included:
[0056] S601, determining whether the service complaint information is generated due to at least one of abnormal user data, abnormal wireless environment, and abnormal hardware equipment.
[0057] S602, if the judgment results are all negative, retrieve the multi-interface call record corresponding to the service complaint information from the call record rule library; if the judgment results are all positive, execute S603.
[0058] S603, output the diagnosis result.
[0059] Figure 7 This is a flowchart of another embodiment of using Flink to synthesize multi-interface call records in the method for locating VoLTE complaint issues in this application. Figure 7 As shown, in this embodiment, the steps of synthesizing multi-interface call records using Flink are as follows:
[0060] S701: Use a decoder to decode the code streams of the Mw interface, ISC interface, Mg interface, S1-U interface, Sh interface, and Cx interface to obtain binary files of the call record data of each interface.
[0061] S702: Convert the binary file of each interface call record data generated in S701 into a text file.
[0062] S703: Using the open source stream processing platform Kafka, the text files of the call list data of each interface in S702 are passed line by line to Flink.
[0063] S704: Flink reads the received call record data of each interface row by row, concatenates the key fields to synthesize the messages of the same call or registration process on each interface, and synthesizes the multi-interface call record data text file.
[0064] Specifically, for the call process, the call list data of the four key interfaces Mw, ISC, Mg, and S1-U can be synthesized; for the registration process, the call list data of the five key interfaces Mw, ISC, S1-U, Sh, and Cx can be synthesized.
[0065] S705: storing the synthesized multi-interface call record data into a call record rule library.
[0066] Figure 8 This is a schematic diagram of an embodiment of the analysis process of four types of VoLTE problem complaints in the method for locating VoLTE complaint problems in this application.
[0067] In this embodiment, by analyzing the key causes of VoLTE complaint problems, the causes of complaint problems are divided into four categories: user data, wireless environment, core network process, and device hardware.
[0068] like Figure 8 As shown, this embodiment prioritizes the diagnostic sequence of the four categories according to the proportion of actual VoLTE service complaint processing reasons, and arranges them in the order of user data, wireless environment, core network process, and device hardware. When service complaint information is received, the four categories are diagnosed in turn.
[0069] Specifically, when diagnosing user data, you can check whether there is any abnormality in the Universal Subscriber Identity Module (USIM) card; when diagnosing the wireless environment, you can check whether the base station has high interference and high load, and whether the wireless coverage indicators are normal; when diagnosing the core network process, check whether the core network interaction signaling is abnormal; when diagnosing hardware equipment, you can check whether there are any warnings in the wireless equipment and core network equipment.
[0070] In this embodiment, the core network process is diagnosed based on the multi-interface call sheet and the abnormal scenario rule entry. The specific implementation method is to retrieve the multi-interface call sheet corresponding to the service complaint information in the call sheet rule library, extract the network element information and the first disconnection condition information from the signaling interaction data in the retrieved multi-interface call sheet, call the abnormal scenario rule in the abnormal scenario rule entry that matches the above network element information and the first disconnection condition information, and locate the cause of the service abnormality corresponding to the service complaint information.
[0071] Fig. 9 This is a schematic diagram of an embodiment of abnormal scenario rule entries in the method for locating VoLTE complaint issues in the present application.
[0072] When calling the abnormal scenario rule entry to locate the cause of the service abnormality corresponding to the service complaint information, for example, if the first disconnection interface extracted from the multi-interface call list is S1-U, the first disconnection network element is SAEGW, the target network element is ENB, the first disconnection status code is 481, the final disconnection status code is 481, and WARNING is Cancel received on initial, then the abnormal scenario rule in the abnormal scenario rule entry that matches the above first disconnection condition information can be called, that is, Fig. 9 The first rule in the code is to locate the cause of the business complaint.
[0073] Fig.10 1 is a schematic diagram of a structure of an embodiment of a positioning device for a VoLTE complaint problem of the present application. The positioning device 103 for a VoLTE complaint problem in the present embodiment can implement the positioning method for a VoLTE complaint problem provided in the present application. Fig.10 As shown, the above-mentioned VoLTE complaint problem positioning device 103 may include: a processing module 101, a storage module 102;
[0074] Processing module 101 is used to respond to the received service complaint information and retrieve the multi-interface call record corresponding to the service complaint information from the call record rule library; it is also used to locate the cause of the service anomaly corresponding to the service complaint information based on the signaling interaction data in the retrieved multi-interface call record.
[0075] The storage module 102 is used to store a call record rule base.
[0076] The call bill rule library includes: multi-interface call bills synthesized from single-interface call bills of various interfaces involved in different business processes, and exception scenario rule entries.
[0077] In response to the received service complaint information, the processing module 101 obtains the complaint number and abnormal time from the service complaint information, and uses the abnormal time in the service complaint information as the complaint time point. Using the complaint number and complaint time point, the multi-interface call sheet of the complaint number at the complaint time point is retrieved from the call sheet rule library of the storage module 102, and the network element information and the first-opening condition information are extracted. The abnormal scenario rule entry is retrieved from the call sheet rule library of the storage module 102, and the abnormal scenario rule corresponding to the network element information and the first-opening condition information in the abnormal scenario rule entry is matched to locate the cause of the above service complaint problem.
[0078] The storage module 102 may be an Hbase database, which is used to store the above-mentioned call record rule library.
[0079] Fig.11This is a structural diagram of another embodiment of the device for locating VoLTE complaint problems in this application. The device for locating VoLTE complaint problems in this embodiment uses multi-interface call records and abnormal scenario rule entries as two separate modules to implement the method for locating VoLTE complaint problems provided in this embodiment of the application. Fig.11 As shown, the positioning device for the above-mentioned VoLTE complaint problem may include:
[0080] Diagnostic module 111: used to receive VoLTE service complaint information, respond to the received service complaint information, and diagnose the abnormal conditions of four majors, namely user data, wireless environment, core network process, and hardware equipment, in accordance with the pre-set priorities. Different diagnostic rules are called according to different professional problems. It should be noted that the priority setting principle is: the four categories of reasons are prioritized according to the proportion of the actual VoLTE service complaint processing reasons.
[0081] Specifically, when diagnosing abnormal conditions of user interaction signaling in the core network process, the diagnostic module 111 calls the corresponding multi-interface call sheet data in the call sheet storage module 112. In a specific embodiment, the diagnostic module 111 obtains the complaint number and abnormal time based on the service complaint information, and uses the abnormal time in the service complaint information as the complaint time point. Based on the complaint number and complaint information, call the multi-interface call sheet of the complaint service corresponding to the complaint number at the complaint time point in the call sheet storage module 112. The diagnostic module 111 extracts the network element information and first-disconnection condition information in the multi-interface call sheet, calls the abnormal scenario rule entry from the rule storage module 113, and matches the network element information and first-disconnection condition information in the multi-interface call sheet with the corresponding abnormal scenario rules to locate the cause of the service complaint problem.
[0082] The bill storage module 112 is used to store the multi-interface bills synthesized from the single-interface bills corresponding to each business process, wherein the multi-interface bills corresponding to different businesses can be stored according to different categories of business types or stored together. The bill storage module 112 can be an Hbase database.
[0083] Specifically, Flink may be used to synthesize the call record data of a single interface involved in each business process to generate a multi-interface call record, which is stored in the call record storage module 112 .
[0084] The rule storage module 113 is used to store abnormal signaling scenario analysis rules.
[0085] In specific implementation, the maintenance personnel can sort out the abnormal scenario diagnosis rules based on the historical complaint handling experience and on-site diagnosis, generate abnormal scenario rule entries, and store them in the rule storage module 113. Then, the rule storage module 113 is associated with the call list storage module 112 to provide diagnostic results such as delimitation positioning and solution suggestions, so as to avoid repeated investigation and handling of historical problems and form experience solidification. In this embodiment, the abnormal scenario rule entries in the rule storage module 113 can be added and modified at any time.
[0086] Fig.12 This is a schematic diagram of the structure of an embodiment of the electronic device of the present application.
[0087] like Fig.12 As shown, the electronic device may include at least one processor; and at least one memory in communication with the processor, wherein: the memory stores program instructions executable by the processor, and the processor calls the program instructions to execute the VoLTE complaint problem positioning method provided in the embodiment of the present application. The electronic device may be a VoLTE complaint problem positioning device, and the specific form of the electronic device is not limited in this embodiment.
[0088] Fig.12 A block diagram of an exemplary electronic device suitable for implementing the embodiments of the present application is shown. Fig.12 The electronic device shown is merely an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.
[0089] like Fig.12 As shown, the electronic device is in the form of a general-purpose computing device. The components of the electronic device may include, but are not limited to: one or more processors 121, a memory 123, and a communication bus 124 connecting different system components (including the memory 123 and the processor 121).
[0090] The communication bus 124 represents one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, a graphics acceleration port, a processor or a local bus using any of a variety of bus structures. For example, these architectures include but are not limited to Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MAC) bus, Enhanced ISA bus, Video Electronics Standards Association (VESA) local bus and Peripheral Component Interconnection (PCI) bus.
[0091] Electronic devices typically include a variety of computer system readable media. These media can be any available media that can be accessed by the electronic device, including volatile and non-volatile media, removable and non-removable media.
[0092] The memory 123 may include computer system readable media in the form of volatile memory, such as random access memory (RAM) and / or cache memory. The electronic device may further include other removable / non-removable, volatile / non-volatile computer system storage media. Fig.12 Not shown, a disk drive for reading and writing a removable non-volatile disk (e.g., a "floppy disk"), and an optical disk drive for reading and writing a removable non-volatile optical disk (e.g., a compact disc read only memory (CD-ROM), a digital versatile disc read only memory (DVD-ROM), or other optical media) may be provided. In these cases, each drive may be connected to the communication bus 124 via one or more data medium interfaces. The memory 123 may include at least one program product having a set (e.g., at least one) of program modules that are configured to perform the functions of the various embodiments of the present application.
[0093] A program / utility having a set (at least one) of program modules may be stored in memory 123, such program modules including, but not limited to, an operating system, one or more application programs, other program modules, and program data, each of which or some combination may include an implementation of a network environment. The program modules typically perform the functions and / or methods of the embodiments described herein.
[0094] The electronic device may also communicate with one or more external devices (e.g., keyboards, pointing devices, displays, etc.), one or more devices that enable a user to interact with the electronic device, and / or any device that enables the electronic device to communicate with one or more other computing devices (e.g., network cards, modems, etc.). Such communication may be performed via the communication interface 122. Furthermore, the electronic device may also communicate with the network adapter ( Fig.12 The network adapter can communicate with one or more networks (such as a local area network (LAN), a wide area network (WAN), and / or a public network, such as the Internet) through the communication bus 124. It should be understood that although Fig.12 Not shown, other hardware and / or software modules may be used in conjunction with the electronic device, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, disk arrays (Redundant Arrays of Independent Drives; hereinafter referred to as: RAID) systems, tape drives, and data backup storage systems.
[0095] The processor 121 executes various functional applications and data processing by running the programs stored in the memory 123, such as implementing the positioning method for VoLTE complaint problems provided in the embodiment of the present application.
[0096] An embodiment of the present application also provides a non-transitory computer-readable storage medium, which stores computer instructions, and the computer instructions enable the computer to execute the VoLTE complaint problem positioning method provided in the embodiment of the present application.
[0097] The above-mentioned non-temporary computer-readable storage medium can adopt any combination of one or more computer-readable media. The computer-readable medium can be a computer-readable signal medium or a computer-readable storage medium. The computer-readable storage medium can be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples (non-exhaustive list) of computer-readable storage media include: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (Read Only Memory; hereinafter referred to as: ROM), an erasable programmable read-only memory (ErasableProgrammable Read Only Memory; hereinafter referred to as: EPROM) or flash memory, optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In this document, a computer-readable storage medium can be any tangible medium containing or storing a program, which can be used by an instruction execution system, device or device or used in combination with it.
[0098] Computer-readable signal media may include a data signal propagated in baseband or as part of a carrier wave, which carries a computer-readable program code. Such propagated data signals may take a variety of forms, including, but not limited to, electromagnetic signals, optical signals, or any suitable combination of the above. Computer-readable signal media may also be any computer-readable medium other than a computer-readable storage medium, which may send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device.
[0099] Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
[0100] Computer program code for performing the operations of the present application may be written in one or more programming languages or a combination thereof, including object-oriented programming languages such as Java, Smalltalk, C++, and conventional procedural programming languages such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., using an Internet service provider to connect through the Internet).
[0101] In the description of this specification, the description with reference to the terms "one embodiment", "some embodiments", "example", "specific example", or "some examples" etc. means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present application. In this specification, the schematic representations of the above terms do not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described may be combined in any one or more embodiments or examples in a suitable manner. In addition, those skilled in the art may combine and combine the different embodiments or examples described in this specification and the features of the different embodiments or examples, without contradiction.
[0102] Any process or method description in a flowchart or otherwise described herein may be understood to represent a module, fragment or portion of code comprising one or more executable instructions for implementing the steps of a custom logical function or process, and the scope of the preferred embodiments of the present application includes alternative implementations in which functions may not be performed in the order shown or discussed, including performing functions in a substantially simultaneous manner or in the reverse order depending on the functions involved, which should be understood by technicians in the technical field to which the embodiments of the present application belong.
[0103] In the several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation. For example, multiple modules can be combined or integrated into another device, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, modules or units, which can be electrical, mechanical or other forms.
[0104] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of hardware plus software functional units.
[0105] The above-mentioned integrated unit implemented in the form of a software functional unit can be stored in a computer-readable storage medium. The above-mentioned software functional unit is stored in a storage medium, including a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) or a processor (Processor) to perform some steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory; hereinafter referred to as: ROM), random access memory (Random Access Memory; hereinafter referred to as: RAM), disk or optical disk and other media that can store program codes.
[0106] The above description is only a preferred embodiment of the present application and is not intended to limit the present application. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application shall be included in the scope of protection of the present application.
Claims
1. A method for locating VoLTE complaint problems, characterized in that: include: Establishing a call bill rule base, wherein the call bill rule base includes a multi-interface call bill generated according to a single-interface call bill of a VoLTE service, wherein the multi-interface call bill includes signaling interaction data of the VoLTE service; In response to the received service complaint information, retrieving a multi-interface call record corresponding to the service complaint information from the call record rule library; Locate the cause of the service anomaly corresponding to the service complaint information according to the signaling interaction data in the retrieved multi-interface call log; The step of retrieving a multi-interface call record corresponding to the service complaint information from the call record rule library in response to the received service complaint information includes: Obtaining the complaint number and complaint time of the received business complaint information; According to the complaint number and the complaint time point, retrieve the multi-interface call record corresponding to the service complaint information from the call record rule library; The call bill rule library also includes: abnormal scenario rule entries; locating the cause of the service abnormality corresponding to the service complaint information according to the signaling interaction data in the retrieved multi-interface call bill, including: Extracting network element information and first-disconnection condition information from the multi-interface call sheet signaling interaction data, wherein the first-disconnection condition information includes a first-disconnection network element, a first-disconnection interface, and a first-disconnection status code; Calling the abnormal scenario rule entry in the call record rule library; Retrieving, from the abnormal scenario rule entry, an abnormal scenario rule corresponding to the network element information and the first removal condition information; The cause of the business anomaly corresponding to the business complaint information is located according to the abnormal scenario rule.
2. The method according to claim 1, characterized in that Before retrieving the multi-interface call sheet corresponding to the service complaint information from the call sheet rule library, the method further includes: determining whether the service complaint information is generated due to at least one of abnormal user data, abnormal wireless environment, and abnormal hardware equipment; If the judgment results are all negative, the multi-interface call record corresponding to the service complaint information is retrieved from the call record rule library.
3. The method according to claim 1, characterized in that: The steps of generating a multi-interface call record according to a single-interface call record of a VoLTE service include: Decode the code streams of each interface involved in the VoLTE service to obtain a single-interface call record corresponding to each interface; The call record data contained in the single-interface call records corresponding to the respective interfaces are merged into a multi-interface call record for the VoLTE service.
4. A device for locating VoLTE complaint problems, characterized in that: include: A storage module, used to establish a call bill rule base, wherein the call bill rule base contains a multi-interface call bill generated according to a single-interface call bill of a VoLTE service, wherein the multi-interface call bill contains signaling interaction data of the VoLTE service; A processing module, configured to retrieve, in response to the received service complaint information, a multi-interface call sheet corresponding to the service complaint information from the call sheet rule base; and locate the cause of the service anomaly corresponding to the service complaint information according to the signaling interaction data in the retrieved multi-interface call sheet; The processing module is specifically used for: Obtaining the complaint number and complaint time of the received business complaint information; According to the complaint number and the complaint time point, retrieve the multi-interface call record corresponding to the service complaint information from the call record rule library; The call bill rule library further includes: abnormal scenario rule entries; the processing module is specifically used for: Extracting network element information and first-disconnection condition information from the multi-interface call sheet signaling interaction data, wherein the first-disconnection condition information includes a first-disconnection network element, a first-disconnection interface, and a first-disconnection status code; Calling the abnormal scenario rule entry in the call record rule library; Retrieving, from the abnormal scenario rule entry, an abnormal scenario rule corresponding to the network element information and the first removal condition information; The cause of the business anomaly corresponding to the business complaint information is located according to the abnormal scenario rule.
5. The device according to claim 4, characterized in that The processing module is further used for: Before retrieving the multi-interface call record corresponding to the service complaint information from the call record rule library, determine whether the service complaint information is caused by at least one of user data abnormality, wireless environment abnormality, and hardware equipment abnormality; if the judgment results are all no, retrieve the multi-interface call record corresponding to the service complaint information from the call record rule library.
6. The device according to claim 4, characterized in that The processing module is specifically used for: Decode the code streams of each interface involved in the VoLTE service to obtain a single-interface call record corresponding to each interface; The call record data contained in the single-interface call records corresponding to the respective interfaces are merged into a multi-interface call record for the VoLTE service.
7. An electronic device, characterized in that: include: at least one processor; as well as at least one memory in communication with the processor, wherein: The memory stores program instructions executable by the processor, and the processor can execute the method according to any one of claims 1 to 3 by calling the program instructions.
8. A non-transitory computer-readable storage medium, characterized in that: The non-transitory computer-readable storage medium stores computer instructions, and the computer instructions enable the computer to execute the method according to any one of claims 1 to 3.
