CN101184017A - Ethernet tunnel processing method, communication system and related equipment - Google Patents

Abstract

The invention discloses an Ethernet tunnel processing method, a communication system and related equipment, which are used to improve the efficiency of Ethernet tunnel processing. The method of the invention includes: receiving the tunnel establishment request sent by the source maintenance endpoint MEP; and establishing the Ethernet tunnel according to the tunnel establishment request and preset tunnel establishment parameters. The invention also provides a communication system and related equipment. The invention can effectively improve the efficiency of Ethernet tunnel processing.

Description

Ethernet tunnel processing method, communication system and related equipment

technical field

The invention relates to the communication field, in particular to an Ethernet tunnel processing method, a communication system and related equipment.

Background technique

As Ethernet is widely used in the metropolitan area, many problems of traditional Ethernet in operation, management and maintenance (OAM, Operations, Administration, and Maintenance) and scalability are becoming more and more prominent. In order to enable Metro Ethernet to have the same capabilities as traditional telecommunication networks in the above aspects, the industry has conducted extensive research on carrier-class Ethernet technologies.

For the carrier Ethernet (CE, Carrier Ethernet) solution, it is mainly implemented based on the media access control stack (Mac-in-Mac) technology. Among them, Provider Backbone Bridging Traffic Engineering (PBB-TE, Provider Backbone Bridging Traffic Engineering), or Provider Backbone Transport (PBT, Provider Backbone Transport) is a carrier-class Ethernet solution based on Mac-in-Mac technology plan.

The core of PBB-TE is: configure through network management and network control, so that the Ethernet service has connectivity in fact, so as to realize the functions of the telecommunication transmission network such as protection switching, OAM, traffic engineering; use MAC-in in the forwarding process -MAC encapsulation to isolate provider network and user network. The core idea of PBB-TE is to transform connectionless Ethernet into a connection-oriented technology through static configuration, so that operators can provide value-added services to users on the basis of protecting existing investments.

PBB-TE uses MAC-in-MAC encapsulation to isolate provider network and user network during forwarding. PBB-TE implements the transparent transmission of customer packets in the provider network by establishing a PBB-TE tunnel in the provider network.

In the Ethernet maintenance domain, there are generally several maintenance endpoints (MEP, Maintenance association End Point) and several maintenance intermediate nodes (MIP, Maintenance domain Intermediate Point). The Ethernet tunnel established between two MEPs may pass through several MIPs, so in order to realize the transparent transmission of customer packets in the provider network, it is necessary to establish Ethernet tunnels between MEPs and maintain the established tunnels .

A method for maintaining an Ethernet tunnel in the prior art is as follows: the administrator manually configures the data on each MEP and MIP to create an Ethernet tunnel. When a MIP or MEP in the tunnel fails, the tunnel needs to be manually Adjust the data configured on other MIPs or MEPs.

In the process of realizing the present invention, the inventor found that the disadvantages of the above-mentioned technologies are: since the creation and maintenance of Ethernet tunnels need to manually configure the data on the MEP and MIP to be realized, the difficulty of configuration and management is greatly increased, and the improve the efficiency of Ethernet tunnel processing.

Contents of the invention

The embodiment of the present invention provides an Ethernet tunnel processing method, a communication system and related equipment, which can improve the efficiency of Ethernet tunnel processing.

The method for processing an Ethernet tunnel provided by an embodiment of the present invention includes: receiving a tunnel establishment request sent by a source maintenance endpoint MEP; and establishing an Ethernet tunnel according to the tunnel establishment request and preset tunnel establishment parameters.

The Ethernet tunnel processing method provided by the embodiment of the present invention includes: establishing a transmission control tunnel according to the data transmission requirement information; acquiring the source MEP and destination MEP information of the transmission control tunnel; When performing data transmission, a data transmission tunnel between the source MEP and a destination MEP is established through the transmission control tunnel; and the transmission control tunnel is maintained according to a preset maintenance rule.

The communication system provided by the embodiment of the present invention includes: a source MEP, configured to send a tunnel establishment request including path information; an MIP, configured to receive the tunnel establishment request sent by the source MEP, and Establish a forwarding table with tunnel establishment parameters, feed back a tunnel establishment response to the source MEP, and forward the tunnel establishment request according to the path information in the tunnel establishment request until the destination MEP is reached; the destination MEP is used to receive the tunnel forwarded by the MIP Establish a request, and feed back a tunnel establishment response to the source MEP through the MIP.

The maintenance endpoint provided by the embodiment of the present invention includes: a tunnel processing request unit, configured to send a tunnel establishment request, or a tunnel deletion request, or a tunnel update request to the MIP or the peer MEP; a processing response receiving unit, configured to receive the MIP or the peer MEP Tunnel Establishment Response, Tunnel Delete Response, or Tunnel Update Response sent by the end MEP.

The maintenance intermediate node provided by the embodiment of the present invention, the maintenance intermediate node includes: a tunnel processing receiving unit, configured to receive a tunnel establishment request, a tunnel deletion request, or a tunnel update request sent by a MEP; a tunnel processing response unit, configured to send The MEP sends a tunnel establishment response, or a tunnel deletion response, or a tunnel update response; the tunnel processing unit is configured to perform corresponding processing on the forwarding table according to the tunnel establishment request, or the tunnel deletion request, or the tunnel update request; the data forwarding unit is configured to The data is forwarded according to the path information in the tunnel establishment request, tunnel deletion request, or tunnel update request.

It can be seen from the above technical solutions that the embodiments of the present invention have the following advantages:

Since the network element receives the tunnel establishment request sent by the source MEP, it will establish the Ethernet tunnel according to the tunnel establishment request and the preset tunnel establishment, so the automatic establishment of the Ethernet tunnel can be realized, thereby improving the processing efficiency of the Ethernet tunnel. efficiency.

Description of drawings

Fig. 1 is the flowchart of the first embodiment of the Ethernet tunnel processing method in the embodiment of the present invention;

FIG. 2 is a schematic diagram of an automatic information discovery process in Ethernet tunnel processing in an embodiment of the present invention;

FIG. 3 is a schematic diagram of a flow diagram of selecting a network element in Ethernet tunnel processing in an embodiment of the present invention;

4 is a schematic diagram of an information negotiation process in Ethernet tunnel processing in an embodiment of the present invention;

5 is a schematic diagram of a tunnel establishment process in Ethernet tunnel processing in an embodiment of the present invention;

6 is a flow chart of the second embodiment of the Ethernet tunnel processing method in the embodiment of the present invention;

FIG. 7 is a schematic diagram of an embodiment of a communication system in an embodiment of the present invention;

FIG. 8 is a schematic diagram of an embodiment of a maintenance endpoint in an embodiment of the present invention;

FIG. 9 is a schematic diagram of an embodiment of maintaining an intermediate node in an embodiment of the present invention.

Detailed ways

The embodiment of the present invention provides an Ethernet tunnel processing method, a communication system and related equipment, which are used to improve the efficiency of Ethernet tunnel processing.

In the embodiment of the present invention, since the network element receives the tunnel establishment request sent by the source MEP, it will establish the Ethernet tunnel according to the tunnel establishment request and the preset tunnel establishment, so the automatic establishment of the Ethernet tunnel can be realized, thereby improving improve the efficiency of Ethernet tunnel processing.

Referring to Fig. 1, the first embodiment of the Ethernet tunnel processing method in the embodiment of the present invention includes:

101. Configure the MEP in the maintenance domain (MD, Maintenance Domain);

In this embodiment, in order to be able to realize the automatic processing (comprising setting up, deleting, updating) of Ethernet tunnel, need at first carry out necessary configuration to MEP in MD, specific configuration includes setting backbone network purpose MAC address (B-DA, Backbone Destination MAC Address), backbone network source MAC address (B-SA, Backbone Source MAC Address) and backbone network virtual local area network (B-VLAN, Backbone Virtual Local Area Network) and other information, it is understandable to use these information as tunnel establishment parameters Notably, in different application environments, specific tunnel establishment parameters may change, and this embodiment only uses these three parameters as an example for illustration.

102. Broadcast the configured tunnel establishment parameters to network elements in the MD;

After the necessary configuration is completed for the MEP in the MD, the configured tunnel establishment parameters need to be broadcast to other MEPs in the MD. In order to realize the broadcast, the OAM message needs to be extended in this embodiment, here to expand the connectivity Check the message (CCM, Continuity Check Message) message as an example to illustrate, first need to reset the OpCode parameter in the extended CCM message, this parameter is used to identify the current message as a signaling message, in this embodiment, the extended CCM The parameter value of the OpCode parameter of the message is set to 11. It can be understood that, in the specific implementation process, the parameter value of this parameter can also be changed to other values, as long as the extended CCM message (hereinafter referred to as the CCM message) can be identified It can be a signaling message.

After resetting the OpCode, it is necessary to expand the new "Type-Length-Value" (TLV, TypeLength Value) parameter to carry the tunnel establishment parameters. Specifically, the following settings can be used:

Type is 70, Length is the length of the MAC address, and Value is B-DA;

Type is 71, Length is the length of the MAC address, and Value is B-SA;

TYpe is 72, Length is the length of VLAN, and Value is B-VLAN;

TYpe is 73, Length is the maximum length of the bandwidth, and Value is the bandwidth value to be reserved for the tunnel.

The foregoing is only an example for illustration, and it can be understood that specific parameter values may be modified according to actual conditions.

After the expansion of the CCM message is completed, the source MEP broadcasts the CCM message containing the tunnel establishment parameters to other MEPs in the MD. It should be noted that when the MD contains a MIP, the MEP may broadcast to other MEPs After some MIPs, the specific broadcast process is shown in Figure 2: MEP1 carries the tunnel establishment parameters in the CCM message and broadcasts to MEP2, and the broadcast process will pass through MIP1, and then MIP2 will reach MEP2. , it should be noted that MEP2 will also broadcast its own tunnel establishment parameters through MIP2 and MIP1 to MEP1 in a CCM message.

103. The network element in the MD saves necessary tunnel establishment parameters;

After each network element receives the tunnel establishment parameters, it will save the received parameters locally. Among them, the MIP only needs to save the necessary parameters for subsequent establishment of the forwarding table, such as B-DA, B-SA and B-VLAN, while the MEP All parameters need to be saved.

104. Broadcast tunnel establishment conditions to network elements in the MD;

After the source MEP publishes its own configured tunnel establishment parameters to the MD, when the MD contains a MIP (that is, when the communication between the source MEP and the destination MEP needs to pass through a certain MIP), it needs to select the MIP and MEP suitable for establishing the tunnel, then the source MEP The MEP needs to broadcast the tunnel establishment conditions in the MD, which can be implemented by extending the Link Trace Message (LTM, Linktrace Message) message. First, it is necessary to reset the OpCode parameter in the extended LTM message. This parameter is used to identify the current message as Signaling message, in this embodiment, the parameter value of the OpCode parameter of the extended LTM message is set to 15. It can be understood that, in the specific implementation process, the parameter value of this parameter can also be changed to other values, as long as it can be identified The extended LTM message (hereinafter referred to as the LTM message) may be a signaling message.

After resetting the OpCode, you need to expand the new TLV parameters to carry the tunnel establishment parameters. Specifically, you can use the following settings:

Type is 70, Length is the length of the MAC address, and Value is B-DA;

Type is 71, Length is the length of the MAC address, and Value is B-SA;

Type is 72, Length is the length of VLAN, and Value is B-VLAN;

Type is 73, Length is the maximum length of the bandwidth, and Value is the bandwidth value to be reserved for the tunnel.

The foregoing is only an example for illustration, and it can be understood that specific parameter values may be modified according to actual conditions.

After the expansion of the LTM message is completed, the source MEP broadcasts the LTM message containing the tunnel establishment conditions to other MEPs in the MD, but the broadcast process will pass through some MIPs. The specific broadcast process is shown in Figure 3: MEP1 establishes the tunnel The conditions are carried in the LTM message and broadcast to MEP2. The broadcast process will pass through MIP1, and MIP2 will reach MEP2. It should be noted that MEP2 also broadcasts its own tunnel establishment conditions through MIP2, MIP1 and MEP1 in the form of an LTM message.

The tunnel establishment conditions in this embodiment may include bandwidth requirements, and the configuration information of the MEP must be corresponding, that is, the B-DA of the source MEP must be the B-SA of the peer MEP, and the B-SA of the source MEP must be that of the peer MEP. For the B-DA, the B-VLAN of the source MEP must be the same as the B-VLAN of the remote MEP. It can be understood that this condition may also include other restrictions in the specific implementation process.

When the network element in the MD receives the tunnel establishment condition, it will judge whether it satisfies the tunnel establishment condition according to its own attributes. The next network element (for example, the next MIP) forwards the tunnel establishment condition, and if it is not satisfied, no LTR message is fed back.

It should be noted that, in order to correspond to the LTM message, the LTR message also needs to be extended in this embodiment. The specific extension method is similar to the method of extending the LTM message. The OpCode parameter is set to 14, and the expansion of the TLV parameter is consistent with the expansion of the TLV parameter in the LTM message.

105. Select a network element that satisfies the tunnel establishment condition;

After the source MEP receives the LTRs fed back in the MD, it selects the network elements that feed back these LTRs as the network elements that meet the tunnel establishment conditions.

106. Generate path information according to network elements that meet the tunnel establishment conditions;

In this embodiment, the LTR fed back by the network element will carry the information of the network element itself, including the MAC address and the like.

After the source MEP obtains the LTR, it calculates the sequence of the MIPs it needs to pass through and the peer MEP it reaches when transmitting data. The specific calculation method can be as follows: first determine the source MEP and destination MEP, and follow the preset plan (such as The shortest algorithm) selects the MIP that the shortest transmission path needs to go through, and determines the MIP according to the distance from the source MEP to the destination MEP.

107. Perform information negotiation with the peer MEP according to the path information;

In this embodiment, after the path information is calculated, the source MEP needs to perform information negotiation with the destination MEP, and the specific content of the negotiation may be data transmission format, data transmission rate and other information.

Concrete negotiation can be realized by extending the loopback message (LBM, Loopback Message) message, first need to reset the OpCode parameter in the extended LBM message, this parameter is used for identifying current message as signaling message, in the present embodiment The parameter value of the OpCode parameter of the extended LBM message is set to 13, it can be understood that, in the specific implementation process, the parameter value of this parameter can also be changed to other values, as long as the extended LBM message (hereinafter referred to as LBM message) may be a signaling message.

After redefining the OpCode, new TLV parameters need to be expanded. The specific way to expand the TLV parameters is the same as the aforementioned way to expand the TLV parameters of other OAM packets, and will not be repeated here.

After the extension of the LBM message is completed, the source MEP conducts information negotiation with the destination MEP through the MIP. Please refer to Figure 4 for details. MEP1 sends a negotiation command containing path information to MIP1. The negotiation command also contains the content that needs to be negotiated. After receiving the negotiation command, MIP1 reads the next forwarding network element from the path information. MAC address, that is, read the MAC address of MIP2, and forward the negotiation command to MIP2. Similarly, MIP2 reads the MAC address of the next forwarding network element from the path information, that is, reads the MAC address of MEP2, and sends the The negotiation command is forwarded to MEP2, and MEP2 negotiates with the information in the received negotiation command according to its own configuration attributes (such as information including data format, data transmission rate, etc.), and sends a message to MEP1 through a loopback response (LBR, Loopback Reply) message. In response, the LBR message also needs to be extended, and the OpCode parameter of the extended LBR message (hereinafter referred to as the LBR message) needs to be reset to 12, and the expansion of the TLV parameter is consistent with the expansion of the TLV parameter in the LBM message. It can be understood that, at the same time, MEP2 sends its own configuration attributes to MEP1 in the same manner to complete information negotiation.

108. Create an Ethernet tunnel.

After the source MEP and the destination MEP complete the information negotiation, the Ethernet tunnel can be established. The specific establishment process is shown in Figure 5, wherein, MEP1 sends a tunnel establishment request containing path information to MIP1, and the establishment request can be carried in the extended LTM message In this paper, the extension method is consistent with the previous method for extending the LTM message. After receiving the tunnel establishment request, MIP1 reads the path information and the tunnel establishment parameters saved by MIP1 in step 103, and according to the path information and the tunnel establishment request Parameters generate a forwarding table, and feed back the LTR message to MEP1, and forward the tunnel establishment request to MIP2 according to the generated forwarding table. After receiving the tunnel establishment request, MIP2 reads the path information therein and saves it in step 103 According to the tunnel establishment parameters, a forwarding table is generated according to the path information and tunnel establishment parameters, and the LTR message is fed back to MEP1 through MIP1, and the tunnel establishment request is forwarded to MEP2 according to the generated forwarding table. After receiving the tunnel establishment request, MEP2 passes MIP1 and MIP2 feed back LTR messages to MEP1, and at the same time create an entity locally, that is, generate an entity for encapsulating data. It is understandable that MEP1 also needs to generate an entity for encapsulating data locally after sending the tunnel establishment request. The entity can encapsulate the received data into corresponding protocol packets (such as real-time streaming protocol packets) according to the properties of the tunnel (for example, the tunnel adopts real-time streaming protocol transmission), and transmit them in the tunnel.

It should be noted that after the tunnel is established, the MEP can send a tunnel delete request or a tunnel update request to the MIP and the peer MEP:

When the MIP receives the tunnel deletion request containing the path information sent by the source MEP, it deletes the locally saved forwarding table according to the tunnel deletion request, and forwards the tunnel deletion request to the next MIP according to the path information, and the next MIP performs the same operation until the final The tunnel deletion request is forwarded to the destination MEP, and the destination MEP deletes the data encapsulation entity, thereby completely deleting the tunnel;

When the MIP receives the tunnel update request containing path information and update information sent by the source MEP, it updates the locally stored forwarding table according to the update information in the tunnel update request, and forwards the tunnel update request to The next MIP, the next MIP performs the same operation until the final tunnel update request is forwarded to the destination MEP, then the destination MEP updates the locally saved parameters, thereby completing the tunnel update.

In this embodiment, after receiving the tunnel establishment request containing path information sent by the source MEP, the MIP will establish a forwarding table according to the tunnel establishment request and preset tunnel establishment parameters, feed back a tunnel establishment response to the source MEP, and The path information in the tunnel establishment request forwards the tunnel establishment request until reaching the destination MEP. Therefore, in the tunnel establishment process, each network element will perform corresponding processing according to the request after receiving the establishment request, such as establishing a forwarding table, and forwarding according to the path information in the establishment request, so the automatic establishment of the Ethernet tunnel can be realized. Thereby, the efficiency of Ethernet tunnel processing is improved.

The above technical solution describes the inclusion of MIP in the MD, that is, the communication between two MEPs needs to go through some MIPs. It can be understood that some simple MDs may not contain MIPs, then the above embodiment The broadcast process in MEP is directly from one MEP to another MEP. At the same time, when the tunnel is established, MIP does not need to establish the forwarding table. When the tunnel is deleted, the MIP does not need to delete the forwarding table. The foregoing embodiments are the same, and will not be repeated here.

The above technical solution describes a completely dynamic tunnel processing method. Another implementation method is introduced below. This implementation method described below can further effectively reduce the cost of tunnel maintenance on the premise of improving the efficiency of Ethernet tunnel processing. Please Referring to Fig. 6, the second embodiment of the Ethernet tunnel processing method in the embodiment of the present invention includes:

601. Establish a transmission control tunnel according to the data transmission requirement information;

In this embodiment, firstly, a specific path needs to be planned in the provider network for data forwarding, that is, a physical path including a source MEP, a destination MEP, and several MIPs is determined in the MD. For this reason, it is necessary to manually create an Ethernet tunnel, which is not used to carry services, but is only used as a transmission control tunnel for subsequent creation of a data transmission tunnel with the same physical path from the source to the sink. It should be noted that the way to establish a transmission control tunnel is consistent with the way of manually configuring tunnels in the prior art. A tunnel can be manually planned as a transmission control tunnel according to specific requirements. The specific requirements can be bandwidth requirements or path requirements, or other transmission requirements.

602. Obtain the source MEP and destination MEP information of the tunnel;

After the transmission control tunnel is established, the source MEP information and the destination MEP information of the tunnel are obtained, including the configuration information configured on the destination MEP.

603. The source MEP broadcasts the source end configuration information to the destination MEP of the transmission control tunnel through the MIP;

When an Ethernet tunnel needs to be created to transmit data later, the source end configuration information is first broadcast through the transmission control tunnel. Among them, the source configuration information includes: resource information (such as bandwidth resources) necessary for tunnel operation, endpoint configuration information (such as B-DA, B-SA, B-VLAN, etc., where B-DA and B-SA are not necessary configuration, because the endpoint of the newly created tunnel must be the same as the endpoint of the transmission control tunnel, only the B-VLAN is different).

604. Receive destination end configuration information fed back by the destination MEP;

After the source end configuration information is broadcast, the source MEP receives the destination end configuration information fed back by the destination MEP.

605. Determine whether the configuration information of the source end is consistent with the configuration information of the destination end, if they are consistent, execute step 606, and if not, execute step 608;

The source MEP compares the obtained configuration information of the destination end of the destination MEP with the local configuration information of the source end.

606. Establish a data transmission tunnel between the source MEP and the destination MEP;

If the source configuration information is consistent with the destination configuration information (for example, the B-DA configured on the local If the B-VLANs of the ends are the same), a data transmission tunnel is established between the two MEPs, and the specific creation method is consistent with the tunnel creation process described in the first embodiment of the Ethernet tunnel processing method in the embodiment of the present invention.

It should be noted that if the configuration of the created data transmission tunnel changes, the updated configuration information can also be broadcast to other network elements that the data transmission tunnel passes through, and other network elements (including MEP and MIP) receive information to update your own configuration.

If a MEP deletes a data transmission tunnel, it can also broadcast to other NEs that the data transmission tunnel passes through. The MIP can choose to delete the corresponding forwarding table, and the peer MEP can choose to delete the created data transmission tunnel.

If the data transmission tunnel to be established has resource limitations such as bandwidth, the MEP can advertise the tunnel establishment conditions to other NEs in the network during the broadcast process, and other NEs will respond if they meet the tunnel establishment conditions. In the tunnel establishment phase, data transmission tunnels are only established between network elements that meet the tunnel establishment conditions.

607. Maintain the transmission control tunnel and end the process;

In this embodiment, since the transmission control tunnel is specially used to serve the data transmission tunnel used for forwarding services that is the same as its physical path, during the maintenance process of the Ethernet tunnel, only the information maintenance of the transmission control tunnel can be performed. Yes, other data transmission tunnels can share the configuration information of the transmission control tunnel, so there is no need to perform information maintenance for each data transmission tunnel, thereby reducing the maintenance cost of the Ethernet tunnel.

608. Execute other exception handling processes.

If the source MEP judges that the source configuration information is inconsistent with the destination configuration information, it will execute the exception handling process, which may be to abandon the establishment of the current data transmission tunnel, or request the peer MEP to resend the destination configuration information.

The following describes the embodiment of the communication system in the embodiment of the present invention. Please refer to FIG. 7. The embodiment of the communication system in the embodiment of the present invention includes:

Source maintenance endpoint 701, configured to send a tunnel establishment request including path information;

The maintenance intermediate node 702 is configured to receive the tunnel establishment request sent by the source maintenance endpoint 701, establish a forwarding table according to the tunnel establishment request and preset tunnel establishment parameters, and feed back a tunnel establishment response to the source maintenance endpoint 701, and according to The path information in the tunnel establishment request forwards the tunnel establishment request until reaching the destination maintenance endpoint 703;

The destination maintenance endpoint 703 is configured to receive the tunnel establishment request forwarded by the maintenance intermediate node 702 , and feed back a tunnel establishment response to the source maintenance endpoint 701 through the maintenance intermediate node 702 .

Please refer to Figure 8, the embodiment of the maintenance endpoint in the embodiment of the present invention includes:

A tunnel processing request unit 801, configured to send a tunnel establishment request, or a tunnel deletion request, or a tunnel update request to the MIP or the peer MEP;

The processing response receiving unit 802 is configured to receive a tunnel establishment response, a tunnel deletion response, or a tunnel update response sent by the MIP or the peer MEP.

In this embodiment, the maintenance endpoint may further include a tunnel establishment control unit 803, and the tunnel establishment control unit 803 includes:

The configuration information broadcasting unit 8031 is configured to broadcast preset configuration information to MEPs in the maintenance domain to which the maintenance endpoint belongs through the MIP;

A network element selection unit 8032, configured to select a MIP and MEP that meet the tunnel establishment conditions from MIPs and other MEPs in the maintenance domain to which the maintenance endpoint belongs;

A path generating unit 8033, configured to generate path information according to the MIP and MEP that meet the tunnel establishment conditions;

The information negotiation unit 8034 is configured to perform information negotiation with the peer MEP through the MIP that meets the tunnel establishment condition.

In this embodiment, the maintenance endpoint may further include:

The data encapsulation unit 804 is configured to encapsulate and send the data packet according to the tunnel transmission attribute after the tunnel is established.

Please refer to Figure 9, the embodiment of maintaining intermediate nodes in the embodiment of the present invention includes:

The tunnel processing receiving unit 901 is configured to receive a tunnel establishment request, a tunnel deletion request, or a tunnel update request sent by the MEP;

A tunnel processing response unit 902, configured to send a tunnel establishment response, or a tunnel deletion response, or a tunnel update response to the MEP;

The tunnel processing unit 903 is configured to perform corresponding processing on the forwarding table according to the tunnel establishment request, or the tunnel deletion request, or the tunnel update request;

The data forwarding unit 904 is configured to forward data according to the path information in the tunnel establishment request, tunnel deletion request, or tunnel update request.

Those of ordinary skill in the art can understand that all or part of the steps in the method of the above-mentioned embodiments can be completed by instructing related hardware through a program. The program can be stored in a computer-readable storage medium, and the program can be executed when executed ,include:

The maintenance intermediate node MIP receives the tunnel establishment request containing path information sent by the source maintenance endpoint MEP; establishes a forwarding table according to the tunnel establishment request and preset tunnel establishment parameters; feeds back a tunnel establishment response to the source MEP, and The path information in the request forwards the tunnel establishment request until reaching the destination MEP.

The storage medium mentioned above may be a read-only memory, a magnetic disk or an optical disk, and the like.

The above has introduced in detail the Ethernet tunnel processing method, communication system and related equipment provided by the embodiment of the present invention. For those of ordinary skill in the art, based on the idea of the embodiment of the present invention, in terms of specific implementation and application range There will be changes. In summary, the contents of this specification should not be construed as limiting the present invention.

Claims (18)

1. an Ethernet tunnel processing method is characterized in that, comprising:

Request is set up in the tunnel that reception sources maintaining end point MEP sends;

According to described tunnel setting up request and the tunnel that presets is set up parameter and set up the Ethernet tunnel.

2. method according to claim 1 is characterized in that, and is described according to described tunnel setting up request and the tunnel that presets is set up parameter and set up the Ethernet tunnel and comprise:

Purpose MEP sets up request to the foundation response of source MEP feedback tunnel according to the tunnel, sets up parameter according to the tunnel that presets and generates the entity that is used for encapsulation of data.

3. method according to claim 1 is characterized in that, described tunnel is set up in the request and comprised routing information;

Described according to described tunnel setting up request and the tunnel that presets is set up parameter and set up the Ethernet tunnel and comprise:

Safeguard that intermediate node MIP sets up request according to described tunnel and the tunnel that presets is set up parameter and set up and transmit;

Set up response to source MEP feedback tunnel, and transmit described tunnel according to the routing information in the foundation request of described tunnel and set up request until the MEP that achieves the goal.

4. method according to claim 3 is characterized in that, the tunnel that described reception sources MEP sends comprises before setting up request:

Source MEP sets up parameter by the tunnel that other MEP broadcasting in the maintenance field of MIP under it are preset;

Receiving described tunnel sets up the MIP of parameter and MEP and parameter is set up in described tunnel is kept at this locality.

5. method according to claim 4 is characterized in that, the tunnel that described reception sources MEP sends comprises before setting up request:

Choose MIP in the maintenance field of source MEP under it and other MEP and satisfy MIP and the MEP that condition is set up in the tunnel;

According to MIP that selects and MEP generation pass information.

6. method according to claim 5 is characterized in that, chooses the MIP in the maintenance field of described source MEP under it and other MEP to satisfy the tunnel and set up the MIP and the MEP of condition and comprise:

Source MEP sets up conditional information by other MEP broadcast tunnels in the maintenance field of MIP under described source MEP, and described tunnel is set up and comprised bandwidth demand in the conditional information;

Receive described tunnel and set up the MIP and the MEP of conditional information and obtain self attribute information, judge that self whether satisfying described tunnel sets up conditional information, if satisfy, then to described source MEP feedback acknowledgment message;

The MIP of the affirmation message correspondence that source MEP recorder is arrived or the relevant information of MEP.

7. method according to claim 6 is characterized in that, MIP that described basis selects and MEP generation pass information comprise:

Source MEP reads the address information of described MIP or MEP from the MIP of record or the relevant information of MEP;

According to the transmission of described address information calculated data the order of MIP of process.

8. method according to claim 5 is characterized in that, comprises after MIP that described basis selects and the MEP generation pass information:

Source MEP sets up the negotiation instruction that the MIP transmission of condition comprises routing information to satisfying the tunnel;

Described MIP is forwarded to purpose MEP according to routing information with described negotiation instruction, and described purpose MEP satisfies the MEP that condition is set up in the tunnel;

Purpose MEP carries out data transfer negotiation according to self configuration attribute and described source MEP.

9. method according to claim 3 is characterized in that, describedly sets up response to source MEP feedback tunnel, and sets up routing information in the request according to described tunnel and transmit the request of setting up of described tunnel and comprise after the MEP that achieves the goal:

The tunnel removal request that comprises routing information that reception sources MEP sends;

According to described the transmitting of described tunnel removal request deletion;

Set up response to source MEP feedback tunnel, and transmit described tunnel removal request until the MEP that achieves the goal according to the routing information in the described tunnel removal request.

10. method according to claim 3 is characterized in that, describedly sets up response to source MEP feedback tunnel, and sets up routing information in the request according to described tunnel and transmit the request of setting up of described tunnel and comprise after the MEP that achieves the goal:

The tunnel update request that comprises routing information and lastest imformation that reception sources MEP sends;

According to the lastest imformation in the described tunnel update request described transmitting upgraded;

Set up response to source MEP feedback tunnel, and transmit described tunnel update request until the MEP that achieves the goal according to the routing information in the described tunnel update request.

11. an Ethernet tunnel processing method is characterized in that, comprising:

Set up transmission control tunnel according to the transfer of data demand information;

Obtain the source MEP and the purpose MEP information in described transmission control tunnel;

When needs carry out transfer of data between described source MEP and purpose MEP, set up data transmission tunnel between described source MEP and the purpose MEP by described transmission control tunnel;

According to the maintenance regulation that presets described transmission control tunnel is safeguarded.

12. method according to claim 11 is characterized in that, the described data transmission tunnel of setting up between described source MEP and the purpose MEP by described transmission control tunnel comprises before:

The source end configuration information that source MEP presets to the purpose MEP broadcasting in described transmission control tunnel by MIP, and receive the destination configuration information that described purpose MEP feeds back;

Judge whether described source end configuration information is corresponding with described destination configuration information, if corresponding, then carry out by described transmission control tunnel and set up data transmission tunnel between described source MEP and the described purpose MEP.

13., it is characterized in that the described data transmission tunnel of setting up between described source MEP and the purpose MEP by transmission control tunnel comprises according to claim 11 or 12 described methods:

Source MEP sends the tunnel that comprises routing information to MIP and sets up request;

The tunnel that MIP asks and presets according to the foundation of described tunnel is set up parameter foundation and is transmitted;

MIP sets up response to source MEP feedback tunnel, and transmits described tunnel according to the routing information in the foundation request of described tunnel and set up request until the MEP that achieves the goal.

14. a communication system is characterized in that, comprising:

Source MEP is used to send the tunnel that comprises routing information and sets up request;

MIP, be used to receive the tunnel foundation request that described source MEP sends, and set up parameter foundation according to the tunnel that the foundation of described tunnel is asked and preset and transmit, set up response to source MEP feedback tunnel, and transmit described tunnel according to the routing information in the foundation request of described tunnel and set up request until the MEP that achieves the goal;

Purpose MEP is used to receive the tunnel foundation request of described MIP forwarding, and responds to described source MEP feedback tunnel foundation by described MIP.

15. a maintaining end point is characterized in that, comprising:

Request unit is handled in the tunnel, is used for sending tunnel foundation request to MIP or opposite end MEP, or the tunnel removal request, or the tunnel update request;

The processing response receiving element is used to receive the tunnel foundation response of MIP or opposite end MEP transmission, or tunnel deletion response, or the tunnel renewal responds.

16. maintaining end point according to claim 15 is characterized in that, described maintaining end point comprises that also the tunnel sets up control unit,

Described tunnel is set up control unit and is comprised:

The configuration information radio unit is used for the configuration information that presets by other MEP broadcasting in the maintenance field of MIP under described maintaining end point;

Network element is chosen the unit, is used for MIP in the maintenance field under the described maintaining end point and other MEP and chooses and satisfy MIP and the MEP that condition is set up in the tunnel;

The path generation unit is used for according to satisfying MIP and the MEP generation pass information that condition is set up in the tunnel;

The information reconciliation unit is used for setting up the MIP and the opposite end MEP of condition and carrying out information reconciliation by satisfying the tunnel.

17., it is characterized in that described maintaining end point also comprises according to claim 15 or 16 described maintaining end points:

The data encapsulation unit is used for according to the tunnel transmission attribute packet being encapsulated transmission after tunnel foundation is finished.

18. safeguard for one kind to it is characterized in that intermediate node, the described intermediate node of safeguarding comprises:

Receiving element is handled in the tunnel, is used to receive the tunnel foundation request that MEP sends, or the tunnel removal request, or the tunnel update request;

Processing response unit, tunnel is used for sending the tunnel to MEP and sets up response, or tunnel deletion response, or the tunnel upgrades response;

The tunnel processing unit is used for setting up request according to the tunnel, or the tunnel removal request, or the tunnel update request is handled transmitting accordingly;

The data forwarding unit is used for setting up request according to the tunnel, or the tunnel removal request, or the routing information in the tunnel update request is transmitted data.

Images