+

WO2018010519A1 - Procédé et appareil pour établir un tunnel de diffusion groupée - Google Patents

Procédé et appareil pour établir un tunnel de diffusion groupée Download PDF

Info

Publication number
WO2018010519A1
WO2018010519A1 PCT/CN2017/088633 CN2017088633W WO2018010519A1 WO 2018010519 A1 WO2018010519 A1 WO 2018010519A1 CN 2017088633 W CN2017088633 W CN 2017088633W WO 2018010519 A1 WO2018010519 A1 WO 2018010519A1
Authority
WO
WIPO (PCT)
Prior art keywords
label
identifier
forwarding device
forwarding
path
Prior art date
Application number
PCT/CN2017/088633
Other languages
English (en)
Chinese (zh)
Inventor
谢经荣
刘毅松
张军林
王东
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2018010519A1 publication Critical patent/WO2018010519A1/fr

Links

Images

Classifications

    • 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/4633—Interconnection of networks using encapsulation techniques, e.g. tunneling
    • 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]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/80—Actions related to the user profile or the type of traffic
    • H04L47/806—Broadcast or multicast traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/82—Miscellaneous aspects
    • H04L47/825—Involving tunnels, e.g. MPLS

Definitions

  • the present application relates to the field of communications, and in particular, to a method and apparatus for establishing a multicast tunnel.
  • a multicast virtual private network can implement multicast forwarding by using an aggregate tunnel.
  • Multiple MVPNs can use the same aggregation tunnel to implement multicast forwarding. This requires configuring corresponding labels for different VPNs on the forwarding devices included in the aggregation tunnel to implement multiple aggregation tunnels for multiple VPNs.
  • the label space on the forwarding device included in the aggregation tunnel needs to store N context labels in addition to the global label space.
  • N context labels
  • the forwarding device uses linear forwarding, it needs to generate hundreds of millions of forwarding entries according to the labels contained in the label space. This makes it impossible for the forwarding device to use a linear table to save and find labels.
  • the operation of finding the forwarding entry matching the label in the packet is heavy, and the cost on the forwarding plane is relatively large. .
  • the embodiment of the present application provides a method and an apparatus for establishing a multicast tunnel, which helps reduce the cost of the forwarding plane and improve the forwarding efficiency.
  • the first aspect provides a method for establishing a multicast tunnel, where the method includes:
  • the first forwarding device sends a request message to the second forwarding device, where the request message includes the information of the label block and the identifier of the path, the information of the label block is used to indicate the size of the label block, and the identifier of the path is used to identify the identifier a tunnel corresponding to the virtual private network VPN between the first forwarding device and the second forwarding device, where the first forwarding device is an upstream device of the second forwarding device;
  • the first forwarding device obtains a forwarding entry corresponding to the tunnel according to the identifier of the first label and the path.
  • the first forwarding device may obtain a forwarding entry that can implement a linear search according to a start label of the label block sent by the second forwarding device, such as the first label, and the identifier of the path.
  • a forwarding entry that can implement a linear search according to a start label of the label block sent by the second forwarding device, such as the first label, and the identifier of the path.
  • the method provided in this embodiment of the present application is applicable to an MVPN scenario.
  • the tunnel is a P2MP tunnel, or the tunnel is a P2P tunnel. If the tunnel is a P2MP tunnel, the first forwarding device is a PE device, the second forwarding device is a P device, or the first forwarding device and the second forwarding device are both PE devices. If the tunnel is a P2P tunnel, the first forwarding device and the second forwarding device are both PE devices.
  • the request message may be a path path message, and a session field of the path message may carry information of the label block.
  • the response message may be a resource reservation protocol RSVP message, and the session field of the RSVP message may carry the identifier of the first label and the path.
  • the method further includes: the first forwarding device determines a tunnel corresponding to the VPN, and the first forwarding device obtains information about the label block according to the tunnel corresponding to the VPN, The information of the tag block is determined by the number of VPNs corresponding to the tunnel.
  • the first forwarding device obtains, according to the identifier of the first label and the path, a forwarding entry corresponding to the tunnel, where the first forwarding device obtains a group according to the identifier of the path.
  • the identifier of the multicast the identifier of the multicast is used to identify the multicast forwarding information corresponding to the path, and the first forwarding device obtains the identifier of the outbound interface according to the identifier of the path, where the outbound interface is the An interface that communicates with the second forwarding device on the first forwarding device; the first forwarding device obtains the forwarding entry according to the first label, the identifier of the multicast, and the identifier of the outbound interface,
  • the forwarding entry includes a second label, an identifier of the multicast, and an identifier of the outbound interface, where the second label is a label obtained according to the first label and an offset, and the offset is The value corresponds to the VPN.
  • the value of the second tag is determined by the value of the offset
  • the value of the offset is determined by the VPN. Determine, for example, the correspondence between the values of the VPN and the offset can be established.
  • the value of the second tag corresponds to the VPN.
  • the method further includes: the first forwarding device receives the first packet from the VPN, and obtains an identifier of the VPN; the first forwarding device according to the forwarding entry, the first The packet and the identifier of the VPN are obtained, and the second packet is sent to the second forwarding device, where the second packet is a multicast packet that is sent to the second forwarding device by using the tunnel.
  • the first forwarding device may obtain the identifier of the VPN according to the interface that receives the first packet.
  • the first packet may carry information related to the VPN, and the first forwarding device may obtain the identifier of the VPN according to the information related to the VPN in the first packet.
  • the first forwarding device obtains the second packet according to the forwarding entry, the first packet, and the identifier of the VPN, and sends the second packet to the second forwarding device, where: the first The forwarding device obtains the value of the offset corresponding to the VPN according to the correspondence and the identifier of the VPN, where the correspondence includes the identifier of the VPN and the value of the offset; the first forwarding device is configured according to Transmitting the entry and the value of the offset to obtain an identifier of the third label and the outbound interface, where the third label is a label obtained according to the first label and the value of the offset,
  • the egress interface is configured to communicate with the second forwarding device, and the first forwarding device sends the second packet to the second forwarding device according to the identifier of the egress interface, where the second packet includes The first message and the third tag are described.
  • the third label is a label corresponding to the VPN obtained according to the value of the offset.
  • the third tag may be the same as the second tag.
  • a method for establishing a multicast tunnel includes:
  • the second forwarding device receives the request message sent by the first forwarding device, where the second forwarding device is the downstream device of the first forwarding device, and the request message includes the information of the label block and the identifier of the path, where the label block
  • the information is used to indicate the size of the label block, and the identifier of the path is used to identify a tunnel corresponding to the virtual private network VPN;
  • the second forwarding device Determining, by the second forwarding device, the first label according to the information of the label block, where the first label is a start label of the label block determined according to the information of the label block;
  • the second forwarding device sends a response message to the first forwarding device, where the response message includes the identifier of the first label and the path.
  • the method further includes: obtaining, by the second forwarding device, an entry corresponding to the tunnel according to the identifier of the first label and the path, where the entry includes a second label,
  • the second tag is a tag obtained according to the first tag and the offset, and the value of the offset corresponds to a VPN.
  • the second forwarding device obtains an entry corresponding to the tunnel according to the identifier of the first label and the path, where the second forwarding device obtains the multicast according to the identifier of the path.
  • the identifier of the multicast is used to identify the multicast forwarding information corresponding to the path, and the second forwarding device obtains the entry according to the first label and the identifier of the multicast.
  • the entry includes the second tag and the identifier of the multicast.
  • the entry further includes information of the label block.
  • the forwarding entry obtained by the first forwarding device is used to guide the forwarding entry
  • the entry obtained by the second forwarding device is used to locate the forwarding entry
  • a first forwarding device where the first forwarding device includes:
  • a first sending unit configured to send a request message to the second forwarding device, where the request message includes the information of the label block and the identifier of the path, where the information of the label block is used to indicate the size of the label block, and the identifier of the path is used by And identifying, by the first forwarding device, the tunnel corresponding to the virtual private network VPN, the first forwarding device is an upstream device of the second forwarding device;
  • a first receiving unit configured to receive a response message sent by the second forwarding device, where the response message includes a first label and an identifier of the path, where the first label is determined according to information of the label block The starting label of the label block;
  • a first obtaining unit configured to obtain, according to the identifier of the first label and the path, a forwarding entry corresponding to the tunnel.
  • the first forwarding device further includes:
  • a determining unit configured to determine a tunnel corresponding to the VPN
  • a second obtaining unit configured to obtain information about the label block according to the tunnel corresponding to the VPN, where information of the label block is determined by a number of VPNs corresponding to the tunnel.
  • the first obtaining unit is specifically configured to:
  • an identifier of the multicast where the identifier of the multicast is used to identify multicast forwarding information corresponding to the path;
  • the forwarding entry Obtaining, according to the first label, the identifier of the multicast, and the identifier of the outbound interface, the forwarding entry, where the forwarding entry includes a second label, the identifier of the multicast, and the outbound interface
  • the second tag is a tag obtained according to the first tag and an offset, and the value of the offset corresponds to a VPN.
  • the first forwarding device further includes:
  • a second receiving unit configured to receive a first packet from the VPN, and obtain an identifier of the VPN
  • a third obtaining unit configured to obtain a second packet according to the forwarding entry, the first packet, and the identifier of the VPN, where the second packet is sent to the second by using the tunnel Forwarding multicast packets of the device;
  • the second sending unit is configured to send the second packet to the second forwarding device.
  • the third obtaining unit is specifically configured to:
  • the second sending unit is configured to send the second packet to the second forwarding device according to the identifier of the outbound interface, where the second packet includes the first packet and the third packet label.
  • a second forwarding device where the second forwarding device includes:
  • a receiving unit configured to receive a request message sent by the first forwarding device, where the second forwarding device is a downstream device of the first forwarding device, where the request message includes information of a label block and an identifier of a path, where the label block The information is used to indicate the size of the label block, and the identifier of the path is used to identify a tunnel corresponding to the virtual private network VPN;
  • An obtaining unit configured to obtain, according to the information of the label block, a first label, where the first label is a starting label of the label block determined according to information of the label block;
  • a sending unit configured to send a response message to the first forwarding device, where the response message includes the identifier of the first label and the path.
  • the second forwarding device further includes:
  • a second obtaining unit configured to obtain, according to the identifier of the first label and the path, an entry corresponding to the tunnel, where the entry includes a second label, and the second label is according to the first The label obtained from the tag and the offset, the value of the offset corresponding to the VPN.
  • the second obtaining unit is specifically configured to:
  • an identifier of the multicast where the identifier of the multicast is used to identify multicast forwarding information corresponding to the path;
  • the entry further includes information of the label block.
  • the second forwarding device provided by the fourth aspect may also adopt the method provided by the first aspect or any possible implementation manner of the first aspect, to obtain a forwarding entry, that is, the second forwarding device may forward to another A device that requests a tag that matches the information of the tag block.
  • the second forwarding device may be the same device as the first forwarding device provided by the third aspect, or may be different from the first forwarding device provided by the third aspect.
  • a first forwarding device comprising: a processor, a memory, a communication interface, and a communication bus, wherein the processor, the memory, and the communication interface pass through the communication bus Connected, the memory is for storing a program; the processor reads the executable instructions included in the program from the memory, and performs the method provided by the first aspect or any one of the implementation manners of the first aspect.
  • a second forwarding device comprising: a processor, a memory, a communication interface, and a communication bus, wherein the processor, the memory, and the communication interface pass through the communication bus Connection
  • the memory is used to store a program; the processor reads the executable instructions included in the program from the memory, and performs the method provided by any one of the second aspect or the second aspect.
  • FIG. 1 is a schematic diagram of a network scenario.
  • FIG. 2(a) is a schematic diagram of a network scenario according to an embodiment of the present application.
  • FIG. 2(b) is a flowchart of a method for establishing a multicast tunnel according to an embodiment of the present application.
  • FIG. 3(a) is a schematic diagram of another network scenario provided by an embodiment of the present application.
  • FIG. 3(b) is a flowchart of a method for establishing a multicast tunnel according to an embodiment of the present application.
  • FIG. 4 is a schematic structural diagram of a first forwarding device according to an embodiment of the present disclosure.
  • FIG. 5 is a schematic structural diagram of a second forwarding device according to an embodiment of the present disclosure.
  • FIG. 6 is a schematic structural diagram of a first forwarding device according to an embodiment of the present disclosure.
  • FIG. 7 is a schematic structural diagram of a second forwarding device according to an embodiment of the present disclosure.
  • site 1, site3, and site5 belong to a virtual private network (VPN) 1, and site2, site4, and site6 belong to VPN 2.
  • Site1 and site2 communicate with PE1.
  • PE1 can communicate with PE2 and PE3 through P.
  • PE2 communicates with site3 and site4.
  • PE4 communicates with site5 and site6.
  • a point-to-multipoint (P2MP) forwarding path can be formed between PE1, PE2, and PE3.
  • VPN1 and VPN2 can share the forwarding path of P2MP between PE1, PE2, and PE3.
  • Two mutually associated label configuration tables are configured on PE1, P, PE2, and PE3.
  • One of the two associated label configuration tables includes a mapping between a tunnel label and a VPN label
  • another label configuration table includes a correspondence between the VPN label and the outbound interface.
  • the PE1 may send a P2MP label to the P according to the pre-configured P2MP forwarding path, where the P2MP label is a tunnel label corresponding to the forwarding path of the P2MP.
  • P can forward the P2MP label from PE1 to PE2 and PE3 according to the pre-configured P2MP forwarding path.
  • PE1 After receiving the first packet from site1 of VPN1, PE1 determines the P2MP label. Based on the P2MP and the two interrelated label configuration tables, the PE1 obtains the VPN1 label and the outbound interface on PE1. The PE1 tunnels the first packet to obtain a second packet. The second packet includes the first packet, a P2MP label, and a VPN1 label. PE1 sends the second packet to P through the outbound interface on PE1. After receiving the second packet, the P obtains the outbound interface on the VPNn label and the P according to the configured two associated label configuration tables and the P2MP labels included in the second packet. P obtains a third packet according to the VPNn label and the second packet. The third packet includes the VPNn label, the P2MP label, and the first packet.
  • the number of outbound interfaces on the P obtained by P is N, and P copies the third packet to obtain N third packets.
  • the P sends the Nth third packet through the N outgoing interfaces, and the outbound interface on each P is used to send the third packet.
  • the PE2 determines an outbound interface for communicating with the site3 of the VPN1 according to the P2MP label and the VPNn label.
  • the PE2 can send the first packet included in the third packet to the site 4 through the outbound interface.
  • the method for the first packet to be sent by the PE3 to the site 5 of the VPN1 is the same as the method for the PE2 to send the first packet to the site 3 of the VPN1, and details are not described herein.
  • the first forwarding device sends a request message to the second forwarding device, where the request message includes the information of the label block and the identifier of the path, where the information of the label block is used to indicate the size of the label block, and the identifier of the path a tunnel corresponding to the virtual private network VPN between the first forwarding device and the second forwarding device, where the first forwarding device is an upstream device of the second forwarding device; and the first forwarding device receives a response message sent by the second forwarding device, where the response message includes a first label and an identifier of the path, where the first label is a start label of the label block determined according to information of the label block; The first forwarding device obtains a forwarding entry corresponding to the tunnel according to the identifier of the first label and the path.
  • the method provided by the embodiment of the present application does not need to store N+1 label spaces on each forwarding device, and can implement linear search without increasing
  • FIG. 2(a) is a schematic diagram of a network scenario according to an embodiment of the present application.
  • PE1 establishes a P2MP tunnel with PE2 and PE3 through P.
  • Site1, site3, and site5 belong to VPN1, and site2, site4, and site6 belong to VPN2.
  • Site1 and site2 communicate with PE1.
  • PE2 communicates with site3 and site4.
  • PE3 communicates with site5 and site6.
  • VPN1 and VPN2 can share P2MP tunnels between PE1, PE2, and PE3.
  • FIG. 2(b) is a flowchart of a method for establishing a multicast tunnel according to an embodiment of the present application. The method for establishing a multicast tunnel provided by the embodiment of the present application is described below with reference to FIG. 2(a) and FIG. 2(b).
  • the PE1 sends a first request message to the P.
  • the first request message includes information of a label block and an identifier of a path.
  • the information of the tag block is used to indicate the size of the tag block.
  • the identifier of the path is used to identify a P2MP tunnel.
  • the P2MP tunnel is a tunnel between PE1, PE2, and PE3.
  • the P2MP tunnel is a tunnel shared by VPN1 and VPN2.
  • PE1 is the upstream device of P and P is the downstream device of PE1.
  • PE1 may obtain information about the label block according to the number of VPNs to which the site with which it communicates. As shown in Figure 2(a), site1 and site2 belong to VPN1 and VPN2, respectively. According to VPN1 and VPN2, PE1 obtains a tag block size of 2. The PE1 can also obtain the identifier of the path according to the VPN1 and the VPN2, that is, the VPN2 and the VPN2 share the P2MP tunnel corresponding to the identifier of the path.
  • the PE1 may obtain the first request message according to the information of the label block and the identifier of the path.
  • the first request message is used to allocate a label corresponding to the P2MP tunnel to the P request.
  • the first request message may be an extended path message.
  • the extended path message may be extended to a session attribute (session_attribute) field in a label request (label_request) included in the path message in the RFC 3209, where the session_attribute field carries information of the label block.
  • the PE1 can obtain the outgoing interface of the communication with the P1 on the PE1 according to the Constraint Shortest Path First (CSPF) or the traffic engineering database (TEDB), that is, the identifier of the first outgoing interface.
  • CSPF Constraint Shortest Path First
  • TDB traffic engineering database
  • the PE1 may send the first request message to the P through the first outbound interface.
  • the first tag is a start tag of the tag block determined by the P according to the information of the tag block.
  • P may select a label block corresponding to the information of the label block from its configured global label space, and obtain a start label of the label block, such as LB1 in FIG. 2(a), and LB1 is P.
  • a label corresponding to the information of the label block The starting tag of the block.
  • P sends a first response message to PE1.
  • P may obtain a first response message according to the identifier of the first label and the path.
  • the first response message includes the first tag and an identifier of the path.
  • the first response message may be a resource reservation protocol message (RSVP message), and the RSVP message may carry the identifier of the first label and the path.
  • RSVP message resource reservation protocol message
  • the P may obtain the first entry according to the identifier of the first label and the path.
  • P may obtain one or more forwarding entries used to guide forwarding according to the first entry.
  • the P obtains the first entry according to the identifier of the first label and the path, and the P obtains a multicast identifier according to the identifier of the path, where the identifier of the multicast is used to identify the identifier.
  • a multicast forwarding information corresponding to the path P obtaining, according to the first label, a second label, where the second label is a label obtained according to the first label and an offset, the offset The value corresponds to the VPN;
  • the P obtains the first entry according to the second label and the identifier of the multicast, where the first entry includes the second label and the identifier of the multicast.
  • the identifier of the multicast that is obtained by the P according to the identifier of the path belongs to the optional content.
  • the identifier of the multicast in the first entry is replaced by the identifier of the path.
  • P may generate a second entry on the control plane, and then generate the first entry in the forwarding plane according to the second entry.
  • P may generate a second entry on the control plane according to the identifier of the first label and the path, where the second entry includes the identifier of the first label and the path.
  • the second entry further includes information about the label block, such as blocksize in FIG. 2(a).
  • the second entry can be expressed as:
  • InLabelBase ⁇ assigned by P> represents the first label allocated by P, that is, LB1 in FIG. 2(a). Session indicates the identity of the path.
  • P the first label allocated by P
  • Session indicates the identity of the path.
  • P may generate a first entry on the forwarding plane according to the second entry.
  • the first entry can be expressed as:
  • InLabelBase ⁇ assigned by P> represents the first label allocated by P, that is, LB1 in FIG. 2(a). Offset represents the offset. InLabelBase ⁇ assigned by P>+offset represents the second tag.
  • the MID indicates the identifier of the multicast, and the MID corresponds to the Session.
  • the PE1 obtains the first forwarding entry according to the first response message.
  • the PE1 obtains the first forwarding entry according to the first response message, and the PE1 obtains a multicast identifier according to the identifier of the path, where the identifier of the multicast is used to identify the path corresponding to the path.
  • the multicast forwarding information is obtained by the PE1 according to the identifier of the path, and the first outbound interface is an interface that communicates with the P1 on the PE1; the PE1 is based on the first label and the multicast And identifying, by the identifier of the first outbound interface, the first forwarding entry, where the first forwarding entry includes the second label, the identifier of the multicast, and an identifier of the first outbound interface.
  • the identifier of the multicast that is obtained by the PE1 according to the identifier of the path belongs to the optional content.
  • the identifier of the multicast in the first forwarding entry is replaced by the identifier of the path.
  • the PE1 may generate a second forwarding entry on the control plane, and then generate the first forwarding entry on the forwarding plane according to the second forwarding entry.
  • the PE1 may generate a second forwarding entry on the control plane according to the first label and the identifier of the path included in the first response message, where the second forwarding entry includes the first label, The identifier of the first outgoing interface and the identifier of the path.
  • PE1 can obtain the identifier of the first outgoing interface by using 201.
  • the second forwarding entry may be expressed as:
  • the Session represents the identifier of the path.
  • OutLabelBase ⁇ assigned by P> indicates the first label assigned by P, that is, LB1 in FIG. 2(a).
  • OutInterface ⁇ to P> indicates the identifier of the first outgoing interface.
  • PE1 may generate a first forwarding entry on the forwarding plane according to the second forwarding entry.
  • the first forwarding entry may be expressed as:
  • the MID indicates the identifier of the multicast, and the MID corresponds to the Session.
  • OutLabelBase ⁇ assigned by P> indicates the first label assigned by P, that is, LB1 in FIG. 2(a). Offset represents the offset.
  • OutLabelBase ⁇ assigned by P>+offset represents the second tag.
  • OutInterface ⁇ to P> indicates the identifier of the first outgoing interface.
  • the second request message includes information of the tag block and an identifier of the path.
  • the information of the label block included in the second request message is the same as the information of the label block included in the first request message, such as blocksize in FIG. 2(a).
  • the identifier of the path included in the second request message is the same as the identifier of the path included in the first request message.
  • P may obtain the second request message according to the information of the label block and the identifier of the path.
  • the second request message is used to request the PE2 to allocate a label corresponding to the P2MP tunnel.
  • the second request message may be an extended path message.
  • the extended path message may be extended to a session_attribute field in a label_request included in the path message in the RFC 3209, where the session_attribute field carries information of the label block.
  • P can obtain an outbound interface on P that can communicate with PE2 according to CSPF or TEDB, that is, an identifier of the second outgoing interface.
  • the P may send the second request message to the PE2 by using the second outbound interface.
  • PE2 allocates a third label.
  • the third label is a starting label of the label block determined by the PE2 according to the information of the label block.
  • the PE2 can select a label block corresponding to the information of the label block from the configured global label space, and obtain a start label of the label block, as shown in FIG. 2(a), LB2, and LB2 is a PE2 and a label.
  • the global label space configured on PE2 is different from the global label space configured on P2.
  • the PE2 sends a second response message to the P.
  • PE2 may obtain a second response message according to the identifier of the third label and the path.
  • the second response message includes the third tag and an identifier of the path.
  • the second response message may be an RSVP message, and the RSVP message is further configured to carry the identifier of the third label and the path.
  • PE2 obtains the third entry.
  • the PE2 may obtain the third entry according to the identifier of the third label and the path.
  • the third entry includes a fourth tag and the identifier of the multicast.
  • the fourth tag is a tag obtained according to the third tag and the offset, and the offset corresponds to a VPN.
  • the PE2 obtains the third entry according to the identifier of the third label and the path, and the PE2 obtains the identifier of the multicast according to the identifier of the path, where the identifier of the multicast is used to identify the identifier.
  • the multicast forwarding information corresponding to the path; the PE2 obtains the fourth label according to the third label and the offset; and the PE2 obtains the first label according to the fourth label and the identifier of the multicast
  • the third entry includes the fourth tag and the identifier of the multicast.
  • the identifier of the multicast that is obtained by the PE2 according to the identifier of the path belongs to the optional content.
  • the identifier of the multicast in the third entry is replaced by the identifier of the path.
  • PE2 may generate a fourth entry in the control plane, and generate the third entry in the forwarding plane according to the fourth entry.
  • the PE2 may generate a fourth entry on the control plane according to the identifier of the third label and the path, where the fourth entry includes the identifier of the third label and the path.
  • the fourth entry can be expressed as:
  • the InLabelBase ⁇ assigned by PE2> indicates the third label allocated by the PE2, that is, LB2 in FIG. 2(a). Session indicates the identity of the path.
  • the foregoing is only one representation of the fourth item, and the specific embodiment of the present application is not limited.
  • PE2 may generate a third entry on the forwarding plane according to the fourth entry.
  • the third entry can be expressed as:
  • the InLabelBase ⁇ assigned by PE2> indicates the third label allocated by the PE2, that is, LB2 in FIG. 2(a). Offset represents the offset. InLabelBase ⁇ assigned by PE2>+offset represents the fourth tag.
  • the MID indicates the identifier of the multicast, and the MID corresponds to the Session.
  • the P obtains a third forwarding entry according to the second response message.
  • the P obtains the third forwarding entry according to the second response message, and the P obtains the identifier of the multicast according to the identifier of the path, and obtains the second outgoing interface according to the identifier of the path.
  • the third forwarding entry is obtained according to the third label, the identifier of the multicast, and the identifier of the second outbound interface, where the third forwarding entry includes a fourth label, the group The identifier of the broadcast and the identifier of the second outgoing interface.
  • the identifier of the multicast that is obtained by the P according to the identifier of the path belongs to the optional content.
  • the identifier of the multicast in the third forwarding entry is replaced by the identifier of the path.
  • the P may generate a fourth forwarding entry on the control plane, and generate the third forwarding entry on the forwarding plane according to the fourth forwarding entry.
  • the P may generate a fourth forwarding entry on the control plane according to the third label included in the second response message and the identifier of the path, where the fourth forwarding entry includes the third label, The identifier of the second outgoing interface and the identifier of the path.
  • the P may obtain the identifier of the second outbound interface by 206.
  • the fourth forwarding entry may be expressed as:
  • the Session represents the identifier of the path.
  • OutLabelBase ⁇ assigned by PE2> indicates the third label allocated by PE2, that is, LB2 in FIG. 2(a).
  • OutInterface ⁇ to PE2> indicates the identifier of the second outgoing interface.
  • P may generate a third forwarding entry on the forwarding plane according to the fourth forwarding entry.
  • the third forwarding The entry can be expressed as:
  • the MID indicates the identifier of the multicast, and the MID corresponds to the Session.
  • OutLabelBase ⁇ assigned by PE2> indicates the third label allocated by PE2, that is, LB2 in FIG. 2(a). Offset represents the offset.
  • OutLabelBase ⁇ assigned by PE2>+offset represents the fourth tag.
  • OutInterface ⁇ to PE2> indicates the identifier of the second outgoing interface.
  • P sends a third request message to PE3.
  • the method of obtaining the third request message by P is the same as the method of obtaining the second request message by P in 206.
  • the third request message includes information of the tag block and an identifier of the path.
  • the third request message is used to request the PE3 to allocate a label corresponding to the P2MP tunnel.
  • P can obtain the outbound interface of communication with PE3 on P, that is, the identifier of the third interface, according to CSPF or TEDB. P may send the third request message to PE3 through the third interface.
  • PE3 assigns a fifth label.
  • the fifth tag may be LB3 in FIG. 2(a).
  • the global label space configured on PE3 is different from the global label space configured on PE.
  • the global label space configured on PE3 is different from the global label space configured on PE2.
  • the PE3 sends a third response message to the P.
  • the method for the PE3 to obtain the third response message is the same as the method for the PE2 to obtain the second response message in 208, and details are not described herein again.
  • the third response message includes the fifth tag and an identifier of the path.
  • PE3 obtains the fifth entry.
  • the fifth entry includes a sixth label and an identifier of the multicast.
  • the sixth tag is a tag obtained according to the fifth tag and the offset.
  • the method of obtaining the fifth entry by PE3 is the same as the method of obtaining the third entry by PE2 in 209.
  • the identifier of the multicast in the fifth entry may be replaced by an identifier of the path.
  • the PE3 may generate a sixth entry in the control plane, and generate the fifth entry in the forwarding plane according to the sixth entry.
  • the PE3 may generate a sixth entry on the control plane according to the fifth label and the identifier of the path, where the sixth entry includes the fifth label and the identifier of the path.
  • the sixth entry can be expressed as:
  • the InLabelBase ⁇ assigned by PE3> indicates the fifth label allocated by the PE3, that is, LB3 in FIG. 2(a). Session indicates the identity of the path.
  • the foregoing is only one representation of the sixth item, and the specific embodiment of the present application is not limited.
  • PE3 may generate a fifth entry on the forwarding plane according to the sixth entry.
  • the fifth entry can be expressed as:
  • the InLabelBase ⁇ assigned by PE3> indicates the fifth label allocated by the PE3, that is, LB3 in FIG. 2(a). Offset represents the offset. InLabelBase ⁇ assigned by PE3>+offset represents the sixth tag.
  • the MID indicates the identifier of the multicast, and the MID corresponds to the Session.
  • the P obtains a fifth forwarding entry according to the third response message.
  • the fifth forwarding entry includes the sixth label, the identifier of the multicast, and an identifier of the third outgoing interface.
  • the method of obtaining the fifth forwarding entry by P is the same as the method of obtaining the third forwarding entry by P in 210.
  • the identifier of the multicast in the fifth forwarding entry may be replaced by an identifier of the path.
  • the P may generate a sixth forwarding entry on the control plane, and generate the fifth forwarding entry on the forwarding plane according to the sixth forwarding entry.
  • the P may generate the sixth forwarding entry on the control plane according to the fifth label and the identifier of the path included in the third response message, where the sixth forwarding entry includes the fifth The label, the identifier of the third outbound interface, and the identifier of the path.
  • P may obtain the identifier of the third outbound interface by 211.
  • the sixth forwarding entry may be expressed as:
  • the Session represents the identifier of the path.
  • OutLabelBase ⁇ assigned by PE3> indicates the fifth label assigned by PE3, that is, LB3 in FIG. 2(a).
  • OutInterface ⁇ to PE3> indicates the identifier of the third outgoing interface.
  • P may generate the fifth forwarding entry on the forwarding plane according to the sixth forwarding entry.
  • the fifth forwarding entry may be expressed as:
  • the MID indicates the identifier of the multicast, and the MID corresponds to the Session.
  • OutLabelBase ⁇ assigned by PE3> indicates the fifth label assigned by PE3, that is, LB3 in FIG. 2(a). Offset represents the offset.
  • OutLabelBase ⁇ assigned by PE3>+offset represents the sixth tag.
  • OutInterface ⁇ to PE3> indicates the identifier of the third outgoing interface.
  • 204 in Embodiment 1 may be performed after 202, such as 204 between 202 and 203, or 204 after 203.
  • 205 may be performed after 203, such as 205 may be performed between 203 and 204, or 205 and 204 may be performed simultaneously, or 205 may be performed after 204.
  • 206 may be performed after 201, such as 206 may be performed between 201 and 202, or 206 may be performed between 202 and 203, or 206 may be performed between 203 and 204, or 206 may be performed after 204.
  • 209 may be performed after 207, such as 209 may be performed between 207 and 208, or 209 may be performed after 208.
  • 210 may be performed after 208, such as 210 may be performed between 208 and 209, or 210 may be performed concurrently with 209.
  • 211 may be performed after 201, such as 211 may be performed concurrently with 206, or 211 may be performed prior to 206.
  • 214 may be performed after 212, such as 214 may be performed between 212 and 213, or 214 may be performed after 213.
  • 215 may be performed after 213, such as 215 may be performed between 213 and 214, or 215 may be performed concurrently with 214.
  • the device included in the P2MP tunnel can forward the packet by using the corresponding entry in FIG. 2(b).
  • the forwarding flow of the message will be described below with reference to FIG. 2(a) and FIG. 2(b).
  • PE1 receives the first packet from site1.
  • the PE1 may determine, according to the port that receives the first packet, that the first packet is from VPN1, that is, site1 belongs to VPN1.
  • the correspondence between the VPN and the offset is stored on the PE1, and the PE1 can obtain the value of the offset corresponding to the VPN1 according to the corresponding relationship, for example, the number of the offset corresponding to the VPN1.
  • the value is 1.
  • PE1 determines that the multicast identifier is the MID. Based on the MID, PE1 obtains the first forwarding entry.
  • the value of the second label in the first forwarding entry is the sum of the values of LB1 and offset, that is, LB1+1, where LB1 is the first label allocated by P, and 1 is the value of offset.
  • the PE1 obtains the second packet according to the values of the first packet and the second label.
  • the second packet includes a value of the first packet and the second label.
  • the PE1 sends the second packet to the P by using the identifier of the first outbound interface.
  • P receives the second message from PE1.
  • the P determines that the first label is LB1 according to the value of the second label included in the second packet, such as LB1+1, P, and determines that the value of the offset is 1.
  • LB1 P can find the first entry that matches LB1, and obtain the multicast identifier as MID.
  • the P obtains two forwarding entries according to the MID, which are a third forwarding entry and a fifth forwarding entry, respectively. After determining that there are two forwarding entries, the P needs to copy the first packet included in the received second packet, that is, obtain two first packets.
  • the value of the fourth label in the third forwarding entry obtained by P is the sum of the value of the third label and the offset, that is, LB2+1, where LB2 is the third label allocated by PE2.
  • the third packet includes values of the first packet and the fourth label.
  • the P sends the third packet to the PE2 by using the identifier of the second egress interface included in the third forwarding entry.
  • the value of the sixth label in the fifth forwarding entry obtained by P is the sum of the value of the fifth label and the offset, that is, LB3+1, where LB3 is the fifth label allocated by PE3.
  • the P obtains the fourth packet according to the value of the second packet and the sixth label.
  • the fourth packet includes values of the first packet and the sixth label.
  • the P sends the fourth packet to the PE3 by using the identifier of the third outbound interface that is included in the fifth forwarding entry.
  • PE2 receives the third message from P.
  • the PE2 determines that the value of the offset is 1 according to the value of the fourth label in the third packet.
  • the PE2 obtains the first packet from the third packet.
  • the PE2 determines that the first packet corresponds to VPN1 according to the value of the offset.
  • the PE2 sends the first packet to the site 3 belonging to the VPN1 through the interface that communicates with the site3.
  • PE3 receives the fourth message from P.
  • the PE3 determines that the value of the offset is 1 according to the value of the sixth label in the fourth packet.
  • the PE3 obtains the first packet from the fourth packet.
  • the PE3 determines that the first packet corresponds to VPN1 according to the value of the offset.
  • the PE3 sends the first packet to the site 5 that belongs to VPN1 through the interface that communicates with the site 5.
  • Site 2 of VPN2 sends a fifth packet to PE1.
  • the method for the PE1 to send the fifth packet to the site 4 connected to the PE2 through the P is the same as the method for the PE1 to send the first packet to the site 3 connected to the PE2 through the P.
  • the method of sending the fifth packet to the site 6 connected to the PE3 through the P1 is the same as the method of transmitting the first packet to the site 5 connected to the PE3 through the P1.
  • the traffic forwarding method of VPN2 will not be described here.
  • each offset corresponds to one VPN
  • each VPN corresponds to one P2MP tunnel
  • each P2MP tunnel corresponds to one MID.
  • the P2MP tunnel can be a logical tunnel.
  • the PE1 as the first forwarding device can transmit the blocksize to the P as the second forwarding device, and obtain the LB1 from the P as the second forwarding device.
  • the PE1 does not need to store N+1 label spaces.
  • Only the LB1 and the offset corresponding to the VPN can be used to forward packets. This helps reduce the cost on the forwarding plane and implement linear lookup.
  • the P as the first forwarding device can send the blocksize to the PE2 as the second forwarding device, and obtain the LB2 from the PE2 as the second forwarding device.
  • the P does not need to store N+1 label spaces. Only the LB2 and the offset corresponding to the VPN can be used to forward packets, which helps reduce the cost on the forwarding plane and implement linear lookup.
  • FIG. 3(a) is a schematic diagram of another network scenario provided by an embodiment of the present application.
  • PE1 Establish a P2P tunnel with PE2, PE3, and PE4.
  • Site1, site6, and site8 belong to VPN1.
  • Site5 belongs to VPN2.
  • Site7 and site9 belong to VPN3.
  • Site1, site2, and site3 communicate with PE1.
  • PE2 communicates with site4 and site5.
  • PE3 communicates with site6 and site7.
  • PE4 communicates with site8 and site9.
  • VPN1 and VPN2 can share P2P tunnels between PE1 and PE2.
  • VPN1 and VPN3 can share the P2P tunnel between PE1 and PE3, and can also share the P2P tunnel between PE1 and PE4.
  • FIG. 3(b) is a flowchart of a method for establishing a multicast tunnel according to an embodiment of the present application. The method for establishing a multicast tunnel provided by the embodiment of the present application is described below with reference to FIG. 3(a) and FIG. 3(b).
  • PE1 sends a first request message to PE2.
  • the first request message includes information of a label block and an identifier of the first path.
  • the information of the tag block is used to indicate the size of the tag block.
  • the identifier of the first path is used to identify a first P2P tunnel, and the first P2P tunnel is a P2P tunnel between PE1 and PE2.
  • PE1 is the upstream device of PE2, and PE2 is the downstream device of PE1.
  • PE1 may obtain the information of the label block according to the number of VPNs to which the site with which it communicates. As shown in FIG. 3(a), PE1 can determine the size of the label block to be 3 according to the number of VPNs.
  • the PE1 may obtain the first request message according to the information of the label block and the identifier of the first path.
  • the first request message is used to request the PE2 to allocate a label corresponding to the first P2MP tunnel.
  • the first request message may be an extended path message.
  • the extended path message may be extended to a session_attribute field in a label_request included in the path message in the RFC 3209, where the session_attribute field carries information of the label block.
  • PE1 can obtain the outgoing interface of PE1 and PE2 according to CSPF or TEDB, that is, the identifier of the first outgoing interface.
  • the PE1 may send the first request message to the PE2 by using the first outbound interface.
  • PE2 allocates a first label.
  • the first label is a starting label of the label block determined by the PE2 according to the information of the label block.
  • the PE2 can select a label block corresponding to the information of the label block from the configured global label space, and obtain a start label of the label block, as shown in FIG. 3(a), LB1, and LB1 is a PE2 and a label.
  • the start tag of the tag block corresponding to the information of the tag block.
  • the PE2 sends a first response message to the PE1.
  • the PE2 may obtain the first response message according to the identifier of the first label and the first path.
  • the first response message includes an identifier of the first tag and the first path.
  • the first response message may be an RSVP message, and the RSVP message may carry the identifier of the first label and the first path.
  • PE2 obtains the first entry.
  • the PE2 can obtain the first entry according to the identifier of the first label and the first path.
  • the PE2 obtains the first entry according to the identifier of the first label and the first path, and the PE2 obtains the first identifier according to the identifier of the first path, where the first identifier is used to identify the a multicast forwarding information corresponding to the first path;
  • the PE2 obtains a second label according to the first label, where the second label is a label obtained according to the first label and an offset, the offset
  • the value corresponds to the VPN;
  • the PE2 obtains the first entry according to the second label and the first identifier, and the first entry includes the second label and the first identifier.
  • the PE2 obtains that the first identifier belongs to the optional content according to the identifier of the first path, and the first identifier in the first entry may be replaced by the identifier of the first path.
  • the PE2 may generate a second entry in the control plane, and generate the first entry in the forwarding plane according to the second entry.
  • the PE2 may generate a second entry on the control plane according to the identifier of the first label and the first path.
  • the second entry includes the first tag and an identifier of the first path.
  • the second entry can be expressed as:
  • the InLabelBase ⁇ assigned by PE2> indicates the first label allocated by the PE2, that is, LB1 in FIG. 3(a).
  • Session 1 represents the identifier of the first path.
  • PE2 may generate a first entry on the forwarding plane according to the second entry.
  • the first entry can be expressed as:
  • the InLabelBase ⁇ assigned by PE2> indicates the first label allocated by the PE2, that is, LB1 in FIG. 3(a). Offset represents the offset. InLabelBase ⁇ assigned by PE2>+offset represents the second tag. ID1 represents the first identifier, and ID1 corresponds to Session1. The above is only one manifestation of the first entry, and the specific embodiment of the present application is not limited.
  • the PE1 obtains the first forwarding entry according to the first response message.
  • the PE1 obtains the first forwarding entry according to the first response message, and the PE1 obtains the first identifier according to the identifier of the first path, and the PE1 obtains the identifier according to the identifier of the first path.
  • the first forwarding entry is obtained by the PE1 according to the first label, the first identifier, and the identifier of the first outgoing interface, where the first forwarding entry includes the first a second label, the first identifier, and an identifier of the first outgoing interface.
  • the PE1 obtains that the first identifier belongs to the optional content according to the identifier of the first path, and the first identifier in the first forwarding entry may be replaced by the identifier of the first path.
  • the PE1 may generate a second forwarding entry on the control plane, and then generate the first forwarding entry on the forwarding plane according to the second forwarding entry.
  • the PE1 may generate a second forwarding entry on the control plane according to the identifier of the first label and the first path that is included in the first response message, where the second forwarding entry includes the first a label, an identifier of the first outbound interface, and an identifier of the first path.
  • PE1 can obtain the identifier of the first outgoing interface by using 301.
  • the second forwarding entry may be expressed as:
  • Session1 represents the identifier of the first path.
  • OutLabelBase ⁇ assigned by PE2> indicates the first label assigned by PE2, that is, LB1 in FIG. 3(a).
  • OutInterface ⁇ to PE2> indicates the identifier of the first outgoing interface.
  • PE1 may generate a first forwarding entry on the forwarding plane according to the second forwarding entry.
  • the first forwarding entry may be expressed as:
  • ID1 represents the first identifier, and ID1 corresponds to Session1.
  • OutLabelBase ⁇ assigned by PE2> indicates the first label assigned by PE2, that is, LB1 in FIG. 3(a). Offset represents the offset.
  • OutLabelBase ⁇ assigned by PE2>+offset represents the second tag.
  • OutInterface ⁇ to PE2> indicates the identifier of the first outgoing interface.
  • the PE1 sends a second request message to the PE3.
  • the second request message includes information of the label block and an identifier of the second path.
  • the second The information of the tag block may be blocksize in FIG. 3(a).
  • the identifier of the second path is used to identify a second P2P tunnel, and the second P2P tunnel is a P2P tunnel between PE1 and PE3.
  • the PE1 may obtain the second request message according to the information of the label block and the identifier of the second path.
  • the second request message is used to request the PE3 to allocate a label corresponding to the second P2P tunnel.
  • the second request message may be an extended path message.
  • the extended path message may be extended to a session_attribute field in a label_request included in the path message in the RFC 3209, where the session_attribute field carries information of the label block.
  • PE1 can obtain the outbound interface that communicates with PE3 on PE1 according to CSPF or TEDB, that is, the identifier of the second interface.
  • the PE1 may send the second request message to the PE3 by using the second interface.
  • PE3 assigns a third label.
  • the third label is a starting label of the label block determined by the PE3 according to the information of the label block.
  • the PE3 may select a label block corresponding to the information of the label block from the configured global label space, and obtain a start label of the label block, as shown in FIG. 3(a), LB2, and LB2 is a PE3.
  • the global label space configured on PE3 is different from the global label space configured on PE2.
  • the PE3 sends a second response message to the PE1.
  • the PE3 may obtain a second response message according to the identifier of the third label and the second path.
  • the second response message includes an identifier of the third tag and the second path.
  • the second response message may be an RSVP message, and the RSVP message may carry the identifier of the third label and the second path.
  • PE3 obtains the third entry.
  • the PE3 may obtain the third entry according to the identifier of the third label and the second path.
  • the third entry includes a fourth tag and a second identity.
  • the fourth tag is a tag obtained according to the third tag and the offset, and the offset corresponds to a VPN.
  • the second identifier is used to identify multicast forwarding information corresponding to the identifier of the second path.
  • the PE3 obtains the third entry according to the identifier of the third label and the second path, and the PE3 obtains the second identifier according to the identifier of the second path; Obtaining the fourth label according to the third label and the offset; the third entry is obtained by the PE3 according to the fourth label and the second identifier, and the third entry includes the fourth label And the second identifier.
  • the PE3 obtains the second identifier as an optional content according to the identifier of the second path, and the second identifier in the third entry may be replaced by the identifier of the second path.
  • the PE3 may generate a fourth entry in the control plane, and generate the third entry in the forwarding plane according to the fourth entry.
  • the PE3 may generate a fourth entry on the control plane according to the identifier of the third label and the second path, where the fourth entry includes the identifier of the third label and the second path.
  • the fourth entry can be expressed as:
  • the InLabelBase ⁇ assigned by PE3> indicates the third label allocated by the PE3, that is, LB2 in FIG. 3(a).
  • Session 2 represents the identifier of the second path.
  • PE3 may generate a third entry on the forwarding plane according to the fourth entry.
  • the third entry can be expressed as:
  • the InLabelBase ⁇ assigned by PE3> indicates the third label allocated by the PE3, that is, LB2 in FIG. 3(a). Offset represents the offset. InLabelBase ⁇ assigned by PE3>+offset represents the fourth tag. ID2 represents the second identifier, and ID2 corresponds to Session2.
  • the foregoing is only one representation of the third item, and the specific embodiment of the present application is not limited.
  • the PE1 obtains a third forwarding entry according to the second response message.
  • the PE1 obtains the third forwarding entry according to the second response message, the PE1 obtains the second identifier according to the identifier of the second path, and the PE1 obtains the identifier according to the identifier of the second path.
  • the third forwarding entry is obtained according to the third label, the second identifier, and the identifier of the second outbound interface, where the third forwarding entry includes the first The identifier of the four labels, the second identifier, and the second outbound interface.
  • the PE1 obtains the second identifier as an optional content according to the identifier of the second path, and the second identifier in the third forwarding entry may be replaced by the identifier of the second path.
  • the PE1 may generate a fourth forwarding entry on the control plane, and generate the third forwarding entry on the forwarding plane according to the fourth forwarding entry.
  • the PE1 may generate a fourth forwarding entry on the control plane according to the identifier of the third label and the second path included in the second response message, where the fourth forwarding entry includes the third a label, an identifier of the second outbound interface, and an identifier of the second path.
  • PE1 may obtain the identifier of the second outbound interface by using 306.
  • the fourth forwarding entry may be expressed as:
  • Session 2 represents the identifier of the second path.
  • OutLabelBase ⁇ assigned by PE3> indicates the third label allocated by PE3, that is, LB2 in FIG. 3(a).
  • OutInterface ⁇ to PE3> indicates the identifier of the second outgoing interface.
  • PE1 may generate a third forwarding entry on the forwarding plane according to the fourth forwarding entry.
  • the third forwarding entry may be expressed as:
  • ID2 represents the second identifier, and ID2 corresponds to Session2.
  • OutLabelBase ⁇ assigned by PE3> indicates the third label allocated by PE3, that is, LB2 in FIG. 3(a). Offset represents the offset.
  • OutLabelBase ⁇ assigned by PE3>+offset represents the fourth tag.
  • OutInterface ⁇ to PE3> indicates the identifier of the second outgoing interface. The foregoing is only one representation of the third forwarding entry, and the specific embodiment of the present application is not limited.
  • the PE1 sends a third request message to the PE4.
  • the method for the PE1 to obtain the third request message is the same as the method for the PE1 to obtain the second request message.
  • the third request message includes information of the tag block and an identifier of the third path.
  • the identifier of the third path is used to identify a third P2P tunnel.
  • the third P2P tunnel is a P2P tunnel between PE1 and PE3.
  • the third request message is used to request the PE4 to allocate a label corresponding to the third P2P tunnel.
  • PE1 can obtain the outbound interface of PE1 and PE4 according to CSPF or TEDB, that is, the identifier of the third interface.
  • the PE1 may send the third request message to the PE4 through the third interface.
  • PE4 assigns a fifth label.
  • the fifth The tag can be LB3 in Figure 3(a).
  • the global label space configured on PE4 is different from the global label space configured on PE2.
  • the global label space configured on PE4 is different from the global label space configured on PE3.
  • the PE4 sends a third response message to the PE1.
  • the method for the PE4 to obtain the third response message is the same as the method for the PE3 to obtain the second response message in 308, and details are not described herein again.
  • the third response message includes an identifier of the fifth tag and the third path.
  • PE4 obtains the fifth entry.
  • the fifth entry includes a sixth tag and a third identifier.
  • the sixth tag is a tag obtained according to the fifth tag and the offset.
  • the method in which PE4 obtains the fifth entry is the same as the method in which 309 PE3 obtains the third entry.
  • the third identifier is used to identify multicast forwarding information corresponding to the third path.
  • the third identifier in the fifth entry may be replaced by the identifier of the third path.
  • the PE4 may generate a sixth entry in the control plane, and generate the fifth entry in the forwarding plane according to the sixth entry.
  • the PE4 may generate a sixth entry on the control plane according to the identifier of the fifth label and the third path, where the sixth entry includes the identifier of the fifth label and the third path.
  • the sixth entry can be expressed as:
  • the InLabelBase ⁇ assigned by PE4> indicates the fifth label allocated by the PE4, that is, LB3 in FIG. 3(a). Session 3 represents the identity of the third path.
  • the foregoing is only one representation of the sixth item, and the specific embodiment of the present application is not limited.
  • PE4 may generate a fifth entry on the forwarding plane according to the sixth entry.
  • the fifth entry can be expressed as:
  • the InLabelBase ⁇ assigned by PE4> indicates the fifth label allocated by the PE4, that is, LB3 in FIG. 3(a). Offset represents the offset. InLabelBase ⁇ assigned by PE4>+offset represents the sixth tag. ID3 represents the third identifier, and ID3 corresponds to Session3.
  • the foregoing is only one representation of the fifth item, and the specific embodiment of the present application is not limited.
  • the PE1 obtains a fifth forwarding entry according to the third response message.
  • the fifth forwarding entry includes an identifier of the sixth label, the third identifier, and the third outbound interface, where the sixth label is a label obtained according to the fifth label and the offset.
  • the identifier of the third outbound interface is used to identify the interface on PE1 that communicates with PE4.
  • the method for the PE1 to obtain the fifth forwarding entry is the same as the method for the PE1 to obtain the third forwarding entry in 310.
  • the third identifier in the fifth forwarding entry may be replaced by the identifier of the third path.
  • the PE1 may generate a sixth forwarding entry on the control plane, and generate the fifth forwarding entry on the forwarding plane according to the sixth forwarding entry.
  • the PE1 may generate the sixth forwarding entry on the control plane according to the fifth label and the identifier of the third path that are included in the third response message, where the sixth forwarding entry includes the a fifth label, an identifier of the third outbound interface, and an identifier of the third path.
  • PE1 can obtain the identifier of the third outbound interface by using 311.
  • the sixth forwarding entry may be expressed as:
  • Session 3 represents the identifier of the path.
  • OutLabelBase ⁇ assigned by PE4> indicates the fifth label assigned by PE4, that is, LB3 in FIG. 3(a).
  • OutInterface ⁇ to PE4> indicates the identifier of the third outgoing interface.
  • PE1 may generate the fifth forwarding entry on the forwarding plane according to the sixth forwarding entry.
  • the fifth forwarding entry may be expressed as:
  • ID3 represents the third identifier, and ID3 corresponds to Session3.
  • OutLabelBase ⁇ assigned by PE4> indicates the fifth label assigned by PE4, that is, LB3 in FIG. 3(a). Offset represents the offset.
  • OutLabelBase ⁇ assigned by PE4>+offset represents the sixth tag.
  • OutInterface ⁇ to PE4> indicates the identifier of the third outgoing interface. The foregoing is only one representation of the fifth forwarding entry, and the specific embodiment of the present application is not limited.
  • 301, 306, and 311 in the second embodiment can be executed at the same time, or 301, 306, and 311 can be executed in any order, which is not limited in this embodiment.
  • 304 may be performed after 302, 305 may be performed after 303, 304 and 305 may be performed simultaneously, or 304 may be performed later than 305.
  • 309 may be performed after 307, 310 may be performed after 308, 309 and 310 may be performed simultaneously, or 309 may be performed later than 310.
  • 314 may be performed after 312, 315 may be performed after 313, 314 and 315 may be performed simultaneously, or 314 may be performed later than 315.
  • each node forms a corresponding entry or forwarding entry on the forwarding plane according to the method provided in the second embodiment.
  • the forwarding entries formed on the forwarding plane of PE1 are as follows:
  • ID11 indicates the value of ID1 when the offset is 1
  • ID12 indicates the value of ID1 when the offset is 2.
  • ID21 indicates the value of ID2 when the offset is 1
  • ID23 indicates the value of ID2 when the offset is 3.
  • ID31 indicates the value of ID3 when the offset is 1, and ID33 indicates the value of ID3 when the offset is 3.
  • the entries formed on the forwarding plane of PE2 are as follows:
  • ID11 indicates the value of ID1 when the offset is 1
  • ID12 indicates the value of ID1 when the offset is 2.
  • the entries formed on the forwarding plane of PE3 are as follows:
  • ID21 indicates the value of ID2 when the offset is 1
  • ID23 indicates the value of ID2 when the offset is 3.
  • the entries formed on the forwarding plane of PE4 are as follows:
  • ID31 indicates the value of ID3 when the offset is 1
  • ID33 indicates the value of ID3 when the offset is 3.
  • PE1, PE2, PE3, or PE4 can use the corresponding entry in Figure 3 (b) to implement packet forwarding.
  • the forwarding process of the packet will be described below with reference to FIG. 3(a).
  • PE1 receives the first packet from site1.
  • the PE1 may determine, according to the port that receives the first packet, that the first packet is from VPN1, that is, site1 belongs to VPN1.
  • the correspondence between the VPN and the offset is stored on the PE1.
  • the PE1 can obtain the value of the offset corresponding to the VPN1 according to the corresponding relationship. For example, the value of the offset corresponding to the VPN1 is 1.
  • PE1 determines that there are VPN1 sites on PE2, PE3, and PE4, and PE1 obtains ID11, ID21, and ID31.
  • the PE1 obtains the first forwarding entry, the third forwarding entry, and the fifth forwarding entry according to the ID11, the ID21, and the ID31, that is, the forwarding entry formed by the offset 1 formed on the PE1.
  • the value of the second label in the first forwarding entry is LB1+1, where LB1 is the first label assigned by PE2, and 1 is the value of offset.
  • the value of the fourth label in the third forwarding entry is LB2+1, where LB2 is the third label allocated by PE3.
  • the value of the sixth label in the fifth forwarding entry is LB3+1, where LB3 is the fifth label allocated by PE3.
  • the PE1 obtains the second packet according to the values of the first packet and the second label.
  • the second packet includes a value of the first packet and the second label.
  • the PE1 sends the second packet to the PE2 by using the identifier of the first outgoing interface.
  • the PE1 obtains the third packet according to the values of the first packet and the fourth label.
  • the third packet includes values of the first packet and the fourth label.
  • the PE1 sends the third packet to the PE3 by using the identifier of the second outbound interface.
  • the PE1 obtains the fourth packet according to the values of the first packet and the sixth label.
  • the fourth packet includes values of the first packet and the sixth label.
  • the PE1 sends the fourth packet to the PE4 by using the identifier of the third outbound interface.
  • PE2 receives the second packet from PE1.
  • the PE2 determines that the value of the offset is 1 according to the value of the second label in the second packet.
  • the PE2 obtains the first packet from the second packet.
  • the PE2 determines that the first packet corresponds to VPN1 according to the value of the offset.
  • the PE2 sends the first packet to the site 4 belonging to the VPN1 through the interface that communicates with the site 4.
  • the method for the PE3 to send the first packet to the site 6 is the same as the method for the PE2 to send the first packet to the site 4.
  • the method for the PE4 to send the first packet to the site 8 is the same as the method for the PE2 to send the first packet to the site 4.
  • the PE1 as the first forwarding device may send the blocksize to the PE2, the PE3, and the PE4 as the second forwarding device, and obtain the start as the label block from the one or more PE devices that are the second forwarding device.
  • Labels such as LB1, LB2, and LB3.
  • the PE1 does not need to store N+1 label spaces. Only the LB1, LB2, LB3, and the offset corresponding to the VPN can be forwarded to the corresponding VPN, which helps reduce the forwarding plane. The cost and implementation of a linear lookup table.
  • FIG. 4 is a schematic structural diagram of a first forwarding device according to an embodiment of the present disclosure.
  • the first forwarding device provided by the embodiment of the present application may be PE1 or P in FIG. 2(a), and may also be PE1 in FIG. 3(a).
  • the first forwarding device provided by the embodiment of the present application is described below with reference to FIG. 4 .
  • the first forwarding device includes a first sending unit 401, a first receiving unit 402, and a first obtaining unit 403.
  • the first sending unit 401 is configured to send a request message to the second forwarding device, where the request message includes information of a label block and an identifier of a path, where information of the label block is used to indicate a size of the label block, where the path is The identifier is used to identify a tunnel corresponding to the virtual private network VPN between the first forwarding device and the second forwarding device, where the first The transmitting device is an upstream device of the second forwarding device.
  • the first receiving unit 402 is configured to receive a response message sent by the second forwarding device, where the response message includes a first label and an identifier of the path, where the first label is determined according to information of the label block.
  • the starting tag of the tag block is configured to receive a response message sent by the second forwarding device, where the response message includes a first label and an identifier of the path, where the first label is determined according to information of the label block.
  • the starting tag of the tag block is configured to receive a response message sent by the second forwarding device, where the response message includes a first label and an identifier of the path, where the first label is determined according to information of the label block.
  • the starting tag of the tag block is configured to receive a response message sent by the second forwarding device, where the response message includes a first label and an identifier of the path, where the first label is determined according to information of the label block.
  • the starting tag of the tag block is configured to receive a response message sent by the second forwarding device, where the response message
  • the first obtaining unit 403 is configured to obtain, according to the identifier of the first label and the path, a forwarding entry corresponding to the tunnel.
  • the first forwarding device further includes: a determining unit 404 and a second obtaining unit 405.
  • the determining unit 404 is configured to determine a tunnel corresponding to the VPN.
  • the second obtaining unit 405 is configured to obtain information about the label block according to the tunnel corresponding to the VPN, where the information of the label block is determined by the number of VPNs corresponding to the tunnel.
  • the first obtaining unit 403 is specifically configured to: obtain an identifier of the multicast according to the identifier of the path, where the identifier of the multicast is used to identify multicast forwarding information corresponding to the path; An identifier of the path, where the identifier of the outbound interface is obtained, where the outbound interface is an interface that communicates with the second forwarding device on the first forwarding device; according to the first label, the identifier of the multicast, and the outgoing An identifier of the interface, where the forwarding entry is obtained, where the forwarding entry includes a second label, the identifier of the multicast, and an identifier of the outbound interface, where the second label is based on the first label and the offset The obtained label, the value of the offset corresponding to the VPN.
  • the first forwarding device further includes: a second receiving unit 406, a third obtaining unit 407, and a second sending unit 408.
  • the second receiving unit 406 is configured to receive the first packet from the VPN, and obtain an identifier of the VPN.
  • the third obtaining unit 407 is configured to obtain a second packet according to the forwarding entry, the first packet, and the identifier of the VPN, where the second packet is sent to the The multicast packet of the second forwarding device.
  • the second sending unit 408 is configured to send the second packet to the second forwarding device.
  • the third obtaining unit 407 is specifically configured to: obtain a value of the offset corresponding to the VPN according to the correspondence and the identifier of the VPN, where the correspondence includes the identifier of the VPN and the partial a value of the shift amount; obtaining, according to the forwarding entry and the value of the offset, an identifier of the third label and the outbound interface, where the third label is a value according to the first label and the offset Obtaining a label, the egress interface is configured to communicate with the second forwarding device, and the second sending unit is configured to send the second packet to the second forwarding device according to the identifier of the egress interface.
  • the second packet includes the first packet and the third label.
  • the first forwarding device provided by the embodiment of the present application may be configured to obtain a linear search according to a start label of a label block sent by the second forwarding device, such as a first label and an identifier of the path.
  • Forwarding entries compared to the usual upstream-assigned mode, help reduce the forwarding cost required by the forwarding plane to support the upstream-assigned mode, and also help reduce storage space and improve forwarding efficiency.
  • the number of the forwarding entries obtained by the first forwarding device is smaller than the forwarding entry formed according to the 1+N label space, and the first forwarding device does not need to save 1+N label spaces, which helps to reduce The occupation of storage space.
  • FIG. 5 is a schematic structural diagram of a second forwarding device according to an embodiment of the present disclosure.
  • the second forwarding device provided by the embodiment of the present application may be P, PE2 or PE3 in FIG. 2(a), and may also be PE2, PE3 or PE4 in FIG. 3(a). If the first forwarding device is PE1 of FIG. 2(a), the second forwarding device may be P of FIG. 2(a). If the first forwarding device is P of FIG. 2(a), the second forwarding device may be PE2 or PE3 of FIG. 2(a).
  • the second forwarding device provided in the embodiment of the present application is described below with reference to FIG.
  • the second forwarding device includes: a receiving unit 501, a first obtaining unit 502, and a sending unit 503.
  • the receiving unit 501 is configured to receive a request message sent by the first forwarding device, where the second forwarding device is The downstream device of the first forwarding device, the request message includes information of a label block and an identifier of a path, the information of the label block is used to indicate a size of the label block, and the identifier of the path is used to identify a virtual private network VPN. Tunnel.
  • the first obtaining unit 502 is configured to obtain, according to the information of the label block, a first label, where the first label is a starting label of the label block determined according to information of the label block.
  • the sending unit 503 is configured to send a response message to the first forwarding device, where the response message includes the identifier of the first label and the path.
  • the second forwarding device further includes a second obtaining unit 504.
  • the second obtaining unit 504 is configured to obtain, according to the identifier of the first label and the path, an entry corresponding to the tunnel, where the entry includes a second label, and the second label is according to the The first tag and the offset obtained tag, the value of the offset corresponding to the VPN.
  • the second obtaining unit 504 is specifically configured to: obtain an identifier of the multicast according to the identifier of the path, where the identifier of the multicast is used to identify multicast forwarding information corresponding to the path; And obtaining, by the first label and the identifier of the multicast, the entry, where the entry includes the second label and the identifier of the multicast.
  • the second forwarding device may allocate the first label to the first forwarding device according to the information of the label block sent by the first forwarding device.
  • the second forwarding device reserves a label block that matches the information of the label block according to the information of the label block.
  • the second forwarding device can obtain an entry matching the two parameters according to the offset and the first label carried in the packet from the first forwarding device, so as to be based on the group in the entry.
  • the identifier of the broadcast is obtained, and the label required for sending the packet to the other forwarding device is obtained, so that the second forwarding device does not need to save 1+N label spaces, which helps reduce the occupation of the storage space.
  • FIG. 6 is a schematic structural diagram of a first forwarding device according to an embodiment of the present disclosure.
  • the first forwarding device provided in this embodiment may be the same as the first forwarding device in FIG.
  • the first forwarding device includes a processor 601, a memory 602, and a communication interface 603.
  • the processor 601, the memory 602, and the communication interface 603 are connected by a communication bus 604.
  • the processor 601 may be an NP.
  • the processor 601 may be a central processing unit (CPU).
  • the memory 602 is used to store programs.
  • the processor 601 performs the following operations in accordance with executable instructions included in the program read from the memory 602.
  • the processor 601 sends a request message to the second forwarding device by using the communication interface 603, where the request message includes the information of the label block and the identifier of the path, where the information of the label block is used to indicate the size of the label block.
  • the identifier of the path is used to identify a tunnel corresponding to the virtual private network VPN between the first forwarding device and the second forwarding device, and the first forwarding device is an upstream device of the second forwarding device.
  • the processor 601 receives, by using the communication interface 603, a response message sent by the second forwarding device, where the response message includes a first label and an identifier of the path, where the first label is according to the label block.
  • the information identifies the starting tag of the tag block.
  • the processor 601 obtains a forwarding entry corresponding to the tunnel according to the identifier of the first label and the path.
  • the processor 601 further determines a tunnel corresponding to the VPN, and the processor 601 further obtains information about the label block according to the tunnel corresponding to the VPN, where the information of the label block is Determined by the number of VPNs corresponding to the tunnel.
  • the processor 601 may obtain a multicast identifier according to the identifier of the path, where the identifier of the multicast is used to identify multicast forwarding information corresponding to the path, and the processor 601 may be configured according to the The identifier of the path is obtained, and the outbound interface is an interface that communicates with the second forwarding device on the first forwarding device;
  • the processor 601 may obtain the forwarding entry according to the first label, the identifier of the multicast, and the identifier of the outbound interface, where the forwarding entry includes a second label, the identifier of the multicast, and
  • the identifier of the outbound interface, the second label is a label obtained according to the first label and an offset, and the value of the offset corresponds to a VPN.
  • the processor 601 further receives the first packet from the VPN by using the communication interface 603, and obtains an identifier of the VPN; the processor 601 is further configured to: according to the forwarding entry, the first a packet and the identifier of the VPN, the second packet is obtained, where the second packet is a multicast packet sent to the second forwarding device by using the tunnel; The communication interface 603 sends the second packet to the second forwarding device.
  • the processor 601 may obtain the value of the offset corresponding to the VPN according to the correspondence and the identifier of the VPN, where the correspondence includes the identifier of the VPN and the value of the offset;
  • the processor 601 may obtain, according to the forwarding entry and the value of the offset, an identifier of the third label and the outbound interface, where the third label is according to the first label and the offset a value obtained by the interface, the outbound interface is configured to communicate with the second forwarding device, and the processor 601 sends the identifier to the second forwarding device by using the communication interface 603 according to the identifier of the outgoing interface.
  • a second packet where the second packet includes the first packet and the third label.
  • the forwarding entry generated by the first forwarding device in the control plane of the embodiment of the present application may be stored in the memory of the processor 601. If the first forwarding device further includes a forwarding chip, the forwarding entry generated by the first forwarding device on the forwarding plane may be stored in the forwarding chip. If the first forwarding device does not include the forwarding chip, the forwarding entry generated by the first forwarding device on the forwarding plane may be stored in the memory or the memory 602 of the processor 601.
  • FIG. 7 is a schematic structural diagram of a second forwarding device according to an embodiment of the present disclosure.
  • the second forwarding device shown in FIG. 7 can be the same as the second forwarding device shown in FIG. 5.
  • the first forwarding device includes a processor 701, a memory 702, and a communication interface 703.
  • the processor 701, the memory 702, and the communication interface 703 are connected by a communication bus 704. If the second forwarding device shown in FIG. 7 is a switch in the network, the processor 701 may be an NP. If the second forwarding device shown in FIG. 7 is a router, the processor 701 may be a CPU.
  • the memory 702 is used to store programs.
  • the processor 701 performs the following operations in accordance with executable instructions included in the program read from the memory 702.
  • the processor 701 receives the request message sent by the first forwarding device by using the communication interface 703, the second forwarding device is a downstream device of the first forwarding device, and the request message includes information and path of the label block.
  • the identifier of the label block is used to indicate the size of the label block, and the identifier of the path is used to identify a tunnel corresponding to the virtual private network VPN.
  • the processor 701 obtains a first label according to the information of the label block, where the first label is a start label of the label block determined according to information of the label block.
  • the processor 701 sends a response message to the first forwarding device by using the communication interface 703, where the response message includes the identifier of the first label and the path.
  • the processor 701 further obtains, according to the identifier of the first label and the path, an entry corresponding to the tunnel, where the entry includes a second label, where the second label is a The first tag and the offset obtained tag, the value of the offset corresponding to the VPN.
  • the processor 701 obtains a multicast identifier according to the identifier of the path, where the identifier of the multicast is used to identify multicast forwarding information corresponding to the path, and the processor 701 is configured according to the foregoing. And obtaining, by the label and the identifier of the multicast, the entry, where the entry includes the second label and the identifier of the multicast.
  • the forwarding entry or entry generated by the first forwarding device in the control plane of the embodiment of the present application may be stored in the memory of the processor 701. If the first forwarding device further includes a forwarding chip, the first forwarding device is on the forwarding plane. The generated forwarding entry or entry can be saved in the forwarding chip. If the first forwarding device does not include a forwarding chip, the forwarding entry or entry generated by the first forwarding device on the forwarding plane may be stored in the memory or the memory 702 of the processor 701.

Landscapes

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

Abstract

La présente invention concerne un procédé pour établir un tunnel de diffusion groupée, capable de réduire les coûts d'un plan de transfert et d'améliorer l'efficacité de transfert. Le procédé comprend les étapes suivantes : un premier dispositif de transfert envoie un message de demande à un second dispositif de transfert, le message de demande comprenant des informations de bloc d'étiquette et un identificateur de trajet, les informations de bloc d'étiquette étant utilisées pour représenter la taille d'un bloc d'étiquette, l'identifiant de chemin étant utilisé pour identifier un tunnel, entre le premier dispositif de transfert et le second dispositif de transfert, correspondant à un réseau privé virtuel (VPN), le premier dispositif de transfert étant un dispositif en amont du second dispositif de transfert ; le premier dispositif de transfert reçoit un message de réponse envoyé par le second dispositif de transfert, le message de réponse comprenant une première étiquette et l'identificateur de trajet, la première étiquette étant une étiquette initiale du bloc d'étiquette déterminée selon les informations de bloc d'étiquette ; le premier dispositif de transfert obtient une entrée de transfert correspondant au tunnel selon la première étiquette et l'identificateur de trajet.
PCT/CN2017/088633 2016-07-12 2017-06-16 Procédé et appareil pour établir un tunnel de diffusion groupée WO2018010519A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610546280.5 2016-07-12
CN201610546280.5A CN106209559B (zh) 2016-07-12 2016-07-12 一种建立组播隧道的方法和装置

Publications (1)

Publication Number Publication Date
WO2018010519A1 true WO2018010519A1 (fr) 2018-01-18

Family

ID=57477873

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/088633 WO2018010519A1 (fr) 2016-07-12 2017-06-16 Procédé et appareil pour établir un tunnel de diffusion groupée

Country Status (2)

Country Link
CN (1) CN106209559B (fr)
WO (1) WO2018010519A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112511444A (zh) * 2020-04-03 2021-03-16 中兴通讯股份有限公司 一种组播流量传输方法、装置、通信节点及存储介质

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108337148B (zh) * 2018-02-07 2019-10-18 北京百度网讯科技有限公司 用于获取信息的方法及装置
CN110224935B (zh) * 2018-03-02 2020-10-23 华为技术有限公司 一种处理组播数据报文的方法及装置
US10587937B2 (en) * 2018-04-09 2020-03-10 Futurewei Technologies, Inc. Packet and optical integration
CN111526079B (zh) * 2020-03-31 2023-10-13 新华三技术有限公司 一种建立隧道的方法和装置

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2006002598A1 (fr) * 2004-06-30 2006-01-12 Huawei Technologies Co., Ltd. Systeme vpn de reseau federateur hybride a site hybride et son procede de mise en oeuvre
US7848335B1 (en) * 2005-10-27 2010-12-07 Juniper Networks, Inc. Automatic connected virtual private network
CN102938734A (zh) * 2012-11-26 2013-02-20 杭州华三通信技术有限公司 Mpls网络中隧道的选择方法及pe设备
WO2013154813A1 (fr) * 2012-04-13 2013-10-17 Nicira, Inc. Extension de réseaux logiques à travers des réseaux privés virtuels de couche 3
US9100213B1 (en) * 2011-06-08 2015-08-04 Juniper Networks, Inc. Synchronizing VPLS gateway MAC addresses
CN105515992A (zh) * 2014-09-26 2016-04-20 杭州华三通信技术有限公司 Vxlan网络中的流表项处理方法及装置

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP4192446B2 (ja) * 2001-06-29 2008-12-10 株式会社日立製作所 通信サービス取引方法および通信システム
CN103269315B (zh) * 2013-04-27 2016-03-30 华为技术有限公司 标签分配方法、装置、系统和网络设备
KR20140134998A (ko) * 2013-05-15 2014-11-25 삼성전자주식회사 통신 시스템에서 음성 서비스 성능 향상을 위한 방법 및 장치
CN104954265B (zh) * 2014-03-25 2018-06-15 华为技术有限公司 发送组播报文的方法及交换机
CN104780090B (zh) * 2015-04-27 2018-10-26 新华三技术有限公司 Vpn组播传输的方法、装置、pe设备

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2006002598A1 (fr) * 2004-06-30 2006-01-12 Huawei Technologies Co., Ltd. Systeme vpn de reseau federateur hybride a site hybride et son procede de mise en oeuvre
US7848335B1 (en) * 2005-10-27 2010-12-07 Juniper Networks, Inc. Automatic connected virtual private network
US9100213B1 (en) * 2011-06-08 2015-08-04 Juniper Networks, Inc. Synchronizing VPLS gateway MAC addresses
WO2013154813A1 (fr) * 2012-04-13 2013-10-17 Nicira, Inc. Extension de réseaux logiques à travers des réseaux privés virtuels de couche 3
CN102938734A (zh) * 2012-11-26 2013-02-20 杭州华三通信技术有限公司 Mpls网络中隧道的选择方法及pe设备
CN105515992A (zh) * 2014-09-26 2016-04-20 杭州华三通信技术有限公司 Vxlan网络中的流表项处理方法及装置

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112511444A (zh) * 2020-04-03 2021-03-16 中兴通讯股份有限公司 一种组播流量传输方法、装置、通信节点及存储介质
CN112511444B (zh) * 2020-04-03 2024-06-04 中兴通讯股份有限公司 一种组播流量传输方法、装置、通信节点及存储介质

Also Published As

Publication number Publication date
CN106209559A (zh) 2016-12-07
CN106209559B (zh) 2019-05-07

Similar Documents

Publication Publication Date Title
EP3624408B1 (fr) Procédé de génération d'entrée de table de transfert, dispositif de commande et dispositif de réseau
US12040965B2 (en) Supporting multicast communications
WO2018010519A1 (fr) Procédé et appareil pour établir un tunnel de diffusion groupée
Aggarwal et al. BGP encodings and procedures for multicast in MPLS/BGP IP VPNs
EP2945330B1 (fr) Procédé de gestion d'itinéraires, procédé d'itinéraires, contrôleur de réseau et routeur
CN107026796B (zh) 一种vpn路由通告方法、数据流转发方法及相关设备
WO2015165311A1 (fr) Procédé permettant de transmettre un paquet de données et dispositif côté fournisseur
CN102413059B (zh) 一种基于spb网络的组播转发方法和spbm桥
EP2991284B1 (fr) Procédé et dispositif utilisés dans un réseau privé virtuel ethernet
WO2017124709A1 (fr) Procédé d'établissement d'un tunnel d'ingénierie de trafic et dispositif
CN111263373A (zh) 数据处理方法、控制器和转发设备
CN105453513B (zh) 报文转发方法、转发表项下发方法及网络设备
WO2014194711A1 (fr) Procédé de traitement de paquets, procédé et dispositif de traitement d'étiquette de dispositif
WO2013182061A1 (fr) Procédé, dispositif et système de distribution d'étiquettes de réseau
US11296997B2 (en) SDN-based VPN traffic scheduling method and SDN-based VPN traffic scheduling system
WO2013139270A1 (fr) Procédé, dispositif et système pour implémenter un réseau privé virtuel en couche 3
US10225091B2 (en) Method for implementing point-to-multipoint multicast, network node, and system
WO2011147341A1 (fr) Procédé et dispositif de réseau pour distribuer des étiquettes de commutation multi-protocole par étiquette
WO2013159694A1 (fr) Procédé, dispositif et système de distribution d'étiquettes
WO2017036384A1 (fr) Équipement de bordure de fournisseur et procédé de transfert de données
CN106230730B (zh) 一种组播传输方法和装置
CN108881024B (zh) 一种组播流量转发方法及装置
US12063153B2 (en) Method and apparatus for implementing multicast
CN106330701A (zh) 环形组网的快速重路由方法及装置
WO2018010568A1 (fr) Procédé de notification d'informations et procédé et appareil de génération d'une entrée de transfert

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17826857

Country of ref document: EP

Kind code of ref document: A1

点击 这是indexloc提供的php浏览器服务，不要输入任何密码和下载