WO2014194711A1 - Procédé de traitement de paquets, procédé et dispositif de traitement d'étiquette de dispositif - Google Patents

Procédé de traitement de paquets, procédé et dispositif de traitement d'étiquette de dispositif Download PDF

Info

Publication number
WO2014194711A1
WO2014194711A1 PCT/CN2014/074573 CN2014074573W WO2014194711A1 WO 2014194711 A1 WO2014194711 A1 WO 2014194711A1 CN 2014074573 W CN2014074573 W CN 2014074573W WO 2014194711 A1 WO2014194711 A1 WO 2014194711A1
Authority
WO
WIPO (PCT)
Prior art keywords
label
ingress
bum
tunnel
message
Prior art date
Application number
PCT/CN2014/074573
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 WO2014194711A1 publication Critical patent/WO2014194711A1/fr

Links

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

Definitions

  • the present invention relates to communication technologies, and in particular, to a message processing method, a device label processing method, and a device. Background technique
  • Multi-Point to Multi-Point (MP2MP) services are an important type of service in communication networks.
  • the MP2MP service can be implemented based on Ethernet.
  • the Virtual Private Network (VPN) service is a typical application based on Ethernet to implement MP2MP services.
  • a VPN can be a virtual private LAN service (VPLS) composed of multiple virtual private networks.
  • VPLS can provide LAN-like services. Users can access the network from multiple geographic locations and access each other. , just like these access points are directly connected to the LAN.
  • FIG. 1 is a schematic diagram of a VPLS network in the prior art, and customer sites in different regions are connected to MPLS.
  • a VPLS is formed on the PEs of the multiple provider edge devices of the network.
  • the PE1, PE2, and PE3 devices form an MP2MP tree.
  • the MP2MP tree is used to carry data of two VPLS networks, g ⁇ VPLS A and VPLS B.
  • the PEs are connected to each other through a Pseudo Wire (PW).
  • PW Pseudo Wire
  • the packets are forwarded through the virtual switch instance (VSI) on the PE.
  • the VSI is similar to a virtual bridge (Virtual Bridge).
  • each PE device has two VSIs, VSI A and VSI B, and VSI A is used to forward VPLS A.
  • Data packet VSI B is used to forward VPLS B data packets.
  • the PE device needs to complete the data through the data plane in the VSI.
  • the MAC address learning of the end station and the remote site is the same as that of the traditional switch.
  • the MAC address learning of the remote site is based on the encapsulation information carried in the data packets received from the network. The correspondence between the source MAC and the PW is completed.
  • the VSI on the PE device sends broadcast, unsolicited unicast, and multicast (BUM) packets across the bearer network to different sites belonging to the same VPLS.
  • BUM multicast
  • FIG. 2 is a schematic diagram of the uplink traffic of the BUM packet being forwarded by using the MP2MP tunnel in the prior art
  • FIG. 3 is a schematic diagram of the downlink traffic of the BUM packet being forwarded by using the MP2MP tunnel in the prior art.
  • an MP2MP tree is established between the three Provider Edge (PE) devices and the provider P device.
  • the MP2MP tree can be used to carry data of multiple VPLS networks.
  • Customer Edge (CE) is connected (shown in the figure).
  • PE1 is used as the root node (source is shown in the figure), and PE2 and PE3 are used as child nodes. In the use of receive).
  • BUM messages may enter from multiple entries and be sent to multiple destinations.
  • the PE1 encapsulates the VPLS label and the MP2MP Tree Lable L3 from the inside and the outside after receiving the packet from the CE.
  • the packet is sent to the P device. After receiving the packet, the P device pops up the label L3 and copies the packet.
  • the packet sent to the PE2 is tagged with L1 and sent to the PE3. Label L2.
  • the packet is sent from the PE3.
  • the PE3 After receiving the packet from the CE, the PE3 encapsulates the VPLS label (Label) and the MP2MP tunnel label L6 in the packet 1 and sends it to the packet.
  • the P device pops up the label L6 and copies the packet.
  • the label sent to PE2 is tagged with L1
  • the packet sent to PE3 is tagged with L4. Comparing FIG. 2 and FIG. 3, it can be seen that for PE2, the tunnel label that receives the packet originating from PE1 and the packet originating from PE3 is L1, and the ingress PE device cannot be identified according to the outer tunnel label. Therefore, The PE2 cannot establish the mapping between the source MAC address and the PW of the packet based on the outer MP2MP tunnel label and the inner VPLS label carried in the packet. Therefore, the MAC address of the remote site (that is, the source MAC address of the packet) cannot be learned. Summary of the invention
  • the embodiment of the invention provides a packet processing method, a device label processing method and a device, so that the egress PE device can know which ingress PE device the received BUM message originates from.
  • a first aspect of the present invention provides a packet processing method, including:
  • the egress provider edge PE device receives a broadcast, an unknown unicast, and a multicast BUM packet sent by the ingress PE device through the multi-point to multi-point MP2MP tunnel, where the BUM packet includes a tunnel label and, where the tunnel label is Labeling the device label of the ingress PE device of the MP2MP tunnel;
  • the egress PE device determines that the BUM message originates from the ingress PE device according to the device label of the ingress PE device.
  • the method before the egress PE device receives the BUM packet sent by the ingress PE device through the MP2MP tunnel, the method further includes:
  • the egress PE device receives a correspondence between the device label of the ingress PE device and the ingress PE device sent by the label management device;
  • the egress device determines that the BUM message originates from the ingress PE device according to the device label of the ingress PE device, and includes:
  • the egress PE device determines that the BUM packet originates from the ingress PE device according to the device label of the ingress PE device and the corresponding relationship.
  • the egress PE device determines, according to the device label of the ingress PE device, that the BUM packet is derived from the ingress PE device, and includes:
  • the egress PE device determines that the BUM message originates from the ingress PE device according to the device label of the ingress PE device and the correspondence between the device label of the pre-configured PE device and the PE device.
  • the BUM message further includes The source media access control MAC address of the BUM message and the VPLS label of the virtual private local area network service, after the determining that the BUM message originates from the ingress PE device, the method further includes: the egress PE device according to the VPLS label Determining a pseudo line PW with the ingress device, establishing a correspondence between the source MAC address and the PW.
  • a second aspect of the present invention provides a packet processing method, including:
  • the ingress provider edge PE device receives the broadcast, unknown unicast, and multicast BUM packets sent by the CE device at the user edge.
  • the ingress PE device sets a tunnel label, a device label of the ingress PE device, and a virtual The private area network service VPLS label is encapsulated in the BUM message, where the tunnel label is a label of a multi-point to multi-point MP2MP tunnel;
  • the ingress PE device sends the encapsulated BUM packet to the egress PE device through the MP2MP tunnel, so that the egress PE device determines that the BUM packet originates from the portal according to the device label of the ingress PE device. PE equipment.
  • the method before the ingress PE device encapsulates the tunnel label, the device label of the ingress PE device, and the VPLS label in the BUM message, the method further includes:
  • the ingress PE device requests the tag management device to obtain the device tag of the ingress PE device.
  • the ingress PE device encapsulates the tunnel label, the device label of the ingress PE device, and the VPLS label in the BUM message, including:
  • the ingress PE device encapsulates the tunnel label and the pre-configured device label of the ingress PE device in the BUM packet.
  • a third aspect of the present invention provides a device label processing method, including:
  • the tag management device receives a device tag allocation request message sent by the first provider edge PE device;
  • the tag management device allocates a device tag to the first PE device according to the device tag allocation request message
  • the tag management device sends the allocated device tag to the first PE device, and sends the first PE device and the device tag to other PE devices that have a packet forwarding relationship with the first PE device. Correspondence between the two.
  • a fourth aspect of the present invention provides an edge provider edge PE device, including:
  • a packet receiving module configured to receive a broadcast, an unknown unicast, and a multicast BUM packet sent by the ingress provider edge PE device by using a multi-point to multi-point MP2MP tunnel, where the BUM packet includes a tunnel label and the ingress PE a device label of the device, where the tunnel label is a label of the MP2MP tunnel;
  • the ingress PE device determining module is configured to determine, according to the device label of the ingress PE device, that the BUM message originates from the ingress PE device.
  • the device further includes: a device label receiving module, configured to receive a correspondence between a device label of the ingress PE device and the ingress PE device sent by the label management device;
  • the ingress PE device determining module is specifically configured to determine that the BUM packet originates from the ingress PE device according to the device label of the ingress PE device and the corresponding relationship.
  • the ingress PE device determining module is specifically configured to: according to the device label of the ingress PE device and the device label of the pre-configured PE device and the PE device Corresponding relationship, determining that the BUM message originates from the ingress PE device.
  • the BUM message further includes The source media access control MAC address of the BUM packet and the VPLS label of the virtual private local area network service, where the device further includes:
  • a MAC address learning module configured to determine, according to the VPLS label, a pseudowire PW between the egress PE device and the ingress PE device, and establish a correspondence between the source MAC address and the PW.
  • a fifth aspect of the present invention provides an ingress provider edge PE device, including:
  • a packet receiving module configured to receive a broadcast, an unknown unicast, and a multicast BUM packet sent by the CE device at the user edge;
  • a packet encapsulating module configured to encapsulate a tunnel label, a device label of the ingress PE device, and a virtual private local area network service VPLS label in the BUM packet, where the tunnel label is a multi-point to multi-point MP2MP tunnel Label
  • a packet sending module configured to send the encapsulated BUM packet to the egress PE device by using the MP2MP tunnel, so that the egress PE device determines, according to the device label of the ingress PE device, that the BUM packet originates from The ingress PE device.
  • the device further includes: a device label obtaining module, configured to apply to the label management device for acquiring a device label of the ingress PE device.
  • the packet encapsulating module is specifically configured to: encapsulate the tunnel label, a pre-configured device label of the ingress PE device, and a VPLS label in the In the BUM message.
  • a sixth aspect of the present invention provides a label management device, including: a receiving module, configured to receive a device label allocation request message sent by the first PE device at the provider edge;
  • a device label allocation module configured to allocate a device label to the first PE device according to the device label allocation request message
  • a sending module configured to send the allocated device label to the first PE device, and send the first PE device and the device label to another PE device that has a packet forwarding relationship with the first PE device Correspondence between the two.
  • the device is a provider edge PE device, a route reflector, or a centralized controller.
  • the embodiment of the present invention provides a packet processing method, a device label processing method, and a device.
  • the packet processing method is provided in the embodiment of the present invention.
  • the BUM packet includes a device label of the ingress PE device, and the device label can uniquely identify the ingress PE device.
  • the egress PE device can determine that the packet originates from the ingress PE device according to the device label in the BUM packet.
  • FIG. 1 is a schematic diagram of a VPLS network in the prior art
  • FIG. 2 is a schematic diagram of uplink traffic for forwarding BUM packets using an MP2MP tunnel in the prior art
  • Figure 3 is a schematic diagram of downlink traffic for forwarding BUM packets using an MP2MP tunnel in the prior art
  • Embodiment 4 is a flowchart of Embodiment 1 of a packet processing method according to the present invention.
  • FIG. 5 is a flowchart of Embodiment 2 of a packet processing method according to the present invention.
  • FIG. 6 is a flowchart of Embodiment 3 of a device label processing method according to the present invention.
  • FIG. 7 is a schematic diagram of a PE device applying for a device label to a label management device
  • 9 is a schematic diagram of a label management device sending a device label to each PE
  • FIG. 10 is a schematic diagram of a message of a device label allocation response message
  • Figure 11 is a schematic diagram of the downlink tunnel label delivery during the establishment of an MP2MP tunnel
  • Figure 12 is a schematic diagram of a package format of an LDP mapping message
  • Figure 13 is a schematic diagram of sending an uplink tunnel label during the establishment of an MP2MP tunnel
  • Figure 15 is a schematic diagram of VPLS forwarding MPUM traffic using an MP2MP tunnel
  • 16 is a package format of a BUM packet forwarded between PEs according to the present invention.
  • Figure 17 is a schematic diagram of VPLS forwarding MPUM traffic using an MP2MP tunnel
  • FIG. 21 is a schematic structural diagram of Embodiment 8 of a label management device according to the present invention.
  • FIG. 22 is a schematic structural diagram of Embodiment 9 of an outlet PE device according to the present invention.
  • Embodiment 10 of an ingress PE device according to the present invention is a schematic structural diagram of Embodiment 10 of an ingress PE device according to the present invention.
  • FIG. 24 is a schematic structural diagram of Embodiment 11 of the label management device of the present invention. Specific form
  • Embodiment 1 of a packet processing method according to the present invention. As shown in FIG. 4, the method provided in this embodiment includes the following steps:
  • Step 101 The egress device receives the BUM packet sent by the PE device through the MP2MP tunnel.
  • the BUM packet includes the tunnel label and the device label of the ingress PE device.
  • the tunnel label is the label of the MP2MP tunnel.
  • the ingress PE device After the broadcast, the unknown unicast, and the multicast packet arrive at the ingress PE device, the ingress PE device forwards the BUM packet to the MP2MP tree according to the tunnel corresponding to the established MP2MP tree.
  • the BUM packet received by the ingress PE device includes the source MAC address of the BUM packet, and the ingress PE device encapsulates the tunnel label and the VPLS label in the BUM packet after receiving the BUM packet.
  • the device label of the ingress PE device is encapsulated in a BUM packet, and the device label can uniquely identify a PE device.
  • the egress PE device receives the BUM packet sent by the ingress PE device through the MP2MP tunnel.
  • the BUM packet includes the tunnel label, the device label of the ingress PE device, the VPLS label, and the source media access control (MAC) of the BUM packet. ) address, where the tunnel label is the label of the MP2MP tunnel.
  • Step 102 The egress PE device determines, according to the device label of the ingress PE device, that the BUM packet originates from the ingress PE device.
  • the egress PE device After receiving the BUM packet, the egress PE device parses the device label of the ingress PE device included in the packet, and determines that the BUM packet originates from the ingress PE device according to the device label.
  • the egress PE device determines that the BUM packet originates from the ingress PE device according to the ingress device identifier carried in the BUM packet and the correspondence between the device label of the ingress PE device and the ingress PE device.
  • the correspondence between the device label of the ingress PE device and the ingress PE device may be pre-configured.
  • a device label is statically configured for each PE device in the network.
  • Each PE device saves the device label used by each PE, and forms a correspondence table between the device label and the PE device.
  • the correspondence table saved on each PE device is the same.
  • the egress PE device determines that the BUM packet originates from the ingress PE device according to the device label of the ingress PE device and the mapping between the device label of the pre-configured PE device and the PE device.
  • the correspondence between the device label of the ingress PE device and the ingress PE device is dynamically configured, and the egress PE device receives the entry sent by the label management device before receiving the BUM packet sent by the ingress PE device through the MP2MP tunnel. Corresponding relationship between the device label of the PE device and the ingress PE device. Then, the egress PE device determines that the BUM message originates from the ingress PE device according to the device label and the corresponding relationship of the ingress PE device. In this manner, the label management device uniformly manages the device label, and each PE device applies for the device label to the label management device before using the device label, and the label management device sends the device label to the applied PE device in addition to the device label.
  • the corresponding relationship between the PE device and the device label is sent to other PE devices that have a packet forwarding relationship with the PE device. In this way, the PE is saved on each PE device.
  • Corresponding relationship between the device and the device label so that the egress device determines that the BUM message originates from the ingress PE device according to the device tag and the correspondence between the PE device and the device tag.
  • the BUM packet includes the device label of the ingress PE device, and the device label can uniquely identify the ingress PE device.
  • the egress PE device can be based on the device label in the BUM packet. , determine that the message originates from the ingress PE device.
  • the method further includes the following steps: The egress PE device determines the PW between the ingress PE device and the source MAC according to the VPLS label.
  • the mapping between the address and the PW in this embodiment, the BUM message further includes the source media MAC address and the VPLS label, and the egress PE device determines the PW between the egress PE device and the ingress PE device according to the VPLS label, according to the determination.
  • the PW establishes the relationship between the source MAC address and the PW.
  • a PW is introduced in the MP2MP tree.
  • the PEs in the MP2MP tree are connected to each other through the pseudowires.
  • the packets are forwarded through the corresponding VSIs on the PEs.
  • An MP2MP tree can carry multiple VPLSs.
  • One VPLS corresponds to one VSI.
  • the VSI performs packet forwarding based on PW communication established between PE devices.
  • the PW between PE devices is different. Therefore, the egress PE device needs to determine which ingress PE device the BUM message originates from, and then determine the pseudowire between the egress PE device and the ingress PE device. Since multiple PWs are established between the two PE devices, each PW is used.
  • the VPLS is transmitted, so the egress PE device needs to determine the corresponding PW according to the carried VPLS label.
  • the egress PE parses the VPLS label and the source MAC address of the packet, and determines a pseudowire between the egress PE device and the ingress PE device according to the VPLS label, and establishes a source. Correspondence between the MAC address and the PW.
  • the egress PE device also needs to query the locally saved MAC address table and forward the packet according to the destination MAC address of the BUM packet.
  • FIG. 5 is a flowchart of Embodiment 2 of a packet processing method according to the present invention. The method provided in this embodiment includes the following steps:
  • Step 201 The ingress PE device receives the BUM packet sent by the CE device.
  • the PE device can be connected to one or more CE devices and receive BUM packets sent by the CE device.
  • the BUM packets contain the source MAC address.
  • Step 202 The ingress PE device encapsulates the tunnel label, the device label of the ingress PE device, and the VPLS label in the BUM packet.
  • the ingress PE device After receiving the BUM packet sent by the CE device, the ingress PE device encapsulates the tunnel label in the outermost layer of the packet according to the established MP2MP tunnel.
  • the tunnel label is the MP2MP tunnel.
  • the label of the channel is encapsulated in the BUM packet by the device label and the VPLS label. Specifically, the VPLS label is encapsulated in the inner layer of the tunnel label, and the device label is encapsulated in the inner layer of the VPLS label.
  • Step 203 The ingress PE device sends the encapsulated BUM packet to the egress PE device through the MP2MP tunnel, so that the egress PE device determines that the BUM packet originates from the ingress PE device according to the device label of the ingress PE device.
  • the encapsulated BUM packet is sent to the egress PE device through the MP2MP tunnel.
  • the BUM packet carries the label of the ingress PE device, so that the egress PE device receives the BUM packet. After that, it can be determined that the message originated from the ingress PE device.
  • a premise of this embodiment is that the ingress PE device needs to store its own device label and VPLS label in advance, so that after receiving the BUM packet sent by the CE device, the device label and the VPLS label are encapsulated in the BUM packet.
  • the VPLS label is allocated by the root node and sent to the PEs in the MP2MP tree. This is the prior art and is not mentioned here. The following describes how the ingress PE device obtains the device labels.
  • the device label of the ingress PE device is pre-configured.
  • a device label is statically configured for each PE device in the network.
  • Each PE device in the network stores the PE used by each PE.
  • the device label is a correspondence table between the device label and the PE device.
  • the corresponding relationship table saved on each PE device is the same.
  • the ingress device After receiving the BUM packet sent by the CE device, the ingress device encapsulates the tunnel label, the device label of the pre-configured ingress PE device, and the VPLS label in the BUM packet.
  • the correspondence between the device label of the ingress PE device and the ingress PE device is dynamically configured. Specifically, the ingress PE device requests the label management device to obtain the device label of the ingress PE device before the tunnel label, the device label of the ingress PE device, and the VPLS label are encapsulated in the BUM packet. Then, when the inbound PE device encapsulates the BUM packet, the device label is encapsulated in the BUM packet and sent to the egress PE device. In this manner, the label management device uniformly manages the device label, and each PE device is in the Before using the device label, apply for a device label to the label management device.
  • the label management device sends the PE device to other PE devices that have a packet forwarding relationship with the PE device. Correspondence between device tags. In this way, the correspondence between the PE device and the device label is saved on each PE device, so that the egress device is labeled according to the device. The signature, and the correspondence between the PE device and the device tag, determines that the BUM message originates from the ingress PE device.
  • FIG. 6 is a flowchart of Embodiment 3 of a device label processing method according to the present invention. As shown in FIG. 6, the method provided in this embodiment includes the following steps:
  • Step 301 The label management device receives a device label allocation request message sent by the first PE device.
  • the label management device can be implemented as an independently deployed Route Reflector (RR) under the existing network architecture, or by a PE device that also functions as an RR.
  • RR Route Reflector
  • PE Route Reflector
  • the label management device can be played by a centralized controller (Controller) of the SDN network.
  • the tag management device manages and assigns a device tag to the PE device, which can uniquely identify a PE device.
  • the label management device and each PE complete the application and maintenance of the device label through the control channel.
  • the PE device sends a device label allocation request message to the label management device, and is used to apply for a device label to the label management device.
  • FIG. 6 is a schematic diagram of the PE device applying for the device label to the label management device, as shown in FIG.
  • the PE2 device, the PE3 device, and the P device form a VPLS.
  • the PE devices in the VPLS network have their own unique IP addresses.
  • the IP address of the PE1 device is 192.168.0.1
  • the IP address of the PE2 device is 192.168.0.2.
  • the IP address is 192.168.0.3
  • the IP address of the P device is 192.168.0.4.
  • Figure 7 is a schematic diagram of a PE device applying for a device label to a label management device.
  • the direction indicated by the arrow in Figure 7 indicates that the PE 1 device sends a device label allocation request message to the label management device.
  • the device label allocation request message of the PE device can be implemented in the following packet format.
  • Figure 8 is a schematic diagram of the device label allocation request message. As shown in Figure 8, the message includes the message type, Message Type, and the applicant Requester identifier.
  • the device can also carry the VPN identifier (the VPN ID), the message type is the label request, and the applicant identifier is the PE device identifier, that is, the PE'Identifier, and the PE device identifier can be the IP address of the PE, because the PE device itself It is a router that has a route forwarding function. Therefore, the PE device identifier can be a router ID.
  • the router ID is specifically used to identify the PE device in the route forwarding process. Of course, other identifiers can also be used. Referring to Figure 8, in this embodiment, the applicant is identified as the IP address 192.168.0.1 of PE1.
  • Step 302 The label management device allocates a device label to the first PE device according to the device label allocation request message.
  • the label management device After the label management device allocates the device label to the first PE device, the device label is sent to the first PE device, and the correspondence between the first PE device and the device label is sent to the other PE device that has the packet forwarding relationship with the first PE device. relationship. Specifically, the label management device carries the assigned label in the note allocation response message and sends it to each PE. Each time the tag management device receives the device tag assignment request message sent by the PE device, it records the identifier of the PE device and the device tag sent by the PE device, so that the device tag assignment request sent by other PE devices is received next time. After the message, the device label assigned to the PE device is sent to all saved PE devices.
  • the label management device receives the device label allocation request message sent by the PE1 device for the first time, records the PE1 device and the device label sent by the PE1 device, and sends the assigned device label to the PE1 device; when the label management device receives the second time
  • the device label allocation request message sent to the PE2 device records the PE2 device and the device label sent by the PE2 device, and sends the assigned device label to the PE2 device, and simultaneously sends the correspondence between the PE2 device and the device label of the PE2 device to the PE1 device.
  • the device label of the PE1 device and the PE1 device is not sent to the PE2 device, and the device label of the PE1 device and the PE1 device is also sent to the PE2.
  • the label management device sends the corresponding relationship between the PE device and the device label to all the PE devices that have been recorded according to the already recorded PE device.
  • FIG. 9 is a schematic diagram of a tag management device transmitting a device tag to each PE.
  • the device label assigned by the label management device to the PE1 device is L7, and the device label is carried in the device label allocation response message and sent to the PE1 device, the PE2 device, and the PE3 device.
  • 10 is a schematic diagram of a message of a device label allocation response message.
  • the message includes a message type, that is, a message type, a label owner (Owner) identifier, and a device label (PE'Label) assigned to the PE.
  • the device tag assigned to the tag owner optionally, the VPN ID.
  • the message type is the label request Label Request, and the label owner identifier and the label assignment request message have the same application identifier. If the label assignment request message carries the VPN ID, the label assignment response message also carries the VPN ID.
  • the applicant identifier is the IP address 192.168.0.1 of the PE1. Therefore, the owner identifier is also the IP address 192.168.0.1 of the PE1.
  • PE1, PE2 and B PE3 are receiving After the device label assignment response message sent by the label management device, the correspondence between the IP address of the PE1 and the device label L7 of the PE1 is recorded and saved. After the MP2MP tunnel is established, each PE knows the IP address of the other party. Therefore, the PE After receiving the packet, the device and the PE3 device know that the owner of the device label is a PE1 device based on the IP address. The PE2 device and the PE3 device also need to send a label allocation request message to the label management device to obtain the device label.
  • the device label management device sends the device label of the PE2 device and the PE3 device to the PE1 device, the PE2 device, and the PE3 device. . In this way, the device labels of the PE1 device, the PE2 device, and the PE3 device are saved on each PE device.
  • the label management device uniformly allocates a device label to each PE device, and sends a correspondence between the device label and the device allocated to each PE device to a packet forwarding relationship with the PE device.
  • Other PE devices such that the ingress PE device encapsulates its own device label when the BUM packet is encapsulated, and the egress PE device determines the packet according to the device label carried in the packet and the corresponding relationship between the PE device and the device label stored in the packet. Originated from that PE device.
  • the process of establishing an MP2MP tunnel is briefly introduced. In this embodiment, the VPLS service is assumed. After the deployment is complete, the process of establishing an MP2MP tunnel and the process of using the MP2MP tunnel to carry BUM traffic are also described.
  • FIG 11 is a schematic diagram of the downlink tunnel label delivery in the process of establishing an MP2MP tunnel.
  • the MP2MP tree established in this embodiment uses the PE1 device as the root node, and the PE2 device, the PE3 device, and the P device as the child nodes.
  • the PE1 device, the PE2 device, and the PE3 device can be used as both an ingress PE device and an egress PE device.
  • the uplink and the downlink mentioned in this embodiment are respectively said for the traffic direction, and the traffic direction is the root node PE1 as a reference point.
  • the process of issuing the downlink tunnel label is as follows:
  • the PE2 device receives the BUM packet from the network side and allocates a downlink tunnel label, such as L1, through the Label Distribution Protocol (LDP) mapping message.
  • the device is notified to the P device.
  • the PE3 device receives the BUM packet from the network side, and assigns a downlink tunnel label, for example, L2, to the P device through the LDP mapping message, and the P device saves the downlink tunnel label information received from the PE2 device and the PE3 device. , assign a downlink tunnel label to the PE1 device. For example, L3,
  • the device is notified to the PE1 device through the LDP mapping message.
  • the format of the LDP mapping message mentioned in this embodiment is shown in Figure 12.
  • Figure 12 is a schematic diagram of the encapsulation format of the LDP mapping message.
  • TLV Value, referred to as TLV
  • FEC Forwarding Equivalence Class
  • the Generic Label TLV represents the label assigned to the corresponding forwarding equivalence class.
  • Label indicates an assigned tunnel label.
  • the downlink tunnel label assigned to PE1 in the figure is L1.
  • the downlink tunnel label assigned to PE2 is L1
  • the assigned downlink tunnel label to PE3 is L3.
  • FIG 13 is a schematic diagram of the uplink label tunneling process in the process of establishing an MP2MP tunnel.
  • the PE device advertises the uplink tunnel label as follows:
  • the PE1 device receives BUM packets from the network side and allocates an uplink tunnel label, for example, L4.
  • the LDP mapping message is sent to the P device.
  • the P device saves the uplink label information received from the PE1 device, and allocates an uplink tunnel label to the PE2 device and the PE3 device.
  • the PE2 device allocates the uplink tunnel label L5 to the PE3 device.
  • the tunnel label L6 is notified to the PE2 device and the PE3 device through the LDP mapping message.
  • a complete MP2MP tunnel with PE1 as the root is established, which is also called a multi-point to multi-point label switching path (MP2MP LSP).
  • MP2MP LSP multi-point to multi-point label switching path
  • the VPLS service can forward the BUM traffic to the network side to utilize the MP2MP tunnel.
  • you need to maintain two tunnel labels. Take the PE2 device as an example.
  • the PE2 device functions as the ingress PE device and receives the BUM packets on the network side and forwards them to PE1 and PE3, the uplink tunnel label L5 is used.
  • the PE2 device functions as the egress PE device.
  • the received packets are all the downlink tunnel labels L1.
  • the PE device After the establishment of the MP2MP tunnel is complete, the PE device needs to apply for the device label to the label management device. For details, refer to the description in the fourth embodiment, and no further details are provided here. In this embodiment, it is assumed that the device label applied by the PE1 device is L7. The device label applied for by the PE2 device is L8, and the device label applied for by the PE3 device is L3. Of course, the above device labels can also be statically configured, and no PE device is required to apply.
  • the MP2MP tunnel label and the device label are all allocated.
  • the channel forwards BUM traffic.
  • FIG. 14 is a flowchart of a method for processing a packet according to a fourth embodiment of the present invention.
  • FIG. 15 is a schematic diagram of a VPLS forwarding an BUM traffic using an MP2MP tunnel.
  • the packet traffic originates from PE1 in the embodiment, so PE1 is used as The ingress device, the PE2 device, and the PE3 device are both used as egress devices.
  • the method provided in this embodiment includes the following steps:
  • Step 401 The PE1 device receives the BUM packet sent by the network side.
  • the BUM packet received by the PE1 device contains the source MAC address.
  • Step 402 The PE1 device encapsulates the tunnel label L3, the device label L7, and the VPLS label in the BUM packet, and sends the encapsulated packet to the P device.
  • FIG. 16 is a package format of a BUM packet forwarded between PEs in the present invention.
  • the BUM packet includes: MP2MP Tree Label, VPLS. Label, PE Label, C-Eth Header, Payload, the explanation of each field is shown in Table 1.
  • the C-Eth Header includes the source MAC address and the destination MAC address of the BUM packet, and the upper layer data type of the Ethernet bearer.
  • the VPLS label indicates a VPLS.
  • the The packet has a PE label, and the PE Label is the device label of the ingress PE device.
  • PE1 encapsulates the device label L7 as the innermost label, that is, the inner layer of the MP2MP tunnel label and the VPLS label.
  • the direction indicated by the arrow in the figure is the flow direction of the packet.
  • PE1 encapsulates the tunnel label L3 in the outermost layer, then the VPLS label, and encapsulates the device label L7 as the innermost label.
  • Step 403 After receiving the BUM message sent by the PE1, the P device ejects the tunnel label L3 and copies the packet, one encapsulated tunnel label L1 and the other encapsulated tunnel label L2.
  • the P device After receiving the packet sent by PE1, the P device ejects the outermost label, that is, the MP2MP tunnel.
  • the label is duplicated and the packet is re-encapsulated.
  • the VPLS label and the device label are not parsed. Therefore, the device label L7 of the PE1 device is also carried in the copied packet.
  • Step 404 The device sends the packet of the tunnel label L1 to the PE2, and sends the packet of the encapsulated tunnel label L2 to the PE3 device.
  • the P device sends the re-encapsulated packets to the corresponding PE device according to their respective tunnel labels.
  • Step 405 The PE1 device and the PE2 device receive the BUM packet sent by the P device, and determine that the BUM packet originates from the PE1 device according to the device label L7 included in the BUM packet.
  • the PE1 device and the PE2 device respectively receive the BUM packets sent by the P device.
  • the BUM packets include the tunnel label, the VPLS label, the device label of the ingress PE device, and the source MAC address of the BUM packet.
  • the PE2 device determines that the BUM packet originates from the PE1 device according to the device label L7 carried in the packet and according to the correspondence between the PE1 device and the device label stored in the packet.
  • the PE2 device is used as an example.
  • the VPLS label is used to determine the PW used by the PE1 device and the PE2 device to carry the VPLS service.
  • the MP2MP tree carries two VPLSs.
  • VPLSA and VPLSB indicate that the PW ID of the packets forwarded between the PE1 and the PE2 is 100, and the PW identifier used to forward the VPLSB packets is 200.
  • the PE2 determines the packet according to the VPLS label carried in the packet.
  • the VPLSA is also the VPLSB, and then determines the PW used, establishes the correspondence between the source MAC address of the BUM packet and the PW, and completes the learning of the MAC address of the remote site.
  • FIG 17 is a schematic diagram of the VPLS using the MP2MP tunnel to forward BUM traffic.
  • the BUM packet is sent from the PE3 device.
  • the PE1 device is the ingress device
  • the PE1 device and the PE2 device are the egress devices
  • the PE3 receives the network side.
  • the tunnel label L6, the VPLS label, and the device label L9 are encapsulated in the packet and sent to the P device.
  • the P device ejects the tunnel label L6 and copies the packet.
  • the tunnel label L1 is encapsulated in the packet and sent to the PE2 device.
  • the tunnel label L4 is encapsulated in another packet and sent to the PE1 device.
  • PE1 and PE3 determine that the packet originates from the PE3 device according to the device label L9 carried in the packet.
  • the BUM packet tunnel label received by PE2 is L1, but the device label carried in the BUM packet from the PE1 device and the PE3 device is different.
  • the PE2 device can determine the BUM based on the device label. The message originated from that PE device. After determining that the BUM message originates from the ingress PE device, determine the PW between the ingress PE device and the ingress PE device according to the VPLS label. Establish a mapping between the source MAC address and the PW.
  • the ingress PE device after receiving the BUM packet sent by the network side, the ingress PE device encapsulates the device label in the packet and sends the label to the egress PE device, so that the egress PE device according to the device carried in the packet
  • the label is determined to be from the ingress PE device, and the PW between the egress PE device and the ingress PE device is determined according to the VPLS label, and the correspondence between the source MAC address and the PW is established, and the MAC address of the remote site is completed. Learning.
  • FIG. 18 is a flowchart of Embodiment 5 of the egress PE device of the present invention.
  • the device provided in this embodiment includes: a packet receiving module 51 and an ingress PE device determining module 52.
  • the packet receiving module 51 is configured to receive a broadcast, an unknown unicast, and a multicast BUM packet sent by the ingress PE device through the multi-point to multi-point MP2MP tunnel, where the BUM packet includes the tunnel label and the device of the ingress PE device.
  • the label, where the tunnel label is the label of the MP2MP tunnel, and the ingress PE device determining module 52 is configured to determine that the BUM message originates from the ingress PE device according to the device label of the ingress PE device.
  • the ingress PE device determining module 52 is specifically configured to determine, according to the device label of the ingress PE device and the correspondence between the device label of the pre-configured PE device and the PE device, that the BUM packet originates from the ingress PE. device.
  • the label of each PE device is pre-configured, and the correspondence between the device label of the ingress PE device and the ingress PE device can be pre-configured.
  • each PE device in the network is statically configured. A device label, each PE device in the network stores the device label used by each PE, and forms a correspondence table between the device label and the PE device. The correspondence table saved on each PE device is the same.
  • the ingress PE device determining module 52 determines that the BUM message originates from the ingress PE device according to the device label of the ingress PE device and the correspondence between the device label of the pre-configured PE device and the PE device.
  • the BUM packet further includes a source MAC address of the BUM packet and a VPLS label
  • the egress PE device further includes a MAC address learning module, where the ingress PE device determining module 52 determines that the BUM packet originates from the portal.
  • the mapping between the source MAC address and the PW is established. Therefore, the learning of the MAC address of the remote site is completed, and a point-to-point connection between the egress PE device and the ingress PE device is established, and the PW connection communication between the egress PE device and the ingress PE device is established.
  • the method provided in this embodiment can be used to implement the solution provided by the method embodiment, and the specific implementation is implemented.
  • the mode and technical effect types are not described here.
  • FIG. 19 is a flowchart of Embodiment 6 of an egress PE device according to the present invention.
  • the device provided in this embodiment includes: a packet receiving module 61, an ingress PE device determining module 62, a device tag receiving module 63, and a MAC address. Learning module 64.
  • the packet receiving module 61 is configured to receive the broadcast, the unknown unicast, and the multicast BUM packet sent by the ingress PE device through the MP2MP tunnel, where the BUM packet includes the tunnel label and the device label of the ingress PE device.
  • the ingress PE device determining module 62 is configured to determine, according to the device label of the ingress PE device, that the BUM message originates from the ingress PE device.
  • the device label receiving module 63 is configured to receive a correspondence between the device label of the ingress PE device sent by the label management device and the ingress PE device.
  • the BUM packet further includes a source MAC address and a VPLS label of the BUM packet
  • the MAC address learning module 64 is configured to determine a pseudowire PW between the egress PE device and the ingress PE device according to the VPLS label, and establish a source. Correspondence between the MAC address and the PW.
  • the ingress PE device determining module is specifically configured to determine that the BUM packet originates from the ingress PE device according to the device label of the ingress PE device and the corresponding relationship.
  • the correspondence between the device label of the ingress PE device and the ingress PE device is dynamically configured, and the ingress PE device determining module 62 determines that the BUM packet originates from the ingress PE device before the device label according to the device label of the ingress PE device.
  • the receiving module 63 receives the correspondence between the device label of the ingress PE device and the ingress PE device sent by the label management device, and the ingress PE device determining module 62 is specifically configured to determine the BUM report according to the device label and the corresponding relationship of the ingress PE device.
  • the text is derived from the ingress PE device.
  • the MAC address learning module 64 determines the PW between the ingress PE device and the egress PE device according to the VPLS label carried in the packet, and establishes the source MAC address and The mapping between the PWs is completed, and the learning of the MAC address of the remote site is completed, and a point-to-point connection between the egress PE device and the ingress PE device is established, and the PW connection communication between the egress PE device and the ingress PE device is established.
  • the label management device uniformly manages the device label, and each PE device applies for the device label to the label management device before using the device label, and the label management device sends the device label to the applied PE device in addition to the device label.
  • the corresponding relationship between the PE device and the device label is sent to other PE devices that have a packet forwarding relationship with the PE device.
  • each PE The corresponding relationship between the PE device and the device label is saved on the device, so that the egress device determines that the BUM message originates from the ingress PE device according to the device label and the correspondence between the PE device and the device label.
  • the egress PE device provided in this embodiment may be used to implement the technical solutions, the specific implementation manners, and the technical effect types provided in the first embodiment and the fourth embodiment, and details are not described herein again.
  • FIG. 20 is a flowchart of Embodiment 7 of the ingress PE device of the present invention.
  • the device provided in this embodiment includes: a packet receiving module 71, a packet encapsulating module 72, and a packet sending module 73.
  • the message receiving module 71 is configured to receive a broadcast, a unknown unicast, and a multicast BUM message sent by the user edge CE device.
  • the packet encapsulating module 72 is configured to encapsulate the tunnel label, the device label of the ingress PE device, and the virtual private local area network service VPLS label in the BUM packet;
  • the encapsulated packet includes the tunnel label, the device label of the ingress PE device, and the VPLS label, and the source MAC address of the BUM packet.
  • the tunnel label is a multi-point to multi-point MP2MP tunnel label.
  • the packet sending module 73 is configured to send the encapsulated BUM packet to the egress PE device through the MP2MP tunnel, so that the egress PE device determines that the BUM packet originates from the ingress PE device according to the device label of the ingress PE device.
  • a premise of the present embodiment is that the ingress PE device needs to obtain its own device label in advance.
  • the device label of each PE device is pre-configured, and each PE device stores a correspondence between the PE device label and the device. Table, the correspondence table saved on each PE device is the same. Therefore, the packet encapsulating module 72 is specifically configured to encapsulate the tunnel label, the device label of the pre-configured ingress PE device, and the VPLS label in the BUM packet.
  • the ingress PE device needs to apply for a device label to the label management device before the packet encapsulation module encapsulates the packet. Therefore, the ingress PE device further includes: a device label obtaining module, configured to apply to the label management device. Obtain the device label of the ingress PE device.
  • the ingress PE device provided in this embodiment may be used to implement the technical solutions provided by the method embodiment 2 and the fourth embodiment.
  • the specific implementation manners and technical effects are similar, and details are not described herein again.
  • FIG. 21 is a schematic structural diagram of Embodiment 8 of the label management device of the present invention.
  • the device provided in this embodiment includes: a receiving module 81, a device label allocating module 82, and a sending module 83.
  • the receiving module 81 is configured to receive a device label assignment sent by the first provider edge PE device. Request message
  • the device label allocation module 82 is configured to allocate a device label to the first PE device according to the device label allocation request message;
  • the sending module 83 is configured to send the allocated device label to the first PE device, and send the correspondence between the first PE device and the device label to other PE devices that have a packet forwarding relationship with the first PE device.
  • each PE device may send a label allocation request message to the label management device for requesting to allocate a device label, and the receiving module 81 of the label management device receives the device label allocation request message sent by the first PE device.
  • the device label allocation module 82 allocates a device label to the first PE device according to the device label allocation request message, and sends the allocated device label to the first PE device that initiates the application through the sending module 83, and simultaneously sends the device to the other PE devices in the network. Sending a correspondence between the first PE device and the device label, so that the other PE device determines the correspondence between the saved PE device and the device label when receiving the BUM packet sent by the first PE device.
  • the message is derived from the first PE device.
  • the device provided in this embodiment can be used to implement the technical solution provided in the third embodiment.
  • the specific implementation and technical effects are similar, and details are not described herein again.
  • the label management device may be a provider edge PE device, a route reflector or a centralized controller.
  • the existing network architecture it can be played by an independently deployed route reflector or by a PE device that also acts as a route reflector.
  • SDN Network Architecture, Label Manager can be played by a centralized controller of the SDN network.
  • FIG. 22 is a schematic structural diagram of Embodiment 9 of the egress PE device of the present invention.
  • the egress PE device 900 provided in this embodiment includes: a processor 91, a memory 92, a transmitter 93, and a receiver 94.
  • the memory 92, the transmitter 93, and the receiver 94 can be connected to the processor 91 via a bus.
  • the memory 92 stores execution instructions.
  • the processor 91 communicates with the memory 92, and the processor 91 executes execution instructions so that the egress PE device 900 performs the message processing method provided by the present invention.
  • the processor 91 is configured to perform the following operations:
  • the receiver 94 is configured to receive a broadcast, an unknown unicast, and a multicast BUM packet sent by the ingress PE device through the multi-point to multi-point MP2MP tunnel, where the BUM packet includes a tunnel label and a device label of the ingress PE device, where the tunnel The label is the label of the MP2MP tunnel;
  • the processor 91 is configured to determine, according to the device label of the ingress PE device, that the BUM message originates from the ingress PE device.
  • the receiver 94 receives the BUM message sent by the ingress PE device through the MP2MP tunnel, and is further configured to receive a correspondence between the device label of the ingress PE device and the ingress PE device sent by the label management device, and store the correspondence in the memory.
  • the processor 91 is specifically configured to determine that the BUM message originates from the ingress PE device according to the device label of the ingress PE device and the correspondence between the device label of the ingress PE device and the ingress PE device.
  • the correspondence between the device label of the PE device and the PE device may be pre-configured and stored in the memory 92, and the processor 91 is specifically configured to use the device label of the ingress PE device and the pre-configured PE device.
  • Correspondence between the device label and the PE device determines that the BUM message originates from the ingress PE device.
  • the BUM packet further includes a source MAC address and a VPLS label.
  • the processor 91 is further configured to determine a pseudowire PW between the ingress PE device and the source MAC address according to the VPLS label. The correspondence between the PWs is to complete the learning of the remote MAC address.
  • FIG. 23 is a schematic structural diagram of Embodiment 10 of the ingress PE device of the present invention.
  • the ingress PE device 100 provided in this embodiment includes: a processor 11, a memory 12, a transmitter 13, and a receiver 14, and the transmitter 13 Both the receiver 14 and the memory 12 can be connected to the processor 11 via a bus.
  • the memory 11 stores the execution instructions.
  • the processor 11 communicates with the memory 12, and the processor 11 executes the execution instructions to cause the ingress PE device to execute the message processing method provided by the embodiment of the present invention.
  • the receiver 14 is configured to receive a broadcast, an unknown unicast, and a multicast BUM message sent by the CE device at the user edge;
  • the processor 11 is configured to encapsulate the tunnel label, the device label of the ingress PE device, and the virtual private local area network service VPLS label in the BUM packet according to the BUM packet received by the receiver 14, where the tunnel label is multi-point to most Point the label of the MP2MP tunnel;
  • the transmitter 13 is configured to send the BUM packet encapsulated by the processor 11 to the egress PE device through the MP2MP tunnel, so that the egress PE device determines that the BUM packet originates from the ingress PE device according to the device label of the ingress PE device.
  • the processor 11 is further configured to apply to the label management device for obtaining the configuration of the ingress PE device before the tunnel label, the device label of the ingress PE device, and the VPLS label are encapsulated in the BUM packet.
  • the label is prepared and the device tag is stored in the memory 12.
  • the processor 92 does not need to apply to the label management device for acquiring the device label, and the device label is pre-configured, and the processor 92 is specifically configured to package the tunnel label, the device label of the pre-configured ingress PE device, and the VPLS label. In the BUM message.
  • the ingress PE device provided in this embodiment may be used to perform the technical solution provided by the foregoing method embodiments, and the specific implementation manners and technical effects are similar, and details are not described herein again.
  • FIG. 24 is a schematic structural diagram of a label management device according to an embodiment of the present invention.
  • the label management device 1100 provided in this embodiment includes: a processor 110, a memory 120, a transmitter 130, and a receiver 140, and a transmitter. Both 130 and receiver 140 and memory 120 can be coupled to processor 110 via a bus.
  • the memory 120 stores execution instructions.
  • the processor 110 communicates with the memory 120, and the processor 110 executes the execution instructions to cause the tag management device 1100 to execute the device tag processing method provided by the embodiment of the present invention.
  • the receiver 140 is configured to receive a device label allocation request message sent by the first provider edge PE device.
  • the processor 110 is configured to allocate a device label to the first PE device according to the device label allocation request message;
  • the transmitter 120 is configured to send the allocated device label to the first PE device, and send the correspondence between the first PE device and the device label to other PE devices that have a packet forwarding relationship with the first PE device.
  • the label management device is a provider edge PE device, a route reflector, or a centralized controller.
  • each PE device may send a label allocation request message to the label management device for requesting to allocate a device label, and the receiver 140 of the label management device receives the device label allocation request message sent by the first PE device.
  • the processor 110 allocates a device label to the first PE device according to the device label allocation request message, and sends the allocated device label to the first PE device that initiates the application through the transmitter 130, and simultaneously sends the device label to the other PE devices in the network.
  • Corresponding relationship between the first PE device and the device label so that the other PE device determines the report according to the correspondence between the saved PE device and the device label when receiving the BUM message sent by the first PE device
  • the text is derived from the first PE device.
  • the aforementioned program can be stored in a calculation
  • the machine can be read from the storage medium.
  • the program when executed, performs the steps including the foregoing method embodiments; and the foregoing storage medium includes: a medium that can store program codes, such as a ROM, a RAM, a magnetic disk, or an optical disk.

Landscapes

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

Abstract

Les modes de réalisation selon la présente invention concernent un procédé de traitement de paquets, un procédé et un dispositif de traitement d'étiquette de dispositif. Le procédé de traitement de paquets comprend les étapes suivantes : (101) un dispositif PE (situé à la périphérie d'un fournisseur) de sortie reçoit un paquet de diffusion, de diffusion individuelle indéterminée et de multidiffusion (BUM) envoyé par un dispositif PE d'entrée par l'intermédiaire d'un tunnel multipoint à multipoint (MP2MP), le paquet BUM comportant une étiquette de tunnel et une étiquette de dispositif du dispositif PE d'entrée, et l'étiquette de tunnel étant une étiquette du tunnel MP2MP ; et (102) le dispositif PE de sortie détermine, selon l'étiquette de dispositif du dispositif PE d'entrée, que le paquet BUM provient du dispositif PE d'entrée. Dans le procédé selon le mode de réalisation de la présente invention, un paquet BUM comprend une étiquette de dispositif d'un dispositif PE d'entrée, l'étiquette de dispositif pouvant identifier de manière unique le dispositif PE d'entrée, et après qu'un dispositif PE de sortie a reçu le paquet BUM, le dispositif PE de sortie peut déterminer que le paquet provient du dispositif PE d'entrée selon l'étiquette de dispositif dans le paquet BUM.
PCT/CN2014/074573 2013-06-03 2014-04-01 Procédé de traitement de paquets, procédé et dispositif de traitement d'étiquette de dispositif WO2014194711A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201310216416.2A CN103312611B (zh) 2013-06-03 2013-06-03 报文处理方法、设备标签处理方法及设备
CN201310216416.2 2013-06-03

Publications (1)

Publication Number Publication Date
WO2014194711A1 true WO2014194711A1 (fr) 2014-12-11

Family

ID=49137410

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2014/074573 WO2014194711A1 (fr) 2013-06-03 2014-04-01 Procédé de traitement de paquets, procédé et dispositif de traitement d'étiquette de dispositif

Country Status (2)

Country Link
CN (1) CN103312611B (fr)
WO (1) WO2014194711A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3389234A4 (fr) * 2015-12-30 2018-12-05 Huawei Technologies Co., Ltd. Procédé de gestion d'étiquette, et procédé et dispositif pour traiter un flux de données
CN114430393A (zh) * 2020-10-16 2022-05-03 华为技术有限公司 报文处理方法、装置及存储介质

Families Citing this family (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103312611B (zh) * 2013-06-03 2016-12-28 华为技术有限公司 报文处理方法、设备标签处理方法及设备
CN104579959B (zh) * 2013-10-18 2017-12-01 上海贝尔股份有限公司 在mpls网络中建立sdn流的标签交换路径的方法和设备
WO2015078002A1 (fr) * 2013-11-29 2015-06-04 华为技术有限公司 Procédé, dispositif et système de traitement de message
CN105099846B (zh) * 2014-04-30 2018-10-19 华为技术有限公司 传输数据报文的方法和供应商边缘设备
CN106453144B (zh) * 2015-08-10 2020-01-31 华为技术有限公司 软件定义网络中的报文处理方法和设备
CN106302176B (zh) * 2016-08-15 2019-10-22 华为技术有限公司 一种用于控制组播传输的方法及设备
WO2018047943A1 (fr) * 2016-09-09 2018-03-15 日本電気株式会社 Système de communication, nœud périphérique, procédé de communication et programme
CN109587059B (zh) * 2017-09-28 2021-07-09 华为技术有限公司 Sr-be内层隧道标签的配置方法、设备及通信系统
CN110224942B (zh) * 2018-03-01 2023-08-04 中兴通讯股份有限公司 一种报文处理方法、装置及存储介质
CN112119615A (zh) * 2019-07-01 2020-12-22 深圳市大疆创新科技有限公司 消息流显示方法和装置、无人驾驶系统以及可移动平台
CN110572322B (zh) * 2019-08-16 2021-07-13 苏州工业职业技术学院 一种通过修改查找关键字提高组播转发效率的方法
CN111740907A (zh) * 2020-05-29 2020-10-02 新华三信息安全技术有限公司 一种报文传输方法、装置、设备及机器可读存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101155130A (zh) * 2006-09-30 2008-04-02 华为技术有限公司 学习mac地址的方法及传送vpls客户数据的系统及设备
CN101170514A (zh) * 2007-12-04 2008-04-30 华为技术有限公司 实现接入电路接口间访问控制的方法和装置
CN101667954A (zh) * 2009-10-14 2010-03-10 中兴通讯股份有限公司 多层虚拟专用局域网业务的网络及其数据处理方法
CN103312611A (zh) * 2013-06-03 2013-09-18 华为技术有限公司 报文处理方法、设备标签处理方法及设备

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101155130A (zh) * 2006-09-30 2008-04-02 华为技术有限公司 学习mac地址的方法及传送vpls客户数据的系统及设备
CN101170514A (zh) * 2007-12-04 2008-04-30 华为技术有限公司 实现接入电路接口间访问控制的方法和装置
CN101667954A (zh) * 2009-10-14 2010-03-10 中兴通讯股份有限公司 多层虚拟专用局域网业务的网络及其数据处理方法
CN103312611A (zh) * 2013-06-03 2013-09-18 华为技术有限公司 报文处理方法、设备标签处理方法及设备

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3389234A4 (fr) * 2015-12-30 2018-12-05 Huawei Technologies Co., Ltd. Procédé de gestion d'étiquette, et procédé et dispositif pour traiter un flux de données
US11233732B2 (en) 2015-12-30 2022-01-25 Huawei Technologies Co., Ltd. Label management method, data stream processing method, and device
US11588730B2 (en) 2015-12-30 2023-02-21 Huawei Technologies Co., Ltd. Label management method, data stream processing method, and device
EP4236251A3 (fr) * 2015-12-30 2023-10-04 Huawei Technologies Co., Ltd. Procédé de gestion d'étiquette et dispositif pour traiter un flux de données
CN114430393A (zh) * 2020-10-16 2022-05-03 华为技术有限公司 报文处理方法、装置及存储介质
CN114430393B (zh) * 2020-10-16 2022-12-06 华为技术有限公司 报文处理方法、装置及存储介质

Also Published As

Publication number Publication date
CN103312611A (zh) 2013-09-18
CN103312611B (zh) 2016-12-28

Similar Documents

Publication Publication Date Title
WO2014194711A1 (fr) Procédé de traitement de paquets, procédé et dispositif de traitement d'étiquette de dispositif
CN109218178B (zh) 一种报文处理方法及网络设备
US10484203B2 (en) Method for implementing communication between NVO3 network and MPLS network, and apparatus
WO2020029976A1 (fr) Procédé de mise en oeuvre inter-domaine de réseau privé virtuel, dispositif et noeud frontière
US8861547B2 (en) Method, apparatus, and system for packet transmission
EP2945330B1 (fr) Procédé de gestion d'itinéraires, procédé d'itinéraires, contrôleur de réseau et routeur
US8693323B1 (en) System and method for managing communications in an access network
WO2017162095A1 (fr) Procédé, dispositif et système de communication basés sur un protocole de spécification de flux
WO2019128621A1 (fr) Procédé pour supporter un réseau privé virtuel de multidiffusion et dispositif
WO2015165311A1 (fr) Procédé permettant de transmettre un paquet de données et dispositif côté fournisseur
WO2008092357A1 (fr) Procédé et dispositif pour établir un tunnel pseudocâblé et transmettre un message à l'aide de celui-ci
WO2015192501A1 (fr) Procédé et appareil de libération d'informations d'adresse
EP2634975A1 (fr) Procédé et dispositif d'envoi de message
WO2014194749A1 (fr) Procédé et appareil de traitement d'implémentation de vpn pour dispositif de bordure
US20120218994A1 (en) Network communication method and network node device
WO2009021458A1 (fr) Procédé, appareil et système de connexion d'un réseau de couche 2 à un réseau de couche 3
JP2014532368A (ja) トラフィックエンジニアリングトンネルに基づく仮想プライベートネットワーク実行方法及びシステム
EP2991284B1 (fr) Procédé et dispositif utilisés dans un réseau privé virtuel ethernet
WO2007095799A1 (fr) Procédé et système permettant de réaliser une émulation pseudo-filaire de bout en bout de l'interface de groupage
WO2017113772A1 (fr) Procédé de gestion d'étiquette, et procédé et dispositif pour traiter un flux de données
WO2013139270A1 (fr) Procédé, dispositif et système pour implémenter un réseau privé virtuel en couche 3
CN113132235B (zh) 基于虚电路的数据报文处理方法、转发表项的构建方法
WO2013182061A1 (fr) Procédé, dispositif et système de distribution d'étiquettes de réseau
WO2009135392A1 (fr) Procédé, système et dispositif de commande de signalisation
WO2008011818A1 (fr) Procédé de fourniture d'un service réseau local privé virtuel à hiérarchie et système réseau

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

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

Country of ref document: EP

Kind code of ref document: A1