WO2015024523A1 - Procédé et système de détermination de défaillance de réseau support ip - Google Patents

Procédé et système de détermination de défaillance de réseau support ip Download PDF

Info

Publication number
WO2015024523A1
WO2015024523A1 PCT/CN2014/084963 CN2014084963W WO2015024523A1 WO 2015024523 A1 WO2015024523 A1 WO 2015024523A1 CN 2014084963 W CN2014084963 W CN 2014084963W WO 2015024523 A1 WO2015024523 A1 WO 2015024523A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
bearer network
message
value
network
Prior art date
Application number
PCT/CN2014/084963
Other languages
English (en)
Chinese (zh)
Inventor
阴元斌
Original Assignee
华为技术有限公司
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 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2015024523A1 publication Critical patent/WO2015024523A1/fr

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
    • H04L41/0677—Localisation of faults
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/11—Identifying congestion
    • H04L47/115—Identifying congestion using a dedicated packet

Definitions

  • a service of a service network such as a service network of a next generation network (NGN) or a wireless network, may be carried over an Internet Protocol (IP) network.
  • NDN next generation network
  • IP Internet Protocol
  • the IP bearer network can carry more and more services, including wireless services, NGN services, Internet Protocol television (IPTV) services, and Internet services.
  • Some services have higher requirements for the service level agreement (SLA) of the IP bearer network.
  • SLA indicators include bandwidth, packet loss rate, delay, and delay variation. If the IP bearer network fails, the service quality of the carried services will be affected. If the service network fails, it will also affect the service quality of the service. Therefore, if the service quality of the service network is abnormal, it is necessary to determine whether the IP bearer network carrying the service is faulty, so as to quickly locate the fault and quickly recover the service.
  • the service network monitors the service quality or receives the fault report sent by the customer, and finds that the service quality of the service is abnormal.
  • the maintenance personnel of the service network first detect whether the service network is faulty. If the maintenance personnel of the service network determine that the service network has not failed, notify the maintenance personnel of the IP bearer network.
  • the maintenance personnel of the IP bearer network check whether the IP bearer network is faulty according to the service information provided by the maintenance personnel of the service network.
  • the embodiment of the present invention provides a method and a system for determining that an IP bearer network is faulty, and is used to solve the problem that the IP bearer network cannot be automatically determined in the prior art.
  • an embodiment of the present invention provides a method for determining a fault of an IP bearer network.
  • the service between the first device and the second device is carried by the IP bearer network, and the first device accesses the IP bearer network by using a third device in the IP bearer network, and the second device passes the IP
  • the fourth device in the bearer network accesses the IP bearer network.
  • the first device monitors a service quality of the service between the first device and the second device.
  • the first device When the quality of service of the service between the first device and the second device is abnormal, the first device sends a request message to the third device, where the request message is sent by the first device And generating, configured to request the third device to detect a service quality of the service in the IP bearer network, and the request message carries an identifier and a quality parameter of the service.
  • the first device receives a response message sent by the third device, where the response message carries an identifier of the service and a first value of the quality parameter of the service in the IP bearer network.
  • a first implementation is provided, the request message or the response message being an extended Dynamic Host Configuration Protocol (DHCP) message.
  • DHCP Dynamic Host Configuration Protocol
  • the DHCP message includes an op field, and when the value of the op field is a first preset value, indicating that the extended DHCP message is the request message; when the value of the op field is 2, indicating the extended The DHCP message is the response message.
  • a third implementation manner is provided, where the extended DHCP message includes an options field, where the options field is used to carry the identifier of the service and The quality parameters of the service.
  • the fourth implementation manner is provided, where the request message further carries a detection time; the quality parameter includes at least one of the following parameters: a packet loss rate, Delay and delay jitter.
  • the fifth device is configured to monitor the service quality of the service between the first device and the second device
  • the method includes: the first device obtaining a second value of the quality parameter of the service between the first device and the second device; the first device determining the second parameter of the quality parameter Whether the value exceeds the third threshold or is lower than the fourth threshold, and when the second value of the quality parameter exceeds the third threshold or is lower than the fourth threshold, determining the first device and The service quality of the service between the second devices is abnormal.
  • the sixth implementation manner is provided, where the identifier of the service includes a source IP address and a destination IP address of the service.
  • the seventh implementation manner is provided, where the identifier of the service includes a five-tuple.
  • the quintuple includes a source IP address, a destination IP address, a protocol number, a source port number, and a destination port number of the service.
  • the quality parameters of the service include at least one of a detection time and the following parameters: packet loss rate, delay, and delay jitter.
  • an eighth implementation wherein the request message or the response message is an extended 802.3ah message.
  • a ninth implementation manner is provided, the first threshold value and the second threshold value At least one of them is stored in the first device.
  • an embodiment of the present invention provides a method for determining a fault of an IP bearer network.
  • the IP bearer network carries the service between the first device and the second device, where the first device accesses the IP bearer network through a third device in the IP bearer network, and the second device passes the IP bearer.
  • the fourth device in the network accesses the IP bearer network.
  • the request message carries an identifier and a quality parameter of the service.
  • the third device acquires a value of the quality parameter of the service between the third device and the fourth device.
  • a first implementation manner where the identifier of the service includes a five-tuple.
  • Determining, according to the identifier of the service, the termination point of the service in the IP bearer network including: obtaining, by parsing the request message, the quintuple carried in the request message; to the IP bearer
  • the network management system of the network sends a message for querying the endpoint, where the message of the query endpoint carries the quintuple of the service and the name of the interface on the third device that receives the request message; receiving the network And a response message sent by the Query Endpoint, where the response message carries the quintuple and an endpoint and an outbound interface of the service in the IP bearer network.
  • a second implementation manner is provided, the determining, according to the identifier of the service, the termination point of the service in the IP bearer network, including: the third device is in an adjacent IP bearer network The device sends a probe message to determine an endpoint and an outbound interface of the service in the IP bearer network.
  • a third implementation manner is provided, where the request message or the response message is an extended dynamic host configuration.
  • the request message or the response message is an extended dynamic host configuration.
  • a fourth implementation manner is provided, where the extended DHCP message includes an op field, and when the value of the op field is a first preset value, the extended DHCP message is indicated. a request message; when the value of the op field is a second preset value, indicating that the extended DHCP message is the response message, and the second preset value is different from the first preset value .
  • a fifth implementation manner is provided, where the extended DHCP message includes an option options field, where the options field is used to carry the identifier of the service and the Quality parameters of the business.
  • an embodiment of the present invention provides a network device, where the network device is a first device.
  • the service between the first device and the second device is carried by the IP bearer network, and the first device accesses the IP bearer network through the third device in the IP bearer network, and the second device passes through the device.
  • the fourth device in the IP bearer network accesses the IP bearer network.
  • the first device includes: a monitoring unit, a determining unit, a message generating unit, and a transmitting and receiving unit.
  • the monitoring unit is configured to monitor a service quality of the service between the first device and the second device.
  • the determining unit is configured to determine whether an abnormality occurs in a service quality of the service between the first device and the second device.
  • the sending and receiving unit is configured to: when the determining unit determines that the service quality of the service between the first device and the second device is abnormal, send a request message to the third device.
  • the request message is generated by the message generating unit, and is configured to request the third device to detect a service quality of the service in the IP bearer network, where the request message carries an identifier and a quality parameter of the service.
  • the message generating unit is configured to generate the request message.
  • the sending and receiving unit is further configured to receive a response message sent by the third device, where the response message carries an identifier of the service and a first value of the quality parameter of the service in the IP bearer network.
  • the determining unit is further configured to determine whether the first value of the quality parameter exceeds a first threshold or is lower than a second threshold, when the first value of the quality parameter exceeds the first threshold or low At a second threshold, confirming the between the third device and the fourth device The IP bearer network has failed.
  • a first implementation is provided, the request message or the response message being an extended dynamic host configuration protocol DHCP message.
  • a second implementation manner where the extended DHCP message includes an op field, and when the value of the op field is a first preset value, the extended DHCP message is indicated. a request message; when the value of the op field is a second preset value, indicating that the extended DHCP message is the response message, and the second preset value is different from the first preset value .
  • a third implementation manner is provided, where the extended DHCP message includes an option options field, where the options field is used to carry the identifier of the service and the Quality parameters.
  • the first device further includes a storage unit for storing at least one of the first threshold and the second threshold.
  • an embodiment of the present invention provides an IP bearer network device.
  • the IP bearer network carries the service between the first device and the second device, where the first device accesses the IP bearer network through a third device in the IP bearer network, and the second device passes the The fourth device in the IP bearer network accesses the IP bearer network.
  • the IP bearer network device is the third device.
  • the third device includes a transmitting and receiving unit and a processing unit.
  • the sending and receiving unit is configured to receive a request message sent by the first device, where the request message carries an identifier and a quality parameter of the service, where the request message is that the first device is in the first device and the The service quality of the service between the second devices is sent when an abnormality occurs.
  • the processing unit is configured to determine, according to the identifier of the service, an endpoint of the service in the IP bearer network, and obtain the quality parameter of the service between the third device and the endpoint And generating a response message, where the response message is used to respond to the request message, and carries an identifier of the service and a value of the quality parameter; the termination point is the fourth device.
  • the sending and receiving unit is further configured to send the response message to the first device.
  • a first implementation manner is provided, where the request message or the response message is an extended dynamic host configuration protocol (DHCP) message.
  • DHCP extended dynamic host configuration protocol
  • a second implementation manner where the extended DHCP message includes an op field, and when the value of the op field is a first preset value, the extended DHCP message is indicated. a request message; when the value of the op field is a second preset value, indicating that the extended DHCP message is the response message, and the second preset value is different from the first preset value .
  • a third implementation manner is provided, where the extended DHCP message includes an option options field, where the options field is used to carry the identifier of the service and the Quality parameters.
  • an embodiment of the present invention provides a system for determining a fault of an IP bearer network, including the first device of any one of the foregoing third or third aspects, and any one of the foregoing fourth or fourth aspect The third device of the implementation.
  • the method, the device, and the system of the present invention can automatically and quickly determine whether the IP bearer network carrying the service is faulty, thereby speeding up fault location.
  • the speed helps to quickly restore business and enhance the customer experience.
  • FIG. 1A is a schematic diagram of a network implementing an embodiment of the present invention.
  • FIG. 1B is a simplified schematic diagram of a network implementing an embodiment of the present invention
  • FIG. 1 is a simplified schematic diagram of a network for implementing an embodiment of the present invention
  • FIG. 2 is a simplified flowchart of a method for determining a fault of an IP bearer network according to an embodiment of the present invention
  • FIG. 3 is a schematic diagram of determining an IP by a first device according to an embodiment of the present invention
  • a method for carrying a network fault is simplified by a flow chart;
  • FIG. 4 is a format diagram of an extended DHCP message according to an embodiment of the present invention.
  • FIG. 5 is a simplified flowchart of a method for determining a fault of an IP bearer network by a third device according to an embodiment of the present invention
  • FIG. 6 is a block diagram showing a simplified functional structure of a first device in an embodiment of the present invention.
  • FIG. 7 is a simplified structural block diagram of a first device in an embodiment of the present invention.
  • FIG. 8 is a block diagram showing a simplified functional structure of a third device in an embodiment of the present invention.
  • FIG. 9 is a simplified structural block diagram of a third device in an embodiment of the present invention.
  • the technical solutions of the present invention will be clearly and completely described in the following with reference to the accompanying drawings and embodiments. It will be apparent that the various embodiments described below are merely exemplary embodiments of the invention. Based on the following various embodiments of the present invention, those skilled in the art can obtain other technical features that can solve the technical problems of the present invention and achieve the technical effects of the present invention by equivalently transforming some or even all of the technical features without creative work. The various embodiments of the invention are apparent from the scope of the invention as disclosed.
  • FIG. 1A is a schematic diagram of a network in which embodiments of the present invention may be implemented.
  • the IP bearer network shown in FIG. 1A can carry at least one of multiple services, such as a wireless service, an NGN service, an IP TV service, an Internet service, and the like.
  • the embodiments of the present invention do not limit the types and quantities of services carried by the IP bearer network.
  • FIG. 1A is simplified in the form of FIG. 1 B and FIG. 1 C.
  • FIG. 1B is a simplified schematic diagram of a network implementing an embodiment of the present invention.
  • Figure 1 C is Another simplified schematic diagram of a network implementing an embodiment of the present invention.
  • a certain service between the first device 102 and the second device 108 is carried by the IP bearer network 100 where the third device 104 and the fourth device 106 are located.
  • the first device 102 accesses the IP bearer network 100 through the third device 104.
  • the second device 108 accesses the IP bearer network 100 through the fourth device 106.
  • FIG. 1B a certain service between the first device 102 and the second device 108 is carried by the IP bearer network 100 where the third device 104 and the fourth device 106 are located.
  • the first device 102 accesses the IP bearer network 100 through the third device 104.
  • the second device 108 accesses the IP bearer network 100 through the fourth device 106.
  • FIG. 1B
  • the IP bearer network 100 in addition to the third device 104 and the fourth device 106, may further include a fifth device 110, where the first device 102 passes the third device 104.
  • the fifth device 110 and the fourth device 106 are in communication with the second device 108.
  • the first device 102 can be a base station and the second device 108 can be a radio network controller (RNC).
  • RNC radio network controller
  • the first device 102 can be a media gateway (MGW), and the second device 108 can be a soft switch (SS).
  • MGW media gateway
  • SS soft switch
  • the embodiment shown in Figures 1A-C is only used to exemplarily illustrate the network structure in the embodiment of the present invention. In actual applications, the network structure can be diversified. It should be noted that in the present application, the naming sequence of the device is arbitrary, and it is not explicitly or implicitly indicated that a device must correspond to the receiving end or the transmitting end of the service.
  • FIG 2 is a simplified flow chart of a method for determining an IP bearer network failure. Referring to Figure 1 B and Figure 1 C, the method includes:
  • the first device 102 monitors the quality of service of a certain service between the first device 102 and the second device 108.
  • the monitoring mentioned here can be monitored regularly or in real time.
  • the monitored object can be a value of one or more quality parameters of the service.
  • the monitoring method is prior art and will not be described in detail herein.
  • the first device 102 determines whether an abnormality occurs in a service quality of the service between the first device 102 and the second device 108, according to the value of the monitored one or more quality parameters. If the first device 102 determines that the service quality of the service does not have an abnormality, it may return 202. 206. If the first device 102 determines that the service quality of the service is abnormal, the first device 102 sends a request message to the third device 104, where the request message is generated by the first device 102, The third device 104 is requested to detect the service quality of the service in the IP bearer network. The request message carries an identifier of the service and at least one quality parameter.
  • the third device 104 receives the request message, and determines an end point of the service in the IP bearer network according to the identifier of the service carried in the request message, for example, in FIG. 1B and FIG.
  • the fourth device 106 is shown.
  • the third device 104 detects a service quality of the service in the IP bearer network, and obtains a first value of the quality parameter of the service between the third device 104 and the endpoint. .
  • the port connecting the third device 104 with the first device 102 is defined as the inbound interface of the third device 104, and the third device 104 is connected to other devices of the IP bearer network (for example, the fourth device 106 in FIG. 1B).
  • the port connected to the fifth device 110 in FIG. 1C is defined as the outbound interface of the third device;
  • the port connecting the fourth device 106 and the second device 108 is defined as the outbound interface of the fourth device 106, and the fourth device is
  • the port connected to other devices of the IP bearer network (for example, the third device 104 in FIG. 1B or the fifth device 110 in FIG. 1C) is defined as an inbound interface of the fourth device.
  • the definition of the outgoing and incoming is only to distinguish the corresponding port, and does not explicitly or implicitly indicate the flow of the service signal.
  • the third device 104 when detecting the service quality of the service in the IP bearer network, may detect the service quality of the service between the inbound interface of the third device 104 and the outbound interface of the fourth device 106. .
  • the quality of service of the service between the inbound interface of the third device 104 and the ingress interface of the fourth device 106 can be detected.
  • the quality of service of the service between the outbound interface of the third device 104 and the inbound interface of the fourth device 106 can be detected.
  • the quality of service of the service between the outbound interface of the third device 104 and the outgoing interface of the fourth device 106 can be detected.
  • the third device 104 detects the service quality of the service between the inbound interface of the third device 104 and the egress interface of the fourth device 106.
  • the network of the IP bearer network The network management system deploys service quality detection of the service between the starting point of the service (the third device 104 shown in FIG. 1B) and the terminal (such as the fourth device 106 shown in FIG. 1B), so that the The third device 104 detects the service quality of the service in the IP bearer network.
  • the detection result of the service quality of the service in the IP bearer network includes a detection value of at least one quality parameter carried in the request message. The detected value is referred to as a first value of the quality parameter.
  • the third device 104 sends a response message to the first device 102, where the response message is generated by the third device 104, and is configured to respond to the request message and carry the The identification of the service and the first value of the quality parameter.
  • the first device 102 determines, according to the first value of the quality parameter carried in the response message, whether the IP bearer network between the third device 104 and the fourth device 106 is faulty.
  • the first device 102 may preset a first threshold of the quality parameter of the service, and when the first value of the quality parameter exceeds the first threshold, confirm The IP bearer network between the three devices 104 and the fourth device 106 has failed.
  • the first device 102 may preset a second threshold of the quality parameter of the service, and when the first value of the quality parameter is lower than the second threshold, confirming a third The IP bearer network between the device 104 and the fourth device 106 has failed.
  • the first device 102 may preset a first range of the quality parameter of the service, and when the first value of the quality parameter is not in the first range, confirm the third device 104 and the first The IP bearer network between the four devices 106 has failed.
  • the first device 102 may preset a second range of the quality parameter of the service, and when the first value of the quality parameter is in the second range, confirm the third device 104 and the first The IP bearer network between the four devices 106 has failed.
  • the above several determination methods can be combined at will.
  • the foregoing scheme of presetting a certain range of the quality parameter of the service may be regarded as the first value of the quality parameter and two of the range The endpoint value is compared to the size.
  • FIG. 3 is a simplified flowchart of a method for determining a fault of an IP bearer network by a first device according to an embodiment of the present invention.
  • the monitoring means may be timed monitoring or real time monitoring.
  • quality detection of real-time services can be deployed between the first device 102 and the second device 108, and the quality of the service can be monitored in real time to obtain real-time values of one (or more) quality parameters of the service.
  • the first device 102 and the second device 108 are monitored in real time.
  • the real-time value of the quality parameter of the service is the second value of the quality parameter.
  • the determining, by the first device 102, whether the quality of service of the service between the first device 102 and the second device 108 is abnormal may be determined by using a second value of the quality parameter.
  • the first device 102 may preset a third threshold of the quality parameter of the service. When it is detected that the second value of the quality parameter of the service exceeds the third threshold, the first device 102 determines that the service quality of the service is abnormal.
  • the third threshold and the first threshold may be the same threshold or different thresholds.
  • the first device 102 may preset a fourth threshold of the quality parameter of the service, when the second value of the quality parameter is lower than the fourth threshold, the first device 102 determining that the quality of service of the service is abnormal.
  • the first device 102 may preset a third range of the quality parameter of the service, when the second value of the quality parameter is not in the third range, the first device 102 determines the The quality of the business of the business is abnormal.
  • the first device 102 may preset a fourth range of the quality parameter of the service, when the second value of the quality parameter is in the fourth range, the first device 102 determines the The quality of the business of the business is abnormal.
  • the above several determination methods can be combined at will. Pre-setting the quality of the service A solution to a range of parameters can be considered to compare the second value of the quality parameter to the two endpoint values of the range.
  • the quality parameter of the service monitored by the first device 102 may include one or more of the following parameters: packet loss rate, delay, and delay jitter.
  • the thresholds of these parameters are: time delay threshold, packet loss rate threshold and delay jitter threshold. When one or more of the packet loss rate, the delay, or the delay jitter exceed their respective thresholds, it may be determined that the service quality of the service is abnormal.
  • the first device 102 sends a request message to the third device 104, where the request message is first.
  • the device 102 is configured to request the third device 104 to detect the service quality of the service in the IP bearer network, and the request message carries the identifier of the service and at least one quality parameter.
  • the identifier of the service may include a source IP address and a destination IP address of the service.
  • the identifier of the service may further include a protocol number, a source port number, and a destination port number of the service.
  • a combination of a source IP address, a destination IP address, a source port number, a destination port number, and a protocol number is called a quintuple.
  • the request message may also carry a detection time.
  • the request message may further carry VLAN information of the service, such as a VLAN ID.
  • Step 308 The first device 102 receives a response message, where the response message carries an identifier of the service and a first value of the quality parameter of the service in the IP bearer network.
  • Step 310 is the same as 214 shown in FIG. 2, and details are not described herein again.
  • both the request message and the response message may be an extended Dynamic Host Configuration Protocol (DHCP) message.
  • DHCP Dynamic Host Configuration Protocol
  • FIG. 4 A schematic diagram of an example of an extended DHCP message is shown in FIG.
  • the fields shown in Figure 4 are in addition to the fields described below.
  • IETF Internet Engineering Task Force
  • Internet Engineering Task Force Standard RFC (Request For Comments, Request for Comments)
  • options are used in a new definition manner to carry the service identifier in the request message or the response message, for example, a quintuple. Optionally, options can also carry VLAN information, etc. An example of options is shown in Table 1.
  • a new value is defined, indicating that the options are options of the request message or the response message.
  • IPAddM The source IP address of the service.
  • IPAddr2 Destination IP address of the service.
  • SubCode3 indicates that Portl is the source port of the service.
  • Portl The source port of the service.
  • Port2 The destination port of the service.
  • PNumber The protocol number of the service.
  • SubCode6 indicates that the subsequent VLAN ID is the VLAN ID of the service.
  • VLAN ID The VLAN ID of the service.
  • SubCode7 indicates that the subsequent Packet Loss Rate is the packet loss rate of the service.
  • Packet Loss Rate The packet loss rate of the service.
  • Delay The delay of the service.
  • SubCode9 9 indicates that the subsequent Delay Variation is the delay jitter of the service.
  • Delay Variation The delay jitter of the service.
  • Detect Time Detection time.
  • the request message in this embodiment may also be generated by extending a message defined in the Institute of Electrical and Electronics Engineers (IEEE) 802.3ah.
  • IEEE 802.3ah the Institute of Electrical and Electronics Engineers
  • Table 2 shows the extended OAM messages.
  • each TLV is as shown in Table 3.
  • Table 3 Data/PAD format
  • the definition format of each TLV is as follows:
  • Type Length Value where Type indicates the type of the TLV, Length indicates the length of the TLV, and Value is the value t .
  • the OAM message shown in Table 2 may include the following TLV.
  • Source Port TLV: Type 3
  • Value is the source port of the service
  • Protocol Number TLV: Type 5
  • Value is the protocol number of the service
  • VLAN number TLV: Type 6
  • Value is the VLAN number of the service.
  • Loss Packet Ratio TLV: Type 7
  • Value is the packet loss rate of the service.
  • Value is the delay jitter of the service.
  • Detect Time TLV: Type 10
  • Value is the detection time.
  • Step 502 The third device 104 receives the request message sent by the first device 102.
  • the implementation of the request message is described in detail in 306, as shown in Figure 3, and will not be described here.
  • Step 504 The third device 104 determines, according to the identifier of the service carried in the request message, for example, a quintuple, an endpoint and an exit of the corresponding service in the IP bearer network.
  • the third device 104 After receiving the request message sent by the first device 102, the third device 104 obtains the quintuple of the service carried in the request message by parsing the request message. The third device 104 sends a message for querying the endpoint to the network management system of the IP bearer network, where the message of the query endpoint carries the quintuple of the service and the third device 104 receives the request message.
  • the name of the interface is the name of the interface.
  • the network management system of the IP bearer network After receiving the message of the query termination point, the network management system of the IP bearer network uses the global physical topology and service topology information saved in the network management system, according to the quintuple of the service and the third The name of the interface on the device 104 that receives the request message determines an endpoint and an outbound interface of the service in the IP bearer network. In this manner, the network management system of the IP network carries out service quality detection of the service on the origin of the service in the IP network and the outbound interface of the endpoint.
  • the third device 104 After the network management system of the IP bearer network determines the end point and the outbound interface of the service in the IP bearer network, the third device 104 sends a response message for querying the endpoint, where the response message carries the The quintuple of the service and the end point and the outbound interface of the service in the IP bearer network.
  • the third device 104 determines, according to the quintuple carried in the request message, an endpoint and an exit of the corresponding service in the IP network, and may also implement the following solution.
  • the third device 104 sends a probe message to the neighboring IP bearer network device, such as the fourth device 106 in the embodiment shown in FIG. 1B, or the fifth device 110 in the embodiment shown in FIG. 1C.
  • the probe message carries a quintuple of the service, and the neighboring IP bearer network device is according to the industry
  • the quintuple of the service, the Forwarding Information Base (FIB) determines the forwarding type corresponding to the service.
  • FIB Forwarding Information Base
  • the neighboring IP bearer network device searches for a public network routing table according to the destination IP address of the service to determine a corresponding routing type. If it is a direct route, the neighboring IP bearer network device is an endpoint of the service in the IP bearer network, and the corresponding outgoing interface is determined by searching the public network routing table according to the destination IP address of the service. If it is an Interior Gateway Protocol (IGP) route, the public network routing table is searched according to the destination IP address of the service to determine a corresponding next hop, and the probe message is forwarded to the next hop.
  • IGP Interior Gateway Protocol
  • the next hop After receiving the probe message, the next hop performs the same operation as the neighboring IP bearer network device until the end point and the outbound interface of the service in the IP bearer network are found. If it is a static route, the neighboring IP bearer network device searches the public network routing table according to the destination IP address of the service to determine a corresponding next hop, and forwards the probe message to the next hop, if not Upon receiving the response, the neighboring IP bearer network device is an endpoint of the service in the IP bearer network, and searches for a corresponding outbound interface by searching a public network routing table according to the destination IP address of the service.
  • the neighboring IP bearer network device forwards the probe message to the next hop, and after receiving the probe message, the next hop performs the same as the neighboring IP bearer network device. Operation until the end point and the outbound interface of the service in the IP bearer network are found.
  • the neighboring IP bearer network device searches the VPN routing table according to the destination IP address of the service to determine the destination IP address.
  • the route type corresponding to the address. If it is a direct route, the neighboring IP bearer network device is an endpoint of the service in the IP bearer network, and searches the routing table of the VPN according to the destination IP address of the service to determine a corresponding outbound interface. . If it is an IGP route or a Border Gateway Protocol (BGP) route, the routing table of the VPN is searched according to the destination IP address of the service to determine a corresponding next hop, and the neighboring IP bearer network device is The next hop forwards the probe message.
  • L3VPN Layer 3 virtual private network
  • the next hop After receiving the probe message, the next hop performs the same operation as the neighboring IP bearer network device, Until the end point and the outbound interface of the service in the IP bearer network are found. If it is a static route, the neighboring IP bearer network device searches the routing table of the VPN according to the destination IP address of the service to determine a corresponding next hop, and forwards the probe message to the next hop, if not Upon receiving the response, the neighboring IP bearer network device is an endpoint of the service in the IP bearer network, and searches for the corresponding outbound interface by searching the routing table of the VPN according to the destination IP address of the service.
  • the neighboring IP bearer network device forwards the probe message to the next hop, and after receiving the probe message, the next hop performs execution with the neighboring IP bearer network device. The same operation is performed until the end point and the outbound interface of the service in the IP bearer network are found.
  • the neighboring IP bearer network device determines an access circuit (AC) interface of the corresponding PW according to the quintuple of the service. Whether it is a physical interface, if the AC interface is a physical interface, the neighboring IP bearer network device is an endpoint of the service in the IP bearer network, and the AC interface is the egress interface. If the AC interface is not a physical interface, the neighboring IP bearer network device forwards the probe message to a next hop, and the next hop performs the same operation as the neighboring IP bearer network device until determining The service is in an endpoint and an outbound interface in the IP bearer network.
  • AC access circuit
  • the AC interface is not a physical interface, it means that the network architecture is Layer 2 (L2) access Layer 3 (Layer 3, L3 for short), and the adjacent IP bearer network device Determining, according to the AC interface, a corresponding L3 interface, determining whether the L3 interface is bound to a VPN. If the L3 interface is bound to a VPN, searching for a corresponding VPN routing table according to the destination IP address of the service is determined. One jump. If the L3 interface is not bound to the VPN, the neighboring IP bearer network device searches for the corresponding public network routing table according to the destination IP address of the service to determine the next hop.
  • L2 Layer 2
  • Layer 3 Layer 3
  • the interface when the FIB is queried, the interface may be determined, and the operation of determining the interface described above may be omitted.
  • the IP bearer network device that receives the probe message may send a probe response message to the third device 104 when determining that the service is in an end point and an outbound interface in the IP bearer network.
  • the probe response message carries an endpoint and an outbound interface of the service in the IP bearer network.
  • the third device 104 sends a service quality detection request message to the network management system of the IP bearer network, where the service quality detection request message carries a starting point, an ingress interface, an endpoint, and an end of the service in the IP bearer network. Outlet interface.
  • the network management system of the IP bearer network deploys service quality detection on the inbound interface of the starting point and the outbound interface of the endpoint.
  • Steps 506 and 508 are the same as steps 210 and 212 shown in Fig. 2, respectively, and will not be described again here.
  • the method for determining the fault of the IP bearer network in the embodiment may automatically determine whether the IP bearer network carrying the service is faulty when the service quality of the service in the service network is abnormal, thereby speeding up The speed of fault location helps to quickly restore business and enhance the customer experience.
  • FIG. 6 is a simplified block diagram of the first device.
  • the service between the first device 600 and the second device is carried by the IP bearer network.
  • the first device 600 accesses the IP bearer network through a third device in the IP bearer network
  • the second device accesses the IP bearer network through a fourth device in the IP bearer network.
  • the first device 600 is a network device that can provide services to users through an IP bearer network.
  • Such a device which is divided by a functional structure, generally includes: a monitoring unit 602, a determining unit 604, a message generating unit 606, and a transmitting and receiving unit 608.
  • the monitoring unit 602 is configured to monitor a service quality of the service between the first device 600 and the second device.
  • the determining unit 604 is configured to determine whether an abnormality occurs in the service quality of the service between the first device 600 and the second device.
  • the sending and receiving unit 608 is configured to: when the determining unit 604 determines that the service quality of the service between the first device 600 and the second device is abnormal, send a request message to the third device, where The request message is generated by the message generating unit 606, and configured to request the third device to detect the service quality of the service in the IP bearer network.
  • the request message carries an identifier and a quality parameter of the service.
  • the message generating unit 606 is configured to generate the request message.
  • the sending and receiving unit 608 is further configured to receive the ringing sent by the third device.
  • the response message carries an identifier of the service and a first value of the quality parameter of the service in the IP bearer network.
  • the determining unit 604 is further configured to determine whether the first value of the quality parameter exceeds a first threshold or is lower than a second threshold, if the first value of the quality parameter exceeds the first width The value is lower than the second threshold, and it is confirmed that the IP bearer network between the third device and the fourth device is faulty.
  • each unit is merely an example.
  • the operation allocation may be completed by different units according to requirements, such as configuration requirements of corresponding hardware or convenience of implementation of software.
  • the internal structure of the first device is divided into different units to perform all or part of the operations described above.
  • FIG. 6 performs corresponding software completion.
  • the foregoing sending and receiving unit 608 may be hardware having a function of executing the foregoing sending and receiving unit, such as a transceiver, or may be capable of performing corresponding
  • the computer program thus completes the transmitting and receiving circuit or other hardware device of the foregoing operation; and the monitoring unit 602 and the determining unit 604 as described above may be hardware having a function of executing the monitoring unit and the determining unit, such as a processor.
  • the described principles are applicable to the various embodiments provided in this specification.
  • FIG. 7 is a block diagram showing a simplified hardware structure of a first device in an embodiment of the present invention.
  • the first device 700 includes a processor 702, a memory 704, and an I/O circuitry 706.
  • the processor 702 is configured to monitor the service quality of the service between the first device 700 and the second device, and determine whether the service quality of the service between the first device 700 and the second device is abnormal.
  • the input/output circuit 706 is configured to send a request message to the third device when the processor 702 determines that the quality of service of the service between the first device 700 and the second device is abnormal.
  • the request message is generated by the processor 702, and is configured to request the third device to detect a service quality of the service in the IP bearer network, where the request message carries an identifier and a quality parameter of the service.
  • the input/output circuit 706 is further configured to receive a response message sent by the third device, where the response message is Carrying an identifier of the service and a first value of the quality parameter of the service in the IP bearer network.
  • the processor 702 is further configured to determine whether the first value of the quality parameter exceeds a first threshold or is lower than a second threshold, if the first value of the quality parameter exceeds the first threshold If the value is lower than the second threshold, it is determined that the IP bearer network between the third device and the fourth device is faulty.
  • the memory 704 is configured to store program instructions that, when executed, cause the processor 702 to perform the operations described above.
  • the service between the first device 700 and the second device is carried by an IP bearer network.
  • the first device 700 accesses the IP bearer network through a third device in the IP bearer network
  • the second device accesses the IP bearer network through a fourth device in the IP bearer network.
  • the memory 704 may be a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like, which can store a program code.
  • the program code may be already installed in the first device 700, or downloaded according to requirements during operation.
  • the memory 704 can include a database that stores network resource information, such as an identifier of the third device.
  • the memory 704 can also be configured to store a pre-configured first threshold and/or a second threshold.
  • FIG. 8 is a simplified structural block diagram of a third device in an embodiment of the present invention.
  • the IP bearer network where the third device 800 is located carries the service between the first device and the second device.
  • the first device accesses the IP bearer network by using the third device
  • the second device accesses the IP bearer network by using a fourth device in the IP bearer network.
  • the third device 800 includes a transmitting and receiving unit 802 and a processing unit 804.
  • the sending and receiving unit 802 is configured to receive a request message sent by the first device, where the request message carries an identifier and a quality parameter of the service.
  • the response message is responsive to the request message and carries an identifier of the service and a value of the quality parameter.
  • the termination point is the fourth device.
  • the sending and receiving unit 802 is further configured to send the response cancellation to the first device. Interest.
  • FIG. 9 is a block diagram showing a simplified hardware structure of a third device in an embodiment of the present invention.
  • the IP bearer network where the third device 900 is located carries the service between the first device and the second device.
  • the first device accesses the IP bearer network by using the third device
  • the second device accesses the IP bearer network by using a fourth device in the IP bearer network.
  • the third device 900 includes an input output circuit 902, a processor 904, and a memory 906.
  • the input/output circuit 902 is configured to receive a request message sent by the first device, where the request message carries an identifier and a quality parameter of the service.
  • the processor 904 is configured to determine, according to the identifier of the service, an endpoint of the corresponding service in the IP bearer network, and obtain the quality parameter of the service between the third device and the endpoint The value; and generate a response message.
  • the response message is responsive to the request message and carries an identification of the service and a value of the quality parameter.
  • the termination point is the fourth device.
  • the input and output circuit 902 is further configured to send the response message to the first device.
  • the memory 906 may include: a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like, which can store program code. One or more of them.
  • the embodiment of the present invention further provides a system for determining a fault of an IP bearer network, including the first device shown in FIG. 6 and the third device shown in FIG. 8.
  • the embodiment of the present invention further provides a system for determining a fault of an IP bearer network, including the first device shown in FIG. 7 and the third device shown in FIG.
  • the first device and the third device provided by the embodiment of the present invention can automatically determine whether the service quality abnormality of the service is abnormal due to the failure of the IP bearer network by detecting the service quality of the service and the message interaction. resulting in.
  • the technical solutions described in the foregoing embodiments may be modified or partially All of the technical features are equivalently substituted; and the modifications or substitutions do not depart from the scope of the technical solutions of the embodiments of the present invention.

Landscapes

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

Abstract

L'invention concerne un procédé de détermination de défaillance de réseau support IP. Un service entre un premier dispositif et un deuxième dispositif est porté par un réseau support IP, et le premier dispositif et le deuxième dispositif accèdent respectivement au réseau support IP via un troisième dispositif et un quatrième dispositif du réseau support IP. Le procédé comprend les étapes suivantes : le premier dispositif contrôle une qualité de service entre le premier dispositif et le deuxième dispositif pour déterminer si la qualité du service est anormale ; si c'est le cas, le premier dispositif envoie un message de demande au troisième dispositif et reçoit un message de réponse envoyé par le troisième dispositif, le message de réponse contenant un quintuple du service et des paramètres de qualité du service dans le réseau support IP. Le premier dispositif détermine si une défaillance du réseau support IP s'est produite, d'après les paramètres de qualité de service contenus dans le message de réponse.
PCT/CN2014/084963 2013-08-22 2014-08-22 Procédé et système de détermination de défaillance de réseau support ip WO2015024523A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201310373190.7A CN103457794B (zh) 2013-08-22 2013-08-22 确定ip承载网故障的方法和系统
CN201310373190.7 2013-08-22

Publications (1)

Publication Number Publication Date
WO2015024523A1 true WO2015024523A1 (fr) 2015-02-26

Family

ID=49739779

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2014/084963 WO2015024523A1 (fr) 2013-08-22 2014-08-22 Procédé et système de détermination de défaillance de réseau support ip

Country Status (2)

Country Link
CN (1) CN103457794B (fr)
WO (1) WO2015024523A1 (fr)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103457794B (zh) * 2013-08-22 2017-02-22 华为技术有限公司 确定ip承载网故障的方法和系统
CN106817273B (zh) * 2015-11-30 2021-09-03 上海诺基亚贝尔股份有限公司 用于l3vpn业务诊断的方法和装置
EP3605956B1 (fr) * 2017-04-01 2023-03-01 Huawei Technologies Co., Ltd. Procédé, dispositif et système de détection de qualité de service iptv
CN112866042B (zh) * 2019-11-12 2023-07-18 中兴通讯股份有限公司 网络质量检测方法、装置、计算机设备和计算机可读介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101056214A (zh) * 2006-06-30 2007-10-17 华为技术有限公司 下一代网络系统及下一代网络中业务质量故障定位方法
CN101420342A (zh) * 2008-11-25 2009-04-29 华为技术有限公司 一种定位故障网络的方法、装置及系统
CN103457794A (zh) * 2013-08-22 2013-12-18 华为技术有限公司 确定ip承载网故障的方法和系统

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7352693B2 (en) * 2005-01-31 2008-04-01 Nextel Communications Inc. Fault tolerant wireless communication systems and methods
CN102143012B (zh) * 2010-08-30 2014-03-26 华为技术有限公司 基于业务的ip承载网监测方法及ip业务质量监测设备

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101056214A (zh) * 2006-06-30 2007-10-17 华为技术有限公司 下一代网络系统及下一代网络中业务质量故障定位方法
CN101420342A (zh) * 2008-11-25 2009-04-29 华为技术有限公司 一种定位故障网络的方法、装置及系统
CN103457794A (zh) * 2013-08-22 2013-12-18 华为技术有限公司 确定ip承载网故障的方法和系统

Also Published As

Publication number Publication date
CN103457794B (zh) 2017-02-22
CN103457794A (zh) 2013-12-18

Similar Documents

Publication Publication Date Title
US11303564B2 (en) Packet forwarding method, apparatus, and system
US10574763B2 (en) Session-identifer based TWAMP data session provisioning in computer networks
US9294369B2 (en) Method and device for processing location information of fault point
WO2019184752A1 (fr) Procédé, appareil et système de gestion de dispositifs de réseau
US10361954B2 (en) Method and apparatus for processing modified packet
WO2015180292A1 (fr) Procédé et appareil de détection de connectivité d'interface de réseau utilisateur d'un réseau privé virtuel
US11134009B2 (en) Packet processing method and apparatus
WO2013097459A1 (fr) Procédé et dispositif de détection de chemin de service
WO2014019348A1 (fr) Procédé, dispositif et système pour l'exploitation, la gestion et la maintenance de configuration oam
EP3420687B1 (fr) Adressage pour expansion de rle dans les locaux du client
US11601335B2 (en) Methods and systems for neighbor-acknowledged graceful insertion/removal protocol
US11895021B2 (en) Message sending and receiving method, apparatus, and system
WO2015024523A1 (fr) Procédé et système de détermination de défaillance de réseau support ip
CN113055293B (zh) 软件定义广域网中的选路方法及装置、通信系统
WO2012142753A1 (fr) Procédé et dispositif de surveillance des performances d'un réseau support ip
WO2012079405A2 (fr) Procédé et système de traitement de trace de liaison
CN106878173B (zh) 一种路由发送方法及装置
WO2022078338A1 (fr) Procédé et appareil de détermination de chemin, et support de stockage informatique
WO2018040614A1 (fr) Procédé, dispositif associé et système d'établissement de trajet commuté par étiquette pour un réseau privé virtuel
WO2015188682A1 (fr) Procédé, dispositif, et système de traitement de chaîne de services
WO2015051696A1 (fr) Procédé et appareil de transmission d'un paquet oam
WO2016107156A1 (fr) Procédé et dispositif de contrôle de bout en bout pour réseau en pont

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

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

Country of ref document: EP

Kind code of ref document: A1