WO2008095435A1 - Multicast method and multicast routing method - Google Patents

Multicast method and multicast routing method Download PDF

Info

Publication number
WO2008095435A1
WO2008095435A1 PCT/CN2008/070187 CN2008070187W WO2008095435A1 WO 2008095435 A1 WO2008095435 A1 WO 2008095435A1 CN 2008070187 W CN2008070187 W CN 2008070187W WO 2008095435 A1 WO2008095435 A1 WO 2008095435A1
Authority
WO
WIPO (PCT)
Prior art keywords
multicast
forwarding
network node
equivalence class
guide information
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2008/070187
Other languages
English (en)
French (fr)
Inventor
Feng Guo
Yi Xiong
Weisi Dong
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to EP08706564A priority Critical patent/EP2109260A4/en
Publication of WO2008095435A1 publication Critical patent/WO2008095435A1/zh
Priority to US12/267,296 priority patent/US8009671B2/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/02Details
    • H04L12/16Arrangements for providing special services to substations
    • H04L12/18Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H04L12/1854Arrangements for providing special services to substations for broadcast or conference, e.g. multicast with non-centralised forwarding system, e.g. chaincast
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/02Topology update or discovery
    • H04L45/04Interdomain routing, e.g. hierarchical routing
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/16Multipoint routing
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/302Route determination based on requested QoS
    • H04L45/306Route determination based on the nature of the carried application
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/48Routing tree calculation
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/50Routing or path finding of packets in data switching networks using label swapping, e.g. multi-protocol label switch [MPLS]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/60Router architectures

Definitions

  • the invention relates to a network routing and forwarding technology, in particular to a multicast method and a multicast routing method. Background of the invention
  • Multicast is a multi-party communication scheme of one to many or many.
  • the path through which the video stream flows in the network forms a tree structure, and the same video stream is transmitted on each branch of the tree, and is replicated at the branch of the tree. It is possible to stream the video to all recipients.
  • This tree is called a distribution tree.
  • the multicast routing protocol first forms a distribution tree. By transmitting a video stream on each branch of the distribution tree and replicating at the fork of the tree, the video stream is ultimately transmitted from the server to all recipients.
  • the join message the third layer.
  • the network device establishes a corresponding route forwarding state.
  • the route forwarding state is used to guide the forwarding of protocol packets and multicast data packets. Therefore, it is collectively referred to as multicast forwarding guide information, and multicast data is added in the route forwarding state.
  • the outbound interface of the packet sends a join message to the upstream Layer 3 network device in the direction of the multicast source server to which the channel television program belongs, performs the same action on the upstream Layer 3 network device, establishes a route forwarding state, and routes the route.
  • An interface is added to the publication item, and the join message is sent to the upstream.
  • the root node three-layer network device sends the multicast data packet along the same distribution tree. Push to the nearest Layer 3 network device.
  • the join message sent by the user includes a multicast source group address pair, that is, a channel section.
  • the destination address is used to identify a multicast session.
  • the address pair is generally expressed in the form of (S, G) or (*, G), or uniformly represented as (S/*, G).
  • S indicates the specified multicast source address, which is the IP address of the source that is sent to the multicast group G.
  • G indicates the specified multicast group address, which is used to identify the set of all receivers in the multipoint communication service.
  • a broadcast group for example, all receivers of a network television program belong to a multicast group; the * indicates an arbitrary multicast source, that is, the receiver does not specify a multicast source.
  • a multicast source group address pair corresponds to a set of state in the Layer 3 network device on the distribution tree.
  • the Layer 3 network device on the distribution tree will establish a corresponding route forwarding entry for the multicast group.
  • the message carrying the status is called a protocol message.
  • the purpose of the embodiments of the present invention is to provide a multicast method and a multicast routing method, which are used to reduce the memory usage of the router and improve the efficiency of protocol packets.
  • the embodiment of the present invention provides a multicast method, including a process of joining a multicast group and a process of forwarding a multicast packet.
  • the multicast forwarding class belongs to a distribution tree or a distribution class. Establishing multicast forwarding guidance information identified by the multicast forwarding equivalence class on the network node of the subtree;
  • the multicast packet of the same multicast forwarding equivalence class is forwarded according to the same multicast forwarding guide information.
  • An embodiment of the present invention further provides a multicast routing method, including:
  • the multicast forwarding guide information of the equivalence class identifier is added to the forwarding guide information, and the join message is continuously sent to the upstream. Continues to the ingress network node of the distribution tree or distribution subtree.
  • the embodiment of the present invention further provides a multicast method, including: dividing a set of multicast data packets forwarded in the same manner into a multicast forwarding equivalence class, and assigning a distribution tree or a distributor to the multicast forwarding equivalence class On the network node of the tree, the multicast forwarding guide information identified by the multicast forwarding equivalence class is statically configured, and the multicast packets of the same multicast forwarding equivalence class are forwarded according to the same multicast forwarding guide information.
  • An embodiment of the present invention further provides an egress network node, where the egress network node includes: a dividing module, a receiving module, a converting module, and a sending module;
  • the dividing module is configured to divide a set of multicast data packets that are forwarded in the same manner into a multicast forwarding equivalence class, and set the multicast data packet of the same multicast forwarding equivalence class and the multicast forwarding
  • the receiving module is configured to output the received join message to the conversion module, and output the received multicast data packet to a sending module.
  • the conversion module is configured to map the received join message to a join message based on the multicast forwarding equivalence class according to the mapping relationship obtained from the splitting module, and establish the multicast forwarding equivalence class
  • the forwarding instruction information of the identifier is output to the sending module, where the mapped packet and the forwarding guide information are output;
  • the sending module is configured to send the received join message to the upstream network node, and send the received multicast data packet to the downstream network node according to the forwarding guide information.
  • An embodiment of the present invention further provides an ingress network node, where the ingress network node includes: a dividing module, a receiving module, a converting module, and a sending module;
  • the dividing module is configured to divide a set of multicast data packets that are forwarded in the same manner into a multicast forwarding equivalence class, and set the multicast data packet of the same multicast forwarding equivalence class and the multicast forwarding The mapping relationship between equivalence classes;
  • the receiving module is configured to output the received join message to the conversion module, and output the received multicast data packet to a sending module;
  • the converting module is configured to establish, according to the received joining message and the mapping relationship obtained from the dividing module, the forwarding guide information that is identified by the multicast forwarding equivalence class; and output the forwarding guide information to the sending Module
  • the sending module is configured to send the received multicast data packet to the downstream network node according to the forwarding guide information.
  • the present invention divides the set of multicast data packets that are forwarded in the same manner into one multicast forwarding equivalence class, and uses the same multicast forwarding guide information for the multicast forwarding equivalence class that flows through the same distribution tree or subtree, reducing The forwarding information of different multicast packets is occupied by the router space, and the route convergence time can be accelerated, and the route switching frequency is reduced, thereby improving space and time efficiency.
  • the present invention does not use a separate (S, G) or (*, G) granularity for the protocol message, that is, no longer for each different (S, G) or (*, G).
  • the join request sends a join message, but is based on the granularity of the multicast forwarding equivalence class.
  • the same protocol packet is used, thereby improving the efficiency of state processing and packet interaction.
  • FIG. 1 is a schematic diagram of a multicast model in the background art
  • FIG. 2 is a schematic diagram of a distribution tree or a distribution subtree based on a multicast forwarding equivalence class according to an embodiment of the present invention
  • FIG. 3 is a flow chart of a method for performing multicast routing based on MFEC according to Embodiment 1 of the present invention
  • FIG. 4 is a MFEC based on the PIM SSM protocol in the second embodiment of the present invention. Schematic diagram of sending a tree and forwarding a multicast packet;
  • FIG. 5 is a schematic diagram of constructing a MFEC-based shared tree and forwarding a multicast data packet in a PIM SM protocol according to Embodiment 3 of the present invention; and forwarding a multicast data packet.
  • FIG. 7 is a structural diagram of a multicast system in an embodiment of the present invention.
  • FIG. 8 is a structural diagram of an egress network node in an embodiment of the present invention. Mode for carrying out the invention
  • Embodiments of the present invention divide a set of multicast data packets forwarded in the same manner into a multicast forwarding equivalence class, and use the same group by a multicast forwarding equivalence class (MFEC) flowing through the same distribution tree or subtree.
  • the forwarding forwarding information is forwarded in the same manner, and the multicast forwarding guide information includes but is not limited to the same multicast routing entry and multicast forwarding entry, thereby aggregating forwarding of multiple multicast data packets, thereby reducing
  • the multicast forwarding guide information of different multicast groups is occupied by the router space, and the route convergence time is accelerated, and the route switching frequency is reduced, thereby improving space and time efficiency. Meanwhile, the protocol packet of the present invention is no longer separate.
  • (S, G) or (*, G) is granular, that is, no longer joins the join request for each different (S, G) or (*, G) join request, but in multicast forwarding
  • the granularity of the equivalence class can improve the efficiency of state processing and message interaction.
  • a set of multicast data packets forwarded in the same manner is divided into a multicast forwarding equivalence class (MFEC), for example, flows through the same multicast distribution tree or a distribution subtree and performs the same forwarding.
  • MFEC multicast forwarding equivalence class
  • a collection of processed packets may be sent programs of multiple channels.
  • these programs are pushed to the router closest to the receiver, assuming a group of recipients receive All of these channel programs, that is, the distribution trees corresponding to all of these channels are the same, then all Multicast packets all flow through the same routing path, then the set of multicast packets can be a MFEC; for the same reason, the multicast packet set flowing through the same distribution subtree is also a MFEC, as shown in Figure 2.
  • the multicast packets forwarded on the router in the ellipse are the same, and the multicast packet flowing through the subtree becomes an MFEC.
  • the root node is called the ingress node
  • the leaf node is called the egress node
  • the nodes other than the root node and the leaf node are called transmissions. ) node.
  • the embodiment of the present invention uses a multicast source group address pair to represent the MFEC, but the multicast source group address pair is different from the existing protocol, and the address pair can represent all channels transmitted on the distribution tree.
  • the representation of the address pair includes but is not limited to the following: (multicast source address, multicast group address/mask), (multicast source address/mask, multicast group address), (multicast source address/ Mask, multicast group address/mask), (multicast source address, ⁇ 239.1.1.1 , 239.1.1.2 ⁇ ), (discrete multicast source address, multicast group address;), (discrete multicast source) Address, multicast group address/mask) or (discrete multicast source address, discrete multicast group address).
  • the multicast group address/mask represents a network segment, and all addresses in the network segment represent multicast group addresses of all channels included in the MFEC. Similarly, the multicast source address/mask also indicates a network. Segments, all addresses in the range of the network segment represent the multicast source addresses of all channels included in the MFEC. Of course, if the addresses of multiple multicast sources or multiple multicast groups are not consecutive, they can also be represented by discrete IP addresses, as shown in the foregoing 4th to 7th representations.
  • the interaction of the protocol packets is performed by using the MFEC as the granularity, and the multicast packets of the same multicast forwarding equivalence class are forwarded by using the same multicast forwarding entry.
  • the fields in the protocol packets or the messages of the channels belonging to the same MFEC can be combined into one in the distribution tree or the distribution subtree corresponding to the MFEC, it is not necessary to establish a corresponding state for each channel. Protocol packets, which saves the router's memory space and reduces the time for route switching.
  • the first embodiment is a method for performing multicast routing based on the MFEC, and the process is as shown in FIG. 3, which specifically includes the following steps:
  • Step 301 Set a mapping relationship between (S/*, G) and MFEC on the Egress router. If (S, G/M) or (*, G/M) belongs to a MFEC, then the Egress router receives the Internet Group Management Protocol/Multicast Receiver Discovery (IGMP/MLD) sent by the receiver host. The Egress router maps the received packets to the corresponding ones (S, G/M), or the join (Join) packets sent by other receivers through protocol-independent multicast (PIM). ) or (*, G/M) IGMP/MLD report message or Join message. There are two mapping methods at this time.
  • IGMP/MLD Internet Group Management Protocol/Multicast Receiver Discovery
  • the first mapping method replaces (S/*, G) in the join message with the identifier (S, G/M) or (*, G/M) of the MEFC;
  • the mapping method is to add a MFEC ID field to the message, and broadcast the correspondence between the MFEC and the MFEC ID to the entire network, or statically configure the corresponding relationship on each node by using a command.
  • the report message is a join message sent by the receiver host to the multicast group, and the join message is a join message transmitted between the routers. Since the Egress router may be connected to the receiver host or connected to the receiver host through other routers, there are two cases as described above.
  • Step 302 Set a mapping relationship between (S/*, G) and MFEC on the ingress router. If (S, G/M) belongs to a MFEC, the Ingress router, when receiving the multicast data packet, queries the multicast forwarding entry identified by the MFEC when the MFEC-based distribution tree or the distribution subtree is constructed, and Forward multicast packets on the corresponding outgoing interface.
  • Step 303 Create a route based on the multicast forwarding equivalence class MFEC.
  • the principle is based on the fact that all multicast packets are forwarded in the same way in the same MFEC.
  • the method of creating a route is divided into dynamic and static.
  • the dynamic creation method is to modify the existing protocol, and the join message sent by the receiver host and the join message transmitted in the MFEC-based distribution tree or distribution subtree are used. Dynamically generate MFEC-based distribution trees or distribution subtrees.
  • the receiver host sends the join message first, and the Egress router directly receives the join message, or receives the join message through other routers, and then performs mapping of (S/*, G) to MFEC, which will be added to the message.
  • the routing entry and the multicast forwarding entry are added, and the outbound interface is added to the entry.
  • the outgoing interface is the outgoing interface of the multicast data packet.
  • the multicast data packet is forwarded downstream through the interface.
  • (S, G /M) is a MFEC
  • the multicast routing entry and multicast forwarding entry will become (S, G/M, GE1/0/1, ⁇ GE2/0/0, GE3/0/0 ⁇ )
  • the inbound interface of the multicast packet, ⁇ GE2/0/0, GE3/0/0) is the outbound interface, and the GE refers to Gigabit Ethernet; then to the distribution tree or
  • the upstream router that distributes the subtree sends the join message identified by the MFEC.
  • the upstream router may be a transit router or an ingress router.
  • the MFEC-based route is established on the entire MFEC distribution tree or distribution subtree.
  • the steps 301 to 303 described above are the process of joining the multicast group, including the receiver host sending the join message and the network node router sending the join message to the upstream node, and the process is actually constructing the MFEC distribution tree or the distribution subtree.
  • the process of performing the process determines the distribution path of the multicast packet.
  • the method of statically creating a MFEC-based route is to statically configure the multicast forwarding guide information, that is, the multicast routing entry and the group, by using the multicast forwarding equivalence class identifier on each node in the distribution tree or the distribution subtree.
  • the forwarding entry is broadcasted, so that the forwarding of the multicast packet is directly guided by the MFEC on each node.
  • a node of a distribution tree or a distribution subtree can be divided into an ingress node by function, that is, an entry of a multicast packet on a distribution tree or a distribution subtree, and a transmission section.
  • the point, that is, the intermediate node also includes the egress node, that is, the egress of the multicast packet on the distribution tree or the distribution subtree.
  • the egress node that is, the egress of the multicast packet on the distribution tree or the distribution subtree.
  • these three types of nodes do not have to exist at the same time. For example, there may be no transit nodes, or only one node is included in the distribution tree or the distribution subtree, then the nodes are both ingress, transport, and egress nodes.
  • the difference between the multicast routing entry and the multicast forwarding entry is that the multicast routing entry is all routing entries established when the router performs routing learning.
  • the multicast forwarding entry is the optimal route in the routing entry. It is the routing entry that the router actually forwards the data packet. However, in a multicast protocol, a multicast routing entry is generally the same as a multicast forwarding entry.
  • dynamic and static creation that is, statically configured to join the interface on the egress router, and configured to the Egress router through commands.
  • Statically joined on an interface The interface is not limited to physical interfaces, and may be virtual logical interfaces.
  • the mapping relationship as described in step 301 is not required to be configured on the egress router, but the MFEC-based join message is directly sent to the upstream router.
  • the method does not have the join message of the receiver host, but the actual effect is the same as that of the receiver host. The result is that the egress router sends the join message to the upstream.
  • the MFEC-based distribution tree or distribution subtree is created, and the multicast routing entries and multicast forwarding entries of each node in the tree are determined, when the multicast packet arrives at the ingress router.
  • the second embodiment of the present invention is a method for constructing a MFEC-based route in a protocol-independent multicast (PIM SSM) of a specified source multicast and forwarding the multicast data packet according to the route.
  • PIM SSM protocol-independent multicast
  • the receiver's host sends an IGMP/MLD (S, G) report message to the router closest to itself. For example, if the receiver wants to watch a program of a certain channel, that is, it needs to receive the (S, G) multicast data stream, it sends an IGMP/MLD (S, G) report message to the Egress router.
  • S, G IGMP/MLD
  • step 3 On the Egress router, convert the (S, G) state to the (S, G/M) state according to the mapping relationship set in step 1.
  • the conversion action is performed after the Egress router receives the report message, that is, the (S, G) field in the message is converted to (S, G/M).
  • the multicast source is determined to be S. Therefore, the Egress router obtains the inbound interface of the multicast source by querying the corresponding routing entry, and then creates a multicast routing and forwarding entry identified by (S, G/M). This entry adds an outbound interface, which is the interface to the receiver host.
  • the Egress router calculates and generates a PIM Join message in the (S, G/M) state, and sends the (S, G/M) PIM Join message to the multicast source in the inbound interface in step 3. .
  • the Transit router on the MFEC is received by the message. 5.
  • Create a (S, G/M) state on the Transit router establish a corresponding route/forward entry with the identifier of (S, G/M), and add the outbound interface of the multicast packet to the entry.
  • the ingress router creates the (S, G/M) state, establishes the corresponding route/forward entry with the (S, G/M) ID, and adds the outbound interface to the entry. If there is no other Layer 3 network device between the ingress router and the multicast source, that is, the ingress router is the Layer 3 network device closest to the multicast source, the data stream sent by the multicast source reaches the ingress router and then switches according to the established multicast. Publish the item and forward it on the outgoing interface.
  • the ingress router can receive and forward the multicast packets sent by the multicast source in the following two ways: Mode 1), Ingress router and multicast source
  • a router can statically configure multicast routing entries and multicast forwarding entries to generate multicast routing entries and forwarding entries identified by (S, G/M).
  • the latest Layer 3 network device forwards the multicast data packet to the ingress router on the outbound interface by configuring the forwarding entry.
  • Method 2 On the Ingress router, according to the mapping relationship configured in step 1, the MFEC is decomposed into corresponding (S, G), and each (S, G)-based PIM Join is sent to the upstream router according to the normal manner. Message.
  • the method of the method 1) is actually a continuation of the technical solution of the embodiment of the present invention, and all the multicast group data streams of the MFEC are pushed to the ingress router.
  • the advantage of the method is that the link on the MFEC distribution tree can be avoided.
  • the method can be sent on demand, that is, only the multicast packet of the multicast group is sent after receiving the join message of a multicast group, between the ingress router and the multicast source. Only (S, G) multicast packets are transmitted on the router as required by the receiver.
  • the multicast source sends a multicast packet.
  • the ingress router queries the multicast forwarding entry identified by MFEC according to the mapping relationship. According to the established (S, G/M) ) Forwards the multicast packet on the outbound interface for the identified forwarding entry.
  • the Transit router receives the multicast data packet, and forwards the multicast data packet downstream on the outbound interface to the Egress according to the established forwarding entry with the (S, G/M) identifier. On the router, the Egress router forwards the multicast packet to the receiver based on the established forwarding entry identified by (S, G/M).
  • the mapping relationship between the multicast packet and the MFEC is preset on the Egress router and the Ingress router.
  • the egress router obtains the user's request to join the multicast group, it directly establishes the MFEC-based multicast routing entry and forwarding entry.
  • the user wants to receive other channel programs of the same MFEC, it is not necessary to change the mapping relationship and routing/forwarding entries, thereby saving the router's memory space and routing switching time.
  • the third embodiment of the present invention is a method for constructing a MFEC-based shared tree and forwarding a multicast data packet in the Sparse Mode Protocol Independent Multicast (PIM SM).
  • the construction method is as shown in FIG. 5, and includes the following steps:
  • the receiver's host sends an IGMP/MLD (*, G) report message to the Egress router. For example, if the receiver wants to watch a program of a certain channel and only knows the address of the multicast group, that is, if he wants to receive the multicast packet of (*, G), it sends an IGMP/MLD (*, G) report to the Egress router. Text.
  • the Egress router converts the (*, G) field in the IGMP/MLD (*, G) report message to the (*, G/M) field according to the MFEC mapping relationship set in step 1, and establishes (S, G). /M ) Add the outbound interface to the specified multicast routing and forwarding entry, or configure the IGMP/MLD static join (*, G/M) in the static configuration mode to trigger the PIM SM to construct the distribution tree.
  • the Egress router calculates and generates a PIM Join message based on (*, G/M) and sends a PIM Join message of (*, G/M) to the RP.
  • the Transit router calculates and generates a PIM Join message based on (*, G/M), and sends a PIM Join message based on (*, G/M) to the RP direction.
  • the source designated router (DR) unicasts (registers) the message to the RP.
  • the source DR is the Layer 3 network node closest to the multicast source.
  • the multicast packets of the multicast source are sent to the source DR continuously. However, the source DR does not forward the request when it does not receive the request to join the multicast group. Packet's.
  • the unicast action is not restricted in this step of the process.
  • the register message of the source DR is periodically sent to the RP. The purpose is to let the RP know the existence of the multicast source, and the role of the RP is The receiver host is associated with the multicast source, and the packet can also be received from the multicast source through the RP.
  • the multicast source (S, G) is converted to the (S, G/M) state according to the MFEC mapping relationship, and the (S, G/M) based register message is unicast to the RP.
  • the RP is an Ingress router, the RP in the present invention converts the (S, G) in the register message to the (S, G/M) state according to the MFEC mapping table after receiving the (S, G) register message.
  • the source DR receives the multicast data packet sent by the multicast source, and forwards the multicast data packet downstream on the outbound interface, and sends the multicast data packet to the receiver host through the Transit router and the Egress router.
  • This embodiment is a method of constructing a shared tree and forwarding a multicast packet if the recipient does not specify a multicast source.
  • the RP needs to associate the multicast group to which the receiver is to join with the multicast source.
  • the path for forwarding multicast packets through the RP is called the shared tree (RPT). Since RPT is not the optimal path from the receiver to the multicast source, and the RPT is often used for multiple (*, G) forwarding requests, The load is large, so the protocol stipulates that under certain trigger conditions, the traffic on the RPT path should be switched to the optimal path, that is, the shortest path tree (SPT) between the receiver and the multicast source, SPT— Also known as the source tree.
  • SPT shortest path tree
  • the triggering condition of the switch is set by the user.
  • the traffic of the downlink multicast packet received by the Egress router is greater than 0 or greater than a certain rate, such as lMbit/s.
  • the switching process is described in Embodiment 4 of the present invention, and the flow thereof is as shown in FIG. 6, and includes the following steps:
  • the multicast packet is forwarded along the RPT.
  • the Egress router that directly connects to the receiver host in Figure 6 initiates an SPT switchover, and calculates and sends a PIM Join message based on (S, G/M) to the multicast source. Text.
  • the source DR is an ingress router, according to step 1, if there is already a mapping relationship between (S, G/M) on the source DR, create a multicast routing/forward with the identifier (S, G/M) as the identifier. An entry is added to the entry. Otherwise, the source DR may be directly connected to the ingress router. There may be other routers in between. There are two solutions to this problem:
  • MFEC-based multicast forwarding entries and multicast routing entries can be statically configured on the router between the source DR router and the ingress router to generate (S, G/M) routing entries and forwarding entries. The configuration is forwarded by the ingress router to the source DR router;
  • the ingress router decomposes the MFEC into multiple corresponding (S, G) according to the mapping relationship in the first step, and sends each (S, G) PIM Join message to the multicast source in the normal manner.
  • the source DR receives the multicast data packet sent by the multicast source and forwards the multicast data packet downstream on the outbound interface.
  • the Transit router receives the multicast data packet and forwards the multicast data packet downstream along the SPT.
  • the last-hop router directly connected to the receiver receives the multicast packet from the upstream of the SPT and initiates the pruning process. Since it has received the multicast packet through the SPT, the RPT needs to be deleted, and then the RTP is calculated and sent to the RP. Prune message based on (S, G/M).
  • the outgoing interface of the RP pruning (S, G/M) sends a (S, G/M) stop register (register stop) message to the source DR, and the source DR pruning (S, G/M) register.
  • Outbound interface no longer forwards packets along the RPT.
  • the dynamic application mode of the MFEC is adopted, that is, according to the preset MFEC mapping relationship, the multicast protocol packet is received as the trigger condition of the IGMP/MLD report/PIM, and the multicast is performed.
  • the /*, G) state is converted to the corresponding MFEC state, and the multicast routing protocol is caused to construct a MFEC-based multicast distribution tree.
  • static application mode can also be used to directly define MFEC-based static join, create a MFEC-based multicast distribution tree, define MFEC routing entries and forwarding entries on the router, and directly guide packet forwarding.
  • Dynamic application mode is used on some network nodes, and static mode is used on some network nodes. For example, static mode is used on the egress router, and dynamic mode is used on other routers.
  • FIG. 7 is a block diagram of an egress network node in an embodiment of the present invention.
  • the egress network node 700 in the embodiment of the present invention includes: a dividing module 701, a receiving module 702, a converting module 703, and a sending module 704;
  • the dividing module 701 is configured to divide a set of multicast data packets forwarded in the same manner into a multicast forwarding equivalence class, and set the multicast data packet of the same multicast forwarding equivalence class and the multicast Forward the mapping relationship between equivalence classes;
  • the receiving module 702 is configured to output the received join message to the conversion module 703; output the received multicast data packet to the sending module 704;
  • the converting module 703 is configured to map, according to the mapping relationship obtained from the dividing module 701, the received joining message into a joining message based on the multicast forwarding equivalence class, and establish the multicast forwarding, etc.
  • the sending module 704 is configured to send the received join message to the upstream network node, and send the received multicast data packet to the downlink network node according to the forwarding guide information.
  • the converting module 703 is further configured to add an outbound interface to the forwarding guide information, and the sending, by the forwarding guide information, the received multicast data packet to the downstream network node, according to the forwarding guide information
  • the outbound interface sends the received multicast packet to the downstream network node.
  • FIG. 8 is a real version of the present invention A structural diagram of an egress network node in the example.
  • the ingress network node 800 in the embodiment of the present invention includes: a dividing module 801, a receiving module 802, a converting module 803, and a sending module 804;
  • the dividing module 801 is configured to divide a set of multicast data packets forwarded in the same manner into a multicast forwarding equivalence class, and set the multicast data packet of the same multicast forwarding equivalence class and the multicast Forward the mapping relationship between equivalence classes;
  • the receiving module 802 is configured to output the received join message to the conversion module 803; output the received multicast data packet to the sending module 804;
  • the conversion module 803 is configured to: establish, according to the received join message and the mapping relationship obtained from the splitting module 801, the forwarding guide information that is identified by the multicast forwarding equivalence class; and output the forwarding guide information.
  • the sending module 804 is configured to send the received multicast data packet to the downstream network node according to the forwarding guide information.
  • the converting module 803 is further configured to add an outbound interface to the forwarding guide information, and the sending the received multicast data packet to the downstream network node according to the forwarding guide information includes: The outbound interface sends the received multicast packet to the downstream network node.
  • the multicast data packets are called multicast forwarding equivalence classes MFEC, and the same multicast forwarding
  • the data packets of the same type are forwarded by the same multicast forwarding entry, which can speed up the route convergence time, reduce the space occupation, and improve the space and time efficiency.
  • the protocol packets are no longer separated by a separate (S, G) or (*, G) is granular, but based on the multicast forwarding equivalence class, which can improve the efficiency of state processing and message interaction.

Landscapes

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

Description

组播方法及组播路由方法
技术领域
本发明涉及网络路由及转发技术,特别是组播方法及组播路由方法。 发明背景
在目前的网络应用中, 视频等多媒体业务的地位日益重要, 而组播 技术则是网络多媒体业务的重要承载技术, 组播是一到多或者多到多的 多方通信形式。 如图 1所示的组播模型中, 视频流在网络中流经的路径 形成一个树形结构, 在这棵树的每一个分支上都传送相同的视频流, 在 树的分叉处进行复制, 就可以将视频流传送到所有的接收者, 这棵树被 称为分发树。 组播路由协议首先形成分发树, 通过在分发树的每一个分 支上传送一个视频流, 在树的分叉处进行复制的过程, 视频流从服务器 最终传送到所有接收者。
以网络电视(IPTV )业务为例, 用户想要收看某频道的电视节目, 则首先要向离自身最近的三层网络设备发送加入组播组的报文, 以下简 称加入报文, 该三层网络设备建立相应的路由转发状态, 所述路由转发 状态因为可以用来指导协议报文和组播数据包的转发, 故统称为组播转 发指导信息, 还要在路由转发状态中添加组播数据包的出接口, 并向该 频道电视节目所隶属的组播源服务器方向的上游三层网络设备发送加 入报文, 在上游三层网络设备上执行相同的动作, 建立路由转发状态, 在路由转发表项中添加出接口, 再向上游发送加入报文, 一直到组播数 据包分发树的根节点接收到加入报文后, 该根节点三层网络设备将组播 数据包沿相同的分发树推送到离用户最近的三层网络设备上。
其中, 在用户发送的加入报文中包含组播源组地址对, 即某频道节 目的地址,用该组播地址对来标识一个组播会话,该地址对一般以( S,G ) 或 (*,G ) 的形式表示, 或统一表示为 (S/*,G ) 。 其中, S 表示指定的 组播源地址, 即表示发向组播组 G的源的 IP地址; G表示指定的组播 组地址, 用于标识多点通信业务中所有接收者的集合, 即组播组, 例如 一个网络电视节目的所有接收者就同属于一个组播组; 所述 *表示任意 组播源, 即接收者未指定组播源。 一个组播源组地址对(S/*,G )在分发 树上的三层网络设备中对应一组状态, 分发树上的三层网络设备将对该 组播组建立相应的路由转发表项, 而携带该状态的消息称为协议报文。 发明内容
本发明的实施例的目的在于提供组播方法及组播路由方法, 用于减 少路由器内存占用及提高协议报文的效率。
本发明的实施例提供了一种组播方法, 包括加入组播组的过程和转 发组播数据包的过程, 在加入组播组的过程中, 在组播转发等价类所属 分发树或分发子树的网络节点上, 建立以组播转发等价类标识的组播转 发指导信息;
在转发组播数据包的过程中, 将同一组播转发等价类的组播数据包 根据同一个组播转发指导信息转发。
本发明的实施例还提供了一种组播路由方法, 包括:
将采用相同方式转发的组播数据包的集合划分为组播转发等价类, 组播转发等价类所属分发树或分发子树的出口网络节点接收到激励后, 则向所述分发树或分发子树的上游网络节点发送加入报文, 建立以组播 转发等价类标识的组播转发指导信息, 并在所述转发指导信息中添加出 接口, 所述上游网络节点建立以组播转发等价类标识的组播转发指导信 息, 在所述转发指导信息中添加出接口, 并继续向上游发送加入报文, 一直到达所述分发树或分发子树的入口网络节点上。
本发明的实施例还提供了一种组播方法, 包括: 将采用相同方式转 发的组播数据包的集合划分为组播转发等价类, 在组播转发等价类所属 分发树或分发子树的网络节点上, 静态配置以组播转发等价类标识的组 播转发指导信息, 将同一组播转发等价类的组播数据包根据同一个组播 转发指导信息转发。
本发明的实施例还提供了一种出口网络节点, 该出口网络节点包 括: 划分模块、 接收模块、 转换模块和发送模块;
所述划分模块, 用于将采用相同方式转发的组播数据包的集合划 分为组播转发等价类, 并设置所述同一组播转发等价类的组播数据包与 所述组播转发等价类之间的映射关系;
所述接收模块 , 用于将所接收到的加入报文输出给所述转换模 块; 将所接收到的组播数据包输出给发送模块;
所述转换模块, 用于根据从划分模块中获取的映射关系, 将所接 收的加入报文映射为基于所述组播转发等价类的加入报文, 建立以所述 组播转发等价类标识的转发指导信息; 将所述映射后的报文和所述转发 指导信息输出给发送模块;
所述发送模块, 用于将所接收到的所述映射后的加入报文发送给 上游网络节点; 根据转发指导信息将所接收到的组播数据包发送给下游 网络节点。
本发明的实施例还提供了一种入口网络节点, 该入口网络节点包 括: 划分模块、 接收模块、 转换模块和发送模块;
所述划分模块, 用于将采用相同方式转发的组播数据包的集合划 分为组播转发等价类, 并设置所述同一组播转发等价类的组播数据包与 所述组播转发等价类之间的映射关系; 所述接收模块, 用于将所接收到的加入报文输出给所述转换模 块; 将所接收到的组播数据包输出给发送模块;
所述转换模块, 用于根据所接收到的加入报文以及从划分模块中 获取的映射关系, 建立以所述组播转发等价类标识的转发指导信息; 将 所述转发指导信息输出给发送模块;
所述发送模块, 用于根据所述转发指导信息将所接收到的组播数 据包发送给下游网络节点。
本发明通过将使用相同方式转发的组播数据包的集合划分为一个 组播转发等价类, 对流经相同分发树或子树的组播转发等价类使用同一 个组播转发指导信息, 减少了不同组播数据包的转发指导信息对路由器 空间的占用, 并且可以加快路由收敛时间, 减少路由切换频率, 从而提 高空间和时间效率。
进一步的, 本发明对协议报文不再以单独的 (S,G )或 (*,G ) 为粒 度, 也就是说, 不再针对每个不同的 (S,G )或(*,G ) 的加入请求发送 加入报文, 而是基于组播转发等价类的粒度, 对于同一组播转发等价类 的加入请求, 使用相同的协议报文, 从而可以提高状态处理和报文交互 的效率。 附图简要说明
图 1为背景技术中的组播模型示意图;
图 2为本发明的实施例中基于组播转发等价类的分发树或分发子树 示意图;
图 3 为本发明的实施例一中基于 MFEC进行组播路由的方法流程 图;
图 4为本发明的实施例二中在 PIM SSM协议中构建基于 MFEC分 发树并转发组播数据包的示意图;
图 5为本发明的实施例三中在 PIM SM协议中构建基于 MFEC的共 享树并转发组播数据包的示意图; 转发组播数据包的示意图。
图 7为本发明的实施例中组播系统的结构图。
图 8为本发明的实施例中出口网络节点的结构图。 实施本发明的方式
本发明的实施例将使用相同方式转发的组播数据包的集合划分为一 个组播转发等价类, 通过对流经相同分发树或子树的组播转发等价类 ( MFEC )使用同一个组播转发指导信息, 采用相同的方式转发, 所述 组播转发指导信息包括但不仅限于相同的组播路由表项和组播转发表 项, 从而聚合了多个组播数据包的转发, 减少了不同组播组的组播转发 指导信息对路由器空间的占用, 并且可以加快路由收敛时间, 减少路由 切换频率, 从而提高空间和时间效率; 同时, 本发明的实施例对协议报 文不再以单独的 (S,G )或 (*,G )为粒度, 也就是说, 不再针对每个不 同的 (S,G )或 (*,G ) 的加入请求发送加入报文, 而 于组播转发等 价类的粒度, 可以提高状态处理和报文交互的效率。
在本发明的实施例中, 将使用相同方式转发的组播数据包的集合划 分为组播转发等价类(MFEC ), 例如流经相同的组播分发树或分发子树 并进行相同的转发处理的数据包的集合。 以 IPTV中的业务为例, 同一 服务器或服务器群可能会发送多个频道的节目, 在接收者的加入请求 下, 这些节目都被推送到离接收者最近的路由器上, 假设一组接收者接 收所有的这些频道节目, 即所有这些频道对应的分发树都相同, 则所有 组播数据包都流经相同的路由路径, 那么这些组播数据包的集合就可以 是一个 MFEC; 同理, 流经相同分发子树的组播数据包集合也是一个 MFEC, 如图 2所示, 椭圆内的路由器上转发的组播数据包都相同, 则 流经该部分子树的组播数据包成为一个 MFEC。在 MFEC分发树或分发 子树中, 如图 2所示, 根节点称为入口 (Ingress ) 节点, 叶子节点称为 出口(Egress )节点,除根节点和叶子节点之外的节点称为传输( Transit ) 节点。
本发明的实施例采用组播源组地址对来表示 MFEC, 但该组播源组 地址对与现有协议中不同, 该地址对能够表示在该分发树上传输的所有 频道。 该地址对的表示方式包括但不限于以下几种: (组播源地址, 组 播组地址 /掩码)、(组播源地址 /掩码, 组播组地址)、(组播源地址 /掩码, 组播组地址 /掩码)、 (组播源地址, { 239.1.1.1 , 239.1.1.2 } )、 (离散的组 播源地址,组播组地址;)、 (离散的组播源地址,组播组地址 /掩码)或(离 散的组播源地址, 离散的组播组地址)。 其中, 组播组地址 /掩码表示一 个网段,该网段范围内的所有地址表示本 MFEC中包括的所有频道的组 播组地址; 同理, 组播源地址 /掩码也表示一个网段, 该网段范围内的所 有地址表示本 MFEC中包括的所有频道的组播源地址。 当然, 如果多个 组播源或多个组播组的地址不连续,也可以采用离散的 IP地址的方式来 表示, 如前述第 4至 7种表示方式。
在本发明的实施例中,协议报文的交互都是以 MFEC为粒度进行的, 同一组播转发等价类的组播数据包使用同一个组播转发表项进行转发。 并且, 由于在一个 MFEC对应的分发树或分发子树中, 可以将属于同一 MFEC的各频道的协议报文或报文中的字段合并为一个, 因此不必针对 每个频道都建立相应的状态和协议报文, 从而节约了路由器的内存空 间, 并减少了路由切换的时间。 实施例一为基于 MFEC进行组播路由的方法, 其流程如图 3所示, 具体包括以下步骤:
步骤 301、 在 Egress路由器上设置( S/*,G )到 MFEC的映射关系。 如果(S,G/M )或 (*,G/M )属于一个 MFEC, 那么当 Egress路由器接 收到接收者主机发送的因特网组管理协议 /组播接收者发现 ( IGMP/MLD ) 加入(report )报文, 或者其它接收者主机通过其它路 由器发送的协议无关组播(PIM )等协议的加入(Join )报文时, Egress 路由器将所接收到的报文映射为对应的 (S,G/M ) 或 ( *,G/M ) 的 IGMP/MLD report报文或 Join报文。 此时有两种映射方法 , 第一种映射 方法是用 MEFC的标识( S,G/M )或( *,G/M )替换加入报文中的( S/*,G ); 第二种映射方法是在报文中增加一个 MFEC ID 字段, 并向全网广播 MFEC与 MFEC ID间的对应关系, 或者通过命令在各节点上静态配置 这种对应关系。 其中, 上述的 report报文是接收者主机向路由器发送的 到组播组的加入报文, 上述的 Join报文是路由器之间传递的加入报文。 因为 Egress路由器可能与接收者主机相连或通过其它路由器与接收者主 机相连, 所以存在以上所述的两种情况。
步骤 302、 在 Ingress路由器上设置( S/*,G )到 MFEC的映射关系。 如果(S,G/M )属于一个 MFEC, 那么 Ingress路由器在接收到组播数据 包时, 查询构建基于 MFEC 的分发树或分发子树时已建立的以 MFEC 标识的组播转发表项, 并在相应出接口上转发组播数据包。
步骤 303、 创建基于组播转发等价类 MFEC的路由。 依据的原则就 是在同一个 MFEC中, 所有组播数据包采用相同方式转发。 创建路由的 方法分为动态和静态两种, 动态创建方式是指修改现有协议, 通过接收 者主机发送的加入报文以及在基于 MFEC 的分发树或分发子树中传递 的加入报文, 来动态生成基于 MFEC的分发树或分发子树。 接收者主机首先发送加入报文, Egress路由器直接接收到该加入报 文, 或者通过其它路由器接收到该加入报文, 则进行(S/*,G )到 MFEC 的映射,将加入报文中的( S,G )或( *,G )字段替换成( S,G/M )或( *,G/M ), 创建以(S,G/M )或(*,G/M )标识的组播路由表项及组播转发表项, 并 在表项中添加出接口, 该出接口是组播数据包的出接口, 组播数据包通 过该接口向下游转发, 比如, 如果(S,G/M ) 为一个 MFEC, 那么组播 路由表项和组播转发表项将变为( S,G/M, GE1/0/1, { GE2/0/0, GE3/0/0 } ) 的形式, 其中 GE1/0/1为组播数据包的入接口, { GE2/0/0, GE3/0/0 ) 为 出接口, 所述 GE是指吉比特以太网; 然后再向分发树或分发子树的上 游路由器发送以 MFEC标识的加入报文。 该上游路由器可能是 Transit 路由器也可能是 Ingress路由器, 如果为 Transit路由器, 则还要继续创 建以(S,G/M )或(*,G/M )标识的组播路由表项及组播转发表项, 在表 项中添加出接口, 向上游路由器发送加入报文, 最终 Ingress路由器会收 到加入报文, 也要创建以(S,G/M )或(*,G/M )标识的组播路由表项及 组播转发表项, 在表项中添加出接口, 至此, 在整个 MFEC分发树或分 发子树上建立了基于 MFEC的路由。
以上所述的步骤 301至步骤 303是加入组播组的过程, 包括接收者 主机发送加入报文和网络节点路由器向上游节点发送加入报文, 该过程 实际上也是构建 MFEC分发树或分发子树的过程, 执行该过程后, 也就 确定了组播数据包的分发路径。
而静态创建基于 MFEC的路由的方式是指在所述分发树或分发子树 中的各个节点上静态配置以组播转发等价类标识的组播转发指导信息, 即组播路由表项及组播转发表项,从而在各节点上以 MFEC为粒度直接 指导组播数据包的转发。 一般来讲, 分发树或分发子树的节点按功能可 划分为入口节点, 即组播数据包在分发树或分发子树上的入口, 传输节 点, 也就是中间节点, 还包括出口节点, 即组播数据包在分发树或分发 子树上的出口。 当然, 这三类节点并非必须同时存在, 例如可以没有传 输节点, 或者在分发树或分发子树上仅包括一个节点, 那么该节点同时 是入口、 传输及出口节点。
所述组播路由表项与组播转发表项的区别在于, 组播路由表项是在 路由器进行路由学习时, 建立的所有的路由表项。
而组播转发表项是路由表项中的最优路由, 是路由器实际进行数据 包转发的路由表项。 但在组播协议中, 组播路由表项与组播转发表项一 般来说是相同的。
除了前述的动态和静态创建基于组播转发等价类 MFEC的路由方式 之外, 还有一种动静相结合的创建方式, 即在 Egress路由器上静态地配 置到接口的加入, 通过命令配置到 Egress路由器某接口上的静态加入, 该接口并非仅限于物理接口, 也有可能是一些虚拟逻辑接口。 按照该方 法, 可不必在 Egress路由器上配置如步骤 301所述的映射关系, 而是直 接向上游路由器发送基于 MFEC的加入报文。该方法虽然没有接收者主 机的加入报文, 但实际效果却与接收者主机发送加入报文相同, 结果都 是触发了 Egress路由器向上游发送加入报文, 因此, 在本发明的实施例 中, 将这两种方法统称为激励, 其中, 动态映射方式称为协议激励, 静 态加入方式称为命令激励。但上述的静态加入方式是在 Egress路由器上 实现的, 但在 Transit路由器及 Ingress路由器上依然是根据下游路由器 发送的加入报文来动态创建路由, 因此从整体上看, 该方法还是动态的 映射方式。
通过如上所述的步骤 301至步骤 303 , 创建了基于 MFEC的分发树 或分发子树, 确定了树上各节点的组播路由表项和组播转发表项, 当组 播数据包到达 Ingress路由器时, 首先根据步骤 302中设置的映射关系, 查询组播转发指导信息, 根据以(S,G/M )或(*,G/M )为标识的组播转 发表项, 在出接口上转发组播数据包, 组播数据包通过所述分发树或分 发子树的 Transit路由器和 Egress路由器的转发, 并最终到达接收者的 主机。
本发明的实施例二是在指定源组播的协议无关组播(PIM SSM ) 中 构建基于 MFEC的路由并按照该路由转发组播数据包的方法,其流程如 图 4所示, 具体包括以下步骤:
1、 在 Egress路由器和 Ingress路由器上预先设置( *,G )或 (S,G ) 到 MFEC的映射关系为 (*,G/M )或 (S,G/M )。
2、 接收者的主机向离自身最近的路由器发送 IGMP/MLD ( S,G ) report报文。 例如接收者想要收看某频道的节目, 即需要接收(S,G )的 组播数据流, 则向 Egress路由器发送 IGMP/MLD ( S,G ) report报文。
3、 在 Egress路由器上, 根据步骤 1中设置的映射关系, 将( S,G ) 状态转换为( S,G/M )状态。 该转换动作是 Egress路由器在接收到 report 报文后进行的, 即将该报文中的 (S,G ) 字段转换为 (S,G/M )。 因为组 播源确定为 S, 因此, Egress路由器通过查询相应路由表项获得到该组 播源的入接口, 再创建以 (S,G/M ) 为标识的组播路由和转发表项, 为 该表项添加出接口, 该出接口就是到接收者主机的接口。
当然也可以采用静态配置的方式在 Egress路由器上配置基于 MFEC 的静态加入, 即在没有接收到 report报文的情况下, 通过相关命令配置 到 Egress路由器某接口上的静态加入,触发 Egress路由器向上游发送加 入报文。
4、 Egress路由器计算并生成( S,G/M )状态的 PIM Join报文, 并在 步骤 3中所述入接口上向组播源方向发送基于 (S,G/M ) 的 PIM Join报 文。 如图 4所示, 接收该报文的是 MFEC上的 Transit路由器。 5、 在 Transit路由器上创建( S,G/M )状态, 建立相应的以( S,G/M ) 为标识的路由 /转发表项, 并在表项中添加组播数据包的出接口, 向源方 向发送( S,G/M ) 的 PIM Join报文。
6、 Ingress路由器创建( S,G/M )状态, 建立相应的以 ( S,G/M ) 为 标识的路由 /转发表项, 并在表项中添加出接口。 如果 Ingress路由器与 组播源之间没有其他三层网络设备,即 Ingress路由器为距离组播源最近 的三层网络设备,那么组播源发出的数据流到达 Ingress路由器后根据已 建立的组播转发表项, 在出接口上进行转发。
如果 Ingress路由器与组播源之间还有其他路由器, 则 Ingress路由 器可以采用如下所述的两种方式接收并转发组播源发送的组播数据包: 方式 1 )、 在 Ingress路由器与组播源之间的路由器上可以采用静态 配置组播路由表项和组播转发表项的方式, 生成以 (S,G/M ) 为标识的 组播路由表项和转发表项, 由距离组播源最近的三层网络设备通过配置 转发表项, 在出接口上向 Ingress路由器转发组播数据包;
方式 2 )、 在 Ingress路由器上, 根据步骤 1 中配置的映射关系, 再 将 MFEC分解为相应的(S,G ), 按照正常方式向上游路由器分别发送基 于每个( S,G ) 的 PIM Join报文。
采用方式 1 ) 的方法, 实际上是对本发明的实施例的技术方案的延 续, 将 MFEC的所有组播组数据流都推送到 Ingress路由器上, 该方法 的优点是能够避免 MFEC 分发树上链路的振荡所导致的组播数据包传 输延迟或抖动等问题, 因为所有组播数据包都被一次性推送到 Ingress 路由器上, 不会因为 MFEC分发树内部的变化受到影响; 而方式 2 ) 的 方法是一种节约带宽的方法, 该方法能够按需发送, 即只有接收到某个 组播组的加入报文才发送这个组播组的组播数据包,在 Ingress路由器与 组播源之间的路由器上按照接收者的需要仅传输(S,G )组播数据包。 7、 组播源发出组播数据包, 当组播数据包到达 Ingress路由器后, Ingress路由器根据映射关系, 查询以 MFEC为标识的组播转发表项,根 据已建立的以 (S,G/M ) 为标识的转发表项, 在出接口上转发组播数据 包。
8、 Transit路由器接收组播数据包, 根据已建立的以 ( S,G/M )为标 识的转发表项, 在出接口上向下游转发组播数据包一直到将组播数据包 转发到 Egress路由器上, Egress路由器同样根据已建立的以 ( S,G/M ) 为标识的转发表项, 将组播数据包转发给接收者。
本实施例应用在特定组播源的情况下, 在 Egress路由器和 Ingress 路由器上预先设置组播数据包与 MFEC间的映射关系。当 Egress路由器 获得用户的加入组播组的请求时,直接建立基于 MFEC的组播路由表项 和转发表项。 当用户想要接收同一 MFEC的其它频道节目时, 不必改变 映射关系和路由 /转发表项,从而节省了路由器的内存空间和路由切换时 间。
本发明的实施例三是应用在稀疏模式协议独立组播( PIM SM )中的 构建基于 MFEC的共享树并转发组播数据包的方法, 其构建方式如图 5 所示, 包括以下步骤:
1、 在 Egress路由器和 Ingress路由器上预设置( *,G )或 ( S,G )到 MFEC的映射关系为 (*,G/M )或 (S,G/M )。
2、 接收者的主机向 Egress路由器发送 IGMP/MLD ( *,G ) report报 文。 例如接收者想要收看某频道的节目, 仅仅知道组播组的地址, 即想 要接收(*,G )的组播数据包,则向 Egress路由器发送 IGMP/MLD ( *,G ) report才艮文。
3、 Egress路由器根据步骤 1中设置的 MFEC映射关系将 IGMP/MLD ( *,G ) report报文中的( *,G )字段转换为( *,G/M )字段,建立以( S,G/M ) 为标识的组播路由和转发表项, 在表项中添加出接口, 或者采用静态配 置的方式, 配置 IGMP/MLD静态加入 ( *,G/M ), 从而触发 PIM SM构 建分发树。
其中, 在该 MFEC上的这些 (*,G ) 的共享树汇聚点 (RP )是相同 的, 否则无法聚合成(*,G/M )状态, 这是因为按照现有协议, 路由器 上生成的 Join报文只能发送给同一个 RP, 如果在 MFEC中对应了多个 RP, 在 Egress路由器上会生成( *,G/M )的 Join报文, 该报文只能发送 给一个 RP, 那么注定有一些组播源是该 RP找不到的。
4、 Egress路由器计算并生成基于( *,G/M )的 PIM Join报文, 并向 RP方向发送( *,G/M ) 的 PIM Join报文。
5、 在 Transit路由器上创建以 ( *,G/M ) 为标识的组播路由 /转发表 项, 并在表项中添加出接口。
6、 Transit路由器计算并生成基于 ( *,G/M ) 的 PIM Join报文, 向 RP方向发送基于 ( *,G/M ) 的 PIM Join报文。
7、 在 RP路由器上创建以 (*,G/M ) 为标识的组播路由 /转发表项, 并在表项中添加出接口。
8、 源指定路由器(DR ) 向 RP单播注册(register )报文。 源 DR 是距离组播源最近的三层网络节点, 组播源的组播数据包会不断地发送 给源 DR, 但源 DR在没接收到加入该组播组的请求时是不会转发该数 据包的。 该单播动作并非限制在本流程的本步骤中进行, 事实上, 源 DR的 register报文是周期性地发送给 RP的, 目的是让 RP获知组播源 的存在, 而 RP的作用就在于将接收者主机与组播源联系在一起, 也能 通过 RP从组播源接收数据包。
如果源 DR是 Ingress路由器,则根据 MFEC映射关系将组播源( S,G ) 转换为 (S,G/M )状态, 向 RP单播基于 (S,G/M ) 的 register报文。 如 果 RP是 Ingress路由器, 则本发明中 RP接收到 ( S,G ) register报文后, 根据 MFEC映射表将 register报文中的 (S,G )转换为 ( S,G/M )状态。
9、 源 DR接收组播源发送的组播数据包, 并在出接口上向下游转发 组播数据包, 通过 Transit路由器和 Egress路由器将组播数据包发送给 接收者的主机。
本实施例是在接收者不指定组播源的情况下, 构建共享树并转发组 播数据包的方法。 在上述的方法种, 需要借助 RP将接收者要加入的组 播组与组播源联系在一起。 通过 RP转发组播数据包的路径称为共享树 ( RPT ), 由于 RPT—般并非是接收者到组播源的最优路径, 并且 RPT 往往为多个 (*,G ) 的转发请求服务, 其负载较大, 因此协议中规定, 在一定的触发条件下,要将 RPT路径上的流量切换到最优路径, 也就是 接收者与组播源间的最短路径树(SPT )上, SPT—般也称为源树。 切 换的触发条件由用户设定,一般可以设置为 Egress路由器接收到的下行 组播数据包的流量大于 0或大于某个速率, 比如 lMbit/s。本发明的实施 例四描述了该切换过程, 其流程如图 6所示, 包括以下步骤:
1、 在 Egress路由器和 Ingress路由器上预先设置( *,G )或 (S,G ) 到 MFEC的映射关系为 (*,G/M )或 (S,G/M )。
2、 组播数据包原本是沿 RPT转发, 此时, 图 6中直连接收者主机 的 Egress路由器发起 SPT切换,计算并向组播源方向发送基于( S,G/M ) 的 PIM Join报文。
3、 在 Transit路由器上创建以 ( S,G/M ) 为标识的组播路由 /转发表 项, 并在表项中添加出接口, 计算并生成基于 ( S,G/M ) 的 PIM Join报 文, 向源方向发送 PIM Join报文。
4、 源 DR如果是 Ingress路由器, 则根据步骤 1 , 在源 DR上已经存 在 (S,G/M ) 的映射关系, 则创建以 (S,G/M ) 为标识的组播路由 /转发 表项,并在表项中添加出接口;否则源 DR有可能和 Ingress路由器直连, 也有可能在其间还有其他路由器, 对于这种情况有两种解决方法:
1 )在源 DR路由器与 Ingress路由器之间的路由器上可以静态配置 基于 MFEC的组播转发表项和组播路由表项, 生成(S,G/M ) 的路由表 项和转发表项,通过该配置由 Ingress路由器向源 DR路由器转发数据包;
2 ) Ingress路由器根据步骤 1中的映射关系将 MFEC分解为相应的 多个(S,G ), 按照常规方式向组播源方向发送每个(S,G ) 的 PIM Join 报文。
5、 源 DR接收组播源发送的组播数据包, 并在出接口上将组播数据 包向下游转发。
6、 Transit路由器接收组播数据包, 沿 SPT向下游转发组播数据包。
7、 直连接收者的最后一跳路由器, 接收来自 SPT上游的组播数据 包, 发起剪枝过程, 因为其已经通过 SPT来接收组播数据包, 需要删除 RPT, 于是计算并向 RP方向发送基于(S,G/M ) 的剪枝(Prune )报文。
8、 RPT上的 Transit路由器剪枝( S,G/M )的出接口, 并向 RP方向 发送基于 ( S,G/M ) 的 Prune报文。
9、 RP剪枝(S,G/M ) 的出接口, 向源 DR发送( S,G/M )的停止注 册( register stop )报文, 源 DR剪枝( S,G/M ) 的 register出接口, 不再 沿 RPT转发数据包。
以上实施例二至实施例四都采用了 MFEC的动态应用方式, 即根据 预先设置的 MFEC映射关系,以收到 IGMP/MLD report/PIM等组播协议 报文为触发条件, 将组播(S/*,G )状态转换成相应的 MFEC状态, 并 促使组播路由协议构建基于 MFEC的组播分发树。 当然也可以采用静态 应用方式,直接定义基于 MFEC的静态加入,创建基于 MFEC的组播分 发树, 在路由器上定义 MFEC路由项及转发项, 直接指导数据包转发。 此外, 可以为每个 MFEC状态设定主备两个入接口, 增强组播转发的健 壮性。 还可以将动态应用方式和静态应用方式相结合, 在部分网络节点 上使用动态方式, 部分网络节点上使用静态方式, 例如在 Egress路由器 上使用静态方式, 其它路由器上使用动态方式。
本发明的实施例中还提供了一种出口网络节点。 图 7为本发明的实 施例中出口网络节点的结构图。 如图 7所示, 本发明实施例中的出口网 络节点 700包括: 划分模块 701、 接收模块 702、 转换模块 703和发送 模块 704;
所述划分模块 701 , 用于将采用相同方式转发的组播数据包的集合 划分为组播转发等价类, 并设置所述同一组播转发等价类的组播数据包 与所述组播转发等价类之间的映射关系;
所述接收模块 702, 用于将所接收到的加入报文输出给所述转换模 块 703; 将所接收到的组播数据包输出给发送模块 704;
所述转换模块 703 , 用于根据从划分模块 701 中获取的映射关系, 将所接收的加入报文映射为基于所述组播转发等价类的加入报文, 建立 以所述组播转发等价类标识的转发指导信息; 将所述映射后的报文和所 述转发指导信息输出给发送模块 704;
所述发送模块 704, 用于将所接收到的所述映射后的加入报文发送 给上游网络节点; 根据转发指导信息将所接收到的组播数据包发送给下 游网络节点。
其中, 所述转换模块 703 , 还用于在所述转发指导信息中添加出接 口; 而所述根据转发指导信息将所接收到的组播数据包发送给下游网络 节点则包括: 根据转发指导信息中的出接口将所接收到的组播数据包发 送给下游网络节点。
本发明的实施例中还提供了一种入口网络节点。 图 8为本发明的实 施例中出口网络节点的结构图。 如图 8所示, 本发明实施例中的入口网 络节点 800包括: 划分模块 801、 接收模块 802、 转换模块 803和发送 模块 804;
所述划分模块 801 , 用于将采用相同方式转发的组播数据包的集合 划分为组播转发等价类, 并设置所述同一组播转发等价类的组播数据包 与所述组播转发等价类之间的映射关系;
所述接收模块 802, 用于将所接收到的加入报文输出给所述转换模 块 803; 将所接收到的组播数据包输出给发送模块 804;
所述转换模块 803 , 用于根据所接收到的加入报文以及从划分模块 801 中获取的映射关系, 建立以所述组播转发等价类标识的转发指导信 息; 将所述转发指导信息输出给发送模块 804;
所述发送模块 804, 用于根据所述转发指导信息将所接收到的组播 数据包发送给下游网络节点。
其中, 所述转换模块 803 , 还用于在所述转发指导信息中添加出接 口; 而所述根据转发指导信息将所接收到的组播数据包发送给下游网络 节点则包括: 根据转发指导信息中的出接口将所接收到的组播数据包发 送给下游网络节点。
总之, 在本发明的实施例中, 由于对流经相同分发树或子树的数据 包使用同一组组播转发表项, 这些组播数据包称为组播转发等价类 MFEC, 同一组播转发等价类的数据报文使用同一个组播转发表项进行 转发, 可以加快路由收敛时间, 降低空间占用, 提高空间和时间效率; 对协议报文也不再以单独的 (S,G )或 (*,G )为粒度, 而是基于组播转 发等价类, 可以提高状态处理和报文交互的效率。

Claims

权利要求书
1、 一种组播方法, 包括加入组播组的过程和转发组播数据包的过 程, 其特征在于, 在加入组播组的过程中, 在组播转发等价类所属分发 树或分发子树的网络节点上, 建立以组播转发等价类标识的组播转发指 导信息;
在转发组播数据包的过程中, 将同一组播转发等价类的组播数据包 根据同一个组播转发指导信息转发。
2、 根据权利要求 1所述的组播方法, 其特征在于, 将采用相同方式 转发的组播数据包划分为组播转发等价类。
3、 根据权利要求 1所述的组播方法, 其特征在于, 所述建立以组播 转发等价类标识的组播转发指导信息的过程包括:
所述组播转发等价类所属分发树或分发子树的出口网络节点接收 到激励后, 向所述分发树或分发子树的上游网络节点发送加入报文, 建 立以组播转发等价类标识的组播转发指导信息, 并在所述组播转发指导 信息中添加出接口, 所述上游网络节点建立以组播转发等价类标识的组 播转发指导信息, 在所述组播转发指导信息中添加出接口, 并继续向上 游发送力口入报文。
4、 根据权利要求 3所述的组播方法, 其特征在于, 该方法进一步包 括:
入口网络节点接收到下游网络节点的加入报文后, 建立以所述组播 转发等价类标识的组播转发指导信息, 在所述组播转发指导信息中添加 出接口。
5、 根据权利要求 1、 2、 3或 4所述的组播方法, 其特征在于, 所述 相同方式转发具体为流经相同的组播分发树或分发子树的组播数据包 进行相同的转发处理。
6、 根据权利要求 1、 2、 3或 4所述的组播方法, 其特征在于, 该方 法进一步包括:
在所述分发树或分发子树的出口网络节点及入口网络节点上设置 所述同一组播转发等价类的组播数据包与所述组播转发等价类之间的 映射关系 , 确定所述组播转发等价类中包含的组播数据包。
7、 根据权利要求 6所述的组播方法, 其特征在于, 所述接收到激励 具体包括:
所述出口网络节点接收到属于同一组播转发等价类的组播数据包 的接收者主机加入报文或下游网络节点的加入报文, 根据所述映射关系 将加入不同组播组的加入报文映射为基于所述组播转发等价类的报文, 创建以所述组播转发等价类标识的组播转发指导信息, 在所述组播转发 指导信息中添加出接口。
8、 根据权利要求 3或 4所述的组播方法, 其特征在于, 所述接收到 激励具体包括:
在接口上配置静态加入, 创建标识所述组播转发等价类的组播转发 指导信息。
9、 根据权利要求 7所述的组播方法, 其特征在于, 所述将多个加入 不同组播组的加入报文映射为基于组播转发等价类的报文具体包括: 在所述多个加入报文中, 根据所述同一组播转发等价类的组播数据 包与组播转发等价类间的映射关系, 用标识所述组播转发等价类的字 段, 替换标识所述属于同一组播转发等价类的组播数据包的组播组地址 对字段; 或者根据所述组播数据包与组播转发等价类间的映射关系, 在 所述多个加入报文中增加标识所述组播转发等价类的字段, 并向全网广 播该标识方法与所述组播转发等价类的对应关系,或通过命令配置所述 对应关系。
10、 根据权利要求 6所述的组播方法, 其特征在于, 该方法进一步 包括:
如果在所述分发树或分发子树的入口网络节点与组播源之间存在 其它网络节点, 则在所述入口网络节点与组播源之间的网络节点上配置 以所述组播转发等价类标识的组播转发指导信息, 生成相应的路由表项 和转发表项, 通过该配置向组播源方向发送加入艮文;
11、 根据权利要求 6所述的组播方法, 其特征在于, 该方法进一步 包括:
如果在所述分发树或分发子树的入口网络节点与组播源之间存在 其它网络节点, 则在所述入口网络节点上, 根据所述映射关系, 将基于 组播转发等价类的加入报文分解为所述组播转发等价类包含的组播数 据包的加入报文, 并向上游路由器发送所述分解后的加入报文。
12、 根据权利要求 5所述的组播方法, 其特征在于, 所述转发组播 数据包具体包括:
入口网络节点接收到隶属于同一组播转发等价类的组播数据包后, 根据所述映射关系, 查询所述组播转发指导信息, 在相应出接口上向下 游节点转发所述组播数据包;
出口网络节点接收到所述组播数据包, 查询组播转发指导信息, 并 在相应出接口上转发所述组播数据包。
13、 根据权利要求 12所述的组播方法, 其特征在于, 该方法进一步 包括:
传输网络节点接收到所述入口网络节点发送的组播数据包, 根据所 述标识组播转发等价类的字段, 查询组播转发指导信息, 在相应出接口 上向出口网络节点转发所述组播数据包。
14、 根据权利要求 12所述的组播方法, 其特征在于, 如果所述出口 网络节点与接收者主机之间存在其它网络节点, 则在所述出口网络节点 与接收者主机之间的网络节点上配置以所述组播转发等价类标识的组 播转发指导信息, 生成相应的路由表项和转发表项, 通过该配置向接收 者主机方向转发组播数据包; 或者, 在所述出口网络节点与接收者主机 之间的网络节点上, 查询以所述组播数据包的地址对标识的组播转发指 导信息, 并向下游网络节点转发所述组播数据包。
15、 一种组播路由方法, 其特征在于, 包括:
将采用相同方式转发的组播数据包的集合划分为组播转发等价类, 组播转发等价类所属分发树或分发子树的出口网络节点接收到激励后, 则向所述分发树或分发子树的上游网络节点发送加入报文, 建立以组播 转发等价类标识的组播转发指导信息, 并在所述转发指导信息中添加出 接口, 所述上游网络节点建立以组播转发等价类标识的组播转发指导信 息, 在所述转发指导信息中添加出接口, 并继续向上游发送加入报文, 一直到达所述分发树或分发子树的入口网络节点上。
16、 根据权利要求 15所述的组播方法, 其特征在于, 所述相同方式 转发具体为流经相同的组播分发树或分发子树并进行相同的转发处理。
17、 一种组播方法, 其特征在于, 包括: 将采用相同方式转发的组 播数据包的集合划分为组播转发等价类, 在组播转发等价类所属分发树 或分发子树的网络节点上, 静态配置以组播转发等价类标识的组播转发 指导信息, 将同一组播转发等价类的组播数据包根据同一个组播转发指 导信息转发。
18、 根据权利要求 17所述的组播方法, 其特征在于, 所述相同方式 转发具体为流经相同的组播分发树或分发子树并进行相同的转发处理。
19、 一种出口网络节点, 其特征在于, 该出口网络节点包括: 划分 模块、 接收模块、 转换模块和发送模块; 所述划分模块, 用于将采用相同方式转发的组播数据包的集合划分 为组播转发等价类, 并设置所述同一组播转发等价类的组播数据包与所 述组播转发等价类之间的映射关系;
所述接收模块, 用于将所接收到的加入报文输出给所述转换模块; 将所接收到的组播数据包输出给发送模块;
所述转换模块, 用于根据从划分模块中获取的映射关系, 将所接收 的加入报文映射为基于所述组播转发等价类的加入报文, 建立以所述组 播转发等价类标识的转发指导信息; 将所述映射后的报文和所述转发指 导信息输出给发送模块;
所述发送模块, 用于将所接收到的所述映射后的加入报文发送给上 游网络节点; 根据转发指导信息将所接收到的组播数据包发送给下游网 络节点。
20、 根据权利要求 19所述的出口网络节点, 其特征在于: 所述转换模块, 还用于在所述转发指导信息中添加出接口; 所述根据转发指导信息将所接收到的组播数据包发送给下游网络 节点包括: 根据转发指导信息中的出接口将所接收到的组播数据包发送 给下游网络节点。
21、 一种入口网络节点, 其特征在于, 该入口网络节点包括: 划分 模块、 接收模块、 转换模块和发送模块;
所述划分模块, 用于将采用相同方式转发的组播数据包的集合划分 为组播转发等价类, 并设置所述同一组播转发等价类的组播数据包与所 述组播转发等价类之间的映射关系;
所述接收模块, 用于将所接收到的加入报文输出给所述转换模块; 将所接收到的组播数据包输出给发送模块;
所述转换模块, 用于根据所接收到的加入报文以及从划分模块中获 取的映射关系, 建立以所述组播转发等价类标识的转发指导信息; 将所 述转发指导信息输出给发送模块;
所述发送模块, 用于根据所述转发指导信息将所接收到的组播数据 包发送给下游网络节点。
22、 根据权利要求 21所述的入口网络节点, 其特征在于: 所述转换模块, 还用于在所述转发指导信息中添加出接口; 所述根据转发指导信息将所接收到的组播数据包发送给下游网络 节点包括: 根据转发指导信息中的出接口将所接收到的组播数据包发送 给下游网络节点。
PCT/CN2008/070187 2007-02-05 2008-01-25 Multicast method and multicast routing method Ceased WO2008095435A1 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP08706564A EP2109260A4 (en) 2007-02-05 2008-01-25 MULTICAST PROCESS AND MULTICAST ROUTING PROCESS
US12/267,296 US8009671B2 (en) 2007-02-05 2008-11-07 Multicast method and multicast routing method

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200710003486A CN101242342B (zh) 2007-02-05 2007-02-05 组播方法及组播路由方法
CN200710003486.4 2007-02-05

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US12/267,296 Continuation US8009671B2 (en) 2007-02-05 2008-11-07 Multicast method and multicast routing method

Publications (1)

Publication Number Publication Date
WO2008095435A1 true WO2008095435A1 (en) 2008-08-14

Family

ID=39681278

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2008/070187 Ceased WO2008095435A1 (en) 2007-02-05 2008-01-25 Multicast method and multicast routing method

Country Status (4)

Country Link
US (1) US8009671B2 (zh)
EP (1) EP2109260A4 (zh)
CN (1) CN101242342B (zh)
WO (1) WO2008095435A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112260950A (zh) * 2020-10-19 2021-01-22 桂林电子科技大学 一种基于业务优先级区分的云存储网络组播流调度方法

Families Citing this family (44)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102025516B (zh) * 2009-09-16 2015-05-13 中兴通讯股份有限公司 一种实现组播业务的方法及系统
US9274851B2 (en) 2009-11-25 2016-03-01 Brocade Communications Systems, Inc. Core-trunking across cores on physically separated processors allocated to a virtual machine based on configuration information including context information for virtual machines
US8855102B2 (en) * 2010-01-29 2014-10-07 Elster Solutions, Llc Wireless communications providing interoperability between devices capable of communicating at different data rates
CA2788325C (en) * 2010-01-29 2016-01-19 Elster Solutions, Llc High priority data reads for acquisition of real-time data in wireless mesh network
US8769155B2 (en) 2010-03-19 2014-07-01 Brocade Communications Systems, Inc. Techniques for synchronizing application object instances
US20110228772A1 (en) 2010-03-19 2011-09-22 Brocade Communications Systems, Inc. Providing multicast services without interruption upon a switchover
US8495418B2 (en) 2010-07-23 2013-07-23 Brocade Communications Systems, Inc. Achieving ultra-high availability using a single CPU
US9104619B2 (en) 2010-07-23 2015-08-11 Brocade Communications Systems, Inc. Persisting data across warm boots
CN102457386B (zh) * 2010-10-25 2014-07-16 杭州华三通信技术有限公司 一种通信设备的双向pim中组播报文转发方法和通信设备
US8683027B2 (en) * 2011-06-08 2014-03-25 International Business Machines Corporation Utilization of uncertainty dependency relationships between items in a data stream
ES2551400T3 (es) * 2011-06-22 2015-11-19 Huawei Technologies Co., Ltd Descubrimiento de un enrutador de último salto de multidifusión independiente del protocolo
US9143335B2 (en) 2011-09-16 2015-09-22 Brocade Communications Systems, Inc. Multicast route cache system
CN102315967B (zh) * 2011-09-19 2017-04-12 中兴通讯股份有限公司 一种组播标签交换路径的中间节点保护方法及装置
CN103503370A (zh) * 2011-10-26 2014-01-08 华为技术有限公司 负载降低的方法及装置
CN102404205B (zh) * 2011-11-04 2017-11-28 中兴通讯股份有限公司 一种抑制组播路由震荡的方法及设备
US9219613B1 (en) * 2011-11-04 2015-12-22 Arris Enterprises, Inc. Alternative set-top gateway source for DOCSIS 3.0
US10581763B2 (en) 2012-09-21 2020-03-03 Avago Technologies International Sales Pte. Limited High availability application messaging layer
US9967106B2 (en) 2012-09-24 2018-05-08 Brocade Communications Systems LLC Role based multicast messaging infrastructure
US9203690B2 (en) 2012-09-24 2015-12-01 Brocade Communications Systems, Inc. Role based multicast messaging infrastructure
US9007944B2 (en) * 2012-10-25 2015-04-14 Microsoft Corporation One-to-many and many-to-one communications on a network
US9712334B2 (en) * 2013-05-21 2017-07-18 Brocade Communications Systems, Inc. Efficient multicast topology construction in a routed network
US9762532B2 (en) * 2013-08-14 2017-09-12 Coriant Oy Method and network device for configuring a data transfer network
CN104579966B (zh) 2013-10-14 2018-08-17 华为技术有限公司 转发表项生成的方法、转发节点和控制器
US9407555B2 (en) * 2014-03-31 2016-08-02 Juniper Networks, Inc. Systems and methods for load balancing multicast traffic
WO2015196361A1 (zh) 2014-06-24 2015-12-30 华为技术有限公司 一种软件定义网络的多播方法、装置及系统
US9619349B2 (en) 2014-10-14 2017-04-11 Brocade Communications Systems, Inc. Biasing active-standby determination
CN104468144B (zh) * 2014-11-28 2018-08-14 北京华为数字技术有限公司 一种空间多播的方法,装置及系统
CN106330774A (zh) * 2015-06-29 2017-01-11 中兴通讯股份有限公司 一种微波链路传输业务数据的方法及装置
CN106941437B (zh) * 2016-01-04 2020-11-17 中兴通讯股份有限公司 一种信息传输方法及装置
CN106301694B (zh) * 2016-08-11 2020-06-19 浙江宇视科技有限公司 一种减少可靠组播传输中数据包重传次数的方法及装置
CN106817308B (zh) * 2016-12-30 2019-12-24 北京华为数字技术有限公司 一种组播流的转发系统、方法及装置
CN106603558B (zh) * 2016-12-30 2019-08-06 杭州迪普科技股份有限公司 Pim-sm下组播源的注册方法和装置
CN109150711B (zh) * 2017-06-19 2022-04-29 中兴通讯股份有限公司 点到多点二层组播业务的保护倒换方法、装置及存储介质
US11310306B2 (en) 2018-11-08 2022-04-19 Juganu, Ltd. Systems and methods for reliable firmware update in tree-based wireless networks
US11297468B2 (en) 2018-11-08 2022-04-05 Juganu, Ltd. Efficient multicast group routing across tree-based wireless network
US11166220B2 (en) 2018-11-08 2021-11-02 Juganu, Ltd. Next-hop routing over a plurality of distinct channels in a mesh network
EP3878215A4 (en) * 2018-11-08 2022-10-19 Juganu Ltd. SYSTEMS AND METHODS FOR MULTICAST GROUP ROUTING, FIRMWARE UPDATE AND NEXT-HOP ROUTING IN TREE-BASED WIRELESS NETWORKS
CN109495908B (zh) * 2018-12-05 2022-03-11 国网辽宁省电力有限公司大连供电公司 一种基于lte无线与超低功耗物联网无线融合的网络优化方法
US11032094B2 (en) * 2019-08-15 2021-06-08 Itron, Inc. Optimized multicast group forwarding
CN111917651B (zh) * 2020-07-13 2022-04-15 烽火通信科技股份有限公司 一种交叉芯片的组播转发方法及系统
US11296983B1 (en) * 2020-09-23 2022-04-05 Nokia Solutions And Networks Oy Stateless multicasting over traffic engineered unicast tunnels
US12615166B2 (en) * 2022-07-12 2026-04-28 Hewlett Packard Enterprise Development Lp Overlay multicast orchestration in software-defined wide area network
CN115442294B (zh) * 2022-07-29 2023-10-31 中盈优创资讯科技有限公司 一种基于bier和ipv 6组播的文件分发方法及装置
CN117812027B (zh) * 2024-02-29 2024-04-30 北京极客天成科技有限公司 Rdma加速组播方法、装置、设备及存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1378365A (zh) * 2002-05-10 2002-11-06 北京港湾网络有限公司 一种ip组播路由转发优化方法
CN1595879A (zh) * 2003-09-08 2005-03-16 华为技术有限公司 一种大容量组播路由表下提高组播数据转发效率的方法
WO2005039085A2 (en) * 2003-10-07 2005-04-28 Cisco Technology, Inc. Enhanced switchover for mpls fast reroute
JP2005236640A (ja) * 2004-02-19 2005-09-02 Nippon Telegr & Teleph Corp <Ntt> Vpnマルチキャストパケット転送方法及びそれを用いたネットワークシステム並びにそれを構成する装置及びプログラム
CN1881931A (zh) * 2005-06-13 2006-12-20 中兴通讯股份有限公司 组播转发路由聚合方法

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6728777B1 (en) * 1999-06-02 2004-04-27 Nortel Networks Limited Method for engineering paths for multicast traffic
KR20030047227A (ko) * 2001-12-08 2003-06-18 삼성전자주식회사 이동통신시스템에서 방송서비스의 종료를 위한 방법 및 장치
CN1330139C (zh) * 2003-07-31 2007-08-01 华为技术有限公司 多协议标签交换(mpls)支持多端口虚拟局域网(vlan)的方法
US8089964B2 (en) * 2005-04-05 2012-01-03 Cisco Technology, Inc. Transporting multicast over MPLS backbone using virtual interfaces to perform reverse-path forwarding checks
US7529199B1 (en) * 2005-05-31 2009-05-05 Cisco Technology, Inc. System and method for resolving conflicts in proxy routing information associated with multicast distribution trees
US20070147371A1 (en) * 2005-09-26 2007-06-28 The Board Of Trustees Of Michigan State University Multicast packet video system and hardware
US8068481B2 (en) * 2006-05-25 2011-11-29 Cisco Technology, Inc. Techniques for reliable switchover to a date multicast distribution tree (MDT)
US8259612B2 (en) * 2006-06-09 2012-09-04 Cisco Technologies, Inc. Method of routing multicast traffic
US7899046B2 (en) * 2006-07-07 2011-03-01 Ver Steeg William C Determining strategy for multicast and/or unicast transmission to correct forward errors

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1378365A (zh) * 2002-05-10 2002-11-06 北京港湾网络有限公司 一种ip组播路由转发优化方法
CN1595879A (zh) * 2003-09-08 2005-03-16 华为技术有限公司 一种大容量组播路由表下提高组播数据转发效率的方法
WO2005039085A2 (en) * 2003-10-07 2005-04-28 Cisco Technology, Inc. Enhanced switchover for mpls fast reroute
JP2005236640A (ja) * 2004-02-19 2005-09-02 Nippon Telegr & Teleph Corp <Ntt> Vpnマルチキャストパケット転送方法及びそれを用いたネットワークシステム並びにそれを構成する装置及びプログラム
CN1881931A (zh) * 2005-06-13 2006-12-20 中兴通讯股份有限公司 组播转发路由聚合方法

Non-Patent Citations (1)

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

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112260950A (zh) * 2020-10-19 2021-01-22 桂林电子科技大学 一种基于业务优先级区分的云存储网络组播流调度方法

Also Published As

Publication number Publication date
US20090059923A1 (en) 2009-03-05
US8009671B2 (en) 2011-08-30
EP2109260A4 (en) 2010-07-28
CN101242342B (zh) 2012-09-19
CN101242342A (zh) 2008-08-13
EP2109260A1 (en) 2009-10-14

Similar Documents

Publication Publication Date Title
CN101242342B (zh) 组播方法及组播路由方法
US7839850B2 (en) Forming equal cost multipath multicast distribution structures
CN101656679B (zh) 一种组播快速收敛方法、路由器和通信系统
CN103493445B (zh) 一种ip组播数据的分层分发方法、系统
CN100454893C (zh) 一种快速组播的实现方法
CN101631274B (zh) 基于标识的组播路由实现系统及其方法
CN101292467A (zh) 用于多方音频视频会议的应用级路由协议
US8270395B2 (en) Forming multicast distribution structures using exchanged multicast optimization data
WO2025124433A9 (zh) 一种公有云中虚拟实例实现云内云间组播功能的方法
CN106790146A (zh) 一种云环境下基于sdn技术实现移动组播的系统及其运行方法
US10567180B2 (en) Method for multicast packet transmission in software defined networks
CN100417141C (zh) 一种组播业务实现方法
CN100477635C (zh) 一种域间组播的传输方法及边缘设备
WO2007054006A1 (en) A base station of wideband wireless access system and a method for realizing group-broadcast service
CN102340450A (zh) 一种支持非单一vlan的组播实现方法及装置
WO2012103748A1 (zh) 一种组播控制方法、路由设备及组播系统
CN101013948A (zh) 构建等耗多径多播分发结构
CN1996931A (zh) 网络组播方法
CN108111323B (zh) vxworks系统下igmpsnooping协议的实现系统
WO2009064165A2 (en) A fast packet forwarding engine for scalable routing
CN100440863C (zh) 扩展路由功能的具体源静态组功能实现方法
CN101227430A (zh) 组播数据转发方法
Yen et al. PIM-compliant SDN-enabled IP multicast service
Tripathi et al. Comparative Analysis of Quality of Service of Dense and CBT Mode of Multicast Routing Strategies
Wu et al. IP Network Multicast Technology and Application Simulation

Legal Events

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

Ref document number: 08706564

Country of ref document: EP

Kind code of ref document: A1

REEP Request for entry into the european phase

Ref document number: 2008706564

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2008706564

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE