WO2018149294A1 - 一种分组网络中处理业务流的方法及装置 - Google Patents

一种分组网络中处理业务流的方法及装置 Download PDF

Info

Publication number
WO2018149294A1
WO2018149294A1 PCT/CN2018/074799 CN2018074799W WO2018149294A1 WO 2018149294 A1 WO2018149294 A1 WO 2018149294A1 CN 2018074799 W CN2018074799 W CN 2018074799W WO 2018149294 A1 WO2018149294 A1 WO 2018149294A1
Authority
WO
WIPO (PCT)
Prior art keywords
service flow
uplink
data packet
downlink
network device
Prior art date
Application number
PCT/CN2018/074799
Other languages
English (en)
French (fr)
Inventor
江元龙
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP21208706.8A priority Critical patent/EP4054155A1/en
Priority to EP18754372.3A priority patent/EP3573288B1/en
Publication of WO2018149294A1 publication Critical patent/WO2018149294A1/zh
Priority to US16/545,218 priority patent/US11201826B2/en
Priority to US17/528,555 priority patent/US11909659B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/34—Flow control; Congestion control ensuring sequence integrity, e.g. using sequence numbers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/28—Routing or path finding of packets in data switching networks using route fault recovery
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/50—Routing or path finding of packets in data switching networks using label swapping, e.g. multi-protocol label switch [MPLS]

Definitions

  • the present application relates to the field of communications, and in particular, to a method and apparatus for processing a service flow in a packet network.
  • a Multi-Protocol Label Switching (MPLS) network uses a fast reroute (FRR) to locally protect a link or a node by a label switching path (LSP), or by establishing a pair.
  • FRR fast reroute
  • LSP label switching path
  • PW pseudowires
  • CE1 is dual-homed to PE1 and PE2. That is, CE1 is connected to PE1 through AC1, and CE1 is connected to PE2 through AC2.
  • PE1 and PE2 are connected through a direct PW, such as D-PW1.
  • CE2 is dual-homed to PE3 and PE4, that is, CE2 is connected to PE3 through AC3, and CE2 is connected to PE4 through AC4.
  • PE3 and PE4 are connected through a direct PW, such as D-PW2.
  • AC1, AC2, AC3, and AC4 are access circuit (AC) in the MPLS network.
  • the PE1 When the service data flows from the PE1 to the CE1, the PE1 receives the service data through the PW1 connected to the PE3. PE1 will copy the business data to obtain two business data. PE1 sends one of the two service data to CE1 through AC1. PE1 forwards another service data of the two service data to PE2 through D-PW1. PE2 sends the service data received through D-PW1 to CE1 through AC2. CE1 detects faults on AC1. When AC1 is normal, CE1 receives service data from AC1. When AC1 fails, CE1 receives service data from AC2.
  • CE1 sends two redundant service data to PE1 and PE2. That is, CE1 sends a service data to PE1 through AC1, and CE1 sends another service data to PE2 through AC2.
  • PE2 After receiving the service data sent by CE1, PE2 sends the service data to PE1 through D-PW1.
  • PE1 detects faults on AC1. When AC1 is normal, PE1 receives service data from AC1. When AC1 fails, PE1 receives service data from D-PW1. Then, PW1 sends service data to PE3.
  • the PE1 and the CE1 need to detect the faults of the connected AC1, and switch the service data receiving mode according to the fault detection result.
  • the forwarding efficiency is low and the fault point needs to be located.
  • the reliability of the service forwarding needs to be further improved. .
  • the embodiment of the present invention provides a method and an apparatus for processing a service flow in a packet network, which helps simplify fault detection and handover operations, and improves forwarding efficiency.
  • a method for processing a service flow in a packet network is provided, the method being applied to a network device group, the network device group comprising a first network device and a second network device, the first network device and The second network device is connected, the first network device is in communication with the third network device, and the second network device is in communication with the fourth network device, the method includes: the first network device obtaining the first uplink service Flow, the first uplink service flow includes at least one uplink data packet, and each uplink data packet in the first uplink service flow includes a sequence number, and each uplink data packet in the first uplink service flow The sequence number included in the file is used to identify the sequence of the uplink data packet in which the uplink data packet is located in the first uplink service flow, and the first uplink service flow is received by the first network device from the third network.
  • the flow is an uplink service flow received by the second network device from the fourth network device, or a service flow obtained by the second network device replicating an uplink service flow from the fourth network device
  • the first network device acquires a third uplink service flow according to the first reference sequence number and the sequence number included in each uplink data packet of the received N uplink service flows, where the third uplink service flow includes at least An uplink data packet, where the N uplink service flows include the first uplink service flow
  • the N is an integer greater than or equal to 2.
  • the first network device and the second network device use the method of copying the service flow, selecting the service flow according to the serial number, and transmitting, and performing high reliability on the service flow transmitted by the third network device and the fifth network device in the packet network.
  • the device of the first network device, the second network device, the third network device, and the fifth network device does not need to perform the cooperation of the fault detection and the switching action, so that the service is avoided in the network.
  • a single point of failure is even the impact of a particular multipoint failure.
  • the above method avoids the complexity of the protocol based on the traditional automatic protection switching technology, and is easier to implement on the network device, thereby improving the scalability of the MPLS network.
  • the method further includes: the first network device receiving an uplink service flow from the third network device and replicating the uplink service flow from the third network device;
  • the network device sends, by using the first pseudowire, a fourth uplink service flow to the second network device, where the fourth uplink service flow is the uplink service flow from the third network device, or is from the The service flow obtained after the uplink service flow of the third network device is copied.
  • the first network device may improve the service reliability of the second network device side by copying the uplink service flow and sending the method to the second network device, thereby helping to avoid the fourth network device failure.
  • the interruption of the uplink service flow transmitted by the second network device is caused.
  • the method further includes: the first network device obtains a first downlink service flow, where the first downlink service flow includes at least one downlink data packet, where the first downlink service flow is Each downlink data packet includes a sequence number, and each downlink data packet in the first downlink service flow includes a sequence number for identifying that the downlink data packet in which the downlink data packet is located is in the first downlink service flow.
  • the first downlink service flow is a downlink service flow received by the first network device from the fifth network device, or is the first network device pair from the fifth network device.
  • the service flow obtained by the downlink service flow is copied; the first network device receives the second downlink service flow sent by the second network device by using the second pseudo line, and the second downlink service flow includes at least one downlink data. a packet, each downlink data packet in the second downlink service flow includes a sequence number, and each downlink data packet in the second downlink service flow includes a sequence number used to identify a downlink data packet In An order in the second downlink service flow, where the second downlink service flow is a downlink service flow received by the second network device from the sixth network device, or is the second network device pair from the The service flow obtained by the downlink service flow of the sixth network device is copied; the first network device obtains the first sequence according to the second reference sequence number and the sequence number included in each downlink data packet of the received M downlink service flows.
  • the third downlink service flow includes the first downlink service flow and the second downlink service flow, and the third downlink service flow includes at least one downlink data packet, and the third downlink Any downlink data packet in the service flow includes a sequence number greater than the second reference sequence number; the first network device sends the third downlink service flow to the third network device.
  • M is an integer greater than or equal to 2.
  • the uplink service flow and the downlink service flow of the first network device and the network device are respectively protected by two bidirectional pseudo lines, which helps to further improve the reliability of the service.
  • the method further includes: the first network device receiving a downlink service flow from the fifth network device, and replicating the downlink service flow from the fifth network device;
  • the network device sends, by using the second pseudowire, a fourth downlink service flow to the second network device, where the fourth downlink service flow is the downlink service flow from the fifth network device, or is from the The service flow obtained after the downlink service flow of the fifth network device is copied.
  • the first network device may improve the service reliability of the second network device side by copying the downlink service flow and sending the method to the second network device, thereby helping to avoid the second network.
  • the acquiring, by the first network device, the third uplink service flow according to the first reference sequence number and the sequence number included in each uplink data packet of the received N uplink service flows includes: The first network device selects a value of the sequence number according to the sequence number included in each uplink data packet in the first uplink service flow and the sequence number included in each uplink data packet in the second uplink service flow.
  • the ith uplink data packet is any uplink data packet in the third uplink service flow, where the The sequence number of the i-th uplink data packet is greater than the first reference sequence number, and the sequence number included in the (i+1)th uplink data packet is greater than the sequence number included in the ith uplink data packet, the ith The +1 uplink data packet is located after the ith uplink data packet in the third uplink service flow.
  • the first network device uses the first reference sequence number and the sequence number included in the uplink data packet to help prevent the same uplink data packet from being present in the third uplink service flow.
  • the uplink data packet and/or the same uplink data packet are repeatedly sent, which helps improve forwarding efficiency.
  • the first network device according to the first reference sequence number and the sequence number included in each uplink data packet of the received N uplink service flows, obtain the third uplink service flow, including The first network device is configured to the first uplink according to an arrival time of each uplink data packet in the first uplink service flow and an arrival time of each uplink data packet in the second uplink service flow.
  • the uplink data packet included in the service flow and the uplink data packet included in the second uplink service flow are sorted to obtain the sorted uplink service flow; and the first network device is in the sorted uplink service flow, And selecting, as the third uplink service flow, the sequence number of the i-th uplink data packet in the third uplink service flow is greater than the number of the uplink data packets of the first uplink sequence.
  • the acquiring, by the first network device, the third downlink service flow according to the second reference sequence number and the sequence number included in each downlink data packet of the received M downlink service flows includes: The first network device selects a sequence number according to a sequence number included in each downlink data packet in the first downlink service flow and a sequence number included in each downlink data packet in the second downlink service flow.
  • a plurality of downlink data packets having a value greater than the second reference sequence number, where the jth downlink data packet is any downlink data packet in the third downlink service flow,
  • the sequence number included in the jth downlink data packet is greater than the second reference sequence number
  • the sequence number included in the j+1th downlink data packet is greater than the sequence number included in the jth downlink data packet, where The j+1 downlink data packet is located after the jth downlink data packet in the third downlink service flow.
  • the first network device uses the second reference sequence number and the sequence number included in the downlink data packet to help prevent the same downlink data packet from being present in the third downlink service flow.
  • the downlink data packet is transmitted and/or the same downlink data packet is repeatedly sent, which helps improve forwarding efficiency.
  • the acquiring, by the first network device, the third downlink service flow according to the second reference sequence number and the sequence number included in each downlink data packet of the received M downlink service flows includes: The first network device is configured to: according to an arrival time of each downlink data packet in the first downlink service flow and an arrival time of each downlink data packet in the second downlink service flow, to the first The downlink data packet included in the line service flow and the downlink data packet included in the second downlink service flow are sorted to obtain the sorted downlink service flow; the first network device is in the sorted downlink service flow.
  • the sequence number of the jth downlink data packet in the third downlink service flow is greater than the multiple downlink data packet of the second downlink service flow.
  • the second reference sequence number, the arrival time of the j+1th downlink data packet in the third downlink service flow is later than the jth downlink data packet, and the j+1th downlink data packet includes
  • the serial number is greater than Said first sequence number j included in the downlink data packet, the j downlink data packet traffic flow in the third down any lower row of the data packet.
  • the method further includes: the first network device updating the value of the first reference sequence number by using a maximum value of a sequence number included in an uplink data packet in the third uplink service flow.
  • the first network device updates the first reference sequence number, which helps to avoid repeatedly sending the same uplink data packet (uplink data packet with the same sequence number), which helps improve forwarding efficiency and uplink.
  • the continuity of the business flow is the following method.
  • the method further includes: the first network device updating a value of the second reference sequence number by using a maximum value of a sequence number included in a downlink data packet in the third downlink service flow.
  • the first network device updates the second reference sequence number, which helps to avoid repeatedly sending the same downlink data packet (downlink data packet with the same sequence number), which helps improve forwarding efficiency and downlink.
  • the continuity of the business flow is the following method.
  • the first network device is a first PE device, the second network device is a second PE device, and the third network device is a CE device, and the fourth network device is The CE device; or the first network device is a PW switching point (SPE) in the first multi-hop pseudowire, the second network device is a second SPE, and the third network device is a a PE device, the fourth network device is a second PE device, and the first PE device and the second PE device communicate with the same CE device; or the first network device is a first SPE, the first The second network device is a second SPE, the third network device is a first PE device, and the fourth PE device is a second PE device, and the first PE device and the second PE device belong to a network device group.
  • SPE PW switching point
  • the first network device is a first SPE
  • the second network device is a second SPE
  • the third network device is a first PE device
  • the fourth network device is a second PE device
  • the first PE device and the second PE device belong to a network device group, A communication device and the second PE PE device to the same CE device.
  • the fifth network device and the sixth network device are the same PE device, or the fifth network device and the sixth network device are different PE devices, or The fifth network device and the sixth network device are different SPEs.
  • the first network device obtaining the first uplink service flow includes: the first network device receiving the An Ethernet frame of the third network device; the first network device obtains a sequence number according to the Ethernet frame; and the first network device obtains, according to the Ethernet frame and the sequence number, the first uplink service flow An uplink data packet, where the uplink data packet includes the Ethernet frame and the sequence number.
  • the obtaining, by the first network device, the sequence number according to the Ethernet frame includes: the first network device performing calculation on the received Ethernet frame to obtain the serial number. Or the first network device obtains the sequence number carried by the Ethernet frame from the Ethernet frame.
  • the obtaining, by the first network device, the uplink data packet included in the first uplink service flow according to the Ethernet frame and the sequence number includes: the first network device, the serial number may be encapsulated in the The outer layer of the Ethernet frame is obtained, and the uplink data packet is obtained.
  • the first network device may carry the sequence number in a context of the Ethernet frame to obtain the uplink data packet.
  • the method for obtaining the sequence number and the uplink data packet can ensure that the same sequence number of the uplink data packet carries the same value, which helps to avoid duplicate uplink data packets in the uplink service flow.
  • a second aspect provides a device for processing a service flow in a packet network, the device being disposed in a first network device in a network device group, the network device group further including a second network device, the first network device Connected to the second network device, the first network device and the third network device are in communication, the second network device is in communication with the fourth network device, the device comprising the first aspect or the first aspect A module of any possible implementation.
  • a third aspect provides a system for processing a service flow in a packet network, where the system includes the apparatus provided by the second aspect and the second network device, where the apparatus provided by the second aspect is disposed on the first network device, The first network device is connected to the second network device, the first network device is in communication with the third network device, and the second network device is in communication with the fourth network device.
  • FIG. 1 is a schematic structural diagram of an existing packet network protection system.
  • FIG. 2 is a schematic diagram of a first network scenario according to an embodiment of the present application.
  • FIG. 3 is a schematic diagram of a second network scenario according to an embodiment of the present disclosure.
  • FIG. 4 is a schematic diagram of a third network scenario provided by an embodiment of the present application.
  • FIG. 5 is a flowchart of a method for processing a service flow in a packet network according to Embodiment 1 of the present application.
  • FIG. 6 is a flowchart of a method for processing a service flow in a packet network according to Embodiment 2 of the present application.
  • FIG. 7 is a schematic diagram of a data packet carrying a control word according to an embodiment of the present disclosure.
  • FIG. 8 is a schematic structural diagram of an apparatus for processing a service flow in a packet network according to an embodiment of the present disclosure.
  • FIG. 9 is a schematic structural diagram of an apparatus for processing a service flow in another packet network according to an embodiment of the present disclosure.
  • the embodiment of the present application provides a method for processing a service flow in a packet network.
  • the method is applied to a network device group, the network device group including a first network device and a second network device, the first network device communicating with the second network device and a third network device, the second network The device communicates with the fourth network device.
  • the structures and functions of the first network device and the second network device are similar.
  • the method includes: the first network device obtains a first uplink service flow, where the first uplink service flow includes at least one uplink data packet, and each uplink data packet in the first uplink service flow includes a sequence The sequence number of each uplink data packet in the first uplink service flow is used to identify the sequence of the uplink data packet in which the uplink data packet is located in the first uplink service flow, and the first uplink service flow An uplink service flow received by the first network device from the third network device, or a service flow obtained by the first network device replicating an uplink service flow from the third network device; Receiving, by the first network device, the second uplink service flow that is sent by the second network device, where the second uplink service flow includes at least one uplink data packet, where the second uplink service flow is Each uplink data packet includes a sequence number, and each uplink data packet in the second uplink service flow includes a sequence number for identifying an uplink data packet in which the uplink data packet is located.
  • the second uplink service flow is an uplink service flow received by the second network device from the fourth network device, or is the second network device pair from the fourth network
  • the service flow obtained by the uplink service flow of the device is copied; the first network device acquires the third uplink according to the first reference sequence number and the sequence number included in each uplink data packet of the received N uplink service flows.
  • a service flow, the third uplink service flow includes at least one uplink data packet, and the N uplink service flows include one or more of the first uplink service flow and the second uplink service flow,
  • the uplink data packet of the third uplink service flow includes a sequence number that is greater than the first reference sequence number; and the first network device sends the third uplink service flow to the fifth network device.
  • FIG. 2 is a schematic diagram of a first network scenario according to an embodiment of the present application.
  • CE1 communicates with PE1 through AC11
  • CE1 communicates with PE2 through AC12.
  • PE1 communicates with PE2 through two bidirectional PWs, PW11 and PW12. If CE1 sends a packet to CE2, it is called uplink communication, and CE2 sends a packet to CE1, which is called downlink communication.
  • PW11 is used to protect uplink communication between PE1 and PE2.
  • PW12 is used to downlink between PE1 and PE2. Communication is protected.
  • the PE 1 includes a first replicator 11, a first selector 12, a second replicator 13, and a second selector 14.
  • the first replicator 11 and the first selector 12 are configured to process messages in the same direction; the second replicator 13 and the second selector 14 are configured to process messages in the same direction.
  • a certain direction in the embodiment of the present application refers to an uplink communication direction or a downlink communication direction.
  • the replicator 21 included in the PE2 is the third replicator 21, the selector 22 included in the PE2 is the third selector 22, and the replicator 23 included in the PE2 is the fourth replicator. 23, the selector 24 included in the PE2 is the fourth selector 24.
  • PE1 communicates with PE3 through PW13.
  • PE2 communicates with PE4 through PW14.
  • PE3 communicates with CE2 through AC21.
  • PE4 communicates with CE2 through AC22.
  • PE1 and PE2 can form a network device group in the first network scenario.
  • PE3 and PE4 can form another network device group in the first network scenario.
  • FIG. 5 is a flowchart of a method for processing a service flow in a packet network according to Embodiment 1 of the present application.
  • a PE in the packet network provided in Embodiment 1 of the present application may be used in any of the PEs, the PE2, the PE3, and the PE4.
  • a method for processing a certain service flow in a packet network provided in Embodiment 1 of the present application will be described below with reference to FIG. 2 and FIG.
  • the service flow can be identified by an Ethernet packet type, a physical port, or a logical port, or by a specific protocol field of the upper layer protocol or a combination thereof.
  • a virtual local area network identifier (VID) corresponding to the logical port may be used to identify a service flow.
  • VIP virtual local area network identifier
  • the specific protocol field of the upper layer protocol may be a source Internet Protocol (IP) source address, a destination IP address, a differentiated service code point (DSCP), a type of service (TOS), a transmission. Transmission Control Protocol (TCP) or TCP layer port number.
  • IP Internet Protocol
  • DSCP differentiated service code point
  • TOS type of service
  • TCP Transmission Control Protocol
  • TCP layer port number TCP layer port number
  • CE1 sends an uplink service flow to PE1 and PE2.
  • CE1 can replicate the upstream service flow and obtain two uplink service flows.
  • CE1 sends one of the two uplink service flows to PE1 through AC11.
  • the uplink service flow may be a series of Ethernet frames on the Ethernet port or on a certain VLAN.
  • the Ethernet connection can be implemented by fiber optic or twisted pair.
  • the AC 11 can also be other types of links, which are not illustrated one by one.
  • CE1 sends another service flow of the two uplink service flows to PE2 through AC12.
  • the service flow may be a series of Ethernet frames on the Ethernet port or on a certain VLAN.
  • AC12 can be the same type of link as AC11.
  • the uplink service flow includes at least one uplink data packet.
  • Each uplink data packet included in the uplink service flow carries a sequence number.
  • the sequence number carried in the uplink data packet is used to identify the sequence of the uplink data packet in which the sequence number is located in the uplink service flow.
  • the order can also be understood as a relative position or an absolute position.
  • the PE1 replicates the received uplink service flow, and obtains a first uplink service flow and a fourth uplink service flow.
  • PE1 receives any one of the Ethernet frames included in the uplink service flow sent by CE1 from AC11.
  • PE1 adds a packet header related to the sequence number to any one of the Ethernet frames on the port module (incoming port module) connected to the AC 11.
  • PE1 adds a carrier sequence to any one of the Ethernet frames.
  • the control word of the number to obtain the upstream data message carrying the control word. See Figure 7 for the complete pseudowire encapsulation format of the data message carrying the control word.
  • the Ethernet Payload is the payload included in the Ethernet frame.
  • An Ethernet Header is a header included in the Ethernet frame.
  • the control word can be used to carry the serial number, that is, the last 16 bits or 28 bits of the serial number that can be placed in the pseudo line control word when it is encapsulated, or a separate 4 bytes placed between the ether header and the control word.
  • the last 28 bits in the control word carry the serial number, which helps to extend the time required for the serial number to reach the maximum value and restore the initial value. This helps to avoid different data packets carrying the same serial number.
  • the sequence number may also be transmitted as a context of the Ethernet frame without PE1 performing the above encapsulation on the Ethernet frame.
  • PE1 sequentially copies the uplink data packet carrying the control word, so as to obtain two identical uplink data packets, as the uplink data packet and the first uplink traffic packet.
  • the sequential copying is to perform copying of the messages one by one according to the received data message sequence. If the first uplink service flow is the uplink service flow received by the PE1, the fourth uplink service flow is a service flow obtained by the PE1 replicating the uplink service flow. If the fourth uplink service flow is the uplink service flow received by the PE1, the first uplink service flow is a service flow obtained by the PE1 replicating the uplink service flow.
  • the first replicator 11 in the PE1 may be configured to replicate the received uplink service flow to obtain the first uplink service flow and the fourth uplink service flow. The first replicator 11 sends the first uplink service flow to the first selector 12.
  • the PE1 may further add a Multiprotocol Label Switching (MPLS) encapsulation on the outer layer of the uplink data packet included in the first uplink service flow.
  • MPLS Multiprotocol Label Switching
  • the MPLS encapsulation may be an encapsulation of an MPLS LSP label and a PW label, or an MPLS encapsulation as an encapsulation PW label.
  • the method provided in the embodiment of the present application is described by taking an MPLS encapsulation as an encapsulation PW label as an example.
  • the MPLS encapsulation is to encapsulate the MPLS LSP label and the PW label, refer to the manner of encapsulating the PW label and the normal MPLS LSP label, which are not illustrated in the embodiment of the present application.
  • the PE1 may encapsulate the PW label corresponding to the PW13 in the outer layer of the control word of the uplink data packet included in the first uplink service flow.
  • the first replicator 11 or the first selector 12 can be used to implement the operations of the foregoing MPLS encapsulation.
  • the PE1 may carry the PW label corresponding to the PW13 in the context of the uplink data packet included in the first uplink service flow.
  • PE1 can obtain the serial number in the following two ways: In one mode, the Ethernet frame received by the PE1 from the AC11 is an IEEE802.1CB type Ethernet frame, and the Ethernet frame carries the serial number, and the PE1 will carry the serial number.
  • the sequence number read in the Ethernet frame is used as the sequence number of the uplink data packet to which the Ethernet frame belongs.
  • the uplink data packet to which the Ethernet frame belongs refers to an uplink data packet including the Ethernet frame. In this way, the same uplink data packet carries the same Ethernet frame, and the same Ethernet frame carries the same sequence number, and PE1 and PE2 obtain the same uplink data carrying the same sequence number.
  • PE1 can obtain the sequence number directly from the Ethernet frame received by the pseudowire, which helps simplify the processing flow and improve the packet processing efficiency.
  • PE1 can generate a sequence number by using a local algorithm according to packet data in the Ethernet frame.
  • the local algorithm can be a hash algorithm.
  • PE1 and PE2 have the same packet data in the same Ethernet frame, and PE1 and PE2 use the same algorithm.
  • PE1 and P2 obtain the same sequence number carried by the same uplink data packet.
  • the first uplink service flow includes at least a first uplink data packet.
  • the first uplink data packet includes a first sequence number.
  • the first sequence number is used to identify an order of the first uplink data packet in the first uplink service flow.
  • the first uplink service flow is the service flow obtained after the uplink service flow received by the PE1 or the uplink service flow received by the PE1 is copied, so the first serial number indicates the The order of the first uplink data message in the uplink service flow received by PE1.
  • the first uplink data packet is any uplink data packet in the first uplink service flow.
  • Each uplink data packet of the fourth uplink service flow also carries a sequence number.
  • the fourth uplink service flow also includes the first uplink data packet.
  • the first uplink data packet included in the fourth uplink service flow is the same as the first uplink data packet in the first uplink service flow.
  • the PE1 sends the fourth uplink service flow to the PE2 through the PW11.
  • the first replicator 11 sends the obtained fourth uplink service flow to the third selector 22 included in the PE2 through the PW11.
  • the PE1 may encapsulate the PW label corresponding to the PW11 in the outer layer of the control word of the uplink data packet included in the fourth uplink service flow, that is, adopt the encapsulation format shown in FIG. 7.
  • the PE1 may send the fourth uplink service flow to the PE2 according to the PW label corresponding to the PW11.
  • PE1 can obtain the outgoing link by searching Table 1 below to complete the transmission of the fourth uplink service flow.
  • the PW label corresponding to the PW11 may also be carried in the context of the uplink data packet of the fourth uplink service flow.
  • PE1 can store the correspondence between the first port and the PW label corresponding to the PW11.
  • the first port is connected to the PW 11 and the first replicator 11, respectively.
  • the second port included in the PE2 is connected to the PW11.
  • the second port is further connected to the third selector 22, that is, the third selector 22 can receive the fourth uplink service flow from the PE1 through the PW11.
  • the operation of the PE1 to push the uplink data packet included in the fourth uplink service flow into the label corresponding to the PE2 may be completed by the first replicator 11 or the first port is completed.
  • the port mentioned in the embodiment of the present application is a logical port.
  • the connection between the internal modules of the device mentioned in the embodiment of the present application refers to connecting a plurality of modules distributed on different ports through a logical channel forwarded by the internal data plane of the device.
  • the connection between the internal module and the logical port mentioned in the embodiment of the present application refers to connecting a plurality of modules and logical ports distributed on different ports through a logical channel forwarded by the internal data plane of the device.
  • the above connections can pass through a Switch Fabric, a storage computing unit, a logic chip, and digital logic. Further, the above connection may be identified by a logical line, or the above logical connection may also be identified by a protocol field such as a VLAN or a label label to import the service flow to a different module.
  • PE1 can save a mapping table, as shown in Table 1.
  • the mapping table saved by PE1 shown in Table 1 includes static information for characterizing the network topology.
  • AC11 in Table 1 indicates an identifier for identifying AC11.
  • the PW in the table indicates the label used to identify the PW.
  • the PW13 in the PW13 is the PW label corresponding to the PW13
  • the PW11 in the PW11 is the PW label in the PW11.
  • the inbound link in Table 1 is the link used by the traffic flow received by PE1.
  • the outgoing link in Table 1 is the link used by the traffic flow sent by PE1.
  • the protection link in Table 1 is the alternate link of the ingress link.
  • PE1 may also maintain a state table, as shown in Table 2.
  • the state table saved by PE1 shown in Table 2 includes dynamic information for recording changes in the output of each packet during the transmission of the service flow. It can be used for status detection and fault monitoring of the device, such as an incorrect incoming link. Or outgoing link, and an abnormal reference sequence number.
  • the specific forms of AC11, PW13, PW12, and PW11 in Table 2 may also be the same identifiers as in Table 1.
  • the inbound link in Table 2 indicates the link from the data packet where the reference sequence number is located.
  • the uplink data packet where the first reference sequence number is located may be from AC11 or PW11, where the third reference sequence number is located.
  • the downlink data message can be from PW13 or PW12.
  • the outbound link in Table 2 indicates the link to which the data packet where the reference sequence number is located.
  • the uplink data packet where the first reference sequence number is located may be sent to PW13, where the third reference sequence number is located.
  • Downstream data packets can be sent to AC11.
  • the first reference sequence number is a sequence number associated with the uplink traffic flow configured by PE1.
  • the third reference sequence number is a sequence number associated with the downlink service flow in which PE1 is configured.
  • the PE2 replicates the received uplink service flow, and obtains a second uplink service flow and a fifth uplink service flow.
  • PE2 receives any one of the Ethernet frames included in the uplink service flow sent by CE1 from AC12. On the port module (incoming port module) connected to the AC12, PE2 adds a package header related to the serial number for any one of the Ethernet frames.
  • the encapsulation mode of the PE2 is the same as that of the PE1 in the 502.
  • the manner in which the PE2 obtains the serial number is the same as the manner in which the PE1 obtains the serial number in 502, and details are not described herein.
  • the PE2 can carry the sequence number of the Ethernet frame received by the AC1 in the uplink data packet of the second uplink service flow, or the sequence number of the Ethernet frame received by the AC1.
  • the uplink data packet of the fifth uplink service flow is the sequence number of the Ethernet frame received by the AC1 in the uplink data packet of the second uplink service flow.
  • PE2 sequentially copies the obtained uplink data packet carrying the control word, and obtains two identical uplink data packets, as the uplink data packet included in the second uplink service flow, and the foregoing The uplink data packet included in the five uplink service flows. If the second uplink service flow is the uplink service flow received by the PE2, the fifth uplink service flow is a service flow obtained by the PE2 replicating the received uplink service flow. If the fifth uplink service flow is the uplink service flow received by the PE2, the second uplink service flow is a service flow obtained by the PE2 replicating the received uplink service flow. As shown in FIG. 2, the third replicator 21 in the PE2 may be configured to replicate the uplink service flow received by the PE2 to obtain the second uplink service flow and the fifth uplink service flow. The third replicator 21 sends the fifth uplink service flow to the third selector 22.
  • the PE2 may further add an MPLS encapsulation on the outer layer of the uplink data packet included in the fifth uplink service flow.
  • the MPLS encapsulation is the same as the corresponding content in 502, and details are not described herein again.
  • the PE2 may encapsulate the PW label corresponding to the PW 14 in the outer layer of the control word of the uplink data packet included in the fifth uplink service flow.
  • the third replicator 21 or the third selector 22 can be used to implement the operations of the foregoing MPLS encapsulation.
  • each uplink data packet of the second uplink service flow carries a sequence number.
  • the second uplink service flow includes a second uplink data packet.
  • the second uplink data message includes a second sequence number.
  • the second sequence number is used to identify an order of the second uplink data packet in the second uplink service flow.
  • the second uplink service number is the service flow obtained after the uplink service flow received by the PE2 or the uplink service flow received by the PE2 is copied, so the second serial number indicates the The order of the second uplink data message in the uplink service flow received by the PE2.
  • the second uplink data packet is any uplink data packet in the second uplink service flow.
  • Each uplink data packet of the fifth uplink service flow carries a sequence number.
  • the fifth uplink service flow also includes the second uplink data packet.
  • the second uplink data packet included in the fifth uplink service flow is the same as the second uplink data packet in the second uplink service flow.
  • the uplink data packet included in the uplink service flow of the CE1 is sent to the PE1 and the PE2 in sequence, and the link length or transmission rate of the AC11 and AC12 is not exactly the same. Therefore, the uplink traffic flow is the first.
  • the time when the uplink data packet arrives at PE1 and PE2 is not necessarily the same. For example, two copies of a certain data packet of the uplink service flow may be received and processed by PE1, or first received and processed by PE2.
  • the PE2 sends the second uplink service flow to the PE1 through the PW11.
  • the third replicator 21 sends the obtained second uplink service flow to the first selector 12 included in the PE1 through the PW11.
  • the PE2 may encapsulate the PW label corresponding to the PW11 in the outer layer of the control word of the uplink data packet included in the second uplink service flow.
  • the PE2 may send the second uplink service flow to the PE1 according to the PW label corresponding to the PW11.
  • PE2 can obtain the outgoing link by looking up Table 3 to complete the sending of the second uplink service flow.
  • the PE2 can store the correspondence between the third port and the PW label corresponding to the PW11.
  • the PW label corresponding to the PW11 used by the PE2 and the PW11label used by the PE1 may be two unidirectional PW labels corresponding to the PW11.
  • the third port is connected to the PW 11 and the third replicator 21, respectively.
  • the third port and the second port may be the same port, or may be a port different from the second port.
  • the fourth port included in PE1 is connected to PW11.
  • the fourth port is also connected to the first selector 12, that is, the first selector 12 can receive the second uplink service flow from the PE2 through the PW11.
  • the first port of the fourth port and the 503 may be the same port, or may be a port different from the first port of the 503.
  • the third replicator 21 puts a label corresponding to PE1 for the second uplink service flow at the third port to which it is connected.
  • both PW11 and PW12 are bidirectional PWs. Any one of PW11 and PW12 has a unique identifier. Any one of PW11 and PW12 is assigned two unidirectional PW labels. The two unidirectional PW labels are bound to one bidirectional PW. For example, in the process of transmitting the uplink service flow through the PW11, the PW label corresponding to the PE1 and the PW label corresponding to the PE2 used by the PE2 are the two unidirectional PW labels to which the PW11 is allocated.
  • the PW label corresponding to the PE1 and the PW label corresponding to the PE2 used by the PE2 are the two unidirectional PW labels to which the PW12 is allocated.
  • PE2 can save a mapping table, as shown in Table 3.
  • the PE2 saved mapping table shown in Table 3 includes static information for characterizing the network topology.
  • the specific forms of AC12, PW11, PW12, and PW14 in Table 3 are the same as those in Table 1, and are not described herein again.
  • the ingress link in Table 3 is the link used by the traffic flow received by PE2.
  • the outgoing link in Table 3 is the link used by the traffic flow sent by PE2.
  • the protection link in Table 3 is the alternate link of the ingress link.
  • PE2 may also maintain a state table, as shown in Table 4.
  • the PE2 saved state table shown in Table 4 includes dynamic information for characterizing the transmission process of the service flow.
  • the specific forms of AC12, PW11, PW12, and PW14 in Table 4 are the same as those in Table 1, and are not described herein again.
  • the inbound link in Table 4 indicates the link from the data packet where the reference sequence number is located.
  • the uplink data packet where the second reference sequence number is located may be from AC12 or PW11, where the fourth reference sequence number is located.
  • the downlink data message can be from PW14 or PW12.
  • the outbound link in Table 4 indicates the link to which the data packet where the reference sequence number is located.
  • the uplink data packet where the second reference sequence number is located may be sent to the PW 14, where the fourth reference sequence number is located.
  • Downstream data packets can be sent to AC12.
  • the second reference sequence number is a sequence number associated with the uplink traffic flow configured by PE2.
  • the fourth reference sequence number is a sequence number related to the downlink service flow that PE2 is configured.
  • the PW11 between PE1 and PE2 will prolong the transmission time.
  • the time point and sequence number of the second uplink service flow and the first uplink service flow received by the first selector 12 of the PE1 are not completely the same.
  • the time point and sequence number of the fourth uplink service flow and the fifth uplink service flow received by the third selector 22 of the PE2 are not completely the same.
  • the PE1 acquires and sends a third uplink service flow according to the first reference sequence number, the first uplink service flow, and the second uplink service flow.
  • the initial value of the first reference sequence number may be zero.
  • the value of the first reference sequence number is updated to the value of the sequence number included in the uplink data message.
  • the PE1 may update the content in the entry in the table 2 that includes the first reference sequence number, and the inbound link is updated to the link through which the uplink data packet is received, and the first reference sequence number is updated to the The sequence number included in the uplink data packet, and the outgoing link is updated to the link through which the uplink data packet is sent.
  • the PE1 obtains the third uplink service flow according to the first reference sequence number, the first uplink service flow, and the second uplink service flow, where the PE1 is configured according to each uplink datagram in the first uplink service flow.
  • the arrival time of the text and the arrival time of each uplink data packet in the second uplink service flow, and the uplink data packet included in the first uplink service flow and the uplink data packet included in the second uplink service flow Sorting the text to obtain the sorted uplink service flow; the PE1 selects, from the sorted uplink service flow, multiple uplink data packets whose sequence number value is greater than the first reference sequence number, as the third The uplink service flow, where the sequence number of the i-th uplink data packet in the third uplink service flow is greater than the first reference sequence number, and the arrival time of the (i+1)th uplink data packet in the third uplink service flow
  • the ith uplink data packet is longer than the ith uplink data packet, and the ith ith uplink data packet includes a sequence number
  • the at least one uplink data packet included in the first uplink service flow may be sent by the first selector. 12 to send.
  • the second uplink service flow arrives at the first selector 12 at time t1.
  • the first uplink service flow has n-1 uplink data messages sent by the first selector 12 before the time t1. n is an integer greater than one.
  • the last uplink data packet that is sent by the first selector 12 and belongs to the first uplink service flow is the n-1th uplink data packet.
  • the first reference sequence number is updated to a sequence number included in the n-1th uplink data message.
  • the first uplink service flow further includes an nth uplink data packet and an n+1th uplink data packet.
  • the nth uplink data packet indicates that the first uplink service flow reaches the first uplink data packet of the first selector 12 at time t1.
  • the second uplink service flow includes an mth uplink data packet and an m+1th uplink data packet.
  • the mth uplink data packet indicates that the second uplink service flow reaches the first uplink data packet of the first selector 12 at time t1. Where m is an integer greater than one.
  • the first selector 12 includes a sequence number included in the mth uplink data packet, a sequence number included in the nth uplink data packet, and the n-1th
  • the serial number included in the uplink data message is compared.
  • the second uplink service flow and the first uplink service flow are both from the same uplink service flow, and the second uplink service flow arrives at the first selector 12 later than the second uplink service flow. Therefore, the sequence number of the mth uplink data packet is less than or equal to the sequence number included in the n-1th uplink data packet.
  • the nth uplink data packet is the uplink data packet in the first uplink service flow before the nth uplink data packet, where the nth uplink data packet is included.
  • the sequence number is greater than the sequence number included in the n-1th uplink data message.
  • the first selector 12 uses the nth uplink data packet as an uplink data packet in the third uplink service flow according to the comparison result.
  • the first selector 12 may update the sequence number included in the nth uplink data message to the first reference sequence number.
  • the first selector 12 may continue to adopt the foregoing method, the sequence number included in the (n+1)th uplink data packet, the sequence number included in the (m+1)th uplink data packet, and the mth Comparing the sequence number included in the uplink data packet with the sequence number included in the nth uplink data packet, determining that the sequence number included in the (n+1)th uplink data packet is greater than the updated first number Baseline serial number.
  • the first selector 12 uses the (n+1)th uplink data packet as an uplink data packet in the third uplink service flow.
  • the first selector 12 may be configured according to the nth uplink data packet, the (n+1)th uplink data packet, the mth uplink data packet, and the At the time when the m+1th uplink data packet arrives, the four uplink data packets are sorted to obtain the sorted uplink service flow.
  • the sorted uplink service flows are arranged in the order of arrival: the mth uplink data packet -> the nth uplink data packet -> the m+1th uplink data packet - > the n+1th uplink data message.
  • the mth uplink data packet is the first packet of the second uplink service flow, and the first uplink service flow and the second uplink service flow are originated from the same uplink service flow, the mth The uplink data packet includes a sequence number that is less than or equal to the sequence number included in the n-1th uplink data packet.
  • the first selector 12 compares the sequence number included in the uplink data packet included in the sorted uplink service flow with the first reference sequence number.
  • the first selector 12 determines that the sequence number included in the mth uplink data packet is less than or equal to the sequence number included in the n-1th uplink data packet, and the first selector 12 determines the location If the same uplink data packet of the mth uplink data packet has been sent, the first selector 12 may discard the mth uplink data packet.
  • the first selector 12 compares the sequence number included in the nth uplink data packet with the n-1th uplink data packet according to the sequence of arrivals in the sorted uplink service flows. Serial number. The sequence number of the nth uplink data packet is greater than the sequence number of the n-1th uplink data packet, and the first selector 12 determines that the nth uplink data packet belongs to the The third upstream traffic flow.
  • the first selector 12 updates the first reference sequence number to a sequence number included in the nth uplink data message.
  • the first selector 12 continues to compare the sequence number included in the nth uplink data packet with the sequence number included in the m+1th uplink data packet. If the sequence number included in the (m+1)th uplink data packet is greater than the sequence number included in the nth uplink data packet, the first selector 12 determines the (m+1)th uplink datagram
  • the text belongs to the third uplink service flow, and the first reference sequence number is updated by using the sequence number included in the (m+1)th uplink data message.
  • the updated value of the first reference sequence number is a sequence number included in the (m+1)th uplink data message.
  • the first selector 12 discards the m+1th uplink Data message.
  • the value of the first reference sequence number is a sequence number included in the nth uplink data message.
  • the first selector 12 compares the sequence number of the (n+1)th uplink data message with the first reference sequence number. When the sequence number of the (n+1)th uplink data packet is greater than the first reference sequence number, the first selector 12 determines that the (n+1)th uplink data packet belongs to the third uplink. business flow.
  • the first selector 12 updates the first reference sequence number by using the sequence number of the (n+1)th uplink data message.
  • the third uplink service flow obtained by the first selector 12 may be: the nth uplink data packet -> the m+1th uplink data packet -> the first n+1 uplink data messages.
  • the third uplink service flow is: the nth uplink data packet-> the n+1th uplink data packet.
  • the third uplink service flow is: the nth uplink data packet-> the m+1th uplink data packet.
  • the second uplink service flow is earlier than the first uplink service flow reaches the first selector 12, and the second uplink service flow is at least An uplink data packet message is sent by the first selector 12, and the first selector 12 can obtain the third uplink service flow by referring to the foregoing method.
  • the third uplink service flow may be: the mth uplink data packet -> the m+1th uplink data packet -> the n+1th uplink data packet.
  • the third uplink service flow is: the mth uplink data packet-> the m+1th uplink data packet.
  • the third uplink service flow is: the mth uplink data packet-> the n+1th uplink data packet.
  • the PE1 may send the third uplink service flow to the next hop.
  • the next hop is a network device that connects to PE1 and is closer to the destination node of the uplink service flow on the LSP of the uplink service flow.
  • the next hop may be an intermediate node capable of transparently transmitting the third uplink service flow, such as a provider (P) device.
  • P provider
  • the next hop of PE1 is PE3.
  • the PE1 may perform label exchange or push label on each uplink data packet included in the third uplink service flow.
  • the PE1 may replace the PW label included in the uplink data packet of the third uplink service flow with the PW label corresponding to the PW13.
  • the PE1 can obtain the label of the next hop, that is, the PW label corresponding to the PW13.
  • PE1 encapsulates the MPLS of the next hop into the outer layer of the control word to obtain an uplink data packet as shown in FIG. 7.
  • the above-described operation of pressing or replacing the label can be realized by the first selector 12.
  • the first selector 12 is further connected to a fifth port, and the fifth port is connected to the PW13.
  • the PE1 pre-stores the correspondence between the fifth port and the label of the next hop.
  • the first selector 12 may obtain a label of the next hop according to a fifth port connected thereto.
  • the action of pushing the label of the next hop may be implemented by a module or device that implements MPLS encapsulation between the first selector 12 and the fifth port, and is not illustrated herein. .
  • the PE2 acquires and sends the sixth uplink service flow according to the second reference sequence number, the fourth uplink service flow, and the fifth uplink service flow.
  • the initial value of the second reference sequence number may be zero.
  • the value of the second reference sequence number is updated to the value of the sequence number included in the uplink data message.
  • the PE2 may update the content in the entry in the table 4 that includes the second reference sequence number, the inbound link is updated to the link through which the uplink data packet is received, and the second reference sequence number is updated to the The sequence number included in the uplink data packet, and the outgoing link is updated to the link through which the uplink data packet is sent.
  • the method is the same and will not be described here.
  • the at least one uplink data packet included in the fifth uplink service flow may be sent by the third selector. 22 to send.
  • the fourth upstream traffic reaches the third selector 22 at time t2.
  • the fifth uplink service flow has m-1 uplink data messages sent by the third selector 22 before the time t2. m is an integer greater than one.
  • the last uplink data packet that is sent by the third selector 22 and belongs to the fifth uplink service flow is the m-1th uplink data packet.
  • the second reference sequence number is updated to a sequence number included in the m-1th uplink data message.
  • the fifth uplink service flow further includes an mth uplink data packet and an m+1th uplink data packet.
  • the mth uplink data packet indicates that the fifth uplink service flow reaches the first uplink data packet of the third selector 22 at time t2.
  • the fourth uplink service flow includes an nth uplink data packet and an n+1th uplink data packet.
  • the nth uplink data packet indicates that the fourth uplink service flow reaches the first uplink data packet of the third selector 22 at time t2. Where n is an integer greater than one.
  • the third selector 22 may acquire the sixth uplink service flow by using the method used by the first selector 12 in 506.
  • the sixth uplink service flow may be: the mth uplink data packet -> the m+1th uplink data packet -> the n+1th uplink data packet.
  • the sixth uplink service flow is: the mth uplink data packet-> the m+1th uplink data packet.
  • the sixth uplink service flow is: the mth uplink data packet-> the n+1th uplink data packet.
  • the third selector 22 can obtain the sixth uplink service flow by referring to the foregoing method.
  • the sixth uplink service flow may be: the nth uplink data packet -> the m+1th uplink data packet -> the n+1th uplink data packet, or the The sixth uplink traffic packet is: the nth uplink data packet -> the n+1th uplink data packet, or the sixth uplink traffic stream is: the nth uplink data packet -> The m+1th uplink data packet.
  • the PE2 may send the sixth uplink service flow to the next hop.
  • the next hop is a network device that connects to the PE2 and is closer to the destination node of the uplink service flow on the LSP of the uplink service flow.
  • the next hop may be an intermediate node capable of transparently transmitting the sixth uplink service, such as a P device.
  • a P device For the embodiment of FIG. 2, if there is no P device, the next hop of PE2 is PE4.
  • the PE2 may press a label or an exchange label for each uplink data packet that is included in the sixth uplink service flow.
  • the label processing method performed by the PE1 the label used by PE2 is the PW label corresponding to PW14.
  • the above-described operation of pressing or replacing the label can be realized by the third selector 22.
  • the third selector 22 is further connected to a sixth port, and the sixth port is connected to the PW 14.
  • the PE2 pre-stores the correspondence between the sixth port and the label of the next hop.
  • the third selector 22 may obtain a label of the next hop according to the six-five port connected thereto.
  • the foregoing action of pushing the label of the next hop may be implemented by a module or device for MPLS encapsulation between the third selector 22 and the sixth port, which is not illustrated herein. Description.
  • 501 to 507 are processing methods of the upstream traffic flow.
  • the third uplink service flow obtained by the PE1 may be identical to the sixth uplink service flow obtained by the PE2, or may not be identical.
  • one uplink service flow is a subset of another uplink service flow, or one uplink service flow is another.
  • the uplink service flow includes the same uplink data packet or different uplink data packet.
  • 501 to 507 as long as the guarantees 502 and 505 are performed prior to 506, 503 and 504 are performed prior to 507, and the order of execution between 502, 503, 504, and 505 is not limited to the order of FIG. 5, 502 and 504. Can be performed simultaneously, or 504 is performed prior to 502. 503 and 505 can be executed simultaneously, or 505 can be performed prior to 503.
  • 508 to 513 provide a processing method of the downlink traffic.
  • the following describes the processing method of the downlink service flow.
  • the PE1 obtains the first downlink service flow and the fourth downlink service flow according to the downlink service flow sent by the PE3.
  • the method for obtaining the first downlink service flow and the fourth downlink service flow by the PE1 is the same as that of the 502.
  • the second replicator 13 in the PE1 is configured to replicate the downlink traffic flow sent by the PE3.
  • One of the first downlink service flow and the fourth downlink service flow is a downlink service flow from the PE3, and the other downlink service flow is a service flow obtained by replicating the downlink service flow from the PE3. .
  • the PE1 sends the fourth downlink service flow to the PE2 through the PW12.
  • the second replicator 13 sends the obtained fourth downlink service flow to the fourth selector 24 included in the PE2 through the PW12.
  • the PW12 is configured to transmit a service flow in a downlink communication direction between PE1 and PE2, that is, transmit a downlink service flow.
  • the PE1 may perform MPLS encapsulation on the downlink data packet included in the fourth downlink service flow, for example, the PE1 replaces the PW label in the downlink data packet included in the fourth downlink service flow with the PW corresponding to the PW12. Label.
  • the PE1 may send the fourth downlink service flow to the PE2 according to the PW label corresponding to the PW12.
  • PE1 can obtain the PW label corresponding to PW12 from Table 1.
  • the second replicator 13 included in the PE1 or the egress port module connected to the second replicator 13 can be used to implement the MPLS encapsulation described above.
  • the PE2 obtains the second downlink service flow and the fifth downlink service flow according to the downlink service flow sent by the PE4.
  • the fourth replicator 23 included in the PE2 may perform the same method as the third replicator 21 to perform replication of the downlink service flow to obtain the second downlink service flow and the fifth downlink service flow.
  • the downlink traffic flow of the second downlink service flow and the fifth downlink service flow is a downlink service flow sent by the PE4, and the other downlink service flow is a service obtained by replicating the downlink service flow sent by the PE4. flow.
  • the downlink service flow sent by the PE4 and the downlink service flow sent by the PE3 may be the same downlink service flow or a downlink service flow that is not identical.
  • the method for processing the downlink service flow is described based on the case where the downlink service flow sent by the PE4 is identical to the downlink service flow sent by the PE3.
  • the selection and/or discarding operation may be performed by referring to the serial number comparison method provided in the embodiment of the present application.
  • the PE2 sends the second downlink service flow to the PE1 through the PW12.
  • the method for the fourth replicator 23 of the PE2 to send the second downlink service flow to the PE1 through the PW12 is the same as the method for the second replicator 13 of the PE1 to send the fourth downlink service flow to the PE2 through the PW12. Let me repeat.
  • the method for the MPLS encapsulation of the downlink data packet included in the second downlink service flow may be the same as the MPLS encapsulation method used by the second replicator 13 and is not described here.
  • the PE1 obtains the third downlink service flow according to the third reference sequence number, the first downlink service flow, and the second downlink service flow, and sends the third downlink service flow.
  • the third reference sequence number is a sequence number related to the downlink service flow.
  • the third reference sequence number may be updated according to the sequence number included in the downlink data packet sent by the PE1 and recorded in Table 2.
  • For the method for the PE1 to obtain the third downlink service flow according to the third reference sequence number refer to the method for the PE1 to obtain the third uplink service flow.
  • the function of the second selector 14 of the PE1 is the same as that of the first selector 12 of the PE1, except that the second selector 14 is for processing a downlink traffic, and the first selector 12 is for processing an uplink service. flow.
  • PE1 can send the third downlink service flow to CE1 through AC11, that is, the second selector 14 can send the third downlink service flow to CE1 through the port where PE1 and AC11 are connected.
  • the PE1 may further remove the MPLS encapsulation and control word included in the third downlink service flow, obtain a downlink Ethernet frame, and send the packet through the AC11.
  • the PE2 obtains and sends the sixth downlink service flow according to the fourth reference sequence number, the fourth downlink service flow, and the fifth downlink service flow.
  • the fourth reference sequence number is a sequence number related to the downlink service flow.
  • the fourth reference sequence number may be updated according to the sequence number included in the downlink data packet sent by the PE2.
  • the function of the fourth selector 24 of PE2 is the same as that of the third selector 22 of PE2, except that the fourth selector 24 is for processing downlink traffic and the third selector 22 is for processing uplink traffic. flow.
  • PE2 can send the sixth downlink service flow to the CE1 through the AC12, that is, the fourth selector 24 can send the sixth downlink service flow to the CE1 through the port where the PE2 and the AC12 are connected.
  • the PE2 may further remove the MPLS encapsulation and control word included in the sixth downlink service flow, obtain a downlink Ethernet frame, and send the packet through the AC12.
  • the third downlink service flow and the sixth downlink service flow may be two identical service flows, or may be two different service flows, for example, one downlink traffic flow is another.
  • a subset of downlink traffic flows, or one downlink traffic flow and another downlink traffic flow include at least one identical downlink data message.
  • 508 to 513 as long as the guarantees 508 and 511 are performed prior to 512, 509 and 510 are executed prior to 513.
  • the order of FIG. 5 is not limited, 508 and 510 may be performed simultaneously, or 510 may be performed prior to 508. 509 and 511 can be executed simultaneously, or 511 can be performed prior to 509.
  • the PE1 and the PE2 are protected by two PWs, and the service flow transmitted between the CE1 and the CE2 is highly reliable by adopting a method of copying the service flow and selecting the service flow according to the serial number.
  • Business protection any one of PE1, PE2, CE1, and CE2 does not need to cooperate with fault detection and switching actions, so that services can be protected from single points of failure or even multiple points of failure in the network. Higher than previous protection technologies.
  • the method avoids the complexity of the protocol based on the traditional automatic protection switching technology, and is easier to implement on high-speed network devices, thereby improving the scalability of the MPLS network.
  • FIG. 3 is a schematic diagram of a second network scenario according to an embodiment of the present disclosure.
  • PE1, PE2, and CE1 included in the second network scenario provided by the embodiment of the present application may use corresponding devices in the first network scenario.
  • the connection between PE1, PE2, and CE1 in the second network scenario is the same as that in the first network scenario, and is not described here.
  • the processing of the uplink service flow and the downlink service flow in the second network scenario is the same as that of the first network scenario.
  • the structure and function of PE3 in the second network scenario can be the same as that of PE1.
  • the structure and function of PE4 in the second network scenario can be the same as that of PE2.
  • PW13 is used for uplink communication between PE3 and PE4, and its function and structure are the same as those of PW11.
  • PW14 is used for downlink communication between PE3 and PE4, and its function and structure are the same as those of PW12.
  • SPE1 and SPE2 form a network device group in the second network scenario.
  • PE1 and PE2 can form one network device group in the second network scenario
  • PE3 and PE4 can form another network device group in the second network scenario.
  • SPE1 communicates with PE1 through PW23 and communicates with PE3 through PW25.
  • SPE2 communicates with PE2 through PW24 and communicates with PE4 through PW26.
  • SPE1 communicates with SPE2 through PW21 and PW22.
  • the PW21 is used to protect the service flow of the uplink communication between the SPE1 and the SPE2, that is, to transmit the uplink service flow.
  • the PW22 is used to protect the service flow of the downlink communication between the SPE1 and the SPE2, that is, to transmit the downlink service flow.
  • the function of the replicator 15 included in the SPE1 is similar to that of the first replicator 11 included in the PE1, and the difference is that the replicator 15 included in the SPE1 is used to replicate the uplink traffic flow from the PE1 and through the PW21 to the SPE2.
  • the SPE1 does not need to add the control word and the PW label corresponding to the PW21 to the uplink data packet from the PE1.
  • the SPE1 can receive the PW label included in the received uplink data packet according to the PW label corresponding to the PW21. Perform a replacement operation.
  • the SPE1 can obtain the sequence number and obtain the corresponding control word and PW21.
  • the selector 16 included in the SPE1 has the same function as the first selector 12 included in the PE1. The difference is that the selector 16 included in the SPE1 needs to perform a PW label replacement operation on the upstream service flow sent to the PE3 on the egress port module. It is ensured that each uplink data packet sent from the selector 16 included in the SPE1 carries the PW label corresponding to the PW24.
  • the function of the replicator 17 included in the SPE1 is the same as that of the second replicator 13 included in the PE1. The difference is that the replicator 17 included in the SPE1 sends the downlink traffic flow from the PE3 to the SPE2 through the PW22 or the downlink traffic flow sent by the PE3. Copy the obtained business flow.
  • the function of the selector 18 included in the SPE1 is the same as that of the second selector 14 included in the PE1. The difference is that the selector 18 included in the SPE1 needs to perform label replacement on the downlink service flow sent to the PE1 on the egress port module.
  • each downlink data packet sent from the selector 18 included in the SPE1 carries the PW label corresponding to the PW23.
  • the processing method of the uplink service flow sent by the SPE1 to the PE refer to the processing method of the uplink service flow sent by the CE1 to the CE1.
  • the processing method of the downlink service flow sent by the SPE1 to the PE3 refer to the processing method of the downlink service flow sent by the PE1 to the PE3. I will not repeat them here.
  • the function of the replicator 25 included in the SPE2 is the same as that of the third replicator 21 included in the PE2, except that the replicator 25 included in the SPE2 is used to replicate the upstream traffic flow from the PE2 and through the PW21 to the SPE1.
  • the service flow obtained by transmitting the uplink service flow from the PE2 or the uplink service flow sent by the PE2.
  • the SPE2 does not need to add the control word and the PW label corresponding to the PW21 to the uplink data packet from the PE2.
  • the SPE2 can receive the PW label included in the received uplink data packet according to the PW label corresponding to the PW21. Perform a replacement operation.
  • the SPE2 can obtain the serial number by using the method adopted by the PE2 and obtain the corresponding control word and PW21.
  • the selector 26 included in the SPE2 has the same function as the third selector 22 included in the PE2. The difference is that the selector 26 included in the SPE2 needs to perform label replacement on the upstream service flow sent to the PE3 on the egress port module to ensure that the label replacement operation is performed on the egress port module.
  • Each uplink data packet sent from the selector 26 included in the SPE2 carries a PW label corresponding to the PW26.
  • the function of the replicator 27 included in the SPE2 is the same as that of the fourth replicator 23 included in the PE2. The difference is that the replicator 27 included in the SPE2 sends the downlink traffic flow from the PE4 to the SPE1 through the PW22 or the downlink traffic flow sent by the PE4. Copy the obtained business flow.
  • the function of the selector 28 included in the SPE 2 is the same as that of the fourth selector 24 included in the PE 2, except that the selector 28 included in the SPE 2 needs to perform label replacement on the downlink service flow sent to the PE 2 on the egress port module, without The operation of removing the control word and the PW label is performed on the downlink data packet sent to the PE2 to ensure that each downlink data packet sent from the selector 28 included in the SPE2 carries the PW label corresponding to the PW24.
  • the processing method of the uplink service flow sent by the SPE2 to the PE2 refer to the processing method of the uplink service flow sent by the CE1 to the CE1.
  • the processing method of the downlink service flow sent by the PE4 to the PE4 refer to the processing method of the downlink service flow sent by the PE2 to the PE4. I will not repeat them here.
  • each network node adopts the structure shown in FIG. 2 or FIG. 3, that is, a grid-like dual PW link mode, which can avoid single point failure and specific multi-point failure in the network.
  • the business is abnormal.
  • FIG. 4 is a schematic diagram of a third network scenario provided by an embodiment of the present application.
  • PE1, PE2, and PE3 form a network device group in the third network scenario.
  • SPE1, SPE2, and SPE3 may form another network device group in the third network scenario.
  • the network device group in the third network scenario includes the same connection relationship and function of the two network devices as the network device group in the first network scenario.
  • the connection between PE1 and CE1, the connection between PE1 and PE2, and the connection between PE2 and CE1 are the same as those in the first network scenario.
  • PE1 can communicate with PE3 through PW13 and PW14.
  • PW13 is used for uplink communication between PE1 and PE3.
  • PW14 is used for downlink communication between PE1 and PE3.
  • PE1 can communicate with SPE1 through PW21.
  • PE2 can communicate with PE3 through PW15 and PW16.
  • PW15 is used for uplink communication between PE2 and PE3.
  • PW16 is used for downlink communication between PE2 and PE3.
  • PE2 can communicate with SPE2 through PW22.
  • PE3 can communicate with SPE3 through PW23.
  • SPE1, SPE2, and SPE3 can be replaced with PEs.
  • the network scenario is not described here.
  • SPE1, SPE2, and SPE3 as a network device group refer to PE1, PE2, and PE3 as an embodiment of a network device group.
  • PE1 and PE2 include the same structure as the corresponding device in the first network scenario.
  • the PE 3 includes a fifth replicator 31, a fifth selector 32, a sixth replicator 33, and a sixth selector 34.
  • the fifth replicator 31 and the fifth selector 32 are configured to implement processing of an uplink traffic flow.
  • the sixth replicator 33 and the sixth selector 34 are used to implement processing of the downlink traffic flow.
  • FIG. 6 is a flowchart of a method for processing a service flow in a packet network according to Embodiment 2 of the present application.
  • the method for processing the service flow in the packet network provided in the second embodiment of the present application may include the content of 501 to 513 in the method provided in the first embodiment, that is, the interaction process between the PE1, the PE2, and the CE1. The content will not be described again.
  • the interaction process between PE3, PE1 and CE1 included in the method provided in the second embodiment of the present application is described below with reference to FIG. 601.
  • CE1 sends an uplink service flow to PE3.
  • 601 can be performed simultaneously with 501 in the first embodiment of the present application, that is, CE1 can replicate the uplink service flow to obtain three uplink service flows, where the three uplink service flows include two replicated uplink service flows.
  • CE1 sends the three uplink service flows to PE1, PE2, and PE3.
  • CE1 may send the uplink service flow to PE3 through AC13.
  • the PE1 replicates the received uplink service flow from the CE1 to obtain the first uplink service flow and the seventh uplink service flow.
  • PE1 can use the method in 501 of Embodiment 1 of the present application to copy the uplink service flow from CE1 to obtain the seventh uplink service flow.
  • the first uplink service flow is the same as the first uplink service flow in the first embodiment of the present application. If the first uplink service flow is the uplink service flow received by the PE1, the seventh uplink service flow is a service flow obtained by the PE1 replicating the uplink service flow. If the seventh uplink service flow is the uplink service flow received by the PE1, the first uplink service flow is a service flow obtained by the PE1 replicating the uplink service flow. As shown in FIG. 4, the first replicator 11 in PE1 transmits the seventh traffic flow to the first selector 12.
  • the method of obtaining the serial number of the PE1 and the method of encapsulating the control word on the received Ethernet frame from the AC11 refer to the method used by the PE1 in the embodiment corresponding to FIG. 5, and details are not described herein again.
  • each uplink data packet of the seventh uplink service flow carries a sequence number.
  • the seventh uplink service flow also includes the first uplink data packet included in the first uplink service flow in 502.
  • the first uplink data packet included in the seventh uplink service flow is the same as the first uplink data packet in the first uplink service flow.
  • the PE1 sends the seventh uplink service flow to the PE3 through the PW13.
  • the first replicator 11 sends the obtained seventh uplink service flow to the fifth selector 32 included in the PE3 through the PW13.
  • the first replicator in the 503. 11 is a method of transmitting the fourth uplink service flow to the third selector 22.
  • the PE1 may perform MPLS encapsulation on the uplink data packet that is included in the seventh uplink service flow.
  • the PE1 may press the PW label corresponding to the PW13 on the uplink data packet included in the seventh uplink service flow.
  • the PE1 can send the fourth uplink service flow to the PE3 through the PW13 according to the PW label corresponding to the PW13.
  • the specific method refer to the corresponding content in 503.
  • the PE3 replicates the received uplink service flow, and obtains an eighth uplink service flow and a ninth uplink service flow.
  • PE3 sequentially copies any uplink data packet included in the uplink service flow received by the PE3, and obtains two identical uplink data packets, as the uplink data packet included in the eighth uplink service flow.
  • the uplink data packet included in the ninth uplink service flow refer to the method for the PE2 to obtain the second uplink service flow and the fifth uplink service flow in 504.
  • the fifth replicator 31 in the PE3 may be configured to replicate the uplink service flow received by the PE3 to obtain the eighth service flow and the ninth service flow.
  • the fifth replicator 31 transmits the ninth traffic flow to the fifth selector 32.
  • the method of obtaining the serial number of the PE3 and the method of encapsulating the control word on the received Ethernet frame from the AC13 refer to the method used by the PE1 in the embodiment corresponding to FIG. 5, and details are not described herein again.
  • the uplink data packet included in the uplink service flow is sent to the PE1, the PE2, and the PE3 in sequence, and the configurations of the AC11, the AC12, and the AC13 are not completely the same. Therefore, the first uplink data packet of the uplink service flow is used.
  • the times to reach PE1, PE2, and PE3 are not necessarily the same. For example, the uplink service flow is first received and processed by the PE1, or the uplink service flow is first received and processed by the PE2, or the uplink service flow is first received and processed by the PE3.
  • the PE3 sends the eighth uplink service flow to the PE1 through the PW13.
  • the fifth replicator 31 sends the obtained eighth uplink service flow to the first selector 12 included in the PE1 through the PW3.
  • the PE3 may perform MPLS encapsulation on the uplink data packet included in the eighth uplink service flow.
  • the PE3 may press the PW label corresponding to the PW13 on the uplink data packet included in the eighth uplink service flow.
  • the PE3 may send the eighth uplink service flow to the PE1 through the PW13 according to the PW label corresponding to the PW13. For details, see the procedure for encapsulating PE2 in 505.
  • the PW13 between PE1 and PE3 will extend the transmission time.
  • the eighth upstream service flow received by the first selector 12 of the PE1 is received.
  • the first uplink traffic flow may not be exactly the same.
  • the seventh uplink service flow and the ninth uplink service flow received by the fifth selector 32 of the PE3 may not be identical.
  • the PE1 obtains and sends the tenth uplink service flow according to the first reference sequence number, the first uplink service flow, the second uplink service flow, and the eighth uplink service flow.
  • the first reference sequence number of the second embodiment of the present application is the same as the first reference sequence number of the first embodiment, and the method for updating the first reference sequence number of the second embodiment is the same as the update method of the first embodiment.
  • the second uplink service flow may be an uplink service flow obtained by the PE2 by using the method in the first embodiment and sent to the PE1.
  • the method for the PE1 to obtain the tenth uplink service flow according to the first reference sequence number is the same as the method for the PE1 to obtain the third uplink service flow in the first embodiment, except that the PE1 in the second embodiment needs to be
  • the received three uplink service flows are sorted and/or filtered, that is, the received first uplink service flow, the second uplink service flow, and the eighth uplink service flow are sorted and/or filtered.
  • the sorting and/or screening method used by PE1 refer to 506 in the first embodiment, and details are not described herein again.
  • the next hop of PE1 is SPE1 in Figure 4.
  • the method for the PE1 to send the tenth uplink service flow to the SPE1 is the same as the method for the PE1 to send the third uplink service flow in the first embodiment, except that the PE1 sends each uplink data to the tenth uplink service flow.
  • the PW label encapsulated in the packet is the PW label corresponding to PW21. Whether the tenth uplink service flow in the second embodiment is the same as the third uplink service flow in the first embodiment depends on the sequence of the first uplink service flow, the second uplink service flow, and the eighth service flow.
  • the uplink data packet selected in the process of the number screening may be the same as the third uplink service flow, or may be different from the third uplink service flow.
  • the PE3 acquires and sends the twelfth uplink service flow according to the fifth reference sequence number, the seventh uplink service flow, the ninth uplink service flow, and the eleventh uplink service flow.
  • the initial value of the fifth reference sequence number in the second embodiment may be zero.
  • the eleventh uplink service flow is an uplink service flow obtained by the PE2 while obtaining the second uplink service flow.
  • the eleventh uplink service flow is the same as the second uplink service flow in the first embodiment.
  • the eleventh uplink service flow may be an uplink service flow received by the CE1 from the CE1, or a service flow obtained after the uplink service flow received by the CE1 is copied by the PE2.
  • the method for the PE2 to obtain the twelfth uplink service flow according to the fifth reference sequence number can be referred to the method for the PE2 to obtain the sixth uplink service flow in the first embodiment.
  • the PE3 in the second embodiment sorts and/or filters the received three uplink service flows, that is, the received seventh uplink service flow, the ninth uplink service flow, and the The twelfth upstream traffic flow is sorted and/or filtered.
  • the sorting and/or screening method used by the PE3 refer to 507 in the first embodiment, and details are not described herein again.
  • the next hop of PE3 is SPE3 in Figure 4.
  • the method for the PE3 to send the twelfth uplink service flow to the SPE3 is the same as the method for the PE2 to send the sixth uplink service flow in the first embodiment, except that the PE3 sends each of the twelfth uplink service flows.
  • the PW label encapsulated in the upstream data packet is the PW label corresponding to the PW23. Whether the twelfth uplink service flow in the second embodiment is the same as the sixth uplink service flow in the first embodiment depends on the seventh uplink service flow, the ninth uplink service flow, and the eleventh service flow.
  • the uplink data packet selected in the process of performing sequence number screening, that is, the twelfth uplink service flow may be the same as the sixth uplink service flow, or may be different from the sixth uplink service flow.
  • 601 to 607 are processing methods of the uplink traffic flow. 601 to 607, as long as the guarantees 602 and 605 are performed prior to 606, 603 and 604 are performed prior to 607, and the order of execution between 602, 603, 604, and 605 is not limited to the order of FIG. 6, 602 and 604. Can be performed simultaneously, or 604 is performed prior to 602. 603 and 605 can be executed simultaneously, or 605 can be performed prior to 603.
  • 608 to 613 are processing methods of the downlink service flow.
  • the following describes the processing method of the downlink service flow.
  • the PE1 obtains the first downlink service flow and the seventh downlink service flow according to the downlink service flow sent by the SPE1.
  • the second replicator 13 in the PE1 is configured to replicate the downlink service flow sent by the SPE1 to obtain the seventh downlink service flow.
  • the seventh downlink service flow may be a downlink service flow from SPE1 or a service flow obtained by replicating a downlink service flow from SPE1.
  • the PE1 sends the seventh downlink service flow to the PE3 through the PW14.
  • the second replicator 13 sends the obtained seventh downlink service flow to the sixth selector 34 included in the PE3 through the PW14.
  • the PE1 may perform MPLS encapsulation on the downlink data packet that is included in the seventh downlink service flow.
  • the PE1 encapsulates the PW label corresponding to the PW14 for the downlink data packet included in the seventh downlink service flow.
  • the PE1 can send the seventh downlink service flow to the PE3 through the PW14 according to the PW label corresponding to the PW14. For details, see 603.
  • the PE3 obtains the eighth downlink service flow and the ninth downlink service flow according to the downlink service flow sent by the SPE3.
  • the sixth replicator 33 included in the PE3 may perform the same method as the third replicator 31 to perform replication of the downlink service flow, and obtain the seventh downlink service flow and the eighth downlink service flow.
  • the downlink service flow sent by the SPE3 and the downlink service flow sent by the SPE1 may be the same downlink service flow, or may be different downlink traffic flows.
  • the method for processing the downlink service flow in the embodiment of the present application the method for processing the downlink service flow is described based on the case where the downlink service flow sent by the SPE3 is identical to the downlink service flow sent by the SPE1.
  • the sequence number comparison method provided in the embodiment of the present application may be used for the selection and/or discarding operation, which is not illustrated one by one.
  • the PE3 sends the eighth downlink service flow to the PE1 through the PW14.
  • the method for the sixth replicator 33 of the PE3 to send the eighth downlink service flow to the PE1 through the PW14 is the same as the method for the second replicator 13 of the PE1 to send the seventh downlink service flow to the PE3 through the PW14. Let me repeat.
  • the MPLS encapsulation method of the downlink data packet included in the eighth downlink service flow may be the same as the MPLS encapsulation method used by the second replicator 13 and is not described here. The difference is that the PE3 encapsulates the PW label corresponding to the PW14 for the downlink data packet included in the eighth downlink service flow. The PE3 can send the eighth downlink service flow to the PE1 through the PW14 according to the PW label corresponding to the PW14.
  • the PE1 obtains and sends the tenth downlink service flow according to the third reference sequence number, the first downlink service flow, the second downlink service flow, and the seventh downlink service flow.
  • the third reference sequence number of the second embodiment is the same as the third reference sequence number of the first embodiment.
  • the method of updating the third reference sequence number of the third embodiment is the same as the updating method of the first embodiment.
  • the method for obtaining the tenth downlink service flow is the same as the method for the PE1 of the second embodiment to obtain the tenth uplink service flow.
  • the difference is that the PE1 in the second embodiment refers to the third reference sequence number when acquiring the tenth downlink service flow, and is different from the first reference sequence number that the PE1 is referring to in the tenth uplink service flow.
  • PE1 can send the tenth downlink service flow to CE1 through AC11, that is, the second selector 14 can send the tenth downlink service flow to CE1 through the port that PE1 and AC11 are connected to.
  • the PE1 may remove the control word and the PW label in each downlink data packet included in the tenth downlink service flow.
  • the PE3 obtains and sends the twelfth downlink service flow according to the sixth reference sequence number, the seventh downlink service flow, the ninth downlink service flow, and the eleventh downlink service flow.
  • the sixth reference sequence number is a sequence number related to the downlink service flow on the PE3.
  • the sixth reference sequence number may be updated according to the sequence number included in the downlink data packet sent by the PE3.
  • the function of the sixth selector 34 of PE2 is the same as that of the fifth selector 32 of the PE3, except that the sixth selector 34 is for processing a downlink traffic, and the fifth selector 32 is for processing an uplink service. flow.
  • the PE3 can send the twelfth downlink service flow to the CE1 through the AC13, that is, the sixth selector 34 can send the twelfth downlink service flow to the CE1 through the port where the PE3 and the AC13 are connected.
  • the control word and the PW label in each downlink data packet included in the twelfth downlink service flow may be removed.
  • 609 and 610 may be executed before 613.
  • the order of execution between 608, 609, 610, and 611 the order of FIG. 6 is not limited, 608 and 610 may be performed simultaneously, or 610 may be performed prior to 608. 609 and 611 can be executed simultaneously, or 611 can be performed prior to 609.
  • the process of the interaction between the PE2, the PE3, and the CE1 in FIG. 4 can be referred to the interaction process between the PE3, the PE1, and the CE1, and is not described in the method provided in the second embodiment of the present application.
  • the three PE devices form a network device group, and any two PE devices in the network device group can implement reliability protection on the received uplink service flow or downlink service flow.
  • the stability and reliability are further improved compared to the method provided in the first embodiment.
  • FIG. 8 is a schematic structural diagram of an apparatus for processing a service flow in a packet network according to an embodiment of the present disclosure.
  • the device shown in FIG. 8 may be any device in the network device group provided by the embodiment of the present application, such as PE1, PE2, SPE1, SPE2, or PE3 in the foregoing method.
  • the apparatus provided in this embodiment of the present application includes a first replication module 801 and a first selection module 802.
  • the first copy module 801 may be the first replicator 11
  • the first selection module 802 may be the first selector 12.
  • the first copy module 801 may be a third replicator 21, and the second selection module 802 may be a third selector 22.
  • the embodiment of the present application is described by taking the first network device included in the network device group as an example.
  • the first replication module 801 is configured to obtain a first uplink service flow, where the first uplink service flow includes at least one uplink data packet, and each uplink data packet in the first uplink service flow includes a sequence number.
  • the sequence number of each uplink data packet in the first uplink service flow is used to identify the sequence of the uplink data packet in which the uplink data packet is located in the first uplink service flow, where the first uplink service flow is An uplink service flow received by the first network device from the third network device, or a service flow obtained by the first network device replicating an uplink service flow from the third network device.
  • the first selection module 802 is configured to receive a second uplink service flow sent by the second network device, where the second uplink service flow includes at least one uplink data packet, and each of the second uplink service flows
  • the uplink data packet includes a sequence number, and the sequence number included in each uplink data packet in the second uplink service flow is used to identify the sequence of the uplink data packet in which the uplink data packet is located in the second uplink service flow.
  • the second uplink service flow is an uplink service flow received by the second network device from the fourth network device, or the second network device is configured to replicate an uplink service flow from the fourth network device. The business flow obtained.
  • the first selection module 802 is configured to obtain a third uplink service flow according to the first reference sequence number and the sequence number included in each uplink data packet of the received N uplink service flows, where the third uplink service flow is used. And including at least one uplink data packet, where the N uplink service flows include the first uplink service flow and the second uplink service flow, and the sequence of any uplink data packet included in the third uplink service flow The number is greater than the first reference serial number.
  • the first selection module 802 is configured to send the third uplink service flow to the fifth network device.
  • the first replication module 801 is further configured to: receive an uplink service flow from the third network device, and copy the uplink service flow from the third network device; a pseudo-line, sending, to the second network device, a fourth uplink service flow, where the fourth uplink service flow is the uplink service flow from the third network device, or is an uplink from the third network device The business flow obtained after the business flow is copied.
  • the device further includes a second copy module 803 and a second selection module 804.
  • the second copy module 803 may be the second replicator 13
  • the second selection module 804 may be the second selector 14.
  • the second replication module 803 may be the fourth replicator 23, and the second selection demonic fast 804 may be the fourth selector 24.
  • the second replication module 803 is further configured to obtain a first downlink service flow, where the first downlink service flow includes at least one downlink data packet, and each downlink data packet in the first downlink service flow.
  • the sequence number is included, and the sequence number included in each downlink data packet in the first downlink service flow is used to identify the sequence of the downlink data packet in which the downlink data packet is located in the first downlink service flow, where a downlink service flow is a downlink service flow received by the first network device from the fifth network device, or a downlink service flow from the fifth network device is copied by the first network device The business flow obtained.
  • the second selection module 804 is further configured to receive, by using a second pseudo line, a second downlink service flow sent by the second network device, where the second downlink service flow includes at least one downlink data packet, and the second Each downlink data packet in the downlink service flow includes a sequence number, and each downlink data packet in the second downlink service flow includes a sequence number used to identify that the downlink data packet in which the downlink data packet is located is in the second downlink.
  • An order in the service flow, where the second downlink service flow is a downlink service flow received by the second network device from the sixth network device, or is the second network device pair from the sixth network device The traffic flow obtained by the downlink traffic flow is copied.
  • the second selection module 804 is further configured to obtain a third downlink service flow, the M downlink service flows, according to the second reference sequence number and the sequence number included in each downlink data packet of the received M downlink service flows.
  • the second selection module 804 is further configured to send the third downlink service flow to the third network device.
  • the second replication module 803 is further configured to: receive a downlink service flow from the fifth network device, and copy the downlink service flow from the fifth network device; a pseudo-line, sending, to the second network device, a fourth downlink service flow, where the fourth downlink service flow is the downlink service flow from the fifth network device, or is a downlink from the fifth network device The business flow obtained after the business flow is copied.
  • the first selection module 802 is specifically configured to: include, according to a sequence number included in each uplink data packet in the first uplink service flow, and each uplink data packet in the second uplink service flow. a serial number, the plurality of uplink data packets whose sequence number is greater than the first reference sequence number, and the ith uplink data packet is any one of the third uplink service flows.
  • the uplink data packet, the ith uplink data packet includes a sequence number that is greater than the first reference sequence number
  • the ith i+1 uplink data packet includes a sequence number that is greater than the ith uplink data packet.
  • the sequence number of the i+1th uplink data packet is located after the ith uplink data packet in the third uplink service flow.
  • the first selection module 802 is specifically configured to: according to an arrival time of each uplink data packet in the first uplink service flow, and an arrival time of each uplink data packet in the second uplink service flow. And sorting the uplink data packet included in the first uplink service flow and the uplink data packet included in the second uplink service flow to obtain the sorted uplink service flow; and from the sorted uplink service flow And selecting, as the third uplink service flow, the sequence number of the i-th uplink data packet in the third uplink service flow is greater than the number of the uplink data packets of the first uplink sequence.
  • the first reference sequence number, the arrival time of the (i+1)th uplink data packet in the third uplink service flow is later than the ith uplink data packet, and the (i+1)th uplink data packet includes The sequence number is greater than the sequence number included in the ith uplink data packet, and the ith uplink data packet is any uplink data packet in the third uplink service stream.
  • the second selection module 804 is specifically configured to: include, according to the sequence number included in each downlink data packet in the first downlink service flow, and each downlink data packet in the second downlink service flow, a sequence number of the third downlink service flow, where the value of the sequence number is greater than the plurality of downlink data packets of the second reference sequence number, and the jth downlink data packet is the third downlink service flow.
  • the sequence number included in the jth downlink data packet is greater than the second reference sequence number, and the sequence number included in the j+1th downlink data packet is greater than the jth downlink data packet
  • the included sequence number, the j+1th downlink data packet is located after the jth downlink data packet in the third downlink service flow.
  • the second selection module 804 is specifically configured to: according to the arrival time of each downlink data packet in the first downlink service flow and the arrival of each downlink data packet in the second downlink service flow. And sorting the downlink data packet included in the first downlink service flow and the downlink data packet included in the second downlink service flow to obtain the sorted downlink service flow; and the downlink service after the sorting And in the stream, selecting a plurality of downlink data packets whose sequence number is greater than the second reference sequence number, and the sequence of the jth downlink data packet in the third downlink service flow is included in the third downlink service flow.
  • the number is greater than the second reference sequence number, and the arrival time of the j+1th downlink data packet in the third downlink service flow is later than the jth downlink data packet, and the j+1th downlink datagram
  • the sequence number included in the text is greater than the sequence number included in the jth downlink data packet, and the jth downlink data packet is any downlink data packet in the third downlink service flow.
  • the first selection module 802 is further configured to update a value of the first reference sequence number by using a maximum value of a sequence number included in an uplink data packet in the third uplink service flow.
  • the second selection module 804 is further configured to update a value of the second reference sequence number by using a maximum value of a sequence number included in the downlink data packet in the third downlink service flow.
  • the first replicator module 801 and/or the second replication module 803 may be disposed in a receiving processing logic module of a physical port of the device.
  • the first selection module 802 and the second selection module 804 can be disposed in a transmission processing logic module of a physical port of the device.
  • the first replication module 801 is specifically configured to: receive an Ethernet frame from the third network device; Obtaining an Ethernet frame, obtaining a sequence number; obtaining, according to the Ethernet frame and the sequence number, an uplink data packet included in the first uplink service flow, where the uplink data packet includes the Ethernet frame and the serial number .
  • the first replication module 801 may be specifically configured to perform calculation on the received Ethernet frame to obtain the serial number. Alternatively, the first replication module 801 may be specifically configured to obtain a sequence number carried by the Ethernet frame from the Ethernet frame.
  • the first replication module 801 may further include a serial number generation module (not shown in FIG. 8).
  • the sequence number generating module may generate a sequence number when receiving an Ethernet frame, so that the first copy module 801 adds the sequence number generated by the sequence number generating module to the uplink data of the first uplink service flow.
  • the serial number generating module may be implemented by a serial number generator.
  • FIG. 9 is a schematic structural diagram of an apparatus for processing a service flow in another packet network according to an embodiment of the present disclosure.
  • the apparatus shown in Fig. 9 can be the same as the apparatus shown in Fig. 8.
  • FIG. 9 may be any device included in the network device group in the network scenario shown in FIG. 2, FIG. 3 or FIG. 4.
  • the apparatus of this embodiment may perform the method employed by any of the PEs in the embodiment corresponding to FIG. 5 or FIG. 6.
  • the apparatus provided in this embodiment includes a processor 901, a memory 902, and a communication interface 903.
  • the processor 901, the memory 902, and the communication interface 903 are connected by a communication bus 904.
  • the memory 902 is used to store programs.
  • the processor 901 executes the method steps performed by any of the PEs in the embodiment corresponding to FIG. 5 or FIG. 6 according to the executable instructions included in the program read from the memory 902.
  • the processor 901 is configured to implement the copy function and the selection function of any of the PEs in the embodiment corresponding to FIG. 5 or FIG. 6.
  • the processor 901 can send and receive uplink data messages and/or downlink data messages through the communication interface 903.
  • the memory 902 can also be used to store the mapping table and the state table in the embodiment corresponding to FIG. 5 or FIG. 6.
  • the embodiment of the present application further provides a system for processing a service flow in a packet network.
  • the system can include a network device group in the above method. Any device included in the network device group may adopt the structure of FIG. 8 or FIG. 9 , and details are not described herein again.
  • any device of the network device group may further press the MPLS LSP label for guiding forwarding according to the encapsulation shown in FIG. 7 according to the forwarding requirement.
  • the specific method of pushing the MPLS LSP label is not described here.
  • the network device group mentioned in the embodiment of the present application and the configuration of the PW between the network device groups may be completed before the method of FIG. 5 or FIG. 6 is executed, and the configuration information or the forwarding entry of the response may be sent.
  • the device in FIG. 2, FIG. 3 or FIG. 4 is aware of the protection link and the protection device corresponding to the device, and is not described in detail in this embodiment.
  • the general purpose processor referred to in the embodiments of the present application may be a microprocessor or the processor may be any conventional processor.
  • the steps of the method disclosed in the embodiments of the present invention may be directly implemented as a combination of hardware and software modules in the processor.
  • the code implementing the above functions may be stored in a computer readable medium.
  • Computer readable media includes computer storage media.
  • a storage medium may be any available media that can be accessed by a computer.
  • the computer readable medium may be a random access memory (English full name is random-access memory, abbreviated as RAM in English), read-only memory (English full name is read-only memory, English abbreviation for ROM) , electrically erasable programmable read-only memory (English full name electrically programmable programmable read-only memory, English abbreviation for EEPROM), read-only optical disk (English full name compact disk read-only memory, English abbreviation for CD-ROM) or other Optical disk storage, magnetic disk storage media or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer.
  • RAM random access memory
  • read-only memory English full name is read-only memory, English abbreviation for ROM
  • electrically erasable programmable read-only memory English full name electrically programmable programmable read-only memory, English abbreviation for EEPROM
  • read-only optical disk English full name compact
  • the computer readable medium may be a compact disc (English full name compact disk, abbreviated as CD), a laser disc, a digital video disc (English full name digital video disc, abbreviated as DVD), a floppy disk or a Blu-ray disc.

Landscapes

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

Abstract

本申请实施例提供了一种分组网络中处理业务流的方法，有助于简化故障检测和切换操作，提高转发效率。所述方法应用于一个网络设备组，所述网络设备组包括第一网络设备和第二网络设备，所述第一网络设备与所述第二网络设备连接。所述第一网络设备获得第一上行业务流；所述第一网络设备通过第一伪线，接收所述第二网络设备发送的第二上行业务流；所述第一网络设备根据第一基准序列号、所述第一上行业务流中每个上行数据报文包括的序列号和所述第二上行业务流中每个上行数据报文包括的序列号，获取第三上行业务流，所述第三上行业务流中的任一上行数据报文包括的序列号大于所述第一基准序列号；所述第一网络设备向下一跳节点发送所述第三上行业务流。

Description

一种分组网络中处理业务流的方法及装置
本申请要求于2017年2月20日提交中国专利局、申请号为CN 201710090953.5、发明名称为“一种分组网络中处理业务流的方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域，尤其涉及一种分组网络中处理业务流的方法及装置。
背景技术
通常多协议标签交换(Multi-Protocol Label Switching，MPLS)网络采用快速重路由(fast reroute，FRR)对标签交换路径(label switching path，LSP)对链路或者节点进行局部保护，或者通过建立端对端的备份LSP来保护工作LSP。一旦工作LSP出现故障，则工作LSP上的所有信流及其对应的所有伪线(pseudowire，PW)都切换到备份LSP。FRR或者端对端保护技术无法对供应商边缘(provider edge，PE)设备导致的故障提供保护。
为了实现对PE设备、链路、LSP或PW等多种故障的保护，可在同一用户边缘(customer edge，CE)设备双归属的两个PE设备间建立一条直连的PW，如图1中PE1和PE2之间的D-PW1，以及PE3和PE4之间的D-PW2。
如图1所示，CE1双归于PE1和PE2，即CE1通过AC1连接到PE1，并且CE1通过AC2连接到PE2。PE1和PE2之间通过一条直连PW，例如D-PW1，连接。CE2双归于PE3和PE4，即CE2通过AC3连接到PE3，并且CE2通过AC4连接到PE4。PE3和PE4之间通过一条直连PW，例如D-PW2，连接。AC1、AC2、AC3和AC4为MPLS网络中的接入电路(attachment circuit，AC)。
当业务数据从PE1流向CE1时，PE1通过连接PE3的PW1接收业务数据。PE1将对业务数据进行复制后获得两份业务数据。PE1将两份业务数据中的一份业务数据通过AC1发送给CE1。PE1将两份业务数据中的另一份业务数据通过D-PW1转发给PE2。PE2将通过D-PW1接收到的业务数据通过AC2发送给CE1。CE1对AC1进行故障检测，当AC1正常时，CE1从AC1接收业务数据；当AC1故障时，CE1从AC2接收业务数据。
当业务数据从CE1流向PE1时，CE1发送两份冗余业务数据至PE1和PE2，即CE1将一份业务数据通过AC1发送给PE1，CE1将另一份业务数据通过AC2发送给PE2。PE2接收到CE1发送的业务数据后，通过D-PW1将该业务数据发送给PE1。PE1对AC1进行故障检测，当AC1正常时，PE1从AC1接收业务数据；当AC1故障时，PE1从D-PW1接收业务数据；然后通过PW1发送业务数据到PE3。
上述方法中，PE1和CE1需要对其连接的AC1各自进行故障检测，并根据故障检测的结果切换业务数据的接收方式，转发效率较低且需要定位故障点，业务转发的可靠性还有待进一步提高。
发明内容
本申请实施例提供了一种分组网络中处理业务流的方法及装置，有助于简化故障检测 和切换操作，提高转发效率。
第一方面，提供了一种分组网络中处理业务流的方法，所述方法应用于一个网络设备组，所述网络设备组包括第一网络设备和第二网络设备，所述第一网络设备与所述第二网络设备连接，所述第一网络设备和第三网络设备通信，所述第二网络设备与第四网络设备通信，所述方法包括：所述第一网络设备获得第一上行业务流，所述第一上行业务流包括至少一个上行数据报文，所述第一上行业务流中的每个上行数据报文包括序列号，所述第一上行业务流中的每个上行数据报文包括的序列号用于标识其所在的上行数据报文在所述第一上行业务流中的顺序，所述第一上行业务流为所述第一网络设备接收到的来自所述第三网络设备的上行业务流，或者为所述第一网络设备对来自所述第三网络设备的上行业务流进行复制所获得的业务流；所述第一网络设备通过第一伪线，接收所述第二网络设备发送的第二上行业务流，所述第二上行业务流包括至少一个上行数据报文，所述第二上行业务流中的每个上行数据报文包括序列号，所述第二上行业务流中的每个上行数据报文包括的序列号用于标识其所在的上行数据报文在所述第二上行业务流中的顺序，所述第二上行业务流为所述第二网络设备接收到的来自所述第四网络设备的上行业务流，或者为所述第二网络设备对来自所述第四网络设备的上行业务流进行复制所获得的业务流；所述第一网络设备根据第一基准序列号和接收到的N个上行业务流中每个上行数据报文包括的序列号，获取第三上行业务流，所述第三上行业务流包括至少一个上行数据报文，所述N个上行业务流包括所述第一上行业务流和所述第二上行业务流，所述第三上行业务流中的任一上行数据报文包括的序列号大于所述第一基准序列号；所述第一网络设备向第五网络设备发送所述第三上行业务流。
其中，所述N为大于或等于2的整数。
上述方法中，第一网络设备和第二网络设备采用复制业务流、根据序列号选取业务流并发送的方法，对分组网络中第三网络设备和第五网络设备传输的业务流进行高可靠性的业务保护。所述第一网络设备、所述第二网络设备、所述第三网络设备和所述第五网络设备中的任一设备无需进行故障检测和切换动作的协同，即可使得业务避免受到网络中的单点故障甚至是特定的多点故障的影响。上述方法避免了采用传统基于自动保护倒换技术带来的协议复杂性，在网络设备上更易于实现，从而可以提高MPLS网络的可扩展性。
可选地，所述方法还包括：所述第一网络设备接收来自所述第三网络设备的上行业务流并对所述来自所述第三网络设备的上行业务流进行复制；所述第一网络设备通过所述第一伪线，向所述第二网络设备发送第四上行业务流，所述第四上行业务流为所述来自所述第三网络设备的上行业务流，或者为来自所述第三网络设备的上行业务流被复制后获得的业务流。
上述方法中，所述第一网络设备可通过复制上行业务流并发送给所述第二网络设备的方法，提高所述第二网络设备侧的业务可靠性，有助于避免第四网络设备故障造成所述第二网络设备传输的上行业务流的中断。
可选地，所述方法还包括：所述第一网络设备获得第一下行业务流，所述第一下行业务流包括至少一个下行数据报文，所述第一下行业务流中的每个下行数据报文包括序列号，所述第一下行业务流中的每个下行数据报文包括的序列号用于标识其所在的下行数据报文在所述第一下行业务流中的顺序，所述第一下行业务流为所述第一网络设备接收到的来自所述第五网络设备的下行业务流，或者为所述第一网络设备对来自所述第五网络设备 的下行业务流进行复制所获得的业务流；所述第一网络设备通过第二伪线，接收所述第二网络设备发送的第二下行业务流，所述第二下行业务流包括至少一个下行数据报文，所述第二下行业务流中的每个下行数据报文包括序列号，所述第二下行业务流中的每个下行数据报文包括的序列号用于标识其所在的下行数据报文在所述第二下行业务流中的顺序，所述第二下行业务流为所述第二网络设备接收到的来自第六网络设备的下行业务流，或者为所述第二网络设备对来自所述第六网络设备的下行业务流进行复制所获得的业务流；所述第一网络设备根据第二基准序列号和接收到的M个下行业务流每个下行数据报文包括的序列号，获取第三下行业务流，所述M个下行业务流包括所述第一下行业务流和所述第二下行业务流，所述第三下行业务流包括至少一个下行数据报文，所述第三下行业务流中的任一下行数据报文包括的序列号大于所述第二基准序列号；所述第一网络设备向所述第三网络设备发送所述第三下行业务流。
其中，所述M为大于或等于2的整数。
上述方法中，所述第一网络设备和所述网络设备的上行业务流和下行业务流分别通过两条双向伪线进行保护，有助于进一步提高业务的可靠性。
可选地，所述方法还包括：所述第一网络设备接收来自所述第五网络设备的下行业务流并对所述来自所述第五网络设备的下行业务流进行复制；所述第一网络设备通过所述第二伪线，向所述第二网络设备发送第四下行业务流，所述第四下行业务流为所述来自所述第五网络设备的下行业务流，或者为来自所述第五网络设备的下行业务流被复制后获得的业务流。
上述方法中，所述第一网络设备可通过复制下行业务流并发送给所述第二网络设备的方法，提高所述第二网络设备侧的业务可靠性，有助于避免所述第二网络设备传输的下行业务流的中断。
在一种可能的实现方式中，所述第一网络设备根据第一基准序列号和接收到的N个上行业务流中每个上行数据报文包括的序列号，获取第三上行业务流包括：所述第一网络设备根据所述第一上行业务流中每个上行数据报文包括的序列号和所述第二上行业务流中每个上行数据报文包括的序列号，选择序列号的值大于所述第一基准序列号的多个上行数据报文，作为所述第三上行业务流，第i上行数据报文为所述第三上行业务流中任一上行数据报文，所述第i上行数据报文包括的序列号大于所述第一基准序列号，所述第i+1上行数据报文包括的序列号大于所述第i上行数据报文包括的序列号，所述第i+1上行数据报文在所述第三上行业务流中位于所述第i上行数据报文之后。
上述方法中，所述第一网络设备通过第一基准序列号和上行数据报文包括的序列号，有助于避免所述第三上行业务流中存在相同的上行数据报文(序列号相同的上行数据报文)和/或重复发送相同的上行数据报文，有助于提高转发效率。
在另一种可能的实现方式中，所述第一网络设备根据第一基准序列号和接收到的N个上行业务流中每个上行数据报文包括的序列号，获取第三上行业务流包括：所述第一网络设备根据所述第一上行业务流中每个上行数据报文的到达时刻和所述第二上行业务流中每个上行数据报文的到达时刻，对所述第一上行业务流包括的上行数据报文和所述第二上行业务流包括的上行数据报文进行排序，获得排序后的上行业务流；所述第一网络设备从所述排序后的上行业务流中，选择序列号的值大于所述第一基准序列号的多个上行数据报文，作为所述第三上行业务流，所述第三上行业务流中第i上行数据报文包括的序列号大 于所述第一基准序列号，所述第三上行业务流中第i+1上行数据报文的到达时刻晚于所述第i上行数据报文，且所述第i+1上行数据报文包括的序列号大于所述第i上行数据报文包括的序列号，所述第i上行数据报文为所述第三上行业务流中任一上行数据报文。
在一种可能的实现方式中，所述第一网络设备根据第二基准序列号和接收到的M个下行业务流中每个下行数据报文包括的序列号，获取第三下行业务流包括：所述第一网络设备根据所述第一下行业务流中每个下行数据报文包括的序列号和所述第二下行业务流中每个下行数据报文包括的序列号，选择序列号的值大于所述第二基准序列号的多个下行数据报文，作为所述第三下行业务流，第j下行数据报文为所述第三下行业务流中任一下行数据报文，所述第j下行数据报文包括的序列号大于所述第二基准序列号，所述第j+1下行数据报文包括的序列号大于所述第j下行数据报文包括的序列号，所述第j+1下行数据报文在所述第三下行业务流中位于所述第j下行数据报文之后。
上述方法中，所述第一网络设备通过第二基准序列号和下行数据报文包括的序列号，有助于避免所述第三下行业务流中存在相同的下行数据报文(序列号相同的下行数据报文)和/或重复发送相同的下行数据报文，有助于提高转发效率。
在另一种可能的实现方式中，所述第一网络设备根据第二基准序列号和接收到的M个下行业务流每个下行数据报文包括的序列号，获取第三下行业务流包括：所述第一网络设备根据所述第一下行业务流中每个下行数据报文的到达时刻和所述第二下行业务流中每个下行数据报文的到达时刻，对所述第一下行业务流包括的下行数据报文和所述第二下行业务流包括的下行数据报文进行排序，获得排序后的下行业务流；所述第一网络设备从所述排序后的下行业务流中，选择序列号的值大于所述第二基准序列号的多个下行数据报文，作为所述第三下行业务流，所述第三下行业务流中第j下行数据报文包括的序列号大于所述第二基准序列号，所述第三下行业务流中第j+1下行数据报文的到达时刻晚于所述第j下行数据报文，且所述第j+1下行数据报文包括的序列号大于所述第j下行数据报文包括的序列号，所述第j下行数据报文为所述第三下行业务流中任一下行数据报文。
可选地，所述方法还包括：所述第一网络设备用所述第三上行业务流中的上行数据报文所包括的序列号的最大值，更新所述第一基准序列号的数值。
上述方法中，所述第一网络设备对第一基准序列号进行更新，有助于避免重复发送相同的上行数据报文(相同序列号的上行数据报文)，有助于提高转发效率和上行业务流的连续性。
可选地，所述方法还包括：所述第一网络设备用所述第三下行业务流中的下行数据报文所包括的序列号的最大值，更新所述第二基准序列号的数值。
上述方法中，所述第一网络设备对第二基准序列号进行更新，有助于避免重复发送相同的下行数据报文(相同序列号的下行数据报文)，有助于提高转发效率和下行业务流的连续性。
在一种可能的实现方式中，所述第一网络设备为第一PE设备，所述第二网络设备为第二PE设备，所述第三网络设备为CE设备，所述第四网络设备为所述CE设备；或者所述第一网络设备为第一多跳伪线中的交换节点(PW switching point，SPE)，所述第二网络设备为第二SPE，所述第三网络设备为第一PE设备，所述第四网络设备为第二PE设备，所述第一PE设备和所述第二PE设备与同一CE设备通信；或者所述第一网络设备为第一SPE，所述第二网络设备为第二SPE，所述第三网络设备为第一PE设备，所述第四网络设 备为第二PE设备，所述第一PE设备和所述第二PE设备属于一个网络设备组；或者所述第一网络设备为第一SPE，所述第二网络设备为第二SPE，所述第三网络设备为第一PE设备，所述第四网络设备为第二PE设备，所述第一PE设备和所述第二PE设备属于一个网络设备组，所述第一PE设备和所述第二PE设备与同一CE设备通信。
在一种可能的实现方式中，所述第五网络设备和所述第六网络设备为相同的PE设备，或者所述第五网络设备和所述第六网络设备为不同的PE设备，或者所述第五网络设备和所述第六网络设备为不同的SPE。
可选地，当所述第一网络设备为PE设备，所述第三网络设备为CE设备，所述第一网络设备获得第一上行业务流包括：所述第一网络设备接收来自所述第三网络设备的以太帧；所述第一网络设备根据所述以太帧，获得序列号；所述第一网络设备根据所述以太帧和所述序列号，获得所述第一上行业务流包括的上行数据报文，所述上行数据报文包括所述以太帧和所述序列号。
其中，所述第一网络设备根据所述以太帧，获得序列号包括：所述第一网络设备对接收到的以太帧进行计算，以获得所述序列号。或者，所述第一网络设备从所述以太帧中获得所述以太帧携带的序列号。
其中，所述第一网络设备根据所述以太帧和所述序列号，获得所述第一上行业务流包括的上行数据报文包括：所述第一网络设备将所述序列号可封装于所述以太帧外层，获得所述上行数据报文。或者，所述第一网络设备将所述序列号可携带于所述以太帧的上下文(context)中，获得所述上行数据报文。
上述获得序列号和上行数据报文的方法，能够保证相同的上行数据报文所携带的序列号的数值相同，有助于避免上行业务流中存在重复的上行数据报文。
第二方面，提供了一种分组网络中处理业务流的装置，所述装置设置于网络设备组中的第一网络设备，所述网络设备组还包括第二网络设备，所述第一网络设备与所述第二网络设备连接，所述第一网络设备和第三网络设备通信，所述第二网络设备与第四网络设备通信，所述装置包括用于实现上述第一方面或第一方面任一可能的实现方式的模块。
第三方面，提供了一种分组网络中处理业务流的系统，所述系统包括第二方面提供的装置和第二网络设备，所述第二方面提供的装置设置于第一网络设备，所述第一网络设备与所述第二网络设备连接，所述第一网络设备和第三网络设备通信，所述第二网络设备与第四网络设备通信。
附图说明
为了更清楚地说明本申请实施例中的技术方案，下面将对实施例描述中所需要使用的附图作一简单的介绍。
图1为现有的分组网络保护系统的结构示意图。
图2为本申请实施例提供的第一种网络场景示意图。
图3为本申请实施例提供的第二种网络场景示意图。
图4为本申请实施例提供的第三种网络场景示意图。
图5为本申请实施例一提供的分组网络中处理业务流的方法流程图。
图6为本申请实施例二提供的分组网络中处理业务流的方法流程图。
图7为本申请实施例提供的一种携带控制字(control word)的数据报文的示意图。
图8为本申请实施例提供的一种分组网络中处理业务流的装置的结构示意图。
图9为本申请实施例提供的另一种分组网络中处理业务流的装置的结构示意图。
具体实施方式
本申请实施例描述的应用场景是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
本申请实施例提供了一种分组网络中处理业务流的方法。所述方法应用于网络设备组，所述网络设备组包括第一网络设备和第二网络设备，所述第一网络设备与所述第二网络设备和第三网络设备通信，所述第二网络设备与第四网络设备通信。所述第一网络设备和所述第二网络设备的结构和功能相似。所述方法包括：所述第一网络设备获得第一上行业务流，所述第一上行业务流包括至少一个上行数据报文，所述第一上行业务流中的每个上行数据报文包括序列号，所述第一上行业务流中的每个上行数据报文包括的序列号用于标识其所在的上行数据报文在所述第一上行业务流中的顺序，所述第一上行业务流为所述第一网络设备接收到的来自所述第三网络设备的上行业务流，或者为所述第一网络设备对来自所述第三网络设备的上行业务流进行复制所获得的业务流；所述第一网络设备通过第一伪线，接收所述第二网络设备发送的第二上行业务流，所述第二上行业务流包括至少一个上行数据报文，所述第二上行业务流中的每个上行数据报文包括序列号，所述第二上行业务流中的每个上行数据报文包括的序列号用于标识其所在的上行数据报文在所述第二上行业务流中的顺序，所述第二上行业务流为所述第二网络设备接收到的来自所述第四网络设备的上行业务流，或者为所述第二网络设备对来自所述第四网络设备的上行业务流进行复制所获得的业务流；所述第一网络设备根据第一基准序列号和接收到的N个上行业务流中每个上行数据报文包括的序列号，获取第三上行业务流，所述第三上行业务流包括至少一个上行数据报文，所述N个上行业务流包括所述第一上行业务流和所述第二上行业务流中的一个或多个，所述第三上行业务流中的任一上行数据报文包括的序列号大于所述第一基准序列号；所述第一网络设备向第五网络设备发送所述第三上行业务流。
图2为本申请实施例提供的第一种网络场景示意图。在本申请实施例提供的第一种网络场景中，CE1通过AC11与PE1通信，CE1通过AC12与PE2通信。PE1通过PW11和PW12两条双向PW与PE2通信。若CE1向CE2发送报文称为上行通信，CE2向CE1发送报文称为下行通信，则PW11用于对PE1与PE2之间的上行通信进行保护，PW12用于对PE1与PE2之间的下行通信进行保护。若CE1向CE2发送报文称为下行通信，CE2向CE1发送报文称为上行通信，则PW11用于对PE1与PE2之间的下行通信进行保护，PW12用于对PE1与PE2之间的上行通信进行保护。PE1包括第一复制器11、第一选择器12、第二复制器13和第二选择器14。所述第一复制器11和所述第一选择器12用于处理同一方向的报文；所述第二复制器13和所述第二选择器14用于处理同一方向的报文。本申请实施例中的某一方向指代的是上行通信方向或下行通信方向。为了与PE1包括的复制器和选择器进行区分，PE2包括的复制器21为第三复制器21，PE2包括的选择器22为第三选择器22，PE2包括的复制器23为第四复制器23，PE2包括的选择器24为第四选择器24。PE1通过PW13与PE3通信。PE2通过PW14与PE4通信。PE3通过AC21与CE2通信。 PE4通过AC22与CE2通信。PE1和PE2可组成第一种网络场景中的一网络设备组。PE3和PE4可组成第一种网络场景中的另一网络设备组。
图5为本申请实施例一提供的分组网络中处理业务流的方法流程图。图2中的PE1、PE2、PE3和PE4中的任一PE均可采用本申请实施例一提供的分组网络中处理业务流的方法。下面结合图2和图5，以PE1和PE2为例，对本申请实施例一提供的分组网络中处理某一条业务流的方法进行说明。在PE上，业务流可以通过以太网报文类型、物理端口或逻辑端口来识别，也可以通过上层协议的特定协议字段或其组合来识别。所述逻辑端口对应的虚拟局域网标识(virtual local area network identifier，VID)可用于标识一条业务流。所述上层协议的特定协议字段可以是源互联网协议(Internet Protocol，IP)源地址、目的IP地址、差分服务码点(differentiated services code point，DSCP)、服务类型(type of service，TOS)、传输控制协议(Transmission Control Protocol，TCP)或TCP层端口号。
501，CE1向PE1和PE2发送上行业务流。
举例说明，CE1可对上行业务流进行复制，获得两条上行业务流。CE1将所述两条上行业务流中的一条业务流，通过AC11发送至PE1。例如，AC11为以太网连接的时候，该上行业务流可以是以太端口上或某个VLAN上的一系列的以太帧。所述以太网连接可通过光纤或双绞线来实现。AC11还可以是其他类型的链路，在此不再逐一举例说明。CE1将所述两条上行业务流中的另一条业务流，通过AC12发送至PE2。例如，AC12为以太网连接的时候，该业务流可以是以太端口上或某个VLAN上的一系列的以太帧。AC12可以是与AC11相同类型的链路。所述上行业务流包括至少一个上行数据报文。所述上行业务流包括的每个上行数据报文中携带有序列号。所述每个上行数据报文所携带的序列号用于标识所述序列号所在的上行数据报文在所述上行业务流中的顺序。所述顺序也可理解成相对位置或绝对位置。
502，PE1对接收到的所述上行业务流进行复制，获得第一上行业务流和第四上行业务流。
举例说明，PE1从AC11接收CE1发送的上行业务流包括的任意一个以太帧。在一种实现方式中，PE1在连接AC11的端口模块(入端口模块)上，为所述任意一个以太帧增加与序列号相关的封装首部，例如，PE1为所述任意一个以太帧添加携带序列号的控制字(control word)，以获得携带control word的上行数据报文。携带control word的数据报文的完整伪线封装格式参见图7。如图7所示，以太净荷(Ethernet Payload)为所述以太帧包括的净荷。以太头(Ethernet Header)为所述以太帧包括的头部。control word可用于携带序列号，即序列号在封装时可以放置在伪线control word中的后16位或者后28位，或者放置在以太首部和控制字之间的单独4个字节。采用control word中的后28位携带序列号，有助于延长序列号达到最大值后恢复到起始值所需的时间，有助于避免不同的数据报文携带同一个序列号的情况。在另一种实现方式中，所述序列号还可作为所述以太帧的上下文(context)进行传输，而无需PE1对以太帧进行上述封装。
举例说明，PE1对所述携带了control word的上行数据报文按序复制，从而获得两个相同的上行数据报文，作为所述第一上行业务流所包括的上行数据报文和所述第四上行业务流所包括的上行数据报文。其中，所述按序复制是按照接收到的数据报文顺序进行逐个报文的复制。如果所述第一上行业务流为PE1接收到的所述上行业务流，则所述第四上行业务流为PE1对所述上行业务流进行复制所获得的业务流。如果所述第四上行业务流为 PE1接收到的所述上行业务流，则所述第一上行业务流为PE1对所述上行业务流进行复制所获得的业务流。如图2所示，PE1中的第一复制器11可用于对接收到的所述上行业务流进行复制，以获得所述第一上行业务流和所述第四上行业务流。所述第一复制器11将所述第一上行业务流发送给第一选择器12。
可选地，PE1还可在所述第一上行业务流包括的上行数据报文外层添加多协议标签交换(Multiprotocol Label Switching，MPLS)封装。MPLS封装可以是封装MPLS LSP label和PW label，或者MPLS封装为封装PW label。本申请实施例提供的方法就以MPLS封装为封装PW label为例进行说明。对于MPLS封装为封装MPLS LSP label和PW label的方式，可参考封装PW label的方式和通常的MPLS LSP label，在本申请实施例中不再举例说明。如图7所示，PE1可在所述第一上行业务流包括的上行数据报文的control word的外层封装与PW13对应的PW label。其中，所述第一复制器11或所述第一选择器12可用于实现上述MPLS封装的操作。或者，PE1可将PW13对应的PW label携带在所述第一上行业务流包括的上行数据报文的context中。
举例说明，PE1可采用下述两种方式，获得序列号：一种方式，PE1从AC11接收到的以太帧是IEEE802.1CB类型的以太帧，所述以太帧携带有序列号，PE1将从所述以太帧中读取的序列号作为所述以太帧所属的上行数据报文的序列号。所述以太帧所属的上行数据报文指代包括所述以太帧的上行数据报文。这样，相同的上行数据报文携带有相同的以太帧，相同的以太帧携带有相同的序列号，则PE1和PE2获得相同的上行数据所携带的序列号相同。上述方式中，PE1可从伪线接收到的以太帧中直接获取序列号，有助于简化处理流程和提高报文处理效率。另一种方式，PE1可以根据以太帧内的报文数据，通过本地的算法计算生成序列号。所述本地的算法可以是哈希算法。PE1和PE2所获得的相同的以太帧内的报文数据相同，且PE1和PE2采用相同的算法，则PE1和P2获得相同的上行数据报文所携带的序列号相同。
举例说明，所述第一上行业务流至少包括第一上行数据报文。所述第一上行数据报文包括第一序列号。所述第一序列号用于标识所述第一上行数据报文在所述第一上行业务流中的顺序。由于所述第一上行业务流为PE1接收到的所述上行业务流或为PE1接收到的所述上行业务流被复制后获得的业务流，因此，所述第一序列号表示的是所述第一上行数据报文在PE1接收到的所述上行业务流中的顺序。所述第一上行数据报文为所述第一上行业务流中的任一上行数据报文。所述第四上行业务流的每个上行数据报文同样地携带有序列号。所述第四上行业务流也包括所述第一上行数据报文。所述第四上行业务流包括的所述第一上行数据报文与所述第一上行业务流中的所述第一上行数据报文相同。
503，PE1通过PW11，向PE2发送所述第四上行业务流。
如图2所示，所述第一复制器11将获得的所述第四上行业务流，通过PW11，发送至PE2包括的第三选择器22。
可选地，PE1可在所述第四上行业务流包括的上行数据报文的control word的外层封装与PW11对应的PW label，即采用图7所示的封装格式。其中，PE1可根据PW11对应的PW label，向PE2发送所述第四上行业务流。PE1可通过查找下述表1来获得出链路，以完成所述第四上行业务流的发送。在另一种实现方式中，所述PW11对应的PW label还可携带在所述第四上行业务流的上行数据报文的context中。
可选地，PE1可保存有第一端口与PW11对应的PW label间的对应关系。所述第一端 口分别连接PW11和所述第一复制器11。进一步地，PE2包括的第二端口连接PW11。所述第二端口还连接所述第三选择器22，即所述第三选择器22可通过PW11接收来自PE1的所述第四上行业务流。PE1为所述第四上行业务流包括的上行数据报文压入PE2对应的label的操作可由所述第一复制器11完成或所述第一端口完成。
本申请实施例中提及的端口为逻辑端口。本申请实施例中提及的设备内部模块间的连接是指通过设备内部数据平面转发的一种逻辑通道将分布在不同端口的多个模块连接起来。本申请实施例中提及的内部模块与逻辑端口间的连接是指通过设备内部数据平面转发的一种逻辑通道将分布在不同端口的多个模块和逻辑端口连接起来。上述的连接可以经过交换网(Switch Fabric)、存储计算单元、逻辑芯片和数字逻辑线路。进一步地，上述的连接可以通过逻辑线路来识别，或者上述的逻辑连接也可以用VLAN或者标签label等协议字段来识别，以便将业务流导入到不同的模块。
可选地，PE1可保存有一映射表，如表1所示。表1所示的PE1保存的映射表包括用于表征网络拓扑结构的静态信息。表1中的AC11表示用于标识AC11的标识。表中的PW表示用于标识PW的label，比如：表1中的PW13具体形式为PW13对应的PW label，表1中的PW11具体形式为PW11对应的PW label，表1中的PW12具体形式为PW12对应的PW label。
表1
入链路 出链路 保护链路
AC11 PW13 PW11
PW13 AC11 PW12
表1中的入链路为PE1接收到的业务流所采用的链路。表1中的出链路为PE1发送的业务流所采用的链路。表1中的保护链路为所述入链路的备用链路。
可选地，PE1还可保存有一状态表，如表2所示。表2所示的PE1保存的状态表包括用于记录业务流发送过程中随着每个报文输出变化的动态信息，它可以用于对设备进行状态检测和故障监控，例如错误的入链路或出链路，以及不正常的基准序列号。表2中的AC11、PW13、PW12和PW11的具体形式也可以是与表1相同的标识。
表2
入链路 出链路 基准序列号
AC11或PW11 PW13 第一基准序列号
PW13或PW12 AC11 第三基准序列号
表2中的入链路表示基准序列号所在的数据报文来自的链路，比如所述第一基准序列号所在的上行数据报文可来自于AC11或PW11，所述第三基准序列号所在的下行数据报文可来自于PW13或PW12。表2中的出链路表示基准序列号所在的数据报文发往的链路，比如所述第一基准序列号所在的上行数据报文可发往PW13，所述第三基准序列号所在的下行数据报文可发往AC11。所述第一基准序列号是PE1被配置的与上行业务流相关的序列号。所述第三基准序列号是PE1被配置的与下行业务流相关的序列号。
504，PE2对接收到的所述上行业务流进行复制，获得第二上行业务流和第五上行业务流。
举例说明，PE2从AC12接收CE1发送的上行业务流包括的任意一个以太帧。PE2在连接AC12的端口模块(入端口模块)上，为所述任意一个以太帧增加与序列号相关的封 装首部。PE2所采用的封装方式与502中PE1所采用的封装方式相同，PE2获得序列号的方式与502中PE1获得序列号的方式相同，在此不再赘述。在另一种实现方式中，PE2可采用PE1所采用的context携带序列号的方式，将从AC12接收到的以太帧对应的序列号携带在所述第二上行业务流的上行数据报文中或所述第五上行业务流的上行数据报文中。
举例说明，PE2对其获得的携带了control word的上行数据报文按序复制，获得两个相同的上行数据报文，作为所述第二上行业务流所包括的上行数据报文和所述第五上行业务流所包括的上行数据报文。如果所述第二上行业务流为PE2接收到的所述上行业务流，则所述第五上行业务流为PE2对接收到的所述上行业务流进行复制所获得的业务流。如果所述第五上行业务流为PE2接收到的所述上行业务流，则所述第二上行业务流为PE2对接收到的所述上行业务流进行复制所获得的业务流。如图2所示，PE2中的第三复制器21可用于对PE2接收到的所述上行业务流进行复制，以获得所述第二上行业务流和所述第五上行业务流。所述第三复制器21将所述第五上行业务流发送给第三选择器22。
可选地，PE2还可在所述第五上行业务流包括的上行数据报文外层添加MPLS封装。MPLS封装与502中的相应内容相同，在此不再赘述。如图7所示，PE2可在所述第五上行业务流包括的上行数据报文的control word的外层封装与PW14对应的PW label。其中，所述第三复制器21或所述第三选择器22可用于实现上述MPLS封装的操作。
举例说明，所述第二上行业务流的每个上行数据报文携带有序列号。所述第二上行业务流包括第二上行数据报文。所述第二上行数据报文包括第二序列号。所述第二序列号用于标识所述第二上行数据报文在所述第二上行业务流中的顺序。由于所述第二上行业务流为PE2接收到的所述上行业务流或为PE2接收到的所述上行业务流被复制后获得的业务流，因此，所述第二序列号表示的是所述第二上行数据报文在PE2接收到的所述上行业务流中的顺序。所述第二上行数据报文为所述第二上行业务流中的任一上行数据报文。所述第五上行业务流的每个上行数据报文携带有序列号。所述第五上行业务流也包括所述第二上行数据报文。所述第五上行业务流包括的所述第二上行数据报文与所述第二上行业务流中的所述第二上行数据报文相同。
由于CE1的上行业务流包括的上行数据报文是按序且连续发送至PE1和PE2，而AC11和AC12的链路长度或传输速率很可能并不完全一样，因此，所述上行业务流的首个上行数据报文到达PE1和PE2的时刻不一定相同。比如：所述上行业务流的某个数据报文的两份拷贝可能先被PE1接收和处理，或者先被PE2接收和处理。
505，PE2通过PW11，向PE1发送所述第二上行业务流。
如图2所示，所述第三复制器21将获得的所述第二上行业务流，通过PW11，发送至PE1包括的第一选择器12。
可选地，PE2可在所述第二上行业务流包括的上行数据报文的control word的外层封装与PW11对应的PW label。其中，PE2可根据PW11对应的PW label，向PE1发送所述第二上行业务流。PE2可通过查找表3来获得出链路，以完成所述第二上行业务流的发送。
可选地，PE2可保存有第三端口与PW11对应的PW label间的对应关系。PE2所采用的PW11对应的PW label和PE1所采用的PW11label可以是对应于PW11的两个单向PW label。所述第三端口分别连接PW11和所述第三复制器21。所述第三端口与所述第二端口可以是同一端口，也可以是与所述第二端口不同的端口。PE1包括的第四端口连接PW11。所述第四端口还连接所述第一选择器12，即所述第一选择器12可通过PW11接收来自PE2 的所述第二上行业务流。所述第四端口与503中的第一端口可以是同一端口，也可以是与503中的第一端口不同的端口。其中，所述第三复制器21在其连接的第三端口为第二上行业务流打上PE1对应的label。
本申请实施例提供的方法中，PW11和PW12均是双向PW。PW11和PW12中的任意一条PW具有唯一的标识。PW11和PW12中的任意一条PW被分配两个单向PW label。所述两个单向PW label与一条双向PW绑定。例如，PE1和PE2在通过PW11传输上行业务流的过程中，PE2采用的与PE1对应的PW label和PE1采用的与PE2对应的PW label是PW11被分配的两个单向PW label。同理，PE1和PE2在通过PW12传输下行业务流的过程中，PE2采用的与PE1对应的PW label和PE1采用的与PE2对应的PW label是PW12被分配的两个单向PW label。
可选地，PE2可保存有一映射表，如表3所示。表3所示的PE2保存的映射表包括用于表征网络拓扑结构的静态信息。表3中的AC12、PW11、PW12和PW14的具体形式与表1的具体形式相同，在此不再赘述。
表3
入链路 出链路 保护链路
AC12 PW14 PW11
PW14 AC12 PW12
表3中的入链路为PE2接收到的业务流所采用的链路。表3中的出链路为PE2发送的业务流所采用的链路。表3中的保护链路为所述入链路的备用链路。
可选地，PE2还可保存有一状态表，如表4所示。表4所示的PE2保存的状态表包括用于表征业务流发送过程中的动态信息。表4中的AC12、PW11、PW12和PW14的具体形式与表1的具体形式相同，在此不再赘述。
表4
入链路 出链路 基准序列号
AC12或PW11 PW14 第二基准序列号
PW14或PW12 AC12 第四基准序列号
表4中的入链路表示基准序列号所在的数据报文来自的链路，比如所述第二基准序列号所在的上行数据报文可来自于AC12或PW11，所述第四基准序列号所在的下行数据报文可来自于PW14或PW12。表4中的出链路表示基准序列号所在的数据报文发往的链路，比如所述第二基准序列号所在的上行数据报文可发往PW14，所述第四基准序列号所在的下行数据报文可发往AC12。所述第二基准序列号是PE2被配置的与上行业务流相关的序列号。所述第四基准序列号是PE2被配置的与下行业务流相关的序列号。
在链路和节点未发生故障，且CE1发送的一个上行数据报文及其复制后获得的上行数据报文同时被PE1和PE2接收的情况下，PE1和PE2之间的PW11会延长传输时间。这样，PE1的第一选择器12接收到的所述第二上行业务流和所述第一上行业务流到达的时间点和序列号就不完全相同。同理，PE2的第三选择器22接收到的所述第四上行业务流和所述第五上行业务流到达的时间点和序列号也不完全相同。
506，PE1根据第一基准序列号、所述第一上行业务流和所述第二上行业务流，获取第三上行业务流并发送。
举例说明，所述第一基准序列号的初始值可以为0。每当所述第一选择器12发送了一 个上行数据报文，所述第一基准序列号的数值被更新为该上行数据报文所包括的序列号的值。可选地，PE1可对表2中包括第一基准序列号的表项中的内容进行更新，入链路更新为接收该上行数据报文所经过的链路，第一基准序列号更新为该上行数据报文所包括的序列号，出链路更新为发送该上行数据报文所经过的链路。
举例说明，PE1根据第一基准序列号、所述第一上行业务流和所述第二上行业务流，获取第三上行业务流包括：PE1根据所述第一上行业务流中每个上行数据报文的到达时刻和所述第二上行业务流中每个上行数据报文的到达时刻，对所述第一上行业务流包括的上行数据报文和所述第二上行业务流包括的上行数据报文进行排序，获得排序后的上行业务流；PE1从所述排序后的上行业务流中，选择序列号的值大于所述第一基准序列号的多个上行数据报文，作为所述第三上行业务流，所述第三上行业务流中第i上行数据报文包括的序列号大于所述第一基准序列号，所述第三上行业务流中第i+1上行数据报文的到达时刻晚于所述第i上行数据报文，且所述第i+1上行数据报文包括的序列号大于所述第i上行数据报文包括的序列号，所述第i上行数据报文为所述第三上行业务流中任一上行数据报文。
当所述第二上行业务流晚于所述第一上行业务流到达所述第一选择器12时，所述第一上行业务流包括的至少一个上行数据报文可经所述第一选择器12进行发送。所述第二上行业务流在t1时刻到达所述第一选择器12。所述第一上行业务流在t1时刻之前有n-1个上行数据报文被所述第一选择器12发送。n为大于1的整数。在t1时刻之前，所述第一选择器12发送的属于所述第一上行业务流的最后一个上行数据报文为第n-1个上行数据报文。所述第一基准序列号被更新为所述第n-1个上行数据报文包括的序列号。所述第一上行业务流还包括第n个上行数据报文和第n+1个上行数据报文。所述第n个上行数据报文表示所述第一上行业务流在t1时刻到达所述第一选择器12的首个上行数据报文。所述第二上行业务流包括第m个上行数据报文和第m+1个上行数据报文。所述第m个上行数据报文表示所述第二上行业务流在t1时刻到达所述第一选择器12的首个上行数据报文。其中，m为大于1的整数。
在一种实现方式中，所述第一选择器12将所述第m个上行数据报文包括的序列号、所述第n个上行数据报文包括的序列号与所述第n-1个上行数据报文包括的序列号进行比较。由于所述第二上行业务流和所述第一上行业务流都来源于同一上行业务流，而所述第二上行业务流晚于所述第二上行业务流到达所述第一选择器12，因此，所述第m个上行数据报文的序列号小于或等于所述第n-1个上行数据报文包括的序列号。由于所述n-1个上行数据报文是所述第一上行业务流中处于所述第n个上行数据报文之前的上行数据报文，因此，所述第n个上行数据报文包括的序列号大于所述第n-1个上行数据报文包括的序列号。所述第一选择器12根据上述比较结果，将所述第n个上行数据报文作为所述第三上行业务流中的上行数据报文。所述第一选择器12可将所述第n个上行数据报文包括的序列号更新到所述第一基准序列号。所述第一选择器12可继续采用上述方法，对所述第n+1个上行数据报文包括的序列号、所述第m+1个上行数据报文包括的序列号、所述第m个上行数据报文包括的序列号和所述第n个上行数据报文包括的序列号进行比较，确定所述第n+1个上行数据报文包括的序列号大于更新后的所述第一基准序列号。所述第一选择器12将所述第n+1个上行数据报文作为所述第三上行业务流中的上行数据报文。
在另一种实现方式中，所述第一选择器12可根据所述第n个上行数据报文、所述第 n+1个上行数据报文、所述第m个上行数据报文和所述第m+1个上行数据报文到达的时刻，对上述四个上行数据报文进行排序，获得排序后的上行业务流。所述排序后的上行业务流按照到达的先后顺序排列为：所述第m个上行数据报文—>所述第n个上行数据报文—>所述第m+1个上行数据报文—>所述第n+1个上行数据报文。当所述第m个上行数据报文为所述第二上行业务流的首包，所述第一上行业务流和所述第二上行业务流来源于同一上行业务流时，所述第m个上行数据报文包括的序列号小于或等于所述第n-1个上行数据报文包括的序列号。所述第一选择器12在获得了所述排序后的上行业务流后，将所述排序后的上行业务流包括的上行数据报文包括的序列号与所述第一基准序列号进行比较。所述第一选择器12确定所述第m个上行数据报文包括的序列号小于或等于所述第n-1个上行数据报文包括的序列号，所述第一选择器12确定与所述第m个上行数据报文相同的上行数据报文已发送过，则所述第一选择器12可丢弃所述第m个上行数据报文。所述第一选择器12按照所述排序后的上行业务流中的到达的先后顺序，比较所述第n个上行数据报文包括的序列号和所述第n-1个上行数据报文包括的序列号。所述第n个上行数据报文包括的序列号大于所述第n-1个上行数据报文包括的序列号，所述第一选择器12确定所述第n个上行数据报文属于所述第三上行业务流。
所述第一选择器12将所述第一基准序列号更新为所述第n个上行数据报文包括的序列号。所述第一选择器12继续用所述第n个上行数据报文包括的序列号与所述第m+1个上行数据报文包括的序列号进行比较。如果所述第m+1个上行数据报文包括的序列号大于所述第n个上行数据报文包括的序列号，则所述第一选择器12确定所述第m+1个上行数据报文属于所述第三上行业务流，且用所述第m+1个上行数据报文包括的序列号更新所述第一基准序列号。所述更新后的所述第一基准序列号的数值为所述第m+1个上行数据报文包括的序列号。如果所述第m+1个上行数据报文包括的序列号小于或等于所述第n个上行数据报文包括的序列号，则所述第一选择器12丢弃所述第m+1个上行数据报文。所述第一基准序列号的数值为所述第n个上行数据报文包括的序列号。所述第一选择器12比较所述第n+1个上行数据报文的序列号和所述第一基准序列号。当所述第n+1个上行数据报文的序列号大于所述第一基准序列号时，所述第一选择器12确定所述第n+1个上行数据报文属于所述第三上行业务流。所述第一选择器12用所述第n+1个上行数据报文的序列号对所述第一基准序列号进行更新。
根据上述方法，所述第一选择器12获取的所述第三上行业务流可以为：所述第n个上行数据报文—>所述第m+1个上行数据报文—>所述第n+1个上行数据报文。或者所述第三上行业务流为：所述第n个上行数据报文—>所述第n+1个上行数据报文。或者所述第三上行业务流为：所述第n个上行数据报文—>所述第m+1个上行数据报文。
在特定的AC1故障或PE1出现业务阻塞然后恢复的情况下，所述第二上行业务流早于所述第一上行业务流到达所述第一选择器12时，所述第二上行业务流至少一个上行数据报文报文被所述第一选择器12发送，所述第一选择器12可参照上述方法获得所述第三上行业务流。所述第三上行业务流可以为：所述第m个上行数据报文—>所述第m+1个上行数据报文—>所述第n+1个上行数据报文。或者所述第三上行业务流为：所述第m个上行数据报文—>所述第m+1个上行数据报文。或者所述第三上行业务流为：所述第m个上行数据报文—>所述第n+1个上行数据报文。
其中，PE1可将所述第三上行业务流发送给下一跳。所述下一跳为上行业务流的LSP 上连接PE1且更靠近上行业务流的目的节点的网络设备。所述下一跳可以是能够透传所述第三上行业务流的中间节点，比如提供商(provider，P)设备。对于图2实施例，若没有P设备，则PE1的所述下一跳是PE3。
可选地，PE1在发送所述第三上行业务流之前，可为所述第三上行业务流包括的每个上行数据报文进行label交换或压入label。当所述第三上行业务流的上行数据报文包括了PW label时，PE1可将所述第三上行业务流的上行数据报文包括的PW label替换为PW13对应的PW label。当所述第三上行业务流的上行数据报文不包括PW label时，PE1可通过表1获得所述下一跳的label，即PW13对应的PW label。PE1将所述下一跳的MPLS封装于control word的外层，以获得图7所示的上行数据报文。上述压入或替换label的操作可由所述第一选择器12实现。
可选地，所述第一选择器12还连接第五端口，所述第五端口连接PW13。PE1预先保存有所述第五端口和所述下一跳的标签(label)的对应关系。所述第一选择器12可根据与其连接的第五端口，获得所述下一跳的label。在其他可实现的方式中，上述压入所述下一跳的label的动作可由所述第一选择器12和所述第五端口间实现MPLS封装的模块或器件实现，在此不再举例说明。
507，PE2根据第二基准序列号、所述第四上行业务流和所述第五上行业务流，获取第六上行业务流并发送。
举例说明，所述第二基准序列号的初始值可以为0。每当所述第三选择器22发送了一个上行数据报文，所述第二基准序列号的数值被更新为该上行数据报文所包括的序列号的值。可选地，PE2可对表4中包括第二基准序列号的表项中的内容进行更新，入链路更新为接收该上行数据报文所经过的链路，第二基准序列号更新为该上行数据报文所包括的序列号，出链路更新为发送该上行数据报文所经过的链路。
其中，PE2根据所述第二基准序列号、所述第四上行业务流和所述第五上行业务流，获取第六上行业务流的方法与前面所述PE1获取所述第三上行业务流的方法相同，在此不再赘述。
当所述第四上行业务流晚于所述第五上行业务流到达所述第三选择器22时，所述第五上行业务流包括的至少一个上行数据报文可经所述第三选择器22进行发送。所述第四上行业务流在t2时刻到达所述第三选择器22。所述第五上行业务流在t2时刻之前有m-1个上行数据报文被所述第三选择器22发送。m为大于1的整数。在t2时刻之前，所述第三选择器22发送的属于所述第五上行业务流的最后一个上行数据报文为第m-1个上行数据报文。所述第二基准序列号被更新为所述第m-1个上行数据报文包括的序列号。所述第五上行业务流还包括第m个上行数据报文和第m+1个上行数据报文。所述第m个上行数据报文表示所述第五上行业务流在t2时刻到达所述第三选择器22的首个上行数据报文。所述第四上行业务流包括第n个上行数据报文和第n+1个上行数据报文。所述第n个上行数据报文表示所述第四上行业务流在t2时刻到达所述第三选择器22的首个上行数据报文。其中n为大于1的整数。
所述第三选择器22可采用506中所述第一选择器12采用的方法，获取所述第六上行业务流。所述第六上行业务流可以为：所述第m个上行数据报文—>所述第m+1个上行数据报文—>所述第n+1个上行数据报文。或者所述第六上行业务流为：所述第m个上行数据报文—>所述第m+1个上行数据报文。或者所述第六上行业务流为：所述第m个上行数 据报文—>所述第n+1个上行数据报文。
当所述第四上行业务流早于所述第五上行业务流到达所述第三选择器22时，所述第四上行业务流至少一个上行数据报文被所述第三选择器22发送，所述第三选择器22可参照上述方法获得所述第六上行业务流。所述第六上行业务流可以为：所述第n个上行数据报文—>所述第m+1个上行数据报文—>所述第n+1个上行数据报文，或者所述第六上行业务流为：所述第n个上行数据报文—>所述第n+1个上行数据报文，或者所述第六上行业务流为：所述第n个上行数据报文—>所述第m+1个上行数据报文。
其中，PE2可将所述第六上行业务流发送给下一跳。所述下一跳为上行业务流的LSP上连接PE2且更靠近所述上行业务流的目的节点的网络设备。所述下一跳可以是能够透传所述第六上行业务流动的中间节点，比如P设备。对于图2实施例，若没有P设备，则PE2的所述下一跳是PE4。
可选地，PE2在发送所述第六上行业务流之前，可为所述第六上行业务流包括的每个上行数据报文压入label或交换label，具体方法可参见PE1进行的标签处理方法。与PE1进行的标签处理方法不同的是，PE2所采用的标签为PW14对应的PW label。PE2可通过表3获得所述下一跳的label，即PW14对应的PW label。上述压入或替换label的操作可由所述第三选择器22实现。
可选地，所述第三选择器22还连接第六端口，所述第六端口连接PW14。PE2预先保存有所述第六端口和所述下一跳的label的对应关系。所述第三选择器22可根据与其连接的所述六五端口，获得所述下一跳的label。在其他可实现的方式中，上述压入所述下一跳的label的动作可由所述第三选择器22和所述第六端口间用于MPLS封装的模块或器件实现，在此不再举例说明。
501至507为上行业务流的处理方法。PE1获取的第三上行业务流与PE2获取的第六上行业务流可以完全相同，也可以不完全相同，比如一个上行业务流是另一个上行业务流的子集，或者一个上行业务流与另一个上行业务流包括有相同的上行数据报文或不相同的上行数据报文。501至507中，只要保证502和505先于506执行，503和504先于507执行即可，对于502、503、504和505之间的执行顺序，不限定于图5的顺序，502和504可同时执行，或者504先于502执行。503和505可以同时执行，或者505先于503执行。
进一步地，对于从CE2到CE1的下行业务流，508至513提供了下行业务流的处理方法。下面对下行业务流的处理方法进行说明。对于相似的部分，可参见上行业务流的处理方法。
508，PE1根据PE3发送的下行业务流，获得第一下行业务流和第四下行业务流。
其中，PE1获得所述第一下行业务流和所述第四下行业务流的方法与502相同。PE1中的第二复制器13用于对PE3发送的下行业务流进行复制。所述第一下行业务流和所述第四下行业务流中的一条下行业务流是来自PE3的下行业务流，另一条下行业务流是对来自PE3的下行业务流进行复制所获得的业务流。
509，PE1通过PW12，向PE2发送所述第四下行业务流。
如图2所示，所述第二复制器13将获得的所述第四下行业务流，通过PW12，发送至PE2包括的第四选择器24。PW12用于在PE1和PE2之间传输下行通信方向的业务信流，即传输下行业务流。
可选地，PE1可对所述第四下行业务流包括的下行数据报文进行MPLS封装，比如PE1 将所述第四下行业务流包括的下行数据报文中的PW label替换为PW12对应的PW label。PE1可根据PW12对应的PW label，向PE2发送所述第四下行业务流。PE1可从表1获得PW12对应的PW label。PE1包括的所述第二复制器13或所述二复制器13连接的出端口模块可用于实现上述MPLS封装。
510，PE2根据PE4发送的下行业务流，获得第二下行业务流和第五下行业务流。
举例说明，PE2包括的第四复制器23可采用与第三复制器21相同的方法，进行下行业务流的复制，获得所述第二下行业务流和所述第五下行业务流。其中，所述第二下行业务流和所述第五下行业务流中的一条下行业务流为PE4发送的下行业务流，另一条下行业务流为对PE4发送的下行业务流进行复制后获得的业务流。
其中，PE4发送的下行业务流与PE3发送的下行业务流可以是完全相同的下行业务流，也可以是不完全相同的下行业务流。在本申请实施例的处理下行业务流的方法中，基于PE4发送的下行业务流与PE3发送的下行业务流完全相同的情况，对下行业务流的处理方法进行说明。对于PE4发送的下行业务流与PE3发送的下行业务流不完全相同的情况，可参照本申请实施例提供的序列号比较方法进行选择和/或丢弃操作，在此不再逐一举例说明。
511，PE2通过PW12，向PE1发送所述第二下行业务流。
其中，PE2的第四复制器23通过PW12向PE1发送所述第二下行业务流的方法与PE1的第二复制器13通过PW12向PE2发送所述第四下行业务流的方法相同，在此不再赘述。
所述第四复制器23对所述第二下行业务流包括的下行数据报文进行MPLS封装的方法可与所述第二复制器13采用的MPLS封装方法相同，在此不再赘述。
512，PE1根据第三基准序列号、所述第一下行业务流和所述第二下行业务流，获取第三下行业务流并发送。
其中，所述第三基准序列号是与下行业务流相关的序列号。所述第三基准序列号可根据PE1发送的下行数据报文包括的序列号进行更新并记录于表2中。PE1根据所述第三基准序列号获取所述第三下行业务流的方法，可参见PE1获取所述第三上行业务流的方法。PE1的第二选择器14的功能与PE1的第一选择器12的功能相同，不同的是所述第二选择器14用于处理下行业务流，所述第一选择器12用于处理上行业务流。
举例说明，PE1可通过AC11向CE1发送所述第三下行业务流，即所述第二选择器14可通过PE1与AC11连接的端口，向CE1发送所述第三下行业务流。在连接AC11的端口模块上，PE1可以进一步将所述第三下行业务流包括的MPLS封装和control word移除，获得下行以太帧并通过AC11发送。
513，PE2根据第四基准序列号、所述第四下行业务流和所述第五下行业务流，获取第六下行业务流并发送。
其中，所述第四基准序列号是与下行业务流相关的序列号。所述第四基准序列号可根据PE2发送的下行数据报文包括的序列号进行更新。PE2根据所述第四基准序列号获取所述第六下行业务流的方法，可参见PE2获取所述第六上行业务流的方法。PE2的第四选择器24的功能与PE2的第三选择器22的功能相同，不同的是所述第四选择器24用于处理下行业务流，所述第三选择器22用于处理上行业务流。
举例说明，PE2可通过AC12向CE1发送所述第六下行业务流，即所述第四选择器24可通过PE2与AC12连接的端口，向CE1发送所述第六下行业务流。在连接AC12的端口模块上，PE2可以进一步将所述第六下行业务流包括的MPLS封装和control word移除， 获得下行以太帧并通过AC12发送。
508至513中，所述第三下行业务流与所述第六下行业务流可以是两条完全相同的业务流，也可以是两条不完全相同的业务流，比如一条下行业务流是另一条下行业务流的子集，或者一条下行业务流和另一条下行业务流包括有至少一个相同的下行数据报文。508至513中，只要保证508和511先于512执行，509和510先于513执行即可。对于508、509、510和511之间的执行顺序，不限定于图5的顺序，508和510可同时执行，或者510先于508执行。509和511可以同时执行，或者511先于509执行。
本申请实施例一提供的方法中，PE1和PE2通过两条PW保护，并采用复制业务流、根据序列号选取业务流并发送的方法，对CE1和CE2间传输的业务流进行高可靠性的业务保护。另外，PE1、PE2、CE1和CE2中的任一设备无需进行故障检测和切换动作的协同，即可使得业务避免受到网络中的单点故障甚至是特定的多点故障的影响，其网络可靠性相对以前的保护技术更高。另外，该方法避免了采用传统基于自动保护倒换技术带来的协议复杂性，在高速网络设备上更易于实现，从而可以提高MPLS网络的可扩展性。
图3为本申请实施例提供的第二种网络场景示意图。如图3所示，本申请实施例提供的第二种网络场景包括的PE1、PE2和CE1可采用第一种网络场景中的相应设备。第二种网络场景中的PE1、PE2和CE1之间的连接与第一种网络场景相同，在此不再赘述。第二种网络场景中的PE1和PE2对上行业务流和下行业务流的处理方式与第一种网络场景相同，具体可参见501至513中的相应内容。第二种网络场景中的PE3的结构和功能可与PE1相同。第二种网络场景中的PE4的结构和功能可与PE2相同。PW13用于PE3和PE4之间的上行通信，其功能和结构与PW11相同。PW14用于PE3和PE4之间的下行通信，其功能和结构与PW12相同。PE3和PE4相互配合处理业务流的方法可参见PE1和PE2相互配合处理业务流的方法，即501至513的相应内容，在此不再赘述。SPE1和SPE2组成了第二种网络场景中的一个网络设备组。此外，PE1和PE2可以组成第二种网络场景中的一个网络设备组，PE3和PE4可组成第二种网络场景中的另一网络设备组。
如图3所示，SPE1通过PW23与PE1通信，通过PW25与PE3通信。SPE2通过PW24与PE2通信，通过PW26与PE4通信。SPE1通过PW21和PW22与SPE2通信。PW21用于SPE1与SPE2之间对上行通信的业务流进行保护，即用于传输上行业务流。PW22用于SPE1与SPE2之间对下行通信的业务流进行保护，即用于传输下行业务流。
举例说明，SPE1包括的复制器15的功能与PE1包括的第一复制器11的功能相近，不同之处包括：SPE1包括的复制器15用于复制来自PE1的上行业务流，且通过PW21向SPE2发送来自PE1的上行业务流或对PE1发送的上行业务流进行复制所获得的业务流。当PE1属于另一网络设备组时，SPE1无需对来自PE1的上行数据报文添加control word和PW21对应的PW label，SPE1可根据PW21对应的PW label对接收到的上行数据报文包括的PW label进行替换操作。当PE1不属于任一网络设备组，且PE1发送给SPE1的上行数据报文中不包括control word和PW label，则SPE1可采用PE1所采用的方法获取序列号并获得携带有control word和PW21对应的PW label的上行数据报文。SPE1包括的选择器16与PE1包括的第一选择器12的功能相同，不同的是SPE1包括的选择器16还需要在出端口模块上对发送至PE3的上行业务流进行PW label替换操作，以保证从SPE1包括的选择器16发送的每个上行数据报文携带有PW24对应的PW label。SPE1包括的复制器17的功能与PE1包括的第二复制器13的功能相同，不同的是SPE1包括的复制器17通过 PW22向SPE2发送来自PE3的下行业务流或者对PE3发送的下行业务流进行复制所获得的业务流。SPE1包括的选择器18的功能与PE1包括的第二选择器14的功能相同，不同的是SPE1包括的选择器18在出端口模块上还需要对发送至PE1的下行业务流进行label替换操作，无需对发送至PE1的下行数据报文进行移除control word和PW label的操作，以保证从SPE1包括的选择器18发送的每个下行数据报文携带有对应于PW23的PW label。SPE1对PE1发送的上行业务流的处理方法可参见PE1对CE1发送的上行业务流的处理方法。SPE1对PE3发送的下行业务流的处理方法可参见PE1对PE3发送的下行业务流的处理方法。在此不再赘述。
举例说明，SPE2包括的复制器25的功能与PE2包括的第三复制器21的功能相同，不同之处包括：SPE2包括的复制器25用于复制来自PE2的上行业务流，且通过PW21向SPE1发送来自PE2的上行业务流或对PE2发送的上行业务流进行复制所获得的业务流。当PE2属于另一网络设备组时，SPE2无需对来自PE2的上行数据报文添加control word和PW21对应的PW label，SPE2可根据PW21对应的PW label对接收到的上行数据报文包括的PW label进行替换操作。当PE2不属于任一网络设备组，且PE2发送给SPE2的上行数据报文中不包括control word和PW label，则SPE2可采用PE2所采用的方法获取序列号并获得携带有control word和PW21对应的PW label的上行数据报文。SPE2包括的选择器26与PE2包括的第三选择器22的功能相同，不同的是SPE2包括的选择器26还需要在出端口模块上对发送至PE3的上行业务流进行label替换操作，以保证从SPE2包括的选择器26发送的每个上行数据报文携带有PW26对应的PW label。SPE2包括的复制器27的功能与PE2包括的第四复制器23的功能相同，不同的是SPE2包括的复制器27通过PW22向SPE1发送来自PE4的下行业务流或者对PE4发送的下行业务流进行复制所获得的业务流。SPE2包括的选择器28的功能与PE2包括的第四选择器24的功能相同，不同的是SPE2包括的选择器28需要在出端口模块上对发送至PE2的下行业务流进行label替换操作，无需对发送至PE2的下行数据报文进行移除control word和PW label的操作，以保证从SPE2包括的选择器28发送的每个下行数据报文携带有PW24对应的PW label。SPE2对PE2发送的上行业务流的处理方法可参见PE2对CE1发送的上行业务流的处理方法。SPE2对PE4发送的下行业务流的处理方法可参见PE2对PE4发送的下行业务流的处理方法。在此不再赘述。
本申请实施例提供的第二种网络场景中，通过在SPE1和SPE2之间部署与图2相似的结构，有助于进一步提高两个PE间的路径冗余，比如通过PE1和PE3间的链路，PE2和PE4间链路，增加了在传输业务流过程中的业务可靠性。在第二种网络场景中，每个网络节点都采用了图2或图3所示的结构，即格栅状的双PW链接方式，能够避免网络中的单点故障和特定多点故障所导致的业务异常。
图4为本申请实施例提供的第三种网络场景示意图。PE1、PE2和PE3组成了第三种网络场景中的一网络设备组。SPE1、SPE2和SPE3可组成第三种网络场景中的另一网络设备组。第三种网络场景中的网络设备组包括的两个网络设备的连接关系和功能与第一种网络场景中的网络设备组相同。PE1与CE1间的连接关系、PE1与PE2间的连接关系和PE2与CE1间的连接关系与第一种网络场景相同。如图4所示，PE1可通过PW13和PW14与PE3通信。PW13用于PE1与PE3间的上行通信。PW14用于PE1与PE3间的下行通信。PE1可通过PW21与SPE1通信。PE2可通过PW15和PW16与PE3进行通信。PW15用于 PE2和PE3间的上行通信。PW16用于PE2和PE3间的下行通信。PE2可通过PW22与SPE2通信。PE3可通过PW23与SPE3通信。在另一种网络场景中，SPE1、SPE2和SPE3可被替换为PE设备，在此不再对该网络场景进行说明。SPE1、SPE2和SPE3作为一网络设备组的实施例可参见PE1、PE2和PE3作为一网络设备组的实施例。PE1和PE2所包括的结构与第一种网络场景中的相应设备相同。PE3包括第五复制器31、第五选择器32、第六复制器33和第六选择器34。其中，第五复制器31和第五选择器32用于实现上行业务流的处理。第六复制器33和第六选择器34用于实现下行业务流的处理。
图6为本申请实施例二提供的分组网络中处理业务流的方法流程图。本申请实施例二提供的分组网络中处理业务流的方法可包括本实施例一提供的方法中的501至513的内容，即PE1、PE2和CE1之间的交互流程，本实施例二对于上述内容不再赘述。下面结合图4，对本申请实施例二提供的方法所包括的PE3、PE1和CE1之间的交互流程进行说明。601，CE1向PE3发送上行业务流。
举例说明，601可与本申请实施例一中的501同时执行，即CE1可对上行业务流进行复制，获得三条上行业务流，所述三条上行业务流包括两条复制后的上行业务流。CE1将所述三条上行业务流分别发送给PE1、PE2和PE3。具体地，CE1可通过AC13，向PE3发送所述上行业务流。
602，PE1对接收到的来自CE1的上行业务流进行复制，获得第一上行业务流和第七上行业务流。
举例说明，PE1可采用本申请实施例一的501中的方法，复制来自CE1的上行业务流，以获得所述第七上行业务流。所述第一上行业务流与本申请实施例一中的第一上行业务流相同。如果所述第一上行业务流为PE1接收到的所述上行业务流，则所述第七上行业务流为PE1对所述上行业务流进行复制所获得的业务流。如果所述第七上行业务流为PE1接收到的所述上行业务流，则所述第一上行业务流为PE1对所述上行业务流进行复制所获得的业务流。如图4所示，PE1中的第一复制器11将所述第七业务流发送给第一选择器12。PE1获得序列号以及在接收到的来自AC11的以太帧上封装control word的方法可参见图5对应的实施例中PE1所采用的方法，在此不再赘述。
举例说明，所述第七上行业务流的每个上行数据报文携带有序列号。所述第七上行业务流也包括502中所述第一上行业务流所包括的第一上行数据报文。所述第七上行业务流包括的所述第一上行数据报文与所述第一上行业务流中的所述第一上行数据报文相同。
603，PE1通过PW13，向PE3发送所述第七上行业务流。
如图4所示，所述第一复制器11将获得的所述第七上行业务流，通过PW13，发送至PE3包括的第五选择器32，具体方法可参见503中所述第一复制器11向第三选择器22发送所述第四上行业务流的方法。
可选地，PE1可对所述第七上行业务流包括的上行数据报文进行MPLS封装，比如PE1可在所述第七上行业务流包括的上行数据报文上压入PW13对应的PW label。PE1可根据PW13对应的PW label，通过PW13发送所述第四上行业务流至PE3，具体方法可参见503中的相应内容。
604，PE3对接收到的所述上行业务流进行复制，获得第八上行业务流和第九上行业务流。
举例说明，PE3对PE3接收到的上行业务流包括的任一上行数据报文按序复制，获得 两个相同的上行数据报文，作为所述第八上行业务流所包括的上行数据报文和所述第九上行业务流所包括的上行数据报文，具体可参见504中PE2获得第二上行业务流和第五上行业务流的方法。如图4所示，PE3中的第五复制器31可用于对PE3接收到的所述上行业务流进行复制，以获得所述第八业务流和所述第九业务流。所述第五复制器31将所述第九业务流发送给第五选择器32。PE3获得序列号以及在接收到的来自AC13的以太帧上封装control word的方法可参见图5对应的实施例中PE1所采用的方法，在此不再赘述。
由于上行业务流包括的上行数据报文是按序且连续发送至PE1、PE2和PE3，而AC11、AC12和AC13的结构并不完全一样，因此，所述上行业务流的首个上行数据报文到达PE1、PE2和PE3的时刻不一定相同。比如：所述上行业务流先被PE1接收和处理，或者所述上行业务流先被PE2接收和处理，或者所述上行业务流先被PE3接收和处理。
605，PE3通过PW13，向PE1发送所述第八上行业务流。
如图4所示，所述第五复制器31将获得的所述第八上行业务流，通过PW3，发送至PE1包括的第一选择器12。
可选地，PE3可对所述第八上行业务流包括的上行数据报文进行MPLS封装，比如PE3可在所述第八上行业务流包括的上行数据报文上压入PW13对应的PW label。PE3可根据PW13对应的PW label，通过PW13发送所述第八上行业务流至PE1。具体方法可参见505中PE2进行封装的流程。
在CE1发送的所述上行业务流被PE1和PE3同时接收的情况下，PE1和PE3之间的PW13会延长传输时间，这样，PE1的第一选择器12接收到的所述第八上行业务流和所述第一上行业务流可能不完全相同。同理，PE3的第五选择器32接收到的所述第七上行业务流和所述第九上行业务流可能不完全相同。
606，PE1根据第一基准序列号、所述第一上行业务流、第二上行业务流和所述第八上行业务流，获取第十上行业务流并发送。
其中，本申请实施例二的第一基准序列号与实施例一的第一基准序列号相同，且实施例二的第一基准序列号的更新方法与实施例一中的更新方法相同。所述第二上行业务流可以是PE2采用实施例一中的方法获得并发送给PE1的上行业务流。
举例说明，PE1根据第一基准序列号获取所述第十上行业务流的方法，与实施例一中PE1获取第三上行业务流的方法相同，不同之处在于，实施例二中的PE1需要对接收到的三条上行业务流进行排序和/或筛选，即对接收到的所述第一上行业务流、所述第二上行业务流和所述第八上行业务流进行排序和/或筛选。PE1所采用的排序和/或筛选方法可参见实施例一中的506，在此不再赘述。
举例说明，PE1的下一跳为图4中的SPE1。PE1向SPE1发送所述第十上行业务流的方法与实施例一中PE1发送所述第三上行业务流的方法相同，不同之处在于PE1向所述第十上行业务流中的每个上行数据报文封装的PW label为PW21对应的PW label。实施例二中的第十上行业务流与实施例一中的第三上行业务流是否相同取决于所述第一上行业务流、所述第二上行业务流和所述第八业务流在进行序列号筛选的过程中被选出的上行数据报文，即所述第十上行业务流可以与所述第三上行业务流相同，也可与所述第三上行业务流不同。
607，PE3根据第五基准序列号、所述第七上行业务流、所述第九上行业务流和第十一上行业务流，获取第十二上行业务流并发送。
其中，实施例二中的第五基准序列号的初始值可为0。所述第五基准序列号的更新方法可参见实施例一中的更新方法，在此不再赘述。所述第十一上行业务流是PE2在获得第二上行业务流的同时获取的上行业务流。所述第十一上行业务流与实施例一中的第二上行业务流相同。所述第十一上行业务流可能是PE2接收到的来自CE1的上行业务流，或者是对PE2接收到的来自CE1的上行业务流进行复制后获得的业务流。
举例说明，PE3根据所述第五基准序列号获取所述第十二上行业务流的方法可参见实施例一中PE2获取第六上行业务流的方法。不同之处在于，实施例二中的PE3是对接收到的三条上行业务流进行排序和/或筛选，即对接收到的所述第七上行业务流、所述第九上行业务流和所述第十二上行业务流进行排序和/或筛选。PE3所采用的排序和/或筛选方法可参见实施例一中的507，在此不再赘述。
举例说明，PE3的下一跳为图4中的SPE3。PE3向SPE3发送所述第十二上行业务流的方法与实施例一中PE2发送所述第六上行业务流的方法相同，不同之处在于PE3向所述第十二上行业务流中的每个上行数据报文封装的PW label为PW23对应的PW label。实施例二中的第十二上行业务流与实施例一中的第六上行业务流是否相同取决于所述第七上行业务流、所述第九上行业务流和所述第十一业务流在进行序列号筛选的过程中被选出的上行数据报文，即所述第十二上行业务流可以与所述第六上行业务流相同，也可与所述第六上行业务流不同。
601至607为上行业务流的处理方法。601至607中，只要保证602和605先于606执行，603和604先于607执行即可，对于602、603、604和605之间的执行顺序，不限定于图6的顺序，602和604可同时执行，或者604先于602执行。603和605可以同时执行，或者605先于603执行。
608至613为下行业务流的处理方法。下面对下行业务流的处理方法进行说明。对于相似的部分，可参见上行业务流的处理方法。
608，PE1根据SPE1发送的下行业务流，获得第一下行业务流和第七下行业务流。
其中，PE1获得所述第七下行业务流的方法可参见602。PE1中的第二复制器13用于对SPE1发送的下行业务流进行复制，以获得所述第七下行业务流。所述第七下行业务流可以是来自SPE1的下行业务流，或者是对来自SPE1的下行业务流进行复制所获得的业务流。
609，PE1通过PW14，向PE3发送所述第七下行业务流。
如图4所示，所述第二复制器13将获得的所述第七下行业务流，通过PW14，发送至PE3包括的第六选择器34。
可选地，PE1可对所述第七下行业务流包括的下行数据报文进行MPLS封装，具体方法可参见PE1对第四下行业务流包括的下行数据报文进行封装的方法。不同之处在于，PE1对所述第七下行业务流包括的下行数据报文封装PW14对应的PW label。PE1可根据PW14对应的PW label，通过PW14发送所述第七下行业务流至PE3，具体方法可参见603。
610，PE3根据SPE3发送的下行业务流，获得第八下行业务流和第九下行业务流。
举例说明，PE3包括的第六复制器33可采用与第三复制器31相同的方法，进行下行业务流的复制，获得所述第七下行业务流和所述第八下行业务流。
其中，SPE3发送的下行业务流与SPE1发送的下行业务流可以是完全相同的下行业务流，也可以是不完全相同的下行业务流。在本申请实施例的处理下行业务流的方法中，基 于SPE3发送的下行业务流与SPE1发送的下行业务流完全相同的情况，对下行业务流的处理方法进行说明。对于SPE3发送的下行业务流与SPE1发送的下行业务流不完全相同的情况，可参照本申请实施例提供的序列号比较方法进行选择和/或丢弃操作，在此不再逐一举例说明。
611，PE3通过PW14，向PE1发送所述第八下行业务流。
其中，PE3的第六复制器33通过PW14向PE1发送所述第八下行业务流的方法与PE1的第二复制器13通过PW14向PE3发送所述第七下行业务流的方法相同，在此不再赘述。
所述第六复制器33对所述第八下行业务流包括的下行数据报文进行MPLS封装的方法可与所述第二复制器13采用的MPLS封装方法相同，在此不再赘述。不同之处在于，PE3对所述第八下行业务流包括的下行数据报文封装PW14对应的PW label。PE3可根据PW14对应的PW label，通过PW14发送所述第八下行业务流至PE1。
612，PE1根据第三基准序列号、所述第一下行业务流、所述第二下行业务流和所述第七下行业务流，获取第十下行业务流并发送。
其中，实施例二的第三基准序列号与实施例一的第三基准序列号相同。实施例三的第三基准序列号的更新方法与实施例一的更新方法相同。实施例二的PE1获取第十下行业务流的方法与实施例二的PE1获取第十上行业务流的方法相同。不同之处在于，实施例二中的PE1在获取所述第十下行业务流时参考第三基准序列号，不同于PE1在获取所述第十上行业务流所参考的第一基准序列号。
举例说明，PE1可通过AC11向CE1发送所述第十下行业务流，即所述第二选择器14可通过PE1与AC11连接的端口，向CE1发送所述第十下行业务流。可选地，PE1向CE1发送所述第十下行业务流之前，可将所述第十下行业务流包括的每个下行数据报文中的control word和PW label移除。
613，PE3根据第六基准序列号、所述第七下行业务流和所述第九下行业务流和第十一下行业务流，获取第十二下行业务流并发送。
其中，所述第六基准序列号是PE3上与下行业务流相关的序列号。所述第六基准序列号可根据PE3发送的下行数据报文包括的序列号进行更新。PE3根据所述第六基准序列号获取所述第十二下行业务流的方法，可参见PE3获取所述第十二上行业务流的方法。PE2的第六选择器34的功能与PE3的第五选择器32的功能相同，不同的是所述第六选择器34用于处理下行业务流，所述第五选择器32用于处理上行业务流。
举例说明，PE3可通过AC13向CE1发送所述第十二下行业务流，即所述第六选择器34可通过PE3与AC13连接的端口，向CE1发送所述第十二下行业务流。可选地，PE3向CE1发送所述第十二下行业务流之前，可将所述第十二下行业务流包括的每个下行数据报文中的control word和PW label移除。
608至613中，只要保证608和611先于612执行，609和610先于613执行即可。对于608、609、610和611之间的执行顺序，不限定于图6的顺序，608和610可同时执行，或者610先于608执行。609和611可以同时执行，或者611先于609执行。
图4中的PE2、PE3和CE1之间的交互流程可参见PE3、PE1和CE1之间的交互流程，在本申请实施例二提供的方法中不再赘述。
本申请实施例二提供的方法中，三台PE设备构成了一个网络设备组，该网络设备组中的任意两台PE设备能够实现对接收到的上行业务流或下行业务流进行可靠性保护，相 比于实施例一提供的方法，进一步提高了稳定性和可靠性。
图8为本申请实施例提供的一种分组网络中处理业务流的装置的结构示意图。图8所示的装置可以是本申请实施例提供的网络设备组中任一设备，比如上述方法中的PE1、PE2、SPE1、SPE2或PE3。本申请实施例提供的装置包括第一复制模块801和第一选择模块802。当所述装置为PE1时，所述第一复制模块801可以是第一复制器11，所述第一选择模块802可以是第一选择器12。当所述装置为PE2时，所述第一复制模块801可以是第三复制器21，所述第二选择模块802可以是第三选择器22。所述本申请实施例以所述装置设置于网络设备组包括的第一网络设备为例进行说明。
所述第一复制模块801用于获得第一上行业务流，所述第一上行业务流包括至少一个上行数据报文，所述第一上行业务流中的每个上行数据报文包括序列号，所述第一上行业务流中的每个上行数据报文包括的序列号用于标识其所在的上行数据报文在所述第一上行业务流中的顺序，所述第一上行业务流为所述第一网络设备接收到的来自所述第三网络设备的上行业务流，或者为所述第一网络设备对来自所述第三网络设备的上行业务流进行复制所获得的业务流。
所述第一选择模块802用于接收所述第二网络设备发送的第二上行业务流，所述第二上行业务流包括至少一个上行数据报文，所述第二上行业务流中的每个上行数据报文包括序列号，所述第二上行业务流中的每个上行数据报文包括的序列号用于标识其所在的上行数据报文在所述第二上行业务流中的顺序，所述第二上行业务流为所述第二网络设备接收到的来自所述第四网络设备的上行业务流，或者为所述第二网络设备对来自所述第四网络设备的上行业务流进行复制所获得的业务流。
所述第一选择模块802用于根据第一基准序列号和接收到的N个上行业务流中每个上行数据报文包括的序列号，获取第三上行业务流，所述第三上行业务流包括至少一个上行数据报文，所述N个上行业务流包括所述第一上行业务流和所述第二上行业务流，所述第三上行业务流中的任一上行数据报文包括的序列号大于所述第一基准序列号。
所述第一选择模块802用于向第五网络设备发送所述第三上行业务流。
可选地，所述第一复制模块801还用于：接收来自所述第三网络设备的上行业务流并对所述来自所述第三网络设备的上行业务流进行复制；通过所述第一伪线，向所述第二网络设备发送第四上行业务流，所述第四上行业务流为所述来自所述第三网络设备的上行业务流，或者为来自所述第三网络设备的上行业务流被复制后获得的业务流。
可选地，所述装置还包括第二复制模块803和第二选择模块804。当所述装置为PE1时，所述第二复制模块803可以为第二复制器13，所述第二选择模块804可以为第二选择器14。当所述装置为PE2时，所述第二复制模块803可以为第四复制器23，所述第二选择恶魔快804可以为第四选择器24。
所述第二复制模块803还用于获得第一下行业务流，所述第一下行业务流包括至少一个下行数据报文，所述第一下行业务流中的每个下行数据报文包括序列号，所述第一下行业务流中的每个下行数据报文包括的序列号用于标识其所在的下行数据报文在所述第一下行业务流中的顺序，所述第一下行业务流为所述第一网络设备接收到的来自所述第五网络设备的下行业务流，或者为所述第一网络设备对来自所述第五网络设备的下行业务流进行复制所获得的业务流。
所述第二选择模块804还用于通过第二伪线，接收所述第二网络设备发送的第二下行 业务流，所述第二下行业务流包括至少一个下行数据报文，所述第二下行业务流中的每个下行数据报文包括序列号，所述第二下行业务流中的每个下行数据报文包括的序列号用于标识其所在的下行数据报文在所述第二下行业务流中的顺序，所述第二下行业务流为所述第二网络设备接收到的来自第六网络设备的下行业务流，或者为所述第二网络设备对来自所述第六网络设备的下行业务流进行复制所获得的业务流。
所述第二选择模块804还用于根据第二基准序列号和接收到的M个下行业务流每个下行数据报文包括的序列号，获取第三下行业务流，所述M个下行业务流包括所述第一下行业务流和所述第二下行业务流，所述第三下行业务流包括至少一个下行数据报文，所述第三下行业务流中的任一下行数据报文包括的序列号大于所述第二基准序列号。
所述第二选择模块804还用于向所述第三网络设备发送所述第三下行业务流。
可选地，所述第二复制模块803还用于：接收来自所述第五网络设备的下行业务流并对所述来自所述第五网络设备的下行业务流进行复制；通过所述第二伪线，向所述第二网络设备发送第四下行业务流，所述第四下行业务流为所述来自所述第五网络设备的下行业务流，或者为来自所述第五网络设备的下行业务流被复制后获得的业务流。
举例说明，所述第一选择模块802具体用于：根据所述第一上行业务流中每个上行数据报文包括的序列号和所述第二上行业务流中每个上行数据报文包括的序列号，选择序列号的值大于所述第一基准序列号的多个上行数据报文，作为所述第三上行业务流，第i上行数据报文为所述第三上行业务流中任一上行数据报文，所述第i上行数据报文包括的序列号大于所述第一基准序列号，所述第i+1上行数据报文包括的序列号大于所述第i上行数据报文包括的序列号，所述第i+1上行数据报文在所述第三上行业务流中位于所述第i上行数据报文之后。
举例说明，所述第一选择模块802具体用于：根据所述第一上行业务流中每个上行数据报文的到达时刻和所述第二上行业务流中每个上行数据报文的到达时刻，对所述第一上行业务流包括的上行数据报文和所述第二上行业务流包括的上行数据报文进行排序，获得排序后的上行业务流；从所述排序后的上行业务流中，选择序列号的值大于所述第一基准序列号的多个上行数据报文，作为所述第三上行业务流，所述第三上行业务流中第i上行数据报文包括的序列号大于所述第一基准序列号，所述第三上行业务流中第i+1上行数据报文的到达时刻晚于所述第i上行数据报文，且所述第i+1上行数据报文包括的序列号大于所述第i上行数据报文包括的序列号，所述第i上行数据报文为所述第三上行业务流中任一上行数据报文。
举例说明，所述第二选择模块804具体用于：根据所述第一下行业务流中每个下行数据报文包括的序列号和所述第二下行业务流中每个下行数据报文包括的序列号，选择序列号的值大于所述第二基准序列号的多个下行数据报文，作为所述第三下行业务流，第j下行数据报文为所述第三下行业务流中任一下行数据报文，所述第j下行数据报文包括的序列号大于所述第二基准序列号，所述第j+1下行数据报文包括的序列号大于所述第j下行数据报文包括的序列号，所述第j+1下行数据报文在所述第三下行业务流中位于所述第j下行数据报文之后。
举例说明，所述第二选择模块804具体用于：根据所述第一下行业务流中每个下行数据报文的到达时刻和所述第二下行业务流中每个下行数据报文的到达时刻，对所述第一下行业务流包括的下行数据报文和所述第二下行业务流包括的下行数据报文进行排序，获得 排序后的下行业务流；从所述排序后的下行业务流中，选择序列号的值大于所述第二基准序列号的多个下行数据报文，作为所述第三下行业务流，所述第三下行业务流中第j下行数据报文包括的序列号大于所述第二基准序列号，所述第三下行业务流中第j+1下行数据报文的到达时刻晚于所述第j下行数据报文，且所述第j+1下行数据报文包括的序列号大于所述第j下行数据报文包括的序列号，所述第j下行数据报文为所述第三下行业务流中任一下行数据报文。
可选地，所述第一选择模块802还用于用所述第三上行业务流中的上行数据报文所包括的序列号的最大值，更新所述第一基准序列号的数值。
可选地，所述第二选择模块804还用于用所述第三下行业务流中的下行数据报文所包括的序列号的最大值，更新所述第二基准序列号的数值。
可选地，所述第一复制器模块801和/或所述第二复制模块803可设置于所述装置的物理端口的接收处理逻辑模块。所述第一选择模块802和所述第二选择模块804可设置于所述装置的物理端口的发送处理逻辑模块。
可选地，当所述第一网络设备为PE设备，所述第三网络设备为CE设备，所述第一复制模块801具体用于：接收来自所述第三网络设备的以太帧；根据所述以太帧，获得序列号；根据所述以太帧和所述序列号，获得所述第一上行业务流包括的上行数据报文，所述上行数据报文包括所述以太帧和所述序列号。
其中，所述第一复制模块801可具体用于对接收到的以太帧进行计算，以获得所述序列号。或者，所述第一复制模块801可具体用于从所述以太帧中获得所述以太帧携带的序列号。
在另一种实现方式中，所述第一复制模块801还可包括序列号生成模块(图8中未示出)。所述序列号生成模块可在接收到一个以太帧时产生一个序列号，以便所述第一复制模块801将所述序列号生成模块产生的序列号添加至所述第一上行业务流的上行数据报文。可选地，所述序列号生成模块可有序列号发生器来实现。
图9为本申请实施例提供的另一种分组网络中处理业务流的装置的结构示意图。图9所示的装置可以是与图8所示的装置相同。图9可以是图2、图3或图4所示的网络场景中网络设备组所包括的任一设备。该实施例的装置可以执行图5或图6对应的实施例中任一PE所采用的方法。该实施例提供的装置包括：处理器901、存储器902和通信接口903。所述处理器901、所述存储器902和所述通信接口903通过通信总线904连接。所述存储器902用于存储程序。所述处理器901根据从所述存储器902中读取的程序所包括的可执行指令，执行上述图5或图6对应的实施例中任一PE所执行的方法步骤。
举例说明，所述处理器901用于实现图5或图6对应的实施例中任一PE所具有的复制功能和选择功能。所述处理器901可通过通信接口903收发上行数据报文和/或下行数据报文。可选地，存储器902还可用于存储图5或图6对应的实施例中的映射表和状态表。
本申请实施例还提供了一种分组网络中处理业务流的系统。该系统可包括上述方法中的网络设备组。所述网络设备组包括的任一设备可采用图8或图9的结构，在此不再赘述。
本申请实施例提供的上述方法和装置中，网络设备组的任一设备可根据转发的需要，在图7所示的封装基础上，进一步压入用来指导转发的MPLS LSP label。对于压入MPLS LSP label的具体方法，不再进行赘述。此外，本申请实施例中提及的网络设备组以及网络设备组间的PW的配置，可在执行图5或图6的方法之前完成，可通过下发响应的配置信 息或转发表项，使得图2、图3或图4中的任一设备获知其自身所对应的保护链路和保护设备，本申请实施例中不再对此进行赘述。
本申请实施例中所提及的通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器。结合本发明实施例所公开的方法的步骤，可以直接体现为处理器中的硬件及软件模块组合执行完成。当使用软件实现时，可以将实现上述功能的代码存储在计算机可读介质中。计算机可读介质包括计算机存储介质。存储介质可以是计算机能够存取的任何可用介质。以此为例但不限于：计算机可读介质可以是随机存取存储器(英文全称为random-access memory，英文缩写为RAM)、只读存储器(英文全称为read-only memory，英文缩写为ROM)、电可擦可编程只读存储器(英文全称为electrically erasable programmable read-only memory，英文缩写为EEPROM)、只读光盘(英文全称为compact disk read-only memory，英文缩写为CD-ROM)或其他光盘存储、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质。计算机可读介质可以是压缩碟(英文全称为compact disk，英文缩写为CD)、激光碟、数字视频光碟(英文全称为digital video disk，英文缩写为DVD)、软盘或者蓝光碟。
本说明书中的各个实施例均采用递进的方式描述，各个实施例之间相同相似的部分互相参见即可，每个实施例重点说明的都是与其他实施例的不同之处。尤其，对于系统实施例而言，由于其基本相似于方法实施例，所以描述的比较简单，相关之处参见方法实施例的部分说明即可。
以上所述，仅为本发明的具体实施方式，但本发明的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本发明揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本发明的保护范围之内。因此，本发明的保护范围应以所述权利要求的保护范围为准。

Claims (22)

  1. 一种分组网络中处理业务流的方法，所述方法应用于一个网络设备组，所述网络设备组包括第一网络设备和第二网络设备，所述第一网络设备与所述第二网络设备连接，所述第一网络设备和第三网络设备通信，所述第二网络设备与第四网络设备通信，其特征在于，所述方法包括：
    所述第一网络设备获得第一上行业务流，所述第一上行业务流包括至少一个上行数据报文，所述第一上行业务流中的每个上行数据报文包括序列号，所述第一上行业务流中的每个上行数据报文包括的序列号用于标识其所在的上行数据报文在所述第一上行业务流中的顺序，所述第一上行业务流为所述第一网络设备接收到的来自所述第三网络设备的上行业务流，或者为所述第一网络设备对来自所述第三网络设备的上行业务流进行复制所获得的业务流；
    所述第一网络设备通过第一伪线，接收所述第二网络设备发送的第二上行业务流，所述第二上行业务流包括至少一个上行数据报文，所述第二上行业务流中的每个上行数据报文包括序列号，所述第二上行业务流中的每个上行数据报文包括的序列号用于标识其所在的上行数据报文在所述第二上行业务流中的顺序，所述第二上行业务流为所述第二网络设备接收到的来自所述第四网络设备的上行业务流，或者为所述第二网络设备对来自所述第四网络设备的上行业务流进行复制所获得的业务流；
    所述第一网络设备根据第一基准序列号和接收到的N个上行业务流中每个上行数据报文包括的序列号，获取第三上行业务流，所述第三上行业务流包括至少一个上行数据报文，所述N个上行业务流包括所述第一上行业务流和所述第二上行业务流，所述第三上行业务流中的任一上行数据报文包括的序列号大于所述第一基准序列号；
    所述第一网络设备向第五网络设备发送所述第三上行业务流。
  2. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    所述第一网络设备接收来自所述第三网络设备的上行业务流并对所述来自所述第三网络设备的上行业务流进行复制；
    所述第一网络设备通过所述第一伪线，向所述第二网络设备发送第四上行业务流，所述第四上行业务流为所述来自所述第三网络设备的上行业务流，或者为来自所述第三网络设备的上行业务流被复制后获得的业务流。
  3. 根据权利要求1或2所述的方法，其特征在于，所述方法还包括：
    所述第一网络设备获得第一下行业务流，所述第一下行业务流包括至少一个下行数据报文，所述第一下行业务流中的每个下行数据报文包括序列号，所述第一下行业务流中的每个下行数据报文包括的序列号用于标识其所在的下行数据报文在所述第一下行业务流中的顺序，所述第一下行业务流为所述第一网络设备接收到的来自所述第五网络设备的下行业务流，或者为所述第一网络设备对来自所述第五网络设备的下行业务流进行复制所获得的业务流；
    所述第一网络设备通过第二伪线，接收所述第二网络设备发送的第二下行业务流，所述第二下行业务流包括至少一个下行数据报文，所述第二下行业务流中的每个下行数据报文包括序列号，所述第二下行业务流中的每个下行数据报文包括的序列号用于标识其所在的下行数据报文在所述第二下行业务流中的顺序，所述第二下行业务流为所述第二网络设备接收到的来自第六网络设备的下行业务流，或者为所述第二网络设备对来自所述第六网 络设备的下行业务流进行复制所获得的业务流；
    所述第一网络设备根据第二基准序列号和接收到的M个下行业务流每个下行数据报文包括的序列号，获取第三下行业务流，所述M个下行业务流包括所述第一下行业务流和所述第二下行业务流，所述第三下行业务流包括至少一个下行数据报文，所述第三下行业务流中的任一下行数据报文包括的序列号大于所述第二基准序列号；
    所述第一网络设备向所述第三网络设备发送所述第三下行业务流。
  4. 根据权利要求2所述的方法，其特征在于，所述方法还包括：
    所述第一网络设备接收来自所述第五网络设备的下行业务流并对所述来自所述第五网络设备的下行业务流进行复制；
    所述第一网络设备通过所述第二伪线，向所述第二网络设备发送第四下行业务流，所述第四下行业务流为所述来自所述第五网络设备的下行业务流，或者为来自所述第五网络设备的下行业务流被复制后获得的业务流。
  5. 根据权利要求1至4任一所述的方法，其特征在于，所述第一网络设备根据第一基准序列号和接收到的N个上行业务流中每个上行数据报文包括的序列号，获取第三上行业务流包括：
    所述第一网络设备根据所述第一上行业务流中每个上行数据报文包括的序列号和所述第二上行业务流中每个上行数据报文包括的序列号，选择序列号的值大于所述第一基准序列号的多个上行数据报文，作为所述第三上行业务流，第i上行数据报文为所述第三上行业务流中任一上行数据报文，所述第i上行数据报文包括的序列号大于所述第一基准序列号，所述第i+1上行数据报文包括的序列号大于所述第i上行数据报文包括的序列号，所述第i+1上行数据报文在所述第三上行业务流中位于所述第i上行数据报文之后。
  6. 根据权利要求1至4任一所述的方法，其特征在于，所述第一网络设备根据第一基准序列号和接收到的N个上行业务流中每个上行数据报文包括的序列号，获取第三上行业务流包括：
    所述第一网络设备根据所述第一上行业务流中每个上行数据报文的到达时刻和所述第二上行业务流中每个上行数据报文的到达时刻，对所述第一上行业务流包括的上行数据报文和所述第二上行业务流包括的上行数据报文进行排序，获得排序后的上行业务流；
    所述第一网络设备从所述排序后的上行业务流中，选择序列号的值大于所述第一基准序列号的多个上行数据报文，作为所述第三上行业务流，所述第三上行业务流中第i上行数据报文包括的序列号大于所述第一基准序列号，所述第三上行业务流中第i+1上行数据报文的到达时刻晚于所述第i上行数据报文，且所述第i+1上行数据报文包括的序列号大于所述第i上行数据报文包括的序列号，所述第i上行数据报文为所述第三上行业务流中任一上行数据报文。
  7. 根据权利要求3或4所述的方法，其特征在于，所述第一网络设备根据第二基准序列号和接收到的M个下行业务流中每个下行数据报文包括的序列号，获取第三下行业务流包括：
    所述第一网络设备根据所述第一下行业务流中每个下行数据报文包括的序列号和所述第二下行业务流中每个下行数据报文包括的序列号，选择序列号的值大于所述第二基准序列号的多个下行数据报文，作为所述第三下行业务流，第j下行数据报文为所述第三下行业务流中任一下行数据报文，所述第j下行数据报文包括的序列号大于所述第二基准序 列号，所述第j+1下行数据报文包括的序列号大于所述第j下行数据报文包括的序列号，所述第j+1下行数据报文在所述第三下行业务流中位于所述第j下行数据报文之后。
  8. 根据权利要求3或4所述的方法，其特征在于，所述第一网络设备根据第二基准序列号和接收到的M个下行业务流每个下行数据报文包括的序列号，获取第三下行业务流包括：
    所述第一网络设备根据所述第一下行业务流中每个下行数据报文的到达时刻和所述第二下行业务流中每个下行数据报文的到达时刻，对所述第一下行业务流包括的下行数据报文和所述第二下行业务流包括的下行数据报文进行排序，获得排序后的下行业务流；
    所述第一网络设备从所述排序后的下行业务流中，选择序列号的值大于所述第二基准序列号的多个下行数据报文，作为所述第三下行业务流，所述第三下行业务流中第j下行数据报文包括的序列号大于所述第二基准序列号，所述第三下行业务流中第j+1下行数据报文的到达时刻晚于所述第j下行数据报文，且所述第j+1下行数据报文包括的序列号大于所述第j下行数据报文包括的序列号，所述第j下行数据报文为所述第三下行业务流中任一下行数据报文。
  9. 根据权利要求1至8任一所述的方法，其特征在于，所述方法还包括：
    所述第一网络设备用所述第三上行业务流中的上行数据报文所包括的序列号的最大值，更新所述第一基准序列号的数值。
  10. 根据权利要求1至9任一所述的方法，其特征在于，所述方法还包括：
    所述第一网络设备用所述第三下行业务流中的下行数据报文所包括的序列号的最大值，更新所述第二基准序列号的数值。
  11. 根据权利要求1至10任一所述的方法，其特征在于，所述第一网络设备为第一运营商边缘PE设备，所述第二网络设备为第二PE设备，所述第三网络设备为用户边缘CE设备，所述第四网络设备为所述CE设备；或者
    所述第一网络设备为第一多跳伪线中的交换节点SPE，所述第二网络设备为第二SPE，所述第三网络设备为第一PE设备，所述第四网络设备为第二PE设备，所述第一PE设备和所述第二PE设备与同一CE设备通信；或者
    所述第一网络设备为第一SPE，所述第二网络设备为第二SPE，所述第三网络设备为第一PE设备，所述第四网络设备为第二PE设备，所述第一PE设备和所述第二PE设备属于一个网络设备组；或者
    所述第一网络设备为第一SPE，所述第二网络设备为第二SPE，所述第三网络设备为第一PE设备，所述第四网络设备为第二PE设备，所述第一PE设备和所述第二PE设备属于一个网络设备组，所述第一PE设备和所述第二PE设备与同一CE设备通信。
  12. 根据权利要求11所述的方法，其特征在于，所述第五网络设备和所述第六网络设备为相同的PE设备，或者所述第五网络设备和所述第六网络设备为不同的PE设备，或者所述第五网络设备和所述第六网络设备为不同的SPE。
  13. 一种分组网络中处理业务流的装置，所述装置设置于网络设备组中的第一网络设备，所述网络设备组还包括第二网络设备，所述第一网络设备与所述第二网络设备连接，所述第一网络设备和第三网络设备通信，所述第二网络设备与第四网络设备通信，其特征在于，所述装置包括第一复制模块和第一选择模块；
    所述第一复制模块用于获得第一上行业务流，所述第一上行业务流包括至少一个上行 数据报文，所述第一上行业务流中的每个上行数据报文包括序列号，所述第一上行业务流中的每个上行数据报文包括的序列号用于标识其所在的上行数据报文在所述第一上行业务流中的顺序，所述第一上行业务流为所述第一网络设备接收到的来自所述第三网络设备的上行业务流，或者为所述第一网络设备对来自所述第三网络设备的上行业务流进行复制所获得的业务流；
    所述第一选择模块用于接收所述第二网络设备发送的第二上行业务流，所述第二上行业务流包括至少一个上行数据报文，所述第二上行业务流中的每个上行数据报文包括序列号，所述第二上行业务流中的每个上行数据报文包括的序列号用于标识其所在的上行数据报文在所述第二上行业务流中的顺序，所述第二上行业务流为所述第二网络设备接收到的来自所述第四网络设备的上行业务流，或者为所述第二网络设备对来自所述第四网络设备的上行业务流进行复制所获得的业务流；
    所述第一选择模块用于根据第一基准序列号和接收到的N个上行业务流中每个上行数据报文包括的序列号，获取第三上行业务流，所述第三上行业务流包括至少一个上行数据报文，所述N个上行业务流包括所述第一上行业务流和所述第二上行业务流，所述第三上行业务流中的任一上行数据报文包括的序列号大于所述第一基准序列号；
    所述第一选择模块用于向第五网络设备发送所述第三上行业务流。
  14. 根据权利要求13所述的装置，其特征在于，所述第一复制模块还用于：
    接收来自所述第三网络设备的上行业务流并对所述来自所述第三网络设备的上行业务流进行复制；
    通过所述第一伪线，向所述第二网络设备发送第四上行业务流，所述第四上行业务流为所述来自所述第三网络设备的上行业务流，或者为来自所述第三网络设备的上行业务流被复制后获得的业务流。
  15. 根据权利要求13或14所述的装置，其特征在于，所述装置还包括第二复制模块和第二选择模块；
    所述第二复制模块还用于获得第一下行业务流，所述第一下行业务流包括至少一个下行数据报文，所述第一下行业务流中的每个下行数据报文包括序列号，所述第一下行业务流中的每个下行数据报文包括的序列号用于标识其所在的下行数据报文在所述第一下行业务流中的顺序，所述第一下行业务流为所述第一网络设备接收到的来自所述第五网络设备的下行业务流，或者为所述第一网络设备对来自所述第五网络设备的下行业务流进行复制所获得的业务流；
    所述第二选择模块还用于通过第二伪线，接收所述第二网络设备发送的第二下行业务流，所述第二下行业务流包括至少一个下行数据报文，所述第二下行业务流中的每个下行数据报文包括序列号，所述第二下行业务流中的每个下行数据报文包括的序列号用于标识其所在的下行数据报文在所述第二下行业务流中的顺序，所述第二下行业务流为所述第二网络设备接收到的来自第六网络设备的下行业务流，或者为所述第二网络设备对来自所述第六网络设备的下行业务流进行复制所获得的业务流；
    所述第二选择模块还用于根据第二基准序列号和接收到的M个下行业务流每个下行数据报文包括的序列号，获取第三下行业务流，所述M个下行业务流包括所述第一下行业务流和所述第二下行业务流，所述第三下行业务流包括至少一个下行数据报文，所述第三下行业务流中的任一下行数据报文包括的序列号大于所述第二基准序列号；
    所述第二选择模块还用于向所述第三网络设备发送所述第三下行业务流。
  16. 根据权利要求14所述的装置，其特征在于，所述第二复制模块还用于：
    接收来自所述第五网络设备的下行业务流并对所述来自所述第五网络设备的下行业务流进行复制；
    通过所述第二伪线，向所述第二网络设备发送第四下行业务流，所述第四下行业务流为所述来自所述第五网络设备的下行业务流，或者为来自所述第五网络设备的下行业务流被复制后获得的业务流。
  17. 根据权利要求13至16任一所述的装置，其特征在于，所述第一选择模块具体用于：
    根据所述第一上行业务流中每个上行数据报文包括的序列号和所述第二上行业务流中每个上行数据报文包括的序列号，选择序列号的值大于所述第一基准序列号的多个上行数据报文，作为所述第三上行业务流，第i上行数据报文为所述第三上行业务流中任一上行数据报文，所述第i上行数据报文包括的序列号大于所述第一基准序列号，所述第i+1上行数据报文包括的序列号大于所述第i上行数据报文包括的序列号，所述第i+1上行数据报文在所述第三上行业务流中位于所述第i上行数据报文之后。
  18. 根据权利要求13至16任一所述的装置，其特征在于，所述第一选择模块具体用于：
    根据所述第一上行业务流中每个上行数据报文的到达时刻和所述第二上行业务流中每个上行数据报文的到达时刻，对所述第一上行业务流包括的上行数据报文和所述第二上行业务流包括的上行数据报文进行排序，获得排序后的上行业务流；
    从所述排序后的上行业务流中，选择序列号的值大于所述第一基准序列号的多个上行数据报文，作为所述第三上行业务流，所述第三上行业务流中第i上行数据报文包括的序列号大于所述第一基准序列号，所述第三上行业务流中第i+1上行数据报文的到达时刻晚于所述第i上行数据报文，且所述第i+1上行数据报文包括的序列号大于所述第i上行数据报文包括的序列号，所述第i上行数据报文为所述第三上行业务流中任一上行数据报文。
  19. 根据权利要求15或16所述的装置，其特征在于，所述第二选择模块具体用于：
    根据所述第一下行业务流中每个下行数据报文包括的序列号和所述第二下行业务流中每个下行数据报文包括的序列号，选择序列号的值大于所述第二基准序列号的多个下行数据报文，作为所述第三下行业务流，第j下行数据报文为所述第三下行业务流中任一下行数据报文，所述第j下行数据报文包括的序列号大于所述第二基准序列号，所述第j+1下行数据报文包括的序列号大于所述第j下行数据报文包括的序列号，所述第j+1下行数据报文在所述第三下行业务流中位于所述第j下行数据报文之后。
  20. 根据权利要求15或16所述的装置，其特征在于，所述第二选择模块具体用于：
    根据所述第一下行业务流中每个下行数据报文的到达时刻和所述第二下行业务流中每个下行数据报文的到达时刻，对所述第一下行业务流包括的下行数据报文和所述第二下行业务流包括的下行数据报文进行排序，获得排序后的下行业务流；
    从所述排序后的下行业务流中，选择序列号的值大于所述第二基准序列号的多个下行数据报文，作为所述第三下行业务流，所述第三下行业务流中第j下行数据报文包括的序列号大于所述第二基准序列号，所述第三下行业务流中第j+1下行数据报文的到达时刻晚于所述第j下行数据报文，且所述第j+1下行数据报文包括的序列号大于所述第j下行数据 报文包括的序列号，所述第j下行数据报文为所述第三下行业务流中任一下行数据报文。
  21. 根据权利要求13至20任一所述的装置，其特征在于，
    所述第一选择模块还用于用所述第三上行业务流中的上行数据报文所包括的序列号的最大值，更新所述第一基准序列号的数值。
  22. 根据权利要求13至21任一所述的装置，其特征在于，
    所述第二选择模块还用于用所述第三下行业务流中的下行数据报文所包括的序列号的最大值，更新所述第二基准序列号的数值。
PCT/CN2018/074799 2017-02-20 2018-01-31 一种分组网络中处理业务流的方法及装置 WO2018149294A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
EP21208706.8A EP4054155A1 (en) 2017-02-20 2018-01-31 Method and apparatus for processing service flow in packet network
EP18754372.3A EP3573288B1 (en) 2017-02-20 2018-01-31 Method and system for processing service flow in packet network
US16/545,218 US11201826B2 (en) 2017-02-20 2019-08-20 Method and apparatus for processing service flow in packet network
US17/528,555 US11909659B2 (en) 2017-02-20 2021-11-17 Method and apparatus for processing service flow in packet network

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710090953.5A CN108462591B (zh) 2017-02-20 2017-02-20 一种分组网络中处理业务流的方法及装置
CN201710090953.5 2017-02-20

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/545,218 Continuation US11201826B2 (en) 2017-02-20 2019-08-20 Method and apparatus for processing service flow in packet network

Publications (1)

Publication Number Publication Date
WO2018149294A1 true WO2018149294A1 (zh) 2018-08-23

Family

ID=63169723

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/074799 WO2018149294A1 (zh) 2017-02-20 2018-01-31 一种分组网络中处理业务流的方法及装置

Country Status (4)

Country Link
US (2) US11201826B2 (zh)
EP (2) EP3573288B1 (zh)
CN (2) CN111555976A (zh)
WO (1) WO2018149294A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113179172A (zh) * 2020-01-24 2021-07-27 华为技术有限公司 故障检测模型的训练方法、装置及系统

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113114564A (zh) 2018-10-31 2021-07-13 华为技术有限公司 一种业务流处理方法及装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101257441A (zh) * 2008-02-29 2008-09-03 华为技术有限公司 转发报文的方法、设备、系统和接收报文的设备
US8724452B2 (en) * 2010-12-30 2014-05-13 Eci Telecom Ltd. Technique for protecting communication traffic in a connection having redundancy
US8724456B1 (en) * 2010-05-19 2014-05-13 Juniper Networks, Inc. Network path selection for multi-homed edges to ensure end-to-end resiliency
CN105991359A (zh) * 2015-02-06 2016-10-05 中兴通讯股份有限公司 一种检测重复仿真报文的方法及装置

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7417950B2 (en) * 2003-02-03 2008-08-26 Ciena Corporation Method and apparatus for performing data flow ingress/egress admission control in a provider network
JP4593484B2 (ja) * 2006-02-03 2010-12-08 アラクサラネットワークス株式会社 データ通信システムおよびその方法
JP4796184B2 (ja) * 2007-03-28 2011-10-19 富士通株式会社 エッジノード冗長システム
CN101330424B (zh) * 2007-06-18 2011-11-02 华为技术有限公司 一种虚拟专用网服务故障处理的方法、系统及装置
CN101902353B (zh) * 2009-05-31 2013-06-12 华为技术有限公司 分组网络的保护方法
CN102215098B (zh) * 2010-04-09 2014-04-16 华为技术有限公司 对客户端设备的业务数据进行传输的方法、装置和系统
US9544927B2 (en) * 2012-07-02 2017-01-10 Alcatel Lucent System, method and computer readable medium for bearer activation in a core network for wireless devices
US9118571B2 (en) * 2013-07-08 2015-08-25 Telefonaktiebolaget L M Ericsson (Publ) Methods of operating load balancing switches and controllers using matching patterns with unrestricted characters

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101257441A (zh) * 2008-02-29 2008-09-03 华为技术有限公司 转发报文的方法、设备、系统和接收报文的设备
US8724456B1 (en) * 2010-05-19 2014-05-13 Juniper Networks, Inc. Network path selection for multi-homed edges to ensure end-to-end resiliency
US8724452B2 (en) * 2010-12-30 2014-05-13 Eci Telecom Ltd. Technique for protecting communication traffic in a connection having redundancy
CN105991359A (zh) * 2015-02-06 2016-10-05 中兴通讯股份有限公司 一种检测重复仿真报文的方法及装置

Non-Patent Citations (1)

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

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113179172A (zh) * 2020-01-24 2021-07-27 华为技术有限公司 故障检测模型的训练方法、装置及系统

Also Published As

Publication number Publication date
EP4054155A1 (en) 2022-09-07
US20220158947A1 (en) 2022-05-19
CN111555976A (zh) 2020-08-18
CN108462591B (zh) 2020-04-14
EP3573288A1 (en) 2019-11-27
CN108462591A (zh) 2018-08-28
EP3573288B1 (en) 2021-12-22
US11201826B2 (en) 2021-12-14
US20190379608A1 (en) 2019-12-12
US11909659B2 (en) 2024-02-20
EP3573288A4 (en) 2020-01-22

Similar Documents

Publication Publication Date Title
US10122614B2 (en) Failure protection for traffic-engineered bit indexed explicit replication
US9781032B1 (en) MPLS label usage in ethernet virtual private networks
US9509591B2 (en) Technique for dual homing interconnection between communication networks
US7269132B1 (en) Method and apparatus for achieving transparent redundancy at a hierarchical boundary
JP4729119B2 (ja) ラベルスイッチングネットワークにおける通信装置
CN101257441B (zh) 转发报文的方法、设备、系统和接收报文的设备
JP5484590B2 (ja) 擬似ワイヤに基づいてサービストラヒックを処理するための方法、デバイスおよびシステム
CN101159690B (zh) 多协议标签交换转发方法、装置及标签交换路径管理模块
US20130272114A1 (en) Pseudo wire switching method and device
JP5168230B2 (ja) 通信システム、エッジルータ及び信号転送方法
US20090225650A1 (en) Path reroute in a computer network
WO2011060667A1 (zh) 一种虚拟专用局域网络中链路保护的方法及设备
CN101999224A (zh) 对虚拟专用lan业务的冗余的以太网自动保护切换接入
WO2012075831A1 (zh) 一种实现组播保护的方法及系统
WO2012130034A1 (zh) 一种vpls快速重路由方法和设备
JP7168286B2 (ja) 通信方法および通信装置
US20220158947A1 (en) Method and Apparatus for Processing Service Flow in Packet Network
WO2016023278A1 (zh) 一种网络保护倒换方法、网络设备及存储介质
GB2448711A (en) Recovering from a failure in a communications network
CN104702431B (zh) 一种虚拟专用网双断保护的方法及装置
WO2008095360A1 (fr) Méthode et système de commutation rapide en cas de défaillance d'une liaison d'un réseau privé virtuel
WO2020119474A1 (zh) 通信方法和装置
CN101888339B (zh) 一种基于mpls-tp的环网抄近保护方法
WO2011020339A1 (zh) 一种分段保护中的切换方法及系统
JP2010200269A (ja) 通信装置、パケット送受信装置、通信方法、及びプログラム

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2018754372

Country of ref document: EP

Effective date: 20190821