WO2012079430A1 - 一种检测故障链路的方法、装置、节点和系统 - Google Patents

一种检测故障链路的方法、装置、节点和系统 Download PDF

Info

Publication number
WO2012079430A1
WO2012079430A1 PCT/CN2011/081285 CN2011081285W WO2012079430A1 WO 2012079430 A1 WO2012079430 A1 WO 2012079430A1 CN 2011081285 W CN2011081285 W CN 2011081285W WO 2012079430 A1 WO2012079430 A1 WO 2012079430A1
Authority
WO
WIPO (PCT)
Prior art keywords
clock reference
program clock
reference value
nodes
node
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2011/081285
Other languages
English (en)
French (fr)
Inventor
刘淑英
向海洲
陈海斌
杨友庆
郑合文
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
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
Priority to BR112013015217A priority Critical patent/BR112013015217B1/pt
Priority to EP11849700.7A priority patent/EP2654310B1/en
Publication of WO2012079430A1 publication Critical patent/WO2012079430A1/zh
Priority to US13/918,571 priority patent/US9036488B2/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client 
    • H04N21/63—Control signaling related to video distribution between client, server and network components; Network processes for video distribution between server and clients or between remote clients, e.g. transmitting basic layer and enhancement layers over different transmission paths, setting up a peer-to-peer communication via Internet between remote STB's; Communication protocols; Addressing
    • H04N21/643—Communication protocols
    • H04N21/64322—IP
    • 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/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
    • H04L43/0811—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking connectivity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/43—Processing of content or additional data, e.g. demultiplexing additional data from a digital video stream; Elementary client operations, e.g. monitoring of home network or synchronising decoder's clock; Client middleware
    • H04N21/4302—Content synchronisation processes, e.g. decoder synchronisation
    • H04N21/4305—Synchronising client clock from received content stream, e.g. locking decoder clock with encoder clock, extraction of the PCR packets
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client 
    • H04N21/63—Control signaling related to video distribution between client, server and network components; Network processes for video distribution between server and clients or between remote clients, e.g. transmitting basic layer and enhancement layers over different transmission paths, setting up a peer-to-peer communication via Internet between remote STB's; Communication protocols; Addressing
    • H04N21/647—Control signaling between network components and server or clients; Network processes for video distribution between server and clients, e.g. controlling the quality of the video stream, by dropping packets, protecting content from unauthorised alteration within the network, monitoring of network load, bridging between two different networks, e.g. between IP and wireless
    • H04N21/64723—Monitoring of network processes or resources, e.g. monitoring of network load
    • H04N21/6473—Monitoring network processes errors
    • 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/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0823—Errors, e.g. transmission errors
    • H04L43/0829—Packet loss
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/80—Responding to QoS

Definitions

  • the present invention relates to the field of interactive network television technologies, and in particular, to a method, device, node and system for detecting a faulty link.
  • IPTV Internet Protocol Television
  • IPTV Internet Protocol Television
  • IPTV mainly provides video services for users. Therefore, the requirements for the transmission network are very high. Once the transmission network cannot meet the transmission quality requirements of IPTV, it will bring about degradation of quality, such as mosaic, pause, and jump of video images, which seriously affects the end users. QoE (Quality of Experience). Therefore, once there is a problem with the transport network, the IPTV service operator wants to be able to quickly and timely locate which link in the transport network has a problem, that is, to achieve fault location.
  • MDI Media Delivery Index
  • the specific MDI includes two measurement indicators: DF (Delay Factor) and MLR (Media Loss Rate).
  • the DF value indicates the delay and jitter condition of the tested video stream; the MLR value indicates the transmission packet loss rate of the tested video stream.
  • each monitoring node After obtaining the DF value and the MLR value, each monitoring node periodically sends the test value to the management center according to its own timing mechanism.
  • the management center compares the DF value and the MLR value periodically reported by different nodes respectively. The two devices between the two devices and the two devices between the devices.
  • the DF value is a statistical value.
  • the basis of the calculation is the difference between the MR (Media Ratio, the bit rate of the media stream) and the number of bytes received during the current measurement period.
  • the DF value only reflects the bit rate of the media stream. In the case of change, it is impossible to accurately measure whether the video picture of the current terminal decoder has paused or jumped, and for the variable bit rate media stream, the DF value loses the reference value; secondly,
  • the calculation of the MLR requires the use of TS CC (Transport Stream Continuity Counter), but the CC has only 4 bits, and the repetition period is too short, so the actual media packet loss rate cannot be accurately calculated; and since the clocks of the nodes are not necessarily synchronized Even if the clock is synchronized, the starting point of the video stream detection and the timing mechanism reported by each node cannot be consistent. These problems make the management center unable to accurately compare the upstream and downstream nodes to the reported detection result of the report, so it is difficult to accurately solve the problem of the fault location desired by the operator.
  • TS CC Transport Stream Continuity Counter
  • embodiments of the present invention provide a method, apparatus, node, and system for detecting a faulty link.
  • the technical solution is as follows:
  • a method of detecting a faulty link including:
  • the node And receiving, by the node, the statistics of the packets that are received by the preset number of the program clock reference values, where all the nodes start to collect statistics from a unified program clock reference value, where the statistics include the starting program. a clock reference value and a terminating program clock reference value, and a number of messages received at the initial program clock reference value and a number of messages received at the terminating program clock reference value;
  • an apparatus for detecting a faulty link comprising:
  • the receiving module is configured to receive, according to a preset number of statistics reported by the packet carrying the program clock reference value, where all nodes are referenced from a unified program clock.
  • the value starts statistical data, where the statistical data includes a starting program clock reference value and a terminating program clock reference value, and a number of messages received at the initial program clock reference value and when the terminating program clock reference value is Number of received messages;
  • An obtaining module configured to obtain, according to the statistics, the number of packets lost between the upstream and downstream nodes of all the nodes;
  • a determining module configured to determine a faulty link according to the number of lost packets between the upstream and downstream nodes.
  • a node comprising:
  • a first receiving module configured to receive a startup command sent by a device that detects a link failure, and obtain a current program clock reference value
  • a statistic module configured to start data statistics from the current program clock reference value, and send, by the sending module, to send, by the preset number of packets carrying the program clock reference value, the device that detects the link failure Statistic data, the apparatus for detecting a link failure is configured to analyze the statistical data, and determine a faulty link, where the statistical data includes a start program clock reference value and a termination program clock reference value, and at the start The number of messages received when the program clock is referenced and the number of messages received when the program clock reference is terminated.
  • a system for detecting a faulty link comprising: means for detecting a link fault, for receiving statistics of packets reported by all nodes every predetermined number of packets carrying a program clock reference value Data, wherein all nodes start statistical data from a unified program clock reference value, the statistical data including a starting program clock reference value and a terminating program clock reference value, and a reference value of the starting program clock Obtaining the number of packets received and the number of packets received when the program clock reference value is terminated; obtaining, according to the statistical data, the number of packets lost between the upstream and downstream nodes in all the nodes; according to the upstream and downstream nodes The number of lost packets, determine the faulty link;
  • a node configured to receive a startup command sent by the device that detects the link failure, obtain a current program clock reference value, perform data statistics from the current program clock reference value, and perform a preset program clock number
  • the reference value packet sends statistical data to the device that detects the link failure, so that the device that detects the link failure analyzes the statistical data to determine the faulty link.
  • the technical solution provided by the embodiment of the present invention obtains the statistical data of the unified time reference of different network nodes, and obtains the accurate number of lost packets between the upstream and downstream nodes by comparison, thereby Determining the faulty link effectively ensures that the IPT V service provider can quickly and effectively locate the network fault.
  • FIG. 1 is a flowchart of a method for detecting a faulty link according to Embodiment 1 of the present invention
  • FIG. 2 is a flowchart of a method for detecting a faulty link according to Embodiment 2 of the present invention
  • Example 2 provides a schematic diagram of information exchange between a node and a management center.
  • FIG. 4 is a schematic diagram of an apparatus for detecting a faulty link according to Embodiment 3 of the present invention
  • FIG. 5 is another detection provided by Embodiment 3 of the present invention.
  • FIG. 6 is a schematic diagram of a node according to Embodiment 3 of the present invention;
  • FIG. 7 is a schematic diagram of another node provided in Embodiment 3 of the present invention.
  • FIG. 8 is a schematic diagram of a system for detecting a faulty link according to Embodiment 3 of the present invention.
  • DETAILED DESCRIPTION OF THE EMBODIMENTS In order to make the objects, technical solutions, and advantages of the present invention more comprehensible, the embodiments of the present invention will be further described in detail below.
  • PCR Program Clock Reference
  • the frequency and phase of the receiver and transmitter are the same, and the synchronous clock of the transceiver is established.
  • the system is counted by a counter to form a PCR value, and then the PCR value is transmitted to the receiving end along with the data at intervals.
  • the receiving end has a working local clock whose rated frequency is equal to the transmitting end clock.
  • the transmitting end will propose the PCR from the transport stream, and the encoded information of the audio frame and the video frame is inserted into the PES.
  • the receiving end puts the PCR value in the audio frame and the video frame in the buffer, waits for the value in the audio and video of the comparison transmitter to appear, and then compares the result. Control the voltage controlled oscillator (VCXO), and adjust the frequency of the transceiver end to phase lock, so that the sound and image of the transceiver end are completely synchronized.
  • VXO voltage controlled oscillator
  • an embodiment of the present invention provides a method for detecting a faulty link, which includes the following steps: Step 101: Receive statistical data reported by all nodes on a preset number of packets carrying a program clock reference value.
  • all nodes start statistical data from a unified program clock reference value, and the statistical data includes a start program clock reference value and a termination program clock reference value, and a number of packets received at the start of the program clock reference value and The number of packets received when the program clock reference value is terminated.
  • Step 102 Obtain the number of packets lost between the upstream and downstream nodes in all nodes according to the statistics.
  • Step 103 Determine the fault chain according to the number of packets lost between the upstream and downstream nodes. road.
  • the number of packets lost between the upstream and downstream nodes in all the nodes is obtained according to the statistics, including:
  • the number of packets lost between the upstream and downstream nodes in all nodes is calculated according to the number of packets received by all nodes between the same starting program clock reference value and the same terminating program clock reference value.
  • determining the faulty link according to the number of packets lost between the upstream and downstream nodes includes: determining whether the number of packets lost between the upper and lower nodes in all nodes is zero;
  • the link between the upstream and downstream nodes is a faulty link.
  • the number of packets received by all nodes between the same starting program clock reference value and the same terminating program clock reference value is calculated, and the foregoing includes:
  • step of calculating the number of packets received by the all nodes at the same starting program clock reference value to the same terminating program clock reference value is continued;
  • the termination program clock reference value of the node that is inconsistent with the termination program clock reference value of the other node is corrected until the termination program clock reference values reported by all the nodes are consistent, and then the calculation starts to calculate that all the nodes are at the same starting program clock.
  • Reference value to the same termination section The step of receiving the number of packets between the clock reference values.
  • the terminating program clock reference value of the node that is inconsistent with the termination program clock reference value of the other node is corrected, and includes:
  • the execution subject in this embodiment is a device for detecting a faulty link
  • the device for detecting a faulty link may be a management center, which is not specifically limited in this embodiment.
  • the technical solution provided by the embodiment of the present invention obtains the statistical data of the unified time reference of different network nodes, and compares and obtains the number of lost IP packets between the upstream and downstream nodes to determine the faulty link, thereby effectively ensuring the IPTV. Service operators quickly and effectively locate network faults.
  • Example 2
  • an embodiment of the present invention provides a method for detecting a faulty link, including: Step 201: A device that detects a faulty link uniformly sends a start statistics command to all nodes, so that each node participating in the monitoring is unified from one node. The PCR message starts counting statistics.
  • each device participating in the monitoring may be referred to as a node in the network
  • the management center is a device that detects the faulty link
  • the PCR packet is a packet carrying the PCR value.
  • the management center uniformly issues the start-up statistics command, so that all nodes participating in the monitoring have a unified reference standard to ensure the accuracy of statistical data. See Figure 3 for the information exchange between the node and the management center.
  • node A and node B obtain the current unified PCR start value, assuming the initial value is PCR (tO), and Start statistics, counting from this current PCR value.
  • Step 202 All nodes report the statistics of the management center once every fixed number of PCR packets.
  • the interval between the statistics of all the nodes is set in advance according to the requirements.
  • the preset number of PCR packets are used as the reference standard.
  • all nodes report to the management center every predetermined number of PCR packets.
  • the statistical data includes: a starting PCR value and a terminating PCR value, and a number of packets received at the start of the PCR value and a number of packets received when the PCR value is terminated.
  • the node A and the node B interval ⁇ PCR feed back the number of received packets to the management center, and count the start/stop PCR values.
  • the A-PCR initial PCR value (tl) the number of packets received at the initial PCR value is Num (tl, A); the PCR value is terminated (t2), and the number of received packets when the PCR value is terminated is Num.
  • the PCR initiator value of the B node (t2, A), the PCR initiator value of the B node (tl), the number of packets received at the initial PCR value is Num (tl, B), the PCR value is terminated (t3), and the report received when the PCR value is started
  • the number of characters is Num ( t3 , ⁇ ).
  • Step 203 The management center determines whether the termination PCR values in the statistics reported by all the nodes are consistent. If yes, step 205 is performed; otherwise, step 204 is performed.
  • the management center keeps the statistics for a certain period of time, and checks whether the monitoring PCR values reported by the monitoring nodes with the PCR packets are consistent. If they are consistent, the packet counting statistics of different nodes are compared, and the statistics are analyzed. Which device is the number of packets from which PCR value to which PCR value, if it is found that the termination PCR value carried by a node is higher than the termination PCR value of other nodes, it indicates that the node may have lost the PCR packet. At this point, the management center sends a message to the node to correct its APCR.
  • Step 204 The management center corrects the termination PCR values of the nodes that are inconsistent with the termination PCR values of other nodes until the "3 ⁇ 4 termination PCR values are consistent on all nodes.
  • the management center finds that the PCR (t2) and the PCR (t3) are inconsistent, it sends a correction message to the node that is inconsistent with the termination PCR values of other nodes, corrects its APCR, and the node that receives the correction message modifies its statistical PCR report.
  • the number of texts is such that when the node that is inconsistent with other nodes performs statistics again, the number of modified PCR packets is counted and the statistics are reported.
  • the corrected PCR value is PCR (t4), and the value is And the number of packets received at the time is reported to the management center. If the termination PCR value of the node A is inconsistent with the termination PCR value of the other node, the correction message is sent to the node A, and if the termination PCR value of the node B is inconsistent with the termination PCR value of the other node, the correction message is sent to the node B.
  • the management center sends a correction message to node A, so that node A corrects the number of PCR packets at the next interval. After the management center sends a correction message, the node will interval according to the correction message.
  • the number of PCR packets is subtracted from the value of the preset PCR packet, the number of the next interval PCR packets obtained by the node A is 99, so that the management center receives the PCR start value sent by the node A again. If it is 102, the termination value should be 200, so that all the monitoring devices sent by the receiving device have the same termination PCR value. The purpose of this is to ensure that the number of packets participating in the statistics is the same as the initial PCR value and the same termination PCR value to ensure that the clock is synchronized, and the packet statistics are inaccurate due to clock inconsistency. The link is not accurate.
  • the device after the new APCR reports the statistics, the device automatically restores the preset number of PCR packets (A PCR). If the new ⁇ PCR value is 99, the monitoring device automatically recovers the ⁇ PCR value of 100 after correcting the termination PCR values of all nodes to the same.
  • the management center continues to send a message for correction until the same termination PCR value exists in the data reported by each statistical node.
  • the steps 203-204 are optional, and the accuracy of the number of lost packets is further ensured. In the case that the PCR message is not lost, the accuracy of terminating the PCR value may not be checked.
  • Step 205 The management center obtains the number of packets lost between nodes according to the statistics reported by the unified APCR.
  • the management center first calculates the number of packets received by all nodes between the same initial PCR value and the same termination PCR value, and the specific calculation method is: the packet received when the PCR value is terminated. The number of packets received at the initial PCR value is subtracted, and the number of packets received between the same initial PCR value and the same termination PCR value is obtained; after all nodes are obtained at the same start The number of packets received between the PCR value and the same PCR value is calculated, and the number of packets lost between the upstream and downstream devices in the nodes participating in the monitoring is calculated.
  • the specific calculation method is as follows: In the same PCR interval, the upstream node The number of received packets is subtracted from the number of packets received by the downstream node.
  • the number of packets lost between upstream and downstream devices is obtained.
  • the same initial PCR value is PCR ( tl ) and the same termination PCR value is PCR ( t4 ), then the number of packets received by the node between PCR ( tl ) and PCR ( t4 ) is calculated.
  • the specific calculation steps are as follows:
  • PCR(tl) is the statistical collection time point
  • the total number of messages received by nodes A and B are: Num(tl, A), Num(tl, B);
  • PCR(t4) is the next statistical collection time point, the total number of messages received by nodes A and B are: Num(t4, A), Num(t4, B);
  • the number of packets received by the node between the same initial PCR value and the same termination PCR value it may be determined whether the number of packets received by each node in the A PCR is consistent. If they are consistent, it indicates that there is no faulty link. If they are inconsistent, calculate the upstream and downstream of all participating devices according to the number of packets received by all nodes between the same initial PCR value and the same termination PCR value. The number of packets lost between devices to determine the faulty link.
  • Step 206 Determine the faulty link according to the number of packets lost between the upstream and downstream nodes.
  • the management center collects the number of packets received by each node according to the consistent termination PCR value, and the number of packets received by each node. If the packet is not lost, different nodes The packet collection count should be consistent during each reporting period, that is, the number of lost packets between upstream and downstream monitoring devices is zero. If the inconsistency is found, the management center needs to compare it, and further calculate and analyze the number of packets lost between the devices and the devices that drop packets. The number of lost packets between the upstream and downstream nodes is determined to be zero. If not, the The link is a faulty link.
  • three nodes, from the upstream node to the downstream node are A, B, and C respectively; the statistical counts reported in a certain period are 1000, 998, and 900 respectively, and the comparison is obtained through the management center: packet loss between A and B 2, 8 packets are lost between B and C.
  • packet loss between AB and BC which are fault links.
  • the management center finally provides the node with the faulty link to the client. If there is a problem between the nodes A and B, the A and B nodes are provided to the client, so that the client can discover the fault link in time. And take certain solutions to ensure the video quality of the client.
  • the monitoring management center obtains the statistical data of the unified time reference of the different network nodes, and obtains the accurate number of lost packets between the upstream and downstream nodes, thereby ensuring the IPTV service operation.
  • the monitoring management center obtains the statistical data of the unified time reference of the different network nodes, and obtains the accurate number of lost packets between the upstream and downstream nodes, thereby ensuring the IPTV service operation.
  • Quickly and effectively locate the network faults which helps the operation and maintenance engineers to quickly troubleshoot and improve the operation and service quality of the IPTV network.
  • an embodiment of the present invention provides an apparatus for detecting a faulty link, including: a receiving module 301, an obtaining module 302, and a determining module 303.
  • the receiving module 301 is configured to receive a preset number of carried program clock reference values of all nodes.
  • the statistical data reported by the message wherein all nodes start statistical data from a unified program clock reference value, and the statistical data includes a starting program clock reference value and a termination program clock reference value, and when the starting program clock reference value is used.
  • the obtaining module 302 is configured to obtain, according to the statistics, the number of packets lost between the upstream and downstream nodes in all nodes;
  • the determining module 303 is configured to determine a faulty link according to the number of lost packets between the upstream and downstream nodes.
  • the obtaining module 302 includes:
  • the first calculating unit 302a is configured to calculate, according to the number of messages received when starting the program clock reference value and the number of messages received when terminating the program clock reference value, all nodes are at the same starting program clock reference value to the same The number of messages received between the termination program clock reference values;
  • the second calculating unit 302b is configured to calculate the number of packets lost between the upstream and downstream nodes in all nodes according to the number of packets received by all nodes between the same starting program clock reference value and the same terminating program clock reference value. .
  • the determining module 303 is specifically configured to:
  • the link between the upstream and downstream nodes is a faulty link.
  • the obtaining module 302 further includes:
  • the determining unit 302c is configured to determine, before the first calculating unit calculates the number of packets received by all the nodes between the same starting program clock reference value and the same terminating program clock reference value, determining the terminating program clock reference reported by all nodes Whether the values are consistent;
  • step of calculating the number of packets received by the all nodes at the same starting program clock reference value to the same terminating program clock reference value is continued;
  • the termination program clock reference value of the node that is inconsistent with the termination program clock reference value of the other node is corrected until the termination program clock reference values reported by all the nodes are consistent, and then the calculation starts to calculate that all the nodes are at the same starting program clock.
  • the terminating program clock reference value of the node that is inconsistent with the termination program clock reference value of the other node includes:
  • the number of packets with the clock reference value, and the number of packets carrying the program clock reference value at the modified interval is used for data statistics.
  • an embodiment of the present invention provides a node, including: a first receiving module 401, a statistics module 402, and a sending module 403.
  • the first receiving module 401 is configured to receive a startup command sent by the device that detects the link failure, and obtain a current program clock reference value;
  • the statistic module 402 is configured to perform data statistics from the current program clock reference value
  • the sending module 403 is configured to send statistics to the device that detects the link fault every preset number of packets carrying the program clock reference value.
  • the device for detecting the link failure analyzes the statistical data to determine the fault link, and the statistical data includes a start program clock reference value and a termination program clock reference value, and a number of packets received at the start of the program clock reference value. The number of messages received when terminating the program clock reference.
  • the node further includes:
  • the second receiving module 404 is configured to: when the device that detects the link fault determines that the terminated program clock reference value sent by the first sending module is inconsistent with the terminating program clock reference value sent by the other node, the device that detects the link failure is sent by the device. Correction message;
  • the correction module 405 is configured to correct the number of packets carrying the program clock reference value in the interval according to the received correction message, obtain a new number of packets carrying the program clock reference value, and perform data statistics again until the node
  • the reported termination program clock reference value is consistent with the termination program clock reference value of other nodes;
  • the recovery module 406 is configured to restore the number of packets carrying the program clock reference value to a preset number of packets carrying the program clock reference value after the statistics are counted and reported according to the number of the packets carrying the program clock reference value in the new interval. Number of texts.
  • an embodiment of the present invention further provides a system for detecting a faulty link, including: a device 501 for detecting a link failure, and a node 502.
  • the device 501 for detecting a link fault is configured to receive statistics reported by all nodes on a preset number of packets carrying a program clock reference value, where all nodes start statistics from a unified program clock reference value, and statistics are collected.
  • the data includes a starting program clock reference value and a terminating program clock reference value, and a number of messages received when starting the program clock reference value and a number of messages received when the program clock reference value is terminated; according to statistical data, Obtaining the number of packets lost between the upstream and downstream nodes in all nodes; determining the faulty link according to the number of packets lost between the upstream and downstream nodes;
  • the node 502 is configured to receive a startup command sent by a device that detects a link failure, obtain a current program clock reference value, and perform data statistics from a current program clock reference value; and preset a number of presets that carry a program clock reference value.
  • the packet sends statistics to the device that detects the link failure, so that the device that detect
  • the device that detects the faulty link obtains the statistical data of the unified time reference of the different network nodes, and compares and obtains the number of packets lost between the upstream and downstream nodes, thereby ensuring the number of packets lost between the upstream and downstream nodes.
  • the IPTV service provider quickly and effectively locates network faults, which facilitates rapid troubleshooting of operation and maintenance engineers and improves IPTV network operation and maintenance and service quality.
  • the device, the node, and the system provided in this embodiment may be the same as the method embodiment.
  • All or part of the above technical solutions provided by the embodiments of the present invention may be completed by hardware related to program instructions, and the program may be stored in a readable storage medium, and the storage medium includes: a ROM, a RAM, a magnetic disk or an optical disk. And other media that can store program code.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Computer Security & Cryptography (AREA)
  • Environmental & Geological Engineering (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Description

一种检测故障链路的方法、 装置、 节点和系统
本申请要求于 2010年 12月 15日提交中国专利局、 申请号为 201010601481.3、 发明名称为 "一种检测故障链路的方法、 装置、 节点和系 统" 的中国专利申请的优先权， 其全部内容通过引用结合在本申请中。 技术领域
本发明涉及交互式网络电视技术领域， 特别涉及一种检测故障链路的 方法、 装置、 节点和系统。
背景技术
IPTV ( Internet Protocol Television , 交互式网络电视）， 是一种利用宽带 IP网络，向家庭用户提供包括数字电视在内的多种交互式服务的技术。 IPTV 主要为用户提供视频业务， 所以对于传送网络的要求非常高， 一旦传送网 络不能满足 IPTV的传送质量要求， 就会带来视频画面的马赛克、 停顿、 跳 跃等质量下降现象， 严重影响终端用户的 QoE ( Quality of Experience, 质 量体验）。 因此一旦传送网络出现问题， IPTV 业务运营商希望能够快速及 时定位到传送网络中哪个链路出现问题， 即实现故障定位。
现有 IPTV网络中， 通过 MDI ( Media Delivery Index, 媒体传输质量指 标）实现对网络故障的检测。 具体的 MDI包括了两个测量指标： DF ( Delay Factor, 延迟因素）和 MLR ( Media Loss Rate, 媒体丟包速率）。 其中， DF 值表明被测试视频流的延迟和抖动状况； MLR值表明被测试视频流的传输 丟包速率。 各监测节点在获得 DF值和 MLR值后， 根据自身的定时机制周 期性的将该测试值发送给管理中心， 管理中心对不同节点周期性上报的 DF 值和 MLR值分别进行比较， 可以得出抖动发生在哪两台设备之间、丟包发 生在哪两台设备之间。 比如上下游的值分别为 DF1 , MLR1 , DF2, MLR2, 如果 DFl=5ms, MLR1=0; DF2= 40ms, MLR2=5; 则说明了在上游设备视 频的抖动（DF )很小， 但到了下游设备抖动（DF ) 比较大， 说明在这两台 设备之间产生了抖动； 理想的 IP视频流传输要求 MLR数值为零， 上游设 备 MLR1=0 , 说明这个周期内没有丟包， 而下游设备 MLR2=5 , 说明下游 设备在该周期内丟了包（每秒 5个 TS ( Transport Stream, 传输流））， 则该 上下游节点之间的链路就是故障链路。
在对现有技术进行分析后， 发明人发现现有技术至少具有如下缺点：
DF值是一个统计意义上的值， 计算的基础是 MR(Media Ratio, 媒体流的码 率)以及当前测量时间段内所接收的字节数之差， DF值仅仅反映了媒体流的 码率变化情况， 无法准确衡量当前终端解码器的视频画面是否发生停顿或 跳跃， 并且对于可变比特率媒体流， 则 DF值更是失去了参考价值； 其次，
MLR的计算需要用到 TS CC ( Transport Stream Continuity Counter, 传输流 连续计数）， 但 CC只有 4比特， 重复周期太短， 因此无法准确计算实际媒 体丟包率； 并且由于各节点的时钟不一定同步， 即使时钟同步， 各节点对 视频流检测的起始点、 上报的定时机制等也不能达到一致。 以上这些问题 使得管理中心对上报的检测计算结果无法进行上下游节点间的精确比较， 因此难以精确的解决运营商希望的故障定位的问题。
发明内容 为了更加精确的找到故障链路， 本发明实施例提供了一种检测故障链 路的方法、 装置、 节点和系统。 所述技术方案如下：
一方面， 提供了一种检测故障链路的方法， 包括：
接收所有节点每隔预设数量的携带节目时钟参考值的报文上报的统计 数据， 其中， 所述所有节点均从一个统一的节目时钟参考值开始统计数据， 所述统计数据中包括起始节目时钟参考值和终止节目时钟参考值、 以及在 所述起始节目时钟参考值时接收的报文数和在所述终止节目时钟参考值时 接收的报文数；
根据所述统计数据， 获取所述所有节点中上下游节点间丟失的报文数； 根据所述上下游节点间丟失的报文数， 确定故障链路。
一方面， 提供了一种检测故障链路的装置， 所述装置包括：
接收模块， 用于接收所有节点每隔预设数量的携带节目时钟参考值的 报文上报的统计数据， 其中， 所述所有节点均从一个统一的节目时钟参考 值开始统计数据， 所述统计数据中包括起始节目时钟参考值和终止节目时 钟参考值、 以及在所述起始节目时钟参考值时接收的报文数和在所述终止 节目时钟参考值时接收的报文数；
获取模块， 用于根据所述统计数据， 获取所述所有节点中上下游节点 间丟失的报文数；
确定模块， 用于根据所述上下游节点间丟失的报文数， 确定故障链路。 另一方面， 提供了一种节点， 所述节点包括：
第一接收模块， 用于接收检测链路故障的装置下发的启动指令， 并获 取当前的节目时钟参考值；
统计模块， 用于从所述当前的节目时钟参考值开始进行数据统计； 发送模块， 用于每隔预设数量的携带节目时钟参考值的报文向所述检 测链路故障的装置发送所述统计数据， 使所述检测链路故障的装置对所述 统计数据进行分析， 确定故障链路， 所述统计数据中包括起始节目时钟参 考值和终止节目时钟参考值、 以及在所述起始节目时钟参考值时接收的报 文数和在所述终止节目时钟参考值时接收的报文数。
另一方面， 还提供了一种检测故障链路的系统， 所述系统包括： 检测链路故障的装置， 用于接收所有节点每隔预设数量的携带节目时 钟参考值的报文上报的统计数据， 其中， 所述所有节点均从一个统一的节 目时钟参考值开始统计数据， 所述统计数据中包括起始节目时钟参考值和 终止节目时钟参考值、 以及在所述起始节目时钟参考值时接收的报文数和 在所述终止节目时钟参考值时接收的报文数； 根据所述统计数据， 获取所 述所有节点中上下游节点间丟失的报文数； 根据所述上下游节点间丟失的 报文数， 确定故障链路；
节点， 用于接收所述检测链路故障的装置下发的启动指令， 获取当前 的节目时钟参考值； 从所述当前的节目时钟参考值开始进行数据统计； 每 隔预设数量的携带节目时钟参考值的报文向所述检测链路故障的装置发送 统计数据， 使所述检测链路故障的装置对所述统计数据进行分析， 确定故 障链路。
本发明实施例提供的技术方案， 通过获取不同网络节点的统一时间基 准的统计数据， 并通过比较得出准确的上下游节点间丟失的报文数， 从而 确定故障链路 , 有效地保证了 IPT V业务运营商快速有效地进行网络故障的 定位。 附图说明 为了更清楚地说明本发明实施例或现有技术中的技术方案， 下面将对 实施例或现有技术描述中所需要使用的附图作简单地介绍， 显而易见地， 下面描述中的附图仅仅是本发明的一些实施例， 对于本领域普通技术人员 来讲， 在不付出创造性劳动性的前提下， 还可以根据这些附图获得其他的 附图。
图 1是本发明实施例 1提供了一种检测故障链路的方法的流程图； 图 2是本发明实施例 2提供了一种检测故障链路的方法的流程图； 图 3是本发明实施例 2提供了一种节点与管理中心的信息交互示意图； 图 4是本发明实施例 3提供的一种检测故障链路的装置的示意图； 图 5是本发明实施例 3提供的另一种检测故障链路的装置的示意图； 图 6是本发明实施例 3提供的一种节点的示意图；
图 7是本发明实施例 3提供的另一种节点的示意图；
图 8是本发明实施例 3提供的一种检测故障链路的系统的示意图。 具体实施方式 为使本发明的目的、 技术方案和优点更加清楚， 下面将结合附图对本 发明实施方式作进一步地详细描述。
在介绍本发明提供的检测故障链路的方法之前， 首先对本发明的基础 知识进行简要的介绍：
PCR( Program Clock Reference,节目时钟参考），是一个实时传输系统， 为了保证收发端的正常工作， 接收端与发射端的频率和相位一致， 而建立 的收发端的同步时钟。 具体的， 在发射端， 利用计数器对系统进行计数， 形成 PCR值， 然后每隔一段时间将 PCR值随数据一起传送给接收端。接收 端有一个正在工作的本地时钟， 其额定频率与发射端时钟相等， 同样也有 一个计数器对接收端本地时钟计数形成一个本地时钟参考。 这时发射端会 将 PCR 从传送流中提出来，与音频帧、 视频帧的编码信息插入 PES ( Packetised Elementary Streams, 带有包头的基本码流） 包中， 接收端将音 频帧、 视频帧中的 PCR值放在緩存器中， 等待比较发射端的音视频中的值 出现， 然后用比较的结果控制压控振荡器 (VCXO), 通过调整使收发端的频 率锁相， 从而实现收发端声音和图像完全同步。
实施例 1
参见图 1 , 本发明实施例提供了一种检测故障链路的方法， 包括： 步骤 101 :接收所有节点每隔预设数量的携带节目时钟参考值的报文上 报的统计数据。
其中， 所有节点均从一个统一的节目时钟参考值开始统计数据， 统计 数据中包括起始节目时钟参考值和终止节目时钟参考值、 以及在起始节目 时钟参考值时接收的报文数和在终止节目时钟参考值时接收的报文数； 步骤 102:根据统计数据，获取所有节点中上下游节点间丟失的报文数； 步骤 103: 根据上下游节点间丟失的报文数， 确定故障链路。
其中， 根据所述统计数据， 获取所有节点中上下游节点间丟失的报文 数， 包括：
根据在起始节目时钟参考值时接收的报文数和在终止节目时钟参考值 时接收的报文数， 计算所有节点在相同的起始节目时钟参考值到相同的终 止节目时钟参考值之间收到的报文数；
根据所有节点在相同的起始节目时钟参考值到相同的终止节目时钟参 考值之间收到的报文数， 计算所述所有节点中上下游节点间丟失的报文数。
本实施例中， 根据上下游节点间丟失的报文数， 确定故障链路， 包括： 判断所有节点中上下节点间丟失的报文数是否为零；
如果不为零， 则上下游节点之间的链路为故障链路。
进一步地， 本实施例中， 计算所有节点在相同的起始节目时钟参考值 到相同的终止节目时钟参考值之间收到的报文数， 之前还包括：
判断所有节点上报的终止节目时钟参考值是否一致；
如果一致， 则继续执行计算所述所有节点在相同的起始节目时钟参考 值到相同的终止节目时钟参考值之间收到的报文数的步骤；
如果不一致， 校正与其它节点的终止节目时钟参考值不一致的节点的 终止节目时钟参考值， 直到所有节点上报的终止节目时钟参考值一致， 再 继续执行计算所述所有节点在相同的起始节目时钟参考值到相同的终止节 目时钟参考值之间收到的报文数的步骤。
本实施例中， 校正与其它节点的终止节目时钟参考值不一致的节点的 终止节目时钟参考值， 包括：
向与其它节点的终止节目时钟参考值不一致的节点发送校正消息， 使 与其它节点的终止节目时钟参考值不一致的节点修改自身间隔的携带节目 时钟参考值的报文数， 并以修改后的节目时钟参考间隔数进行数据统计。
其中， 本实施例中的执行主语为检测故障链路的装置， 该检测故障链 路的装置可以是管理中心， 本实施例对此不做具体限定。
本发明实施例提供的技术方案， 通过获取不同网络节点的统一时间基 准的统计数据， 并通过比较得出准确的上下游节点间丟失的 IP包数， 从而 确定故障链路，有效地保证了 IPTV业务运营商快速有效地进行网络故障的 定位。 实施例 2
参见图 2, 本发明实施例提供了一种检测故障链路的方法， 包括： 步骤 201 : 检测故障链路的装置向所有节点统一下发启动统计指令，使 参与监控的每个节点从一个统一的 PCR报文开始统计计数。
本实施例中， 每个参与监测的设备都可以称作网络中的一个节点， 管 理中心为检测故障链路的装置， PCR报文就是携带 PCR值的报文。 其中， 管理中心统一下发启动统计指令， 使所有参与监测的节点有统一的参考标 准， 确保统计数据的准确性。 参见图 3 所示的节点与管理中心的信息交示 意图， 在管理中心下发启动统计指令后， 节点 A和节点 B获取当前统一的 PCR起始值， 假设起始值为 PCR ( tO ), 并启动统计， 从这个当前的 PCR 值开始计数。
步骤 202: 所有节点均每隔固定数量的 PCR报文上报管理中心一次统 计数据。
本实施例中， 根据需求， 预先设置所有节点上报统计数据的间隔时间， 为了保证时间的统一性和准确性，以间隔预设数量的 PCR报文为参考标准。 间隔的 PCR报文数量用△ PCR表示， △ PCR =n个 PCR报文， 其中 n可以 是 100, 150等， 本实施例在此不做具体限定。
本实施例中， 所有节点每隔预设数量的 PCR报文向管理中心上报一次 统计数据， 其中， 统计数据包括， 起始 PCR值和终止 PCR值、 以及在起始 PCR值时接收的报文数和在终止 PCR值时接收的报文数。 参见图 3 , 节点 A和节点 B间隔△ PCR向管理中心反馈一次接收报文数， 并统计起始 /终止 PCR值。 如， A节点 PCR起始 PCR值（ tl ), 在起始 PCR值时接收的报文 数为 Num ( tl , A ); 终止 PCR值（t2 ), 终止 PCR值时接收的报文数为 Num(t2,A), B节点 PCR起始 PCR值（ tl ), 起始 PCR值时接收的报文数为 Num ( tl , B ), 终止 PCR值（ t3 ),起始 PCR值时接收的报文数为 Num ( t3 , Β )。
步骤 203: 管理中心判断所有节点上报的统计数据中的终止 PCR值是 否一致， 如果一致， 则执行步骤 205; 否则执行步骤 204。
其中，如果丟失了带有 PCR值的 PCR报文，则在统计预设间隔的 PCR 数时， 就会出现终止 P CR值不一致的问题。 本实施例中， 管理中心保留一 定时间的这些统计数据， 并检查各个监测节点上报带有 PCR报文中的终止 PCR值是否一致， 如果一致， 则比较不同节点的收包统计计数， 并分析出 哪台设备在哪个 PCR值到哪个 PCR值之间的丟包数量，如果发现某个节点 上报统计计数携带的终止 PCR值大于其他节点的终止 PCR值，则说明该节 点可能丟失了 PCR报文， 此时管理中心向该节点发消息校正其 APCR。
步骤 204: 管理中心校正与其它节点的终止 PCR值不一致的节点的终 止 PCR值， 直到所有节点上"¾的终止 PCR值一致。
本实施例中， 如果接收到的终止 PCR值不统一， 先对该监测节点接收 的 PCR值进行校正， 直到各监测节点上报的统计数据中存在相同的终止 PCR值。 参见图 3 , 如果管理中心发现 PCR ( t2 )和 PCR ( t3 )不一致， 则 向与其它节点的终止 PCR值不一致的节点发校正消息， 校正其 APCR, 收 到校正消息的节点修改其统计 PCR报文的数量， 使与其它节点不一致的节 点再次进行数据统计时， 以修改后的 PCR报文间隔数进行统计， 并上报统 计数据， 如校正后的终止 PCR值为 PCR ( t4 ) , 将该值和在该值时接收的报 文数上报给管理中心。 其中， 如果节点 A的终止 PCR值与其它节点的终止 PCR值不一致， 则向节点 A发送校正消息， 如果节点 B的终止 PCR值与 其它节点的终止 PCR值不一致， 则向节点 B发送校正消息。 如， 预设的间 隔 PCR报文数量为 100 , 起始 PCR值为 1 , 则终止 PCR值应该为 100 , 但 节点 A的终止 PCR值为 101 , 其它节点的终止 PCR值为 100, 则说明节点 A中丟了一个 PCR报文， 那么管理中心向节点 A下发校正消息， 使节点 A 修正下一次间隔的 PCR报文数量， 管理中心每次发校正消息后， 节点根据 该校正消息将间隔的 PCR报文数量在预设的 PCR报文的基础上减去一个数 值，则上述节点 A得到的下次间隔 PCR报文的数量为 99,这样管理中心再 次收到节点 A发送的 PCR起始值是 102, 终止值应该为 200, 从而保证接 收到的所有监测设备发送的终止 PCR值相同。 这样做的目的是， 保证其参 与统计的报文数，有相同的起始 PCR值和相同的终止 PCR值，保证时钟的 同步， 避免由于时钟不一致导致报文统计结果不准确， 最终使故障检测的 链路不准确。
本实施例中， 按照新的 APCR上报统计计数以后， 设备自动恢复预设 的 PCR报文数量（ A PCR )。 如上述新的 Δ PCR值为 99, 则将所有节点的 终止 PCR值修正到一致以后， 该监测设备自动恢复 Δ PCR值为 100。
本实施例中， 如果校正一次以后仍然存在某一台设备的终止 PCR值大 于其他设备的 PCR值， 则管理中心继续发消息进行校正， 直到各统计节点 上报的数据中存在相同的终止 PCR值。 本实施例中， 步骤 203-204是可选 地， 进一步保证丟包数量的准确性， 在能保证 PCR报文不丟失的情况下， 也可以不用检查终止 PCR值的准确性。
步骤 205: 管理中心根据统一的 APCR上报的统计数据，得到节点间丟 失的报文数。
本实施例中， 管理中心先计算所有节点在相同的起始 PCR值到相同的 终止 PCR值之间收到的报文数， 具体的计算方法为： 将在终止的 PCR值时 接收的报文数减去在起始的 PCR值时接收的报文数， 得到的就是在相同的 起始 PCR值到相同的终止 PCR值之间收到的报文数；在得到所有节点在相 同的起始 PCR值到相同的终止 PCR值之间收到的报文数，再计算所有参与 监测的节点中上下游设备间丟失的报文数， 具体的计算方法为： 在相同的 PCR 间隔内， 上游节点收到的报文数减去下游节点收到的报文数， 得到上 下游设备间丟失的报文数。 如图 3中相同的起始 PCR值为 PCR ( tl ) , 相同 的终止 PCR值为 PCR ( t4 ), 则计算节点在 PCR ( tl )到 PCR ( t4 )之间接 收到的报文数。 具体计算步骤如下：
( 1 )假设 PCR(tl)为统计釆集时间点， 节点 A和 B收到的总报文数量 分别为： Num(tl ,A) , Num(tl ,B); ( 2 )假设 PCR(t4)为下一个统计釆集时间点， 节点 A和 B收到的总报 文数量分别为： Num(t4,A) , Num(t4,B)；
( 3 ) PCR ( tl )到 PCR ( t4 )之间， 节点 A和 B间网络丟失报文数为： Diff = Num(t4,A) - Num(tl,A) -[ Num(t4,B) - Num(tl,B)]。
其中，可选地，在计算所有节点在相同的起始 PCR值到相同的终止 PCR 值之间收到的报文数之后， 可以先判断各节点在 A PCR 内收到的报文数是 否一致， 如果一致， 则表明没有故障链路， 如果不一致， 则再根据所有节 点在相同的起始 PCR值到相同的终止 PCR值之间收到的报文数，计算所有 参与监测的设备中上下游设备间丟失的报文数， 以确定故障链路。
步骤 206: 根据上下游节点间丟失的报文数， 确定故障链路。
本实施例中， 管理中心才艮据一致的终止 PCR值来统计与上次一致的起 始 PCR值之间， 各节点各自收到多少报文， 如果在报文不丟失的情况下， 不同节点在每个上报周期内收包计数应该是一致的， 即上下游监测设备之 间的丟包数量为零。 如果发现不一致， 需要管理中心比较一下， 进一步计 算分析得出设备之间丟包数量及丟包的设备， 其中， 判断上下游节点间的 丟包数量是否为零， 如果不为零， 则表明该链路为故障链路。 比如三个节 点， 从上游节点到下游节点分别为 A, B , C; 某个周期内上报的统计计数 分别为 1000 , 998 , 900 , 则通过管理中心比较得出： A和 B之间丟包 2个， B和 C之间丟包 8个。说明 AB之间， BC之间都存在丟包，都是故障链路。
本实施例中，管理中心最终将出现故障链路的节点提供给客户端，如 A、 B节点间出现问题， 则将 A、 B节点提供给客户端， 使客户端能及时发现故 障链路， 并釆取一定的解决措施， 最终保证用户端的视频质量。
本发明实施例提供的技术方案的有益效果是： 监控管理中心获取不同 网络节点的统一时间基准的统计数据， 并通过比较得出准确的上下游节点 间丟失的报文数，从而保证 IPTV业务运营商快速有效地进行网络故障的定 位， 有助于运维工程师的快速故障排除， 提高 IPTV网络运维及服务质量。 实施例 3
参见图 4 , 本发明实施例提供了一种检测故障链路的装置， 包括： 接收 模块 301、 获取模块 302、 确定模块 303。
接收模块 301 ,用于接收所有节点每隔预设数量的携带节目时钟参考值 报文上报的统计数据， 其中， 所有节点均从一个统一的节目时钟参考值开 始统计数据， 统计数据中包括起始节目时钟参考值和终止节目时钟参考值、 以及在起始节目时钟参考值时接收的报文数和在终止节目时钟参考值时接 收的报文数；
获取模块 302 , 用于根据统计数据， 获取所有节点中上下游节点间丟失 的报文数；
确定模块 303 , 用于根据上下游节点间丟失的报文数， 确定故障链路。 参见图 5 , 本实施例中， 获取模块 302 , 包括：
第一计算单元 302a, 用于根据在起始节目时钟参考值时接收的报文数 和在终止节目时钟参考值时接收的报文数， 计算所有节点在相同的起始节 目时钟参考值到相同的终止节目时钟参考值之间收到的报文数；
第二计算单元 302b, 用于根据所有节点在相同的起始节目时钟参考值 到相同的终止节目时钟参考值之间收到的报文数， 计算所有节点中上下游 节点间丟失的报文数。
其中， 确定模块 303 , 具体用于：
判断所有节点中上下节点丟失的报文数是否为零；
如果不为零， 则上下游节点之间的链路为故障链路。
参见图 5 , 本实施例中， 获取模块 302还包括：
判断单元 302c, 用于在第一计算单元计算所有节点在相同的起始节目 时钟参考值到相同的终止节目时钟参考值之间收到的报文数之前， 判断所 有节点上报的终止节目时钟参考值是否一致；
如果一致， 则继续执行计算所述所有节点在相同的起始节目时钟参考 值到相同的终止节目时钟参考值之间收到的报文数的步骤；
如果不一致， 校正与其它节点的终止节目时钟参考值不一致的节点的 终止节目时钟参考值， 直到所有节点上报的终止节目时钟参考值一致， 再 继续执行计算所述所有节点在相同的起始节目时钟参考值到相同的终止节 目时钟参考值之间收到的报文数的步骤。
其中， 校正与其它节点的终止节目时钟参考值不一致的节点的终止节 目时钟参考值， 包括：
向与其它节点的终止节目时钟参考值不一致的节点发送校正消息， 使 与其它节点的终止节目时钟参考值不一致的节点修改自身间隔的携带节目 时钟参考值的报文数， 并以修改后的间隔携带节目时钟参考值的报文数进 行数据统计。
参见图 6, 本发明实施例提供了一种节点， 包括： 第一接收模块 401、 统计模块 402、 发送模块 403。
第一接收模块 401 , 用于接收检测链路故障的装置下发的启动指令， 获 取当前的节目时钟参考值；
统计模块 402 , 用于从当前的节目时钟参考值值开始进行数据统计； 发送模块 403 ,用于每隔预设数量的携带节目时钟参考值的报文向检测 链路故障的装置发送统计数据， 使检测链路故障的装置对统计数据进行分 析， 确定故障链路， 统计数据中包括起始节目时钟参考值和终止节目时钟 参考值、 以及在起始节目时钟参考值时接收的报文数和在终止节目时钟参 考值时接收的报文数。
参见图 7 , 本实施例中， 节点还包括：
第二接收模块 404 ,用于当检测链路故障的装置判断出第一发送模块发 送的终止的节目时钟参考值与其它节点发送的终止节目时钟参考值不一致 时， 接收检测链路故障的装置发送的校正消息；
校正模块 405 , 用于根据接收到的校正消息，修正自身间隔的携带节目 时钟参考值的报文数量， 得到新的间隔携带节目时钟参考值的报文数量， 并再次进行数据统计， 直到该节点上报的终止节目时钟参考值与其它节点 的终止节目时钟参考值一致；
恢复模块 406 ,用于根据新的间隔携带节目时钟参考值的报文数量进行 统计计数并上报后， 将间隔携带节目时钟参考值的报文数量恢复为预设数 量的携带节目时钟参考值的报文数。
参见图 8, 本发明实施例还提供了一种检测故障链路的系统， 包括： 检 测链路故障的装置 501、 节点 502。
检测链路故障的装置 501 ,用于接收所有节点每隔预设数量的携带节目 时钟参考值的报文上报的统计数据， 其中， 所有节点均从一个统一的节目 时钟参考值开始统计数据， 统计数据中包括起始节目时钟参考值和终止节 目时钟参考值、 以及在起始节目时钟参考值时接收的报文数和在所述终止 节目时钟参考值时接收的报文数； 根据统计数据， 获取所有节点中上下游 节点间丟失的报文数； 根据上下游节点间丟失的报文数， 确定故障链路； 节点 502, 用于接收检测链路故障的装置下发的启动指令， 获取当前的 节目时钟参考值； 从当前的节目时钟参考值开始进行数据统计； 每隔预设 数量的携带节目时钟参考值的报文向检测链路故障的装置发送统计数据， 使检测链路故障的装置对统计数据进行分析， 确定故障链路。
本发明实施例提供的技术方案的有益效果是： 检测故障链路的装置获 取不同网络节点的统一时间基准的统计数据， 并通过比较得出准确的上下 游节点间丟失的报文数，从而保证 IPTV业务运营商快速有效地进行网络故 障的定位， 有助于运维工程师的快速故障排除， 提高 IPTV网络运维及服务 质量。
本实施例提供的装置、 节点， 系统， 具体可以， 与方法实施例属于同 一构思， 其具体实现过程详见方法实施例， 这里不再赘述。
本发明实施例提供的上述技术方案的全部或部分可以通过程序指令相 关的硬件来完成， 所述程序可以存储在可读取的存储介质中， 该存储介质 包括： ROM、 RAM, 磁碟或者光盘等各种可以存储程序代码的介质。
以上所述仅为本发明的较佳实施例， 并不用以限制本发明， 凡在本发 明的精神和原则之内， 所作的任何修改、 等同替换、 改进等， 均应包含在 本发明的保护范围之内。

Claims

权利要求
1、 一种检测故障链路的方法， 其特征在于， 所述方法包括：
接收所有节点每隔预设数量的携带节目时钟参考值的报文上报的统计 数据， 其中， 所述所有节点均从一个统一的节目时钟参考值开始统计数据， 所述统计数据中包括起始节目时钟参考值和终止节目时钟参考值、 以及在 所述起始节目时钟参考值时接收的报文数和在所述终止节目时钟参考值时 接收的报文数；
根据所述统计数据， 获取所述所有节点中上下游节点间丟失的报文数； 根据所述上下游节点间丟失的报文数， 确定故障链路。
2、根据权利要求 1所述的方法， 其特征在于， 所述根据所述统计数据， 获取所述所有节点中上下游节点间丟失的报文数， 包括：
根据在起始节目时钟参考值时接收的报文数和在终止节目时钟参考值 时接收的报文数， 计算所述所有节点在相同的起始节目时钟参考值到相同 的终止节目时钟参考值之间收到的报文数；
根据所述所有节点在相同的起始节目时钟参考值到相同的终止节目时 钟参考值之间收到的报文数， 计算所述所有节点中上下游节点间丟失的报 文数。
3、 根据权利要求 1所述的方法， 其特征在于， 所述根据所述上下游节 点间丟失的报文数， 确定故障链路， 包括：
判断所述所有节点中上下节点间丟失的报文数是否为零；
如果不为零， 则所述上下游节点之间的链路为故障链路。
4、 根据权利要求 2所述的方法， 其特征在于， 所述计算所述所有节点 在相同的起始节目时钟参考值到相同的终止节目时钟参考值之间收到的报 文数， 之前还包括：
判断所述所有节点上报的终止节目时钟参考值是否一致；
如果一致， 则继续执行所述计算所述所有节点在相同的起始节目时钟 参考值到相同的终止节目时钟参考值之间收到的报文数的步骤； 如果不一致， 校正所述与其它节点的终止节目时钟参考值不一致的节 点的终止节目时钟参考值， 直到所述所有节点上报的终止节目时钟参考值 一致， 再继续执行所述计算所述所有节点在相同的起始节目时钟参考值到 相同的终止节目时钟参考值之间收到的报文数的步骤。
5、 根据权利要求 4所述的方法， 其特征在于， 所述校正所述与其它节 点的终止节目时钟参考值不一致的节点的终止节目时钟参考值， 包括： 向与其它节点的终止节目时钟参考值不一致的节点发送校正消息， 使 所述与其它节点的终止节目时钟参考值不一致的节点修改自身间隔携带节 目时钟参考值的报文数， 并以所述修改后的间隔携带节目时钟参考值的报 文数进行数据统计。
6、 一种检测故障链路的装置， 其特征在于， 所述装置包括：
接收模块， 用于接收所有节点每隔预设数量的携带节目时钟参考值的 报文上报的统计数据， 其中， 所述所有节点均从一个统一的节目时钟参考 值开始统计数据， 所述统计数据中包括起始节目时钟参考值和终止节目时 钟参考值、 以及在所述起始节目时钟参考值时接收的报文数和在所述终止 节目时钟参考值时接收的报文数；
获取模块， 用于根据所述统计数据， 获取所述所有节点中上下游节点 间丟失的报文数；
确定模块， 用于根据所述上下游节点间丟失的报文数， 确定故障链路。
7、 根据权利要求 6所述的装置， 其特征在于， 所述获取模块， 包括： 第一计算单元， 用于根据在起始节目时钟参考值时接收的报文数和在 终止节目时钟参考值时接收的报文数， 计算所述所有节点在相同的起始节 目时钟参考值到相同的终止节目时钟参考值之间收到的报文数；
第二计算单元， 用于根据所述所有节点在相同的起始节目时钟参考值 到相同的终止节目时钟参考值之间收到的报文数， 计算所述所有节点中上 下游节点间丟失的报文数。
8、 根据权利要求 6所述的装置， 其特征在于， 所述确定模块， 具体用 于：
判断所述所有节点中上下节点间丟失的报文数是否为零；
如果不为零， 则所述上下游节点之间的链路为故障链路。
9、 根据权利要求 7所述的装置， 其特征在于， 所述获取模块还包括： 判断单元， 用于在所述第一计算单元计算所述所有节点在相同的起始 节目时钟参考值到相同的终止节目时钟参考值之间收到的报文数之前， 判 断所述所有节点上报的终止节目时钟参考值是否一致；
如果一致， 则继续执行所述计算所述所有节点在相同的起始节目时钟 参考值到相同的终止节目时钟参考值之间收到的报文数的步骤；
如果不一致， 校正所述与其它节点的终止节目时钟参考值不一致的节 点的终止节目时钟参考值， 直到所述所有节点上报的终止节目时钟参考值 一致， 再继续执行所述计算所述所有节点在相同的起始节目时钟参考值到 相同的终止节目时钟参考值之间收到的报文数的步骤。
10、 根据权利要求 9所述的装置， 其特征在于， 所述校正所述与其它 节点的终止节目时钟参考值不一致的节点的终止节目时钟参考值， 包括： 向与其它节点的终止节目时钟参考值不一致的节点发送校正消息， 使 所述与其它节点的终止节目时钟参考值不一致的节点修改自身间隔携带节 目时钟参考值的报文数， 并以所述修改后的间隔携带节目时钟参考值的报 文数进行数据统计。
11、 一种节点， 其特征在于， 所述节点包括：
第一接收模块， 用于接收检测链路故障的装置下发的启动指令， 并获 取当前的节目时钟参考值；
统计模块， 用于从所述当前的节目时钟参考值开始进行数据统计； 发送模块， 用于每隔预设数量的携带节目时钟参考值的报文向所述检 测链路故障的装置发送所述统计数据， 使所述检测链路故障的装置对所述 统计数据进行分析， 确定故障链路， 所述统计数据中包括起始节目时钟参 考值和终止节目时钟参考值、 以及在所述起始节目时钟参考值时接收的报 文数和在所述终止节目时钟参考值时接收的报文数。
12、 根据权利要求 11所述的节点， 其特征在于， 所述节点还包括： 第二接收模块， 用于当所述检测链路故障的装置判断出所述第一发送 考值不一致时， 接收所述检测链路故障的装置发送的校正消息；
校正模块， 用于根据所述接收到的校正消息， 修正自身间隔的携带节 目时钟参考值的报文数量， 得到新的间隔携带节目时钟参考值的报文数量， 并再次进行数据统计， 直到所述节点上报的终止节目时钟参考值与所述其 它节点的终止节目时钟参考值一致；
恢复模块， 用于根据所述新的间隔携带节目时钟参考值的报文数量进 行统计计数并上报后， 将间隔携带节目时钟参考值的报文数量恢复为所述 预设数量的携带节目时钟参考值的报文数。
13、 一种检测故障链路的系统， 其特征在于， 所述系统包括： 检测链路故障的装置， 用于接收所有节点每隔预设数量的携带节目时 钟参考值的报文上报的统计数据， 其中， 所述所有节点均从一个统一的节 目时钟参考值开始统计数据， 所述统计数据中包括起始节目时钟参考值和 终止节目时钟参考值、 以及在所述起始节目时钟参考值时接收的报文数和 在所述终止节目时钟参考值时接收的报文数； 根据所述统计数据， 获取所 述所有节点中上下游节点间丟失的报文数； 根据所述上下游节点间丟失的 报文数， 确定故障链路；
节点， 用于接收所述检测链路故障的装置下发的启动指令， 并获取当 前的节目时钟参考值； 从所述当前的节目时钟参考值开始进行数据统计； 每隔预设数量的携带节目时钟参考值的报文向所述检测链路故障的装置发 送统计数据， 使所述检测链路故障的装置对所述统计数据进行分析， 确定 故障链路。
PCT/CN2011/081285 2010-12-15 2011-10-25 一种检测故障链路的方法、装置、节点和系统 Ceased WO2012079430A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
BR112013015217A BR112013015217B1 (pt) 2010-12-15 2011-10-25 método, aparelho, nó e sistema de detecção de link defeituoso
EP11849700.7A EP2654310B1 (en) 2010-12-15 2011-10-25 Lossy link detection method, apparatus, node and system
US13/918,571 US9036488B2 (en) 2010-12-15 2013-06-14 Faulty link detection method, apparatus, node, and system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201010601481.3 2010-12-15
CN201010601481.3A CN102137282B (zh) 2010-12-15 2010-12-15 一种检测故障链路的方法、装置、节点和系统

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US13/918,571 Continuation US9036488B2 (en) 2010-12-15 2013-06-14 Faulty link detection method, apparatus, node, and system

Publications (1)

Publication Number Publication Date
WO2012079430A1 true WO2012079430A1 (zh) 2012-06-21

Family

ID=44296923

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/081285 Ceased WO2012079430A1 (zh) 2010-12-15 2011-10-25 一种检测故障链路的方法、装置、节点和系统

Country Status (5)

Country Link
US (1) US9036488B2 (zh)
EP (1) EP2654310B1 (zh)
CN (1) CN102137282B (zh)
BR (1) BR112013015217B1 (zh)
WO (1) WO2012079430A1 (zh)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103220190A (zh) * 2013-04-22 2013-07-24 华为技术有限公司 一种故障检测的方法及装置
WO2016197736A1 (zh) * 2016-01-08 2016-12-15 中兴通讯股份有限公司 一种网络故障检测方法及装置
EP2741439B1 (en) * 2012-11-01 2018-08-22 Huawei Technologies Co., Ltd. Network failure detecting method and monitoring center
CN111372131A (zh) * 2018-12-25 2020-07-03 中兴通讯股份有限公司 网络故障检测方法、装置、机顶盒、云平台、系统及介质

Families Citing this family (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102137282B (zh) 2010-12-15 2014-02-19 华为技术有限公司 一种检测故障链路的方法、装置、节点和系统
EP2690882B1 (en) * 2011-08-16 2015-07-08 Huawei Technologies Co., Ltd. Iptv fault location method, device and system
CN102546263A (zh) * 2012-02-21 2012-07-04 德科仕通信(上海)有限公司 在iptv网络中视频服务器和ip网络的故障隔离方法及系统
EP2645628B1 (en) * 2012-03-29 2015-06-17 Alcatel Lucent Continuous detection of dead or impaired IPTV streams
US20150146012A1 (en) * 2013-11-27 2015-05-28 Sprint Communications Company L.P. Video presentation quality display in a wireless communication device
CN103888303A (zh) * 2014-04-21 2014-06-25 国家电网公司 一种数据报文的控制方法和装置
CN104639955B (zh) * 2015-03-09 2017-10-27 德科仕通信(上海)有限公司 检测mpeg2‑ts vbr码流质量问题的方法
CN107846291B (zh) * 2016-09-18 2020-02-14 华为技术有限公司 报文处理方法、故障定位方法及网络设备
CN108345621B (zh) * 2017-01-24 2022-03-08 腾讯科技（深圳）有限公司 一种数据对账方法、系统及数据系统
CN106850640A (zh) * 2017-02-15 2017-06-13 北京浩瀚深度信息技术股份有限公司 基于序列号的rtp业务识别方法及系统
JP6986358B2 (ja) * 2017-03-29 2021-12-22 三菱重工業株式会社 情報処理装置、情報処理方法およびプログラム
CN107154867A (zh) * 2017-04-24 2017-09-12 北京星网锐捷网络技术有限公司 网络故障检测方法及装置
CN108965934B (zh) * 2017-05-27 2021-01-29 华为技术有限公司 一种故障检测方法、监控设备及网络设备
CN109587520B (zh) * 2017-09-29 2021-06-22 中兴通讯股份有限公司 一种定位视频业务故障的方法和设备
CN111866599B (zh) * 2019-04-25 2022-05-13 中国移动通信集团福建有限公司 一种质差的定界方法、装置及设备
CN113709777B (zh) * 2020-05-21 2025-12-16 华为技术有限公司 一种故障处理方法、装置及系统
CN112751733B (zh) * 2021-02-08 2022-11-08 北京金山云网络技术有限公司 一种链路检测方法、装置、设备、系统及交换机
CN115988243A (zh) * 2021-10-14 2023-04-18 中兴通讯股份有限公司 故障定位方法及系统、计算机可读存储介质
CN114374855B (zh) * 2022-01-05 2023-05-23 烽火通信科技股份有限公司 直播花屏诊断方法、装置、设备及可读存储介质
CN116566800B (zh) * 2023-05-17 2026-01-27 岚图汽车科技股份有限公司 面向中央计算与区域协同控制架构的网络诊断方法及装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1815970A (zh) * 2005-02-01 2006-08-09 华为技术有限公司 一种检测网络链路故障并定位故障的方法
CN101166122A (zh) * 2006-10-18 2008-04-23 中兴通讯股份有限公司 一种实现通信终端间网络故障的定位方法
CN101646099A (zh) * 2009-08-28 2010-02-10 重庆重邮东电通信技术有限公司 一种网络电视质量测试方法
CN101729296A (zh) * 2009-12-29 2010-06-09 中兴通讯股份有限公司 一种以太网流量统计分析的方法和系统
CN102137282A (zh) * 2010-12-15 2011-07-27 华为技术有限公司 一种检测故障链路的方法、装置、节点和系统

Family Cites Families (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020035698A1 (en) * 2000-09-08 2002-03-21 The Regents Of The University Of Michigan Method and system for protecting publicly accessible network computer services from undesirable network traffic in real-time
US7362707B2 (en) * 2001-07-23 2008-04-22 Acme Packet, Inc. System and method for determining flow quality statistics for real-time transport protocol data flows
JP2006333254A (ja) * 2005-05-27 2006-12-07 Fujifilm Holdings Corp 動画像リアルタイム通信端末、動画像リアルタイム通信端末の制御方法及び動画像リアルタイム通信端末の制御プログラム
KR100739710B1 (ko) * 2005-06-14 2007-07-13 삼성전자주식회사 패킷의 손실 타입을 판별하는 방법 및 장치
CN100558051C (zh) * 2005-08-10 2009-11-04 华为技术有限公司 对双向转发链路进行故障检测的方法
US8005030B2 (en) * 2005-12-30 2011-08-23 Cisco Technology, Inc. WLAN diagnostics using traffic stream metrics
US8300530B2 (en) * 2007-02-08 2012-10-30 Ixia Detecting media rate for measuring network jitter
JP4798285B2 (ja) * 2007-03-23 2011-10-19 富士通株式会社 パケットの伝送品質計測方法、およびパケット受信計測装置
CN101616037B (zh) * 2009-07-27 2012-02-29 华为技术有限公司 网络通信中丢包的检测方法、装置及系统
CN101808021A (zh) * 2010-04-16 2010-08-18 华为技术有限公司 故障检测方法、装置及系统以及报文统计方法、节点设备

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1815970A (zh) * 2005-02-01 2006-08-09 华为技术有限公司 一种检测网络链路故障并定位故障的方法
CN101166122A (zh) * 2006-10-18 2008-04-23 中兴通讯股份有限公司 一种实现通信终端间网络故障的定位方法
CN101646099A (zh) * 2009-08-28 2010-02-10 重庆重邮东电通信技术有限公司 一种网络电视质量测试方法
CN101729296A (zh) * 2009-12-29 2010-06-09 中兴通讯股份有限公司 一种以太网流量统计分析的方法和系统
CN102137282A (zh) * 2010-12-15 2011-07-27 华为技术有限公司 一种检测故障链路的方法、装置、节点和系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP2654310A4 *

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2741439B1 (en) * 2012-11-01 2018-08-22 Huawei Technologies Co., Ltd. Network failure detecting method and monitoring center
CN103220190A (zh) * 2013-04-22 2013-07-24 华为技术有限公司 一种故障检测的方法及装置
WO2016197736A1 (zh) * 2016-01-08 2016-12-15 中兴通讯股份有限公司 一种网络故障检测方法及装置
CN111372131A (zh) * 2018-12-25 2020-07-03 中兴通讯股份有限公司 网络故障检测方法、装置、机顶盒、云平台、系统及介质
CN111372131B (zh) * 2018-12-25 2022-08-26 中兴通讯股份有限公司 网络故障检测方法、装置、机顶盒、云平台、系统及介质

Also Published As

Publication number Publication date
EP2654310A1 (en) 2013-10-23
US20130279347A1 (en) 2013-10-24
CN102137282B (zh) 2014-02-19
EP2654310A4 (en) 2014-01-01
CN102137282A (zh) 2011-07-27
BR112013015217A2 (pt) 2016-09-13
BR112013015217B1 (pt) 2018-09-25
EP2654310B1 (en) 2016-02-24
US9036488B2 (en) 2015-05-19

Similar Documents

Publication Publication Date Title
CN102137282B (zh) 一种检测故障链路的方法、装置、节点和系统
US10681574B2 (en) Video quality monitoring
US8644316B2 (en) In-band media performance monitoring
EP2244426B1 (en) A method and system for evaluating users quality of experience and network device
EP2690882B1 (en) Iptv fault location method, device and system
US8248942B2 (en) Monitoring of real-time transport protocol (RTP) packet flow along RTP path
US8873368B2 (en) Method for processing channel switching failure case, terminal device, and channel switching server
EP3425909B1 (en) Video quality monitoring
US9043851B2 (en) Methods, systems, and computer readable media for measuring multicast latency
US20130061278A1 (en) Method and System for Implementing Interaction between Set-Top Box (STB) and Home Gateway
US11936930B2 (en) Data processing method, server, and data collection device
EP3491784B1 (en) Estimation of losses in a video stream
WO2009059521A1 (en) Method and system for monitoring and controlling media transmission quality
CN102630377B (zh) 处理组播流质量参数的方法、装置和系统
US9635569B2 (en) Method and apparatus for measuring end-to-end service level agreement in service provider network
CN106303752A (zh) 一种mpeg2-ts/udp/ip码流丢包故障判定方法
Baltoglou et al. Real-world IPTV network measurements
Yin et al. WebRTC-StallQuant: In-Band, Tag-Free Estimation of Stall-Duration Distributions for QoE
Jiang et al. REQMM: Real-time end-user QoE monitoring middleware for IP-based commercial TV service
Serral-Gracià et al. Metrics and QoE assessment in P2PTV applications
Serral‐Gracià et al. QoS and QoE Effects of Packet Losses in Multimedia Video Streaming
HK40003135A (zh) 视频质量监控
HK40003135B (zh) 视频质量监控

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: 11849700

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2011849700

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112013015217

Country of ref document: BR

ENP Entry into the national phase

Ref document number: 112013015217

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20130617