WO2016107156A1

WO2016107156A1 - End-to-end monitoring method and device for bridge network

Info

Publication number: WO2016107156A1
Application number: PCT/CN2015/085103
Authority: WO
Inventors: 王月梅; 刘爱华
Original assignee: 中兴通讯股份有限公司
Priority date: 2014-12-31
Filing date: 2015-07-24
Publication date: 2016-07-07

Abstract

Disclosed is an end-to-end monitoring method for a bridge network. The method comprises: generating OAM packet characteristic information and a packet format; identifying an OAM packet according to the generated OAM packet characteristic information; and executing an OAM function according to the generated packet format to complete end-to-end OAM monitoring for a bridge network. Also disclosed is an end-to-end monitoring device for a bridge network. The present invention is simple and easy to implement, L2VPN and L3VPN bridge networks can be directly crossed, end-to-end OAM fault detection and performance measurement can be flexibly implemented, and service monitoring can be conveniently and rapidly implemented.

Description

Bridge network end-to-end monitoring method and device

Technical field

The present invention relates to the field of network detection, and in particular, to a method and apparatus for monitoring end-to-end of a bridge network.

Background technique

In a hierarchical network structure, the network is usually divided into: an access layer, an aggregation layer, and a core layer. As shown in FIG. 1 , the aggregation layer or the access layer is deployed as an L2VPN (Layer 2 Virtual Private Network), and the core layer is deployed as a Layer 3 Virtual Private Network (Layer 3 Virtual Private Network).

In the related art, the L2VPN mainly adopts the MPLS-TP (Muti-protocol label switching-transport profile) OAM (Operation Administration and Maintenance) and Ethernet OAM detection. In L3VPN, MPLS-TP OAM and IP layer OAM mechanisms are adopted. For L2VPN and L3VPN bridging networking scenarios (the access layer generally uses L2VPN networking, the aggregation or core layer generally adopts L3VPN networking, the bearer service traverses L2VPN and L3VPN networks, and the L2VPN and L3VPN borders have bridge devices to complete L2VPN and L3VPN services. The MPLS-TP OAM does not provide the OAM function of the end-to-end bearer service of the L2L3 network. The existing L2VPN end-to-end OAM mechanism (such as the Ethernet service OAM mechanism) cannot traverse the L3VPN network; and the L3VPN end-to-end OAM mechanism (such as IP ping) does not support the L2VPN network; resulting in the L2+L3 group. In the network, OAM can only be deployed in segments. However, this type of deployment cannot quickly and uniformly perform fault detection and performance measurement of the OAM from the edge node of the L2VPN network to the edge node of the L3VPN network (the UNI side, that is, the user network interface side) and the network intermediate node (the NNI side, that is, the network interface side). (such as connectivity, packet loss rate, frame delay, throughput, etc.); in addition, this segmented OAM deployment mode has complex OAM management and poor fault location and ease of use. Therefore, how to locate the internal fault of L2L3 bridge and how to implement L2VPN network or L3VPN network, how to achieve unified end-to-end OAM fault detection and performance measurement is an urgent problem to be solved.

Summary of the invention

The main purpose of the embodiments of the present invention is to provide a network end-to-end monitoring method and device, which aims to solve the problem that the connectivity of the OAM detection link in the L2VPN and the L3VPN bridge network is poor and cannot be detected. The connectivity of the L2VPN network access device cannot detect the connectivity of the link across the L2VPN network or the L3VPN network, and cannot detect the internal fault of the L2L3 bridge.

To achieve the above object, an embodiment of the present invention provides an end-to-end monitoring method for a bridge network, where the monitoring method of the bridge network end-to-end includes:

Generate OAM packet feature information and packet format.

Identifying an OAM packet according to the generated OAM packet feature information;

According to the generated packet format, the OAM function is executed to complete the end-to-end OAM monitoring of the bridged network.

In the embodiment of the present invention, the step of generating the OAM packet feature information and the packet format includes:

According to the bridged network, the operation management and maintenance OAM model is constructed, and the maintenance endpoint MEP/maintenance intermediate point MIP node and the OAM function set are defined.

In the embodiment of the present invention, the performing the OAM function according to the generated packet format, and completing the end-to-end OAM monitoring of the bridge network includes:

Select the OAM function in the OAM function set;

Encapsulating OAM packets according to the selected OAM function and the defined packet format;

The encapsulated OAM message is sent to the target MEP or MIP node.

In the embodiment of the present invention, after the step of identifying the OAM packet according to the generated OAM packet feature information, the method further includes:

The device determines whether the received packet is an OAM packet according to the characteristic information of the OAM packet.

After the step of determining whether the received packet is an OAM packet according to the OAM packet feature information, the method further includes:

If it is determined that the received packet is an OAM packet, it is determined whether the current node needs to be processed;

If the current node processing is not required, the OAM message is forwarded to the next node of the bridged network.

In order to solve the above technical problem, an embodiment of the present invention further provides an end-to-end monitoring device for a bridge network, where the bridge network end-to-end monitoring device includes:

The generating module is configured to generate OAM packet feature information and a packet format.

The identification module is configured to identify the OAM packet according to the generated OAM packet feature information;

The execution module is configured to perform OAM function according to the generated packet format, and complete end-to-end OAM monitoring of the bridge network.

In the embodiment of the present invention, the monitoring device for bridging the network end-to-end further includes:

The build module is set to build an OAM model based on the bridged network, defining the MEP/MIP node and the OAM feature set.

In the embodiment of the present invention, the execution module includes:

The selected unit is set to the OAM function in the selected OAM function set;

The encapsulating unit is configured to encapsulate the OAM packet according to the selected OAM function and the defined packet format;

The sending unit is configured to send the encapsulated OAM message to the target MEP or MIP node.

The determining module is configured to determine whether the received packet is an OAM packet according to the characteristic information of the OAM packet.

The forwarding module is configured to determine whether the received packet is an OAM packet, and then determines whether the current node needs to be processed. If the current node processing is not required, the OAM packet is forwarded to the next node of the bridge network.

The end-to-end monitoring method of the bridge network provided by the embodiment of the present invention generates the OAM packet feature information and the packet format, identifies the OAM packet according to the generated OAM packet feature information, and performs the OAM function according to the generated packet format. , complete end-to-end OAM monitoring of the bridge network. The invention is simple and easy to use, and can directly bridge the network through the L2VPN and the L3VPN; the end-to-end OAM fault detection and performance measurement can be flexibly implemented, and the service monitoring can be realized conveniently and quickly.

DRAWINGS

Figure 1 is a schematic diagram of an existing L2VPN and L3VPN bridge network;

2 is a schematic diagram of networking of an L2VPN and an L3VPN bridge network according to an embodiment of the present invention;

3 is a schematic diagram of an OAM model constructed by an L2VPN network and an L3VPN bridge network according to an embodiment of the present invention;

4 is a schematic flowchart of a first embodiment of a method for monitoring an end-to-end bridging network according to the present invention;

5 is a schematic flowchart of a second embodiment of a method for monitoring an end-to-end bridging network according to the present invention;

FIG. 6 is a schematic flowchart of the steps of performing OAM function according to the generated packet format in FIG. 4 to complete end-to-end OAM monitoring of the bridge network; FIG.

7 is a schematic flowchart diagram of a third embodiment of a method for monitoring an end-to-end bridging network according to the present invention;

8 is a schematic diagram of functional modules of a first embodiment of a bridge network end-to-end monitoring apparatus according to the present invention;

9 is a schematic diagram of functional modules of a second embodiment of a bridge network end-to-end monitoring apparatus according to the present invention;

10 is a schematic diagram of a refinement function module of the execution module in FIG. 8;

FIG. 11 is a schematic diagram of functional modules of a third embodiment of a bridge network end-to-end monitoring apparatus according to the present invention.

The implementation, functional features, and advantages of the present invention will be further described in conjunction with the embodiments.

detailed description

It is understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

In this embodiment, the bridge network is an L2VPN and an L3VPN bridge network, as shown in FIG. 2, FIG. 2 is a schematic diagram of the L2VPN and the L3VPN bridge network, and the L2VPN and the L3VPN bridge network, including the first CE. (Customer Edge, user edge device) (CE1), second CE (CE2), first PE (Provider Edge, edge device) (PE1), second PE (PE2), third PE (PE3), and first P (Provider, intermediate point device) (P1), the first CE, the first PE, the second PE, the first P, the third PE, and the second CE are sequentially connected in sequence.

As shown in FIG. 3, FIG. 3 is a schematic diagram of an OAM model constructed by an L2VPN network and an L3VPN bridge network according to an embodiment of the present invention. The OAM model includes a first MEP (Maintenance Association End Point) and a first MIP (Maintenance Domain). The intermediate point, the maintenance intermediate point, the second MIP, and the second MEP, the first MEP, the first MIP, the second MIP, and the second MEP are sequentially connected in sequence.

The present invention provides a method for monitoring the end-to-end of the bridge network. FIG. 4 is a schematic flowchart of the first embodiment of the method for monitoring the end-to-end of the bridge network according to the present invention. The method for monitoring the end-to-end of the bridge network provided by the first implementation includes:

Step S100: Generate OAM packet feature information and a message format.

The end-to-end monitoring device of the bridge network generates OAM packet feature information and packet format according to the defined MEP/MIP node. The format of the packet is shown in Table 1:

Table 1

The OAM packet feature information includes an Ether-type, an OAM tag, and an MEG ID number.

Step S200: Identify an OAM packet according to the generated OAM packet feature information.

The end-to-end monitoring device of the bridge network identifies the OAM packet according to the defined OAM packet feature information on the defined MEP/MIP node, wherein only the layer 2 feature information and the layer 3 feature information can be valid, or both of them are valid. Used to indicate that it is an OAM message. For the L2VPN domain, only the Layer 2 feature information of the OAM packet can be identified. The L3VPN domain can only identify the Layer 3 feature information. At this time, the L2/L3 bridge point in the MEG group completes the conversion of the Layer 2 feature information and the Layer 3 feature information. For the L2VPN domain, the Layer 2 and Layer 3 feature information can be mixed and identified. At this time, the L2 endpoint in the MEG group needs to identify the Layer 3 feature information. Specifically, the OAM message feature information includes an Ether-type, an OAM tag, and an MEG ID number, wherein the custom Ether-type is used to mark the OAM type of L2+L3. The OAM flag in the reserved field of the IP packet header is used to define the flag OLAG when the OAM is the IP OAM function set, and is used to distinguish the specific OAM type in the L2+L3OAM. The custom MEG ID number indicates the ID number of the MEG group configured by the user to distinguish specific OAM instances.

Step S300: Perform an OAM function according to the generated packet format, and complete end-to-end OAM monitoring of the bridged network.

The end-to-end monitoring device of the bridge network selects and executes the OAM function from the OAM function set according to the defined message format and the OAM function set, and encapsulates the OAM message according to the selected OAM function and the defined packet format; The OAM packet is sent to the target MEP or MIP node to complete the end-to-end OAM monitoring of the bridged network.

The end-to-end monitoring method of the bridge network provided by the invention is simple and easy to use, and can directly bridge the network through the L2VPN and the L3VPN; the end-to-end OAM fault detection and performance measurement can be flexibly implemented, and the service monitoring can be realized conveniently and quickly.

The present invention provides a method for monitoring the end-to-end of the bridge network. FIG. 5 is a schematic flowchart of the second embodiment of the method for monitoring the end-to-end of the bridge network according to the first embodiment. The monitoring method to the end, before step S100 includes:

In the step S100A, the OAM model is constructed according to the bridge network, and the MEP/MIP node and the OAM function set are defined, that is, the OAM function is executed according to the defined message format and the OAM function is performed, and the end-to-end OAM detection of the bridge network is completed.

The end-to-end monitoring device of the bridge network constructs an OAM model according to the bridge network, and defines a MEP/MIP node and an OAM function set. The bridged network and the constructed OAM model are further shown in FIG. 2 and FIG. 3. The OAM model supports the L2+L3 networking, that is, the typical end is an OAM endpoint in the L2VPN, and the other end is an endpoint in the L3VPN. In this embodiment, the first MEP, the first MIP, the second MIP, and the second MEP are defined. The OAM model, which defines the MEP on the user side of the edge node of the L2VPN network and the L3VPN network, and defines the MIP on the network side of the intermediate node of the L2VPN network and the L3VPN network, and joins the same MEG (Maintenance entity group). )in. The defined MEP and MIP have the common attributes of the L2+L3VPN network, and can traverse the L2VPN and L3VPN networks to provide end-to-end OAM monitoring. The L2+L3OAM MEP/MIP common attribute can be a unified L2VPN attribute (including but not limited to port, VLAN, MAC address, etc.) or a unified L3VPN attribute (including but not limited to IP address, IP DSCP (Differentiated Services Code Point). , differential service code point) or other IP header fields, etc., or a mixed L2+L3VPN attribute. The MEG group maintains the common attributes of the L2+L3MEP/MIP and identifies the group information by using the MEG ID. The defined OAM feature set includes IP (internet protocol) OAM function, TWAMP (two-way active measurement pro-tocol) and OAM function and Ethernet Y.1731OAM function. Specifically, the function set can refer to Y.1731 definition such as CC (Continuity Check), LB (Loopback), LT (Link Trace), and AIS (Alarm Indication Signal). Alarm indication signal), LCK (Lock Signal), LM (Frame Loss Measurement), DM (frame delay measurement), and TST (TEST).

As shown in FIG. 6, FIG. 6 is a schematic flowchart of the refinement of step S300 in FIG. 4, where the step S300 includes:

Step S310, selecting an OAM function in the OAM function set.

The end-to-end monitoring device of the bridge network selects the OAM function from the OAM function set, selects one of the OAM function set IP OAM function, the TWAMP OAM function, and the Ethernet Y.1731OAM function, for example, selects the OAM function set IP OAM. Features.

In step S320, the OAM packet is encapsulated according to the selected OAM function and the defined packet format.

The end-to-end monitoring device of the bridge network encapsulates OAM packets according to the selected OAM function and the defined packet format. For example, the encapsulated OAM packet may be a connectivity detection packet or a measurement packet.

Step S330: Send the encapsulated OAM message to the target MEP or MIP node.

The end-to-end monitoring device of the bridge network sends the encapsulated OAM message to the target MEP or the MIP node. For example, as shown in FIG. 3, the first MEP forwards the encapsulated OAM message to the first MIP and the second MIP2. Send to the second MEP to complete the end-to-end OAM monitoring of the bridged network.

As shown in FIG. 7, FIG. 7 is a schematic flowchart of a third embodiment of a method for monitoring an end-to-end bridging network according to the present invention. On the basis of the first embodiment, the method for monitoring the end-to-end bridging network provided by the third implementation, step S200 It also includes:

Step S200A: Determine, according to the feature information of the OAM packet, whether the received packet is an OAM packet.

The end-to-end monitoring device of the bridge network determines whether the received packet is an OAM packet according to the characteristic information of the OAM packet. For example, when the first MIP receives the packet, it determines whether the received packet is based on the ETHER-TYPE value. OAM packet; determines whether the OAM type is an IP OAM type according to the L2+L3OAM flag.

Step S200B: If it is determined that the received packet is an OAM packet, it is determined whether the current node processing is needed; if the current node processing is not required, the OAM packet is forwarded to the next node of the bridge network.

The end-to-end monitoring device of the bridge network determines that the received message is an OAM packet, and determines the OAM packet according to the OAM packet characteristic information, for example, according to the Layer 3 attribute in the packet, and the Dest IP (destination IP) value. Yes The current node processing is required. If the current node processing is required, the processing is performed according to the content corresponding to the OAM function in the OAM packet, and the processing flow is ended. If the current node processing is not needed, it is forwarded to the second MIP.

The following takes the IP OAM function, TWAMP OAM function and Ethernet Y.1731OAM application as examples to further explain the end-to-end monitoring method of the bridge network:

First, IP OAM function

If the IP OAM function is used as an example, the end-to-end connectivity of the L2+L3 bridge network is detected through the Internet Control Message Protocol (ICMP) protocol. The specific processes include:

Step S510: Construct an IP OAM model according to the bridged network, and define a maintenance endpoint MEP/maintenance intermediate point MIP node.

The end-to-end monitoring device of the bridge network creates an OAM model, defines the MEP or MIP node, and adds it to the same MEG. For example, the ID number of the MEG group is set to 1, and the MEG1 is referred to as MEG1. As shown in Figure 3, the O2 model of the L2+L3 network is shown in Figure 3. The L2VPN attributes include: port, VLAN, DMAC, SMAC, and Ether Type (custom Ether-Type, which is used to indicate the L2+L3OAM type). The L3VPN attribute settings include: IP address, priority, and lifetime (TTL). The IP address of the first MEP port is the same as the IP address of the first network segment (referred to as the first IP address). The first MIP is configured with Layer 2 and Layer 3 bridge forwarding, and the PORT+VLAN to IP mapping relationship is created. The IP address of the MIP port is set to the second IP, and the IP address of the second MEP port is set to the third IP.

Step S520: Define IP OAM packet feature information and a packet format according to the defined MEP/MIP node.

The end-to-end monitoring device of the bridge network defines the packet format according to the defined MEP/MIP node as shown in Table 2:

Table 2

For further reference to Table 2, the specific packet format corresponding to the Ping function is as follows:

DEST MAC: Destination MAC, using multicast MAC.

ETHER-TYPE: Custom Ether-type tag L2+L3OAM type.

The L2+L3OAM flag in the IP message header reserved field: When the OAM is the IP OAM function set, the definition is marked as the first Flag (this value can be customized to distinguish the specific OAM type in the L2+L3OAM).

The MEG ID number indicates the ID number of the MEG group configured by the user and distinguishes the specific OAM instance. SRC IP is the IP address of the port that initiated the ping.

DEST IP is the destination IP of the ping.

Date is a specific OAM PDU.

Step S530: The first MEP in the L2VPN network starts and performs an IP OAM function, and sets a destination IP of the PING and a gateway IP. The IP OAM function is enabled and executed, including selecting the IP OAM function set, selecting the MIP or MEP of the receiving end, and using the IP of the receiving MIP or MEP as the destination IP and the IP of the MEP1 as the source IP. The selected IP OAM function, the source IP address, and the destination IP are saved as configuration information and transmitted to the receiving end.

Step S540: The first MEP encapsulates the L2+L3 connectivity detection packet by using the source IP address, the destination IP address, and the selected IP OAM function, the L2VPN attribute, and the L3VPN attribute.

Step S550: The first MEP forwards the encapsulated L2+L3 connectivity detection packet to the first MIP by the router node where the L2VPN is located according to the Layer 2 information PORT and the VLAN.

Step S560: When the first MIP receives the encapsulated L2+L3 connectivity detection packet, determines whether the received packet is an L2+L3 connectivity detection packet according to the Ether-type value, and determines the OAM type according to the L2+L3OAM flag. Whether it is an IP OAM type, and if so, whether the L2+L3 connectivity detection packet needs to be processed by the current node according to the Layer 3 attribute and the Dest IP value in the L2+L3 connectivity detection packet, and if necessary, according to the L2+ The content corresponding to the OAM function in the L3OAM packet is processed. The processing of the OAM function belongs to the prior art, and is not described here again. If no processing is required, the first MIP bridge node determines that the L2+L3 connectivity check packet is mapped to the 8-bit protocol type custom protocol in the IP packet header according to the Ether-type value of the connectivity check packet. The type value Type (which can use the unused protocol type value) is converted to an IP packet according to the mapping of PORT+VLAN and IP, and forwarded to the second MIP.

Step S570: After receiving the packet, the second MIP, as the MEP node of the L3VPN network, determines whether the protocol type of the received IP packet header and the L2+L3OAM flag bit are customized protocol type values and Flag flags. If yes, it determines whether the current node needs to be processed according to the Dest IP. If not, it is processed according to the existing process. The processing of the OAM function is performed according to the OAM PDU protocol data unit corresponding to the OAM function in the L2+L3 connectivity detection packet, and the processing of the OAM function belongs to the prior art, and is not described here. If no processing is required, the OAM message is forwarded to the second MEP.

Step S570: After receiving the packet, the second MEP determines that the L2+L3 connectivity detection packet needs to be processed by itself, and then processes according to the content of the OAM in the packet according to the prior art.

Second, TWAMP OAM function

The One-Way Active Measurement Protocol (OWAMP) and the Two-Way Active Measurement Protocol (TWAMP) are becoming active IP performance measurement tools in mobile networks, but cannot span L2VPN networks. In this implementation, they can be in the middle or edge of L2VPN edge nodes and L3VPNs. The OWAMP and TWAMP protocols are deployed in the node to complete the performance measurement of the L2+L3 network. The OWAMP protocol is similar to the TWAMP protocol deployment and implementation. The difference is that OWAMP is a one-way active measurement, and TWAMP is a two-way active measurement. In this embodiment, the TWAMP is taken as an example to describe the packet loss rate of the edge node of the L3VPN network to the edge node of the L2VPN network. The specific processing flow of delay, delay jitter, and packet out-of-order performance, and the performance monitoring processing method of the L3VPN network intermediate node to the L2VPN network edge node are also the same, and will not be described in detail here.

Step S610: Create an OAM model according to the bridged network.

The TWAMP protocol is deployed on the first MEP and the second MEP. The Control-Client and the Session-Sender are deployed on the second MEP and serve as the control terminal. The Server and the Session-Reflector are deployed on the first MEP and serve as the responding end.

Step S620: Define IP OAM packet feature information and a packet format according to the defined MEP/MIP node.

The format of the Test message of the TWAMP protocol is shown in Table 3:

table 3

The DEST IP in the packet is the IP address of the destination port. The IP packet header reserved field is marked with the L2+L3OAM and identified as the second Flag.

Step S630, establishing a configuration control connection according to the TWAMP Control protocol second MEP and the first MEP.

The second MEP initiates a performance measurement to the first MEP. The second MEP acts as the monitoring initiator and begins to perform the TWAMP OAM function.

Step S640: The second MEP uses the source IP address, the destination IP address, and the selected TWAMP OAM function, the L2VPN attribute, and the L3VPN attribute to form an L2+L3TWAMP measurement message.

Step S650: The second MEP sends the L2+L3OAM message to the second MIP.

Step S660: The second MIP receives the L2+L3OAM packet, and determines whether it is an L2+L3OAM packet according to the second Flag identifier in the L2+L3OAM flag in the packet IP header reserved field, and then determines according to the Dest IP. Whether the OAM packet needs to be processed by the current node, if not, the OAM packet is forwarded to the first MIP; otherwise, the content is processed according to the OAM function in the L2+L3OAM packet, and the processing flow is ended.

Step S670: The first MIP receives the L2+L3OAM packet, and determines whether it is an L2+L3OAM packet according to the L2+L3OAM flag in the reserved field of the packet IP header. If yes, it determines whether the current node needs to be processed according to the Dest IP. If not required, the Layer 2 and Layer 3 OAM packet mapping and IP mapping are performed to the specified PORT+VLAN (the ETHER-TYPE uses the custom ETYPE, and the DAMC uses the multicast MAC). After the Layer 2 and Layer 3 bridged network is forwarded, the OAM packet is forwarded. Send to the first MEP.

Step S670: The first MEP receives the L2+L3OAM packet, determines whether it is an L2+L3OAM packet according to the ETHER-TYPE value, and then determines the L2+L3OAM according to the second Flag identifier in the L2+L3OAM flag in the IP header reserved field. Whether the type is TWAMP or not, and whether the Dest IP in the packet is the IP address of the port. If it is determined that the L2+L3OAM packet needs to be processed by itself, the response packet is encapsulated according to the content of the OAM in the OAM packet. The response message is processed.

Third, Ethernet Y.1731OAM function

The Ethernet OAM mechanism of the L2VPN network cannot traverse the L3VPN network. If the Ethernet OAM mechanism is used, the connectivity and performance of the L2+L3 network can be detected. In the network architecture shown in Figure 2, the ITU-T Y.1731 protocol is deployed in PE1, PE2, P1, and PE3, and the connectivity between PE1 and PE2 or PE3 is detected by Y.1731, and the link is detected. The performance, the specific processing flow is as follows:

Step S710: Construct an L2+L3OAM model according to the bridge network.

The specific method is as described in the first embodiment. On the first MIP (bridge node) node, but not limited to PORT+VLAN and IP mapping, ETHER-TYPE and IP packet protocol type mapping, complete Layer 2 and Layer 3 bridge forwarding of L2+L3OAM packets.

Step S720: Define an L2+L3OAM message format.

The CCM (Continuity Check Message) packet is used as an example. The format of the specific packet is shown in Table 4. The ETHER-TYPE is a custom value used to mark L2+L3OAM packets. The DMAC is a group. The broadcast MAC; the L2+L3OAM flag Flag recorded in the IP packet header reserved field is used to indicate the Y.1731 protocol type Ethernet OAM.

Table 4

Step S730: The first MEP selects the Y.1731OAM function, starts OAM detection, and performs the Y.1731OAM function.

The Y.1731 OAM functions selected by the first MEP include: CC, LB, LT, AIS, LCK, LM, DM, and TST.

Step S740: Encapsulate the L2+L3OAM packet according to the defined packet format and the OAM function. The encapsulated CCM message is as described in Table 4. For other functional message formats, only the OAM PDU part content and the Opcode and TLV Offset values need to be replaced.

Step S750: The first MEP forwards the L2+L3OAM packet to the first MIP by the router node where the L2VPN is located.

Step S760: The first MIP receives the L2+L3OAM packet, and determines whether it is an L2+L3OAM packet according to the Ether-Type value. If yes, the L2+L3OAM type identifier in the IP packet header reserved field and the corresponding OAM. The value of the OpCode (opcode) in the PDU is used to determine whether the L2+L3OAM needs to be processed by the current node. If not, the L2+L3OAM packet is forwarded and forwarded according to the Layer 2 and Layer 3 OAM packet forwarding rules, and the L2+L3OAM packet is sent. Forwarding to the second MIP; otherwise, processing the OAM content according to the OAM function in the L2+L3OAM packet, and ending the processing flow. The Layer 2 and Layer 3 OAM packet forwarding in the above process is based on the L2+L3OAM Ether-Type mapping. The protocol type value in the IP packet header protocol type field is used to identify the L2+L3OAM packet. PORT+VLAN Map to IP completed.

Step S770: The second MIP receives the L2+L3OAM packet, and determines whether it is an L2+L3OAM packet according to the IP packet header protocol type field. If yes, it determines whether the current node needs to be processed according to the Dest IP. The Layer 3 forwarding protocol forwards the OAM packet to the second MEP.

Step S780: After receiving the OAM packet, the second MEP determines whether it needs to be processed according to the IP packet header protocol type field and the Dest IP, and if necessary, according to the L2+L3OAM type in the IP packet header reserved field. The flag is used to determine whether it is an OAM type. If it is an OAM type, the content of the OAM is processed according to the prior art.

As shown in FIG. 8, FIG. 8 is a schematic diagram of a functional module of a bridge network end-to-end monitoring apparatus according to a first embodiment of the present invention. The bridge network end-to-end monitoring apparatus provided by the first embodiment includes:

The generating module 10 defines the OAM packet feature information and the packet format according to the defined MEP/MIP node.

The identification module 20 is configured to identify the OAM packet according to the defined OAM packet feature information on the defined MEP/MIP node;

The executing module 30 is configured to perform an OAM function according to the defined packet format and the OAM function set, and complete end-to-end OAM monitoring of the bridge network.

The generating module 10 of the monitoring device of the bridge network end-to-end generates the OAM packet characteristic information and the packet format according to the defined MEP/MIP node, and the packet format is further shown in Table 1. The OAM packet feature information includes an Ether-type, an OAM tag, and an MEG ID number.

The identification module 20 of the monitoring device of the bridge network end-to-end identifies the OAM packet according to the defined OAM packet feature information on the defined MEP/MIP node, wherein only the layer 2 feature information and the layer 3 feature information may be valid, or Both are valid and are used to indicate that they are OAM messages. For the L2VPN domain, only the Layer 2 feature information of the OAM packet can be identified. The L3VPN domain can only identify the Layer 3 feature information. At this time, the L2/L3 bridge point in the MEG group completes the conversion of the Layer 2 feature information and the Layer 3 feature information. For the L2VPN domain, the Layer 2 and Layer 3 feature information can be mixed and identified. At this time, the L2 endpoint in the MEG group needs to identify the Layer 3 feature information. Specifically, the OAM message feature information includes an Ether-type, an OAM tag, and an MEG ID number, wherein the custom Ether-type is used to mark the OAM type of L2+L3. The OAM flag in the reserved field of the IP packet header is used to define the flag OLAG when the OAM is the IP OAM function set, and is used to distinguish the specific OAM type in the L2+L3OAM. The custom MEG ID number indicates the ID number of the MEG group configured by the user to distinguish specific OAM instances.

The execution module 30 of the end-to-end monitoring device of the bridge network selects and executes the OAM function from the OAM function set according to the defined message format and the OAM function set, and encapsulates the OAM message according to the selected OAM function and the defined packet format. The encapsulated OAM message is sent to the target MEP or MIP node to complete the end-to-end OAM monitoring of the bridged network.

The end-to-end monitoring device of the bridge network provided by the invention is simple and easy to use, and can directly bridge the network through the L2VPN and the L3VPN; the end-to-end OAM fault detection and performance measurement can be flexibly implemented, and the service monitoring can be realized conveniently and quickly.

As shown in FIG. 9, FIG. 9 is a schematic diagram of a functional module of a second embodiment of a bridge network end-to-end monitoring apparatus according to the present invention. On the basis of the first embodiment, the bridge network end-to-end monitoring apparatus provided by the second embodiment is provided. include:

The building module 40 is configured to construct an OAM model according to the bridged network, and define a MEP/MIP node and an OAM function set.

The building block 40 of the bridge network end-to-end monitoring device constructs an OAM model according to the bridge network, and defines a MEP/MIP node and an OAM function set. Among them, the bridged network and the constructed OAM model are further shown in Figure 2 and As shown in Figure 3, the OAM model supports L2+L3 networking, that is, the typical end is the OAM endpoint in the L2VPN, and the other end is the endpoint in the L3VPN. In this embodiment, the first MEP, the first MIP, the second MIP, and the second MEP are defined. The OAM model defines the MEP on the edge node user side endpoints of the L2VPN network and the L3VPN network respectively, and defines the MIP on the L2VPN network and the L3VPN network intermediate node network side endpoint, and joins the same MEG. The defined MEP and MIP have the common attributes of the L2+L3VPN network, and can traverse the L2VPN and L3VPN networks to provide end-to-end OAM monitoring. The L2+L3OAM MEP/MIP common attribute can be a unified L2VPN attribute (including but not limited to port, VLAN, MAC address, etc.), or it can be a unified L3VPN attribute (including but not limited to IP address, IP DSCP or other IP header field). Etc.), or a mixed L2+L3VPN attribute. The MEG group maintains the common attributes of the L2+L3MEP/MIP and identifies the group information by using the MEG ID. The defined OAM feature set includes IP OAM functionality, TWAMP OAM functionality, and Ethernet Y.1731OAM functionality. Specifically, the function set can be defined with reference to Y.1731 such as CC, LB, LT, AIS, LCK, LM, DM, TST, and the like.

As shown in FIG. 10, FIG. 10 is a schematic diagram of a refinement function module of the execution module in FIG. 8. The execution module 30 includes:

The selecting unit 31 is set to select the OAM function in the OAM function set;

The encapsulating unit 32 is configured to encapsulate the OAM packet according to the selected OAM function and the defined packet format.

The sending unit 33 is configured to send the encapsulated OAM message to the target MEP or MIP node.

The selected unit 31 of the monitoring device for bridging the network end-to-end selects the OAM function from the OAM function set, selects one of the OAM function set IP OAM function, the TWAMP OAM function, and the Ethernet Y.1731OAM function, for example, selects OAM. IP OAM function in the function set.

The encapsulation unit 32 of the end-to-end monitoring device of the bridge network encapsulates the OAM message according to the selected OAM function and the defined message format. For example, the encapsulated OAM packet may be a connectivity detection packet or a measurement packet.

The transmitting unit 33 of the monitoring device that bridges the network end sends the encapsulated OAM message to the target MEP or the MIP node. For example, as shown in FIG. 3, the first MEP sends the encapsulated OAM message to the first MIP and the second MIP2. After forwarding, it is sent to the second MEP, thereby completing the end-to-end OAM monitoring of the bridged network.

As shown in FIG. 11, FIG. 11 is a schematic diagram of a functional module of a third embodiment of a bridge network end-to-end monitoring apparatus according to the present invention. On the basis of the first embodiment, the bridge network end-to-end monitoring apparatus provided by the third embodiment is provided. Also includes:

The determining module 50 is configured to determine, according to the OAM packet feature information, whether the received packet is an OAM packet.

The forwarding module 60 is configured to determine whether the current node processing is required if the received message is an OAM message, and forward the OAM message to the next node of the bridge network if the current node processing is not required.

The judging module 50 of the monitoring device of the bridge network end-to-end determines whether the received packet is an OAM packet according to the characteristic information of the OAM packet. For example, when the first MIP receives the packet, it determines that the received packet is received according to the ETHER-TYPE value. Whether the packet is an OAM packet; whether the OAM type is an IP OAM type according to the L2+L3OAM flag.

The forwarding module 60 of the end-to-end monitoring device of the bridge network determines that the received message is an OAM message, and determines the location according to the OAM message characteristic information, for example, according to the three-layer attribute in the message, the Dest IP (destination IP) value. Whether the OAM packet needs to be processed by the current node, if the current node processing is required, the processing is performed according to the content corresponding to the OAM function in the OAM packet, and the processing flow is ended. If the current node processing is not needed, it is forwarded to the second MIP.

The above are only the preferred embodiments of the present invention, and are not intended to limit the scope of the invention, and the equivalent structure or equivalent process transformations made by the description of the present invention and the drawings are directly or indirectly applied to other related technical fields. The same is included in the scope of patent protection of the present invention.

Industrial applicability

The technical solution provided by the embodiment of the present invention can be applied to the end-to-end monitoring process of the bridge network, generating the OAM packet feature information and the packet format, and identifying the OAM packet according to the generated OAM packet feature information; The message format, the OAM function is implemented, and the end-to-end OAM monitoring of the bridge network is completed. The invention is simple and easy to use, and can directly bridge the network through the L2VPN and the L3VPN; the end-to-end OAM fault detection and performance measurement can be flexibly implemented, and the service monitoring can be realized conveniently and quickly.

Claims

An end-to-end monitoring method for a bridge network, comprising:

Generate OAM packet feature information and packet format.

Identifying an OAM packet according to the generated OAM packet feature information;

According to the generated packet format, the OAM function is executed to complete the end-to-end OAM monitoring of the bridged network.
The method for monitoring the end-to-end of the bridge network according to claim 1, wherein the step of generating the OAM message feature information and the message format comprises:

According to the bridged network, the operation management and maintenance OAM model is constructed, and the maintenance endpoint MEP/maintenance intermediate point MIP node and the OAM function set are defined.
The method for monitoring the end-to-end of the bridge network according to claim 1, wherein the performing the OAM function according to the generated packet format, and completing the end-to-end OAM monitoring of the bridge network includes:

Select the OAM function in the OAM function set;

Encapsulating OAM packets according to the selected OAM function and the defined packet format;

The encapsulated OAM message is sent to the target MEP or MIP node.
The method for monitoring the end-to-end of the bridge network according to claim 1 or 2, wherein the step of identifying the OAM packet according to the generated OAM packet feature information further includes:

The device determines whether the received packet is an OAM packet according to the characteristic information of the OAM packet.
The method for monitoring the end-to-end of the bridge network according to claim 1 or 2, wherein the step of determining whether the received packet is an OAM packet according to the OAM packet characteristic information further includes:

If it is determined that the received packet is an OAM packet, it is determined whether the current node needs to be processed;

If the current node processing is not required, the OAM message is forwarded to the next node of the bridged network.
An end-to-end monitoring device for a bridge network, comprising:

The generating module is configured to generate OAM packet feature information and a packet format.

The identification module is configured to identify the OAM packet according to the generated OAM packet feature information;

The execution module is configured to perform OAM function according to the generated packet format, and complete end-to-end OAM monitoring of the bridge network.
The bridge network end-to-end monitoring device of claim 6, wherein the bridge network end-to-end monitoring device further comprises:

The build module is set to build an OAM model based on the bridged network, defining the MEP/MIP node and the OAM feature set.
The bridge network end-to-end monitoring device of claim 6 wherein said

Execution modules include:

The selected unit is set to the OAM function in the selected OAM function set;

The encapsulating unit is configured to encapsulate the OAM packet according to the selected OAM function and the defined packet format;

The sending unit is configured to send the encapsulated OAM message to the target MEP or MIP node.
The bridge network end-to-end monitoring device of claim 6 or 7, wherein the bridge network end-to-end monitoring device further comprises:

The determining module is configured to determine whether the received packet is an OAM packet according to the characteristic information of the OAM packet.
The bridge network end-to-end monitoring device of claim 6 or 7, wherein the bridge network end-to-end monitoring device further comprises:

The forwarding module is configured to determine whether the received packet is an OAM packet, and then determines whether the current node needs to be processed. If the current node processing is not required, the OAM packet is forwarded to the next node of the bridge network.