A method for counting the number of users with network failures

Abstract

The present invention discloses a method for counting the number of users affected by network failures, which relates to the technical field of broadband operator networks; it includes the following steps: obtaining user and device-related data; obtaining real-time alarm data of all network devices; correlating the alarm data with the user data and performing analysis; recording the analysis results and recording the detailed list of users affected by group faults; providing a group fault management interface and performing UI page rendering. The user data includes user account data, basic user account opening data, and user topology data, and the acquisition methods are as follows: obtaining user account data from the user system; obtaining the basic user account opening data from the service system. The device-related data includes classifier data and optical attenuation data. The present invention can quickly determine the faulty link and the number of affected users, provide a basis for rapid troubleshooting for the network operation and maintenance department, as well as decision-making evaluation of faults within the owner, thereby enabling the customer service and operation and maintenance departments and improving the processing efficiency.

Description

Technical Field

[0001] The present invention relates to the technical field of broadband operator networks, and particularly relates to a method for counting the number of users affected by network failures. Background Art

[0002] With the development of mobile Internet technology, broadband network operation has gradually come into people's view. By deploying a large number of broadband network providing devices in public places such as shopping malls and cinemas, temporary broadband networks can be provided for people.

[0003] With the popularization of broadband and the complexity of lines, it is particularly important to detect and eliminate network failures and count and record the faulty users.

[0004] At present, when a network failure occurs, the network cannot timely and accurately match the user scope affected by the faulty network element. This results in that when a failure occurs, the operator cannot effectively evaluate the number of users affected by the failure, which affects internal decision-making; for users, they cannot clearly know the actual cause of the failure and the repair situation, which affects the user experience. Summary of the Invention

[0005] The purpose of the present invention is to solve the disadvantages existing in the prior art, and to propose a method for counting the number of users affected by network failures.

[0006] In order to achieve the above purpose, the present invention adopts the following technical solutions:

[0007] A method for counting the number of users affected by network failures includes the following steps:

[0008] S1: Obtain user and device related data;

[0009] S2: Obtain real-time alarm data of all network devices;

[0010] S3: Associate the alarm data with the user data and perform analysis;

[0011] S4: Record the analysis result and record the detailed list of users affected by the group failure;

[0012] S5: Provide a group failure management interface and perform UI page rendering.

[0013] Preferably: In S1, the user data includes user account data, basic user account opening data, and user topology data.

[0014] Preferably: The obtaining method of S1 is as follows:

[0015] A1: Obtain user account data from the user system;

[0016] A2: Obtain the basic user account opening data from the service system;

[0017] A3: Obtain user topology data.

[0018] Preferably: In the above S1, the device-related data includes classifier data and optical attenuation data.

[0019] Preferably: The method for obtaining the device-related data in S1 is as follows:

[0020] B1: Obtain primary and secondary classifier data from the line source;

[0021] B2: Collect the optical attenuation data of the four-layer network device.

[0022] Preferably: In the above S3, it specifically includes the following steps:

[0023] C1: Analyze the alarm data and associate the alarm with the user topology;

[0024] C2: Analyze whether the path of the user topology is the only path;

[0025] C3: Analyze the user data affected by the alarm.

[0026] Preferably: In the above S4, it specifically includes the following steps:

[0027] D1: Record the analysis result of the group fault;

[0028] D2: Record the detailed list of users affected by the group fault.

[0029] Preferably: In the above D2, the detailed list of users includes the affected user accounts that match each other, the basic user account opening data, the user topology path data, and the user device data.

[0030] Preferably: In the above S5, the specific method is: encapsulate the interfaces related to the group fault query, topology restoration, etc. of this fault, define the input and output parameters of the interfaces with unified specifications, form a group fault management interface, and the page renders and displays the data returned by the interface.

[0031] The beneficial effects of the present invention are as follows:

[0032] 1. The present invention can quickly judge the faulty link and the number of affected users, provide a basis for rapid troubleshooting for the network operation and maintenance department, and provide a decision-making evaluation of the fault for the owner's internal department. Thereby, it can empower the customer service and operation and maintenance departments and improve the processing efficiency.

[0033] 2. The present invention realizes the standardization and unity of capabilities, supports providing true and effective data for troubleshooting based on entrances such as device IP and user accounts, can improve the fault handling time, reduce the waiting time of users, and provide a guarantee for improving the quality of customer service. Description of the Drawings

[0034] Figure 1 This is a schematic flow diagram of a method for counting the number of users with network failures proposed by the present invention. Detailed implementation manners

[0035] The technical solutions of this patent will be further described in detail below in conjunction with the specific implementation manners.

[0036] In the description of this patent, it should be noted that unless otherwise clearly specified and limited, the terms "installation", "connection", "linkage", "setting" should be understood in a broad sense. For example, it can be fixedly connected and set, or detachably connected and set, or integrally connected and set. For those of ordinary skill in the art, the specific meanings of the above terms in this patent can be understood according to specific circumstances.

[0037] Embodiment 1:

[0038] A method for counting the number of users with network failures includes the following steps:

[0039] S1: Obtain user and device related data;

[0040] S2: Obtain real-time alarm data of all network devices;

[0041] S3: Correlate the alarm data with the user data and perform analysis;

[0042] S4: Record the analysis results and record the detailed list of users affected by the group failure;

[0043] S5: Provide a group failure management interface and perform UI page rendering.

[0044] Embodiment 2:

[0045] A method for counting the number of users with network failures, this embodiment is improved based on Embodiment 1: In S1, the user data includes user account data, basic user account opening data, and user topology data.

[0046] The acquisition method is as follows:

[0047] A1: Obtain user account data from the user system;

[0048] A2: Obtain the basic user account opening data from the service system;

[0049] A3: Obtain user topology data.

[0050] In S1, the device related data includes classifier data and optical attenuation data

[0051] The acquisition method is as follows:

[0052] B1: Obtain the first- and second-level classifier data from the line source;

[0053] B2: Collect the optical attenuation data of the four-layer network device.

[0054] In S3, it specifically includes the following steps:

[0055] C1: Analyze the alarm data and associate the alarm with the user topology;

[0056] C2: Analyze whether the user topology path is the only path;

[0057] C3: Analyze the user data affected by the alarm.

[0058] In S4, it specifically includes the following steps:

[0059] D1: Record the results of the group fault analysis;

[0060] D2: Record the detailed list of users affected by the group fault.

[0061] In D2, the detailed user list includes the affected user accounts, basic user account opening data, user topology path data, and user device data that match each other.

[0062] In S5, the specific method is: encapsulate the interfaces related to this fault such as group fault query and topology restoration, define the standardized interface input and output parameters, form the group fault management interface, and the page renders and displays the data returned by the interface.

[0063] In this embodiment: It can quickly judge the faulty link and the number of affected users, can provide a basis for quick troubleshooting for the network operation and maintenance department, and the internal decision-making evaluation of the fault for the owner. Thereby, it can empower the customer service and operation and maintenance departments, improve the processing efficiency, and achieve the standardization and unity of capabilities. It supports providing true and effective data for the troubleshooting basis through entrances such as device IP and user accounts, can improve the fault handling time, and reduce the waiting time of users, providing guarantee for improving the customer service quality.

[0064] The above is only a preferred specific embodiment of the present invention, but the protection scope of the present invention is not limited thereto. Any person skilled in the art within the technical scope disclosed by the present invention, according to the technical solution and inventive concept of the present invention, makes equivalent substitutions or changes, and all should be covered within the protection scope of the present invention.

Claims

1. A method for counting the number of users affected by network failures, characterized in that, it includes the following steps: S1: Obtain user and device-related data; S2: Obtain real-time alarm data of all network devices; S3: Associate the alarm data with the user data and perform analysis; S4: Record the analysis results and record the detailed list of users affected by the group fault; S5: Provide a group fault management interface and perform UI page rendering; In the above S1, the user data includes user account data, basic user account opening data, and user topology data; The obtaining method of the above S1 is: A1: Obtain user account data from the user system; A2: Obtain the basic user account opening data from the service system; A3: Obtain user topology data; In the above S1, the device-related data includes classifier data and optical attenuation data; The obtaining method of the above S1 device-related data is: B1: Obtain the first- and second-level classifier data from the line source; B2: Collect the optical attenuation data of four-layer network devices; In the above S3, it specifically includes the following steps: C1: Analyze the alarm data and associate the alarm data with the user topology; C2: Analyze whether the user topology path affected is the only path; C3: Analyze the user data affected by the alarm; In the above S4, it specifically includes the following steps: D1: Record the group fault analysis results; D2: Record the detailed list of users affected by the group fault; In the above D2, the detailed user list includes the affected user accounts, basic user account opening data, user topology path data, and user device data that match each other; In the above S5, the specific method is: encapsulate the interfaces related to this fault such as group fault query and topology restoration, define the interface input and output parameters with unified specifications, form a group fault management interface, and the page renders and displays the data returned by the interface.

Images