WO2010075771A1 - 一种组播虚拟私有网络的外联网组网方法、***和装置 - Google Patents

一种组播虚拟私有网络的外联网组网方法、***和装置 Download PDF

Info

Publication number
WO2010075771A1
WO2010075771A1 PCT/CN2009/076182 CN2009076182W WO2010075771A1 WO 2010075771 A1 WO2010075771 A1 WO 2010075771A1 CN 2009076182 W CN2009076182 W CN 2009076182W WO 2010075771 A1 WO2010075771 A1 WO 2010075771A1
Authority
WO
WIPO (PCT)
Prior art keywords
multicast
vpn
source
instance
group address
Prior art date
Application number
PCT/CN2009/076182
Other languages
English (en)
French (fr)
Inventor
刘毅松
苏海洋
陈重
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP09836058.9A priority Critical patent/EP2378720B1/en
Publication of WO2010075771A1 publication Critical patent/WO2010075771A1/zh
Priority to US13/174,063 priority patent/US9031069B2/en

Links

Classifications

    • 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
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4641—Virtual LANs, VLANs, e.g. virtual private networks [VPN]
    • 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/50—Routing or path finding of packets in data switching networks using label swapping, e.g. multi-protocol label switch [MPLS]

Definitions

  • the invention relates to a method, system and device for networking an extranet virtual private network.
  • the application is submitted to the Chinese Patent Office on December 31, 2008, and the application number is 200810191759.7, and the invention name is "a kind of multicast virtual private network.”
  • the priority of the Chinese Patent Application for Networking, Method, and Apparatus is hereby incorporated by reference.
  • the embodiments of the present invention relate to the field of communications technologies, and in particular, to a method, system, and apparatus for networking an extranet virtual private network. Background technique
  • IP (Internet Protocol) multicast refers to sending a packet to a certain subset of nodes in the network in the form of best-effort in the IP network.
  • the subset of nodes is called multicast.
  • Group leg lticast group
  • the source host sends only one data.
  • the destination address in the data is the multicast group address. All receivers in the multicast group can receive the same data copy, and only the hosts in the multicast group can receive the data. Other hosts outside the multicast group cannot receive this data.
  • VPN Virtual Private Network
  • ISP Internet Service Provider
  • NSP Network Service Provider
  • the VPN consists of the CE (Customer Edge, the user network edge device), the PE (Provider Edge, the service provider network edge device), and the P (Provider, service provider network backbone router).
  • the CE is directly connected to the SP (Service Provider).
  • Network connection exclusive to a certain VPN, only for dedicated VPN services, only maintain a set of forwarding mechanisms, can be for routers or exchange
  • the machine can also be a host; the PE is directly connected to the CE, and is connected to the public network and the VPN network, and serves multiple VPNs at the same time; P is not directly connected to the CE.
  • PE and P are managed only by the SP, and the CE is managed only by the user unless the user delegates management rights to the SP.
  • a PE can access multiple CEs, and a CE can also connect multiple PEs belonging to the same or different service providers.
  • the PE must strictly distinguish the information of each network and maintain a set of forwarding mechanisms independently for each network.
  • a set of software and hardware facilities that serve the same network on the PE is called an instance. Multiple instances can exist on the PE at the same time. The same instance can be distributed on multiple PEs.
  • the multicast VPN solution needs to support the multicast function in the SP backbone network (the core network or the public network).
  • the multicast data and control packets in the private network instance are transmitted to the remote site of the VPN through the public network.
  • a multicast instance running on a VPN instance in a VPN instance is called a private network multicast instance.
  • a multicast instance running on the public network of a PE router is called a public network multicast instance.
  • the public network multicast instance does not need to know the multicast data transmitted on the private network.
  • the private network multicast instance does not need to know the multicast routing information in the public network instance.
  • the private network multicast instances are isolated from each other.
  • the networking solution may be that the source PE configures the receiver VPN multicast instance, and adds the receiver group's shared group Sha re-Group address in the newly configured receiver VPN multicast instance to establish a newly configured receiver VPN multicast.
  • the instance is connected to the multicast tunnel of the original receiver VPN multicast instance.
  • the original receiver VPN multicast instance and the newly configured receiver VPN multicast instance can communicate using the intranet int rane t mode.
  • the receiver VPN multicast instance and the source VPN multicast instance implement ex t rane t through local crossover, that is, through internal messages between different VPN multicast instances on the same device to complete PIM (Pro toco l Independent Mul) Ti ca st, protocol-independent multicast protocol) The transmission of text and multicast data.
  • the networking scheme in the prior art may also be that the receiver PE configures the source VPN multicast instance, and adds the Sha re-Group address of the original VPN to the newly configured source VPN multicast instance to establish a newly configured source VPN group.
  • the multicast instance is broadcasted to the multicast tunnel of the original VPN multicast instance.
  • the newly configured source VPN multicast instance and the original source VPN multicast instance can communicate using the int rane t mode.
  • the newly configured source VPN is configured.
  • Group The broadcast instance and the receiver VPN multicast instance implement the ext rane t in the local cross mode, that is, the internal message between different VPN multicast instances on the same device is used to communicate the PIM protocol packet and the multicast data packet. .
  • the inventor has found that at least the following problems exist in the prior art: In the prior art, whether the source PE configures the receiver VPN multicast instance or the receiver PE configures the source VPN multicast instance, The local private network cross-implements the multicast VPN ext rane t , and the multicast flow of the remote VPN site still uses the multicast tunnel of the same VPN. If the receiver VPN multicast instance needs to receive multicast data from multiple different source VPNs, the receiver PE must configure multiple source VPN multicast instances. The receiver PE may not have the services of the VPN instance. The system resources of the receiver PE router are too large. Source PE Configuration Receiver The same problem occurs with VPN multicast instances.
  • the embodiments of the present invention provide an extranet networking method, system, and device for a multicast virtual private network, which reduces network load.
  • the embodiment of the present invention provides a method for networking an extranet of a virtual private network (VPN) VPN, including: establishing a multicast tunnel to the source VPN multicast instance according to the shared group Share-Group address of the source VPN. And a multicast tunnel interface connected to the multicast tunnel;
  • VPN virtual private network
  • the public network multicast data packet of the source re-group of the source VPN is obtained, and the multicast data from the source VPN multicast instance is obtained.
  • the embodiment of the present invention further provides an extranet networking system of a multicast VPN, including a source VPN and a receiver VPN, where:
  • the receiver VPN is configured to establish a multicast tunnel to the source VPN multicast instance and a multicast tunnel interface connected to the multicast tunnel according to the shared group Share-Group address of the added source VPN.
  • the multicast tunnel interface sends the encapsulated protocol-independent multicast PIM protocol packet, and the encapsulated PIM protocol packet is forwarded in the public network, and the source VPN multicast instance is encapsulated according to the encapsulated PIM
  • the protocol packet generates the public network multicast data packet of the Share-Group of the source VPN, and decapsulates the received public network multicast data packet of the source VPN of the source VPN, and obtains the source VPN multicast source from the source VPN.
  • the multicast data of the instance is configured to establish a multicast tunnel to the source VPN multicast instance and a multicast tunnel interface connected to the multicast tunnel according to the shared group Share-Group address of the added source VPN.
  • the multicast tunnel interface sends the encapsulated protocol-independent multicast PIM protocol packet, and the encapsulated
  • An embodiment of the present invention further provides a receiver VPN multicast instance, including:
  • Establishing a module configured to establish a multicast tunnel to the source VPN multicast instance, and a multicast tunnel interface connected to the multicast tunnel, according to the share-group address of the added source VPN;
  • a sending module configured to send the encapsulated PIM protocol packet to the multicast tunnel interface established by the establishing module, forward the encapsulated PIM protocol packet in the public network, and enable the source VPN multicast
  • the instance generates a public network multicast data packet of the Share-Group of the source VPN according to the encapsulated PIM protocol.
  • the obtaining module is configured to decapsulate the received public network multicast data packet of the Share-Group of the source VPN, and obtain the multicast data from the source VPN multicast instance.
  • the technical solution of the embodiment of the present invention has the following advantages: the share-group address of the source VPN is added to the receiver VPN multicast instance, and the multicast tunnel of the receiver VPN multicast instance to the source VPN multicast instance is established, thereby reducing The occupation of router system resources reduces the network load.
  • FIG. 1 is a flowchart of a method for networking an extranet of a multicast VPN according to an embodiment of the present invention
  • FIG. 2 is a flowchart of another method for networking an extranet of a multicast VPN according to an embodiment of the present invention
  • FIG. 4 is a flowchart of a method for networking an extranet of a multicast VPN according to an embodiment of the present invention
  • FIG. 5 is a schematic structural diagram of a VPN instance of a receiver according to an embodiment of the present invention. Another structure of the receiver VPN multicast instance in the example. detailed description
  • the VPN instance is not configured separately, and the source-group address of the source VPN is added to the receiver VPN multicast instance, so that the PIM protocol packet of the receiver VPN can reach the remote source VPN, and the multicast data of the source VPN.
  • the message can also reach the far-end receiver VPN.
  • FIG. 1 it is a flowchart of an extranet networking method for a multicast VPN according to an embodiment of the present invention, which includes the following steps:
  • Step 101 Establish a multicast tunnel to the source VPN multicast instance and a multicast tunnel interface connected to the multicast tunnel according to the Sha re-Group address of the added source VPN.
  • the VPN instance that provides the multicast data source is called the source VPN multicast instance
  • the PE router where the source VPN multicast instance is located is called the source PE
  • the VPN instance that needs to receive the multicast data is called the receiver VPN group.
  • the broadcast instance is not in the same VPN as the source VPN multicast instance.
  • the PE router where the receiver VPN multicast instance resides is called the receiver PE.
  • Receiver VPN multicast instance is added to the shared group of the source VPN. After the share-group address, the multicast data forwarding range of the source VPN multicast instance is specified.
  • PIM SM Parse Mode
  • the forwarding range of the multicast data of the specified source VPN multicast instance is the private network group address range
  • PIM SSM Source Spec ic M tec icas t, the source multicast
  • the multicast forwarding range of the specified source VPN multicast instance is private. Source group address range.
  • Step 102 Send the encapsulated PIM protocol packet to the multicast tunnel interface, forward the encapsulated PIM protocol packet on the public network, and enable the source VPN multicast instance to generate the source VPN share according to the encapsulated PIM protocol packet. Group-shared public network multicast data packets.
  • the multicast tunnel interface of the encapsulated PIM protocol >3 ⁇ 4 text is determined according to the private network group address or the source group address.
  • the share-group corresponding to the multicast tunnel interface encapsulates the PIM protocol packet of the receiver VPN multicast instance into the encapsulated PIM protocol packet of the Share-Group, and encapsulates the encapsulated PIM protocol packet through the public network multicast instance.
  • the text is forwarded in the public network.
  • the source VPN multicast instance decapsulates the encapsulated PIM protocol packet forwarded by the public network to obtain the PIM protocol packet of the receiver VPN multicast instance.
  • the source VPN multicast instance obtains the receiver VPN multicast instance.
  • the source VPN multicast instance encapsulates the multicast data of the source VPN according to the PIM protocol packet, and sends the public network multicast data packet encapsulating the source VPN multicast data through the public network. Give the receiver a VPN multicast instance.
  • Step 103 Decapsulate the public network multicast data of the Share-Group of the source VPN, and obtain the multicast data from the source VPN multicast instance.
  • the source VPN multicast instance obtains the PIM protocol packet, and encapsulates the multicast data into the public network multicast data packet of the source VPN share-Group according to the PIM protocol packet, and encapsulates the encapsulated group through the public network multicast instance.
  • the broadcast data is forwarded in the public network.
  • the receiver VPN multicast instance receives the encapsulated multicast data, decapsulates the encapsulated multicast data, and obtains the multicast data, thereby implementing the extranet networking of the multicast VPN.
  • the receiver multicast multicast instance After receiving the multicast data from the source VPN multicast instance, the receiver multicast multicast instance checks whether the group address or source group address of the multicast data is within the forwarding range of the multicast data of the specified source VPN multicast instance. If the group address or source group address of the multicast data is within the forwarding range of the multicast data of the specified source VPN multicast instance, the multicast data is forwarded according to the receiver VPN multicast route; if the group address of the multicast data or If the source group address is not within the forwarding range of the multicast data of the specified source VPN multicast instance, the multicast data is discarded.
  • the embodiment of the present invention ensures isolation between VPN multicast instances.
  • the multicast forwarding with the remote site of the VPN and other source VPN remote sites are respectively different groups.
  • the multicast tunnels are used to send multicast protocol packets and receive multicast data packets.
  • each receiver VPN multicast is used.
  • the instance establishes a multicast tunnel to the source VPN. Only the source VPN is used for the address space forwarded by the ext rane.
  • the other address spaces of the VPN multicast instances are still isolated, that is, the int rane of the source VPN multicast instance.
  • the address space is invisible to each recipient VPN, and the int rane t and other ex t rane t address spaces of each recipient VPN instance are also invisible to each other.
  • the technical solution of the embodiment of the present invention has the following advantages: the multicast tunnel of the receiver VPN multicast instance to the source VPN multicast instance is established by adding the Share-Group address of the source VPN in the receiver VPN multicast instance, thereby reducing the pair.
  • the occupation of router system resources reduces the network load.
  • FIG. 2 it is a flow chart of another method for networking an extranet VPN in the embodiment of the present invention.
  • the method for networking the extranet of the multicast VPN is as shown in FIG.
  • PE1 is the PE router where the VPN RED multicast instance resides
  • PE2 is the PE router where the VPN BLUE multicast instance resides
  • CE1 is connected to the multicast source and CE2 is connected to the receiver.
  • the extranet networking method of the multicast VPN includes the following steps:
  • Step 201 Add a Share-Group address G1 to the VPN RED multicast instance on the PE1 side.
  • a VPN RED multicast instance is a VPN instance that provides a multicast data source, and PE1 is a VPN RED multicast instance.
  • the PE router where the instance is located. After the share of the Share-Grou address G1 is added to the VPN RED multicast instance, data can be transmitted to the public network.
  • Step 202 Add a Share-Grou address G1 to the VPN BLUE multicast instance on the PE2 side.
  • the VPN BLUE multicast instance is a VPN instance that needs to receive multicast data. It is not in the same VPN as the VPN RED multicast instance.
  • PE2 is the PE router where the VPN BLUE multicast instance resides. Add a Share-Grou address to the VPN BLUE multicast instance. After the G1 is configured, the private network group address range Gr/Mr is specified. The multicast tunnel of the VPN BLUE multicast instance to the VPN RED multicast instance can be established.
  • the CE1 is connected to the multicast source
  • the CE2 is connected to the receiver
  • the VPN RED multicast instance and the VPN BLUE multicast instance are both running PIM SM
  • the VPN RED RP Radvous Point
  • CE1 CE2
  • the interface connecting the receiver enables IGMP (Internet Group Management Protocol).
  • the VPN BLUE multicast instance can also add the VPN Share-Group address G2 to receive multicast data from the remote site of the VPN.
  • Step 203 The receiver sends an IGMP (*, G) report message to the CE2 to request the VPN RED to broadcast the data.
  • IGMP (*, G) report message
  • the private network group address of the message is G, and the private network source address is vacant.
  • Step 204 CE2 sends a PIM (*, G) join request to PE2.
  • the PIM (*, G) join request is a PIM protocol packet.
  • the private network group address of the packet is G, and the private network source address is vacant.
  • Step 205 The PE2 generates a multicast route (*, G) entry of the VPN BLUE multicast instance.
  • the private network group address of the multicast routing ( * , G ) entry is G and the private network source address is vacant.
  • Step 206 PE2 finds that the upstream router is PE 1 according to the RP address.
  • Step 207 The VPN BLUE multicast instance checks whether the private network group address of the multicast routing (*, G) entry belongs to the specified private network group address range Gr/Mr.
  • Step 208 the VPN BLUE multicast instance discards the PIM (*, G) join request.
  • Step 209 The VPN BLUE multicast instance encapsulates the PIM (*, G) join request through the multicast tunnel to the VPN RED multicast instance.
  • Step 210 The multicast distribution tree of the public network G1 sends the encapsulated PIM (*, G) join request.
  • Step 211 The VPN RED multicast instance decapsulates the public network data from the multicast distribution tree of the public network G1, and obtains a PIM (*, G) join request.
  • Step 212 The VPN RED multicast instance processes the PIM (*, G) join request to generate a multicast route (*, G) entry.
  • Step 213 CE1 sends VPN RED multicast data (S, G) to PE1.
  • the private network group address of the VPN RED multicast data is G, and the private network source address is S.
  • Step 214 PE 1 creates a multicast route (S, G) entry.
  • the private network group address of the multicast routing (S, G) entry is G, and the private network source address is S.
  • Step 215 The VPN RED multicast instance encapsulates the VPN RED multicast data (S, G) through the VPN RED multicast tunnel.
  • Step 216 The multicast distribution tree of the public network G1 sends the private network multicast data of the encapsulated VPN RED.
  • Step 217 The VPN BLUE multicast instance decapsulates the public network data from the public network G1 multicast distribution tree, and obtains VPN RED multicast data (S, G).
  • Step 218 The VPN BLUE multicast instance checks whether the private network group address of the VPN RED multicast data (S, G) belongs to the specified private network group address range Gr/Mr.
  • step 220 If the private network group address of the VPN RED multicast data (S, G) belongs to the specified private network group address range Gr/Mr, go to step 220; if the private network group address of the VPN RED multicast data (S, G) is not If the specified private network group address range is Gr/Mr, go to step 219.
  • Step 219 The VPN BLUE multicast instance discards the VPN RED multicast data (S, G).
  • Step 220 The VPN BLUE multicast instance creates a multicast route (S, G) entry.
  • Step 221 The VPN BLUE multicast instance forwards the VPN RED multicast data (S, G) to CE2.
  • the multicast tunnel of the receiver VPN multicast instance to the source VPN multicast instance is established by adding the Share-Group address of the source VPN in the receiver VPN multicast instance, and the receiving and receiving is performed.
  • Whether the private network group address of the multicast data belongs to the specified private network group address range ensures the isolation between the VPN multicast instances, reduces the occupation of the router system resources, and reduces the network load.
  • FIG. 4 it is a flow chart of a method for networking an extranet of a multicast VPN in the embodiment of the present invention.
  • the method for networking the extranet of the multicast VPN is as shown in FIG.
  • PE1 is the PE router where the VPN RED multicast instance resides
  • PE2 is the PE router where the VPN BLUE multicast instance resides
  • CE1 is connected to the multicast source and CE2 is connected to the receiver.
  • the extranet networking method of the multicast VPN includes the following steps:
  • Step 401 Add a Share-Group address G1 to the VPN RED multicast instance on the PE1 side.
  • a VPN RED multicast instance is a VPN instance that provides a multicast data source, and PE1 is a PE router where the VPN RED multicast instance resides. After the VPN RED multicast instance is added to the Share-Grou address G1, data can be transmitted to the public network.
  • Step 402 Add a Share-Grou address G1 to the VPN BLUE multicast instance on the PE2 side.
  • the VPN BLUE multicast instance is a VPN instance that needs to receive multicast data. It is not in the same VPN as the VPN RED multicast instance.
  • PE2 is the PE router where the VPN BLUE multicast instance resides. Add a Share-Grou address G1 to the VPN BLUE multicast instance, specify the private network source group address range (Sr/Ms r, Gr/Mgr), and establish a multicast tunnel from the VPN BLUE multicast instance to the VPN RED multicast instance.
  • the network performs data transmission.
  • the CE1 is connected to the multicast source
  • the CE2 is connected to the receiver
  • the VPN RED multicast instance, and the VPN BLUE multicast instance are both running PIM SSM
  • the interface of the CE2 directly connected to the receiver is enabled with IGMP.
  • Step 403 The receiver sends an IGMP (S, G) report message to the CE2 to request VPN RED multicast data.
  • the private network group address of the IGMP (S, G) report is G, and the private network source address is S.
  • Step 404 CE2 sends a PIM (S, G) join request to PE2.
  • the PIM (S, G) join request is the P IM protocol, and the private network group address is G and the private network source address is S.
  • Step 405 The PE2 generates a multicast route (S, G) entry of the VPN BLUE multicast instance.
  • the private network group address of the multicast routing (S, G) entry is G, and the private network source address is S.
  • Step 406 PE2 finds that the upstream router is PE1 according to the source address of the private network.
  • Step 407 The VPN BLUE multicast instance checks whether the private network source group address of the multicast routing (S, G) entry belongs to the specified private network source group address range (Sr/Msr, Gr/Mgr).
  • step 408 is performed.
  • Step 408 The VPN BLUE multicast instance discards the PIM (S, G) join request.
  • Step 409 The VPN BLUE multicast instance encapsulates the PIM (S, G) join request through the multicast tunnel to the VPN RED multicast instance.
  • Step 410 The multicast distribution tree of the public network G1 sends the encapsulated PIM (S, G) join request.
  • Step 411 The VPN RED multicast instance decapsulates the public network data from the multicast distribution tree of the public network G1, and obtains a PIM (S, G) join request.
  • Step 412 The VPN RED multicast instance processes the PIM (S, G) join request to generate a multicast route (S, G) entry.
  • Step 413 CE1 sends VPN RED multicast data (S, G) to PE1.
  • the private network group address of the VPN RED multicast data is G, and the private network source address is S.
  • Step 414 The VPN RED multicast instance encapsulates the VPN RED multicast data (S, G) through the multicast tunnel of the VPN RED.
  • Step 415 The multicast distribution tree of the public network G1 sends the private network multicast data (S, G) of the encapsulated VPN RED.
  • Step 416 The VPN BLUE multicast instance decapsulates the public network data from the public network G1 multicast distribution tree, and obtains the VPN RED multicast data (S, G).
  • Step 417 The VPN BLUE multicast instance checks whether the private network source group address of the VPN RED multicast data (S, G) belongs to the specified private network source group address range (Sr/Ms r, Gr/Mgr).
  • the private network group address of the VPN RED multicast data (S, G) belongs to the specified private network source group address range (Sr/Ms r, Gr/Mgr), go to step 419; if the VPN RED multicast data (S, If the private network source group address of the G) does not belong to the specified private network source group address range (Sr/Ms r, Gr/Mgr), go to step 418.
  • Step 418 The VPN BLUE multicast instance discards the VPN RED multicast data (S, G).
  • Step 419 The VPN BLUE multicast instance forwards the VPN RED multicast data (S, G) to the CE2.
  • the multicast tunnel of the receiver VPN multicast instance to the source VPN multicast instance is established by adding the Share-Group address of the source VPN in the receiver VPN multicast instance, and the receiving and receiving is performed. Whether the private network source group address of the multicast data belongs to the specified private network source group address range, ensures isolation between VPN multicast instances, reduces the occupation of router system resources, and reduces network load.
  • the embodiment of the present invention further provides a multicast VPN extranet networking system, including a source VPN and a receiver VPN, where: the recipient VPN is used to establish a sharing group Share-Group address according to the added source VPN.
  • the multicast tunnel to the source VPN multicast instance and the multicast tunnel interface connected to the multicast tunnel send the encapsulated protocol-independent multicast P IM protocol packet to the multicast tunnel interface, and forward the packet in the public network.
  • the encapsulated PIM protocol packet is generated, and the source VPN multicast instance generates a public network multicast data packet of the source-VPN Share-Group according to the encapsulated PIM protocol packet, and decapsulates the received source VPN.
  • the public network multicast data packet of the share-group obtains the multicast data from the source VPN multicast instance.
  • the receiver VPN multicast instance 500 includes:
  • the establishing module 510 is configured to establish a multicast tunnel to the source VPN multicast instance and a multicast tunnel interface connected to the multicast tunnel according to the share-group address of the added source VPN.
  • the VPN instance that provides the multicast data source is called the source VPN multicast instance
  • the PE router where the source VPN multicast instance is located is called the source PE
  • the VPN instance that needs to receive the multicast data is called the receiver VPN group.
  • the broadcast instance is not in the same VPN as the source VPN multicast instance.
  • the PE router where the receiver VPN multicast instance resides is called the receiver PE.
  • the establishment module 510 of the receiver VPN multicast instance adds the Share-Group address of the source VPN, and establishes the receiver VPN multicast instance to the source VPN group.
  • the sending module 520 is configured to send the encapsulated protocol-independent multicast PIM protocol packet to the multicast tunnel interface established by the establishing module 510, and forward the encapsulated PIM protocol packet in the public network, and make the source VPN multicast instance
  • the encapsulated PIM protocol packet generates the public network multicast data packet of the Share-Group of the source VPN.
  • the multicast tunnel interface that sends the encapsulated PIM protocol packet is determined according to the private network group address or the source group address, and the multicast tunnel interface is corresponding to the multicast tunnel interface.
  • the Sha re-Group encapsulates the PIM protocol packet of the receiver VPN multicast instance into the encapsulated PIM protocol of the Share-Group, and encapsulates the encapsulated PIM protocol packet through the public network multicast instance. Forward in the public network.
  • the source VPN multicast instance decapsulates the encapsulated PIM protocol forwarded in the public network, obtains the PIM protocol text of the receiver VPN multicast instance, and obtains the receiver VPN multicast instance in the source VPN multicast instance.
  • the source VPN multicast instance encapsulates the multicast data of the source VPN according to the PIM protocol packet, and sends the public network multicast data packet encapsulating the source VPN multicast data through the public network. Give the receiver a VPN multicast instance.
  • the obtaining module 530 is configured to decapsulate the received public network multicast data packet of the source-VPN of the source VPN, and obtain the multicast data from the source VPN multicast instance.
  • the source VPN multicast instance obtains the PIM protocol packet, and encapsulates the multicast data into the public network multicast data packet of the source VPN Share-Group according to the PIM protocol packet, and encapsulates the encapsulated multicast data through the public network multicast instance. Forward in the public network.
  • the obtaining module 530 receives the encapsulated multicast data, decapsulates the encapsulated multicast data, obtains the multicast data, and implements an extranet networking of the multicast VPN.
  • the embodiment of the present invention ensures isolation between VPN multicast instances.
  • the multicast forwarding with the remote site of the VPN and other source VPN remote sites are respectively different groups.
  • the multicast tunnels are used to send multicast protocol packets and receive multicast data packets.
  • each receiver VPN multicast is used.
  • the instance establishes a multicast tunnel to the source VPN. Only the source VPN is used for the address space forwarded by the ext rane.
  • the other address spaces of the VPN multicast instances are still isolated, that is, the intranet of the source VPN multicast instance is int.
  • the rane t address space is invisible to each receiver VPN, and the int rane t and other ext rane t address spaces of each recipient VPN instance are also invisible to each other.
  • the technical solution of the embodiment of the present invention has the following advantages: the multicast tunnel of the receiver VPN multicast instance to the source VPN multicast instance is established by adding the Share-Group address of the source VPN in the receiver VPN multicast instance, thereby reducing the pair.
  • the occupation of router system resources reduces the network load.
  • FIG. 6 is a schematic diagram of another receiver VPN multicast instance structure in the embodiment of the present invention.
  • the receiver VPN multicast instance 600 includes:
  • the establishing module 610 is configured to establish a multicast tunnel to the source VPN multicast instance and a multicast tunnel interface connected to the multicast tunnel according to the share-group address of the added source VPN.
  • a VPN instance that provides a multicast data source is called a source VPN multicast instance, and the source is
  • the PE router where the VPN multicast instance resides is called the source PE.
  • the VPN instance that needs to receive multicast data is called the receiver VPN multicast instance.
  • the VPN instance is not in the same VPN as the source VPN multicast instance.
  • the PE of the receiver VPN multicast instance is located.
  • the router is called the receiver PE.
  • the setup module 610 of the receiver VPN multicast instance adds the Share-Group address of the source VPN, and establishes the receiver VPN multicast instance to the source VPN group.
  • the specifying module 620 is configured to specify a forwarding range of the multicast data of the source VPN multicast instance.
  • the specifying module 620 specifies the forwarding range of the multicast data of the source VPN multicast instance.
  • the multicast data of the specified source VPN multicast instance is The forwarding range is the private network group address range.
  • the multicast forwarding range of the specified source VPN multicast instance is the private network source group address range. .
  • the determining module 630 is configured to determine, according to the private network group address or the source group address, the multicast tunnel interface that sends the PIM protocol packet by the sending module 640.
  • the sending module 640 is configured to send the encapsulated PIM protocol packet to the multicast tunnel interface established by the establishing module 610, so that the encapsulated PIM protocol packet is forwarded on the public network and the source VPN multicast instance is encapsulated according to the PIM.
  • the protocol packet generates the public network multicast data packet of the Share-Group of the source VPN.
  • the sending module 640 encapsulates the PIM protocol packet into the encapsulated PIM protocol packet of the Share-Group according to the Share-Group corresponding to the multicast tunnel interface, and encapsulates the encapsulated PIM protocol packet through the public network multicast instance. Forwarding in the public network.
  • the source VPN multicast instance decapsulates the encapsulated PIM protocol packets forwarded by the public network to obtain PIM protocol packets.
  • the obtaining module 650 is configured to decapsulate the public network multicast data packet of the share-group of the source VPN, and obtain the multicast data from the source VPN multicast instance.
  • the source VPN multicast instance obtains the PIM protocol packet, and encapsulates the multicast data into the public network multicast data packet of the source VPN Share-Group according to the PIM protocol packet, and encapsulates the encapsulated multicast data through the public network multicast instance. Forward in the public network.
  • the obtaining module 650 receives the encapsulated multicast data, decapsulates the encapsulated multicast data, and obtains multicast data.
  • the checking module 660 is configured to check a group address or a source group of the multicast data acquired by the obtaining module 650. Whether the address is within the forwarding range of the multicast data of the specified source VPN multicast instance.
  • the checking module 660 checks whether the group address or the source group address of the multicast data acquired by the obtaining module 650 is within the forwarding range of the multicast data of the specified source VPN multicast instance. If the group address or source group address of the multicast data is within the forwarding range of the multicast data of the specified source VPN multicast instance, the multicast data is forwarded according to the receiver VPN multicast route; if the group address of the multicast data or If the source group address is not within the forwarding range of the multicast data of the specified source VPN multicast instance, the multicast data is discarded.
  • the forwarding module 670 is configured to: in the check module 660, check that the group address or the source group address of the multicast data is in the forwarding range of the multicast data of the specified source VPN multicast instance, and forward the multicast according to the receiver VPN multicast route. data.
  • the discarding module 680 is configured to discard the multicast data when the check module 660 checks that the group address of the multicast data or the source group address is not in the forwarding range of the multicast data of the specified source VPN multicast instance.
  • the multicast tunnel of the receiver VPN multicast instance to the source VPN multicast instance is established by adding the Sha re-Group address of the source VPN in the receiver VPN multicast instance, and checking Whether the group address or source group address of the received multicast data is within the forwarding range of the multicast data of the specified source VPN multicast instance, ensuring isolation between VPN multicast instances and reducing resources of the router system. Occupied, reduced network load.
  • the present invention can be implemented by means of software plus a necessary general hardware platform, and of course, can also be through hardware, but in many cases, the former is a better implementation. the way.
  • the technical solution of the present invention which is essential or contributes to the prior art, may be embodied in the form of a software product stored in a storage medium, including a plurality of instructions for making a
  • the terminal device (which may be a cell phone, a personal computer, a server, or a network device, etc.) performs the methods described in various embodiments of the present invention.

Landscapes

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

Description

一种组播虚拟私有网络的外联网组网方法、 ***和装置 本申请要求于 2008 年 12 月 31 日提交中国专利局、 申请号为 200810191759.7, 发明名称为 "一种组播虚拟私有网络的外联网组网方法、 ***和装置" 的中国专利申请的优先权， 其全部内容通过引用结合在本申请 中。 技术领域
本发明实施例涉及通信技术领域， 特别是涉及一种组播虚拟私有网络的 外联网组网方法、 ***和装置。 背景技术
IP ( Internet Protocol, 网际协议）组播是指在 IP 网络中将数据包以 尽力传送（best-effort )的形式发送到网络中的某个确定的节点子集， 该节 点子集称为组播组（腿 lticast group) 。 源主机只发送一份数据， 该份数据 中的目的地址为组播组地址， 组播组中的所有接收者都可接收到同样的数据 拷贝， 并且只有组播组内的主机可以接收该数据， 组播组外的其他主机不能 收到该数据。
VPN (Virtual Private Network, 虚拟私有网络）是依靠 ISP ( Internet Service Provider, 因特网月良务提供商）和 NSP ( Network Service Provider , 网络服务提供商）在公共网络中建立的虚拟专用通信网络， 可以将现有的 IP 网络分解成逻辑上隔离的网络。
VPN由 CE (Customer Edge, 用户网络边缘设备） 、 PE (Provider Edge, 服务提供商网络边缘设备）和 P (Provider, 服务提供商网络骨干路由器） 组成， CE直接与 SP (Service Provider, 服务提供商） 网络相连， 专属于某 ― VPN, 只为专属的 VPN服务， 仅维护一套转发机制， 可以为路由器或交换 机， 也可以为一台主机； PE与 CE直接相连， 同时接入公网和 VPN网络， 同 时为多个 VPN服务； P不与 CE直接相连。 PE和 P仅由 SP管理， CE仅由用户 管理， 除非用户把管理权委托给 SP。 一台 PE可以接入多台 CE , —台 CE也可 以连接属于相同或不同服务提供商的多台 PE。 PE上必须严格区分各个网络的 信息， 并为各个网络独立维护一套转发机制。 PE上为同一网络服务的一套软 硬件设施统称为一个实例， PE上可以同时存在多个实例， 同一实例可以分布 在多个 PE上。
组播 VPN方案需要在 SP骨干网 （核心网络或公网）中支持组播功能， 将 私网实例中的组播数据和控制报文透过公网传递到 VPN的远端站点。 PE路由 器上在 VPN实例中运行的组播实例称之为私网组播实例， PE路由器的公网部 分运行的组播实例称之为公网组播实例。 公网组播实例不需要了解私网中传 递的组播数据， 私网组播实例也不需要了解公网实例中的组播路由信息， 各 个私网组播实例之间相互隔离。
如果 VPN用户需要接收其他 VPN用户的组播数据， 可以使用组播 VPN外 联网 ext rane t组网方案。该组网方案可以是源 PE配置接收者 VPN组播实例， 并在新配置的接收者 VPN组播实例中添加接收者 VPN的共享组 Sha re-Group 地址， 建立新配置的接收者 VPN组播实例到原接收者 VPN组播实例的组播隧 道， 原接收者 VPN组播实例和新配置的接收者 VPN组播实例可以使用内联网 int rane t方式通信； 而在源 PE设备上， 新配置的接收者 VPN组播实例和源 VPN组播实例通过本地交叉方式实现 ex t rane t , 即通过同一设备上不同 VPN 组播实例之间的内部消息进行通信， 以完成 PIM ( Pro toco l Independent Mul t i ca s t , 协议无关组播协议） 文和组播数据 ^艮文的传递。 现有技术中的 组网方案也可以是接收者 PE配置源 VPN组播实例，并在新配置的源 VPN组播 实例中添加原源 VPN的 Sha re-Group地址， 建立新配置的源 VPN组播实例到 原源 VPN组播实例的组播隧道， 新配置的源 VPN组播实例和原源 VPN组播实 例可以使用 int rane t方式通信； 而在接收者 PE设备上， 新配置的源 VPN组 播实例和接收者 VPN组播实例通过本地交叉方式实现 ext rane t , 即通过同一 设备上不同 VPN组播实例之间的内部消息进行通信， 以完成 PIM协议报文和 组播数据报文的传递。
发明人在实现本发明的过程中， 发现现有技术至少存在如下问题： 现有技术中， 无论是源 PE配置接收者 VPN组播实例， 还是接收者 PE配 置源 VPN组播实例，都是使用本地私网交叉实现组播 VPN ext rane t ,远端 VPN 站点的组播流仍然使用同一 VPN的组播隧道。 如果接收者 VPN组播实例需要 从多个不同的源 VPN接收组播数据，则接收者 PE都要额外配置多个源 VPN组 播实例， 而接收者 PE可能并没有上述 VPN实例的业务， 对接收者 PE路由器 的***资源占用过大。 源 PE配置接收者 VPN组播实例存在同样的问题。
另外，如果源 VPN组播实例的组播流存在多个远端 PE的 VPN组播实例需 要接收， 由于每个接收者 VPN都要通过自身的组播隧道传递组播流， 公网会 在多个接收者 VPN的共享组 Share-Group组播分发树中封装复制， 同时对一 份组播数据转发多份流量 , 增加了网络负载。 发明内容
本发明实施例提供一种组播虚拟私有网络的外联网组网方法、 ***和装 置， 减轻了网络负载。
本发明实施例提出一种组播虚拟私有网络 VPN的外联网组网方法， 包括： 才艮据添加的源 VPN的共享组 Share-Group地址， 建立到所述源 VPN组播 实例的组播隧道， 以及与所述组播隧道相连的组播隧道接口；
向所述组播隧道接口发送封装后的协议无关组播 PIM协议报文， 在公网 中转发所述封装后的 PIM协议报文， 并使所述源 VPN组播实例根据所述封装 后的 PIM协议报文生成源 VPN的 Share-Group的公网组播数据报文；
解封装接收到的所述源 VPN的 Sha re-Group的公网组播数据报文， 获取 来自所述源 VPN组播实例的组播数据。 本发明实施例还提出一种组播 VPN的外联网组网***， 包括源 VPN和接 收者 VPN, 其中：
所述接收者 VPN, 用于根据添加的源 VPN的共享组 Share-Group地址， 建立到所述源 VPN组播实例的组播隧道， 以及与所述组播隧道相连的组播隧 道接口， 向所述组播隧道接口发送封装后的协议无关组播 PIM协议报文， 在 公网中转发所述封装后的 PIM协议报文， 并使所述源 VPN组播实例根据所述 封装后的 PIM协议报文生成源 VPN的 Share-Group的公网组播数据报文， 并 解封装接收到的所述源 VPN的 Share-Group的公网组播数据报文， 获取来自 所述源 VPN组播实例的组播数据。
本发明实施例还提出一种接收者 VPN组播实例， 包括：
建立模块， 用于才艮据添加的源 VPN的 Share-Group地址， 建立到所述源 VPN组播实例的组播隧道， 以及与所述组播隧道相连的组播隧道接口；
发送模块， 用于向所述建立模块建立的所述组播隧道接口发送封装后的 PIM协议报文， 在公网中转发所述封装后的 PIM协议报文， 并使所述源 VPN 组播实例根据所述封装后的 PIM协议 ^艮文生成源 VPN的 Share-Group的公网 组播数据报文；
获取模块， 用于解封装接收到的所述源 VPN的 Share-Group的公网组播 数据报文， 获取来自所述源 VPN组播实例的组播数据。
本发明实施例的技术方案具有以下优点， 因为在接收者 VPN组播实例中 添加源 VPN的 Share-Group地址， 建立接收者 VPN组播实例到源 VPN组播实 例的组播隧道， 从而， 减少了对路由器***资源的占用， 减轻了网络负载。 附图说明
为了更清楚地说明本发明实施例或现有技术中的技术方案， 下面将对实 施例或现有技术描述中所需要使用的附图作简单地介绍， 显而易见地， 下面 描述中的附图仅仅是本发明的一些实施例， 对于本领域普通技术人员来讲， 在不付出创造性劳动性的前提下， 还可以根据这些附图获得其他的附图。 图 1为本发明实施例中的一种组播 VPN的外联网组网方法流程图； 图 2为本发明实施例中的另一种组播 VPN的外联网组网方法流程图； 图 3为本发明实施例中的外联网组网方法的组网示意图；
图 4为本发明实施例中的又一种组播 VPN的外联网组网方法流程图； 图 5为本发明实施例中的一种接收者 VPN组播实例结构示意图； 图 6为本发明实施例中的另一种接收者 VPN组播实例结构示意图。 具体实施方式
本发明实施例不另外配置 VPN实例， 通过在接收者 VPN组播实例中添加 源 VPN的 Share-Group地址， 使接收者 VPN的 PIM协议报文可以到达远端源 VPN, 源 VPN的组播数据报文也可以到达远端接收者 VPN。
下面将结合本发明实施例中的附图， 对本发明实施例中的技术方案进行 清楚、 完整地描述， 显然， 所描述的实施例是本发明一部分实施例， 而不是 全部的实施例。 基于本发明中的实施例， 本领域普通技术人员在没有作出创 造性劳动前提下所获得的所有其他实施例， 都属于本发明保护的范围。
如图 1所示， 为本发明实施例中的一种组播 VPN的外联网组网方法流程 图， 包括以下步骤：
步骤 101 , 根据添加的源 VPN的 Sha re-Group地址， 建立到源 VPN组播 实例的组播隧道， 以及与组播隧道相连的组播隧道接口。
本发明实施例中， 提供组播数据源的 VPN实例称为源 VPN组播实例， 源 VPN组播实例所在的 PE路由器称为源 PE;需要接收组播数据的 VPN实例称为 接收者 VPN组播实例， 与源 VPN组播实例不在同一个 VPN, 接收者 VPN组播 实例所在的 PE路由器称为接收者 PE。 在源 PE侧的源 VPN组播实例中添加源 VPN 的 Sha re-Group 地址后， 在接收者 VPN 组播实例中也添加源 VPN 的 Share-Grou 地址， 建立接收者 VPN组播实例到源 VPN组播实例的组播隧道 , 以及与组播隧道相连的组播隧道接口。
接收者 VPN组播实例添加源 VPN的共享组 Share-Group地址后， 指定源 VPN组播实例的组播数据的转发范围。 当接收者 VPN组播实例和源 VPN组播 实例均运行 PIM SM ( Parse Mode , 稀疏模式） 时， 上述指定的源 VPN组播实 例的组播数据的转发范围为私网组地址范围；当接收者 VPN组播实例和源 VPN 组播实例均运行 PIM SSM ( Source Spec if ic Mul t icas t , 特定源组播） 时， 上述指定的源 VPN组播实例的组播数据的转发范围为私网源组地址范围。 本 发明实施例可以使用（ Share-Group , 私网组地址 /掩码）、 [Share-Group, (私 网源地址 /掩码，私网组地址 /掩码 )]和 [Share-Group, (离散的组地址集合 )] 等形式， 指定不同源 VPN extranet组播数据的转发范围。
步骤 102 , 向组播隧道接口发送封装后的 PIM协议报文， 在公网中转发 封装后的 PIM协议报文， 并使源 VPN组播实例根据封装后的 PIM协议报文生 成源 VPN的共享组（ Share-Group ) 的公网组播数据报文。
在接收者 VPN组播实例向远端 PE发送封装后的 PIM协议报文之前， 需要 先根据私网组地址或源组地址确定发送封装后的 PIM协议 >¾文的组播隧道接 口， 并按照组播隧道接口对应的 Share-Group, 将接收者 VPN组播实例的 PIM 协议报文封装为该 Share-Group的封装后的 PIM协议报文，通过公网组播实例 将封装后的 PIM协议报文在公网中进行转发。源 VPN组播实例对公网中转发的 封装后的 PIM协议报文进行解封装，获取接收者 VPN组播实例的 PIM协议报文， 在源 VPN组播实例获取到接收者 VPN组播实例的 PIM协议报文之后， 该源 VPN 组播实例将根据该 PIM协议报文封装该源 VPN的组播数据，并通过公网将该封 装了源 VPN组播数据的公网组播数据报文发送给接收者 VPN组播实例。
步骤 103 , 解封装接收到的源 VPN的 Share-Group的公网组播数据 4艮文， 获取来自源 VPN组播实例的组播数据。
源 VPN组播实例获取 PIM协议报文，根据 PIM协议报文将组播数据封装为 源 VPN Share-Group的公网组播数据报文， 并通过公网组播实例将封装后的组 播数据在公网中进行转发。接收者 VPN组播实例接收封装后的组播数据，对封 装后的组播数据进行解封装，获取组播数据，从而实现组播 VPN的外联网组网。
接收者 VPN组播实例获取来自源 VPN组播实例的组播数据之后， 检查组 播数据的组地址或源组地址是否在指定的源 VPN组播实例的组播数据的转发 范围内。 如果组播数据的组地址或源组地址在指定的源 VPN组播实例的组播 数据的转发范围内， 则按照接收者 VPN组播路由， 转发组播数据； 如果组播 数据的组地址或源组地址不在指定的源 VPN组播实例的组播数据的转发范围 内， 则丟弃组播数据。
本发明实施例保证了各 VPN组播实例之间的隔离， 对接收者 VPN组播实 例而言， 与本 VPN的远端站点以及其他源 VPN远端站点的组播转发均通过各 自不同的组播隧道， 各组播隧道之间没有任何连通， 各自创建组播隧道接口 用于发送组播协议报文和接收组播数据报文； 对源 VPN组播实例而言， 各接 收者 VPN 组播实例均建立到源 VPN 的组播隧道， 可见的只有源 VPN 用于 ext rane t转发的地址空间， 各 VPN组播实例其他的地址空间仍然是隔离的， 即源 VPN组播实例的 int rane t地址空间对各接收者 VPN不可见， 各接收者 VPN实例的 int rane t和其他 ex t rane t地址空间也互相不可见。
本发明实施例的技术方案具有以下优点， 因为通过在接收者 VPN组播实 例添加源 VPN的 Share-Group地址， 建立接收者 VPN组播实例到源 VPN组播 实例的组播隧道， 减少了对路由器***资源的占用， 减轻了网络负载。
如图 2所示， 为本发明实施例中的另一种组播 VPN的外联网组网方法流 程图， 本实施例中， 该组播 VPN的外联网组网方法应用在如图 3所示的组网 中， PE1为 VPN RED组播实例所在的 PE路由器， PE2为 VPN BLUE组播实例所 在的 PE路由器， CE1连接组播源， CE2连接接收者。 该组播 VPN的外联网组 网方法包括以下步骤：
步骤 201 , PE1侧的 VPN RED组播实例添加 Share-Group地址 Gl。
VPN RED组播实例为提供组播数据源的 VPN实例， PE1为 VPN RED组播实 例所在的 PE路由器。 VPN RED组播实例添加 Share-Grou 地址 G1后， 可以 与公网进行数据传输。
步骤 202, PE2侧的 VPN BLUE组播实例添加 Share-Grou 地址 Gl。
VPN BLUE组播实例为需要接收组播数据的 VPN实例， 与 VPN RED组播实 例不在同一个 VPN, PE2为 VPN BLUE组播实例所在的 PE路由器。 VPN BLUE 组播实例添加 Share-Grou 地址 G1后，指定私网组地址范围 Gr/Mr,建立 VPN BLUE组播实例到 VPN RED组播实例的组播隧道， 可以与公网进行数据传输。
本发明实施例中， CE1连接组播源， CE2连接接收者， VPN RED组播实例 和 VPN BLUE组播实例均运行 PIM SM, VPN RED的 RP ( Rendezvous Point, 汇 聚点） 配置在 CE1, CE2 直连接收者的接口使能 IGMP ( Internet Group Management Protocol , 因特网组管理协议） 。 VPN BLUE 组播实例添加 Share-Group地址 G1, 同时指定私网组地址范围 Gr/Mr。 VPN BLUE组播实例还 可以添加本 VPN Share-Group地址 G2, 用于接收本 VPN远端站点的组播数据。
步骤 203, 接收者向 CE2发送 IGMP (*, G) report报文， 请求 VPN RED组 播数据。
IGMP (*, G) report ^艮文的私网组地址为 G, 私网源地址空缺。
步骤 204, CE2向 PE2发送 PIM(*， G)加入请求。
PIM(*， G)加入请求为 PIM协议报文， 该报文的私网组地址为 G, 私网源 地址空缺。
步骤 205, PE2生成 VPN BLUE组播实例的组播路由 （ *, G )表项。
组播路由 （ * , G )表项的私网组地址为 G , 私网源地址空缺。
步骤 206, PE2根据 RP地址， 查找到上游路由器为 PE 1。
步骤 207, VPN BLUE组播实例检查组播路由 （ *, G )表项的私网组地址是 否属于指定的私网组地址范围 Gr/Mr。
如果组播路由 （*,G)表项的私网组地址属于 Gr/Mr, 则执行步骤 209; 如果组播路由 （ *, G )表项的私网组地址不属于 Gr/Mr, 则执行步骤 208。 步骤 208, VPN BLUE组播实例丟弃 PIM (*， G)加入请求。
步骤 209, VPN BLUE组播实例通过到 VPN RED组播实例的组播隧道， 封 装 PIM(*,G)加入请求。
步骤 210, 公网 G1的组播分发树发送封装后的 PIM(*， G)加入请求。
步骤 211, VPN RED组播实例从公网 G1的组播分发树解封装公网数据， 获取 PIM(*,G)加入请求。
步骤 212, VPN RED组播实例处理 PIM (*, G)加入请求，生成组播路由（*, G) 表项。
步骤 213, CE1将 VPN RED组播数据（S, G)发送到 PE1。
VPN RED组播数据的私网组地址为 G , 私网源地址为 S。
步骤 214, PE 1创建组播路由（S , G)表项。
组播路由（S, G)表项的私网组地址为 G, 私网源地址为 S。
步骤 215, VPN RED组播实例将 VPN RED组播数据（S, G)通过 VPN RED的 组播隧道封装。
步骤 216, 公网 G1的组播分发树发送封装后的 VPN RED的私网组播数据
(S, G)。
步骤 217, VPN BLUE组播实例从公网 G1组播分发树解封装公网数据， 获 取 VPN RED组播数据 (S, G)。
步骤 218, VPN BLUE组播实例检查 VPN RED组播数据（S, G)的私网组地址 是否属于指定的私网组地址范围 Gr/Mr。
如果 VPN RED 组播数据（S,G)的私网组地址属于指定的私网组地址范围 Gr/Mr, 则执行步骤 220; 如果 VPN RED组播数据（S， G)的私网组地址不属于 指定的私网组地址范围 Gr/Mr, 则执行步骤 219。
步骤 219, VPN BLUE组播实例丟弃 VPN RED组播数据（S, G)。
步骤 220, VPN BLUE组播实例创建组播路由（S , G)表项。
步骤 221 , VPN BLUE组播实例将 VPN RED组播数据（S, G)转发给 CE2。 步骤 111 , 接收者从 CE2获取 VPN RED组播数据 (S, G) 。
本发明实施例的技术方案具有以下优点， 因为通过在接收者 VPN组播实 例添加源 VPN的 Share-Group地址， 建立接收者 VPN组播实例到源 VPN组播 实例的组播隧道， 并检查接收到的组播数据的私网组地址是否属于指定的私 网组地址范围， 保证了各 VPN组播实例之间的隔离， 减少了对路由器***资 源的占用， 减轻了网络负载。
如图 4所示， 为本发明实施例中的又一种组播 VPN的外联网组网方法流 程图， 本实施例中， 该组播 VPN的外联网组网方法为应用在如图 3所示的组 网中， PE1为 VPN RED组播实例所在的 PE路由器， PE2为 VPN BLUE组播实例 所在的 PE路由器， CE1连接组播源， CE2连接接收者。 该组播 VPN的外联网 组网方法包括以下步骤：
步骤 401 , PE1侧的 VPN RED组播实例添加 Share-Group地址 Gl。
VPN RED组播实例为提供组播数据源的 VPN实例， PE1为 VPN RED组播实 例所在的 PE路由器。 VPN RED组播实例添加 Share-Grou 地址 G1后， 可以 与公网进行数据传输。
步骤 402 , PE2侧的 VPN BLUE组播实例添加 Share-Grou 地址 Gl。
VPN BLUE组播实例为需要接收组播数据的 VPN实例， 与 VPN RED组播实 例不在同一个 VPN, PE2为 VPN BLUE组播实例所在的 PE路由器。 VPN BLUE 组播实例添加 Share-Grou 地址 G1 , 指定私网 源组地址范围 (Sr/Ms r, Gr/Mgr) , 建立 VPN BLUE组播实例到 VPN RED组播实例的组播隧道， 可以与公网进行数据传输。
本发明实施例中， CE1连接组播源， CE2连接接收者， VPN RED组播实例 和 VPN BLUE组播实例均运行 PIM SSM, CE2直连接收者的接口使能 IGMP。 VPN
BLUE 组播实例添加 Share-Grou 地址 G1 , 同时指定私网源组地址范围 (Sr/Ms r, Gr/Mgr) 0 VPN BLUE组播实例还可以添加本 VPN Share-Grou 地址
G2 , 用于接收本 VPN远端站点的组播数据。 步骤 403, 接收者向 CE2发送 IGMP (S, G) report ^艮文， 请求 VPN RED组 播数据。
IGMP (S, G) report 文的私网组地址为 G, 私网源地址为 S。
步骤 404, CE2向 PE2发送 PIM(S, G)加入请求。
PIM(S, G)加入请求为 P IM协议 ^艮文， 该^艮文的私网组地址为 G , 私网源 地址为 S。
步骤 405, PE2生成 VPN BLUE组播实例的组播路由 （ S, G )表项。
组播路由 （S, G)表项的私网组地址为 G, 私网源地址为 S。
步骤 406, PE2 艮据私网源地址， 查找到上游路由器为 PE1。
步骤 407, VPN BLUE组播实例检查组播路由 （ S, G )表项的私网源组地址 是否属于指定的私网源组地址范围（Sr/Msr，Gr/Mgr)。
如果组播路由 （S，G)表项的私网源组地址属于（Sr/Msr,Gr/Mgr)， 则执 行步骤 409； 如果组播路由 （ S, G ) 表项的私网源组地址不属于
(Sr/Msr, Gr/Mgr) , 则执行步骤 408。
步骤 408, VPN BLUE组播实例丟弃 PIM (S, G)加入请求。
步骤 409, VPN BLUE组播实例通过到 VPN RED组播实例的组播隧道， 封 装 PIM(S, G)加入请求。
步骤 410, 公网 G1的组播分发树发送封装后的 PIM(S, G)加入请求。
步骤 411, VPN RED组播实例从公网 G1的组播分发树解封装公网数据， 获取 PIM (S, G)加入请求。
步骤 412, VPN RED组播实例处理 PIM (S, G)加入请求，生成组播路由（S， G) 表项。
步骤 413, CE1将 VPN RED组播数据（S, G)发送到 PE1。
VPN RED组播数据的私网组地址为 G , 私网源地址为 S。
步骤 414, VPN RED組播实例将 VPN RED组播数据（S, G)通过 VPN RED的 组播隧道封装。 步骤 415 , 公网 G1的组播分发树发送封装后的 VPN RED的私网组播数据 (S, G)。
步骤 416 , VPN BLUE组播实例从公网 G1组播分发树解封装公网数据， 获 取 VPN RED组播数据（S, G)。
步骤 417 , VPN BLUE组播实例检查 VPN RED组播数据（S, G)的私网源组地 址是否属于指定的私网源组地址范围（Sr/Ms r, Gr/Mgr)。
如果 VPN RED组播数据（S, G)的私网组地址属于指定的私网源组地址范围 (Sr/Ms r, Gr/Mgr) , 则执行步骤 419 ; 如果 VPN RED组播数据（S, G)的私网源 组地址不属于指定的私网源组地址范围（Sr/Ms r, Gr/Mgr) , 则执行步骤 418。
步骤 418 , VPN BLUE组播实例丟弃 VPN RED组播数据（S, G)。
步骤 419 , VPN BLUE组播实例将 VPN RED组播数据（S, G)转发给 CE2。 步骤 420 , 接收者从 CE2获取 VPN RED组播数据 (S, G)。
本发明实施例的技术方案具有以下优点， 因为通过在接收者 VPN组播实 例添加源 VPN的 Share-Group地址， 建立接收者 VPN组播实例到源 VPN组播 实例的组播隧道， 并检查接收到的组播数据的私网源组地址是否属于指定的 私网源组地址范围， 保证了各 VPN组播实例之间的隔离， 减少了对路由器系 统资源的占用， 减轻了网络负载。
本发明实施例还提出了一种组播 VPN的外联网组网***， 包括源 VPN和 接收者 VPN,其中：该接收者 VPN,用于根据添加的源 VPN的共享组 Share-Group 地址， 建立到该源 VPN组播实例的组播隧道， 以及与该组播隧道相连的组播 隧道接口， 向该组播隧道接口发送封装后的协议无关组播 P IM协议报文， 在 公网中转发封装后的 PIM协议报文， 并使源 VPN组播实例根据封装后的 P IM 协议报文生成源 VPN的 Share-Group的公网组播数据报文， 并解封装接收到 的该源 VPN的 Share-Group的公网组播数据报文， 获取来自该源 VPN组播实 例的组播数据。
如图 5所示，为本发明实施例中的一种接收者 VPN组播实例结构示意图， 该接收者 VPN组播实例 500 , 包括：
建立模块 510, 用于根据添加的源 VPN的 Share-Group地址， 建立到源 VPN组播实例的组播隧道， 以及与组播隧道相连的组播隧道接口。
本发明实施例中， 提供组播数据源的 VPN实例称为源 VPN组播实例， 源 VPN组播实例所在的 PE路由器称为源 PE;需要接收组播数据的 VPN实例称为 接收者 VPN组播实例， 与源 VPN组播实例不在同一个 VPN, 接收者 VPN组播 实例所在的 PE路由器称为接收者 PE。
源 PE侧的源 VPN组播实例添加源 VPN的 Share-Group地址后， 接收者 VPN组播实例中的建立模块 510添加源 VPN的 Share-Group地址， 建立接收 者 VPN组播实例到源 VPN组播实例的组播隧道， 以及与组播隧道相连的组播 隧道接口。
发送模块 520 , 用于向建立模块 510建立的组播隧道接口发送封装后的 协议无关组播 PIM协议报文， 在公网中转发封装后的 PIM协议报文， 并使源 VPN组播实例根据封装后的 PIM协议报文生成源 VPN的 Share-Group的公网 组播数据报文。
发送模块 520向远端 PE发送封装后的 PIM协议报文时，需要先根据私网 组地址或源组地址确定发送封装后的 PIM协议报文的组播隧道接口， 并按照 组播隧道接口对应的 Sha re-Group , 将接收者 VPN组播实例的 P IM协议 ^艮文 封装为该 Share-Group的封装后的 PIM协议 ^艮文， 通过公网组播实例将封装 后的 PIM协议报文在公网中进行转发。 源 VPN组播实例对公网中转发的封装 后的 PIM协议 ^艮文进行解封装， 获取接收者 VPN组播实例的 PIM协议 文， 在源 VPN组播实例获取到接收者 VPN组播实例的 PIM协议报文之后，该源 VPN 组播实例将根据该 PIM协议报文封装该源 VPN的组播数据， 并通过公网将该 封装了源 VPN组播数据的公网组播数据报文发送给接收者 VPN组播实例。
获取模块 530, 用于解封装接收到的源 VPN的 Share-Group的公网组播 数据报文， 获取来自源 VPN组播实例的组播数据。 源 VPN组播实例获取 PIM协议报文， 根据 PIM协议报文将组播数据封装 为源 VPN Share-Group的公网组播数据报文， 并通过公网组播实例将封装后 的组播数据在公网中进行转发。 获取模块 530接收封装后的组播数据， 对封 装后的组播数据进行解封装， 获取组播数据， 实现组播 VPN的外联网组网。
本发明实施例保证了各 VPN组播实例之间的隔离， 对接收者 VPN组播实 例而言， 与本 VPN的远端站点以及其他源 VPN远端站点的组播转发均通过各 自不同的组播隧道， 各组播隧道之间没有任何连通， 各自创建组播隧道接口 用于发送组播协议报文和接收组播数据报文； 对源 VPN组播实例而言， 各接 收者 VPN 组播实例均建立到源 VPN 的组播隧道， 可见的只有源 VPN 用于 ext rane t转发的地址空间， 各 VPN组播实例其他的地址空间仍然是隔离的， 即源 VPN组播实例的内部网 int rane t地址空间对各接收者 VPN不可见，各接 收者 VPN实例的 int rane t和其他 ext rane t地址空间也互相不可见。
本发明实施例的技术方案具有以下优点， 因为通过在接收者 VPN组播实 例添加源 VPN的 Share-Group地址， 建立接收者 VPN组播实例到源 VPN组播 实例的组播隧道， 减少了对路由器***资源的占用， 减轻了网络负载。
如图 6所示， 为本发明实施例中的另一种接收者 VPN组播实例结构示意 图， 该接收者 VPN组播实例 600 , 包括：
建立模块 610 , 用于根据添加的源 VPN的 Share-Group地址， 建立到源 VPN组播实例的组播隧道， 以及与组播隧道相连的组播隧道接口。
本发明实施例中， 提供组播数据源的 VPN实例称为源 VPN组播实例， 源
VPN组播实例所在的 PE路由器称为源 PE;需要接收组播数据的 VPN实例称为 接收者 VPN组播实例， 与源 VPN组播实例不在同一个 VPN, 接收者 VPN组播 实例所在的 PE路由器称为接收者 PE。
源 PE侧的源 VPN组播实例添加源 VPN的 Share-Group地址后， 接收者 VPN组播实例中的建立模块 610添加源 VPN的 Share-Group地址， 建立接收 者 VPN组播实例到源 VPN组播实例的组播隧道， 以及与组播隧道相连的组播 隧道接口。
指定模块 620 , 用于指定源 VPN组播实例的组播数据的转发范围。
指定模块 620指定源 VPN组播实例的组播数据的转发范围，当接收者 VPN 组播实例和源 VPN组播实例均运行 P IM SM时， 上述指定的源 VPN组播实例的 组播数据的转发范围为私网组地址范围； 当接收者 VPN组播实例和源 VPN组 播实例均运行 PIM SSM时， 上述指定的源 VPN组播实例的组播数据的转发范 围为私网源组地址范围。 本发明实施例可以使用 （Share-Group , 私网组地 址 /掩码） 、 [Share-Group, (私网源地址 /掩码， 私网组地址 /掩码） ]和 [Share-Group , (离散的组地址集合） ]等形式， 指定不同源 VPN extranet 组播数据的转发范围。
确定模块 630 , 用于根据私网组地址或源组地址， 确定发送模块 640发 送 PIM协议报文的组播隧道接口。
发送模块 640 , 用于向建立模块 610建立的组播隧道接口发送封装后的 PIM协议报文， 使封装后的 PIM协议报文在公网中转发并使源 VPN组播实例 根据封装后的 PIM协议报文生成源 VPN的 Share-Group的公网组播数据报文。
发送模块 640按照组播隧道接口对应的 Share-Group, 将 PIM协议报文 封装为该 Share-Group的封装后的 PIM协议 ^艮文， 通过公网组播实例将封装 后的 PIM协议报文在公网中进行转发。 源 VPN组播实例对公网中转发的封装 后的 PIM协议报文进行解封装， 获取 PIM协议报文。
获取模块 650, 用于解封装接收到的源 VPN的 Share-Group的公网组播 数据报文， 获取来自源 VPN组播实例的组播数据。
源 VPN组播实例获取 PIM协议报文， 根据 PIM协议报文将组播数据封装 为源 VPN Share-Group的公网组播数据报文， 并通过公网组播实例将封装后 的组播数据在公网中进行转发。 获取模块 650接收封装后的组播数据， 对封 装后的组播数据进行解封装， 获取组播数据。
检查模块 660 , 用于检查获取模块 650获取的组播数据的组地址或源组 地址是否在指定的源 VPN组播实例的组播数据的转发范围内。
检查模块 660检查获取模块 650获取的组播数据的组地址或源组地址是 否在指定的源 VPN组播实例的组播数据的转发范围内。 如果组播数据的组地 址或源组地址在指定的源 VPN组播实例的组播数据的转发范围内， 则按照接 收者 VPN组播路由， 转发组播数据； 如果组播数据的组地址或源组地址不在 指定的源 VPN组播实例的组播数据的转发范围内， 则丟弃组播数据。
转发模块 670 , 用于在检查模块 660检查到组播数据的组地址或源组地 址在指定的源 VPN组播实例的组播数据的转发范围内， 按照接收者 VPN组播 路由， 转发组播数据。
丟弃模块 680 , 用于在检查模块 660检查到组播数据的组地址或源组地 址不在指定的源 VPN组播实例的组播数据的转发范围内， 丟弃组播数据。
本发明实施例的技术方案具有以下优点， 因为通过在接收者 VPN组播实 例添加源 VPN的 Sha re-Group地址， 建立接收者 VPN组播实例到源 VPN组播 实例的组播隧道， 并检查接收到的组播数据的组地址或源组地址是否在指定 的源 VPN组播实例的组播数据的转发范围内， 保证了各 VPN组播实例之间的 隔离， 减少了对路由器***资源的占用， 减轻了网络负载。
通过以上的实施方式的描述， 本领域的技术人员可以清楚地了解到本发 明可借助软件加必需的通用硬件平台的方式来实现， 当然也可以通过硬件， 但很多情况下前者是更佳的实施方式。 基于这样的理解， 本发明的技术方案 本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来， 该计算机软件产品存储在一个存储介质中， 包括若干指令用以使得一台终端 设备（可以是手机， 个人计算机， 服务器， 或者网络设备等）执行本发明各 个实施例所述的方法。
以上所述仅是本发明的优选实施方式， 应当指出， 对于本技术领域的普 通技术人员来说， 在不脱离本发明原理的前提下， 还可以做出若干改进和润 饰， 这些改进和润饰也应视本发明的保护范围。

Claims

权 利 要 求 书
1、 一种组播虚拟私有网络 VPN的外联网组网方法， 其特征在于， 包括： 才艮据添加的源 VPN的共享组 Share-Group地址， 建立到所述源 VPN组播 实例的组播隧道， 以及与所述组播隧道相连的组播隧道接口；
向所述组播隧道接口发送封装后的协议无关组播 PIM协议报文， 在公网 中转发所述封装后的 PIM协议报文， 并使所述源 VPN组播实例根据所述封装 后的 PIM协议 文生成所述源 VPN的 Share-Group的公网组播数据 4艮文； 解封装接收到的所述源 VPN的 Sha re-Group的公网组播数据报文， 获取 来自所述源 VPN组播实例的组播数据。
2、 根据权利要求 1所述的方法， 其特征在于， 在所述根据添加的源 VPN 的共享组 Sha re-Group地址， 建立到所述源 VPN组播实例的组播隧道之前， 还包括：
在所述源 VPN组播实例添加所述 Share-Grou 地址； 和在接收者 VPN组 播实例添加所述 Share-Grou 地址。
3、 根据权利要求 2所述的方法， 其特征在于， 在所述接收者 VPN组播实 例添加所述 Share-Grou 地址之后， 还包括：
指定所述源 VPN组播实例的组播数据的转发范围；
在所述获取来自源 VPN组播实例的组播数据之后， 还包括：
检查所述组播数据的组地址或源组地址是否在所述指定的源 VPN组播实 例的组播数据的转发范围内；
当所述组播数据的组地址或源组地址在所述指定的源 VPN组播实例的组 播数据的转发范围内时， 按照接收者 VPN组播路由， 转发所述组播数据。
4、 根据权利要求 3所述的方法， 其特征在于， 还包括： 当所述组播数据 的组地址或源组地址不在所述指定的源 VPN组播实例的组播数据的转发范围 内时， 丟弃所述组播数据。
5、 根据权利要求 1所述的方法， 其特征在于， 所述向组播隧道接口发送 封装后的 PIM协议报文之前， 还包括：
根据私网组地址或源组地址， 确定所述发送 PIM协议 >¾文的组播隧道接 口。
6、 根据权利要求 1所述的方法， 其特征在于， 所述向组播隧道接口发送 封装后的协议无关组播 P IM协议报文， 在公网中转发所述封装后的 P IM协议 报文， 并使所述源 VPN组播实例根据所述封装后的 PIM协议报文生成源 VPN 的 Share-Group的公网组播数据 4艮文， 包括：
根据所述组播隧道接口将 PIM协议报文进行封装，生成所述封装后的 PIM 协议报文；
通过公网将所述封装后的 P IM协议报文转发给所述源 VPN组播实例， 以 使所述源 VPN组播实例对接收到的所述封装后的 PIM协议报文进行解封装， 以获取 PIM协议 文， 并根据所述 PIM协议 文封装所述源 VPN组播实例的 组播数据；
接收来自所述源 VPN组播实例的 Share-Group的公网组播数据报文， 所 述公网组播数据报文为根据所述 PIM协议报文封装组播数据生成的。
7、 一种组播 VPN的外联网组网***， 其特征在于， 包括源 VPN和接收者 VPN, 其中：
所述接收者 VPN, 用于根据添加的源 VPN的共享组 Share-Group地址， 建立到所述源 VPN组播实例的组播隧道， 以及与所述组播隧道相连的组播隧 道接口， 向所述组播隧道接口发送封装后的协议无关组播 PIM协议报文， 在 公网中转发所述封装后的 PIM协议报文， 并使所述源 VPN组播实例根据所述 封装后的 PIM协议报文生成源 VPN的 Share-Group的公网组播数据报文， 并 解封装接收到的所述源 VPN的 Share-Group的公网组播数据报文， 获取来自 所述源 VPN组播实例的组播数据。
8、 根据权利要求 7所述的组播 VPN的外联网组网***， 其特征在于， 所 述接收者 VPN, 还用于： 指定源 VPN组播实例的组播数据的转发范围， 当接 收者 VPN组播实例获取来自源 VPN组播实例的组播数据之后， 检查组播数据 的组地址或源组地址是否在指定的源 VPN 组播实例的组播数据的转发范围 内， 当所述组播数据的组地址或源组地址在所述指定的源 VPN组播实例的组 播数据的转发范围内时， 按照接收者 VPN组播路由， 转发所述组播数据。
9、 根据权利要求 8所述的组播 VPN的外联网组网***， 其特征在于， 所 述接收者 VPN , 还用于： 当所述组播数据的组地址或源组地址不在所述指定 的源 VPN组播实例的组播数据的转发范围内时， 丟弃所述组播数据。
10、 根据权利要求 7所述的组播 VPN的外联网组网***， 其特征在于， 所述接收者 VPN, 还用于： 在向组播隧道接口发送封装后的 PIM协议报文之 前， 根据私网组地址或源组地址， 确定所述发送 PIM协议 ^艮文的组播隧道接 口。
11、 一种接收者 VPN组播实例， 其特征在于， 包括：
建立模块， 用于才艮据添加的源 VPN的 Share-Group地址， 建立到所述源 VPN组播实例的组播隧道， 以及与所述组播隧道相连的组播隧道接口；
发送模块， 用于向所述建立模块建立的所述组播隧道接口发送封装后的
PIM协议报文， 在公网中转发所述封装后的 PIM协议报文， 并使所述源 VPN 组播实例根据所述封装后的 PIM协议 ^艮文生成源 VPN的 Sha re-Group的公网 组播数据报文；
获取模块， 用于解封装接收到的所述源 VPN的 Share-Group的公网组播 数据报文， 获取来自所述源 VPN组播实例的组播数据。
12、根据权利要求 11所述的接收者 VPN组播实例，其特征在于，还包括： 指定模块， 用于指定所述源 VPN组播实例的组播数据的转发范围； 检查模块， 用于检查获取模块获取的所述组播数据的组地址或源组地址 是否在所述指定的源 VPN组播实例的组播数据的转发范围内；
转发模块， 用于当所述检查模块检查到所述组播数据的组地址或源组地 址在所述指定的源 VPN组播实例的组播数据的转发范围内时，按照接收者 VPN 组播路由， 转发所述组播数据。
1 3、根据权利要求 12所述的接收者 VPN组播实例，其特征在于，还包括： 丟弃模块， 用于当所述检查模块检查到所述组播数据的组地址或源组地 址不在所述指定的源 VPN组播实例的组播数据的转发范围内时， 丟弃所述组 播数据。
14、根据权利要求 11所述的接收者 VPN组播实例，其特征在于，还包括： 确定模块， 用于根据私网组地址或源组地址， 确定所述发送模块发送所 述 PIM协议报文的组播隧道接口。
PCT/CN2009/076182 2008-12-31 2009-12-29 一种组播虚拟私有网络的外联网组网方法、***和装置 WO2010075771A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP09836058.9A EP2378720B1 (en) 2008-12-31 2009-12-29 Extranet networking method, system and device for multicast virtual private network
US13/174,063 US9031069B2 (en) 2008-12-31 2011-06-30 Method, system, and apparatus for extranet networking of multicast virtual private network

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200810191759.7 2008-12-31
CN200810191759.7A CN101459606B (zh) 2008-12-31 2008-12-31 一种组播虚拟私有网络的外联网组网方法、***和装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US13/174,063 Continuation US9031069B2 (en) 2008-12-31 2011-06-30 Method, system, and apparatus for extranet networking of multicast virtual private network

Publications (1)

Publication Number Publication Date
WO2010075771A1 true WO2010075771A1 (zh) 2010-07-08

Family

ID=40770243

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2009/076182 WO2010075771A1 (zh) 2008-12-31 2009-12-29 一种组播虚拟私有网络的外联网组网方法、***和装置

Country Status (4)

Country Link
US (1) US9031069B2 (zh)
EP (1) EP2378720B1 (zh)
CN (1) CN101459606B (zh)
WO (1) WO2010075771A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130259042A1 (en) * 2011-02-22 2013-10-03 Hangzhou H3C Technologies Co., Ltd. Multicast packet transmission

Families Citing this family (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP4421517B2 (ja) * 2005-06-07 2010-02-24 株式会社東芝 情報処理サーバ、遠隔操作システムおよび遠隔操作方法
CN101459606B (zh) 2008-12-31 2011-04-20 华为技术有限公司 一种组播虚拟私有网络的外联网组网方法、***和装置
CN102045180B (zh) * 2009-10-16 2014-02-05 中兴通讯股份有限公司 一种实现虚拟专用网间的组播方法和***
CN102137024B (zh) * 2011-04-19 2013-11-20 福建星网锐捷网络有限公司 报文处理方法、出口路由设备及边界路由设备
CN102299848B (zh) * 2011-08-23 2014-07-02 福建星网锐捷网络有限公司 一种组播报文传输方法及运营商边缘设备
US8885643B2 (en) * 2011-11-04 2014-11-11 Futurewei Technologies, Inc. Method for multicast flow routing selection
CN103326940B (zh) * 2012-03-22 2017-04-26 华为技术有限公司 在网络中转发报文的方法和运营商边缘设备
CN103152280B (zh) * 2013-03-12 2016-05-25 福建星网锐捷网络有限公司 组播流的传输方法、装置和入口边缘设备
US9432280B2 (en) * 2013-10-30 2016-08-30 Alcatel Lucent Network device configured to generate empty route for limiting number of withdrawal messages
US9503279B2 (en) 2014-04-08 2016-11-22 Alcatel Lucent Network device with service and client routing elements configured to support any-source multicast extranets
US10833880B2 (en) 2014-08-07 2020-11-10 Nokia Technologies Oy Controlled switching of multicast traffic between selective and inclusive routes based on number of multicast receivers
US9473315B2 (en) 2014-08-07 2016-10-18 Alcatel Lucent Network device configured to track multicast receivers
WO2016071738A1 (en) * 2014-11-06 2016-05-12 Pismo Labs Technology Ltd. Methods and systems for establishing vpn connections at a vpn management server
CN105743797B (zh) * 2016-04-05 2019-03-29 深圳市风云实业有限公司 基于接口绑定的组播vpn隧道建立方法
WO2018193285A1 (en) * 2017-04-17 2018-10-25 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for enabling a scalable multicast virtual private network service across a multicast label distribution protocol network using in-band signaling
CN109495406A (zh) * 2017-09-13 2019-03-19 中兴通讯股份有限公司 组播虚拟专用网络vpn流量的转发方法及转发设备
CN110636033B (zh) * 2018-06-25 2021-11-26 中国电信股份有限公司 组播数据传输方法、***、组播隧道终结点和存储介质
CN114221913A (zh) * 2019-02-21 2022-03-22 华为技术有限公司 一种发送和获取断言报文的方法和网络节点
CN112532563B (zh) * 2019-09-17 2022-04-05 华为技术有限公司 报文的发送方法和装置
CN111740893B (zh) * 2020-06-30 2022-02-11 成都卫士通信息产业股份有限公司 软件定义vpn的实现方法、装置、***、介质和设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060209831A1 (en) * 2005-03-21 2006-09-21 Cisco Technology, Inc. VPN services using address translation over an IPv6 network
CN101159659A (zh) * 2007-11-23 2008-04-09 清华大学 在软线式隧道中运用单一静态双向共享树进行组播的方法
CN101217458A (zh) * 2007-12-28 2008-07-09 华为技术有限公司 一种虚拟私有网上资源分配的方法及路由器和***
CN101459606A (zh) * 2008-12-31 2009-06-17 华为技术有限公司 一种组播虚拟私有网络的外联网组网方法、***和装置

Family Cites Families (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6339595B1 (en) * 1997-12-23 2002-01-15 Cisco Technology, Inc. Peer-model support for virtual private networks with potentially overlapping addresses
US7830787B1 (en) * 2001-09-25 2010-11-09 Cisco Technology, Inc. Flooding control for multicast distribution tunnel
US7574526B2 (en) * 2003-07-31 2009-08-11 International Business Machines Corporation Multicast group management in infiniband
CN100379226C (zh) * 2004-12-14 2008-04-02 华为技术有限公司 一种虚拟路由器方式的虚拟专用网络的组播方法
US7720994B2 (en) * 2005-01-13 2010-05-18 Cisco Technology, Inc. Method for suppression of multicast join/prune messages from extranet receivers
US7839850B2 (en) * 2006-01-30 2010-11-23 Juniper Networks, Inc. Forming equal cost multipath multicast distribution structures
US7626984B2 (en) * 2006-10-25 2009-12-01 At&T Corp. Method and apparatus for providing congruent multicast and unicast routing
US7856014B2 (en) * 2006-10-27 2010-12-21 International Business Machines Corporation High capacity multicast forwarding
CN100531040C (zh) * 2007-02-07 2009-08-19 杭州华三通信技术有限公司 实现组播虚拟专用网绑定的方法及设备
US8166205B2 (en) * 2007-07-31 2012-04-24 Cisco Technology, Inc. Overlay transport virtualization
US7873020B2 (en) * 2007-10-01 2011-01-18 Cisco Technology, Inc. CAPWAP/LWAPP multicast flood control for roaming clients

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060209831A1 (en) * 2005-03-21 2006-09-21 Cisco Technology, Inc. VPN services using address translation over an IPv6 network
CN101159659A (zh) * 2007-11-23 2008-04-09 清华大学 在软线式隧道中运用单一静态双向共享树进行组播的方法
CN101217458A (zh) * 2007-12-28 2008-07-09 华为技术有限公司 一种虚拟私有网上资源分配的方法及路由器和***
CN101459606A (zh) * 2008-12-31 2009-06-17 华为技术有限公司 一种组播虚拟私有网络的外联网组网方法、***和装置

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130259042A1 (en) * 2011-02-22 2013-10-03 Hangzhou H3C Technologies Co., Ltd. Multicast packet transmission

Also Published As

Publication number Publication date
US20110255536A1 (en) 2011-10-20
EP2378720B1 (en) 2014-07-30
CN101459606B (zh) 2011-04-20
EP2378720A4 (en) 2013-01-23
EP2378720A1 (en) 2011-10-19
CN101459606A (zh) 2009-06-17
US9031069B2 (en) 2015-05-12

Similar Documents

Publication Publication Date Title
WO2010075771A1 (zh) 一种组播虚拟私有网络的外联网组网方法、***和装置
US8369246B2 (en) Method and apparatus for sending and receiving multicast packets on a multicast tree
AU697935B2 (en) Method for establishing restricted broadcast groups in a switched network
CN102075439B (zh) 一种组播报文转发方法和路由设备
WO2006063513A1 (fr) Procede de multidiffusion dans un reseau prive virtuel utilisant un routeur virtuel
CN102137000B (zh) 一种建立切换组播分发树的方法、装置及***
WO2012088982A1 (zh) 路由信息发布方法、设备及虚拟专用网***
US20090225660A1 (en) Communication device and operation management method
JP2003032287A (ja) ネットワーク間接続方法、その装置およびその装置を用いたシステム
WO2008017270A1 (fr) Procédé, dispositif et système ethernet supportant un acheminement multidiffusion à source spécifique
WO2013139159A1 (zh) 在网络中转发报文的方法和运营商边缘设备
WO2018014767A1 (zh) 一种信息确定方法、装置及存储介质
WO2009082905A1 (fr) Procédé système et dispositif commutateur permettant l'établissement dynamique de réseau local virtuel de multidiffusion
WO2007054006A1 (fr) Station de base de système d’accès sans fil large bande et système pour réaliser un service de diffusion de groupe
WO2018171396A1 (zh) 一种数据传输方法、装置及***
WO2007079632A1 (fr) PROCÉDÉ DE DISPOSITION DE MULTIDIFFUSION, PROCÉDÉ DE MULTIDIFFUSION ET APPAREIL DANS LES ÎLOTS IPv6
CN102045250B (zh) Vpls中组播报文的转发方法和服务提供商边缘设备
WO2013139234A1 (zh) 一种组播传输方法、装置和网络***
WO2007048296A1 (fr) Méthode et système pour obtenir la cohérence de l’état d’un circuit virtuel
WO2014169856A1 (zh) 一种组播通信方法和汇聚交换机
WO2009076839A1 (zh) 供应商边缘设备之间传送报文的方法、***及设备
KR20040033866A (ko) 가상 랜을 이용한 아이피 멀티캐스트 서비스방법
WO2010069174A1 (zh) 一种数据的传输方法、***及装置
WO2014079208A1 (zh) Trill网络的通信方法及装置、***
WO2008154796A1 (fr) Procédé et équipement permettant de commander la transmission de paquets de données de multidiffusion dans la station de base et la passerelle du système wimax

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2009836058

Country of ref document: EP