WO2008110117A1 - Procédé et dispositif permettant un test de défaut de réseau - Google Patents

Procédé et dispositif permettant un test de défaut de réseau Download PDF

Info

Publication number
WO2008110117A1
WO2008110117A1 PCT/CN2008/070475 CN2008070475W WO2008110117A1 WO 2008110117 A1 WO2008110117 A1 WO 2008110117A1 CN 2008070475 W CN2008070475 W CN 2008070475W WO 2008110117 A1 WO2008110117 A1 WO 2008110117A1
Authority
WO
WIPO (PCT)
Prior art keywords
call
test
network node
loop
parameter information
Prior art date
Application number
PCT/CN2008/070475
Other languages
English (en)
Chinese (zh)
Inventor
Wendi Xiao
Kefeng Wang
Original Assignee
Huawei Technologies Co., Ltd.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co., Ltd. filed Critical Huawei Technologies Co., Ltd.
Publication of WO2008110117A1 publication Critical patent/WO2008110117A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/22—Arrangements for supervision, monitoring or testing
    • H04M3/26—Arrangements for supervision, monitoring or testing with means for applying test signals or for measuring
    • H04M3/28—Automatic routine testing ; Fault testing; Installation testing; Test methods, test equipment or test arrangements therefor
    • H04M3/30—Automatic routine testing ; Fault testing; Installation testing; Test methods, test equipment or test arrangements therefor for subscriber's lines, for the local loop
    • H04M3/307—Automatic routine testing ; Fault testing; Installation testing; Test methods, test equipment or test arrangements therefor for subscriber's lines, for the local loop using ringback
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/50—Testing arrangements

Definitions

  • the present invention relates to the field of network technologies, and in particular, to a network fault testing method and apparatus. Background technique
  • the detection method of the network fault condition includes the ISDN user part protocol ISUP (ISDN User Part) continuity check, the designated relay dial test, and the automatic detection of the external relay turn-on state, but these methods are only It can determine whether there is a fault in the network under test, and what kind of fault exists, and it is impossible to determine which line of the specific gateway in the network is faulty.
  • the automatic detection of the external relay conduction state test method is used to detect the network faults between the two ends (end office 1 and end office 2) as an example. The specific process is as follows, as shown in Figure 1:
  • Step 1 Establish a test loop.
  • the telephone 1 belongs to the end office 1 , the number is 100, the telephone 2 belongs to the destination end office (the end office 2), the telephone number is 200, the telephone 3 belongs to the end office 1 , and the telephone number is 300.
  • Phone 1 dials the number 2 of the telephone 2, and there are many paths for the call message from the end office 1 to the end office 2, such as the telephone 1 -> end office 1 -> tandem office 1 -> tandem office 2 - end office 2 >Telephone 2, Telephone 1 -> End Office 1 -> Connection Office 3 -> Connection Office 4 -> End Office 2 -> Telephone 2, Telephone 1 -> End Office 1 -> Connection Office 1 -> Connection Bureau 3 -> Gateway 4 -> End Office 2 -> Phone 2; the above paths can be randomly selected by the network.
  • the end office 2 judges the call. After the number is the test call number, the data is changed to 300 according to the number configured therein, and the number is changed to 300 (that is, the number of the telephone 3 belonging to the end office 1), and the call message is transferred to the end office 1, possibly in the middle. After the gateway 4 -> tandem 3 -> end 1 , or tandem 2 -> tandem 1 -> end 1 , end 1 receives the call message and then forwards the call to phone 3, and Establish the test loop establishment of end office 1 to end office 2.
  • Step 2 Test according to the test circuit.
  • the end office 1 sends a test signal to the telephone 3 through the telephone 1, such as 12345678, and determines whether there is a fault between the end office 1 and the end office 2 through the signal reception condition of the telephone 3, such as poor voice quality, crosstalk, single pass. Waiting for the situation.
  • the test call specific path from the end office 1 to the end office 2 and the path from the end office 2 to the telephone 3 are unknown, it is only possible to determine whether the communication is available through the tests of the telephone 1 and the telephone 3. Fault, without knowing the specific fault path and the specific location of the fault.
  • the embodiments of the present invention provide a network fault detection method and device, which are used to solve the problem that the fault path in the network cannot be detected in the prior art;
  • a network fault detection method specifically includes the following steps:
  • test loop is detected and a corresponding fault call path is determined based on the call path parameter information when the test loop fails.
  • the embodiment of the present invention further provides a communication network fault testing apparatus, including:
  • Testing a call originating unit configured to initiate a test call to the test destination network node,
  • the call path parameter information of the test call is transmitted to the test destination network node by the test call request;
  • test call receiving unit configured to receive a callback call initiated by the test destination network node on a call path corresponding to the call path parameter information, where the test call and the callback call are connected to the test destination network node for testing a loop, where the callback call request carries call path parameter information;
  • the first detecting unit determines that the test loop has been established according to the received callback call, and detects the test loop, and determines a corresponding fault call path according to the call path parameter information when the test loop fails.
  • a callback call is established on the corresponding test call path according to the call path parameter information in the call message, and the test call and the callback call are connected as a test loop, and then the test is performed.
  • the loop performs detection to determine whether the call path is faulty. Further, using the backtesting method, the specific path location is found in the fault path segment.
  • FIG. 2 is a schematic diagram of an embodiment of a network fault testing method according to an embodiment of the present invention.
  • FIG. 3 is a flow chart of an embodiment of a method for determining a test loop in the method embodiment of FIG. 2;
  • FIG. 4 is a flow chart showing another embodiment of a method for determining a test loop in the method embodiment of FIG. 2;
  • FIG. 5 is a flowchart of an embodiment of a network fault testing method according to an embodiment of the present invention.
  • FIG. 6 is a flowchart of another embodiment of a network fault testing method according to an embodiment of the present invention.
  • FIG. 7 is a schematic structural diagram of an embodiment of a network fault testing apparatus according to an embodiment of the present invention
  • FIG. 8 is a schematic structural diagram of a second network fault testing apparatus according to an embodiment of the present disclosure
  • FIG. 9 is a schematic structural diagram of an embodiment of a third network fault testing apparatus according to an embodiment of the present invention. detailed description
  • the embodiments of the present invention are directed to the problem that the network fault path cannot be determined in the existing network detection technology, and the following solutions are proposed: a test call message is initiated, and a callback call is established according to the call path corresponding to the call path parameter information in the call message, and the call is made. Connect the test call and the callback call, establish a test loop, and then determine whether the call path is faulty by detecting the test loop.
  • the new test loop formed by sequentially establishing the call path parameters or sequentially removing and connecting the corresponding network nodes in the fault path is tested to determine the fault.
  • the specific location by performing a backtesting test on the faulty call path, the new test loop formed by sequentially establishing the call path parameters or sequentially removing and connecting the corresponding network nodes in the fault path is tested to determine the fault. The specific location.
  • FIG. 2 specifically includes the following three main steps:
  • Step 201 Initiating a test call, and transmitting call path parameter information of the test call in the test call message.
  • Step 202 Establish a callback call on the corresponding call path according to the call path parameter information, and connect the test call and the callback call as a test loop.
  • Step 203 Detect whether the test loop is faulty, and if yes, Then the call path is faulty, otherwise the call path is normal.
  • Embodiments of the present invention provide two methods of recording call path parameters for establishing a test loop with an explicit call path, which are described below:
  • test start end office such as SP1
  • test destination network node the test start end office
  • SP2 the destination end office
  • test destination network node and the intermediate network node are relative. In the case of backtesting, when any intermediate network node is in the last position in the test loop, it may become a test destination network node.
  • the test loop is determined by randomly selecting the call path through a special number. That is, the initiating test initiating network node to be tested initiates a special test call, and the call message carries a call path parameter that records the call path of the test initiating network node, such as a special test initiated by an IAM (Initial Address Message).
  • IAM Initial Address Message
  • the IAM message carries the call path parameter of the originating network node call path of the test, and then each network node that receives the test call message in the network initiates according to the called number of the test call to the next network node.
  • Step 301 The network node receives the call
  • an intermediate network node in the network is described herein as a main body.
  • Step 302 Determine, according to the special number carried in the call message, whether the call is a test call, if it is a test call, go to step 303, otherwise, go to step 315; Step 303, determine whether the network node is a destination network node, if If it is the destination network node, go to step 304, otherwise go to step 309;
  • the judgment may be made according to the called number in the call. If the network node does not belong to the network node to which the called party belongs, such as the MSC (Mobile Switching Center) to which the called party belongs, it may be determined. The outgoing network node is not the destination network node, otherwise it is the destination network node.
  • the MSC Mobile Switching Center
  • Step 304 Find the next network node of the callback call from the call path parameter. Callback path;
  • Step 305 Start (ie, generate) a callback to the next network node according to the call path of the next network node, and connect the test call and the callback call;
  • Step 306 Record an incoming call path (a call path of all network nodes that previously participated in the call) in a call path parameter of the IAM;
  • Step 307 Add a call path of the current call to a call path parameter of the IAM.
  • Step 308 Initiate a call back call. The method flow ends.
  • Step 309 it is determined whether the network node is the originating network node, if it is the originating network node, then go to step 310, otherwise, go to step 312;
  • Step 310 Record a call path of the current call to a call path parameter of the IAM;
  • Step 311 Initiate a test call. The method flow ends.
  • Step 312 Record a call path parameter of the call path of all network nodes that previously participated in the call to the IAM;
  • Step 313 Add a call path of the current call to a call path parameter of the IAM.
  • Step 314 Initiate a test call. The method flow ends.
  • Step 315 determining whether the call is a callback call, if it is a callback call, then go to step 316, otherwise go to step 318;
  • Step 316 Determine whether the network node is an originating network node. If the network node is initiated, go to step 317; otherwise, go to steps 304-308 to complete the method.
  • Step 317 Establish a test loop according to the call path determined by the call path parameter recorded in the IAM message. The method flow ends.
  • Step 318 processing according to ordinary calls.
  • the second method Determine the test path based on the network topology map (physical connection diagram between the end offices). That is, the initiating network node to be tested initiates a special test call, and the call path parameter in the call message carries the current call. If the call path of all the network nodes that have passed, such as a special test call initiated by the IAM message, the IAM message carries the call path parameters of all the network nodes through which the call passes, and then each network node in the call path according to the call path The record corresponding to the parameter initiates a call to the next network node in turn, and passes the call path parameter to the next network node until the call returns to the originating network node again. At this point, the call test loop is successfully established.
  • Step 401 The network node receives the call.
  • Step 402 Determine whether the current call is a special test call of the specified call path, and if yes, go to step 403, otherwise go to step 407;
  • whether the special test call of the specified call path is determined according to the special number carried in the received call message and the call path parameter.
  • Step 403 determining whether the network node is the originating network node, if the network node is initiated, then go to step 404, otherwise go to step 405;
  • Step 404 Determine a test loop according to a call path parameter in the call message. The method flow ends.
  • Step 405 Find a call path of the next network node according to the recorded call path parameter.
  • Step 406 Initiate a special call according to a call path of the next network node, and carry a call path parameter in the call message; the method ends.
  • Step 407 processing according to ordinary calls.
  • Embodiment 1 Referring to FIG. 5, which is a flowchart of an embodiment of the present invention, the specific steps are as follows:
  • Step 501 Test the end office SP1, that is, the test originating network node, and initiate a special test call to the SSP1 through the IAM message, where the IAM message includes a new optional parameter record to record the call path from SP1 to SSP1.
  • the parameters included in the test call message are: DPC (Destination signaling Point Code): SSP1; CIC (Circuit Identification Code): CIC1; Call Path CellTRace: SP1+CIC1.
  • the call path parameter is CellTRace: SP1+CICK
  • Step 502 The gateway SSP1 receives the call and recognizes that the call is a special test call, and further obtains the called party identifier, such as the called number, by parsing the call message, thereby determining to which network node to send the call. And selecting the next network node, such as the gateway SSP2 in this embodiment, and then initiating a special test call to the gateway SSP2 through the IAM message, and adding the call path of SSP1 to SPP2 to the call path in the original IAM message. In the parameters, and pass the new call path parameters to the SSP2 via the IAM message.
  • the parameters carried in the call message at this time include: DPC: SSP2; CIC: CIC2; CellTRace: (SP1+CIC1), (SSP1+CIC2).
  • the call path parameters here are: Cell Trace: ( SP1 + CIC1 ) , (SSP1 + CIC2).
  • the special test call here can be added with a special prefix on the called number. If the called number is 123456, then the prefix is changed to ***123456, where *** is a special prefix; The call type parameter representation is added to facilitate receiving the call message party to identify the call type.
  • Step 503 The processing procedure of the gateway SSP2 is the same as that of step 302.
  • the call is sent to the end office SP2.
  • the parameters carried by the call message are: DPC: SP2; CIC: CIC3; CellTRace: (SP1+CIC1), (SSP1+CIC2), (SSP2+CIC3).
  • Step 504 the end office SP2 receives the call, and recognizes that the call is a special
  • the test call is made, and the called party, such as the called number, finds that the called party of the call belongs to the local office, and initiates a test callback call to the gateway SSP2 according to the call path parameter transmitted by the special test call. And connect the special test call to the test callback call to form a closed loop test loop.
  • the call path parameters in the IAM message of the test callback call include the call path of the original special test call, and the newly added SP2 to SSP2 call path, specifically: DPC: SSP2; CIC: CIC4; CellTRace: (SP1+ CIC1), (SSP1+CIC2), (SSP2+CIC3), (SP2+CIC4).
  • Step 505 The gateway SSP2 receives the call, and finds that the call belongs to the test callback call, and is known according to the call path parameter (the call path parameter in the test callback message sent from the previous network node SP2)
  • the next network node that is called back is the network node SPP1 to which the test call message is sent.
  • a test call is initiated to the SSP1, and the call path of the 4th S SP2 to S SP 1 is added to the call path in the original IAM message.
  • the parameters in the message are: DPC: SSP1; CIC: CIC5; CellTRace: (SP1+CIC1), (SSP1+CIC2), (SSP2+CIC3), (SP2+CIC4), (SSP2+CIC5).
  • Step 506 The processing procedure of the gateway SSP1 is the same as step 505; the parameters carried in the test callback message sent to the end office SP1 are: DPC: SP1; CIC: CIC6; CellTRace: (SP1+CIC1), (SSP1+ CIC2), (SSP2+CIC3), (SP2+CIC4), (SSP2+CIC5), (SP1+CIC6).
  • Step 507 The end office SP1 receives the call, and finds that the call belongs to the test callback call, and the call belongs to the local office, and the end office SP1 can determine that the special test call has been successfully established, and determines that the path of the test loop is SP1- SSP1-SSP2-SP2 -—— SP2-SSP2-SSP1-SP1.
  • Step 508 the end office SP1 initiates a test signal, for example, the test signal is: 123456789, when the signal reaches the end office SP1 again through the test loop, the receiving device is started to receive the number, if the receiving result is not: 123456789, but other numbers , then indicates that the transmission has failed.
  • the test signal is: 123456789
  • the receiving device is started to receive the number, if the receiving result is not: 123456789, but other numbers , then indicates that the transmission has failed.
  • Step 509 Start a backtesting test step, that is, on the faulty call path, first Deactivating the test call connection between the two adjacent network nodes and the corresponding callback call connection from the destination network node of the test loop to the test initiation network node according to the call trajectory path recorded in the call trajectory path parameter, and After the removal, the remaining test call connection and the call back call connection are connected as a new test loop, and the call trajectory composed of the remaining network nodes is used as a new test loop, and then the new voice path is tested.
  • the voice paths of SSP2 and SP2 may be removed first according to the call trajectory path parameters.
  • the specific implementation of the removal mode can send a message carrying the Disconnect command to the SSP2 through the test end office SP1.
  • SSP2-SP2 session is removed by the SSP2, and then the SSP1 sends a message carrying the Connect command to the SSP2.
  • SSP2 reconnects the special test call of SSP1-SSP2 and the callback call of SSP2-SSP1 to establish a new test loop:
  • SP1-SSP1-SSP2 SSP2-SSP1-SP1; Or after the SSP2 receives the removal command of the test end office SP1, removes the SSP2-SP2 voice channel, and directly connects the SSP1-SSP2 special test call with the SSP2-SSP1 back.
  • a network node on the call path is sequentially used as a test destination network node to establish a test loop, that is, the SSP1 to SP2 voice path is first removed.
  • test end office SP1 tests the new test loop.
  • the test loop established two times adjacently when the previously established test loop is normal and the test loop established afterwards fails, the line between the adjacent network nodes added in the test loop established later is the faulty line segment.
  • Step 510 Taking the voice channel composed of the two network nodes SSP2 and SP2 as an example, if the test signal sent to the new test loop is: 1234546789, and the received signal is also: 123456789, then the new test loop has no transmission fault.
  • the end office SP1 can determine according to the test result, and the transmission failure occurs in SSP2 and SP2.
  • the specific location may refer to the call path from SSP2 to SP2 recorded in the call path and the call path from SP2 to SSP2.
  • Step 511 Taking the voice path composed of the two network nodes SSP2 and SP2 as an example, if the test signal sent to the new test loop is: 123456789, the received signal is not: 123456789, then the new test loop still has a transmission fault. Then, steps 309 and 310 are repeated, and the network node is gradually removed again. For example, if the SSP1 and SP2 are first removed, the SSP1-SSP2 session is removed again. The new test loop is: SP1-SSP1——SSP1-SP1.
  • the specific location of the fault is determined according to the path of the new test loop and the removed test loop, if the call path is backtracked When it reaches between SP1 and SSP1, the backtesting is terminated. If there is still a transmission fault in the test loop, it indicates that the transmission fault point is on the way from SP1 to SSP1.
  • the present invention may further carry the record test indicator parameter in the test signal message according to the test fault type, and compare the index parameters of the test loop before and after the removal to determine whether there are multiple faults.
  • the backtesting test is performed on the faulty call path from the test destination network node to the test initiation network node segment by segment method, and the test signal parameter is carried in the test signal
  • the SSP2- is removed After SP2, test the new test loop SP1-SSP1-SSP2——SSP2-SSP1-SP1, and record the indicator parameters, then further remove SSP1-SSP2, for the new test loop SP1-SSP1——SSP1-SP1 Test and record the indicator parameters.
  • the embodiment of the present invention can also test the result of each test. Recording, follow-up testing can apply the test record results of previous tests, and the test history results can also be used to analyze network performance, optimize test plans, and so on.
  • the test end office SP1 and each network node that receives the special test call are different according to the previous test record.
  • the previous network node sends a special test call to avoid repeatedly detecting the test loop that has been detected before, so as to ensure that all paths between SP1 and SP2 are traversed quickly and accurately.
  • the specific location of the fault can be determined by the test loop established in the embodiment of the present invention when the test loop is consistent with the faulty voice path.
  • Embodiment 2 Referring to FIG. 6 , a flowchart of another embodiment of the present invention, the specific steps are as follows:
  • Step 601 The test end office SP1, that is, the test originating network node, initiates a special test call, and the call path in the IAM message of the call includes the call path of all network nodes through which the call passes, and SP1 finds the arrival from the call path.
  • the path of a network node, SSP1+CIC1 sends the called IAM message to the next network node SSP1.
  • the IAM message contains the parameters: DPC: SSP1; CIC: CIC1; CellTRace: (SP1+CIC1), (SSP1 +CIC2), (SSP2+CIC3), (SP2+CIC4), (SSP2+CIC5), (SP1+CIC6).
  • Step 602 After receiving the special call, the gateway SSP1 finds that it is a special test call and the call path parameter carried in the test call message has specified a call path, and the SSP1 finds the next network according to the call path.
  • the special test call here can be added with a special prefix on the called number. If the called number is 123456, then the prefix is changed to ***123456, where *** is a special prefix; or by increasing the call type parameter In order to receive the call message party to identify this call type.
  • Step 603 The processing of the gateway SSP2 is the same as step 602, obtaining the next network node from the message, and sending the call message to the next network node SP2, the path is SP2+CIC3, and carrying the parameter in the call message: DPC: SP2; CIC: CIC3; CellTRace: (SP1+CIC1), (SSP1+CIC2), (SSP2+CIC3), (SP2+CIC4), (SSP2+CIC5), (SP1+CIC6).
  • DPC SP2
  • CIC CIC3
  • CellTRace (SP1+CIC1), (SSP1+CIC2), (SSP2+CIC3), (SP2+CIC4), (SSP2+CIC5), (SP1+CIC6).
  • Step 604 After receiving the call message, the end office SP2 finds that it is the destination network node, obtains the next network node of the test callback from the message, and sends a test callback message to the next network node SSP2, the path is SSP2+ CIC4, and carries the parameters in the call message: DPC: SSP2; CIC: CIC4; CellTRace: (SP1+CIC1), (SSP1+CIC2), (SSP2+CIC3), (SP2+CIC4), (SSP2+CIC5), (SP1+CIC6).
  • DPC SSP2
  • CIC CIC4
  • CellTRace (SP1+CIC1), (SSP1+CIC2), (SSP2+CIC3), (SP2+CIC4), (SSP2+CIC5), (SP1+CIC6).
  • Step 605 The processing of the tandem office SSP2 is the same as step 603, that is, the next network node is obtained in the message, and the test callback message is sent to the next network node SSP1, the path is SSP1+CIC5, and the parameter is carried in the callback message.
  • DPC SSP1; CIC: CIC5; CellTRace: (SP1+CIC1), (SSP1+CIC2), (SSP2+CIC3), (SP2+CIC4), (SSP2+CIC5), (SP1+CIC6)
  • Step 606 The processing of the gateway SSP1 is the same as step 605, that is, the path to the next network node is SP1+CIC6, and the parameters are carried: DPC: SP1; CIC: CIC6; CellTRace: (SP1+CIC1), (SSP1+ The test callback message of CIC2), (SSP2+CIC3), (SP2+CIC4), (SSP2+CIC5), (SP1+CIC6) is sent to the test end office SP1.
  • DPC SP1
  • CIC CIC6
  • CellTRace (SP1+CIC1), (SSP1+ The test callback message of CIC2), (SSP2+CIC3), (SP2+CIC4), (SSP2+CIC5), (SP1+CIC6) is sent to the test end office SP1.
  • Step 607 The test end office SP1 receives the call, identifies that the call belongs to the call back call by parsing the received test callback message, and returns the call according to the original test call path, and the call belongs to the local end office, and the test end office SP1 can determine that the special test call has been successfully established and determine that the path of the test loop is SP1-SSP1-SSP2-SP2 - SP2-SSP2-SSP1-SP1.
  • Step 608 the test end office SP1 initiates a test signal, for example, the test signal is: 123456789, when the signal reaches the end office SP1 again through the test loop, the receiving device is started to receive the number, if the receiving result is not: 123456789, but other digital, Then it indicates that the transmission has failed.
  • the test signal is: 123456789
  • the receiving device is started to receive the number, if the receiving result is not: 123456789, but other digital, Then it indicates that the transmission has failed.
  • Step 609 Start a backtracking test, that is, on the faulty call path, first remove two adjacent network nodes from the destination network node of the test loop to the test initiation network node according to the call trace path recorded in the call trace path parameter.
  • the test call connection between the test call and the corresponding callback call connection, and after each removal, the remaining test call connection and the call back call connection are connected as a new test loop, and the call trajectory composed of the remaining network nodes is used as a new Test loop, and then test to the new road.
  • the voice paths of SSP2 and SP2 can be removed first according to the call track path parameters.
  • the specific implementation of the removal mode can send a message carrying the Disconnect command to the SSP2 through the test end office SP1.
  • the SSP2-SP2 session is removed by the gateway SSP2, and then the SSP1 sends a message carrying the Connect command to the SSP2.
  • SSP2 reconnects the special test call of SSP1-SSP2 and the callback call of SSP2-SSP1, establishes a new test loop: SP1-SSP1-SSP2 SSP2-SSP1-SP1; or after SSP2 receives the removal command of test end office SP1
  • SSP2-SP2 session directly connect the special test call of SSP1-SSP2 with the callback call of SSP2-SSP1 to establish a new test loop: SP1-SSP1-SSP2 SSP2-SSP1-SP1.
  • a network node on the call path is sequentially used as a test destination network node to establish a test loop, that is, the SSP1 to SP2 voice path is first removed. Then remove the SSP2 to SP2 loop, and then, as in the above method, re-open the special test call and callback call to establish a new test loop: such as SP1-SSP1 - SSP1-SP, SP1-SSP1-SSP2 - SSP2-SSpl-SPl, l.
  • the test end office SP1 tests the new test loop. In the test loop established two times adjacently, when the previously established test loop is normal and the test loop established later becomes faulty, the line between the adjacent network nodes added in the test loop established later is the faulty line segment.
  • Step 610 Taking the voice channel composed of two network nodes SSP2 and SP2 as an example, if the test signal sent to the new test loop is: 1234546789, the received signal is received. The signal is also: 123456789, then it indicates that there is no transmission failure in the new test loop. According to the test result, the end office SP1 can determine that the transmission fault occurs between SSP2 and SP2, and the specific location can refer to the call path from SSP2 to SP2 recorded in the call path and the call path from SP2 to SSP2.
  • Step 611 Taking the voice channel composed of the two network nodes SSP2 and SP2 as an example, if the test signal sent to the new test loop is: 123456789, the received signal is not: 123456789, then the new test loop still has a transmission fault. Then, repeat steps 309, 310, and then gradually remove the network node. For example, if it is first removed from SSP2 and SP2, then the SSP1-SSP2 session is removed again.
  • the new test loop is: SP1-SSP1 - SSP1-SP1
  • the specific location of the fault is determined according to the path of the new test loop and the removed test loop, if the call path is backtracked When it reaches between SP1 and SSP1, the backtesting is terminated. If there is still a transmission fault in the test loop, it indicates that the transmission fault point is on the way from SP1 to SSP1.
  • all call paths between any two endpoints can be obtained according to the network topology, and then the call path is specified by the present embodiment - test, Traversing the entire topology of the network. If the topology network is faulty, the solution can accurately locate the fault point on the network.
  • the above embodiment uses the ISUP protocol as an example to describe a technical solution for detecting a network transmission fault point by adding a call path parameter in an IAM message.
  • the method of calling the path can also complete the scheme.
  • the IAM message function in the embodiment of the present invention can also be implemented by extending the TEST message.
  • other schemes such as BICC, TUP, and PRA can be used to implement the scheme.
  • the specific processing flow is the same as the above process, and will not be described here.
  • the embodiment of the present invention further provides a network fault testing apparatus 701, which can be set on a network node to perform fault testing.
  • the network The fault testing device 701 includes: a test call initiating unit 702, a test call receiving unit 703, and a first detecting unit 704;
  • the test call initiating unit 702 is configured to initiate a test call to the test destination network node, where the call path parameter information of the test call is transmitted to the test destination network node by using the test call request;
  • the test call receiving unit 703 is configured to receive a callback call initiated by the test destination network node on a call path corresponding to the call path parameter information, where the test call and the callback call are tested by the destination network node. Connected as a test loop, where the callback call request carries call path parameter information;
  • the first detecting unit 704 is configured to determine that a test loop has been established according to the received callback call, and detect the test loop, and determine a corresponding fault call path according to the call path parameter information when the test loop fails.
  • the network fault detecting apparatus provided by the present invention further includes a recording unit. Record the test result of the test loop and the corresponding call path parameter information.
  • the network fault detecting apparatus may further include a call back call initiating unit, configured to, when receiving the test call, initiate a call back according to the call path parameter information of the test call, and connect the test call and the call back call.
  • a call back call initiating unit configured to, when receiving the test call, initiate a call back according to the call path parameter information of the test call, and connect the test call and the call back call.
  • FIG. 8 is a schematic structural diagram of the network fault detecting apparatus, which specifically includes: a test call originating unit. 702.
  • the test call initiating unit 702 is configured to initiate a test call to the test destination network node, where the call path parameter information of the test call passes the test.
  • the call request is passed to the test destination network node;
  • the test call receiving unit 703 is configured to receive a callback call initiated by the test destination network node on a call path corresponding to the call path parameter information, where the test call and the callback call are tested by the destination network node.
  • the callback path request carries call path parameter information;
  • the first detecting unit 704 is configured to determine that a test loop has been established according to the received callback call, and detect the test loop, and when the test loop is faulty Determining a corresponding fault call path according to the call path parameter information;
  • the second detecting unit 705 is configured to receive, after detecting the test loop fault and the corresponding fault path information determined according to the call path parameter information, on the fault call path, initiate the slave station
  • the test destination network node begins to tear down the test call connection between the two adjacent network nodes and the corresponding callback call connection piece by piece, and connects the remaining test call connection and the call back call connection to each new after each removal.
  • FIG. 9 is a schematic structural diagram of the network fault detecting apparatus, which specifically includes: a test call initiating unit 702, Test call receiving unit 703, first detecting unit 704, second detecting unit 706;
  • the test call initiating unit 702 is configured to initiate a test call to the test destination network node, where the call path parameter information of the test call is transmitted to the test destination network node by using the test call request;
  • the test call receiving unit 703 is configured to receive a callback call initiated by the test destination network node on a call path corresponding to the call path parameter information, where the test call and the callback call are tested by the destination network node. Connected as a test loop, where the callback call request carries call path parameter information;
  • the first detecting unit 704 is configured to determine that a test loop has been established according to the received callback call, and detect the test loop, and determine a corresponding fault call path according to the call path parameter information when the test loop is faulty;
  • the third detecting unit 706 is configured to receive, after the first detecting unit detects the fault of the test loop and determine the corresponding fault path information according to the call path parameter information, initiate a slave test on the fault call path. Initiating network node one Starting from the side, a network node on the call path is used as a test destination network node to establish a test loop command, and each established test loop is detected; and in the test loop established two times adjacently, the previously established test loop is normal. When the test loop that is established later fails, the line between the adjacent network nodes added in the test loop that is established later is the faulty line segment.
  • An embodiment of the present invention further provides a communication network testing system, including:
  • test device configured to initiate a test call to the test destination network node, where the test call carries call path parameter information of the test call; and the test destination network node receives a call path corresponding to the call path parameter information Callback call, wherein the test call and the callback call are connected to the test destination network node as a test loop, the callback call request carries call path parameter information; detecting the test loop, and when the test loop Determining a corresponding fault call path according to the call path parameter information when the fault occurs;
  • a destination network node configured to receive a test call that carries the call path parameter information sent by the test device, and respond to the test device with a callback call carrying the call path parameter information.
  • the structure of the above test apparatus can be as shown in Fig. 7, Fig. 8, or Fig. 9 above, and the description thereof will not be repeated.
  • a callback call can be established on the corresponding test call path according to the call path parameter information in the call message, and the test call and the callback call are connected as a test loop, and then By detecting the test loop, it is determined whether the call path is faulty. Further, using the backtesting method, the specific path location is found in the fault path segment. It can be understood that the network fault testing method and apparatus described in the above embodiments can be applied to a circuit domain voice transmission network or other types of transmission networks.
  • the present invention can be implemented by means of software plus a necessary general hardware platform, and of course, can also be through hardware, but in many cases, the former is a better implementation. the way. Based on such understanding, the technical solution of the present invention can contribute in essence or to the part that contributes to the prior art.
  • the form of a software product is stored in a storage medium, including instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform various embodiments of the present invention Said method.
  • a computer device which may be a personal computer, a server, or a network device, etc.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Telephonic Communication Services (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

L'invention concerne un procédé permettant un test de défaut de réseau. Ledit procédé comprend les étapes consistent à : émettre un appel de test au nœud de réseau de destination de test et transmettre les informations de paramètres de trajet d'appel audit nœud de réseau de destination de test à travers la requête d'appel de test ; recevoir l'appel de retour émis par ledit nœud de réseau de destination à travers le trajet d'appel correspondant aux informations de paramètres de trajet d'appel, et connecter ledit appel de test audit appel de retour pour former la boucle de test ; détecter ladite boucle de test et confirmer le trajet approprié d'appel de défaut en fonction desdites informations de paramètres de trajet d'appel lorsqu'il y a un défaut dans la boucle de test. L'invention concerne également le dispositif de détection permettant de réaliser ledit procédé. Dans le mode de réalisation, il est déterminé s'il y a, ou non, un défaut dans le trajet d'appel en établissant l'appel de retour à travers le trajet d'appel correspondant aux informations de paramètres de trajet d'appel dans les informations d'appel, et en connectant ledit appel de test à l'appel de retour pour former la boucle de test et en détectant ensuite ladite boucle de test.
PCT/CN2008/070475 2007-03-12 2008-03-12 Procédé et dispositif permettant un test de défaut de réseau WO2008110117A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CNA2007100734984A CN101022474A (zh) 2007-03-12 2007-03-12 一种网络故障测试方法和装置
CN200710073498.4 2007-03-12

Publications (1)

Publication Number Publication Date
WO2008110117A1 true WO2008110117A1 (fr) 2008-09-18

Family

ID=38710123

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2008/070475 WO2008110117A1 (fr) 2007-03-12 2008-03-12 Procédé et dispositif permettant un test de défaut de réseau

Country Status (2)

Country Link
CN (1) CN101022474A (fr)
WO (1) WO2008110117A1 (fr)

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101022474A (zh) * 2007-03-12 2007-08-22 华为技术有限公司 一种网络故障测试方法和装置
CN101360317A (zh) * 2008-09-25 2009-02-04 中国移动通信集团浙江有限公司 一种用于评估接续时长的测试方法
CN109802855B (zh) * 2018-12-28 2020-08-07 华为技术有限公司 一种故障定位方法及装置
CN112532747B (zh) * 2020-12-23 2023-04-18 北京百度网讯科技有限公司 用于输出信息的方法、装置、设备以及存储介质
CN114785666B (zh) * 2022-06-22 2022-10-04 北京必示科技有限公司 一种网络故障排查方法与系统

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2000013375A (ja) * 1998-06-24 2000-01-14 Toshiba Corp Ｓｔｍ回線を含むａｔｍネットワークシステムの保守方法
US6079036A (en) * 1994-11-17 2000-06-20 Nortel Networks Corporation Call message with traveling log for testing intelligent telecommunications network
EP1253749A2 (fr) * 2001-04-27 2002-10-30 Lucent Technologies Inc. Test à bouclage en retour pour des réseaux hybrides multiprotocole
CN1894895A (zh) * 2004-01-07 2007-01-10 思科技术公司 对外部前缀的转发问题的检测
CN101022474A (zh) * 2007-03-12 2007-08-22 华为技术有限公司 一种网络故障测试方法和装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6079036A (en) * 1994-11-17 2000-06-20 Nortel Networks Corporation Call message with traveling log for testing intelligent telecommunications network
JP2000013375A (ja) * 1998-06-24 2000-01-14 Toshiba Corp Ｓｔｍ回線を含むａｔｍネットワークシステムの保守方法
EP1253749A2 (fr) * 2001-04-27 2002-10-30 Lucent Technologies Inc. Test à bouclage en retour pour des réseaux hybrides multiprotocole
CN1894895A (zh) * 2004-01-07 2007-01-10 思科技术公司 对外部前缀的转发问题的检测
CN101022474A (zh) * 2007-03-12 2007-08-22 华为技术有限公司 一种网络故障测试方法和装置

Also Published As

Publication number Publication date
CN101022474A (zh) 2007-08-22

Similar Documents

Publication Publication Date Title
US9118510B2 (en) Voice over network (VoN)/voice over internet protocol (VoIP) architect having hotline and optional tie line
US8934861B2 (en) Technique for monitoring a call
US9054887B2 (en) Method and apparatus for enabling communications assistance for law enforcement act services
US8520816B2 (en) Method and apparatus for providing end-to-end call completion status
JPH0683315B2 (ja) 通信網監視方法およびシステムおよび通信網要素
JP2008508753A (ja) ハイブリッド通信ネットワークにおいて相関手段を提供する方法および装置
WO2008110117A1 (fr) Procédé et dispositif permettant un test de défaut de réseau
CN110401965B (zh) VoLTE语音质量拨测分析方法及系统
WO2008021316A2 (fr) Procédés, systèmes, et produits-programmes informatiques pour l'élimination d'une situation de renvoi d'appel en épingle dans un réseau de télécommunications
JP5240201B2 (ja) Ｉｐ電話自動試験システム及び方法
US8064452B2 (en) Method and apparatus for routing calls to an alternative endpoint during network disruptions
JP2009200584A (ja) 緊急呼処理装置、方法、プログラム、並びにサーバ装置及びこれを用いた緊急呼処理システム
CN103401882A (zh) Voip网关语音链路备份方法及系统
CN105592514A (zh) 语音电话切换处理方法及装置
WO2005043879A1 (fr) Procede de suivi d'appel sur tout le reseau dans un systeme de commutation
GB2494136A (en) Processing requests in a telecommunications network
CN100417293C (zh) 一种呼叫处理方法
US8699681B2 (en) Method and apparatus for monitoring blocked calls in a communication network
CN103650468B (zh) 通信控制系统和通信控制方法
CA3024447C (fr) Systeme et procede d'analyse de connexion entre un fournisseur de communication et un dispositif distant
JP2002261931A (ja) 回線試験方法および装置およびプログラムおよび記録媒体
JP5826792B2 (ja) 通信装置、プログラム、及び通信システム
Shimokura et al. Specification execution model for detecting feature interactions
WO2015172453A1 (fr) Procédé et dispositif de dépôt de messages basé sur un système de communications mobiles sous ip

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 08715211

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 08715211

Country of ref document: EP

Kind code of ref document: A1