CN114205217A

CN114205217A - Network fault notification method and device, storage medium and electronic equipment

Info

Publication number: CN114205217A
Application number: CN202111533242.3A
Authority: CN
Inventors: 李宛; 刘刚; 王昌盛; 黎杨惠; 胡宁宁; 孙宝平; 李瑞瑞; 邱文霞; 赵锦涛
Original assignee: China Telecom Corp Ltd
Current assignee: China Telecom Corp Ltd
Priority date: 2021-12-15
Filing date: 2021-12-15
Publication date: 2022-03-18
Anticipated expiration: 2041-12-15
Also published as: CN114205217B

Abstract

The present disclosure provides a network failure notification method and apparatus, a storage medium, and an electronic device; relates to the technical field of communication. The method comprises the steps of receiving fault alarm information, and matching network account information affected by a fault through a network management system according to the fault alarm information; searching customer information influenced by the fault through a customer management system according to the network account information; generating a corresponding H5 link based on the fault type information and the fault equipment information to obtain fault notification information containing an H5 link; and sending the fault notification information to a corresponding client or a client terminal according to the client information affected by the fault. The method and the device solve the problems that the existing passive inquiry mode causes poor customer experience and cannot timely, effectively and actively inform the user of the network fault.

Description

Network fault notification method and device, storage medium and electronic equipment

Technical Field

The present disclosure relates to the field of communications technologies, and in particular, to a network fault notification method, a network fault notification apparatus, a computer-readable medium, and an electronic device.

Background

With the rapid advance of network technology, networks have become popular in daily life, and network operators provide services to users to meet various needs of the users, and it is important to ensure the service experience of the users. However, because of the failure of the operator equipment or an emergency, a network failure occurs sometimes, and it is important to enable the user to know the first-line failure situation in time when the network fails, so as to improve the user experience in the failure period.

At present, when a network fails, a client is always in an unknown passive state about the network failure condition, and generally, the user asks for failure reasons by dialing a customer service telephone, so that the user experience is poor.

For network faults, the existing mode of acquiring fault information by passively dialing a customer service telephone by a user can lead to the sudden increase of the traffic of the customer service telephone in a short time, and the customer service telephone is always unavailable or needs to be connected for a long time, thereby further influencing the customer experience; meanwhile, the problem that the client side cannot timely acquire the first-line fault information exists.

It is to be noted that the information disclosed in the above background section is only for enhancement of understanding of the background of the present disclosure, and thus may include information that does not constitute prior art known to those of ordinary skill in the art.

Disclosure of Invention

An object of the embodiments of the present disclosure is to provide a network failure notification method, a network failure notification apparatus, a computer-readable medium, and an electronic device, so as to solve the problem that the existing passive query method is poor in customer experience and cannot timely, effectively, and actively notify a user of a network failure to a certain extent.

According to a first aspect of the present disclosure, there is provided a network failure notification method, including:

receiving fault alarm information, wherein the fault alarm information at least comprises fault type information and fault equipment information;

matching network account information affected by the fault through a network management system according to the fault type information and the fault equipment information;

searching customer information influenced by the fault through a customer management system according to the network account information;

generating a corresponding H5 link based on the fault type information and the fault equipment information to obtain fault notification information containing an H5 link; the H5 link is provided with a field maintenance uploading control, a user feedback control, a fault description control and a timing control for displaying fault information on an H5 page corresponding to the H5 link;

and sending the fault notification information to a corresponding client or a client terminal according to the client information affected by the fault.

In an exemplary embodiment of the present disclosure, based on the foregoing scheme, the receiving the fault warning information at least includes:

receiving first fault alarm information reported by fault equipment;

receiving second fault alarm information triggered by the customer service system;

and receiving third fault alarm information uploaded by operation and maintenance personnel.

In an exemplary embodiment of the present disclosure, based on the foregoing solution, the receiving the second fault warning information triggered by the customer service system includes:

receiving fault complaint customer information sent by a customer service system;

matching a customer management system to obtain corresponding complaint network account information according to the fault complaint customer information;

and according to the complaint network account information, the matching network management system obtains a corresponding optical line terminal OLT equipment address, a passive optical network PON port number or a base station identifier to obtain second fault type information and fault equipment information, namely second fault warning information.

In an exemplary embodiment of the present disclosure, based on the foregoing scheme, the fault type information includes a broadband network fault and a wireless network fault;

when the fault type information is a broadband network fault, the fault equipment information at least comprises alarm time, a fault reason, an OLT equipment address and a PON port number;

and when the fault type information is a wireless network fault, the fault equipment information at least comprises alarm time, a fault reason and a base station identifier.

In an exemplary embodiment of the present disclosure, based on the foregoing scheme, the matching, by the network management system, the network account information affected by the fault according to the fault type information and the fault device information includes:

when the fault type information is a broadband network fault, inquiring a network management system according to an OLT (optical line terminal) equipment address and a PON (passive optical network) port number to obtain a broadband account to which the corresponding drop-on equipment belongs;

when the fault type information is a wireless network fault, then:

matching user address information of a client management system according to the base station identification;

counting the network utilization rate corresponding to the user address within preset time;

and determining a corresponding network account according to the network utilization rate.

In an exemplary embodiment of the present disclosure, based on the foregoing scheme, the finding, by the customer management system, the customer information affected by the fault according to the network account information includes:

when the fault type information is a broadband network fault, searching customer information of a corresponding user through a customer management system according to the network account information;

and when the fault type information is a wireless network fault, directly obtaining the customer information through the network account information.

In an exemplary embodiment of the present disclosure, based on the foregoing scheme, the generating a corresponding H5 link based on the fault type information and the faulty device information includes:

predicting a fault scene and repairing time according to the fault type information and the fault equipment information;

selecting one template from preset H5 page templates for editing to generate an H5 notification page; so that H5 has a field repair upload control, user feedback control, fault description control for presenting fault information, and timing control on the notification page.

Associating the generated H5 notification page with a two-dimensional code or short link generates an H5 link.

In an exemplary embodiment of the present disclosure, based on the foregoing scheme, the predicting a fault scenario and a repair duration according to the fault type information and the fault device information includes:

acquiring historical fault information; the historical fault information comprises historical fault alarm information, historical fault scenes and historical repair duration;

training a fault classification prediction model by adopting historical fault information; the fault classification prediction model is as follows;

and predicting the fault scene category and the repair duration of the current fault by adopting the trained fault classification prediction model.

In an exemplary embodiment of the present disclosure, based on the foregoing scheme, the method further includes:

determining a fault notification mode according to the alarm time, wherein the fault notification mode comprises an instant notification and a delay notification;

when the instant notification is determined, corresponding fault notification information is sent to the client in real time after the fault warning information is received;

when the notification is determined to be delayed, determining delay time according to the alarm time;

and sending corresponding fault notification information to the client based on the delay time length.

According to a second aspect of the present disclosure, there is provided a network failure notification apparatus including:

the system comprises a receiving module, a judging module and a judging module, wherein the receiving module is used for receiving fault alarm information, and the fault alarm information at least comprises fault type information and fault equipment information;

the matching module is used for matching network account information affected by the fault through a network management system according to the fault type information and the fault equipment information;

the searching module is used for searching customer information influenced by faults through a customer management system according to the network account information;

the generating module is used for generating a corresponding H5 link based on the fault type information and the fault equipment information to obtain fault notification information containing an H5 link; the H5 link is provided with a field maintenance uploading control, a user feedback control, a fault description control and a timing control for displaying fault information on an H5 page corresponding to the H5 link;

and the sending module is used for sending the fault notification information to a corresponding client or a client terminal according to the client information affected by the fault.

According to a third aspect of the present disclosure, there is provided a computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements the method of any one of the above.

According to a fourth aspect of the present disclosure, there is provided an electronic device comprising: a processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to perform the method of any one of the above via execution of the executable instructions.

Exemplary embodiments of the present disclosure may have some or all of the following benefits:

in the network fault notification method provided by the disclosed example embodiment, the network management system may match network account information affected by a fault according to the received fault type information and fault device information; and then according to the network account information, searching customer information affected by the fault through a customer management system, further determining the customer information needing fault notification, and ensuring that each user affected by the fault can know the fault condition in time. Generating a corresponding H5 link based on the fault type information and the fault equipment information to obtain fault notification information containing an H5 link; and the H5 link is provided with a field maintenance uploading control, a user feedback control, a fault description control for displaying fault information and a timing control on a corresponding H5 page. And sending the fault notification information to a corresponding client or a client terminal according to the client information affected by the fault. On one hand, the fault information of the user can be timely and actively informed, and the current situation that the user passively learns the fault is improved. On the other hand, a maintenance worker can upload a field maintenance picture through the H5 link, so that a user can timely and effectively know the fault condition and the specific maintenance progress, and the user experience is improved. In addition, the interaction between the user and a front-line maintenance worker can be carried out through the H5 link, the flexibility of obtaining fault information is increased, and the user experience is further improved.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and together with the description, serve to explain the principles of the disclosure. It is to be understood that the drawings in the following description are merely exemplary of the disclosure, and that other drawings may be derived from those drawings by one of ordinary skill in the art without the exercise of inventive faculty.

Fig. 1 is a schematic diagram illustrating an exemplary system architecture to which a network failure notification method and apparatus according to an embodiment of the present disclosure may be applied;

FIG. 2 schematically illustrates a flow diagram of a network failure notification method according to one embodiment of the present disclosure;

FIG. 3 schematically illustrates a flow diagram for implementing receiving second fault alert information in accordance with one embodiment of the present disclosure;

FIG. 4 schematically illustrates a flow diagram of a network account determination process for a wireless network in one embodiment according to the present disclosure;

FIG. 5 schematically illustrates an H5 link generation process flow diagram according to one embodiment of the disclosure;

FIG. 6 schematically illustrates a fault scenario and repair duration prediction process in accordance with an embodiment of the present disclosure;

FIG. 7 schematically illustrates a flow diagram of a prediction process for a fault classification prediction model in one embodiment according to the present disclosure;

FIG. 8 schematically illustrates a different inter-system network failure notification process in one embodiment according to the present disclosure;

FIG. 9 schematically shows a block diagram of a network failure notification apparatus according to an embodiment of the present disclosure;

FIG. 10 illustrates a schematic structural diagram of a computer system suitable for use in implementing an electronic device of an embodiment of the present disclosure.

Detailed Description

Example embodiments will now be described more fully with reference to the accompanying drawings. Example embodiments may, however, be embodied in many different forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of example embodiments to those skilled in the art. The described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to give a thorough understanding of embodiments of the disclosure. One skilled in the relevant art will recognize, however, that the subject matter of the present disclosure can be practiced without one or more of the specific details, or with other methods, components, devices, steps, and the like. In other instances, well-known technical solutions have not been shown or described in detail to avoid obscuring aspects of the present disclosure.

Furthermore, the drawings are merely schematic illustrations of the present disclosure and are not necessarily drawn to scale. The same reference numerals in the drawings denote the same or similar parts, and thus their repetitive description will be omitted. Some of the block diagrams shown in the figures are functional entities and do not necessarily correspond to physically or logically separate entities. These functional entities may be implemented in the form of software, or in one or more hardware modules or integrated circuits, or in different networks and/or processor devices and/or microcontroller devices.

Fig. 1 is a schematic diagram illustrating a system architecture 100 of an exemplary application environment to which a network failure notification method and apparatus according to an embodiment of the present disclosure may be applied. As shown in fig. 1, the system architecture 100 may include one or more of

alarm terminal devices

101, 102, 103, a fault notification server 104, a network management system server 105, a customer management system server 106, and a user terminal 107. The network 104 is used for communication between the

terminal devices

101, 102, 103 and the fault notification server, between the fault notification server 104 and the network management system server 105, between the fault notification server 104 and the client management system server 106, and between the fault notification server 104 and the user terminal 107 via the network, respectively. The network may include various connection types, such as wired, wireless communication links, or fiber optic cables, to name a few. The alert

terminal devices

101, 102, 103 may be various electronic devices having a display screen, including but not limited to desktop computers, portable computers, smart phones, tablet computers, and the like. But also a malfunctioning device such as an optical line termination, OLT, device or the like. It should be understood that the number of

alarm terminal devices

101, 102, 103, fault notification server 104, network management system server 105, customer management system server 106 and user terminals 107 in fig. 1 is merely illustrative. There may be any number of terminal devices and servers, as desired for implementation. For example, network management system server 105 may be a server cluster comprised of multiple servers, or the like.

The network failure notification method provided by the embodiment of the present disclosure may be executed in the failure notification server 104, and accordingly, the network failure notification apparatus is generally disposed in the failure notification server 104.

Network failures have become an inevitable problem with the popularity of networks and the expansion of network lines. At present, a client is always in an unknown passive state under the condition of network failure, so that the experience of the client is reduced. The main problems are as follows: 1) the client is completely unaware of the fault repairing process and does not know the fault repairing service process of front-line personnel; 2) the client can only passively accept the information without a problem feedback channel; 3) for an impending barrier caused by a third party, the client is not notified in advance. Especially for the district type group trouble that leads to because the third party's reason, for example bad weather, municipal power failure, municipal construction, external force destruction etc. because the user that involves is numerous, need advance or timely carry out the trouble notice to improve user experience.

The technical solution of the embodiment of the present disclosure is explained in detail below:

referring to fig. 2, a network failure notification method according to an example embodiment of the present disclosure may include:

step S210, receiving fault alarm information, wherein the fault alarm information at least comprises fault type information and fault equipment information;

step S220, matching network account information affected by the fault through a network management system according to the fault type information and the fault equipment information;

step S230, searching customer information affected by the fault through a customer management system according to the network account information;

step S240, generating a corresponding H5 link based on the fault type information and the fault equipment information to obtain fault notification information containing an H5 link; the H5 link is provided with a field maintenance uploading control, a user feedback control, a fault description control and a timing control for displaying fault information on an H5 page corresponding to the H5 link;

and step S250, sending the fault notification information to a corresponding client or a client terminal according to the client information affected by the fault.

In the network fault notification method provided in this example embodiment, network account information affected by a fault may be matched by the network management system according to the received fault type information and fault device information; and then according to the network account information, searching customer information affected by the fault through a customer management system, further determining the customer information needing fault notification, and ensuring that each user affected by the fault can know the fault condition in time. Generating a corresponding H5 link based on the fault type information and the fault equipment information to obtain fault notification information containing an H5 link; and the H5 link is provided with a field maintenance uploading control, a user feedback control, a fault description control for displaying fault information and a timing control on a corresponding H5 page. And sending the fault notification information to a corresponding client or a client terminal according to the client information affected by the fault. On one hand, the fault information of the user can be timely and actively informed, and the current situation that the user passively learns the fault is improved. On the other hand, a maintenance worker can upload a field maintenance picture through the H5 link, so that a user can timely and effectively know the fault condition and the specific maintenance progress, and the user experience is improved. In addition, the interaction between the user and a front-line maintenance worker can be carried out through the H5 link, the flexibility of obtaining fault information is increased, and the user experience is further improved.

Next, in another embodiment, the above steps are explained in more detail.

In step S210, fault warning information is received, where the fault warning information at least includes fault type information and fault device information.

In the present exemplary embodiment, the fault warning information may include fault type information and fault device information; the fault type information may include a broadband network fault and a wireless network fault. If the fault type information is a broadband network fault, the fault equipment information may include alarm time, a fault reason, an OLT equipment address, and a PON port number; the system may further include a work order processing time limit, a local network, a local direction, an alarm type, an alarm description, and the like, which is not particularly limited in this example. If the fault type information is a wireless network fault, the fault equipment information at least comprises alarm time, a fault reason and a base station identifier; and the system also can comprise work order processing time limit, local network, office direction, base station name, alarm type, alarm description and the like. This example is not particularly limited thereto.

The source of the fault warning information may be first fault warning information reported by the faulty device, and the first fault warning information may be directly derived from the faulty device, or may be information reported by the faulty device to a transfer station (e.g., a network management system) and then forwarded by the transfer station. The alarm information of the broadband network fault is from an optical line terminal OLT network element arranged in a central control station and a batch of optical network unit ONU network elements matched with each other and arranged in a user place; when the OLT equipment is off-line and the main optical circuit of the PON port is disconnected, two kinds of broadband obstacles with large influence areas are generated. The alarm information of the wireless network fault comes from a base station, an IPRAN (radio access network IP) alarm, a base station dynamic ring, a network topology and the like. The source of the fault warning information can also be second fault warning information triggered by the customer service system, and the second fault warning information can be information judged and input by customer service personnel according to the received fault information, or can be warning information directly formed by the customer service system according to the condition of the customer service call. The source of the fault warning information can also be third fault warning information uploaded by front-line operation and maintenance personnel. The present example does not particularly limit the source of the fault warning information.

For example, when a group fault notification is performed, whether a group fault occurs or not can be determined according to a plurality of user numbers, broadband numbers or mobile phone numbers in the suddenly increased co-office direction where the customer service has heard the fault, and then second fault warning information is generated. Referring to fig. 3, the second fault warning information is generated through the following steps S310 to S340.

In step S310, the customer information of the fault complaint sent by the customer service system is received. In this example embodiment, the customer service system may determine, according to the fault complaint information entered by the customer service staff, user information of the network fault, such as broadband account information and user contact information, and may further include complaint time information. And the user information is used as the fault complaint customer information; the customer service system can also automatically determine the network fault user according to the conversation content between the customer service and the user.

In step S320, according to the fault complaint customer information, the matching customer management system obtains corresponding complaint network account information. In the present exemplary embodiment, the network account information of the fault complaint customer may be matched in the customer management system according to the fault complaint customer information, for example, the contact address or the user account of the customer.

In step S330, according to the complaint network account information, the matching network management system obtains a corresponding optical line terminal OLT device address, passive optical network PON port number, or base station identifier, and obtains second fault type information and fault device information, that is, second fault warning information. In this example embodiment, according to the complaint network account information, an optical line terminal OLT device address, a passive optical network PON port number (for a broadband network), or a base station identifier (for a wireless network) corresponding to the network account may be matched in a network management system (e.g., an end-to-end network management system) to obtain fault device information and fault type information.

In step S220, matching the network account information affected by the fault through the network management system according to the fault type information and the fault device information. In this exemplary embodiment, if the fault type information is a broadband network fault, the network management system is queried to obtain a broadband account to which the corresponding drop-in device belongs according to the address of the OLT device and the port number of the PON. The network management system may be an end-to-end system, and the system queries a broadband account to which a network terminal affected by a faulty device belongs. On the basis, the AAA authentication charging system can be matched again based on the matched broadband account number to determine the active broadband account number of the disabled user so as to eliminate the unused broadband account number users. In this example, the broadband account matched by the network management system may be used as a final fault-affecting broadband account; the determined active broadband account of the disabled user may also be used as a final fault affecting the broadband account, which is not particularly limited in this example.

In the present exemplary embodiment, referring to fig. 4, for the failure type information is a wireless network failure, the network account information affected by the failure is determined through steps S410-S430.

In step S410, the user address information of the customer management system is matched according to the base station identifier. In this example embodiment, a wireless network area where a base station acts may be determined according to base station information such as a base station identifier and a base station name, and user address information of the wireless network acting area may be matched in the customer management system, for example, when a user opens a wireless network, registered user residence information and user work address may be included, and the residence address information and the work address information may include a cell name, floor information, and house number information. And when the residence or the working address of the user falls into the action range of the base station, acquiring the corresponding address information of the user.

In step S420, the network usage rate corresponding to the user address within a preset time is counted. In the present exemplary embodiment, a time period may be set, which may be set according to calendar year data and a user address, for example, may be set to ten days, one month, or several months. The network usage rate of the user address obtained in step S410 within the preset time is counted, where the network usage rate may be a ratio of the network usage time to the preset time, and a unit of the time may be day or hour, which is not particularly limited in this example. The network usage time may be an actual network usage time of the user, or may be a network usage time determined by a preset rule. For example, the network usage time of a user whose network usage time exceeds 2 hours within one day is defined as 1 day, the network usage time of a user whose network usage time is less than 1 hour within one day is defined as 0, and the network usage time of a user whose network usage time is less than 2 hours and greater than 1 hour within one day is defined as 0.5 day. The preset rule is not particularly limited in this example.

In step S430, a corresponding network account is determined according to the network usage rate. In this example embodiment, the network account to which the user address (e.g., a cell) whose network usage rate is greater than the preset threshold belongs may be used as the network account affected by the fault. The network account to which the user address with the maximum network utilization rate in the preset time belongs may also be used as the network account affected by the fault, and the information of the network account affected by the fault may also be determined in other ways according to the network utilization rate, which is not particularly limited in this example. In this example embodiment, when a group fault condition is met, the acquired user network accounts hung under several continuous fault base stations may be used as network accounts affected by the fault, for example, the user network accounts hung under five continuous fault base stations may be used as network accounts affected by the fault.

In step S230, according to the network account information, the customer information affected by the fault is found by the customer management system. In this exemplary embodiment, if the fault type information is a broadband network fault, the client information of the corresponding user may be found through the client management system according to the network account information. And if the fault type information is a wireless network fault, directly obtaining the customer information through the network account information. The customer information may be the customer's contact, such as the customer's contact phone or cell phone number. For a wireless network, the network account information is the mobile phone number of the client. For broadband users, the contact information of the client, such as a mobile phone number, can be searched through the client management system.

In step S240, based on the failure type information and the failure device information, a corresponding H5 link is generated, resulting in failure notification information including an H5 link. In this example embodiment, the fault notification information including the link H5 may include basic fault information and the link H5, where the basic fault information may include repair duration and fault scenario, and may further include information such as fault cause, which is not particularly limited in this example. In this example, the basic failure information can be directly displayed in the notification short message, so that the user can obtain the basic failure information without clicking the link H5, thereby improving the failure notification effect.

In the present exemplary embodiment, the H5 link is used to display more detailed fault information. The H5 link is provided with a field maintenance uploading control, a user feedback control, a fault description control and a timing control for displaying fault information on a corresponding H5 page. In the present exemplary embodiment, H5 refers to Html (internet hypertext markup language) 5 th generation and also refers to all digital products produced in the H5 language. Its main goal is to semantize the internet while providing better support for embedding of various media. The H5 page has only one page from top to bottom, and can also be simply understood as a single web page, and is matched with information such as various pictures, videos, characters and the like. And the HTML5 technology can realize one-time development, can be used by multiple ends across platforms, namely one-time website release, and can simultaneously realize browsing experience at each terminal such as a PC, a mobile phone, WeChat, an IPAD and the like. In addition, the H5 page usually uses a large amount of scrolling detection effects, i.e. a large amount of text or pictures can be automatically loaded while the page is being slid, which is very suitable for mobile browsing.

In the present exemplary embodiment, the field maintenance uploading control is used for a front-line maintenance staff to upload picture or video information of field maintenance, so that a user can timely know the current field maintenance situation by browsing an H5 page, and the failure notification efficiency is improved. In addition, text information may also be uploaded, and the form of the uploaded information is not particularly limited in this example. The user feedback control is used for commenting and feeding back the fault notification information by a user, so that a front-line maintenance worker can timely know the maintenance effect and the user feedback. The fault description control for displaying fault information is used for displaying information such as fault reasons and fault scenes of the fault, and can also include first-line maintenance personnel information and a maintenance personnel contact mode, so that a user and first-line maintenance personnel can communicate with fault removal conditions in time, for example, residual fault removal time estimated by the maintenance personnel. And the timing control is used for displaying the residual time of the repair duration estimated by the system, and the residual time can be displayed in a dynamic countdown mode. In this example embodiment, the H5 page may further include other modules, for example, information such as a comp flow, and may further include a fault work order processing flow unit and a complaint unit, which is not particularly limited in this example.

In the present exemplary embodiment, referring to fig. 5, generating a corresponding H5 link based on the failure type information and the failed device information may be accomplished through steps S510-S530.

In step S510, a fault scenario and a repair duration are predicted according to the fault type information and the fault device information. In the present example embodiment, the fault scenario may be a municipal project, a municipal power outage, a line cut, special weather (e.g., a sand storm, a typhoon, a debris flow), and other scenarios, and the like.

In the present exemplary embodiment, referring to fig. 6, a failure scenario and a repair duration may be determined through steps S610-S630.

In step S610, history failure information is acquired. In the present example embodiment, historical fault data may be obtained from a historical fault database. Data selection can be performed according to fault scenes and occurrence time. For example, historical fault information may be selected that is recent and encompasses all fault scenarios. Historical fault alarm information, historical fault scenario information, and historical repair duration may be included. The historical fault warning information may include fault type information and fault equipment information, may also include information such as warning time, fault cause, local network, office direction, and the like, and may also include time limit information of a warning work order, which is not particularly limited in this example. Historical fault scenario information may include municipal works, municipal blackouts, line cuts, special weather (e.g., sand storms, typhoons, debris flows), and other scenarios, among others. The historical repair time period may be the actual time period it takes to repair the fault that has occurred.

In step S620, training a fault classification prediction model using the historical fault information; the fault classification prediction model may be a random forest prediction model, a Light-gbm (Light Gradient Boosting machine), or the like, or may be another similar network model, which is not particularly limited in this example. For example, the training process is described by taking a random forest algorithm as an example. The random forest prediction model is a more accurate and stable model obtained by establishing a plurality of decision trees and fusing the decision trees, and is a combination of bagging thought and random selection characteristics. And when a certain sample needs to be predicted, counting the prediction results of each tree in the forest on the sample, and selecting the final result from the prediction results by a voting method. The training of the random forest is to reduce the training variance by characteristic sampling and improve the integration generalization capability. The training process is a process of continuously adjusting model parameters. The parameters of the random forest prediction model are divided into two categories: the process parameters and the base learner parameters are debugged first (e.g., the number of base learners) and then the base learner parameters (e.g., the maximum depth of the decision tree). The training process may be: firstly, randomly putting back samples from an original training set by using a Bootstrap method, taking m samples, and carrying out n _ tree times of sampling, wherein m is a positive integer, and n _ tree is a positive integer, so as to generate n _ tree training sets. Secondly, for n _ tree training sets, n _ tree decision tree models are trained respectively, namely one training set trains one decision tree model. Then, for a single decision tree model, assuming that the number of training sample features is n, where n is a positive integer, the best feature is selected for splitting according to information gain/information gain ratio/kini index and the like during each splitting. Each decision tree is split until all training samples for that node belong to the same class. And finally, forming a random forest model by the generated multiple decision trees.

In step S630, the trained fault classification prediction model is used to predict the fault scene category and the repair duration of the current fault. In the present exemplary embodiment, as shown in fig. 7, the inputs of the fault classification prediction model are the fault cause, the fault type, the local network, the office direction, the actual duration of repair work, the work order time limit, etc., and the outputs are the predicted fault scenario and the predicted repair time duration, and when determining the fault scenario, the fact is a classification problem, and the final classification result can be determined according to voting of a plurality of tree classifiers. For the restoration duration prediction, the essence is a regression problem, and the final prediction result can be determined by the mean value of the predicted values of the multiple trees.

In step S520, selecting one of preset H5 page templates for editing to generate an H5 notification page; so that H5 has a field repair upload control, user feedback control, fault description control for presenting fault information, and timing control on the notification page. According to the user requirements, selecting a proper template from preset H5 page templates for editing, wherein the template can comprise a plurality of link assemblies and functional areas, one link assembly can be set as a field maintenance uploading control, and a plurality of functional areas can be set as a user feedback control, a fault description control for displaying fault information and a timing control; other link components or function modules may also be added, for example, a front-line service person contact link component or function module, etc., which is not limited in this example. The H5 notification page is generated after the above editing is completed.

In step S530, the generated H5 notification page is associated with the two-dimensional code or the short link to generate an H5 link. In the present example embodiment, the generated H5 notification page may be associated with a two-dimensional code or short link, generating a corresponding H5 link to facilitate the dissemination of information. The user can check the information on the H5 page by clicking the received H5 link, so that the user can timely and effectively acquire fault conditions, first-line maintenance information, real-time fault processing conditions and the like, transparent notification of faults is realized, and user experience is improved.

In step S250, the fault notification information is sent to the corresponding client or client terminal according to the client information affected by the fault.

In this example embodiment, the customer information affected by the fault may be a contact address of the customer affected by the fault, such as a mobile phone number or client account information. The fault notification information may include the H5 link generated in the above embodiment, may further include a fault reason and a fault description, and may further include basic information (such as name, work category, working age, etc.) and a contact manner thereof, so that the user can communicate with the front-line maintenance staff in time. The failure notification information may also include compensation information for the user by the operator, such as the gift traffic or the telephone charge. This example is not particularly limited thereto. In the present exemplary embodiment, the fault notification information may be sent to the user terminal (user mobile phone) by a short message, or the fault notification information may be pushed to the client of the user by the electric channel system, for example, the fault notification information may be pushed to the wechat client of the user or other clients by an operator online business hall, a palm business hall, or a wechat public number, etc.

In this exemplary embodiment, a failure notification manner may be determined according to the alarm time, where the failure notification manner includes an immediate notification and a delayed notification. For example, if the alarm time is night, the fault notification mode is determined as delayed notification to avoid disturbing the rest of the client. And if the fault notification is determined to be the instant notification, immediately sending corresponding fault notification information to the client after receiving the fault warning information. And if the delay notice is determined, determining the delay time according to the alarm time. For example, when the alarm occurs at night, the time period from the alarm time to the daytime working time (for example, seven or eight points) is calculated and taken as the delay time period. And finally, sending corresponding fault notification information to the client based on the delay time length.

In this example embodiment, a return visit process of the failure notification result may also be included. For example, the fault notification result can be revisited by dialing the telephone of the fault notification user through artificial intelligence. The following process can be carried out: firstly, according to the return visit purpose, a return visit number is randomly selected from fault or group fault short message notification numbers according to a set rule. And then the return visit number list is transmitted to the intelligent outbound platform. And setting an external calling operation on the intelligent external calling platform, and counting the external calling return visit result.

For example, as shown in fig. 8, the network failure notification process of the present disclosure is illustrated by one specific embodiment.

For group barriers, it comes from three channels:

step S801, first alarm information sent by network element equipment; step S802, a front-line worker inputs second alarm information caused by the equipment fault through the terminal equipment; step S803, the customer service receives the third warning message triggered by the failed sudden increase of the plurality of subscriber numbers, broadband numbers or mobile phone numbers. For example: and the fault network element equipment sends first alarm information. The broadband group fault alarm information is from an OLT network element, an ONU network element and the like, and the wireless group fault alarm information is from a base station, an IPRAN alarm, a base station dynamic loop, a network topology and the like. For example, the network element device alarm information includes: broad band group barrier: OLT equipment IP address or PON port frame-plate-groove; for example, a PON port main optical circuit breaker under a broadband OLT device. The wireless group barrier is defined as: more than five contiguous base station IDs.

Step S804, the fault notification server receives the fault warning information.

And step S805, generating an alarm work order. And converting the alarm work order of the equipment dimension into a group obstacle alarm work order of the user dimension. In actual operation, an equipment comprehensive alarm work order can be generated according to the alarm information. And converting the original equipment alarm information into a comprehensive alarm work order according to a preset group fault service order rule. The step is that the equipment alarm information is generated into a comprehensive alarm work order according to the business rules formulated by the service requirements of the operator group fault, and the comprehensive alarm work order is divided into a broadband dispatching rule and a wireless dispatching rule. The finally generated broadband comprehensive alarm work order comprises alarm time, work order processing time limit, a local network, a local direction, an alarm type, an OLT equipment IP address or a PON port, alarm description and the like; the generated wireless comprehensive alarm work order comprises alarm time, work order time limit, local network, office direction, alarm type, base station ID, base station name, fault reason and the like.

And step S806, sending the alarm work order to a network management system.

Step S807, the network management system matches the information of the network account affected by the fault according to the received alarm work order.

And step S808, sending the matched network account information to a customer management system.

Step S809, the customer management system receives the network account information, and searches the customer information affected by the fault according to the network account information.

In step S810, the customer management system sends the customer information affected by the fault to the fault notification server.

In step S811, the failure notification server receives client information affected by the failure.

Step S812, the fault notification server generates a corresponding H5 link based on the fault type information and the fault equipment information, and obtains fault notification information containing an H5 link; the H5 link is provided with a field maintenance uploading control, a user feedback control, a fault description control and a timing control for displaying fault information on an H5 page corresponding to the H5 link;

in step S813, the fault notification server sends the fault notification information to the corresponding client or client terminal according to the client information affected by the fault. I.e. push group barrier transparency notification information to the customer. And (4) distinguishing different obstacle scenes, and pushing H5-linked transparent group obstacle notification information or give away traffic to the user.

Step S814, a line maintainer uploads the pictures, videos, and texts during the maintenance process through the H5 link. In this example, after the uploaded information passes the audit, the customer can check the group obstacle repair process of the first-line maintainer by clicking a short message or an H5 link pushed by a micro-hall, and meanwhile, online interaction, online feedback and the like between the first-line maintainer and the obstacle-receiving user are supported.

Step S815, artificial intelligence calls back to visit. And setting different topics for the user sending the group fault transparency notification information according to different return visit purposes, and then carrying out outbound return visit to finally obtain a return visit result.

According to the network fault notification method provided by the disclosure, the network account information affected by the fault can be matched through the network management system according to the received fault type information and the fault equipment information; and then according to the network account information, searching customer information affected by the fault through a customer management system, further determining the customer information needing fault notification, and ensuring that each user affected by the fault can know the fault condition in time. Generating a corresponding H5 link based on the fault type information and the fault equipment information to obtain fault notification information containing an H5 link; and the H5 link is provided with a field maintenance uploading control, a user feedback control, a fault description control for displaying fault information and a timing control on a corresponding H5 page. And sending the fault notification information to a corresponding client or a client terminal according to the client information affected by the fault. On one hand, the fault information of the user can be timely and actively informed, and the current situation that the user passively learns the fault is improved. On the other hand, a maintenance worker can upload a field maintenance picture through the H5 link, so that a user can timely and effectively know the fault condition and the specific maintenance progress, and the user experience is improved. In addition, the interaction between the user and a front-line maintenance worker can be carried out through the H5 link, the flexibility of obtaining fault information is increased, and the user experience is further improved.

Further, in the present exemplary embodiment, a network failure notification apparatus 900 is also provided. The network failure notification apparatus 900 may be applied to a server. Referring to fig. 9, the network failure notification apparatus 900 may include:

a receiving module 910, configured to receive fault alarm information, where the fault alarm information at least includes fault type information and fault device information;

the matching module 920 may be configured to match, according to the fault type information and the fault device information, network account information affected by the fault through a network management system;

a searching module 930, configured to search, according to the network account information, customer information affected by the fault through a customer management system;

a generating module 940, configured to generate a corresponding H5 link based on the fault type information and the fault device information, to obtain fault notification information including an H5 link; the H5 link is provided with a field maintenance uploading control, a user feedback control, a fault description control and a timing control for displaying fault information on an H5 page corresponding to the H5 link;

the sending module 950 may be configured to send the fault notification information to a corresponding client or client terminal according to the client information affected by the fault.

In an exemplary embodiment of the present disclosure, the receiving module 910 may include:

the first receiving module may be configured to receive first fault warning information reported by a faulty device.

And the second receiving module can be used for receiving second fault alarm information triggered by the customer service system.

And the third receiving module can be used for receiving third fault warning information uploaded by operation and maintenance personnel.

In an exemplary embodiment of the present disclosure, the second receiving module may include:

the receiving submodule can be used for receiving fault complaint customer information sent by the customer service system;

the account number determining module can be used for matching a customer management system to obtain corresponding complaint network account number information according to the fault complaint customer information;

the fault device determining module may be configured to, according to the complaint network account information, match the network management system to obtain a corresponding optical line terminal OLT device address, passive optical network PON port number, or base station identifier, and obtain second fault type information and fault device information, that is, second fault warning information.

In an exemplary embodiment of the present disclosure, the generating module includes:

the prediction module can be used for predicting a fault scene and repairing time according to the fault type information and the fault equipment information;

the editing module can be used for selecting one template from preset H5 page templates to edit so as to generate an H5 notification page; so that H5 has a field repair upload control, user feedback control, fault description control for presenting fault information, and timing control on the notification page.

And the association module can be used for associating the generated H5 notification page with the two-dimensional code or the short link to generate an H5 link.

The specific details of each module or unit in the network fault notification apparatus have been described in detail in the corresponding network fault notification method, and therefore are not described herein again.

As another aspect, the present application also provides a computer-readable medium, which may be contained in the electronic device described in the above embodiments; or may exist separately without being assembled into the electronic device. The computer readable medium carries one or more programs which, when executed by an electronic device, cause the electronic device to implement the method as described in the embodiments below. For example, the electronic device may implement the steps shown in fig. 2 to 8.

It should be noted that the computer readable media shown in the present disclosure may be computer readable signal media or computer readable storage media or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present disclosure, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In contrast, in the present disclosure, a computer-readable signal medium may include a propagated data signal with computer-readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.

It should be noted that the computer system 1000 of the electronic device shown in fig. 10 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present disclosure.

As shown in fig. 10, the computer system 1000 includes a Central Processing Unit (CPU)1001 that can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM)1002 or a program loaded from a storage section 1008 into a Random Access Memory (RAM) 1003. In the RAM 1003, various programs and data necessary for system operation are also stored. The CPU 1001, ROM 1002, and RAM 1003 are connected to each other via a bus 1004. An input/output (I/O) interface 1005 is also connected to bus 1004.

The following components are connected to the I/O interface 1005: an input section 1006 including a keyboard, a mouse, and the like; an output section 1007 including a display such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; a storage portion 1008 including a hard disk and the like; and a communication section 1009 including a network interface card such as a LAN card, a modem, or the like. The communication section 1009 performs communication processing via a network such as the internet. The driver 1010 is also connected to the I/O interface 1005 as necessary. A removable medium 1011 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 1010 as necessary, so that a computer program read out therefrom is mounted into the storage section 1008 as necessary.

In particular, the processes described below with reference to the flowcharts may be implemented as computer software programs, according to embodiments of the present disclosure. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method illustrated in the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network through the communication part 1009 and/or installed from the removable medium 1011. When the computer program is executed by a Central Processing Unit (CPU)1001, various functions defined in the method and apparatus of the present application are executed.

The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

It should be noted that although the various steps of the methods of the present disclosure are depicted in the drawings in a particular order, this does not require or imply that these steps must be performed in this particular order, or that all of the depicted steps must be performed, to achieve desirable results. Additionally or alternatively, certain steps may be omitted, multiple steps combined into one step execution, and/or one step broken down into multiple step executions, etc., are all considered part of this disclosure.

It should be understood that the disclosure disclosed and defined in this specification extends to all alternative combinations of two or more of the individual features mentioned or evident from the text and/or drawings. All of these different combinations constitute various alternative aspects of the present disclosure. The embodiments of this specification illustrate the best mode known for carrying out the disclosure and will enable those skilled in the art to utilize the disclosure.

Claims

1. A method for network fault notification, comprising:

2. The network fault notification method of claim 1, wherein the receiving fault alarm information at least comprises:

receiving first fault alarm information reported by fault equipment;

3. The method according to claim 2, wherein the receiving the second fault warning message triggered by the customer service system comprises:

4. The network failure notification method according to claim 1, wherein the failure type information includes a broadband network failure and a wireless network failure;

5. The method according to claim 4, wherein matching, by the network management system, the network account information affected by the fault according to the fault type information and the fault device information includes:

when the fault type information is a wireless network fault, then:

6. The method according to claim 4, wherein the finding, according to the network account information, the customer information affected by the fault by a customer management system includes:

7. The network fault notification method according to claim 1, wherein the generating a corresponding H5 link based on the fault type information and the faulty device information comprises:

selecting one template from preset H5 page templates for editing to generate an H5 notification page; so that the H5 notification page has a field maintenance uploading control, a user feedback control, a fault description control for displaying fault information and a timing control;

8. The method according to claim 7, wherein predicting a fault scenario and a repair duration according to the fault type information and the faulty device information comprises:

training a fault classification prediction model by adopting historical fault information;

9. The method of claim 4, wherein the method further comprises:

10. A network failure notification apparatus, comprising:

11. A computer-readable medium, on which a computer program is stored, which program, when being executed by a processor, is adapted to carry out the method of any one of claims 1-9.

12. An electronic device, comprising:

one or more processors;

storage means for storing one or more programs which, when executed by the one or more processors, cause the one or more processors to carry out the method of any one of claims 1-9.