CN100442722C - Method and device for diagnosing network faults - Google Patents

Abstract

The invention discloses a network fault diagnosis method to solve the problems of inaccurate positioning, long positioning time and high cost in diagnosing network faults in the prior art; the method is as follows: the network side receives and records the user's fault Declare; determine whether the call of the user reporting the fault is normal, if not, determine that the user line is faulty, otherwise, initiate a connectivity test command from the customer premise equipment CPE corresponding to the user to the network side, and judge whether the connectivity of the protocol layer is based on the test result Normal, if not normal, then determine the protocol layer connectivity failure, otherwise, send a simulation protocol operation or/and request from the CPE to the network side, and determine whether the network protocol is normal according to the operation result. The invention also discloses a network fault diagnosis device at the same time.

Description

Method and device for diagnosing network faults

technical field

The invention relates to broadband network technology, in particular to a fault diagnosis method and device of a Digital Subscriber Line (DSL) broadband network.

Background technique

User access to DSL broadband network needs to go through DSL customer premise equipment (CPE), digital subscriber line access module (DSLAM) (CPE and DSLAM are DSL access equipment), broadband access server (BAS), DNS server (DNS Server) When a user encounters a network failure, multiple functional departments (billing center, network management center, measurement room, ground bureau, and outside line team, etc.) need to coordinate and cooperate to find and eliminate the failure.

At present, for DSL network troubleshooting, telecom operators generally use the broadband test board solution to test the line in the measurement room, and use the network management to support the line grabbing function to locate line faults. If it is not a line failure, the network management center personnel check the port status to determine whether there is a failure, or the outside personnel go to the location of the user terminal to assist in understanding the failure phenomenon, and then all parties communicate and locate repeatedly, and gradually troubleshoot the failure based on experience. After troubleshooting, users need to be notified to try to see if the broadband network can be used normally.

The above-mentioned fault location method has the following disadvantages:

1. Line faults generally account for less than 20% of all broadband network faults, and line tests require expensive broadband test heads, so their implementation will be limited due to cost issues, especially in small and medium sites.

2. The entire troubleshooting process relies on experience to check step by step, which not only takes a long time and high labor costs, but also the positioning is not completely accurate.

3. The troubleshooting process requires the cooperation of the user on site, which leads to a long troubleshooting cycle due to human factors, and also affects customer satisfaction.

Contents of the invention

The invention provides a network fault diagnosis method and its device to solve the problems of inaccurate positioning, long positioning time and high cost in diagnosing network faults in the prior art.

A method for diagnosing a network fault, wherein a user terminal in the network accesses an external network through a customer premises equipment (CPE), a digital subscriber line access module (DSLAM), and a broadband access server (BAS) successively, comprising the steps of:

A, the network management side receives and records the failure report of the user; B, judges whether the communication of the user reporting the failure is normal, if normal, then proceed to step C, otherwise determine that the user line is faulty; C, from the corresponding customer premises equipment (CPE) of the user Initiate a connectivity test command to the network side, judge whether the protocol layer connectivity is normal according to the test results, if so, continue to step D, otherwise, determine the protocol layer connectivity failure; D, send the simulation protocol operation or/or from the CPE to the network side and request, and determine whether the network protocol is normal according to the operation result.

In step A, when the user declares a fault, the user is prompted by voice to input information about whether the call is normal, and in step B, it is directly judged whether the user’s call is normal according to the information; or, in step B, it is judged by initiating a call to the user number Whether the user's call is normal.

Step C includes the following steps:

C1, activate and deactivate the digital subscriber line access module (DSLAM) port, if the activation and deactivation are normal, then continue to step C2, otherwise determine that the central office is faulty; C2, carry out remote reset to the customer premises equipment (CPE), If it cannot be reset normally, it is determined that the CPE is faulty, otherwise continue to step C3; C3, initiate a Ping command from the CPE to the broadband access server (BAS), if the BAS responds normally, then continue to step C4, otherwise it is determined that the connectivity between the CPE and the BAS is faulty ; C4. Initiate a Ping command from the CPE to the network control equipment in the direction from the BAS to the network. If each network control equipment responds normally, proceed to the subsequent steps; otherwise, it is determined that there is a connectivity fault between the BAS and the network control equipment that responds abnormally. .

Step D comprises the following steps:

D1, initiate the PPP call of emulation from CPE to BAS, judge whether BAS is normal to the response of PPP call, if then continue step D2, otherwise determine BAS protocol layer failure; D2, initiate domain name resolution request from CPE to domain name server (DNS), If the DNS server responds abnormally, it is determined that the DNS protocol layer is faulty. If it is determined that the DNS is normal, it also includes the following steps: D3, initiating a file transfer protocol (FTP) speed test from the CPE, and determining whether there is a local network and/or according to the test result from the CPE to the standard file transfer protocol (FTP) test server The external network speed is low.

A network fault diagnosis device, comprising:

The diagnosis management unit is used to establish the mapping relationship between users and related network resources in the network, receive and record the user's failure report, and determine that the user's line failure is determined if the user who declares the failure is abnormal; Then issue a connectivity test command, and judge whether the connectivity of the protocol layer is normal according to the received test result. If it is abnormal, determine that the connectivity of the protocol layer is faulty; Whether the network protocol is normal;

The diagnostic agent unit is configured to initiate a connectivity test command from the customer premises equipment CPE corresponding to the user to the network side according to the connectivity test command issued by the diagnostic management unit, and return the test result to the diagnostic management unit; and according to the The simulation test command issued by the diagnosis management unit sends a simulation protocol operation or/and request from the CPE to the network side, and returns the test result to the diagnosis management unit.

The diagnostic management unit includes:

A fault report interface module, configured to receive report information related to faults;

The user resource management module is used to bind user information to the physical port used by the user;

Diagnosis configuration management module, used to configure test parameters;

Network management interface module, used to issue test commands;

The test task management module is used to establish test tasks according to configuration test parameters and collect test results;

The fault diagnosis and analysis module is used for fault analysis according to the test results.

The diagnosis management unit further includes: a Web service access support module, which is used to provide browser access.

The present invention has the following beneficial effects:

1. Through the automatic fault diagnosis function of this system, telecom maintenance personnel can quickly locate the fault section and improve the troubleshooting speed.

2. Through the transformation of the voice prompt, the user is forced to power on, reducing the misjudgment of the automatic fault diagnosis, and collecting the connection and disconnection of the line.

3. Through the verification test automatically performed by the system, after the telecom maintenance personnel troubleshoot, they can verify whether the network is normal or not without the cooperation of the user.

4. Through the automatic fault diagnosis of this system, using the standard FTP reference server and standard reference website, the local telecom maintenance personnel can judge whether it is the fault of the access network or the fault of different routing bureaus of the external network (MAN).

5. Combined with user resource management, the system performs troubleshooting directly based on the user's declared phone number, which reduces the inconvenience for maintenance personnel to operate in multiple systems.

6. The present invention is a solution based on terminal management, which solves 80% of network failures and does not require a broadband test head, so it is suitable for diagnostic testing of small and medium sites.

Description of drawings

Figure 1 is a schematic diagram of an end-to-end protocol stack of a broadband system;

Fig. 2 is a fault diagnosis device of the present invention and a schematic diagram of networking of the system where it is located;

Fig. 3 is a structural schematic diagram of a diagnosis management unit in the fault diagnosis device;

Fig. 4 is the flowchart of diagnosing connectivity failure among the present invention;

Fig. 5 is a flow chart of diagnosing protocol layer faults in the present invention.

Detailed ways

From the aspect of broadband network Internet access service operation, the entire service channel can be divided into PC, PC-Customer Premise Equipment (CPE), CPE, CPE-Digital Subscriber Line Access Module (DSLAM), DSLAM, DSLAM-Broadband Access Server (BAS ), BAS, BAS-intetnet server and internet server links, all these links may have problems, the management scope of the local telecom network operator is between CPE and BAS, and the present invention covers PC-CPE, CPE, CPE-DSLAM, DSLAM , DSLAM-BAS, BAS, BAS-internet server these links fault diagnosis and location, the present invention does not diagnose the fault of PC and internet server itself. The CPE refers to the terminal equipment used in the DSL network, including ADSL CPE, VDSLCPE, G.SHDSL CPE, etc.

Referring to shown in Fig. 1, common end-to-end protocol (PPP) dial-up user's protocol description in the dial-up process and surfing the Internet process is as follows (note: PPP dial-up is the practical mode of most individual ordinary users at present):

1. PPP dial-up process protocol description

(1) During PPP dialing, the user initiates a PPP call on the PC side and requests authentication, and the authentication request is carried on the Ethernet frame (MAC).

(2) On the CPE, encapsulate the MAC frame in the ATM cell and pack it in the DSL superframe.

(3) Data is exchanged between the CPE and the central office DSLAM access device through fixed-length DSL superframes.

(4) The DSLAM unpacks the ATM cells from the DSL superframe. If it is a DSLAM with an ATM uplink interface, it communicates with the BAS authentication device through ATM cells; if it is a DSLAM with an IP The element is restored to the MAC frame, and communicates with the BAS authentication device through the MAC frame.

(5) The BAS extracts the PPP dial-up authentication request packet from the MAC frame and performs authentication. If the authentication is passed, an IP address is allocated, included in the PP response, and sent to the PC in the opposite direction to the authentication request, so that the user has an IP address, you can go online. Among them, the PPP call is terminated on the BAS.

2. Protocol description in the process of surfing the Internet

(1) When surfing the Internet, all application layer and session layer protocols (such as HTTP requests, FTP, SMTP, etc.) used by users on the PC side are carried on IP packets. Since there are many applications, they all belong to the upper layer protocol. Here The enumeration of application packets above the IP packet is omitted. All IP packets are carried on Ethernet frames (MAC).

(2) On the CPE, encapsulate the MAC frame in the ATM cell and pack it in the DSL superframe.

(3) Data is exchanged between the CPE and the central office DSLAM access device through fixed-length DSL superframes.

(4) The DSLAM unpacks the ATM cells from the DSL superframe. If it is a DSLAM with an ATM uplink interface, it communicates with the BAS authentication device through ATM cells; if it is a DSLAM with an IP The element is restored to the MAC frame, and communicates with the BAS authentication device through the MAC frame.

(5) BAS receives the IP packet, forwards it directly to the router on the Internet, and finally reaches the Internet server required by the upper layer protocol. The Internet server packs the response message of the application layer protocol into an IP packet and returns it to the BAS, and the BAS transmits the data to the user's PC in the opposite direction.

In order to be able to diagnose DSL broadband network faults at low cost and quickly, the present invention finds the corresponding user resource through the phone number in the system resource management after the user declares the fault, and first judges whether the user line is normal; if the user line is normal, it automatically downloads Send a command to initiate a connectivity test command from the customer premises equipment (CPE) to the network side, and judge whether the protocol layer connectivity is normal according to the test result; if the protocol layer connectivity is normal, initiate a simulation test from the CPE, that is, initiate a simulation protocol at the CPE The operation or/and request is sent to the network side, and it is determined whether the network protocol is normal according to the operation result.

Referring to Fig. 2, the fault diagnosis device of the present invention includes a diagnosis management unit and a diagnosis agent unit. The diagnosis management unit is arranged on the network management side, and the diagnosis agent unit can be arranged in the CPE. The diagnosis management unit is responsible for establishing the mapping relationship between users and related network resources, and automatically sends a series of test commands to the diagnosis agent unit in the CPE; The unit returns the test result, and the diagnosis management unit analyzes the fault segment and the protocol layer of the test result, locates the fault segment and outputs the cause of the fault.

Referring to Figure 3, the diagnosis management unit includes:

Web service access support module: the system is based on the Apache platform, provides IE access through the Web service access control layer, and realizes zero client installation (that is, it does not need to install any client, just use the internet explorer that comes with the PC operating system) .

Fault report interface module: used to connect to the fault report form system of the telecom operator's Operation Support System (OSS), and automatically accept the relevant report information of the fault report to realize the automatic fault diagnosis function.

User resource management module: Bind the broadband user name, account number, phone number and the specific physical port location information used by the user, and support the query of the declared user.

Fault diagnosis and analysis module: According to the results of user tests, analyze and judge faults, and provide the function of one-key diagnosis (including step-by-step diagnosis).

Diagnosis configuration management module: the user configures various test parameters according to needs, and forms different configuration templates for use during testing.

Test task management module: According to the user, the test task is automatically established by using the diagnostic configuration, the test results are collected, and provided to the diagnostic analysis module for troubleshooting.

Network management interface module: used to connect to the network management system, and issue Simple Network Management Protocol (SNMP) commands to the equipment through the network management system to request the execution of test functions.

When the user cannot access the Internet, he needs to report the failure to 112 or 10000 of the telecommunications bureau and leave his phone number. The network management system can find out the equipment port and CPE corresponding to the user line according to the telephone number. In order to judge whether the user's line is normal, a relatively simple method is to ask the user to input whether the call is normal in the voice prompt of the fault report, and record the user's phone number and the information into the network management database. Of course, the user may not be required to input, but the system may actively call the user number to determine whether the line is normal.

In order to not require the cooperation of the user when locating the fault and troubleshooting, when the user reports the fault, the prompt sound is used to prompt the user to turn on the power of the CPE after reporting the fault.

After receiving the trouble report work order from the user, the diagnosis management unit can find the user resources corresponding to the telephone number that reported the trouble from the network management database, and use the SNMP protocol to automatically send various test commands to the diagnosis agent unit on the DSLAM and CPE to Execute various simulation and physical tests on the network path of the reporting user, and report the test results to the diagnosis management unit; the diagnosis management unit analyzes the fault segment and protocol layer according to the test results, outputs the test results in a graphical form and prompts the corresponding cause of issue.

Referring to Figure 4, the process of diagnosing whether there is a fault in the connectivity of the IP layer is as follows:

Step 10: According to the user's phone number, find out whether the call entered by the user is normal, if the user determines that the call is normal, go to step 11, otherwise determine that the user's line is faulty.

Step 11: Deactivate and activate the DSLAM port to ensure that the central office port problem is eliminated. If it can be activated normally, proceed to step 12; otherwise, it is determined that the central office is faulty.

After the local end fails, it can be eliminated by changing the port and other replacement methods.

Step 12: Remotely reset the CPE. If the CPE is reset normally, go to Step 13; otherwise, determine that the CPE is faulty.

Because some faults may be caused by CPE software faults, it is necessary to reset the CPE remotely before performing a series of tests to eliminate general software faults (due to the difference in the level of end users, even if the prompt tone or manual After the platform requires the user to perform a reset, the system also needs to automatically perform this operation to ensure the basis for fault judgment in the entire process). For CPE faults, the replacement method can be used to troubleshoot.

Step 13: Initiate a ping test from the CPE. The destination address of the ping is the IP address of the BAS to detect the connectivity from the CPE to the BAS. If the BAS returns a normal ping test result, it indicates that the connectivity from the CPE to the BAS is normal. Proceed to the steps 14; otherwise, it is determined that there is a connectivity fault between the CPE and the BAS, and proceed to step 15.

Step 14: Initiate a ping test from the CPE to the DNS server, egress router, and internet server. If each server can return a normal ping test result, it indicates that the connectivity between the CPE and each server is normal. Otherwise, it is determined that the CPE returns abnormally. There is a connectivity failure between the servers of the Ping test results.

Step 15: Perform asynchronous transfer mode (ATM) layer F5 loopback, sequentially detect the connectivity from the BAS to the DSLAM, and the connectivity from the DSLAM to the CPE, and troubleshoot the faults found in the ATM layer using the replacement method. If there is no problem with the ATM layer detection, it is determined that there is a problem with the IP layer software of the BAS or DSLAM, and you can troubleshoot by changing the port or loading the software.

OAMF5 layer loopback, that is, inserting OAM loopback diagnostic cells into ATM cells to realize data transmission quality diagnosis at the ATM layer: first loop back from the ATM (downlink port) of the BAS to the DSL port corresponding to the reporting user to detect the DSLAM ATM layer connection between DSLAM and BAS; then loop back from ATM port of DSLAM to DSL port of CPE to detect ATM connection between DSLAM and CPE (supported by diagnostic agent unit of CPE).

If the connectivity to the IP layer is normal, you need to test whether the protocol layer is faulty. As shown in Figure 5, the testing process of the protocol layer is as follows:

Step 20: Initiate a PPP (point-to-point) simulation test from the CPE, that is, initiate a PPP call similar to a PC from the CPE (consistent with the process that the user calls through the CPE), and determine whether the response of the BAS to the PPP call is normal according to the BAS equipment return result, If it is normal, go to step 21; otherwise, it is determined that the BAS protocol layer is faulty.

According to the failure reason returned by the PPP call, it can be located whether the IP address allocation for the BAS is unsuccessful, or whether the authentication password is incorrect and other reasons (supported by the diagnostic agent unit on the CPE).

Step 21: Carry out a domain name server (DNS) simulation test, that is, initiate a DNS request through the CPE to simulate the domain name resolution process of the user's PC online request, and judge whether the DNS protocol response is normal according to the result returned by the DNS server. If it is normal, proceed to step 22, otherwise determine the DNS There is a glitch.

Step 22: Perform file transfer protocol (FTP) speed measurement, that is, initiate an FTP request from the CPE to a standard FTP test server, and calculate the FTP download rate according to the size and download time of the downloaded file. If there is a slow FTP rate, then proceed to step 23, and if there is a situation that the protocol is not supported, then a prompt is given.

According to the test results from the CPE to the standard FTP test server, it can be determined whether the speed of the local network or the external network is slow.

Step 23: Reactivate the CPE multiple times, and judge whether the activation rate is low or the high-layer protocol rate is low through line activation parameters and FTP speed measurement. If the activation rate is low, it can be determined that it is caused by aging and crosstalk at the line end. If the activation rate is normal, and If the FTP rate is low, it is determined to be an egress bottleneck on the network side, and the upward bandwidth of the office needs to be adjusted.

After all troubleshooting, it is necessary to perform PPP simulation test and FTP test again to ensure user network availability. If problems are found during verification testing, re-diagnose. If the verification test is normal, the customer is notified that the fault has been rectified.

For more convenient testing, the following test templates can be customized:

Customized Ping test destination IP template: Customize different templates for different Dynamic Host Configuration Protocol (DHCP) servers, DNS servers, BAS servers, routers connected to the internet, and operator standard test websites, so that different users can use Different templates are tested to quickly determine the on-off status of different servers or different network segments.

Customize the target server template for FTP speed test: There are many reasons for the slow Internet speed. For operators, it is mainly to ensure the speed of the network provided by themselves. By setting up a standard FTP server, the speed of the server test is good or bad. It can be judged whether it is the network provided by the operator itself or the quality of service problem of the external network.

Customized DNS/PPP simulation template: Since built-in account information is required for PPP simulation, different templates can be used to set different PPP simulation account parameters for operators in different regions, which is convenient for self-definition.

By realizing the interface with the OSS system, troubleshooting, testing and diagnosis of the entire system are performed automatically.

By adopting the invention, the telecommunication operator can quickly locate which physical link and which protocol layer the fault occurs in the broadband network through the automatic test function. The terminal management solution of the present invention will have great commercial value when applied in small and medium sites.

Obviously, those skilled in the art can make various changes and modifications to the present invention without departing from the spirit and scope of the present invention. Thus, if these modifications and variations of the present invention fall within the scope of the claims of the present invention and equivalent technologies thereof, the present invention also intends to include these modifications and variations.

Claims (13)

1, a kind of diagnostic method of network failure, the user terminal in the described network insert external network by customer premises equipment, CPE CPE, Digital Subscriber Line access module DSLAM, BAS Broadband Access Server BAS successively; It is characterized in that, comprise the steps:

A, webmaster side joint are received and accuse the fault Shen of recording user;

B, judge that whether the user's communication of fault is accused in the Shen normal, if normally then continue step C, otherwise determines the subscriber's line fault;

C, initiate the continuity testing order to network side, judge according to test result whether the protocol layer connectedness is normal from the customer premises equipment, CPE CPE of described user's correspondence, if then continue step D, otherwise, determine the protocol layer failure of connectivity;

D, send the simulation protocol operation or/and request to network side, and determine according to operating result whether procotol is normal from described CPE.

2, whether normally the method for claim 1 is characterized in that, in the steps A, import conversation information by the voice suggestion user when the subscriber complaint fault, judges directly according to this information whether this user's communication is normal in step B; Perhaps, in step B, judge by making a call whether user's communication is normal to Subscriber Number.

3, method as claimed in claim 2 is characterized in that, in the steps A, also opens the CPE power supply by the voice suggestion user when the subscriber complaint fault.

4, the method for claim 1 is characterized in that, step C may further comprise the steps:

C1, Digital Subscriber Line access module DSLAM port is activated and deactivating operation, if activate and deexcitation normally then continues step C2, otherwise definite local side fault;

C2, customer premises equipment, CPE CPE is carried out remote reset, then determine this CPE fault, otherwise continue step C3 if can not normally reset;

C3, initiate the Ping order to BAS Broadband Access Server BAS,, then continue step C4 if BAS replys normally from CPE, otherwise failure of connectivity between definite CPE and BAS;

C4, the net control device that makes progress to network side to BAS respectively from CPE are initiated the Ping order, if each net control device is replied normally, then continue subsequent step; Otherwise determine that there is failure of connectivity in BAS between improper net control device of replying.

5, method as claimed in claim 4 is characterized in that, determines also to comprise the steps: behind the failure of connectivity between CPE and BAS in step C3

C31, respectively carrying out asynchronous transfer mode ATM layer F5 loopback between CPE and the DSLAM and between DSLAM and the BAS to determine whether the ATM layer exists fault, if the ATM layer is normal, then determine the IP layer software fault of BAS or DSLAM.

6, as each described method of claim 1 to 5, it is characterized in that step D comprises the steps:

D1, call out to the PPP that BAS initiates emulation, judge whether BAS is normal to the response that PPP calls out from CPE, if then continue step D2, otherwise definite BAS protocol layer fault;

D2, initiate the domain name mapping request to domain name server (DNS) from CPE, undesired if dns server is replied, then determine DNS Protocol layer fault.

7, method as claimed in claim 6 is characterized in that, determines that DNS just often also comprises the steps:

D3, initiate file transfer protocol (FTP) FTP rate test,, determine whether to exist local network and/or external network speed low according to test result from CPE to normative document host-host protocol FTP testing server from CPE.

8, method as claimed in claim 7 is characterized in that, if when existing FTP speed slow, also comprises the steps:

D4, repeatedly activate CPE, test the speed by line activation parameter and FTP, determine activation rate low still be that upper-layer protocol speed is low, if activation rate is low, then determine to exist line scan pickup coil side aging and crosstalk; If upper-layer protocol speed is low, determine that then there is bottleneck in the network side outlet.

9, method as claimed in claim 8 is characterized in that, this method also comprises step:

E, fix a breakdown;

Whether F, the PPP that initiates emulation to BAS from CPE call out and initiate file transfer protocol (FTP) FTP rate test from CPE, get rid of with validation fault.

10, a kind of network fault diagnosis device is characterized in that, comprising:

Diagnose administrative unit, be used for setting up the mapping relations between network user and the network of relation resource, receive the also fault Shen announcement of recording user,, then determine the subscriber's line fault if judge that the user's communication of Shen announcement fault is unusual; If judge that the user's communication of Shen announcement fault is normal, then issue the continuity testing order, and judge according to the test result that receives whether the protocol layer connectedness is normal, if unusual, then determine the protocol layer failure of connectivity; If normal, then issue the emulation testing order, and determine according to the test result that receives whether procotol is normal;

The diagnostic agent unit is used for the continuity testing order that issues according to described diagnosis administrative unit, initiates the continuity testing order from the customer premises equipment, CPE CPE of user's correspondence to network side, and returns test result to the diagnosis administrative unit; And, send the simulation protocol operation or/and ask to network side, and return test result to the diagnosis administrative unit from described CPE according to the emulation testing order that described diagnosis administrative unit issues.

11, trouble-shooter as claimed in claim 10 is characterized in that, described diagnosis management unit pack is drawn together:

Interface module is accused in the fault Shen, is used to receive the Shen relevant with fault and accuses information;

The user resources administration module is used for user profile is tied to the physical port that the user uses;

The diagnosis Configuration Manager is used for the configuration testing parameter;

The network management interface module is used to issue test command;

The test assignment administration module is used for setting up test assignment according to the configuration testing parameter, and collects test result;

The Analysis on Fault Diagnosis module is used for carrying out accident analysis according to test result.

12, trouble-shooter as claimed in claim 11 is characterized in that, described diagnosis administrative unit also comprises:

Web service visit support module is used to provide the visit of browser mode.

As claim 10,11 or 12 described trouble-shooters, it is characterized in that 13, described diagnostic agent unit is arranged among the customer premises equipment, CPE CPE in the network, described diagnosis administrative unit is arranged in the network of network management system.

Images