CN102447569B - Protection method for point-to-multipoint multicast service and network equipment - Google Patents

Protection method for point-to-multipoint multicast service and network equipment Download PDF

Info

Publication number
CN102447569B
CN102447569B CN201110451318.8A CN201110451318A CN102447569B CN 102447569 B CN102447569 B CN 102447569B CN 201110451318 A CN201110451318 A CN 201110451318A CN 102447569 B CN102447569 B CN 102447569B
Authority
CN
China
Prior art keywords
leaf node
node device
network
fault
main leaf
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.)
Expired - Fee Related
Application number
CN201110451318.8A
Other languages
Chinese (zh)
Other versions
CN102447569A (en
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.)
ZTE Corp
Original Assignee
ZTE Corp
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 ZTE Corp filed Critical ZTE Corp
Priority to CN201110451318.8A priority Critical patent/CN102447569B/en
Publication of CN102447569A publication Critical patent/CN102447569A/en
Application granted granted Critical
Publication of CN102447569B publication Critical patent/CN102447569B/en
Expired - Fee Related legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Landscapes

  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

The invention discloses a protection method for the point-to-multipoint (P2MP) multicast service, which comprises the following steps of: setting network equipment as reserve network equipment; judging whether the corresponding master leaf node equipment or a branch path on which the master leaf node equipment is positioned fails by the network equipment; and when the corresponding master leaf node equipment or the branch path on which the master leaf node equipment is positioned is determined to fail, protecting the multicast service by the network equipment via a protection path. The invention also discloses network equipment. According to the protection method and the network equipment, cost is saved, and the multicast service can be protected by a simple protection path.

Description

Method for protecting point-to-multipoint multicast service and network equipment
Technical Field
The present invention relates to a Multi-Protocol label switching (MPLS) technology in the field of network transmission, and in particular, to a method and a network device for protecting a Point-to-multipoint (P2MP, Point 2 Multiple Point) multicast service.
Background
MPLS is a framework for fast packet switching and routing that provides network data traffic with the capabilities of destination, routing, forwarding, and switching. MPLS is mainly used to solve network problems such as network speed, scalability, Quality of Service (QoS) management and traffic engineering. P2MP multicast technology is a transport technology in MPLS that transports traffic from a single sender device to multiple receiver devices. The unidirectional link with fixed bandwidth in the P2MP multicast transmission network is composed of a plurality of network devices with routing and/or switching functions; the network device connected to the sending end device is called a root node device, and the network device connected to the receiving end device is called a leaf node device.
At present, the protection method for multicast service in P2MP multicast transmission network mainly includes the following two methods:
one is a protection method based on a transmission path 1+1, and the protection method is as follows: the same two paths are established between the root node equipment and the leaf node equipment, and when one path fails, the failed path is directly disconnected to use the other path. However, this protection method incurs a large amount of setup and maintenance costs due to the large number of paths that need to be established.
The other is a 1: 1 protection method based on the double-homing protection technology of the client side link, and the protection method comprises the following steps: and respectively establishing a working path and a protection path between the root node equipment and the leaf node equipment, and informing the root node equipment of using the protection path by the leaf node equipment when the working path has a fault. However, this protection method requires establishing a reverse link between the leaf node device and the root node device for notifying of the failure, and then starting the establishment of the protection path from the root node device, which increases the complexity of the path establishment.
It can be seen that, in the existing protection method for P2MP multicast service, either a large amount of network establishment cost is consumed due to the need to establish a large number of paths, or the complexity of establishing a protection path due to establishing a reverse link and establishing a protection path from a root node device is not able to achieve protection of multicast service with a simple protection link while saving cost.
Disclosure of Invention
In view of this, an object of the present invention is to provide a method and a network device for protecting P2MP multicast services, which not only save cost, but also use a simple protection path to implement protection of multicast services.
In order to achieve the purpose, the technical scheme of the invention is realized as follows:
the invention provides a method for protecting point-to-multipoint P2MP multicast service, which comprises the following steps:
setting a network device as a standby network device, wherein the network device judges whether a corresponding main leaf node device or a branch path where the main leaf node device is located has a fault, and when the corresponding main leaf node device or the branch path where the main leaf node device is located has the fault, the network device protects the multicast service by using a protection path.
In the above solution, before the determining whether the corresponding active leaf node device or the branch path where the active leaf node device is located fails, the method further includes: and configuring a protection path.
In the above scheme, the protection path is: the network device configures a backup access link with a client device served by the corresponding main leaf node device, and configures a main/standby device protection path with the corresponding main leaf node device.
In the foregoing solution, the determining whether the corresponding main leaf node device or the branch path where the main leaf node device is located fails includes:
the network equipment is used as standby network equipment for receiving a fault detection message sent by corresponding main leaf node equipment, judging whether the main leaf node equipment has a fault according to the condition of receiving the fault detection message, and judging whether a fault notice sent by the corresponding main leaf node equipment is received;
if the main leaf node device does not have a fault and does not receive a fault notice sent by the main leaf node device, determining that the main leaf node device or a branch path where the main leaf node device is located does not have a fault;
if the main leaf node equipment fails, judging that the main leaf node equipment fails;
and if the fault notification sent by the main leaf node equipment is received, determining whether the fault type is that the transmission path of the main leaf node fails or the access link of the main leaf node fails according to the fault notification.
In the foregoing solution, the protecting the multicast service by using the protection path includes: and the network equipment judges whether to use the backup access link or the main/standby equipment protection path to protect the multicast service according to the fault type of the main leaf node equipment.
In the above scheme, the determining, according to the type of the failure of the active leaf node device, whether to use the backup access link or the active/standby device protection path to protect the multicast service includes:
if the network equipment judges that the fault type is the fault of the transmission path of the main leaf node according to the fault notification, when the network equipment serving as the standby network equipment is the leaf node equipment in the P2MP multicast transmission network, the multicast service is sent to the main leaf node equipment by using the main equipment protection path; when the network device serving as the standby network device is not a leaf node device in the P2MP multicast transmission network, the network device acquires a multicast service from the leaf node device in the P2MP multicast transmission network, and sends the multicast service to the active leaf node device by using the active/standby device protection path;
if the network equipment judges that the fault type is that the access link of the main leaf node is in fault according to the fault notice, the network equipment receives the multicast service sent by the main leaf node equipment, and sends the received multicast service to the client equipment served by the main leaf node equipment by using the backup access link;
if the network device determines that the primary leaf node device has a fault and the network device is a leaf node device in a P2MP multicast transmission network, the network device sends the multicast service received by the network device to a receiving end device served by the primary leaf node device corresponding to the network device by using a backup access link; if the network device determines that the active leaf node device fails and the network device is not a leaf node device in the P2MP multicast transmission network, the network device obtains a multicast service from the leaf node device in the P2MP multicast transmission network, and sends the multicast service to a receiving end device served by the active leaf node device using a backup access link.
The present invention also provides a network device, comprising: the system comprises a path configuration module, a fault detection module and a control module; wherein,
the path configuration module is used for protecting the multicast service by using the protection path when receiving the notification for protecting the multicast service sent by the control module;
the fault detection module is used for judging whether the corresponding main leaf node equipment or the branch path where the main leaf node equipment is located has a fault, and informing the control module that the main leaf node equipment or the branch path where the main leaf node equipment is located has a fault when the corresponding main leaf node equipment or the branch path where the main leaf node equipment is located has a fault;
and the control module is used for notifying the path configuration module to protect the multicast service after receiving the notification that the corresponding main leaf node device or the branch path where the main leaf node device is located fails, which is sent by the failure detection module, after the network device is set as the standby network device.
In the foregoing solution, the path configuration module is further configured to configure a protection path.
In the above solution, the path configuration module is specifically configured to configure a backup access link with a client device served by a corresponding active leaf node device, and configure a primary/secondary device protection path with the corresponding active leaf node device.
In the above scheme, the fault detection module is specifically configured to receive network information sent by the path configuration module, determine whether the main leaf node device fails according to a receiving condition of a fault detection packet in the network information, and simultaneously determine whether a fault notification sent by the corresponding main leaf node device is received, and if the main leaf node device fails and does not receive the fault notification sent by the main leaf node device, determine that the main leaf node device or a branch path where the main leaf node device is located does not fail;
if the main leaf node equipment fails, judging that the main leaf node equipment fails;
and if the fault notification sent by the main leaf node equipment is received, determining whether the fault type is that the transmission path of the main leaf node fails or the access link of the main leaf node fails according to the fault notification.
In the above scheme, the control module is specifically configured to determine, according to a fault type of the primary leaf node device, whether to use the backup access link or the primary and secondary device protection path to protect the multicast service, and then notify the path configuration module to send the multicast service to the corresponding receiving end device served by the primary leaf node device using the backup access link or the primary and secondary device protection path;
correspondingly, the path configuration module is further configured to receive a notification sent by the control module, where the notification is sent by using the backup access link or the active/standby device protection path to send the multicast service to the receiving end device served by the corresponding active leaf node device.
In the foregoing solution, the control module is specifically configured to, if it is determined according to the failure notification that the transmission path of the active leaf node has a failure in the failure type, notify the path configuration module to send the multicast service to the active leaf node device using the active-standby device protection path when the network device serving as the standby network device is a leaf node device in a P2MP multicast transmission network; when the network device as the standby network device is not a leaf node device in the P2MP multicast transmission network, the notification path configuration module acquires the multicast service from the leaf node device in the P2MP multicast transmission network, and sends the multicast service to the active leaf node device by using the active/standby device protection path;
if the access link of the main leaf node is judged to have a fault according to the fault notice, the notification path configuration module receives the multicast service sent by the main leaf node device, and sends the received multicast service to the client device served by the main leaf node device by using the backup access link;
if the main leaf node device is judged to have a fault and the network device is the leaf node device in the P2MP multicast transmission network, the notification path configuration module sends the received multicast service to the corresponding receiving end device served by the main leaf node device by using the backup access link; if it is determined that the active leaf node device fails and the network device is not a leaf node device in the P2MP multicast transmission network, the notification path configuration module acquires a multicast service from the leaf node device in the P2MP multicast transmission network, and sends the multicast service to a receiving end device served by the active leaf node device using a backup access link.
According to the protection method and the network equipment for the P2MP multicast service, when the standby network equipment detects that the corresponding main leaf node equipment or the branch path where the main leaf node equipment is located has a fault, the multicast service is protected, so that a large amount of network establishment cost consumed for establishing a large amount of protection paths in a transmission network can be avoided; in addition, because the invention can directly determine whether to protect the multicast service by using the protection path by the standby network equipment, the P2MP multicast service can be protected by using a simple protection path.
Drawings
Fig. 1 is a schematic flow chart of a protection method for P2MP multicast service according to the present invention;
fig. 2 is a diagram of a backup access link in a P2MP multicast transmission network;
fig. 3 is a diagram illustrating a backup access link in a P2MP multicast transmission network;
fig. 4 is a schematic diagram of the structure of the network device according to the present invention.
Detailed Description
The basic idea of the invention is: setting the network device as a standby network device, judging whether the corresponding main leaf node device or the branch path where the main leaf node device is located has a fault, and when determining that the corresponding main leaf node device or the branch path where the main leaf node device is located has the fault, the network device protects the multicast service by using the protection path.
The present invention will be described in further detail with reference to the accompanying drawings and specific embodiments.
As shown in fig. 1, the present invention provides a method for protecting P2MP multicast service, which includes the following steps:
step 101: when the selected network device is used as a standby network device of any active leaf node device in the P2MP multicast transmission network, the network device is set as a standby network device.
Here, the selected network device may be a leaf node device in the P2MP multicast transmission network, or may not be a leaf node device in the P2MP multicast transmission network;
the setting as a standby network device may include: storing the equipment information of the corresponding main leaf node equipment and the equipment information of the receiving end equipment served by the main leaf node equipment; the method for setting the network device and the content to be set are performed according to the prior art, and are not described herein.
Step 102: the network equipment accesses the transmission network and establishes a protection path.
Here, the protection path includes: the network equipment configures a backup access link with client equipment served by corresponding main leaf node equipment, and configures a main equipment protection path with the corresponding main leaf node equipment;
the backup access link is an access link between a standby network device and a corresponding active leaf node device, and may include: source node device information, link identification, destination node device information, and the like; the method for configuring the backup access link may be manually established by an operator, or may be implemented by using a path table preset in the network device, where the use of the path table and the table establishment method of the path table are both implemented by the prior art, and are not described herein again;
the configuration of the active/standby device protection path with the corresponding active leaf node device may be manually established by an operator, or may be implemented by using a path table preset in the network device, which are all the prior art, and are not described herein again.
In this step, the network device also executes a function in the network in addition to the function of the standby network device in the transmission network, and the network device also receives network information in real time in the transmission network and sends the network information to the corresponding network device, for example, as shown in fig. 2, where the network device 2 is used as the standby network device of the network device 1, and the network device 2 is also used as a leaf node device in the P2MP multicast transmission network, and the network device 2 receives the multicast service sent by the switching routing device and sends the multicast service to the corresponding receiving end device 2;
wherein the network information is: the network device is in the transmission network and receives the information sent by all other network devices.
Step 103: the network device judges whether the corresponding main leaf node device or the branch path where the main leaf node device is located has a fault in real time, if no fault occurs, the step 103 is executed repeatedly; otherwise, step 104 is performed.
Here, the determining whether the corresponding active leaf node device or the branch path where the active leaf node device is located fails includes: the network equipment receives a fault detection message sent by corresponding main leaf node equipment, judges whether the main leaf node equipment has a fault according to the condition of receiving the fault detection message and judges whether a fault notice sent by the corresponding main leaf node equipment is received;
if the main leaf node device does not have a fault and does not receive the fault notice sent by the main leaf node device, determining that the main leaf node device and the link of the main leaf node device do not have a fault;
if the main leaf node equipment fails, judging that the main leaf node equipment fails; if a fault notification sent by the main leaf node equipment is received, determining whether the fault type is that the transmission path of the main leaf node fails or the access link of the main leaf node fails according to the fault notification;
the transmission path is a path from a root node to the main leaf node equipment specified in the prior art; the access link is a path between the main leaf node equipment and the service client equipment thereof specified in the prior art;
the generation and sending method of the fault detection message is the prior art, and for example, the fault detection message can be a continuous detection and connection Verification (CC & CV, continuity Check & Connectivity Verification) message; the fault notification may include: the generation and transmission method of the fault type, the fault node information and the like is the prior art, and is not described herein.
The judging whether the main leaf node equipment fails according to the condition of receiving the fault detection message is that: the network equipment detects whether all network information received by the network equipment is fault detection messages sent by main leaf node equipment, if so, the time length between the fault detection messages sent by the main leaf node equipment and the fault detection messages sent by the main leaf node equipment is recorded, if the time length exceeds a preset time length threshold, the main leaf node equipment is judged to have faults, otherwise, the main leaf node equipment is judged not to have faults;
the duration threshold is a duration preset according to an actual situation, for example, the duration threshold may be preset to 3 seconds.
Step 104: the network equipment protects the multicast service by using the protection path.
Here, the protection of the multicast service is as follows: the network device determines whether to use the backup access link or the active/standby device protection path to protect the multicast service according to the fault type of the active leaf node device, and then sends the multicast service to the corresponding receiving end device served by the active leaf node device by using the backup access link or the active/standby device protection path, specifically:
if the network equipment judges that the fault type is the fault of the transmission path of the main leaf node according to the fault notice, when the network equipment serving as the standby network equipment is the leaf node equipment in the P2MP multicast transmission network, the multicast service received by the network equipment is copied, the multicast service is sent to the main leaf node equipment by using the main equipment protection path, and meanwhile, the network equipment sends the multicast service to the receiving end equipment served by the network equipment; when the network device serving as the standby network device is not a leaf node device in the P2MP multicast transmission network, the network device acquires a multicast service from the selected leaf node device, and sends the multicast service to the active leaf node device by using the active/standby device protection path;
if the network equipment judges that the fault type is that the access link of the main leaf node is in fault according to the fault notice, the network equipment receives the multicast service sent by the main leaf node equipment, uses the backup access link to send the received multicast service to the client equipment served by the main leaf node equipment, and simultaneously sends the multicast service to the receiving end equipment served by the network equipment;
if the network device judges that the main leaf node device has a fault, when the network device serving as the standby network device is the leaf node device in the P2MP multicast transmission network, the multicast service received by the network device is copied and sent to the receiving end device corresponding to the network device and the receiving end device served by the main leaf node device corresponding to the network device by using the backup access link; for example, as shown in fig. 2, where the network device 1 and the network device 2 are both in the same P2MP multicast transmission network and are leaf node devices, the network device 1 is a primary leaf node device, the network device 2 is configured as a standby network device of the network device 1, and after the network device 2 determines to open the backup access link, the received multicast service is simultaneously sent to the receiving end device 2 and the receiving end device 1 corresponding to the network device; when the network device serving as the standby network device is not a leaf node device in the P2MP multicast transmission network, the network device acquires the multicast service from the selected leaf node device, and sends the multicast service to the corresponding receiving end device served by the main leaf node device by using the backup access link; for example, as shown in fig. 3, where the network device 1 and the network device 3 are leaf node devices, the network device 1 is a standby network device configured by a main leaf node device and the network device 2 as the network device 1, and when the network device 2 determines that the network device 1 has a fault, the multicast service extracted from the network device 3 is sent to the receiving end device 1 served by the network device 1 by using a backup access link. The selected leaf node device may be selected according to leaf node device information preset in the network device.
After the step 104 is completed, the network device serving as the standby network device may further determine whether a failure removal packet sent by the corresponding primary leaf node device is received, and if so, stop protecting the multicast service, and execute step 103; otherwise, continuing to protect the multicast service.
In addition, in step 103, before the network device determines in real time whether the corresponding active leaf node device or the branch path where the active leaf node device is located fails, the active leaf node device further needs to perform the following operations:
step a: when the network device is determined to be the active leaf node device in the P2MP multicast transmission network, the network device is set as the active leaf node device.
Here, the network device is a leaf node device in a P2MP multicast transmission network;
the setting as the active leaf node device may include: and storing the equipment information of the corresponding standby network equipment and the equipment information of the receiving end equipment served by the main leaf node equipment.
Step b: and configuring a main/standby equipment protection path with the corresponding standby network equipment.
Here, the primary/standby device protection path may be manually established by an operator, or may be implemented by using a path table preset in the network device, which are all the prior art and are not described herein again.
Step c: when the tasks in the P2MP multicast transmission network are normally executed, the primary and standby device protection paths are used to periodically send fault detection messages to the corresponding standby network devices, and meanwhile, whether a branch path where the primary and standby device protection paths are located has a fault is judged according to the conditions of receiving the fault detection messages sent by the root node device and the receiving end device respectively, and if the fault occurs, a fault notification is sent to the corresponding standby network devices; if there is no failure, the tasks in the P2MP multicast transmission network are continuously executed.
Here, the determining whether the branch path where the self is located has a fault is: according to the time length judgment between the fault detection messages respectively sent by the root node equipment and the receiving end equipment,
if the time length between the fault detection messages sent by the root node equipment exceeds a preset time length threshold, judging that the self transmission path has a fault, notifying the fault of the transmission path of the main leaf node of the fault type of the corresponding standby network equipment to the fault of the corresponding standby network equipment, and sending the multicast service to the client equipment after receiving the multicast service sent by the corresponding network equipment;
if the time length between the fault detection messages sent by the receiving end equipment exceeds a preset time length threshold, judging that the self access link has a fault, notifying the fault of the access link of which the fault type is the main leaf node of the corresponding standby network equipment to the fault, and sending the multicast service received by the self to the corresponding standby network equipment.
The failure detection messages sent by the root node device and the receiving end device respectively can be set to be sent periodically by the root node device and the receiving end device, and can also be set to be sent periodically when a network manager determines to start the failure detection function. If the fault occurs, after sending the fault notification to the corresponding standby network device, the network management personnel also can repair and remove the network device, once the fault is removed, the network device is accessed to the P2MP multicast transmission network again as the main leaf node device, and sends a fault removal message to the corresponding standby network device.
The present invention also provides a network device, as shown in fig. 4, the network device includes: a path configuration module 21, a fault detection module 22 and a control module 23; wherein,
a path configuration module 21, configured to protect the multicast service by using a protection path when receiving a notification sent by the control module 23 to protect the multicast service;
a fault detection module 22, configured to determine whether a corresponding primary leaf node device or a branch path where the primary leaf node device is located fails, and when it is determined that the corresponding primary leaf node device or the branch path where the primary leaf node device is located fails, notify the control module 23 that the main leaf node device or the branch path where the primary leaf node device is located corresponding to the primary leaf node device fails;
the control module 23 is configured to, after the network device is set as a standby network device and receives the notification that the corresponding active leaf node device or the branch path where the active leaf node device is located fails, sent by the failure detection module 22, notify the path configuration module 21 to protect the multicast service.
The control module 23 is further configured to perform a standby network device setup when the selected network device is selected as a standby network device of any active leaf node device in the P2MP multicast transmission network.
The control module 23 is further configured to notify the path configuration module 21 to configure a backup access link with the client device served by the corresponding primary leaf node device and configure a primary/secondary device protection path with the corresponding primary leaf node device after the network device where the path configuration module is located is accessed to the transmission network; correspondingly, the path configuration module 21 is specifically configured to, after receiving the notification sent by the control module 23, configure a backup access link with a client device served by the corresponding active leaf node device, and configure a primary/secondary device protection path with the corresponding active leaf node device.
The path configuration module 21 is further configured to receive network information and send the received network information to a network device corresponding to the network information.
The path configuration module 21 is further configured to send the received network information to the corresponding network device and send the network information to the fault detection module 22; the failure detection module 22 is further configured to receive the network information sent by the path configuration module 21.
The failure detection module 22 is specifically configured to determine, by using the network information sent by the path configuration module 21, whether a failure occurs in the corresponding active leaf node device or in the branch path where the active leaf node device is located, and if no failure occurs, the control module 23 is notified that the links of the active leaf node device and the active leaf node device are not failed, otherwise, if the active leaf node device is failed, judging that the main leaf node device has a fault, if receiving a fault notice sent by the main leaf node device, determining whether the fault type is that the transmission path of the main leaf node fails or the access link of the main leaf node fails according to the fault notification, and notifying the control module 23 that the transmission path of the main leaf node device or the main leaf node device fails or the access link of the main leaf node fails; correspondingly, the control module 23 is specifically configured to protect the multicast service after receiving the notification that neither the link of the active leaf node device nor the link of the active leaf node device fails, or the transmission path of the active leaf node device or the active leaf node device fails, or the access link of the active leaf node fails, sent by the failure detection module 22.
The fault detection module 22 is specifically configured to determine whether the main leaf node device fails according to a receiving condition of a fault detection packet of the main leaf node device corresponding to the network information sent by the path configuration module 21, determine whether a fault notification sent by the main leaf node device exists in the network information sent by the path configuration module 21, and determine that the main leaf node device fails if the main leaf node device fails and does not receive the fault notification sent by the main leaf node device; otherwise, the main leaf node equipment is judged to have a fault.
The fault detection module 22 is specifically configured to determine whether the primary leaf node device fails according to a time length between each time a fault detection packet sent by the primary leaf node device is received, determine that the primary leaf node device fails if the time length exceeds a preset time length threshold, and determine that the primary leaf node device does not fail otherwise.
The control module 23 is specifically configured to, when protecting the multicast service, determine whether to use the backup access link or the active/standby device protection path to protect the multicast service according to the fault type of the active leaf node device, and then notify the path configuration module 21 to send the multicast service to the corresponding receiving end device served by the active leaf node device using the backup access link or the active/standby device protection path; correspondingly, the path configuration module 21 is further configured to receive a notification sent by the control module 23 that the multicast service is sent to a receiving end device served by the corresponding active leaf node device by using the backup access link or the active/standby device protection path;
the method specifically comprises the following steps:
if the control module 23 determines that the failure type is that the transmission path of the primary leaf node fails according to the failure notification, when the network device is a leaf node device in a P2MP multicast transmission network, the control module notifies the path configuration module 21 to copy the received multicast service, and sends the multicast service to the primary leaf node device by using the primary and secondary device protection paths, and simultaneously sends the multicast service to the receiving end device served by the network device; when the network device is not a leaf node device in the P2MP multicast transmission network, notifying the path configuration module 21 to acquire a multicast service from the selected leaf node device, and sending the multicast service to the active leaf node device by using the active/standby device protection path;
if the control module 23 determines that the access link of the main leaf node has a fault according to the fault notification, it notifies the path configuration module 21 to receive the multicast service sent by the main leaf node device, and sends the received multicast service to the client device served by the main leaf node device and simultaneously sends the multicast service to the receiving device served by the network device by using the backup access link;
if the control module 23 determines that the active leaf node device fails, when the network device of the standby network device is a leaf node device in a P2MP multicast transmission network, the notification path configuration module 21 copies the received multicast service, and sends the copy service to the receiving end device corresponding to the network device and the receiving end device served by the active leaf node device corresponding to the network device by using the backup access link; when the network device of the standby network device is not a leaf node device in the P2MP multicast transmission network, the notification path configuration module 21 acquires the multicast service from the selected leaf node device, and sends the multicast service to the receiving end device served by the corresponding active leaf node device by using the backup access link.
The path configuration module 21 is further configured to determine whether a failure elimination packet sent by the corresponding primary leaf node device is received, and if so, send the failure elimination packet to the control module 23, otherwise, do not perform an operation; correspondingly, the control module 23 is further configured to stop protecting the multicast service after receiving the failure removal message sent by the path configuration module 21.
The control module 23 is further configured to, when it is determined that the network device is a primary leaf node device in the P2MP multicast transmission network, set the primary leaf node device, store configuration information of the primary leaf node device, and notify the path configuration module 21 and a corresponding standby network device to configure a primary-standby device protection path; correspondingly, the path configuration module 21 is further configured to receive a notification sent by the control module 23 that the main/standby device protection path is configured with the corresponding standby network device, and configure the main/standby device protection path with the corresponding standby network device.
The control module 23 is further configured to, when the network device in which the network device is located serves as a primary leaf node device, establish a detection link, and notify the fault detection module 22 to periodically send a fault detection packet to the path configuration module 21; correspondingly, the fault detection module 22 is further configured to receive a notification sent by the control module 23 that the fault detection message is periodically sent, and periodically send the fault detection message to the path configuration module 21; the path configuration module 21 is further configured to send the fault detection packet to the corresponding standby network device after receiving the fault detection packet sent by the fault detection module 22.
The fault detection module 22 is further configured to determine whether a branch path where the branch path is located has a fault according to a status of a fault detection packet in the network information sent by the path configuration module 21, send a fault notification to a corresponding standby network device if the branch path has a fault, and do not perform an operation if the branch path has no fault;
wherein, the judging whether the own link fails according to the condition of receiving the fault detection message is that: judging according to the time length between fault detection messages respectively sent by the root node equipment and the receiving end equipment after each time of receiving, if the time length between the fault detection messages sent by the root node equipment exceeds a preset time length threshold, judging that the self transmission path has a fault, and notifying the fault of the transmission path of the main leaf node of the fault type of the corresponding standby network equipment; if the time length between the fault detection messages sent by the receiving end equipment exceeds a preset time length threshold, judging that the self access link has a fault, notifying the fault of the access link of which the fault type is the main leaf node of the corresponding standby network equipment to the fault, and sending the multicast service received by the self to the corresponding standby network equipment.
The above description is only a preferred embodiment of the present invention, and is not intended to limit the scope of the present invention.

Claims (8)

1. A method for protecting a point-to-multipoint P2MP multicast service, the method comprising:
setting a network device as a standby network device, wherein the network device judges whether a corresponding main leaf node device or a branch path where the main leaf node device is located has a fault, and when the corresponding main leaf node device or the branch path where the main leaf node device is located has the fault, the network device protects the multicast service by using a protection path;
the determining whether the corresponding main leaf node device or the branch path where the main leaf node device is located fails includes: the network equipment is used as standby network equipment for receiving a fault detection message sent by corresponding main leaf node equipment, judging whether the main leaf node equipment has a fault according to the condition of receiving the fault detection message, and judging whether a fault notice sent by the corresponding main leaf node equipment is received; wherein,
the protecting the multicast service by using the protection path includes:
if the network equipment judges that the fault type is the fault of the transmission path of the main leaf node according to the fault notification, when the network equipment serving as the standby network equipment is the leaf node equipment in the P2MP multicast transmission network, the multicast service is sent to the main leaf node equipment by using the main equipment protection path; when the network device serving as the standby network device is not a leaf node device in the P2MP multicast transmission network, the network device acquires a multicast service from the leaf node device in the P2MP multicast transmission network, and sends the multicast service to the active leaf node device by using the active/standby device protection path;
if the network equipment judges that the fault type is that the access link of the main leaf node is in fault according to the fault notice, the network equipment receives the multicast service sent by the main leaf node equipment, and sends the received multicast service to the client equipment served by the main leaf node equipment by using the backup access link;
if the network device determines that the primary leaf node device has a fault and the network device is a leaf node device in a P2MP multicast transmission network, the network device sends the multicast service received by the network device to a client device served by the primary leaf node device corresponding to the network device by using a backup access link; if the network device determines that the active leaf node device fails and the network device is not a leaf node device in the P2MP multicast transmission network, the network device obtains a multicast service from the leaf node device in the P2MP multicast transmission network, and sends the multicast service to a client device served by the active leaf node device using a backup access link.
2. The method of claim 1, wherein before determining whether the corresponding active leaf node device or the branch path where the active leaf node device is located fails, the method further comprises: and configuring a protection path.
3. The method of claim 1 or 2, wherein the protection path is:
the network device and the backup access link configured by the client device served by the corresponding main leaf node device, and the main and backup device protection path configured by the corresponding main leaf node device.
4. The method according to claim 1 or 2, wherein the determining whether the corresponding active leaf node device or the branch path where the active leaf node device is located fails further includes:
if the main leaf node device does not have a fault and does not receive a fault notice sent by the main leaf node device, determining that the main leaf node device or a branch path where the main leaf node device is located does not have a fault;
if the main leaf node equipment fails, judging that the main leaf node equipment fails;
and if the fault notification sent by the main leaf node equipment is received, determining whether the fault type is that the transmission path of the main leaf node fails or the access link of the main leaf node fails according to the fault notification.
5. A network device, characterized in that the network device comprises: the system comprises a path configuration module, a fault detection module and a control module; wherein,
the path configuration module is used for protecting the multicast service by using the protection path when receiving the notification for protecting the multicast service sent by the control module;
a fault detection module, configured to receive network information sent by the path configuration module, determine whether a primary leaf node device fails according to a receiving condition of a fault detection packet in the network information, determine whether a fault notification sent by a corresponding primary leaf node device is received, determine whether a branch path where the corresponding primary leaf node device or the primary leaf node device is located fails, and notify the control module that a branch path where the primary leaf node device or the primary leaf node device corresponding to the primary leaf node device fails when it is determined that the branch path where the corresponding primary leaf node device or the primary leaf node device is located fails;
the control module is used for notifying the path configuration module to protect the multicast service after receiving the notification that the corresponding main leaf node device or the branch path where the main leaf node device is located fails, which is sent by the failure detection module, after the network device is set as a standby network device; wherein,
the control module is specifically configured to, if it is determined according to the fault notification that the transmission path of the active leaf node has a fault in the fault type, notify the path configuration module to send the multicast service to the active leaf node device using the active-standby device protection path when the network device serving as the standby network device is a leaf node device in a P2MP multicast transmission network; when the network device as the standby network device is not a leaf node device in the P2MP multicast transmission network, the notification path configuration module acquires the multicast service from the leaf node device in the P2MP multicast transmission network, and sends the multicast service to the active leaf node device by using the active/standby device protection path;
if the access link of the main leaf node is judged to have a fault according to the fault notice, the notification path configuration module receives the multicast service sent by the main leaf node device, and sends the received multicast service to the client device served by the main leaf node device by using the backup access link;
if the main leaf node device is judged to have a fault and the network device is the leaf node device in the P2MP multicast transmission network, the notification path configuration module sends the received multicast service to the client device served by the corresponding main leaf node device by using the backup access link; if it is determined that the active leaf node device fails and the network device is not a leaf node device in the P2MP multicast transmission network, the notification path configuration module acquires a multicast service from the leaf node device in the P2MP multicast transmission network, and sends the multicast service to the client device served by the active leaf node device using the backup access link.
6. The network device of claim 5,
the path configuration module is further used for configuring a protection path.
7. The network device of claim 6,
the path configuration module is specifically configured to configure a backup access link with a client device served by the corresponding active leaf node device, and configure a protection path of the active and standby device with the corresponding active leaf node device.
8. The network device of claim 5,
the fault detection module is further configured to:
if the main leaf node device does not have a fault and does not receive a fault notice sent by the main leaf node device, determining that the main leaf node device or a branch path where the main leaf node device is located does not have a fault;
if the main leaf node equipment fails, judging that the main leaf node equipment fails;
and if the fault notification sent by the main leaf node equipment is received, determining whether the fault type is that the transmission path of the main leaf node fails or the access link of the main leaf node fails according to the fault notification.
CN201110451318.8A 2011-12-29 2011-12-29 Protection method for point-to-multipoint multicast service and network equipment Expired - Fee Related CN102447569B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201110451318.8A CN102447569B (en) 2011-12-29 2011-12-29 Protection method for point-to-multipoint multicast service and network equipment

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201110451318.8A CN102447569B (en) 2011-12-29 2011-12-29 Protection method for point-to-multipoint multicast service and network equipment

Publications (2)

Publication Number Publication Date
CN102447569A CN102447569A (en) 2012-05-09
CN102447569B true CN102447569B (en) 2015-06-03

Family

ID=46009677

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201110451318.8A Expired - Fee Related CN102447569B (en) 2011-12-29 2011-12-29 Protection method for point-to-multipoint multicast service and network equipment

Country Status (1)

Country Link
CN (1) CN102447569B (en)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106302165A (en) * 2015-05-22 2017-01-04 中兴通讯股份有限公司 The guard method of a kind of point-to-multi-point tunnel and device
CN105490935A (en) * 2015-12-08 2016-04-13 国网浙江省电力公司宁波供电公司 Method and system for analyzing paths among multiple points

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1946040A (en) * 2006-10-13 2007-04-11 华为技术有限公司 Protective method and device for multicast service
CN101656679A (en) * 2009-09-25 2010-02-24 华为技术有限公司 Method for rapidly converging multicast, router and communication system
CN101674199A (en) * 2009-09-22 2010-03-17 中兴通讯股份有限公司 Method for realizing switching during network fault and finders
CN102195848A (en) * 2010-03-10 2011-09-21 中兴通讯股份有限公司 Multicast service stream protection realization method, device and system
WO2011144088A2 (en) * 2011-05-26 2011-11-24 华为技术有限公司 Method for service protection and access device

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101483558B (en) * 2008-01-10 2012-07-04 华为技术有限公司 Method, system and apparatus for packet switching network access by network appliance

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1946040A (en) * 2006-10-13 2007-04-11 华为技术有限公司 Protective method and device for multicast service
CN101674199A (en) * 2009-09-22 2010-03-17 中兴通讯股份有限公司 Method for realizing switching during network fault and finders
CN101656679A (en) * 2009-09-25 2010-02-24 华为技术有限公司 Method for rapidly converging multicast, router and communication system
CN102195848A (en) * 2010-03-10 2011-09-21 中兴通讯股份有限公司 Multicast service stream protection realization method, device and system
WO2011144088A2 (en) * 2011-05-26 2011-11-24 华为技术有限公司 Method for service protection and access device

Also Published As

Publication number Publication date
CN102447569A (en) 2012-05-09

Similar Documents

Publication Publication Date Title
CN100512292C (en) Apparatus and method of real-time recovering service
CN108965123B (en) Link switching method and network communication system
US7869376B2 (en) Communicating an operational state of a transport service
JP5350461B2 (en) Enhanced traffic indication in connection failure management
US8886831B2 (en) System and methodology for fast link failover based on remote upstream failures
US8117337B2 (en) Method and device for implementing link pass through in point-to-multipoint network
CN101610535B (en) Method, system and device for ensuring BFD conversation stability on the scene of multilink direct connection
CN104301146A (en) Link switching method and device in software defined network
CN104980372A (en) Relay System And Switching Device
CN101860492A (en) Quick switching method, device and system
CN106789630B (en) A kind of network protection method and system, controller, equipment
CN105429814B (en) Method and equipment for protecting BFD (bidirectional forwarding detection) by using multiple board cards
CN107342809B (en) Service performance monitoring and fault positioning method and device
CN102780615B (en) Link backup method and routing forwarding device
CN103490921B (en) Network protection method, device, lower link point and system
CN102868569A (en) Method, node and system for detecting performance of three-layer virtual private network
WO2011095101A1 (en) Linear 1: n protection method, device and system for packet transport network
US8477655B2 (en) Method, device, and system for establishing label switching path in fast rerouting switching
CN102820990A (en) Method and device for switching service protection
CN102891769A (en) Link fault informing method and apparatus
CN101777997A (en) Method and system for switching flow of network link
CN102238067B (en) Switching method and device on Rapid Ring Protection Protocol (RRPP) ring
EP2892180B1 (en) Service traffic protection method and apparatus
CN103036724B (en) State information transmission method, the network equipment and unit equipment
CN106330699B (en) Multicast link switching method and device and routing equipment

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
C10 Entry into substantive examination
SE01 Entry into force of request for substantive examination
C14 Grant of patent or utility model
GR01 Patent grant
CF01 Termination of patent right due to non-payment of annual fee
CF01 Termination of patent right due to non-payment of annual fee

Granted publication date: 20150603

Termination date: 20191229