WO2014194711A1 - 报文处理方法、设备标签处理方法及设备 - Google Patents
报文处理方法、设备标签处理方法及设备 Download PDFInfo
- 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
Links
- 238000003672 processing method Methods 0.000 title claims abstract description 32
- 238000000034 method Methods 0.000 claims abstract description 39
- 238000005538 encapsulation Methods 0.000 claims description 6
- 238000007726 management method Methods 0.000 description 66
- 238000010586 diagram Methods 0.000 description 32
- 238000013507 mapping Methods 0.000 description 14
- 230000008569 process Effects 0.000 description 11
- 230000000694 effects Effects 0.000 description 6
- 230000004044 response Effects 0.000 description 6
- 238000004891 communication Methods 0.000 description 5
- 230000006870 function Effects 0.000 description 4
- 230000006855 networking Effects 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 2
- 238000004364 calculation method Methods 0.000 description 1
- 238000002372 labelling Methods 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000005641 tunneling Effects 0.000 description 1
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
本发明实施例提供一种报文处理方法、设备标签处理方法及设备,该报文处理方法包括:出口提供商边缘Provider Edge(PE)设备接收入口PE设备通过多点到多点Multi-Point to Multi-Point(MP2MP)隧道发送的广播、未知单播、组播Broadcast,Unknown Unicast,Multicast(BUM)报文,所述BUM报文中包含隧道标签以及所述入口PE设备的设备标签,其中,所述隧道标签为所述MP2MP隧道的标签(101);所述出口PE设备根据所述入口PE设备的设备标签,确定所述BUM报文源自所述入口PE设备(102)。本实施例提供的方法,BUM报文中包含入口PE设备的设备标签,该设备标签能够唯一标识入口PE设备,出口PE设备在接收到该BUM报文后,能够根据BUM报文中的设备标签,确定该报文源自入口PE设备。
Description
报文处理方法、 设备标签处理方法及设备 本申请要求于 2013 年 06 月 03 日提交中国专利局、 申请号为 201310216416. 2、 发明名称为 "报文处理方法、 设备标签处理方法及设备" 的中国专利申请的优先权, 其全部内容通过引用结合在本申请中。
技术领域
本发明涉及通信技术, 尤其涉及一种报文处理方法、 设备标签处理方 法及设备。 背景技术
多点到多点 (Multi-Point to Multi-Point, 简称 MP2MP) 业务是通信网 络中的一个重要业务类型。 目前 MP2MP业务可以基于以太网实现, 其中, 虚拟专用网 (Virtual Private Network, 简称 VPN) 业务是基于以太网实现 MP2MP业务的一个典型应用。 VPN可以是多个虚拟专用网络组成的一个虚 拟专用局域网业务 (Virtual Private LAN Service, 简称 VPLS ) , VPLS可以 提供类似局域网的业务, 可以是用户从多个地理位置分散点同时接入网络, 相互访问, 就像这些接入点直接接入到局域网。
现有技术中, 实现 MP2MP大都采用多协议标签交换 (Multi Protocol Label Switch, 简称 MPLS ) 技术, 如图 1所示, 图 1为现有技术中 VPLS 网络的示意图, 不同地域的客户站点连接到 MPLS 网络的多个提供商边缘 设备 PE上构成一个 VPLS, 图 1中, PE1、 PE2、 PE3设备组成一个 MP2MP 树, 该 MP2MP树用来承载 2个 VPLS网络的数据, g卩 VPLS A和 VPLS B。 各 PE设备之间通过伪线 (Pseudo Wire, 简称 PW) 进行全连接, 通过 PE 设备上对应的虚拟交换实例 VSI (Virtual Switch Instance ) 进行报文转发, VSI类似一个虚拟网桥(Virtual Bridge, 简称 VB), 网络侧的 PW与用户侧 连接 CE的接口都可以看成是这个 VB的端口, 图中每个 PE设备上都有两 个 VSI, VSI A和 VSI B , VSI A用来转发 VPLS A数据报文, VSI B用来转 发 VPLS B数据报文。 一方面, PE设备要在 VSI中通过数据平面完成对本
端站点和远端站点的 MAC学习, 对本端站点的 MAC地址学习与传统交换 机方式一致,对远端站点的 MAC地址学习则是根据从网络侧接收到的数据 报文所携带的封装信息建立报文源 MAC与 PW的对应关系来完成。另一方 面, PE设备上的 VSI将广播、未知单播、组播(Broadcast, Unknown Unicast, Multicast, 简称 BUM) 报文跨承载网发送到属于同一 VPLS的不同站点。
图 2为现有技术中使用 MP2MP隧道转发 BUM报文的上行流量示意 图,图 3为现有技术中使用 MP2MP隧道转发 BUM报文的下行流量示意图。 如图 2和图 3所示, 通过三个提供商边缘 (Provider Edge, 简称 PE) 设备 与提供商 P设备建立一个 MP2MP树,该 MP2MP树可以用来承载多个 VPLS 网络的数据, PE设备与客户边缘 (Customer Edge, 简称 CE) 相连 (图中 为示出), 图 2和图 3中, 该 MP2MP数中, PE1作为根节点(图中用 source 表示), PE2和 PE3作为子节点 (图中用 receive表示)。
在 MP2MP树中, BUM报文可能从多个入口进入,发往多个目的出口。 如图 2所示, 当 BUM报文始发自 PE1时, PE1接收到 CE发送的报文后, 从内向外对报文封装 VPLS标签(Label)和 MP2MP隧道标签(MP2MP Tree Lable) L3封转在报文中,发送给 P设备, P设备收到报文后,弹出标签 L3 , 将报文复制两份, 将发送给 PE2的报文中加上标签 L1 , 发送给 PE3的报文 中加上标签 L2。 如图 3所示, 报文始发自 PE3, PE3接收到 CE发送的报 文后, 从内向外对报文封装 VPLS标签(Label)和 MP2MP隧道标签 L6封 转在报文 1中, 发送给 P设备, P设备收到报文后, 弹出标签 L6, 将报文 复制两份, 将发送给 PE2的报文中加上标签 L1 , 发送给 PE3的报文中加上 标签 L4。 比较图 2和图 3可知, 对于 PE2来说, 接收到来自 PE1始发的报 文和来自 PE3始发的报文的隧道标签都是 L1 , 根据外层隧道标签无法识别 入口 PE设备, 因此, PE2无法根据报文所携带的外层 MP2MP隧道标签加 内层 VPLS标签来建立报文源 MAC与 PW的对应关系,从而无法完成远端 站点的 MAC (即报文源 MAC) 的学习。 发明内容
本发明实施例提供一种报文处理方法、 设备标签处理方法及设备, 使 出口 PE设备能够获知接收到的 BUM报文源自哪个入口 PE设备。
本发明第一方面提供一种报文处理方法, 包括:
出口提供商边缘 PE设备接收入口 PE设备通过多点到多点 MP2MP隧 道发送的广播、 未知单播、 组播 BUM报文, 所述 BUM报文中包含隧道标 签以及, 其中, 所述隧道标签为所述 MP2MP隧道的标签所述入口 PE设备 的设备标签;
所述出口 PE设备根据所述入口 PE设备的设备标签, 确定所述 BUM 报文源自所述入口 PE设备。
在本发明第一方面的第一种可能的实现方式中,所述出口 PE设备接收 入口 PE设备通过 MP2MP隧道发送的 BUM报文之前, 还包括:
所述出口 PE设备接收标签管理设备发送的所述入口 PE设备的设备标 签与所述入口 PE设备之间的对应关系;
所述出口 PE设备根据所述入口 PE设备的设备标签, 确定所述 BUM 报文源自所述入口 PE设备, 包括:
所述出口 PE设备根据所述入口 PE设备的设备标签和所述对应关系, 确定所述 BUM报文源自所述入口 PE设备。
在本发明第一方面的第二种可能的实现方式中,所述出口 PE设备根据 所述入口 PE设备的设备标签,确定所述 BUM报文源自所述入口 PE设备, 包括:
所述出口 PE设备根据所述入口 PE设备的设备标签以及预先配置的 PE 设备的设备标签与 PE设备之间的对应关系, 确定所述 BUM报文源自所述 入口 PE设备。
结合本发明第一方面及本发明第一方面的第一种和第二种可能的实现 方式,在本发明第一方面的第三种可能的实现方式中,所述 BUM报文中还 包含所述 BUM报文的源媒体接入控制 MAC地址以及虚拟专用局域网业务 VPLS标签, 所述确定所述 BUM报文源自所述入口 PE设备之后, 还包括: 所述出口 PE设备根据所述 VPLS标签确定与所述入口设备之间的伪线 PW, 建立所述源 MAC地址与所述 PW之间的对应关系。
本发明第二方面提供一种报文处理方法, 包括:
入口提供商边缘 PE设备接收用户边缘 CE设备发送的广播、未知单播、 组播 BUM报文;
所述入口 PE设备将隧道标签、 所述入口 PE设备的设备标签以及虚拟
专用局域网业务 VPLS标签封装在所述 BUM报文中, 其中, 所述隧道标签 为多点到多点 MP2MP隧道的标签;
所述入口 PE设备通过所述 MP2MP隧道向出口 PE设备发送封装后的 BUM报文, 以使所述出口 PE设备根据所述入口 PE设备的设备标签,确定 所述 BUM报文源自所述入口 PE设备。
在本发明第二方面的第一种可能的实现方式中,所述入口 PE设备将隧 道标签、 所述入口 PE设备的设备标签以及 VPLS标签封装在所述 BUM报 文中之前, 还包括:
所述入口 PE设备向标签管理设备申请获取所述入口 PE设备的设备标 签。
在本发明第二方面的第二种可能的实现方式中,所述入口 PE设备将隧 道标签、 所述入口 PE设备的设备标签以及 VPLS标签封装在所述 BUM报 文中, 包括:
所述入口 PE设备将所述隧道标签、 预先配置的所述入口 PE设备的设 备标签封装在所述 BUM报文中。
本发明第三方面提供一种设备标签处理方法, 包括:
标签管理设备接收第一提供商边缘 PE 设备发送的设备标签分配请求 消息;
所述标签管理设备根据所述设备标签分配请求消息,为所述第一 PE设 备分配设备标签;
所述标签管理设备向所述第一 PE设备发送分配好的设备标签,并向与 所述第一 PE设备具有报文转发关系的其它 PE设备发送所述第一 PE设备 与所述设备标签之间的对应关系。
本发明第四方面提供一种出口提供商边缘 PE设备, 包括:
报文接收模块, 用于接收入口提供商边缘 PE 设备通过多点到多点 MP2MP隧道发送的广播、 未知单播、 组播 BUM报文, 所述 BUM报文中 包含隧道标签以及所述入口 PE设备的设备标签, 其中, 所述隧道标签为所 述 MP2MP隧道的标签;
入口 PE设备确定模块, 用于根据所述入口 PE设备的设备标签, 确定 所述 BUM报文源自所述入口 PE设备。
在本发明第四方面的第一种可能的实现方式中, 所述设备, 还包括:
设备标签接收模块,用于接收标签管理设备发送的所述入口 PE设备的 设备标签与所述入口 PE设备之间的对应关系;
所述入口 PE设备确定模块具体用于, 根据所述入口 PE设备的设备标 签和所述对应关系, 确定所述 BUM报文源自所述入口 PE设备。
在本发明第四方面的第二种可能的实现方式中,所述入口 PE设备确定 模块具体用于, 根据所述入口 PE设备的设备标签以及预先配置的 PE设备 的设备标签与 PE设备之间的对应关系, 确定所述 BUM报文源自所述入口 PE设备。
结合本发明第四方面及本发明第四方面的第一种和第二种可能的实现 方式,在本发明第四方面的第三种可能的实现方式中,所述 BUM报文中还 包含所述 BUM报文的源媒体接入控制 MAC地址以及虚拟专用局域网业务 VPLS标签, 所述设备还包括:
MAC地址学习模块, 用于根据所述 VPLS标签确定所述出口 PE设备 与所述入口 PE设备之间的伪线 PW, 建立所述源 MAC地址与所述 PW之 间的对应关系。
本发明第五方面提供一种入口提供商边缘 PE设备, 包括:
报文接收模块, 用于接收用户边缘 CE设备发送的广播、 未知单播、 组 播 BUM报文;
报文封装模块, 用于将隧道标签、所述入口 PE设备的设备标签以及虚 拟专用局域网业务 VPLS标签封装在所述 BUM报文中, 其中, 所述隧道标 签为多点到多点 MP2MP隧道的标签;
报文发送模块, 用于通过所述 MP2MP隧道向出口 PE设备发送封装后 的 BUM报文, 以使所述出口 PE设备根据所述入口 PE设备的设备标签, 确定所述 BUM报文源自所述入口 PE设备。
在本发明第五方面的第一种可能的实现方式中, 所述设备, 还包括: 设备标签获取模块,用于向标签管理设备申请获取所述入口 PE设备的 设备标签。
在本发明第五方面的第二种可能的实现方式中, 所述报文封装模块具 体用于, 将所述隧道标签、 预先配置的所述入口 PE 设备的设备标签以及 VPLS标签封装在所述 BUM报文中。
本发明第六方面提供一种标签管理设备, 包括:
接收模块,用于接收提供商边缘第一 PE设备发送的设备标签分配请求 消息;
设备标签分配模块, 用于根据所述设备标签分配请求消息, 为所述第 一 PE设备分配设备标签;
发送模块, 用于向所述第一 PE设备发送分配好的设备标签, 并向与所 述第一 PE设备具有报文转发关系的其它 PE设备发送所述第一 PE设备与 所述设备标签之间的对应关系。
在本发明第六方面的第一种可能的实现方式中, 所述设备为提供商边 缘 PE设备、 路由反射器或者集中控制器。
本发明实施例提供一种报文处理、 设备标签处理方法及设备, 本发明 实施例提供的报文处理方法, BUM报文中包含入口 PE设备的设备标签, 该设备标签能够唯一标识入口 PE设备, 出口 PE设备在接收到该 BUM报 文后, 能够根据 BUM报文中的设备标签, 确定该报文源自入口 PE设备。 附图说明
为了更清楚地说明本发明实施例或现有技术中的技术方案, 下面将对 实施例或现有技术描述中所需要使用的附图作简单地介绍, 显而易见地, 下面描述中的附图仅仅是本发明的一些实施例, 对于本领域普通技术人员 来讲, 在不付出创造性劳动性的前提下, 还可以根据这些附图获得其他的 附图。
图 1为现有技术中 VPLS网络的示意图;
图 2为现有技术中使用 MP2MP隧道转发 BUM报文的上行流量示意 图;
图 3为现有技术中使用 MP2MP隧道转发 BUM报文的下行流量示意 图;
图 4为本发明报文处理方法实施例一的流程图;
图 5为本发明报文处理方法实施例二的流程图;
图 6为本发明设备标签处理方法实施例三的流程图;
图 7为 PE设备向标签管理设备申请设备标签的示意图;
图 9为标签管理设备向各 PE发送设备标签的示意图;
图 10为设备标签分配响应消息的报文示意图;
图 11为 MP2MP隧道建立过程中下行隧道标签下发示意图;
图 12为 LDP Mapping消息的封装格式示意图;
图 13为 MP2MP隧道建立过程中上行隧道标签下发示意图;
图 14为本发明报文处理方法实施例四的流程图;
图 15为 VPLS使用 MP2MP隧道转发 BUM流量的示意图;
图 16为本发明中在各 PE之间转发的 BUM报文的封装格式;
图 17为 VPLS使用 MP2MP隧道转发 BUM流量的示意图;
图 18为本发明出口 PE设备实施例五的流程图;
图 19为本发明出口 PE设备实施例六的流程图;
图 20为本发明入口 PE设备实施例七的流程图;
图 21为本发明标签管理设备实施例八的结构示意图;
图 22为本发明出口 PE设备实施例九的结构示意图;
图 23为本发明入口 PE设备实施例十的结构示意图;
图 24为本发明标签管理设备实施例十一的结构示意图。 具体实 式
为使本发明实施例的目的、 技术方案和优点更加清楚, 下面将结合本 发明实施例中的附图, 对本发明实施例中的技术方案进行清楚、 完整地描 述, 显然, 所描述的实施例是本发明一部分实施例, 而不是全部的实施例。 基于本发明中的实施例, 本领域普通技术人员在没有做出创造性劳动前提 下所获得的所有其他实施例, 都属于本发明保护的范围。
图 4为本发明报文处理方法实施例一的流程图, 如图 4所示, 本实施 例提供的方法包括以下歩骤:
歩骤 101、出口 PE设备接收入口 PE设备通过 MP2MP隧道发送的 BUM 报文, BUM报文中包含隧道标签以及入口 PE设备的设备标签其中, 隧道 标签为 MP2MP隧道的标签。
对于广播、 未知单播、 组播报文到达入口 PE设备后, 入口 PE设备根 据已经建立的 MP2MP树对应的隧道, 将 BUM报文转发到 MP2MP树中的
其他出口 PE设备上。 本实施例中, 入口 PE设备接收到的 BUM报文中包 括该 BUM报文的源 MAC地址, 入口 PE设备在接收到 BUM报文后, 不 仅将隧道标签和 VPLS标签封装在 BUM报文, 还将入口 PE设备的设备标 签封装在 BUM报文, 该设备标签能够唯一标识一个 PE设备。 出口 PE设 备接收入口 PE设备通过 MP2MP隧道发送的 BUM报文, BUM报文中包含 隧道标签、 入口 PE设备的设备标签、 VPLS标签以及 BUM报文的源媒体 接入控制 (Media Access Control, 简称 MAC) 地址, 其中, 该隧道标签为 MP2MP隧道的标签。
歩骤 102、出口 PE设备根据入口 PE设备的设备标签,确定 BUM报文 源自入口 PE设备。
出口 PE设备接收到 BUM报文后, 解析获取报文中包含的入口 PE设 备的设备标签, 根据该设备标签, 确定该 BUM报文始发自入口 PE设备。
具体地, 出口 PE设备可以根据 BUM报文中的携带的入口设备标识, 以及自身存储的入口 PE设备的设备标签和入口 PE设备之间的对应关系确 定 BUM报文始发自入口 PE设备。
一种实现方式中, 入口 PE设备的设备标签和入口 PE设备之间的对应 关系可以预先配置,在初始组网时为网络中的每个 PE设备上都静态配置一 个设备标签, 该网络中每个 PE设备都保存各个 PE所使用的设备标签, 组 成设备标签与 PE设备的对应关系表, 每个 PE设备上保存的对应关系表都 是相同的。 出口 PE设备接收到 BUM报文后, 根据入口 PE设备的设备标 签以及预先配置的 PE 设备的设备标签与 PE 设备之间的对应关系, 确定 BUM报文源自入口 PE设备。
在另一种实现方式中, 入口 PE设备的设备标签和入口 PE设备之间的 对应关系动态配置, 出口 PE设备接收入口 PE设备通过 MP2MP隧道发送 的 BUM报文之前, 接收标签管理设备发送的入口 PE设备的设备标签与入 口 PE设备之间的对应关系; 然后, 出口 PE设备根据入口 PE设备的设备 标签和对应关系, 确定 BUM报文源自入口 PE设备。 在这种方式中, 由标 签管理设备统一管理设备标签,每一个 PE设备在使用设备标签之前都向标 签管理设备申请设备标签, 标签管理设备除了将该设备标签发送给申请的 PE设备外, 还向与该 PE设备具有报文转发关系的其它 PE设备发送该 PE 设备与设备标签之间的对应关系。 这样, 每个 PE设备上都会保存有该 PE
设备与设备标签之间的对应关系, 从而使得出口设备根据该设备标签, 以 及 PE设备与设备标签之间的对应关系确定该 BUM报文源自入口 PE设备。
本实施例提供的方法, BUM报文中包含入口 PE设备的设备标签, 该 设备标签能够唯一标识入口 PE设备, 出口 PE设备在接收到该 BUM报文 后, 能够根据 BUM报文中的设备标签, 确定该报文源自入口 PE设备。
进一歩地, 在歩骤 102之后, 即出口 PE设备确定 BUM报文源自入口 PE设备之后还可以包括以下歩骤: 出口 PE设备根据 VPLS标签确定与入 口 PE设备之间的 PW, 建立源 MAC地址与 PW之间的对应关系, 本实施 例中, BUM报文中还包含源媒体 MAC地址以及 VPLS标签, 出口 PE设 备根据 VPLS标签确定该出口 PE设备与入口 PE设备之间的 PW, 根据确 定的 PW建立源 MAC地址与 PW之间的关系。先简单介绍 PW,在 MP2MP 树中各 PE之间都通过伪线进行全连接, 且通过 PE设备上对应的 VSI进行 报文转发,一个 MP2MP树可以承载多个 VPLS,—个 VPLS对应一个 VSI, VSI在进行报文转发时是根据 PE设备之间建立的 PW通信, 各个 PE设备 之间的 PW是不同的。 因此, 出口 PE设备首先需要确定 BUM报文源自哪 个入口 PE设备, 进而确定出口 PE设备和入口 PE设备之间的伪线, 由于 两个 PE设备之间会建立多条 PW, 每条 PW用于传输一个 VPLS, 所以出 口 PE设备还需要根据携带的 VPLS标签确定对应的 PW。具体地, 出口 PE 在确定 BUM报文源自入口 PE设备之后, 解析获取该报文的 VPLS标签以 及源 MAC地址, 并根据 VPLS标签确定出口 PE设备与入口 PE设备之间 的伪线, 建立源 MAC地址与 PW之间的对应关系。 出口 PE设备还需要査 询本地保存的 MAC地址表, 根据 BUM报文的目的 MAC, 转发该报文。
图 5为本发明报文处理方法实施例二的流程图, 本实施例提供的方法, 包括以下歩骤:
歩骤 201、 入口 PE设备接收 CE设备发送的 BUM报文。
PE设备可以和一个或多个 CE设备连接, 接收 CE设备发送来的 BUM 报文, 该 BUM报文中包含源 MAC地址。
歩骤 202、入口 PE设备将隧道标签、入口 PE设备的设备标签以及 VPLS 标签封装在 BUM报文中。
入口 PE设备在接收到 CE设备发送的 BUM报文后, 根据已经建立的 MP2MP隧道, 将隧道标签封装在报文的最外层, 该隧道便签为 MP2MP隧
道的标签, 并将自身的设备标签以及 VPLS标签封装在 BUM报文中, 具体 地,将 VPLS标签封装在隧道标签的内层,将设备标签封装在 VPLS标签的 内层。
歩骤 203、 入口 PE设备通过 MP2MP隧道向出口 PE设备发送封装后 的 BUM报文, 以使出口 PE设备根据入口 PE设备的设备标签, 确定 BUM 报文源自入口 PE设备。
入口 PE设备将报文封装好后, 通过 MP2MP隧道将封装后的 BUM报 文发送至出口 PE设备, 该 BUM报文中携带入口 PE设备的标签, 从而使 得出口 PE设备在接收到该 BUM报文后, 能够确定该报文源自入口 PE设 备。
本实施例的一个前提是,入口 PE设备需要预先存储自身的设备标签和 VPLS标签, 从而在接收到 CE设备发送的 BUM报文后, 将自身的设备标 签和 VPLS标签封装在 BUM报文中。其中, VPLS标签在触发建立 MP2MP 树时, 由根节点分配并下发给 MP2MP树中的各 PE设备, 此为现有技术, 这里不再赘述, 以下主要介绍入口 PE设备如何获取设备标签。
一种实现方式中, 入口 PE设备的设备标签预先配置, 在初始组网时为 网络中的每个 PE设备上都静态配置一个设备标签, 该网络中每个 PE设备 都保存各个 PE所使用的设备标签,组成设备标签与 PE设备的对应关系表, 每个 PE设备上保存的对应关系表都是相同的。 入口设备在接收到 CE设备 发送的 BUM报文后, 将隧道标签、 预先配置的入口 PE设备的设备标签以 及 VPLS标签封装在 BUM报文中。
在另一种实现方式中, 入口 PE设备的设备标签和入口 PE设备之间的 对应关系动态配置。 具体地, 入口 PE设备将隧道标签、 入口 PE设备的设 备标签以及 VPLS标签封装在 BUM报文中之前,向标签管理设备申请获取 入口 PE设备的设备标签。 然后, 入口 PE设备在封装 BUM报文时, 将自 身的设备标签封装在 BUM报文中, 发送给出口 PE设备, 在这种方式中, 由标签管理设备统一管理设备标签,每一 PE设备在使用设备标签之前都向 标签管理设备申请一个设备标签, 标签管理设备除了将该设备标签发送给 申请的 PE设备外, 还向与该 PE设备具有报文转发关系的其它 PE设备发 送该 PE设备与设备标签之间的对应关系。 这样, 每个 PE设备上都会保存 有该 PE设备与设备标签之间的对应关系,从而使得出口设备根据该设备标
签,以及 PE设备与设备标签之间的对应关系确定该 BUM报文源自入口 PE 设备。
图 6为本发明设备标签处理方法实施例三的流程图, 如图 6所示, 本 实施例提供的方法, 包括以下歩骤:
歩骤 301、 标签管理设备接收第一 PE设备发送的设备标签分配请求消 息。
标签管理设备即 Label Manager在现有网络架构下, 可以为一***立部 署的路由反射器 (Route Reflector, 简称 RR) 实现, 或者是由一台兼做 RR 的 PE设备。 在软件自定义网络(Software-Defined Network, 简称 SDN)架 构下, 标签管理设备可以由 SDN网络的集中控制器 (Controller) 来扮演。
标签管理设备为 PE设备管理和分配一个设备标签,该设备标签能够唯 一标识一个 PE设备。 标签管理设备和各 PE之间通过控制通道完成设备标 签的申请和维护。
首先, PE设备向标签管理设备发送设备标签分配请求消息, 用于向标 签管理设备申请一个设备标签, 图 6为 PE设备向标签管理设备申请设备标 签的示意图, 如图 6所示, PE1设备、 PE2设备、 PE3设备和 P设备组成一 个 VPLS, 位于该 VPLS网内的 PE设备都具有各自唯一的 IP地址, PE1设 备的 IP为 192.168.0.1, PE2设备的 IP地址为 192.168.0.2, PE3设备的 IP 地址为 192.168.0.3, P设备的 IP地址为 192.168.0.4。
图 7为 PE设备向标签管理设备申请设备标签的示意图, 图 7中箭头所 指的方向表示 PE 1 设备向标签管理设备发送设备标签分配请求消息。 PE 设备的设备标签分配请求消息具体可以通过以下报文格式实现, 图 8 为设 备标签分配请求消息的报文示意图, 如图 8所示, 该报文包括消息类型即 Message Type, 申请者 Requester标识,可选地,还可以携带 VPN标识 (; VPN ID), 消息类型为标签请求 Label Request, 申请者标识为 PE 设备标识即 PE'Identifier, PE设备标识可以为 PE的 IP地址, 由于 PE设备本身就是一 台路由器, 具有路由转发功能, 因此, PE设备标识可以为路由器 ID, 路由 器 ID具体用于在路由转发过程中标识该 PE设备, 当然还可以采用其他标 识。 参照图 8, 本实施例中, 申请者标识为 PE1的 IP地址 192.168.0.1。
歩骤 302、 标签管理设备根据设备标签分配请求消息, 为第一 PE设备 分配设备标签。
歩骤 303、 标签管理设备向第一 PE设备发送分配好的设备标签, 并向 与第一 PE设备具有报文转发关系的其它 PE设备发送第一 PE设备与设备 标签之间的对应关系。
标签管理设备为第一 PE设备分配设备标签后, 向第一 PE设备发送设 备标签,并向与第一 PE设备具有报文转发关系的其它 PE设备发送第一 PE 设备与设备标签之间的对应关系。 具体地, 标签管理设备将分配好的标签 携带在便签分配响应消息中发送给各 PE。 标签管理设备每次在接收到 PE 设备发送的设备标签分配请求消息后, 都会记录该 PE 设备的标识和为该 PE设备发送的设备标签, 以便下次接收到其他 PE设备发送的设备标签分 配请求消息后,向保存的所有 PE设备都发送为该 PE设备分配的设备标签。 例如,标签管理设备第一次接收到 PE1设备发送的设备标签分配请求消息, 记录 PE1设备以及为 PE1设备发送的设备标签, 并向 PE1设备发送分配的 设备标签; 当标签管理设备第二次接收到 PE2设备发送的设备标签分配请 求消息, 记录 PE2设备以及为 PE2设备发送的设备标签, 并且向 PE2设备 发送分配的设备标签, 同时向 PE1设备发送 PE2设备和为 PE2设备的设备 标签的对应关系,并且根据记录査询到没有向 PE2设备发送 PE1设备与 PE1 设备的设备标签, 则将 PE1设备与 PE1设备的设备标签也发送给 PE2。 以 此类推, 标签管理设备在接收到 PE设备发送的标签设备分配请求消息后, 根据已经记录的 PE设备, 向已经记录的所有 PE设备都发送该 PE设备与 设备标签的对应关系。
图 9为标签管理设备向各 PE发送设备标签的示意图。 如图 9所示, 标 签管理设备为 PE1设备分配的设备标签为 L7, 并将该设备标签携带在设备 标签分配响应消息中分别发送给 PE1设备、 PE2设备和 PE3设备。 图 10为 设备标签分配响应消息的报文示意图, 如图 10所示, 该报文包括消息类型 即 Message Type , 标签拥有者 (Owner) 标识, 分配给 PE 的设备标签 (PE'Label) , 即分配给标签拥有者的设备标签, 可选地, 还可以携带 VPN ID。 其中, 消息类型为标签请求 Label Request, 标签拥有者标识和标签分 配请求消息中的申请标识相同, 若标签分配请求消息中携带了 VPN ID, 则 在标签分配响应消息中也携带 VPN ID。
参照图 9, 本实施例中, 申请者标识为 PE1的 IP地址 192.168.0.1, 因 此, 拥有者标识也为 PE1的 IP地址 192.168.0.1。 PE1、 PE2禾 B PE3在接收
到标签管理设备发送的设备标签分配响应消息后, 记录和保存 PE1的 IP地 址和 PE1 的设备标签 L7的对应关系, 由于在建立 MP2MP隧道后, 各个 PE都互相知道对方的 IP地址, 因此, PE 2设备和 PE3设备在收到报文后, 根据 IP地址知道设备标签的拥有者是 PE1设备。其中 PE2设备和 PE3设备 也需要向标签管理设备发送标签分配请求消息, 获取自身的设备标签, 设 备标签管理设备将 PE2设备和 PE3设备的设备标签也分别发送给 PE 1设 备、 PE2设备和 PE3设备。 这样, 在各 PE设备上, 都保存有 PE1设备、 PE2设备和 PE3设备的设备标签。
本实施例提供的方法, 标签管理设备统一为每个 PE 设备分配设备标 签,并将为每个 PE设备分配的设备标签与设备之间的对应关系发送给与该 PE设备具有报文转发关系的其它 PE设备,以使得入口 PE设备在封转 BUM 报文时自身的设备标签封装进去,出口 PE设备根据报文中携带的设备标签 及自身存储的 PE设备与设备标签的对应关系, 确定报文源自与那个 PE设 备。
以下将通过具体例子说明出口 PE设备和入口 PE设备如何使用设备标 签进行报文的转发, 在介绍报文转发过程之前, 先简单介绍一下 MP2MP 隧道的建立过程, 本实施例中, 假设 VPLS 业务已经部署完毕, 此处仅描 述 MP2MP隧道建立过程和 VPLS使用 MP2MP隧道承载 BUM流量的具体 过程。
图 11为 MP2MP隧道建立过程中下行隧道标签下发示意图, 本实施例 中建立的 MP2MP树, 是以 PE1设备作为根节点, PE2设备、 PE3设备及 P 设备作为子节点, 在 MP2MP隧道中, 流量即可以从根节点流入, 也可以从 其他子节点流入, 因此, 本发明中, PE1设备、 PE2设备、 PE3设备既可以 作为入口 PE设备, 也可以作为出口 PE设备。 本实施例中提到的上行和下 行分别是是针对流量方向说的, 而流量方向是以根节点 PE1作为参考点。
如图 11所示, 各 PE设备发布下行隧道标签过程如下: PE2设备为从 网络侧接收 BUM报文, 分配一个下行隧道标签, 例如 L1 , 通过标签分发 协议(Label Distribution Protocol, 简称 LDP) Mapping 消息通知给 P设备, PE3设备为从网络侧接收 BUM报文, 分配一个下行隧道标签, 例如 L2, 通过 LDP Mapping 消息通知给 P设备, P设备保存从 PE2设备和 PE3设备 接收到的下行隧道标签信息,为 PE1设备分配一个下行隧道标签。例如 L3 ,
通过 LDP Mapping 消息通知给 PEl设备。本实施例中提到的 LDP Mapping 消息的格式如图 12所示, 图 12为 LDP Mapping消息的封装格式示意图, 这里只简单描述一下该消息中包括的两个类型、 长度、 值 (Type、 Length, Value, 简称 TLV), 一个是转发等价类 (Forwarding Equivalence Class, 简 称 FEC) TLV, 用来表示一系列分组用相似或同样的特征, 其可能以同样 的方式被运送, 即它可能被束缚到相同的 MPLS 标签中转发。 通用标签 (Generic Label TLV) 表示为相应的转发等价类分配的标签。 参照图 11, FEC TVL为标签类型和根节点 IP地址, 即图中 Type=MP2MP down表示该 标签为 MP2MP下行标签, 该 MP2MP树的根节点 IP地址为 192.168.0.1, Label表示分配的隧道标签, 图中给 PE1分配的下行隧道标签为 L2给 PE2 分配的下行隧道标签为 L1,给 PE3分配分配的下行隧道标签为 L3。
图 13为 MP2MP隧道建立过程中上行标签隧道下发示意图, 如图 13 所示, 各 PE 设备发布上行隧道标签过程如下: PE1 设备为从网络侧接收 BUM报文, 分配一个上行隧道标签, 例如 L4, 通过 LDP Mapping 消息通 知给 P设备, P设备保存从 PE1设备接收到的上行标签信息, 并为 PE2设 备和 PE3设备各分配一个上行隧道标签, 例如为 PE2设备分配上行隧道标 签 L5,为 PE3设备行隧道标签 L6,通过 LDP mapping 消息分别通知给 PE2 设备和 PE3设备。
经过如上处理过程, 就建立了以 PE1为根的完整的 MP2MP隧道, 也 称为多点到多点标签交换路径 (MP2MP LSP) 0 VPLS 业务向网络侧转发 BUM流量就可以利用 MP2MP隧道了。 对于每个 PE设备需要维护两个隧 道标签, 以 PE2设备为例, 当 PE2设备作为入口 PE设备, 接收网络侧的 BUM报文, 并转发给 PE1和 PE3时, 使用的上行隧道标签 L5 , 当 PE2设 备作为出口 PE设备,接收 P设备转发的始发自 PE1设备或 PE3设备的 BUM 报文时, 接收到的报文采用的都是下行隧道标签 Ll。
在 MP2MP隧道建立完成后, 各 PE设备还需要向标签管理设备申请设 备标签, 具体可参照实施例四中的描述, 这里不再赘述, 本实施例中假设 PE1设备申请到的设备标签为 L7, PE2设备申请到的设备标签为 L8, PE3 设备申请到的设备标签为 L3。 当然上述设备标签也可以静态配置, 不需要 PE设备申请。
在 MP2MP隧道标签和设备标签都分配好后,就可以使用该 MP2MP隧
道转发 BUM流量了。
图 14为本发明报文处理方法实施例四的流程图, 图 15为 VPLS使用 MP2MP隧道转发 BUM流量的示意图, 参照图 14和图 15, 实施例中报文 流量始发自 PE1 , 因此 PE1作为入口设备, PE2设备和 PE3设备都作为出 口设备。 本实施例提供的方法包括以下歩骤:
歩骤 401、 PE1设备接收网络侧发送的 BUM报文。
PE1设备接收到的 BUM报文中包含源 MAC地址。
歩骤 402、 PE1设备将隧道标签 L3 , 设备标签 L7以及 VPLS标签封装 在 BUM报文中, 并将封装后的报文发送给 P设备。
本实施例中, 报文封装格式可参照图 16, 图 16为本发明中在各 PE之 间转发的 BUM报文的封装格式,如图 16所示, BUM报文包括: MP2MP Tree Label, VPLS Label、 PE Label、 C-Eth Header, Payload, 各字段解释如表一 所示
其中, C-Eth Header中包含 BUM报文的源 MAC地址和目的 MAC地 址, 以及以太网承载的上层数据类型, VPLS标签标示一个 VPLS, 和现有 技术的 BUM报文相比, 本实施中的报文多了一层 PE Label, PE Label为入 口 PE设备的设备标签。 具体的, PE1将设备标签封装 L7为最内层标签, 即封装在 MP2MP隧道标签和 VPLS标签的内层。 如图 14所示, 图中箭头 指示的方向, 是报文的流向, PE1 将隧道标签 L3 封装在最外层, 然后是 VPLS标签, 将设备标签 L7封装为最内层标签。
歩骤 403、 P设备接收到 PE1发送的 BUM报文后, 弹出隧道标签 L3 , 将报文复制两份, 一份封装隧道标签 L1 , 另一份封装隧道标签 L2。
P设备接收到 PE1发送的报文后,弹出最外层的标签, 即 MP2MP隧道
标签, 并将报文复制两份, 重新封装隧道标签, 并不解析 VPLS 标签和设 备标签, 因此, PE1设备的设备标签 L7还携带在复制后的报文中。
歩骤 404、 P设备将封装隧道标签 L1的报文发送给 PE2, 将封装隧道 标签 L2的报文发送给 PE3设备。
P设备将重新封装后的报文,按照各自的隧道标签,分别发送至对应的 PE设备。
歩骤 405、 PE1设备和 PE2设备接收 P设备发送的 BUM报文, 根据 BUM报文中包含的设备标签 L7, 确定 BUM报文源自 PE1设备。
PE1设备和 PE2设备分别接收 P设备发送的 BUM报文, BUM报文中 包含隧道标签、 VPLS标签、 入口 PE设备的设备标签以及 BUM报文的源 MAC地址。 例如, PE2设备根据报文中携带的设备标签 L7, 并根据自身存 储的 PE1设备和设备标签的对应关系确定该 BUM报文源自 PE1设备。
以 PE2设备为例, 在确定 BUM报文源自 PE1设备后, 根据 VPLS标 签确定 PE1设备和 PE2设备之间的承载该 VPLS业务时所使用的 PW, 例 如 MP2MP树承载两个 VPLS, 分别为用 VPLSA和 VPLSB表示, PE1和 PE2之间转发 VPLSA的报文时使用的 PW的标识为 100, 转发 VPLSB报 文时使用的 PW标识为 200, PE2根据报文中携带的 VPLS标签, 确定报文 属于 VPLSA还是 VPLSB, 进而确定所使用的 PW, 建立 BUM报文的源 MAC与该 PW之间的对应关系, 完成远端站点的 MAC地址的学习。
图 17为 VPLS使用 MP2MP隧道转发 BUM流量的示意图,如图 17所 示, BUM报文始发自 PE3设备, 贝 lj PE3设备作为入口设备, PE1设备和 PE2设备作为出口设备, PE3接收到网络侧发送的 BUM报文后, 将隧道标 签 L6、 VPLS标签和设备标签 L9封装在报文中, 发送给 P设备, P设备接 收到报文后, 弹出隧道标签 L6, 将报文复制两份, 一份报文中封装隧道标 签 L1 , 并发送给 PE2设备, 另一份报文中封装隧道标签 L4, 发送给 PE1 设备。 PE1和 PE3在接收到 BUM报文后, 根据报文中携带的设备标签 L9 确定该报文源自 PE3设备。
比较图 15和图 17可知, PE2接收到的 BUM报文隧道标签都是 L1 , 但是始发自 PE1设备和 PE3设备的 BUM报文中携带的设备标签不同, PE2 设备根据该设备标签能够确定 BUM报文源自那个 PE设备。并在确定 BUM 报文源自入口 PE设备之后,根据 VPLS标签确定与入口 PE设备之间的 PW,
建立源 MAC地址与 PW之间的对应关系。
本实施例提供的方法, 入口 PE设备在接收到网络侧发送的 BUM报文 后, 将设备标签也封装在报文中, 发送给出口 PE设备, 从而使得出口 PE 设备根据报文中携带的设备标签, 确定该 BUM报文源自入口 PE设备, 并 根据 VPLS标签确定出口 PE设备与入口 PE设备之间的 PW, 建立源 MAC 地址与 PW之间的对应关系, 完成对远端站点的 MAC地址的学习。
图 18为本发明出口 PE设备实施例五的流程图, 如图 18所示, 本实施 例提供的设备包括: 报文接收模块 51和入口 PE设备确定模块 52。
其中,报文接收模块 51,用于接收入口 PE设备通过多点到多点 MP2MP 隧道发送的广播、未知单播、 组播 BUM报文, BUM报文中包含隧道标签、 以及入口 PE设备的设备标签, 其中, 隧道标签为 MP2MP隧道的标签; 入口 PE设备确定模块 52, 用于根据入口 PE设备的设备标签, 确定 BUM报文源自入口 PE设备。
在一种实现方式中, 入口 PE设备确定模块 52具体用于, 根据入口 PE 设备的设备标签以及预先配置的 PE设备的设备标签与 PE设备之间的对应 关系, 确定 BUM报文源自入口 PE设备。 在这种方式中, 各 PE设备标签 预先配置好, 入口 PE设备的设备标签和入口 PE设备之间的对应关系可以 预先配置,在初始组网时为网络中的每个 PE设备上都静态配置一个设备标 签, 该网络中每个 PE设备都保存各个 PE所使用的设备标签, 组成设备标 签与 PE设备的对应关系表,每个 PE设备上保存的对应关系表都是相同的。 入口 PE设备确定模块 52,根据入口 PE设备的设备标签以及预先配置的 PE 设备的设备标签与 PE设备之间的对应关系, 确定 BUM报文源自入口 PE 设备。
本实施例中, BUM报文中还包含 BUM报文的源 MAC地址以及 VPLS 标签, 该出口 PE设备还可以包括 MAC地址学习模块, 用于在入口 PE设 备确定模块 52确定 BUM报文源自入口 PE设备后,根据 VPLS标签确定出 口 PE设备与入口 PE设备之间的 PW,建立源 MAC地址与 PW之间的对应 关系。 从而完成了对远端站点 MAC地址的学习, 建立出口 PE设备与入口 PE设备之间点到点的连接,通过出口 PE设备和入口 PE设备之间的 PW连 接通信。
本实施例提供的方法可用于执行方法实施例一提供的方案, 具体实现
方式和技术效果类型, 这里不再赘述。
图 19为本发明出口 PE设备实施例六的流程图, 如图 19所示, 本实施 例提供的设备包括: 报文接收模块 61、 入口 PE设备确定模块 62、 设备标 签接收模块 63以及 MAC地址学习模块 64。
其中,报文接收模块 61,用于接收入口 PE设备通过 MP2MP隧道发送 的广播、 未知单播、 组播 BUM报文, BUM报文中包含隧道标签以及入口 PE设备的设备标签。
入口 PE设备确定模块 62, 用于根据入口 PE设备的设备标签, 确定 BUM报文源自入口 PE设备。
设备标签接收模块 63, 用于接收标签管理设备发送的入口 PE设备的 设备标签与入口 PE设备之间的对应关系。
本实施例中, BUM报文中还包含 BUM报文的源 MAC地址以及 VPLS 标签, MAC地址学习模块 64, 用于根据 VPLS标签确定出口 PE设备与入 口 PE设备之间的伪线 PW, 建立源 MAC地址与 PW之间的对应关系。
入口 PE设备确定模块具体用于, 根据所述入口 PE设备的设备标签和 所述对应关系, 确定所述 BUM报文源自所述入口 PE设备。
本实施例中, 入口 PE设备的设备标签和入口 PE设备之间的对应关系 动态配置, 入口 PE设备确定模块 62根据入口 PE设备的设备标签, 确定 BUM报文源自入口 PE设备之前,设备标签接收模块 63接收标签管理设备 发送的入口 PE设备的设备标签与入口 PE设备之间的对应关系,则入口 PE 设备确定模块 62具体用于, 根据入口 PE设备的设备标签和对应关系, 确 定 BUM报文源自入口 PE设备。 在入口 PE设备确定模块 62确定 BUM报 文源自入口 PE设备之后, MAC地址学习模块 64根据报文中携带的 VPLS 标签,确定入口 PE设备和出口 PE设备之间的 PW,建立源 MAC地址和该 PW之间的映射关系, 从而完成了对远端站点 MAC地址的学习, 建立出口 PE设备与入口 PE设备之间点到点的连接, 通过出口 PE设备和入口 PE设 备之间的 PW连接通信。
在这种方式中, 由标签管理设备统一管理设备标签, 每一个 PE设备在 使用设备标签之前都向标签管理设备申请设备标签, 标签管理设备除了将 该设备标签发送给申请的 PE设备外, 还向与该 PE设备具有报文转发关系 的其它 PE设备发送该 PE设备与设备标签之间的对应关系。这样, 每个 PE
设备上都会保存有该 PE设备与设备标签之间的对应关系,从而使得出口设 备根据该设备标签, 以及 PE设备与设备标签之间的对应关系确定该 BUM 报文源自入口 PE设备。
本实施例提供的出口 PE设备,可用于执行方法实施例一和实施例四提 供的技术方案, 具体实现方式和技术效果类型, 这里不再赘述。
图 20为本发明入口 PE设备实施例七的流程图, 如图 20所示, 本实施 例提供的设备包括:报文接收模块 71、报文封装模块 72、报文发送模块 73。
其中, 报文接收模块 71, 用于接收用户边缘 CE设备发送的广播、 未 知单播、 组播 BUM报文;
报文封装模块 72, 用于将隧道标签、 入口 PE设备的设备标签以及虚 拟专用局域网业务 VPLS标签封装在 BUM报文中;
封装后的报文中包括隧道标签、入口 PE设备的设备标签以及 VPLS标 签, 还包括该 BUM报文的源 MAC地址等信息, 其中, 隧道标签为多点到 多点 MP2MP的隧道标签。
报文发送模块 73,用于通过 MP2MP隧道向出口 PE设备发送封装后的 BUM报文, 以使出口 PE设备根据入口 PE设备的设备标签, 确定 BUM报 文源自入口 PE设备。
本实施例的一个前提是, 入口 PE设备需要预先获取自身的设备标签, 一种实现方式中, 各 PE设备的设备标签预先配置, 各 PE设备上都保存有 一个 PE设备标签与设备的对应关系表, 各 PE设备上保存的对应关系表都 相同。 因此, 报文封装模块 72具体用于, 将隧道标签、预先配置的入口 PE 设备的设备标签以及 VPLS标签封装在 BUM报文中。 另一种实现方式中, 入口 PE设备需要在报文封装模块封装报文之前, 向标签管理设备申请一个 设备标签, 因此, 入口 PE设备还包括: 设备标签获取模块, 用于向标签管 理设备申请获取入口 PE设备的设备标签。
本实施例提供的入口 PE 设备可用于执行方法实施例二和实施例四提 供的技术方案, 具体实现方式和技术效果类似, 这里不再赘述。
图 21为本发明标签管理设备实施例八的结构示意图, 如图 21所示, 本实施例提供的设备包括: 接收模块 81、 设备标签分配模块 82、 发送模块 83。
接收模块 81, 用于接收第一提供商边缘 PE设备发送的设备标签分配
请求消息;
设备标签分配模块 82, 用于根据设备标签分配请求消息, 为第一 PE 设备分配设备标签;
发送模块 83, 用于向第一 PE设备发送分配好的设备标签, 并向与第 一 PE设备具有报文转发关系的其它 PE设备发送第一 PE设备与设备标签 之间的对应关系。
各 PE设备在网络建立好后,都可以向标签管理设备发送标签分配请求 消息, 用于请求分配一个设备标签, 标签管理设备的接收模块 81接收第一 PE设备发送的设备标签分配请求消息, 由设备标签分配模块 82根据设备 标签分配请求消息, 为第一 PE设备分配设备标签, 并通过发送模块 83将 分配好的设备标签发送给发起申请的第一 PE设备, 同时向网络中其他 PE 设备都发送该第一 PE设备与设备标签之间的对应关系, 以使其他 PE设备 在接收到该第一 PE设备发送来的 BUM报文时, 根据保存的 PE设备与设 备标签之间的对应关系确定该报文源自该第一 PE设备。
本实施例提供的设备, 可用于执行方式实施例三提供的技术方案, 具 体实现方式和技术效果类似, 这里不再赘述。
本实施例中, 标签管理设备可以为提供商边缘 PE设备、 路由反射器或 者、 集中控制器。 具体来说, 在现有网络架构下, 可以由一***立部署的 路由反射器来扮演, 或者是由一台兼做路由反射器的 PE 设备来扮演。 在 SDN (网络架构下, Label Manager可以由 SDN网络的集中控制器来扮演。
图 22为本发明出口 PE设备实施例九的结构示意图, 本实施例提供的 出口 PE设备 900包括: 处理器 91、 存储器 92、 发射器 93和接收器 94。 存储器 92、发射器 93以及接收器 94可以和处理器 91通过总线相连。其中, 存储器 92存储执行指令, 当出口 PE设备 900运行时, 处理器 91与存储器 92之间通信, 处理器 91执行执行指令使得出口 PE设备 900执行本发明提 供的报文处理方法。 本实施例中, 处理器 91用于执行以下操作:
接收器 94,用于接收入口 PE设备通过多点到多点 MP2MP隧道发送的 广播、 未知单播、 组播 BUM报文, BUM报文中包含隧道标签以及入口 PE 设备的设备标签, 其中, 隧道标签为 MP2MP隧道的标签;
处理器 91, 用于根据入口 PE设备的设备标签, 确定 BUM报文源自入 口 PE设备。
接收器 94接收入口 PE设备通过 MP2MP隧道发送的 BUM报文之前, 还用于接收标签管理设备发送的入口 PE设备的设备标签与入口 PE设备之 间的对应关系; 并将该对应关系存储在存储器 92中, 则处理器 91具体用 于根据入口 PE设备的设备标签和入口 PE设备的设备标签与入口 PE设备 之间的对应关系, 确定 BUM报文源自入口 PE设备。
本实施例中, PE设备的设备标签与 PE设备之间的对应关系还可以预 先配置, 存储在存储器 92中, 则处理器 91具体用于根据入口 PE设备的设 备标签以及预先配置的 PE设备的设备标签与 PE设备之间的对应关系, 确 定 BUM报文源自入口 PE设备。
BUM报文中还包括源 MAC地址以及 VPLS标签,处理器 91确定 BUM 报文源自入口 PE设备之后, 还用于根据 VPLS标签确定与入口 PE设备之 间的伪线 PW, 建立源 MAC地址与 PW之间的对应关系, 即完成对远端 MAC地址的学习。
本实施例提供的方法, 可以用于执行上述方法实施例, 具体实现方式 和技术效果类似, 这里不再赘述。
图 23为本发明入口 PE设备实施例十的结构示意图, 如图 23所示, 本 实施例提供的入口 PE设备 100包括: 处理器 11、 存储器 12、 发射器 13和 接收器 14,发射器 13和接收器 14以及存储器 12都可以通过总线与处理器 11相连。 其中, 存储器 11存储执行指令, 当入口 PE设备运行时, 处理器 11与存储器 12之间通信,处理器 11执行所述执行指令使得入口 PE设备执 行本发明实施例提供的报文处理方法。
接收器 14, 用于接收用户边缘 CE设备发送的广播、 未知单播、 组播 BUM报文;
处理器 11, 用于根据接收器 14接收到的 BUM报文, 将隧道标签、 入 口 PE设备的设备标签以及虚拟专用局域网业务 VPLS标签封装在 BUM报 文中, 其中, 隧道标签为多点到多点 MP2MP隧道的标签;
发射器 13, 用于通过 MP2MP隧道向出口 PE设备发送处理器 11封装 后的 BUM报文,以使出口 PE设备根据入口 PE设备的设备标签,确定 BUM 报文源自入口 PE设备。
处理器 11还用于在将隧道标签、 入口 PE设备的设备标签以及 VPLS 标签封装在 BUM报文中之前, 向标签管理设备申请获取入口 PE设备的设
备标签, 并将设备标签存储在存储器 12中。
在一种实现方式中, 处理器 92不需要向标签管理设备申请获取设备标 签, 设备标签预先配置, 则处理器 92具体用于将隧道标签、 预先配置的入 口 PE设备的设备标签以及 VPLS标签封装在 BUM报文中。
本实施例提供的入口 PE设备,可用于执行上述方法实施例提供的技术 方案, 具体实现方式和技术效果类似, 这里不再赘述。
图 24为本发明标签管理设备实施例 ^一的结构示意图, 如图 24所示, 本实施例提供的标签管理设备 1100包括: 处理器 110、 存储器 120、 发射 器 130和接收器 140,发射器 130和接收器 140以及存储器 120都可以通过 总线与处理器 110相连。 其中, 存储器 120存储执行指令, 当标签管理设 备运行时, 处理器 110与存储器 120之间通信, 处理器 110执行所述执行 指令使得标签管理设备 1100执行本发明实施例提供的设备标签处理方法。
接收器 140, 用于接收第一提供商边缘 PE设备发送的设备标签分配请 求消息;
处理器 110, 用于根据所述设备标签分配请求消息, 为第一 PE设备分 配设备标签;
发射器 120, 用于向第一 PE设备发送分配好的设备标签, 并向与第一 PE设备具有报文转发关系的其它 PE设备发送第一 PE设备与所述设备标签 之间的对应关系。
本实施例中, 标签管理设备为提供商边缘 PE设备、 路由反射器或者、 集中控制器。
各 PE设备在网络建立好后,都可以向标签管理设备发送标签分配请求 消息, 用于请求分配一个设备标签, 标签管理设备的接收器 140接收第一 PE设备发送的设备标签分配请求消息, 由处理器 110根据设备标签分配请 求消息, 为第一 PE设备分配设备标签, 并通过发射器 130将分配好的设备 标签发送给发起申请的第一 PE设备, 同时向网络中其他 PE设备都发送该 第一 PE设备与设备标签之间的对应关系, 以使其他 PE设备在接收到该第 一 PE设备发送来的 BUM报文时, 根据保存的 PE设备与设备标签之间的 对应关系确定该报文源自该第一 PE设备。
本领域普通技术人员可以理解: 实现上述各方法实施例的全部或部分 歩骤可以通过程序指令相关的硬件来完成。 前述的程序可以存储于一计算
机可读取存储介质中。 该程序在执行时, 执行包括上述各方法实施例的歩 骤; 而前述的存储介质包括: ROM、 RAM, 磁碟或者光盘等各种可以存储 程序代码的介质。
最后应说明的是: 以上各实施例仅用以说明本发明的技术方案, 而非 对其限制; 尽管参照前述各实施例对本发明进行了详细的说明, 本领域的 普通技术人员应当理解: 其依然可以对前述各实施例所记载的技术方案进 行修改, 或者对其中部分或者全部技术特征进行等同替换; 而这些修改或 者替换, 并不使相应技术方案的本质脱离本发明各实施例技术方案的范围。
Claims
1、 一种报文处理方法, 其特征在于, 包括:
出口提供商边缘 PE设备接收入口 PE设备通过多点到多点 MP2MP隧 道发送的广播、 未知单播、 组播 BUM报文, 所述 BUM报文中包含隧道标 签以及所述入口 PE设备的设备标签, 其中, 所述隧道标签为所述 MP2MP 隧道的标签;
所述出口 PE设备根据所述入口 PE设备的设备标签, 确定所述 BUM 报文源自所述入口 PE设备。
2、 根据权利要求 1所述的方法, 其特征在于, 所述出口 PE设备接收 入口 PE设备通过 MP2MP隧道发送的 BUM报文之前, 还包括:
所述出口 PE设备接收标签管理设备发送的所述入口 PE设备的设备标 签与所述入口 PE设备之间的对应关系;
所述出口 PE设备根据所述入口 PE设备的设备标签, 确定所述 BUM 报文源自所述入口 PE设备, 包括:
所述出口 PE设备根据所述入口 PE设备的设备标签和所述对应关系, 确定所述 BUM报文源自所述入口 PE设备。
3、 根据权利要求 1所述的方法, 其特征在于, 所述出口 PE设备根据 所述入口 PE设备的设备标签,确定所述 BUM报文源自所述入口 PE设备, 包括:
所述出口 PE设备根据所述入口 PE设备的设备标签以及预先配置的 PE 设备的设备标签与 PE设备之间的对应关系, 确定所述 BUM报文源自所述 入口 PE设备。
4、 根据权利要求 1~3 中任一项所述的方法, 其特征在于, 所述 BUM 报文中还包含所述 BUM报文的源媒体接入控制 MAC地址以及虚拟专用局 域网业务 VPLS标签,所述确定所述 BUM报文源自所述入口 PE设备之后, 还包括:
所述出口 PE设备根据所述 VPLS标签确定与所述入口 PE设备之间的 伪线 PW, 建立所述源 MAC地址与所述 PW之间的对应关系。
5、 一种报文处理方法, 其特征在于, 包括:
入口提供商边缘 PE设备接收用户边缘 CE设备发送的广播、未知单播、
组播 BUM报文;
所述入口 PE设备将隧道标签、 所述入口 PE设备的设备标签以及虚拟 专用局域网业务 VPLS标签封装在所述 BUM报文中, 其中, 所述隧道标签 为多点到多点 MP2MP隧道的标签;
所述入口 PE设备通过所述 MP2MP隧道向出口 PE设备发送封装后的 BUM报文, 以使所述出口 PE设备根据所述入口 PE设备的设备标签,确定 所述 BUM报文源自所述入口 PE设备。
6、 根据权利要求 5所述的方法, 其特征在于, 所述入口 PE设备将隧 道标签、 所述入口 PE设备的设备标签以及 VPLS标签封装在所述 BUM报 文中之前, 还包括:
所述入口 PE设备向标签管理设备申请获取所述入口 PE设备的设备标 签。
7、 根据权利要求 5所述的方法, 其特征在于, 所述入口 PE设备将隧 道标签、 所述入口 PE设备的设备标签封装在所述 BUM报文中, 包括: 所述入口 PE设备将所述隧道标签、 预先配置的所述入口 PE设备的设 备标签以及 VPLS标签封装在所述 BUM报文中。
8、 一种设备标签处理方法, 其特征在于, 包括:
标签管理设备接收第一提供商边缘 PE 设备发送的设备标签分配请求 消息;
所述标签管理设备根据所述设备标签分配请求消息,为所述第一 PE设 备分配设备标签;
所述标签管理设备向所述第一 PE设备发送分配好的设备标签,并向与 所述第一 PE设备具有报文转发关系的其它 PE设备发送所述第一 PE设备 与所述设备标签之间的对应关系。
9、 一种出口提供商边缘 PE设备, 其特征在于, 包括:
报文接收模块, 用于接收入口提供商边缘 PE 设备通过多点到多点 MP2MP隧道发送的广播、 未知单播、 组播 BUM报文, 所述 BUM报文中 包含隧道标签以及所述入口 PE设备的设备标签, 其中, 所述隧道标签为所 述 MP2MP隧道的标签;
入口 PE设备确定模块, 用于根据所述入口 PE设备的设备标签, 确定 所述 BUM报文源自所述入口 PE设备。
10、 根据权利要求 9所述的设备, 其特征在于, 还包括: 设备标签接收模块,用于接收标签管理设备发送的所述入口 PE设备的 设备标签与所述入口 PE设备之间的对应关系;
所述入口 PE设备确定模块具体用于, 根据所述入口 PE设备的设备标 签和所述对应关系, 确定所述 BUM报文源自所述入口 PE设备。
11、 根据权利要求 9所述的设备, 其特征在于, 所述入口 PE设备确定 模块具体用于, 根据所述入口 PE设备的设备标签以及预先配置的 PE设备 的设备标签与 PE设备之间的对应关系, 确定所述 BUM报文源自所述入口 PE设备。
12、 根据权利要求 9-11 中任一所述的设备, 其特征在于, 所述 BUM 报文中还包含所述 BUM报文的源媒体接入控制 MAC地址以及虚拟专用局 域网业务 VPLS标签, 所述设备还包括:
MAC地址学习模块, 用于根据所述 VPLS标签确定所述出口 PE设备 与所述入口 PE设备之间的伪线 PW, 建立所述源 MAC地址与所述 PW之 间的对应关系。
13、 一种入口提供商边缘 PE设备, 其特征在于, 包括:
报文接收模块, 用于接收用户边缘 CE设备发送的广播、 未知单播、 组 播 BUM报文;
报文封装模块, 用于将隧道标签、所述入口 PE设备的设备标签以及虚 拟专用局域网业务 VPLS标签封装在所述 BUM报文中, 其中, 所述隧道标 签为多点到多点 MP2MP隧道的标签;
报文发送模块, 用于通过所述 MP2MP隧道向出口 PE设备发送封装后 的 BUM报文, 以使所述出口 PE设备根据所述入口 PE设备的设备标签, 确定所述 BUM报文源自所述入口 PE设备。
14、 根据权利要求 13所述的设备, 其特征在于, 还包括:
设备标签获取模块,用于向标签管理设备申请获取所述入口 PE设备的 设备标签。
15、 根据权利要求 13所述的设备, 其特征在于, 所述报文封装模块具 体用于, 将所述隧道标签、 预先配置的所述入口 PE 设备的设备标签以及 VPLS标签封装在所述 BUM报文中。
16、 一种标签管理设备, 其特征在于, 包括:
接收模块,用于接收第一提供商边缘 PE设备发送的设备标签分配请求 消息;
设备标签分配模块, 用于根据所述设备标签分配请求消息, 为所述第 一 PE设备分配设备标签;
发送模块, 用于向所述第一 PE设备发送分配好的设备标签, 并向与所 述第一 PE设备具有报文转发关系的其它 PE设备发送所述第一 PE设备与 所述设备标签之间的对应关系。
17、 根据权利要求 16所述的设备, 其特征在于, 所述设备为提供商边 缘 PE设备、 路由反射器或者集中控制器。
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201310216416.2 | 2013-06-03 | ||
CN201310216416.2A CN103312611B (zh) | 2013-06-03 | 2013-06-03 | 报文处理方法、设备标签处理方法及设备 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2014194711A1 true WO2014194711A1 (zh) | 2014-12-11 |
Family
ID=49137410
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2014/074573 WO2014194711A1 (zh) | 2013-06-03 | 2014-04-01 | 报文处理方法、设备标签处理方法及设备 |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN103312611B (zh) |
WO (1) | WO2014194711A1 (zh) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP3389234A4 (en) * | 2015-12-30 | 2018-12-05 | Huawei Technologies Co., Ltd. | Label management method, and method and device for processing data stream |
CN114430393A (zh) * | 2020-10-16 | 2022-05-03 | 华为技术有限公司 | 报文处理方法、装置及存储介质 |
Families Citing this family (12)
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 (zh) * | 2013-11-29 | 2015-06-04 | 华为技术有限公司 | 一种消息处理的方法、设备及*** |
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 (ja) * | 2016-09-09 | 2018-03-15 | 日本電気株式会社 | 通信システム、エッジノード、通信方法及びプログラム |
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)
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 | 华为技术有限公司 | 报文处理方法、设备标签处理方法及设备 |
-
2013
- 2013-06-03 CN CN201310216416.2A patent/CN103312611B/zh active Active
-
2014
- 2014-04-01 WO PCT/CN2014/074573 patent/WO2014194711A1/zh active Application Filing
Patent Citations (4)
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)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP3389234A4 (en) * | 2015-12-30 | 2018-12-05 | Huawei Technologies Co., Ltd. | Label management method, and method and device for processing data stream |
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 (en) * | 2015-12-30 | 2023-10-04 | Huawei Technologies Co., Ltd. | Label management method and device for processing data stream |
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 (zh) | 报文处理方法、设备标签处理方法及设备 | |
CN109218178B (zh) | 一种报文处理方法及网络设备 | |
US10484203B2 (en) | Method for implementing communication between NVO3 network and MPLS network, and apparatus | |
WO2020029976A1 (zh) | Vpn跨域的实现方法、装置和边界节点 | |
US8861547B2 (en) | Method, apparatus, and system for packet transmission | |
EP2945330B1 (en) | Route management method, route method, network controller and router | |
US8693323B1 (en) | System and method for managing communications in an access network | |
WO2017162095A1 (zh) | 基于流规则协议的通信方法、设备和*** | |
WO2019128621A1 (zh) | 一种组播虚拟专用网络的承载方法和设备 | |
WO2015165311A1 (zh) | 传输数据报文的方法和供应商边缘设备 | |
WO2008092357A1 (fr) | Procédé et dispositif pour établir un tunnel pseudocâblé et transmettre un message à l'aide de celui-ci | |
WO2015192501A1 (zh) | 地址信息的发布方法及装置 | |
EP2634975A1 (en) | Method and device for sending message | |
WO2014194749A1 (zh) | 边缘设备的vpn实现处理方法及装置 | |
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 (en) | Method and device used in ethernet virtual private network | |
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 (zh) | 一种标签管理方法,数据流处理方法及设备 | |
WO2013139270A1 (zh) | 实现三层虚拟专用网络的方法、设备及*** | |
CN113132235B (zh) | 基于虚电路的数据报文处理方法、转发表项的构建方法 | |
WO2013182061A1 (zh) | 一种网络标签分配方法、设备与*** | |
WO2009135392A1 (zh) | 一种信令控制的方法、***及设备 | |
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 |