WO2016176842A1 - Method, device, controller and network element for ethernet interface addressing in mpls-tp tunnel - Google Patents

Abstract

Disclosed in the present invention is a method, device controller and network element for Ethernet interface addressing in an MPLS-TP tunnel, which belongs to the technical field of communications. The method includes: the controller obtains information of an ingress interface from a first network element to a second network element in the MPLS-TP tunnel to be established, wherein the second network element is the next hop network element of the first network element on the MPLS-TP tunnel path; according to the information of the ingress interface from the first network element to the second network element, the controller obtains a MAC address of the ingress interface from the first network element to the second network element; according to the MAC address of the ingress interface from the first network element to the second network element, the controller obtains a MAC address of the ingress interface of the next hop network element of the first network element, and transmits the MAC address of the ingress interface of the next hop network element of the first network element to the first network element. The device includes a first obtaining module, a second obtaining module and an addressing module. The problem that mistake checking and correcting is difficult when IP address configuration is wrong is solved, the network maintenance workload is reduced and the processing speed of the network element is enhanced.

Description

Ethernet interface addressing method, device, controller and network element in MPLS-TP tunnel Technical field

The present invention relates to the field of communication technologies, and in particular, to an Ethernet interface addressing method, apparatus, controller, and network element in a MPLS-TP (Multi-Protocol Label Switching Transport Profile) tunnel.

Background technique

MPLS-TP is a transmission technology that combines the characteristics of MPLS packet switching and traditional transport network. MPLS-TP provides an MPLS-TP tunnel for data packet transmission. An MPLS-TP tunnel consists of two or more network elements and connections between different network elements. Data packets can be transmitted between these network elements. When the MPLS-TP tunnel is used to transmit the MPLS packet, the network element in the MPLS-TP tunnel sends the MPLS packet, and the network element acquires the inbound interface of the next hop network element in the MPLS-TP tunnel. a MAC (Media Access Control) address, the MAC address is encapsulated in the MPLS packet, and the encapsulated MPLS packet is sent to the next hop network element, and the next hop network element is The MPLS packet continues to be sent downstream.

The prior art provides an Ethernet interface addressing method for the next hop network element in the MPLS-TP tunnel, which may be: the network element obtains the IP of the inbound interface of the next hop network element (Internet Protocol) The address of the protocol is based on the IP address of the inbound interface of the next hop. The MAC address of the inbound interface of the next hop NE is obtained through the ARP (Address Resolution Protocol) protocol.

In the process of implementing the present invention, the inventors have found that the prior art has at least the following problems:

Before sending a packet, you need to configure an IP address for the inbound interface of all NEs in the MPLS-TP network. Because the number of network elements in an MPLS-TP network is very large, and the number of inbound interfaces included in each network element is also large, the workload for configuring an IP address for the inbound interfaces of all network elements in the MPLS-TP network is large. It is easy to make mistakes in configuration. In addition, running ARP on a network element consumes a large number of CPUs (Central Processing Units), which affects the processing speed of network elements.

Summary of the invention

In order to solve the problems of the prior art, the present invention provides an Ethernet interface addressing method, apparatus, controller, and network element in an MPLS-TP tunnel. The technical solutions are as follows:

In a first aspect, an embodiment of the present invention provides an Ethernet interface addressing method in an MPLS-TP tunnel, where the method includes:

Obtaining, by the controller, the inbound interface information of the first network element to the second network element in the MPLS-TP tunnel path of the transmission subset based on the multi-protocol label switching, where the second network is in the MPLS-TP tunnel path The element is a next hop network element of the first network element;

The controller acquires a media access control MAC address of the inbound interface of the first network element to the second network element according to the inbound interface information of the first network element to the second network element;

The controller obtains a MAC address of an inbound interface of a next hop network element of the first network element according to a MAC address of the inbound interface of the first network element to the second network element, where the first network is The MAC address of the inbound interface of the next hop element of the element is sent to the first network element.

With the implementation of the first aspect, in a first possible implementation manner of the first aspect, the inbound interface information of the first network element to the second network element includes an inbound interface identifier of the second network element. .

With reference to the first aspect or the first possible implementation manner of the first aspect, in a second possible implementation manner of the first aspect, the inbound interface information of the first network element to the second network element includes The network element identifier of the second network element and the inbound interface identifier of the second network element.

With reference to the first aspect, or any one of the first to the second possible implementations of the first aspect, in a third possible implementation manner of the first aspect, the controller is configured according to the first network element Before the inbound interface information of the second network element is obtained, before the media access control MAC address of the inbound interface of the first network element to the second network element is obtained, the method further includes:

The controller receives and saves interface information of the second network element and a MAC address of the interface;

The interface information of the second network element includes an inbound interface identifier of the second network element and a network element identifier of the second network element, where a MAC address of the interface of the second network element includes the second network element MAC address of the inbound interface.

With reference to the first aspect, or any one of the first to the third possible implementation manners of the first aspect, in a fourth possible implementation manner of the first aspect, the method further includes:

The controller receives a MAC address modification request of the inbound interface of the second network element, where the MAC address modification request of the inbound interface carries the MAC address of the inbound interface modified by the second network element;

The controller updates the MAC address of the inbound interface of the second network element according to the MAC address of the inbound interface modified by the second network element;

The controller updates the MAC address of the inbound interface of the next hop network element of the first network element according to the MAC address of the inbound interface of the second network element.

In a second aspect, an embodiment of the present invention provides an Ethernet interface addressing method in an MPLS-TP tunnel, where the method includes:

The network element acquires an MPLS packet based on a multi-protocol label exchange;

Receiving, by the network element, a media access control MAC address of an inbound interface of a next hop network element of the network element;

The network element encapsulates the MAC address of the inbound interface of the next hop network element of the network element into the MPLS packet.

With the implementation of the second aspect, in a first possible implementation manner of the second aspect, before the acquiring, by the network element, the MPLS packet, the network element further includes:

The network element sends the interface information of the network element and the MAC address of the interface to the controller, so that the controller saves the interface information of the network element and the MAC address of the interface;

The interface information of the network element includes an inbound interface identifier of the network element and a network element identifier of the network element, and a MAC address of the interface of the network element includes a MAC address of an inbound interface of the network element.

With reference to the second aspect, or the first possible implementation manner of the second aspect, in a second possible implementation manner of the second aspect, the method further includes:

Transmitting, by the network element, a MAC address modification request of the inbound interface to the controller, where the MAC address modification request of the inbound interface carries the MAC address of the inbound interface modified by the network element, so that the controller is configured according to the network The MAC address of the inbound interface of the meta-modified device updates the MAC address of the inbound interface of the network element.

In a third aspect, an embodiment of the present invention provides an Ethernet interface addressing device in an MPLS-TP tunnel, where the device includes:

a first acquiring module, configured to acquire inbound interface information of the first network element to the second network element in the MPLS-TP tunnel path of the transmission subset based on the multi-protocol label switching, in the MPLS-TP tunnel path The second network element is a next hop network element of the first network element;

a second obtaining module, configured to acquire, according to the inbound interface information of the first network element to the second network element, a media access control MAC address of the inbound interface of the first network element to the second network element;

An addressing module, configured to: according to the MAC address of the inbound interface of the first network element to the second network element And obtaining a MAC address of the inbound interface of the next hop network element of the first network element, and sending the MAC address of the inbound interface of the next hop network element of the first network element to the first network element.

With the implementation of the third aspect, in a first possible implementation manner of the third aspect, the inbound interface information of the first network element to the second network element includes an inbound interface identifier of the second network element. .

With the third aspect or the first possible implementation manner of the third aspect, in a second possible implementation manner of the third aspect, the inbound interface information of the first network element to the second network element includes The network element identifier of the second network element and the inbound interface identifier of the second network element.

With reference to the third aspect, or any one of the first to the second possible implementation manners of the third aspect, in a third possible implementation manner of the third aspect, the device further includes:

a storage module, configured to receive and save interface information of the second network element and a MAC address of the interface;

The interface information of the second network element includes an inbound interface identifier of the second network element and a network element identifier of the second network element, where a MAC address of the interface of the second network element includes the second network element MAC address of the inbound interface.

With reference to the third aspect, or any one of the first to the third possible implementation manners of the third aspect, in a fourth possible implementation manner of the third aspect, the device further includes:

The first receiving module is configured to receive a MAC address modification request of the inbound interface of the second network element, where the MAC address modification request of the inbound interface carries the MAC address of the inbound interface modified by the second network element;

a first update module, configured to update, according to the MAC address of the inbound interface that is modified by the second network element, a MAC address of the inbound interface of the second network element;

And a second update module, configured to update, according to the MAC address of the inbound interface of the second network element, the MAC address of the inbound interface of the next hop element of the first network element.

In a fourth aspect, an embodiment of the present invention provides an Ethernet interface addressing device in an MPLS-TP tunnel, where the device includes:

a third acquiring module, configured to acquire an MPLS packet based on a multi-protocol label exchange;

a second receiving module, configured to receive a media access control MAC address of an inbound interface of a next hop network element of the network element;

The encapsulating module is configured to encapsulate the MAC address of the inbound interface of the next hop network element of the network element into the MPLS packet.

In conjunction with the implementation of the fourth aspect, in a first possible implementation manner of the fourth aspect, The device also includes:

The first sending module is configured to send the interface information of the network element and the MAC address of the interface to the controller, so that the controller saves the interface information of the network element and the MAC address of the interface;

The interface information of the network element includes an inbound interface identifier of the network element and a network element identifier of the network element, and a MAC address of the interface of the network element includes a MAC address of an inbound interface of the network element.

With reference to the fourth aspect, or the first possible implementation manner of the fourth aspect, in a second possible implementation manner of the fourth aspect, the device further includes:

a second sending module, configured to send a MAC address modification request of the inbound interface to the controller, where the MAC address modification request of the inbound interface carries the MAC address of the inbound interface modified by the network element, so that the controller is configured according to the The MAC address of the inbound interface of the network element is updated to update the MAC address of the inbound interface of the network element.

In a fifth aspect, an embodiment of the present invention provides a controller, where the controller includes: a first processor and a first transmitter;

The first processor is configured to acquire inbound interface information of the first network element to the second network element in the MPLS-TP tunnel path of the multi-protocol label switching based on the multi-protocol label switching, in the MPLS-TP tunnel The second network element in the path is a next hop network element of the first network element;

The first processor is further configured to acquire media access control of the inbound interface of the first network element to the second network element according to the inbound interface information of the first network element to the second network element. MAC address;

The first processor is further configured to obtain, according to a MAC address of the inbound interface of the first network element to the second network element, a MAC address of an inbound interface of a next hop network element of the first network element;

The first transmitter is configured to send, to the first network element, a MAC address of an inbound interface of a next hop network element of the first network element.

With the implementation of the fifth aspect, in a first possible implementation manner of the fifth aspect, the inbound interface information of the first network element to the second network element includes an inbound interface identifier of the second network element. .

With reference to the fifth aspect, or the first possible implementation manner of the fifth aspect, in the second possible implementation manner of the fifth aspect, the inbound interface information of the first network element to the second network element includes The network element identifier of the second network element and the inbound interface identifier of the second network element.

With reference to the fifth aspect, or any one of the first to the second possible implementation manners of the fifth aspect, in a third possible implementation manner of the fifth aspect, the first processor is further configured to receive and save The interface information of the second network element and the MAC address of the interface;

The interface information of the second network element includes an inbound interface identifier of the second network element and a network element identifier of the second network element, where a MAC address of the interface of the second network element includes the second network element MAC address of the inbound interface.

With reference to the fifth aspect, or any one of the first to the third possible implementation manners of the fifth aspect, in a fourth possible implementation manner of the fifth aspect, the controller further includes: a first receiver;

The first receiver is configured to receive a MAC address modification request of the inbound interface of the second network element, where the MAC address modification request of the inbound interface carries the MAC address of the inbound interface modified by the second network element ;

The first processor is further configured to: update, according to the MAC address of the inbound interface that is modified by the second network element, a MAC address of the inbound interface of the second network element;

The first processor is further configured to update, according to the MAC address of the inbound interface of the second network element, a MAC address of an inbound interface of the next hop element of the first network element.

In a sixth aspect, an embodiment of the present invention provides a network element, where the network element includes: a second processor and a second receiver;

The second processor is configured to acquire an MPLS packet based on a multi-protocol label exchange;

The second receiver is configured to receive a media access control MAC address of an inbound interface of a next hop network element of the network element;

The second processor is further configured to encapsulate a MAC address of an inbound interface of a next hop network element of the network element into the MPLS packet.

With the implementation of the sixth aspect, in a first possible implementation manner of the sixth aspect, the network element further includes: a second transmitter;

The second transmitter is configured to send the interface information of the network element and the MAC address of the interface to the controller, so that the controller saves the interface information of the network element and the MAC address of the interface;

The interface information of the network element includes an inbound interface identifier of the network element and a network element identifier of the network element, and a MAC address of the interface of the network element includes a MAC address of an inbound interface of the network element.

With reference to the sixth aspect, or the first possible implementation manner of the sixth aspect, in a second possible implementation manner of the sixth aspect, the network element further includes: a second transmitter;

The second transmitter is further configured to send a MAC address modification request of the inbound interface to the controller, where the MAC address modification request of the inbound interface carries the MAC address of the inbound interface modified by the network element, so as to facilitate the Updating, by the controller, the network element according to the MAC address of the inbound interface modified by the network element MAC address of the inbound interface.

In the present invention, the controller obtains the MAC address of the inbound interface of the next hop element of the first network element in the MPLS-TP tunnel path to be established, and the next hop element of the first network element The MAC address of the inbound interface is sent to the first network element, so that the first network element directly receives the MAC address of the inbound interface of the next hop network element of the next hop element of the first network element, and does not need to be the inbound interface of the network element. The IP address is configured to implement IP-free planning and configuration. This solves the problem of troubleshooting error correction when the IP address configuration error occurs. This greatly reduces the workload of network maintenance. Moreover, the ARP protocol does not need to be run on the NE. Improve the processing speed of network elements.

DRAWINGS

1-1 is a flowchart of an Ethernet interface addressing method in an MPLS-TP tunnel according to Embodiment 1 of the present invention;

1-2 is a flowchart of an Ethernet interface addressing method in another MPLS-TP tunnel according to Embodiment 1 of the present invention;

2-1 is a flowchart of an Ethernet interface addressing method in an MPLS-TP tunnel according to Embodiment 2 of the present invention;

2-2 is a schematic diagram of an MPLS-TP tunnel provided by Embodiment 2 of the present invention;

3 is a flowchart of an Ethernet interface addressing method in an MPLS-TP tunnel according to Embodiment 3 of the present invention;

4 is a flowchart of a method for updating a crosstab of an MPLS-TP tunnel according to Embodiment 4 of the present invention;

5 is a schematic structural diagram of an Ethernet interface addressing device in an MPLS-TP tunnel according to Embodiment 5 of the present invention;

6 is a schematic structural diagram of an Ethernet interface addressing device in an MPLS-TP tunnel according to Embodiment 6 of the present invention;

7 is a schematic structural diagram of a controller according to Embodiment 7 of the present invention;

FIG. 8 is a schematic structural diagram of a network element according to Embodiment 8 of the present invention.

detailed description

The embodiments of the present invention will be further described in detail below with reference to the accompanying drawings.

Example 1

The embodiment of the invention provides an Ethernet interface addressing method in an MPLS-TP tunnel. The execution body of the method is a controller, and the controller can centrally control the network and deploy the system on the independent server; For computers or servers, etc. Referring to Figure 1-1, the method includes:

Step 101a: The controller acquires inbound interface information of the first network element to the second network element in the MPLS-TP tunnel path of the transmission subset based on the multi-protocol label switching, and the second network in the MPLS-TP tunnel path. The element is the next hop network element of the first network element;

Step 102a: The controller acquires a media access control MAC address of the inbound interface of the first network element to the second network element according to the inbound interface information of the first network element to the second network element.

Step 103a: The controller obtains the MAC address of the inbound interface of the next hop element of the first network element according to the MAC address of the inbound interface of the first network element to the second network element, and the next hop element of the first network element The MAC address of the inbound interface is sent to the first network element.

The embodiment of the present invention provides an Ethernet interface addressing method in an MPLS-TP tunnel. The method is implemented by a network element, and the network element may be a router or the like. Referring to Figure 1-2, the method includes:

Step 101b: The network element acquires an MPLS packet based on a multi-protocol label exchange.

Step 102b: The network element receives the media access control MAC address of the inbound interface of the next hop network element of the network element.

Step 103b: The network element encapsulates the MAC address of the inbound interface of the next hop network element of the network element into the MPLS packet.

In the embodiment of the present invention, the controller obtains the MAC address of the inbound interface of the next hop element of the first network element in the MPLS-TP tunnel path to be established, and the next hop of the first network element The MAC address of the inbound interface of the element is sent to the first network element, so that the first network element directly receives the MAC address of the inbound interface of the next hop element of the next hop element of the first network element, and does not need to be the network element. The IP address of the inbound interface is configured to implement IP-free planning and configuration. This solves the problem of troubleshooting error correction when the IP address configuration error occurs. This greatly reduces the workload of network maintenance. Moreover, the ARP protocol does not need to be run on the NE. , thereby improving the processing speed of the network element.

Example 2

The embodiment of the invention provides an Ethernet interface addressing method in an MPLS-TP tunnel. The execution body of the method is a controller, and the controller can centrally control the network and deploy on a separate server. The system; the controller can be a computer or a server. See Figure 2-1, where the method includes:

Step 201: The controller receives a tunnel establishment request, where the tunnel establishment request carries parameters of the source node, the destination node, and the tunnel.

When the MPLS packet is sent by the user, the MPLS-TP tunnel is set up in the MPLS-TP network. The MPLS-TP tunnel is used to send the tunnel request to the controller through the client device or the first node. The source node, the destination node, and the parameters of the tunnel, the parameters of the tunnel may be the bandwidth of the tunnel, and the like; the controller receives the tunnel establishment request, and performs step 202.

Step 202: The controller calculates an MPLS-TP tunnel path to be established according to the tunnel establishment request.

The controller calculates an MPLS-TP tunnel path from the source node to the destination node and satisfying the parameters of the tunnel according to the parameters of the source node, the destination node, and the tunnel. The MPLS-TP tunnel path includes at least each of the passed NE identifiers and the inbound interface identifiers. Optionally, the MPLS-TP tunnel path may further include an outbound interface identifier, an inbound label, and an outgoing label.

For example, the MPLS-TP tunnel path generated by the controller is shown in Figure 2-2. In the MPLS-TP tunnel path, the network element identifier of the network element 1 is NE1, the outbound interface identifier of the network element 1 is P1, the outgoing interface label is 201, and the network element identifier of the network element 2 is NE2, and the network element 2 is The inbound interface ID is P2, the MAC address of the inbound interface is MAC2, the inbound interface label is 201, the outbound interface ID is P3, the outbound interface MAC address is MAC3, the outbound interface label is 202, and the NE label of the NE 3 is NE3. The inbound interface of the network element 3 is identified as P4, the MAC address of the inbound interface is MAC4, the inbound interface label is 202, the outbound interface identifier is P5, the outbound interface is MAC5, and the outgoing interface label is 203. The inbound interface identifier is NE4, the inbound interface identifier of the inbound interface 4 is P6, the inbound interface MAC address is MAC6, and the inbound interface label is 203.

Step 203: The controller acquires inbound interface information of the first network element to the second network element in the MPLS-TP tunnel path.

The first network element is any one of the MPLS-TP tunnel paths, and the second network element is the next hop network element of the first network element in the MPLS-TP tunnel path; the first network element to the first network element The inbound interface information of the second network element includes the inbound interface identifier of the second network element; or the inbound interface information of the first network element to the second network element includes the network element identifier of the second network element and the inbound interface identifier of the second network element. .

Step 204: The controller acquires the MAC address of the inbound interface of the first network element to the second network element according to the inbound interface information of the first network element to the second network element.

The controller obtains, according to the inbound interface information of the first network element to the second network element, the MAC address of the inbound interface of the first network element to the second network element from the correspondence between the inbound interface information of the second network element and the MAC address of the interface address.

Before the step, the second network element sends the interface information of the second network element and the MAC address of the interface to the controller, where the controller receives and saves the interface information of the second network element and the MAC address of the interface, and the interface of the second network element The MAC address includes the MAC address of the inbound interface of the second network element. The interface information of the second network element includes the inbound interface identifier of the second network element, or the interface information of the second network element includes the inbound interface identifier of the second network element and the network element identifier of the second network element.

If the inbound interface information of the first network element to the second network element includes the inbound interface identifier of the second network element, the step may be: the controller uses the second network element that is pre-stored according to the inbound interface identifier of the second network element. The MAC address of the inbound interface of the first network element to the second network element is obtained by the mapping between the inbound interface identifier and the MAC address of the inbound interface of the second network element.

Before the step, the controller needs to store the mapping between the inbound interface identifier of the second network element and the MAC address of the inbound interface of the second network element, where the interface identifier includes the inbound interface identifier and the outbound interface identifier, but the network element is not When an MPLS-TP tunnel is set up, the inbound interface and the outbound interface are collectively called interfaces. The specific process is as follows:

When the network element and the controller are online, or when the network element receives the query request sent by the controller, each network element in the MPLS-TP network sends the interface identifier of the local network element and the MAC address of the interface to the controller. The controller receives the interface identifier of the local network element and the MAC address of the interface sent by each network element, and saves the interface identifier of each network element and the MAC address of the interface.

The interface identifier may be an index number that uniquely identifies the interface, or a triplet identifier that is composed of a physical board number, a subcard number, and an interface ID.

If the inbound interface information of the first network element to the second network element includes the inbound interface identifier of the second network element and the network element identifier of the second network element, the step may be:

The controller obtains the network element identifier of the second network element, and identifies the network element identifier and the first network element of the second network element according to the network element identifier of the second network element and the inbound interface identifier of the first network element to the second network element. And obtaining, by the mapping between the inbound interface identifier of the second network element and the MAC address of the inbound interface of the second network element, the MAC address of the inbound interface of the first network element to the second network element.

Before the step, the controller needs to store the network element identifier of the second network element, the inbound interface identifier of the first network element to the second network element, and the correspondence between the first network element and the MAC address of the inbound interface of the second network element. The interface identifier includes the inbound interface identifier and the outbound interface identifier, but the MPLS-TP tunnel is not established in the network element. In the case of a path, the inbound interface and the outbound interface are collectively referred to as the interface. The specific process is as follows:

When the network element and the controller are online, or when the network element receives the query request sent by the controller, each network element in the MPLS-TP network sends the network element identifier, interface identifier, and interface of the local network element to the controller. The controller receives the network element identifier, the interface identifier, and the MAC address of the interface of each network element, and saves the network element identifier, interface identifier, and MAC address of each interface.

The network element identifier may be an IP address of the network element or a management ID (IDentity, ID number) of the network element.

When the controller communicates with the network element, if the controller sends a query request to the network element and the network element sends the network element identifier, the interface identifier, and the MAC address of the interface to the controller, the PCEP (Path Computation Element Communication Protocol) may be adopted. , the path calculation unit interaction protocol) and the Openflow (Open Flow Table Protocol) and other protocols are implemented, and the transmission protocol is not specifically limited in the embodiment of the present invention.

For example, the correspondence between the NE identifier, the interface identifier, and the MAC address of the interface stored in the controller is as follows:

Table 1

NE identifier	Interface identifier	MAC address of the interface
			NE1	P1	MAC1
NE2	P2	MAC2
			NE2	P3	MAC3
NE3	P4	MAC4
			NE3	P5	MAC5
NE4	P6	MAC6
			......	......	......

The MPLS-TP tunnel path includes the network element identifier, the inbound interface identifier, and the outbound interface identifier, and the controller calculates the MPLS-TP tunnel path, and the network element identifier and the network element included in the MPLS-TP tunnel path are obtained. The inbound interface identifier and the outbound interface identifier; for example, the controller learns that the network element identifiers included in the MPLS-TP tunnel path are NE1, NE2, NE3, and NE4, respectively; and the inbound interface identifiers are P2, P4, and P6, respectively. The controller obtains the network element identifier of the next hop network element of the network element 1 as NE2, and the inbound interface identifier of the network element 1 to the network element 2 is P2, according to the next hop network element of the network element 1 The network element identifies NE2 and the inbound interface identifier P2 of the network element 1 to the network element 2, and obtains the MAC address of the inbound interface of the next hop network element of the network element 1 from the table 1 as MAC2; likewise, the next hop of the network element 2 The network element identifier of the network element is NE3, and the inbound interface identifier of the network element 2 to the network element 3 is P4. The network element identifier NE3 of the next hop network element of the network element 2 and the inbound interface identifier of the network element 2 to the network element 3 are identified. P4, the MAC address of the inbound interface of the next hop network element of the network element 2 is obtained from Table 1, and the network element identifier of the next hop network element of the network element 3 is NE4, and the network element 3 is connected to the network element 4. The interface identifier is P6, and the network element identifier NE4 of the next hop network element of the network element 3 and the inbound interface identifier P6 of the network element 3 to the network element 4 are obtained, and the entry of the next hop network element of the network element 3 is obtained from the table 1. The MAC address of the interface is MAC6.

The interface in the embodiment of the present invention is a network side interface. Therefore, before the network element sends the network element identifier, the interface identifier, and the MAC address of the interface to the controller, the network element determines whether the interface is a network side interface. If yes, the network element identifier, the interface identifier, and the MAC address of the interface are sent to the controller; if not, the process ends.

The step of determining, by the network element, whether the interface is a network side interface may be:

If the interface is enabled with MPLS-TP or is on the line card, if the interface is enabled with MPLS-TP or on the line card, the interface is determined to be the network-side interface. If the interface is not enabled with MPLS-TP. If the board is not on the line card, the interface is not the network side interface.

The MPLS-TP is enabled to forward MPLS packets.

Step 205: The controller obtains the MAC address of the inbound interface of the next hop network element of the first network element according to the MAC address of the inbound interface of the first network element to the second network element.

The controller uses the MAC address of the inbound interface of the first network element to the second network element as the MAC address of the inbound interface of the next hop network element of the first network element.

Optionally, the controller may write the MAC address of the inbound interface of the next hop element of the first network element into the crosstab of the MPLS-TP tunnel.

For example, the MAC address MAC2 of the inbound interface of the next hop NE of NE1, the MAC address MAC4 of the inbound interface of the next hop NE of NE2, and the addresses MAC6 and NE4 of the inbound interface of the next hop NE of NE3. The MAC address of the inbound interface of the next-hop NE is invalid. The cross-tab of the MPLS-TP tunnel can also include the inbound interface identifier of the local NE, the inbound label, and the local network. The outbound interface identifier, outgoing label, network element identifier of the next hop network element, and/or the inbound interface identifier of the next hop network element are as shown in Table 2 below.

Table 2

Net element

Incoming interface

Entry criteria

Interface label

Bid

MAC address of the inbound interface of the next hop NE

knowledge	knowledge	sign	knowledge	sign	address
						NE1	\	\		P1	201	MAC2
NE2
		P2	201	P3	202	MAC4
NE3
		P4	202	P5	203	MAC6
NE4
		P6	203	\	\	\......

Step 206: The controller sends the MAC address of the inbound interface of the next hop network element of the first network element to the first network element.

In this step, the controller may also obtain the cross-tab of the first network element, and send the cross-tab corresponding to the first network element to the first network element.

For any network element included in the MPLS-TP tunnel path, the controller obtains the inbound interface identifier, the inbound label, and the outbound interface identifier of the network element from the cross-tab of the MPLS-TP tunnel according to the network element identifier of the network element. The outbound label, the MAC address of the inbound interface of the next hop network element, and the like, and the obtained information is used as a cross table of the network element, and the cross table of the network element is sent to the network element.

For example, the cross-tab of the network element identifier NE1 including the network element 1 is obtained from the following table 3, and the information of the table 3 is sent to the network element 1; likewise, the network element including the network element 2 is obtained from the table 2. The cross-tab of the identifier NE2 is as shown in Table 4 below. The information of Table 4 is sent to the network element 2, and the cross-tab of the network element identifier NE3 including the network element 3 is obtained from Table 2, as shown in Table 5 below. The information is sent to the network element 3; the cross-tab of the network element identifier NE4 including the network element 4 is obtained from the table 2, and the information of the table 6 is sent to the network element 4.

table 3

Table 4

table 5

Table 6

The controller can implement the cross-tab of the network element by using a protocol such as a PC Comp (Path Computation Element Communication Protocol) and an OpenFlow (Open Flow Table Protocol), in the embodiment of the present invention. The protocol for the crosstab of the network element to be sent by the controller is not specifically limited.

Further, the controller may directly send the cross-tab of the MPLS-TP tunnel to each network element.

In the embodiment of the present invention, the controller obtains the MAC address of the inbound interface of the next hop element of the first network element in the MPLS-TP tunnel path to be established, and the next hop of the first network element The MAC address of the inbound interface of the element is sent to the first network element, so that the first network element directly receives the MAC address of the inbound interface of the next hop element of the next hop element of the first network element, and does not need to be the network element. The IP address of the inbound interface is configured to implement IP-free planning and configuration. This solves the problem of troubleshooting error correction when the IP address configuration error occurs. This greatly reduces the workload of network maintenance. Moreover, the ARP protocol does not need to be run on the NE. , thereby improving the processing speed of the network element.

Example 3

The embodiment of the present invention provides an Ethernet interface addressing method in an MPLS-TP tunnel path. The method is implemented by a network element, and the network element may be a router or the like. Referring to FIG. 3, the method includes:

Step 301: The network element acquires the MPLS packet and receives the MAC address of the inbound interface of the next hop network element of the network element.

The step of the network element acquiring the MPLS packet may be:

When the network element is the first node in the MPLS-TP tunnel path, the network element receives the source node to send The packet of the MPLS-TP tunnel that transmits the packet is written in the packet to obtain the MPLS packet; when the network element is not the first node in the MPLS-TP tunnel path, the network element The MPLS packet sent by the last hop network element of the network element in the MPLS-TP tunnel path is received.

The step of the network element receiving the MAC address of the inbound interface of the next hop element of the network element may be:

The network element receives the MAC address of the inbound interface of the next hop network element of the network element sent by the controller; or receives the cross table of the network element sent by the controller, where the cross table includes at least the next hop of the network element The MAC address of the inbound interface of the NE, and the MAC address of the inbound interface of the next hop NE of the NE is obtained from the crosstab of the NE.

The network element is any network element in the MPLS-TP tunnel path.

Step 302: The network element encapsulates the MAC address of the inbound interface of the next hop network element of the network element into the MPLS packet.

Step 303: The network element sends the encapsulated MPLS packet to the next hop network element of the network element.

The next hop network element of the network element receives the encapsulated MPLS packet, and determines whether the MAC address of the inbound interface carried in the MPLS packet is the MAC address of the inbound interface of the local network element. If yes, repeat steps 301 and 302. And 303, and sending the MPLS packet to the next hop network element of the next hop network element; if not, discarding the MPLS packet.

In the embodiment of the present invention, the controller obtains the MAC address of the inbound interface of the next hop element of the first network element in the MPLS-TP tunnel path to be established, and the next hop of the first network element The MAC address of the inbound interface of the element is sent to the first network element, so that the first network element directly receives the MAC address of the inbound interface of the next hop element of the next hop element of the first network element, and does not need to be the network element. The IP address of the inbound interface is configured to implement IP-free planning and configuration. This solves the problem of troubleshooting error correction when the IP address configuration error occurs. This greatly reduces the workload of network maintenance. Moreover, the ARP protocol does not need to be run on the NE. , thereby improving the processing speed of the network element.

Example 4

When the MAC address of the interface of the network element included in the MPLS-TP tunnel path changes, the MAC address of the interface of the second network element changes as an example for convenience of description. The controller may update the cross-tab of the MPLS-TP tunnel by using the following steps. The execution body of the method is a controller. Referring to FIG. 4, the method includes:

Step 401: The controller receives the MAC address modification request of the inbound interface sent by the second network element, where the MAC address modification request of the inbound interface carries the inbound interface identifier of the second network element and the modified inbound interface. MAC address;

When the MAC address of the inbound interface of the second network element changes, the second network element sends a MAC address modification request of the inbound interface to the controller, and the MAC address modification request of the inbound interface carries at least the inbound interface of the second network element. The identifier and the modified MAC address of the inbound interface can also carry the NE identifier of the second network element. The controller receives the MAC address modification request of the inbound interface sent by the second network element, so as to update the MAC address of the inbound interface of the second network element, and step 402 is performed.

Further, when the controller receives the MAC address modification request of the inbound interface sent by the second network element, the controller obtains the inbound interface identifier of the second network element from the MAC address modification request of the inbound interface, and determines whether the ingress interface is a network side interface. If the inbound interface is a network side interface, step 402 is performed; if the ingress interface is not a network side interface, the process ends.

The step of determining whether the ingress interface is a network side interface may be:

The controller determines whether the inbound interface is enabled with MPLS or is on the line card. If the inbound interface is enabled with MPLS or on the line card, the ingress interface is determined to be the network side interface. If the inbound interface is not enabled with MPLS. If the board is not on the line card, the ingress interface is not the network side interface.

The MPLS-TP is enabled to forward MPLS packets.

Step 402: The controller updates the MAC address of the inbound interface of the second network element according to the MAC address of the inbound interface modified by the second network element.

The controller modifies the MAC address of the inbound interface of the second network element stored locally to the MAC address of the inbound interface of the second network element. And the controller determines that the MAC address of the inbound interface of the second network element is the MAC address of the inbound interface of the next hop element of the first network element;

Optionally, the step of the controller determining that the MAC address of the inbound interface of the second network element is the MAC address of the inbound interface of the next hop element of the first network element may be:

The controller traverses all the MPLS-TP tunnel paths included in the MPLS-TP network, and checks whether the MAC address of the inbound interface of the next hop element of the first network element in the MPLS-TP tunnel path is the MAC address of the inbound interface of the second network element. The address, if yes, determines that the MAC address of the inbound interface modified by the second network element is the MAC address of the inbound interface of the next hop element of the first network element.

Step 403: The controller updates the MAC address of the inbound interface of the second network element according to the MAC address of the inbound interface modified by the second network element.

The controller modifies the MAC address of the inbound interface of the second network element stored locally to the MAC address of the inbound interface of the second network element.

Step 404: The controller updates the first network according to the MAC address of the inbound interface modified by the second network element. MAC address of the inbound interface of the next hop element of the element;

The controller modifies the MAC address of the inbound interface of the next hop element of the first network element to the MAC address of the inbound interface of the second network element.

Optionally, the controller modifies, in the cross-tab of the first network element, the MAC address of the inbound interface of the next hop element of the first network element to the MAC address of the inbound interface of the second network element.

Step 405: The controller sends the MAC address of the inbound interface of the next hop element of the modified first network element to the first network element.

The first network element receives the modified MAC address of the inbound interface of the next hop of the first network element, and sends the MPLS packet to the next hop element of the modified first network element. The MAC address of the inbound interface is encapsulated into the MPLS packet, and the encapsulated MPLS packet is sent to the next hop NE of the first network element.

In this step, the controller may also send the modified cross table of the first network element to the first network element. The first network element receives the modified cross-tab sent by the controller. When the MPLS packet is sent, the first network element obtains the modified next-hop network element of the first network element from the modified cross-tab. The MAC address of the interface encapsulates the MAC address of the inbound interface of the next hop of the first network element into the MPLS packet, and sends the encapsulated MPLS packet to the next hop of the first NE. Network element.

It should be noted that, for each MPLS-TP tunnel in the MPLS-TP network, the cross-tab of the MPLS-TP tunnel is updated according to the above method.

In the embodiment of the present invention, the controller obtains the MAC address of the inbound interface of the next hop element of the first network element in the MPLS-TP tunnel path to be established, and the next hop of the first network element The MAC address of the inbound interface of the element is sent to the first network element, so that the first network element directly receives the MAC address of the inbound interface of the next hop element of the next hop element of the first network element, and does not need to be the network element. The IP address of the inbound interface is configured to implement IP-free planning and configuration. This solves the problem of troubleshooting error correction when the IP address configuration error occurs. This greatly reduces the workload of network maintenance. Moreover, the ARP protocol does not need to be run on the NE. , thereby improving the processing speed of the network element.

Example 5

The embodiment of the present invention provides an Ethernet interface addressing device in an MPLS-TP tunnel, and the device may be a controller. Referring to FIG. 5, the device includes:

The first obtaining module 501 is configured to obtain the inbound interface information of the first network element to the second network element in the MPLS-TP tunnel path of the transmission subset based on the multi-protocol label switching, in the MPLS-TP tunnel. The second network element in the path is the next hop network element of the first network element;

The second obtaining module 502 is configured to obtain, according to the inbound interface information of the first network element to the second network element, a media access control MAC address of the inbound interface of the first network element to the second network element;

The addressing module 503 is configured to obtain, according to the MAC address of the inbound interface of the first network element to the second network element, the MAC address of the inbound interface of the next hop element of the first network element, and the next hop of the first network element The MAC address of the inbound interface of the NE is sent to the first NE.

Further, the inbound interface information of the first network element to the second network element includes an inbound interface identifier of the second network element.

Further, the inbound interface information of the first network element to the second network element includes the network element identifier of the second network element and the inbound interface identifier of the second network element.

Further, the device further includes:

a storage module, configured to receive and save interface information of the second network element and a MAC address of the interface;

The interface information of the second network element includes the inbound interface identifier of the second network element and the network element identifier of the second network element, and the MAC address of the interface of the second network element includes the MAC address of the inbound interface of the second network element.

Further, the device further includes:

The first receiving module is configured to receive a MAC address modification request of the inbound interface of the second network element, where the MAC address modification request of the inbound interface carries the MAC address of the inbound interface modified by the second network element;

a first update module, configured to update, according to the MAC address of the inbound interface modified by the second network element, a MAC address of the inbound interface of the second network element;

And a second update module, configured to update, according to the MAC address of the inbound interface of the second network element, the MAC address of the inbound interface of the next hop element of the first network element.

In the embodiment of the present invention, the controller obtains the MAC address of the inbound interface of the next hop element of the first network element in the MPLS-TP tunnel path to be established, and the next hop of the first network element The MAC address of the inbound interface of the element is sent to the first network element, so that the first network element directly receives the MAC address of the inbound interface of the next hop element of the next hop element of the first network element, and does not need to be the network element. The IP address of the inbound interface is configured to implement IP-free planning and configuration. This solves the problem of troubleshooting error correction when the IP address configuration error occurs. This greatly reduces the workload of network maintenance. Moreover, the ARP protocol does not need to be run on the NE. , thereby improving the processing speed of the network element.

Example 6

Embodiments of the present invention provide an Ethernet interface addressing device in an MPLS-TP tunnel, and the device It can be a network element, see FIG. 6, wherein the device includes:

The third obtaining module 601 is configured to acquire an MPLS packet based on the multi-protocol label exchange;

The second receiving module 602 is configured to receive a media access control MAC address of an inbound interface of a next hop network element of the network element.

The encapsulating module 603 is configured to encapsulate the MAC address of the inbound interface of the next hop network element of the network element into the MPLS packet.

Further, the device further includes:

The first sending module is configured to send the interface information of the network element and the MAC address of the interface to the controller, so that the controller saves the interface information of the network element and the MAC address of the interface;

The interface information of the network element includes the inbound interface identifier of the network element and the network element identifier of the network element. The MAC address of the interface of the network element includes the MAC address of the inbound interface of the network element.

Further, the device further includes:

The second sending module is configured to send a MAC address modification request of the inbound interface to the controller, where the MAC address modification request of the inbound interface carries the MAC address of the inbound interface modified by the network element, so that the controller can modify the inbound according to the network element. The MAC address of the interface updates the MAC address of the inbound interface of the NE.

In the embodiment of the present invention, the controller obtains the MAC address of the inbound interface of the next hop element of the first network element in the MPLS-TP tunnel path to be established, and the next hop of the first network element The MAC address of the inbound interface of the element is sent to the first network element, so that the first network element directly receives the MAC address of the inbound interface of the next hop element of the next hop element of the first network element, and does not need to be the network element. The IP address of the inbound interface is configured to implement IP-free planning and configuration. This solves the problem of troubleshooting error correction when the IP address configuration error occurs. This greatly reduces the workload of network maintenance. Moreover, the ARP protocol does not need to be run on the NE. , thereby improving the processing speed of the network element.

Example 7

FIG. 7 is a schematic structural diagram of a controller according to another embodiment of the present invention, including: as shown in FIG. 7, the controller 700 includes a first processor 701, a first memory 702, a first transmitter 703, and a first Receiver 704, first input/output interface 705, first communication interface 706, and first bus 707. The first processor 701, the first memory 702, the first transmitter 703, the first receiver 704, the first input/output interface 705, and the first communication interface 706 implement communication connection with each other through the first bus 707. The first processor 701 can be a general-purpose central processing unit (CPU), a microprocessor, and an application-specific integrated circuit (Application Specific Integrated). The circuit (abbreviated as ASIC), or at least one integrated circuit, is used to execute the related program to implement the technical solution provided by the embodiment of the present invention. The first memory 702 can be a read only memory (ROM), a static storage device, a dynamic storage device, or a random access memory (RAM). The first memory 702 can store an operating system and other applications. When the technical solution provided by the embodiment of the present invention is implemented by software or firmware, the program code for implementing the technical solution provided by the embodiment of the present invention is saved in the first memory 702 and executed by the first processor 701. The first input/output interface 705 is configured to receive input data and information, and output data such as an operation result. The first communication interface 706 implements communication between the controller 700 and other devices or communication networks using transceivers such as, but not limited to, transceivers. The first bus 707 can include a path for communicating information between various components of the controller 700.

In a specific implementation process, the first processor 701 executes code stored in the first memory 702 for performing an Ethernet interface addressing method in an MPLS-TP tunnel:

Obtaining, by the controller, the inbound interface information of the first network element to the second network element in the MPLS-TP tunnel path of the transmission subset based on the multi-protocol label switching, where the second network is in the MPLS-TP tunnel path The element is a next hop network element of the first network element;

The controller acquires a media access control MAC address of the inbound interface of the first network element to the second network element according to the inbound interface information of the first network element to the second network element;

The controller obtains a MAC address of an inbound interface of a next hop network element of the first network element according to a MAC address of the inbound interface of the first network element to the second network element, where the first network is The MAC address of the inbound interface of the next hop element of the element is sent to the first network element.

Further, the inbound interface information of the first network element to the second network element includes an inbound interface identifier of the second network element.

Further, the inbound interface information of the first network element to the second network element includes a network element identifier of the second network element and an inbound interface identifier of the second network element.

Further, the controller obtains the media access control MAC address of the inbound interface of the first network element to the second network element according to the inbound interface information of the first network element to the second network element. ,Also includes:

The controller receives and saves interface information of the second network element and a MAC address of the interface;

The interface information of the second network element includes an inbound interface identifier of the second network element and a network element identifier of the second network element, where a MAC address of the interface of the second network element includes the second network element MAC address of the inbound interface.

Further, the method further includes:

The controller receives a MAC address modification request of the inbound interface of the second network element, where the MAC address modification request of the inbound interface carries the MAC address of the inbound interface modified by the second network element;

The controller updates the MAC address of the inbound interface of the second network element according to the MAC address of the inbound interface modified by the second network element;

The controller updates the MAC address of the inbound interface of the next hop network element of the first network element according to the MAC address of the inbound interface of the second network element.

In the embodiment of the present invention, the controller obtains the MAC address of the inbound interface of the next hop element of the first network element in the MPLS-TP tunnel path to be established, and the next hop of the first network element The MAC address of the inbound interface of the element is sent to the first network element, so that the first network element directly receives the MAC address of the inbound interface of the next hop element of the next hop element of the first network element, and does not need to be the network element. The IP address of the inbound interface is configured to implement IP-free planning and configuration. This solves the problem of troubleshooting error correction when the IP address configuration error occurs. This greatly reduces the workload of network maintenance. Moreover, the ARP protocol does not need to be run on the NE. , thereby improving the processing speed of the network element.

Example 8

FIG. 8 is a schematic structural diagram of a network element according to another embodiment of the present invention, including: as shown in FIG. 8, the network element 800 includes a second processor 801, a second memory 802, a second transmitter 803, and a second Receiver 804, second input/output interface 805, second communication interface 806, and second bus 807. The second processor 801, the second memory 802, the second transmitter 803, the second receiver 804, the second input/output interface 805, and the second communication interface 806 implement communication connection with each other through the second bus 807. The second processor 801 can be a general-purpose central processing unit (CPU), a microprocessor, an application specific integrated circuit (ASIC), or at least one integrated circuit for performing correlation. The program is implemented to implement the technical solutions provided by the embodiments of the present invention. The second memory 802 can be a read only memory (ROM), a static storage device, a dynamic storage device, or a random access memory (RAM). The second memory 802 can store an operating system and other applications. When the technical solution provided by the embodiment of the present invention is implemented by software or firmware, the program code for implementing the technical solution provided by the embodiment of the present invention is saved in the second memory 802 and executed by the second processor 801. The second input/output interface 805 is configured to receive input data and information, and output data such as an operation result. The second communication interface 806 uses a transceiver such as, but not limited to, a transceiver, Communication between the network element 800 and other devices or communication networks is implemented. The second bus 807 can include a path for communicating information between various components of the network element 800.

In a specific implementation process, the second processor 801 executes code stored in the second memory 802 for performing an Ethernet interface addressing method in an MPLS-TP tunnel:

The network element acquires an MPLS packet based on a multi-protocol label exchange;

Receiving, by the network element, a media access control MAC address of an inbound interface of a next hop network element of the network element;

The network element encapsulates the MAC address of the inbound interface of the next hop network element of the network element into the MPLS packet.

Further, before the acquiring, by the network element, the MPLS packet, the network element further includes:

The network element sends the interface information of the network element and the MAC address of the interface to the controller, so that the controller saves the interface information of the network element and the MAC address of the interface;

The interface information of the network element includes an inbound interface identifier of the network element and a network element identifier of the network element, and a MAC address of the interface of the network element includes a MAC address of an inbound interface of the network element.

Further, the method further includes:

Transmitting, by the network element, a MAC address modification request of the inbound interface to the controller, where the MAC address modification request of the inbound interface carries the MAC address of the inbound interface modified by the network element, so that the controller is configured according to the network The MAC address of the inbound interface of the meta-modified device updates the MAC address of the inbound interface of the network element.

In the embodiment of the present invention, the controller obtains the MAC address of the inbound interface of the next hop element of the first network element in the MPLS-TP tunnel path to be established, and the next hop of the first network element The MAC address of the inbound interface of the element is sent to the first network element, so that the first network element directly receives the MAC address of the inbound interface of the next hop element of the next hop element of the first network element, and does not need to be the network element. The IP address of the inbound interface is configured to implement IP-free planning and configuration. This solves the problem of troubleshooting error correction when the IP address configuration error occurs. This greatly reduces the workload of network maintenance. Moreover, the ARP protocol does not need to be run on the NE. , thereby improving the processing speed of the network element.

It should be noted that, when the Ethernet interface addressing device in the MPLS-TP tunnel provided by the foregoing embodiment is addressed by the Ethernet interface in the MPLS-TP tunnel, only the division of each functional module is used as an example. In practical applications, The above function assignment can be completed by different functional modules as needed, that is, the internal structure of the device is divided into different functional modules to complete all or part of the above description. Features. In addition, the Ethernet interface addressing device in the MPLS-TP tunnel provided by the foregoing embodiment is the same as the Ethernet interface addressing method in the MPLS-TP tunnel, and the specific implementation process is described in the method embodiment, and details are not described herein again. .

A person skilled in the art may understand that all or part of the steps of implementing the above embodiments may be completed by hardware, or may be instructed by a program to execute related hardware, and the program may be stored in a computer readable storage medium. The storage medium mentioned may be a read only memory, a magnetic disk or an optical disk or the like.

The above are only the preferred embodiments of the present invention, and are not intended to limit the present invention. Any modifications, equivalents, improvements, etc., which are within the spirit and scope of the present invention, should be included in the protection of the present invention. Within the scope.

Claims (24)

1. An Ethernet interface addressing method in an MPLS-TP tunnel, characterized in that the method includes:

   Obtaining, by the controller, the inbound interface information of the first network element to the second network element in the MPLS-TP tunnel path of the transmission subset based on the multi-protocol label switching, where the second network is in the MPLS-TP tunnel path The element is a next hop network element of the first network element;

   The controller acquires a media access control MAC address of the inbound interface of the first network element to the second network element according to the inbound interface information of the first network element to the second network element;

   The controller obtains a MAC address of an inbound interface of a next hop network element of the first network element according to a MAC address of the inbound interface of the first network element to the second network element, where the first network is The MAC address of the inbound interface of the next hop element of the element is sent to the first network element.
2. The method according to claim 1, wherein the inbound interface information of the first network element to the second network element comprises an inbound interface identifier of the second network element.
3. The method according to claim 1, wherein the inbound interface information of the first network element to the second network element comprises a network element identifier of the second network element and an entry of the second network element Interface identifier.
4. The method according to claim 1 or 3, wherein the controller acquires the first network element to the second according to the inbound interface information of the first network element to the second network element Before the media access control MAC address of the inbound interface of the NE, it also includes:

   The controller receives and saves interface information of the second network element and a MAC address of the interface;

   The interface information of the second network element includes an inbound interface identifier of the second network element and a network element identifier of the second network element, where a MAC address of the interface of the second network element includes the second network element MAC address of the inbound interface.
5. The method of claim 1 wherein the method further comprises:

   The controller receives a MAC address modification request of the inbound interface of the second network element, where the MAC address modification request of the inbound interface carries the MAC address of the inbound interface modified by the second network element;

   The controller updates the second network according to the MAC address of the inbound interface modified by the second network element The MAC address of the inbound interface of the element;

   The controller updates the MAC address of the inbound interface of the next hop network element of the first network element according to the MAC address of the inbound interface of the second network element.
6. An Ethernet interface addressing method in an MPLS-TP tunnel, characterized in that the method includes:

   The network element acquires an MPLS packet based on a multi-protocol label exchange;

   Receiving, by the network element, a media access control MAC address of an inbound interface of a next hop network element of the network element;

   The network element encapsulates the MAC address of the inbound interface of the next hop network element of the network element into the MPLS packet.
7. The method of claim 6, wherein before the acquiring, by the network element, the MPLS packet, the network element further includes:

   The network element sends the interface information of the network element and the MAC address of the interface to the controller, so that the controller saves the interface information of the network element and the MAC address of the interface;

   The interface information of the network element includes an inbound interface identifier of the network element and a network element identifier of the network element, and a MAC address of the interface of the network element includes a MAC address of an inbound interface of the network element.
8. The method of claim 6 wherein the method further comprises:

   Transmitting, by the network element, a MAC address modification request of the inbound interface to the controller, where the MAC address modification request of the inbound interface carries the MAC address of the inbound interface modified by the network element, so that the controller is configured according to the network The MAC address of the inbound interface of the meta-modified device updates the MAC address of the inbound interface of the network element.
9. An Ethernet interface addressing device in an MPLS-TP tunnel, characterized in that the device comprises:

   a first acquiring module, configured to acquire inbound interface information of the first network element to the second network element in the MPLS-TP tunnel path of the transmission subset based on the multi-protocol label switching, in the MPLS-TP tunnel path The second network element is a next hop network element of the first network element;

   a second obtaining module, configured to acquire, according to the inbound interface information of the first network element to the second network element, a media access control MAC address of the inbound interface of the first network element to the second network element;

   An addressing module, configured to obtain, according to a MAC address of the inbound interface of the first network element to the second network element, a MAC address of an inbound interface of a next hop network element of the first network element, where the The MAC address of the inbound interface of the next hop network element of a network element is sent to the first network element.
10. The device according to claim 9, wherein the inbound interface information of the first network element to the second network element comprises an inbound interface identifier of the second network element.
11. The device according to claim 9, wherein the inbound interface information of the first network element to the second network element comprises a network element identifier of the second network element and an entry of the second network element Interface identifier.
12. The device according to claim 9 or 11, wherein the device further comprises:

    a storage module, configured to receive and save interface information of the second network element and a MAC address of the interface;

    The interface information of the second network element includes an inbound interface identifier of the second network element and a network element identifier of the second network element, where a MAC address of the interface of the second network element includes the second network element MAC address of the inbound interface.
13. The device of claim 9 wherein said device further comprises:

    The first receiving module is configured to receive a MAC address modification request of the inbound interface of the second network element, where the MAC address modification request of the inbound interface carries the MAC address of the inbound interface modified by the second network element;

    a first update module, configured to update, according to the MAC address of the inbound interface that is modified by the second network element, a MAC address of the inbound interface of the second network element;

    And a second update module, configured to update, according to the MAC address of the inbound interface of the second network element, the MAC address of the inbound interface of the next hop element of the first network element.
14. An Ethernet interface addressing device in an MPLS-TP tunnel, characterized in that the device comprises:

    a third acquiring module, configured to acquire an MPLS packet based on a multi-protocol label exchange;

    a second receiving module, configured to receive a media access control MAC address of an inbound interface of a next hop network element of the network element;

    An encapsulating module, configured to encapsulate a MAC address of an inbound interface of a next hop network element of the network element into the In MPLS packets.
15. The device of claim 14 wherein said device further comprises:

    The first sending module is configured to send the interface information of the network element and the MAC address of the interface to the controller, so that the controller saves the interface information of the network element and the MAC address of the interface;

    The interface information of the network element includes an inbound interface identifier of the network element and a network element identifier of the network element, and a MAC address of the interface of the network element includes a MAC address of an inbound interface of the network element.
16. The device of claim 14 wherein said device further comprises:

    a second sending module, configured to send a MAC address modification request of the inbound interface to the controller, where the MAC address modification request of the inbound interface carries the MAC address of the inbound interface modified by the network element, so that the controller is configured according to the The MAC address of the inbound interface of the network element is updated to update the MAC address of the inbound interface of the network element.
17. A controller, the controller comprising: a first processor and a first transmitter;

    The first processor is configured to acquire inbound interface information of the first network element to the second network element in the MPLS-TP tunnel path of the multi-protocol label switching based on the multi-protocol label switching, in the MPLS-TP tunnel The second network element in the path is a next hop network element of the first network element;

    The first processor is further configured to acquire media access control of the inbound interface of the first network element to the second network element according to the inbound interface information of the first network element to the second network element. MAC address;

    The first processor is further configured to obtain, according to a MAC address of the inbound interface of the first network element to the second network element, a MAC address of an inbound interface of a next hop network element of the first network element;

    The first transmitter is configured to send, to the first network element, a MAC address of an inbound interface of a next hop network element of the first network element.
18. The controller according to claim 17, wherein the inbound interface information of the first network element to the second network element comprises an inbound interface identifier of the second network element.
19. The controller according to claim 17, wherein the inbound interface information of the first network element to the second network element comprises a network element identifier of the second network element and the second network element Incoming interface knowledge.
20. A controller according to claim 17 or 19, wherein

    The first processor is further configured to receive and save interface information of the second network element and a MAC address of the interface;

    The interface information of the second network element includes an inbound interface identifier of the second network element and a network element identifier of the second network element, where a MAC address of the interface of the second network element includes the second network element MAC address of the inbound interface.
21. The controller of claim 17, wherein the controller further comprises: a first receiver;

    The first receiver is configured to receive a MAC address modification request of the inbound interface of the second network element, where the MAC address modification request of the inbound interface carries the MAC address of the inbound interface modified by the second network element ;

    The first processor is further configured to: update, according to the MAC address of the inbound interface that is modified by the second network element, a MAC address of the inbound interface of the second network element;

    The first processor is further configured to update, according to the MAC address of the inbound interface of the second network element, a MAC address of an inbound interface of the next hop element of the first network element.
22. A network element, where the network element includes: a second processor and a second receiver;

    The second processor is configured to acquire an MPLS packet based on a multi-protocol label exchange;

    The second receiver is configured to receive a media access control MAC address of an inbound interface of a next hop network element of the network element;

    The second processor is further configured to encapsulate a MAC address of an inbound interface of a next hop network element of the network element into the MPLS packet.
23. The network element according to claim 22, wherein the network element further comprises: a second transmitter;

    The second transmitter is configured to send the interface information of the network element and the MAC address of the interface to the controller, so that the controller saves the interface information of the network element and the MAC address of the interface;

    The interface information of the network element includes an inbound interface identifier of the network element and a network element identifier of the network element. The MAC address of the interface of the network element includes the MAC address of the inbound interface of the network element.
24. The network element according to claim 22, wherein the network element further comprises: a second transmitter;

    The second transmitter is further configured to send a MAC address modification request of the inbound interface to the controller, where the MAC address modification request of the inbound interface carries the MAC address of the inbound interface modified by the network element, so as to facilitate the The controller updates the MAC address of the inbound interface of the network element according to the MAC address of the inbound interface modified by the network element.

Images