Classifications

• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L49/00—Packet switching elements
  • H04L49/20—Support for services
  • H04L49/201—Multicast operation; Broadcast operation
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L12/00—Data switching networks
  • H04L12/02—Details
  • H04L12/16—Arrangements for providing special services to substations
  • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L12/00—Data switching networks
  • H04L12/02—Details
  • H04L12/16—Arrangements for providing special services to substations
  • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
  • H04L12/1854—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast with non-centralised forwarding system, e.g. chaincast
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L45/00—Routing or path finding of packets in data switching networks
  • H04L45/16—Multipoint routing
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L45/00—Routing or path finding of packets in data switching networks
  • H04L45/58—Association of routers
  • H04L45/586—Association of routers of virtual routers
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L49/00—Packet switching elements
  • H04L49/70—Virtual switches
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L12/00—Data switching networks
  • H04L12/02—Details
  • H04L12/16—Arrangements for providing special services to substations
  • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
  • H04L12/1886—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast with traffic restrictions for efficiency improvement, e.g. involving subnets or subdomains

Definitions

• a traditional network architecture has a hierarchical structure of two layers or multiple layers. As shown in FIG. 1 , according to functions and deployment locations of layers, networks can be divided into different layers (including core layer, aggregation layer, and edge access). Layers and peers). Dual-homed redundant connections are usually used between layers to improve reliability and aggregate user traffic layer by layer.
• the access layer is responsible for the network access of the user terminal, and is used to provide a rich user interface type.
• the nodes are widely distributed and the interface density is large.
• the aggregation layer is responsible for aggregating the access node traffic, and is used to expand the service coverage of the core node.
• the type is rich, the aggregation ability is strong, and the integrated service processing capability is available; the core layer is responsible for high-speed forwarding, inter-area service interworking, and the number of nodes is small.
• the existing network architecture uses two or more switching master devices in the same network layer to form a virtual network device when processing point-to-multipoint exchange messages. Ways to reduce the complexity of using multiple redundant components.
• the existing hardware cluster routers connect multiple high-end routers to the central switching matrix chassis through ultra-short-range optical fibers, which constitutes one to four, two to eight, or Four-draft sixteen large-scale cluster routers. Due to the introduction of a dedicated central switching matrix machine and ultra-short-range fiber interconnection technology, the network topology is complex, and route convergence and stability are poor.
• the embodiment of the invention provides a multicast packet processing method and device, which implements efficient and reliable routing and forwarding of multicast packets in a virtual aggregated cluster routing system.
• the embodiment of the present invention provides the following technical solutions:
• the embodiment of the invention provides a multicast packet processing method, including: Receive multicast packets;
• An embodiment of the present invention provides a multicast packet processing apparatus, including:
• a receiving unit configured to receive a multicast packet
• An obtaining unit configured to obtain, according to the multicast routing entry carried in the multicast packet received by the receiving unit, a local router interface corresponding to the multicast packet;
• a forwarding unit configured to forward the multicast packet received by the receiving unit to the local router interface obtained by the acquiring unit, and forward the packet to the cluster routing system interface for sending.
• the embodiment of the present invention can obtain a local router interface corresponding to the multicast packet according to the multicast routing entry carried in the multicast packet, and then forward the multicast packet to the cluster through the local router interface.
• the routing system interface sends.
• a plurality of routing devices can be clustered into a virtual routing system, and the external routing function is a separate routing node that supports the multicast service, so that the multicast packets can be efficiently and reliably implemented in the virtualized cluster routing system. Routing and forwarding enables the cluster routing system to support multicast services with high efficiency and high quality.
• Figure 1 is a schematic diagram of the hierarchical structure of a traditional network architecture
• FIG. 2 is a schematic flowchart of a method for processing a multicast packet according to an embodiment of the present invention
• FIG. 3 is a schematic diagram of interface distribution of a cluster routing system according to an embodiment of the present invention.
• FIG. 4 is a schematic flowchart of another multicast packet processing method according to an embodiment of the present disclosure.
• FIG. 5 is a schematic diagram of interface distribution of another cluster routing system according to an embodiment of the present disclosure.
• FIG. 6 is a schematic flowchart of another multicast packet processing method according to an embodiment of the present disclosure.
• FIG. 7 is a schematic flowchart of another method for processing a multicast packet according to an embodiment of the present invention
• FIG. 8 is a schematic structural diagram of a multicast packet processing apparatus according to an embodiment of the present invention
• FIG. 9 is a schematic structural diagram of another multicast packet processing apparatus according to an embodiment of the present disclosure
• FIG. 10 is a schematic structural diagram of another multicast packet processing apparatus according to an embodiment of the present disclosure
• FIG. 11 is a schematic structural diagram of still another multicast packet processing apparatus according to an embodiment of the present invention.
• Embodiment 1 is a schematic structural diagram of still another multicast packet processing apparatus according to an embodiment of the present invention. The embodiments of the present invention will be further described in detail with reference to the drawings and specific embodiments.
• Embodiment 1 is a schematic structural diagram of still another multicast packet processing apparatus according to an embodiment of the present invention. The embodiments of the present invention will be further described in detail with reference to the drawings and specific embodiments. Embodiment 1:
• FIG. 2 is a schematic flowchart of a method for processing a multicast packet according to Embodiment 1 of the present invention. As shown in FIG. 2, the method may include:
• the multicast packet received in the foregoing 101 may carry a multicast routing entry, and the expression of the multicast routing entry may be (S, G), where S is a source address, G is a group address, or may be (*) , G) , where * is any source address and G is the group address.
• the cluster routing system interface corresponding to the multicast packet is obtained by querying the external multicast forwarding information base (eMFIB).
• eMFIB external multicast forwarding information base
• the correspondence between the multicast routing entries (S, G) and the cluster routing system interface is pre-established in eMFIB.
• the internal forwarding information base may be further queried to obtain a local router interface corresponding to the multicast packet.
• the corresponding relationship between the cluster routing system interface and the local router interface in the cluster routing system is pre-established in the IFIB.
• a master node and a plurality of slave nodes may be included, and the master node is connected to each slave node.
• the primary node can be a high-capacity high-performance router
• the secondary node can be a small-capacity, low-performance router.
• the edge interface of the master node and the slave node connected to the cluster routing system is the cluster routing system interface; the interface connecting the master node and the slave node is the inner interface; all interfaces of the master node or the slave node are local router interfaces;
• the interface can also be the interface of the cluster routing system.
• the interface is called the inbound interface and the outbound interface.
• the eMFIB and the IFIB may be stored in each of the local routers in the cluster routing system, so that when any local router receives the externally received multicast packet carrying the multicast routing entry, the multicast packet may be
• the multicast routing entries carried in the file are respectively queried by the eMFIB and the IFIB to obtain the local router interface corresponding to the multicast packet, and the multicast packet is forwarded.
• the foregoing multicast packet is forwarded to the local router interface obtained by the obtained multicast packet, and then sent to the cluster routing system interface for sending.
• the value of the TTL (Time To Live) carried in the multicast packet can be reduced by 1.
• the identifier when the multicast packet is forwarded, the identifier may be encapsulated in the multicast packet, and the identifier may be an identifier of the interface of the cluster routing system, or an internal shared tree (1ST) identifier, and the 1ST identifier is The common identifier of the same multicast packet on the interface of the cluster routing system.
• the packet is encapsulated in the multicast packet to facilitate the rapid identification of the forwarding interface.
• the multicast packet is quickly forwarded from the corresponding interface to improve the forwarding speed.
• the multicast routing processing method provided by the embodiment of the present invention is not limited to the two-layer hierarchical tree topology in the embodiment, and is in a multi-hop multi-hop hierarchical tree topology and a ring topology. Both apply.
• the local router interface corresponding to the multicast packet is obtained according to the multicast routing entry carried in the multicast packet, and then the multicast packet is forwarded to the cluster routing system interface by using the local router interface.
• a plurality of routing devices can be clustered into a virtual routing system, and the external routing function is a separate routing node that supports the multicast service, so that the multicast packets can be efficiently and reliably implemented in the virtualized cluster routing system. Routing and forwarding enables the cluster routing system to support multicast services with high efficiency and high quality.
• FIG. 4 is a schematic flowchart of a method for processing a multicast packet according to Embodiment 2 of the present invention. As shown in FIG. 4, the method may include:
• the cluster routing system generates eMFIB.
• the eMFIB is used to store the correspondence between the multicast routing entry (S, G) and the cluster routing system interface.
• the cluster routing system can generate eMFIB by using, but not limited to, dynamic centralized mode and distributed generation mode.
• the specific implementation of generating eMFIB in a dynamic centralized manner is as follows:
• the cluster routing system is regarded as a routing node, shielding the internal interconnection mechanism of the cluster routing system, focusing only on The external connection port of the cluster routing system;
• the designated high-performance aggregation router main Rl is the master node, the main R1 supports the multicast routing calculation protocol (PIM-DM / PIM-SIM I MSDP / MBGP, etc.), and the slave nodes (R2, R3, R4) do not support any multicast. Route calculation protocol;
• the C-cluster routing system internally transmits the message: the slave node receives the neighbor message received from the external connection port (ExtP) of the cluster routing system, and reports the neighbor message to the master node (main R1) through the internal connection port (IntP);
• the master node (main R1) runs the multicast routing calculation protocol according to the neighbor information received from the external node of the slave node routing system ExtP, generates eMFIB, and performs corresponding multicast control function;
• El, eMFIB The primary node computes the generated eMFIB and sends it to the master and slave nodes in the cluster routing system.
• the cluster routing system is regarded as a routing node, which shields the internal interconnection mechanism of the cluster routing system, and only pays attention to the external connection port of the cluster routing system;
• Each node of the cluster routing system receives external neighbor information
• Each node supports the multicast routing calculation protocol (PIM-DM I PIM-SIM I MSDP I MBGP, etc.), and generates an external network topology map based on these neighbor information, and uses the cluster routing system as a The node calculates the routing table and generates eMFIB.
• PIM-DM I PIM-SIM I MSDP I MBGP etc.
• the node calculates the routing table and generates eMFIB.
• the eMFIB generated by the above 401 can be as shown in Table 1 below:
• the cluster routing system generates an internal forwarding information base IFIB.
• the form of the IFIB can be as shown in the following table.
• Table 2 is the IFIB of the main R1
• Table 3 is the IFIB from the R2
• Table 4 is the IFIB from the R3: Table 2 IFIB of the main Rl
• the primary R1 can obtain the outbound interface of the cluster routing system from the eMFIB shown in Table 1 according to the multicast routing entry (S1, 224. 1. 0. 0) carried in the multicast packet.
• the outgoing interface of the cluster routing system is ExtP21, ExtP22, and ExtP31. , ExtP32 ; and further, the local router interface corresponding to the multicast packet obtained from the IFIB shown in Table 2 above is ExtPl l , IntPl l , IntP12 0
• the foregoing 403 may establish a multicast routing entry according to the correspondence between the multicast routing entry and the cluster routing system interface (ie, eMFIB), and the correspondence between the cluster routing system interface and the local router interface inside the cluster routing system (ie, IFIB). Correspondence with the local router interface inside the cluster routing system is saved to the MFIB of each local router.
• eMFIB the correspondence between the multicast routing entry and the cluster routing system interface
• IFIB local router interface inside the cluster routing system
• the generation of MFIB can be generated by each node in the cluster routing system, or it can be generated by the master node for each node and delivered to the slave node.
• the MFIB of the primary R1 is generated, and the primary node R1 searches for the eMFIB shown in Table 1, and learns that the multicast routing entry needs to be entered from the cluster routing system interface ExtP11, and forwarded to the cluster routing system interface ExtP21, ExtP22, ExtP31, ExtP32 for transmission;
• the outbound interface of the cluster routing system is indexed to look up the IFIB of the primary R1 shown in Table 2. It is found that the ExtP21 and ExtP22 interfaces correspond to the IntPl interface of the local router; the ExtP31 and ExtP32 interfaces correspond to the IntP12 interface of the local router, and the IntPl l and IntP12 are MFIB.
• the local router outbound interface in the table use the cluster routing system inbound interface ExtPl l to look up the IFIB of the primary R1 shown in Table 2, and know that the local router outbound interface is ExtPl l, then it is the local router in the MFIB table.
• an entry of the MFIB table of the main R1 is generated, according to which By analogy, all entries of the MFIB of the primary R1 can be generated, as shown in Table 5 below:
• MFIB from R2 can be generated, as shown in Table 6. Look up the eMFIB shown in Table 1 from the node R2, and learn that the multicast routing entry needs to enter the cluster routing system from the ExtPl interface and forward it to the ExtP21, ExtP22, ExtP31, and ExtP32 interfaces to send out the cluster routing system interface; The outbound interface is indexed to look up the IFIB from R2 shown in Table 3.
• ExtP21 and ExtP22 interfaces respectively correspond to the ExtP21 interface and the ExtP22 interface of the local router
• ExtP31 and ExtP32 interfaces correspond to the IntP21 interface of the local router
• ExtP21, ExtP22, and IntP21 are The local router outbound interface in the MFIB table; use the cluster routing system inbound interface ExtPl l to look up the IFIB from R2 shown in Table 3, and know that the local router outbound interface is ExtP21, then it is the local router inbound interface in the MFIB table.
• an entry from the MFIB table of R2 is generated, and by analogy, all entries of the MFIB from R2 can be generated, as shown in the following table:
• the multicast packets corresponding to the interface of the at least two cluster routing systems are merged, and one copy is sent to the local router interface, and the suppression of the multicast packet is repeated. Copy, save energy.
• the primary R1 will go to the ExtP21, and the multicast packets of the ExtP22 interface will be copied and copied to the IntPl.
• the multicast packets destined for the ExtP31 and ExtP32 will be copied and copied to the IntP12 and sent to the IntP31.
• the default forwarding interface list is deleted to another local router.
• the interface is configured to prevent multicast packets from being repeatedly forwarded between several local routers, or the same multicast packet is forwarded by several local routers to form a loop, causing deadlocks and wasting system resources.
• the outbound interface of the multicast packet that is sent out to the ExtP31 and the ExtP32 interface is intP21, and the multicast packet enters the IntP21 from the inbound interface of the R2, and is not forwarded, and is preset in the MFIB from the R2.
• the outbound interface IntP21 is removed from the forwarding interface list.
• the outbound interface of the multicast packet that is sent out to the ExtP21 and the ExtP22 interface is in the intP31, and the multicast packet enters the inbound interface IntP31 of the R3, and is not forwarded.
• the interface IntP31 is removed from the MFIB of R3. From R2, the MFIB entry from R3 becomes as follows:
• the cluster routing system receives the multicast packet.
• the primary R1 in the cluster routing system receives the multicast packet carrying the multicast routing entry (S1, 224. 1. 0. 0).
• the TTL value carried in the multicast packet is decremented by 1.
• the embodiment of the present invention can implement the clustering of a plurality of routing devices into a virtual routing node, and combine the eMFIB and the IFIB to generate the MFIB, and then directly query the MFIB and then forward the multicast packet, thereby reducing the number of internal forwarding of the multicast packet. Improve routing convergence speed and stability, and reduce fault management complexity.
• FIG. 6 is a schematic flowchart of a multicast packet processing method according to Embodiment 3 of the present invention. As shown in FIG. 6, the method may include:
• the cluster routing system generates eMFIB.
• the cluster routing system generates an internal forwarding information base IFIB.
• the cluster routing system receives the multicast packet carrying the multicast routing entry.
• the cluster routing system interface obtained as the identifier is encapsulated in the multicast packet. 607. Send the encapsulated multicast packet to the corresponding local router through the obtained local router interface, so that the local router forwards the encapsulated multicast packet to the cluster routing system interface according to the identifier.
• the primary R1 can search for the eMFIB as shown in Table 1, and obtain the cluster routing system interface corresponding to the multicast packet;
• the obtained cluster routing system interface is used as an index to find the IFIB of the primary R1, and the local router interface corresponding to the multicast packet is obtained.
• the obtained cluster routing system interface is used as the identifier, encapsulated in the multicast packet, and then sent to the corresponding The local router forwards the encapsulated multicast packet to the cluster routing system interface through the local routing interface according to the identifier.
• the corresponding local router searches for the local router interface of the corresponding local router according to the identifier of the multicast packet, and sends the encapsulated multicast packet to the next level corresponding to the obtained local router interface.
• the local router and so on, forwards the encapsulated multicast packets to the cluster routing system interface for transmission.
• the identifier can enable the slave node to send the packet to the interface based on the outbound interface of the cluster routing system as shown in the identifier to improve forwarding efficiency.
• the interface of the multicast packet to the other local router is the same interface as the interface of the current local router, the IFIB or the preset forwarding interface list is deleted.
• the interface to another local router is used to prevent multicast packets from being repeatedly forwarded between several local routers.
• the same multicast packet is forwarded by several local routers in sequence, causing a deadlock and wasting system resources.
• the identifier is removed from the multicast packet and the TTL value carried by the multicast packet is decremented by one.
• the embodiment of the present invention can encapsulate the cluster router interface as an identifier in the multicast packet and send it to the local router, so that the local router can be configured according to the local router.
• the device forwards the multicast packets to the cluster routing system interface to prevent the local routers from querying the eMFIB. This improves the forwarding efficiency and reduces the number of internal multicast forwardings. , reduce the complexity of fault management.
• Embodiment 4
• FIG. 7 is a schematic flowchart of a method for processing a multicast packet according to Embodiment 4 of the present invention. As shown in FIG. 7, the method may include:
• the cluster routing system generates eMFIB.
• the cluster routing system generates an internal forwarding information base IFIB.
• the same multicast routing entry (S, G) and (*, G) entries of the cluster routing system interface can be combined, and the 1ST identifier is assigned, as shown in Table 10;
• the above-mentioned 701 generates eMFIB
• 702 generates IFIB
• 703 generates an internal shared tree identifier without a prior order limitation, and the subsequent embodiments are also the same.
• the generation of the internal multicast forwarding information base is basically the same as that of the 403 using the eMFIB and the IFIB generated and simplifying the multicast forwarding information base in the foregoing embodiment, except that the internal shared tree identifier 1ST is used instead of the cluster routing system interface.
• the IMFIB for storing the correspondence between the internal shared tree identifier 1ST and the local router interface inside the cluster routing system can be as shown in Table 11 below:
• the cluster routing system receives the multicast packet carrying the multicast routing entry.
• the internal shared tree identifier can be obtained from Table 10.
• the local router forwards the multicast packet that encapsulates the internal shared tree identifier to the cluster routing system interface according to the internal shared tree identifier.
• the corresponding local router searches for the local router interface of the corresponding local router according to the internal shared tree identifier of the multicast packet, and obtains the local router interface of the corresponding local router, and sends the multicast packet encapsulated by the internal shared tree to the obtained local router interface.
• the identifier is removed from the multicast packet.
• the TTL (Time To Live) value carried in the multicast packet can be decremented by one.
• the IFIB or the preset forwarding interface list is deleted to another The interface of the local router is used to prevent multicast packets from being repeatedly forwarded between several local routers.
• the same multicast packet is forwarded by several local routers to form a loop, causing deadlock and wasting system resources.
• the embodiment of the present invention combines the same multicast routing entry of the cluster routing system interface, thereby reducing the number of entries in the internal multicast forwarding information base, improving the forwarding efficiency, and reducing the number of internal forwarding of multicast packets and improving routing. Convergence speed and stability reduce fault management complexity.
• the embodiment of the present invention provides several multicast packet processing devices. For details, refer to the following embodiments.
• Embodiment 5 is a diagrammatic representation of Embodiment 5:
• FIG. 8 is a schematic structural diagram of a multicast packet processing apparatus according to Embodiment 5 of the present invention. As shown in Figure 8, the device can include:
• the receiving unit 801 is configured to receive a multicast packet.
• the obtaining unit 802 is configured to obtain, according to the multicast routing entry carried in the multicast packet received by the receiving unit 801, the local router interface corresponding to the multicast packet.
• the forwarding unit 803 is configured to forward the multicast packet received by the receiving unit 801 to the local router interface obtained by the obtaining unit 803, and forward the packet to the cluster routing system interface for transmission.
• the multicast packet processing apparatus can implement a virtual aggregation of multicast packets by using a plurality of routing devices to be a virtual routing system. Efficient and reliable routing and forwarding within the cluster routing system enables the cluster routing system to support multicast services with high efficiency and high quality.
• FIG. 9 is a schematic structural diagram of another multicast packet processing apparatus according to Embodiment 5 of the present invention.
• the multicast packet processing device shown in FIG. 9 adds the following unit:
• the first establishing unit 804 is configured to: before receiving the multicast packet, the receiving unit 801, according to The correspondence between the multicast routing entry and the cluster routing system interface, and the correspondence between the cluster routing system interface and the local router interface in the cluster routing system establishes a correspondence between the multicast routing entry and the local router interface inside the cluster routing system;
• the corresponding relationship between the multicast routing entry established by the first establishing unit 804 and the local router interface in the cluster routing system may be the same as that in Table 2, Table 3 and Table 4 in the foregoing embodiment, and is not described in this embodiment.
• the first saving unit 805 is configured to save the correspondence between the multicast routing entry established by the first establishing unit and the local router interface in the cluster routing system to the multicast forwarding information base MFIB of each local router;
• the MFIB may be the same as Table 5, Table 6, and Table 7 in the foregoing embodiment, and the embodiment is not repeated.
• the obtaining unit 802 can specifically query the multicast forwarding information base MFIB according to the multicast routing entry carried in the multicast packet received by the receiving unit 801, and obtain the local router interface corresponding to the multicast packet.
• the multicast packets corresponding to at least two cluster routing system interfaces are merged, and one copy is sent to the local router interface, and the multicast packet is suppressed.
• the text is repeatedly copied to save energy.
• the default forwarding interface list is deleted to another local router.
• the interface is configured to prevent multicast packets from being repeatedly forwarded between several local routers, or the same multicast packet is forwarded by several local routers to form a loop, causing deadlocks and wasting system resources.
• FIG. 10 is a schematic structural diagram of another multicast packet processing apparatus according to Embodiment 5 of the present invention.
• the obtaining unit 802 may include:
• the first obtaining sub-unit 8021 is configured to obtain, according to the multicast routing entry carried in the multicast packet received by the receiving unit 801, the cluster routing corresponding to the multicast packet from the correspondence between the multicast routing entry and the interface of the cluster routing system.
• System interface
• the correspondence between the multicast routing entry and the cluster routing system interface may be stored in the eMFIB as described in the foregoing embodiment.
• the second obtaining sub-unit 8022 is configured to obtain, according to the cluster routing system interface obtained by the first obtaining sub-unit 8021, the local corresponding to the multicast packet from the correspondence between the cluster routing system interface and the local router interface in the cluster routing system.
• Router interface obtained by the first obtaining sub-unit 8021, the local corresponding to the multicast packet from the correspondence between the cluster routing system interface and the local router interface in the cluster routing system.
• the correspondence between the cluster routing system interface and the local router interface inside the cluster routing system may be saved in the IFIB mentioned in the foregoing embodiment.
• the forwarding unit 803 may include:
• the first encapsulation sub-unit 8031 is configured to encapsulate the interface of the cluster routing system obtained by the first obtaining sub-unit 8021 as an identifier, and encapsulate the packet on the multicast packet.
• the first forwarding sub-unit 8032 is configured to send the encapsulated identifier multicast packet to the corresponding local router through the local router interface obtained by the second obtaining sub-unit 8022, so that the corresponding local router encapsulates the identified group according to the identifier.
• the broadcast message is forwarded to the cluster routing system interface for transmission.
• the corresponding local router searches for the local router interface of the corresponding local router according to the identifier of the multicast packet, and sends the encapsulated multicast packet to the next level through the obtained local router interface. Corresponding local routers, and so on, until the encapsulated multicast packets are forwarded to the cluster routing system interface for transmission.
• the above-mentioned identifier can enable the slave node in the device to directly find the outbound interface of the cluster routing system or the local router, and quickly send the packet to the interface to save energy.
• FIG. 11 is a schematic structural diagram of another multicast packet processing apparatus according to Embodiment 5 of the present invention.
• the multicast packet processing device shown in FIG. 11 adds the following unit:
• the processing unit 806 is configured to: before the receiving unit 801 receives the multicast packet, route the cluster.
• the multicast routing entries with the same system interface are merged, the corresponding internal shared tree identifier 1ST is allocated, and the correspondence between the multicast routing entry and the internal shared tree identifier 1ST is saved.
• the correspondence between the multicast routing entry and the internal shared tree identifier 1ST saved by the processing unit 806 may be the same as that of the table 10 in the foregoing embodiment, and is not described in this embodiment.
• the second establishing unit 807 is configured to: according to the correspondence between the multicast routing entry and the internal shared tree identifier 1ST, the correspondence between the multicast routing entry and the cluster routing system interface, and the locality of the cluster routing system interface and the cluster routing system Corresponding relationship between the router interface establishes a correspondence between the internal shared tree identifier 1ST and a local router interface inside the cluster routing system;
• the corresponding relationship between the internal shared tree identifier 1ST established by the second establishing unit 807 and the local router interface in the cluster routing system may be the same as that of the table 11 in the foregoing embodiment, and is not described in this embodiment.
• the second saving unit 808 is configured to save the correspondence between the internal shared tree identifier 1ST established by the second establishing unit 807 and the local router interface in the cluster routing system to the internal multicast forwarding information base IMFIB of each local router;
• the obtaining unit 802 may obtain the internal shared tree identifier from the correspondence between the multicast routing entry and the internal shared tree identifier 1ST saved by the processing unit 806 according to the multicast routing entry carried in the multicast packet received by the receiving unit 801. 1ST, querying the internal multicast forwarding information base IMFIB according to the obtained internal shared tree identifier 1ST, obtained The local router interface corresponding to the foregoing multicast packet is obtained;
• the forwarding unit 803 may include:
• the second encapsulation sub-unit 8033 is configured to encapsulate the internal shared tree identifier 1ST obtained by the obtaining unit 802 on the multicast packet.
• the second forwarding sub-unit 8034 is configured to send the local router interface obtained by the internal shared tree identifier to the corresponding local router through the local router interface obtained by the obtaining unit 802, so that the corresponding local router encapsulates the identifier according to the internal shared tree identifier.
• the multicast packets identified by the internal shared tree are forwarded to the cluster routing system interface for transmission.
• the corresponding local router searches for the local router interface of the corresponding local router according to the internal shared tree identifier encapsulated in the multicast packet, and the multicast packet encapsulated by the internal shared tree is passed through the obtained local router.
• the interface is sent to the local router corresponding to the next level, and so on, until the multicast packet encapsulated in the internal shared tree is forwarded to the cluster routing system interface for transmission.
• the identifier is removed from the multicast packet.
• the multicast packet processing apparatus can implement a virtual aggregation of multicast packets by using a plurality of routing devices to be a virtual routing system. Efficient and reliable routing and forwarding within the cluster routing system enables the cluster routing system to support multicast services with high efficiency and high quality.
• the foregoing storage medium includes: a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like.
• ROM read-only memory
• RAM random access memory
• magnetic disk a magnetic disk
• optical disk a magnetic disk, or an optical disk, and the like.

Landscapes

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

Priority Applications (4)

Applications Claiming Priority (2)

Related Child Applications (1)

Publications (1)

Family

ID=44157033

Family Applications (1)

Country Status (5)

Cited By (2)

Families Citing this family (9)

Citations (4)

Family Cites Families (20)

• 2009
  • 2009-12-22 CN CN2009102543590A patent/CN102104488B/zh not_active Expired - Fee Related
• 2010
  • 2010-12-09 JP JP2012545065A patent/JP5455139B2/ja not_active Expired - Fee Related
  • 2010-12-09 WO PCT/CN2010/079609 patent/WO2011076065A1/zh not_active Ceased
  • 2010-12-09 EP EP10838628.5A patent/EP2518949B1/en not_active Not-in-force
• 2012
  • 2012-06-20 US US13/528,586 patent/US9191311B2/en not_active Expired - Fee Related
• 2015
  • 2015-10-15 US US14/884,243 patent/US9973443B2/en active Active

Patent Citations (4)

Also Published As

Similar Documents

Legal Events