WO2014198217A1

WO2014198217A1 - Tunnel processing method and system, control plane equipment and forwarding plane equipment

Info

Publication number: WO2014198217A1
Application number: PCT/CN2014/079635
Authority: WO
Inventors: 梁乾灯; 尤建洁; 梁亮; 陈勇
Original assignee: 中兴通讯股份有限公司
Priority date: 2013-06-14
Filing date: 2014-06-10
Publication date: 2014-12-18
Also published as: CN104243299B; CN104243299A

Abstract

Disclosed are a tunnel processing method and system, control plane equipment and forwarding plane equipment. The method comprises: configuring a group of general tunnel encapsulation commands and decapsulation commands which correspond to the action of compressing into a specified encapsulation header and the action of popping up a specified encapsulation header respectively; then executing the corresponding actions of compressing into the specified encapsulation header and popping up the specified encapsulation header according to the tunnel encapsulation and decapsulation commands respectively. The forwarding plane equipment is configured to execute the corresponding actions of compressing into the specified encapsulation head and popping up the specified encapsulation head according to the tunnel encapsulation and decapsulation commands respectively. By using the invention with respect to tunnel encapsulation and decapsulation processing, uniform service configuration controls of forwarding behavior models can be carried out in the forwarding plane equipment to accurately control the behavior of said equipment.

Description

TECHNICAL FIELD The present invention relates to a tunnel processing technology in the field of network communication in a software defined network (SDN) architecture, and more particularly to an open flow (OpenFlow) pipeline. Tunnel processing method and system, control plane device, and forwarding surface device. BACKGROUND OF THE INVENTION As today's networks expose more and more ills and the need for network performance is increasing, researchers have to incorporate many complex functions into the router's architecture, such as open shortest path first ( OSPF), Border Gateway Protocol (BGP), Multicast, Differentiated Services, Traffic Engineering, Network Address Translation (NAT), Firewall, Multi-Protocol Label Switching (MPLS), etc. This makes switching devices such as routers more and more bloated and the space for performance improvement is getting smaller and smaller. However, in stark contrast to the dilemma of the network sector, the computer field has evolved with each passing day. A careful review of the development of the computer field, it is not difficult to find that the key is that the computer field has found a simple and usable hardware underlying (x86 instruction set). Thanks to such a common hardware underlying layer, in terms of software, both the application and the operating system have achieved rapid development. Many people who advocate redesigning the computer network architecture now believe that the network can replicate the success of the computer field to solve all the problems encountered by the current network. Under the guidance of this idea, the future network must be like this: The underlying data path (switch, router) is "*, simple, minimal" and defines a publicly available flow table that is open to the public. The application program interface (API), while using the controller to control the entire network. Future researchers can freely call the underlying APIs on the controller to program, thus enabling network innovation. Based on the above concept, the SDN architecture emerged, which was originally a new network innovation architecture proposed by the Stanford University clean slate research group. At present, the core technology is the OpenFlow protocol. The SDN architecture is implemented based on OpenFlow. In the SDN architecture, the data forwarding plane and control plane of the switching device are separated. Therefore, the upgrade of the network protocol and the switching policy only needs to change the control plane. By separating the data forwarding plane and the control plane, flexible control of network traffic is realized, which provides a good platform for innovation of core network and application. The switch that enters the OpenFlow technology is usually called OpenFlow switch. It is different from the traditional switch. The OpenFlow switch converts the packet forwarding process that is completely controlled by the switch/router into the OpenFlow switch and the controller. The separation of data forwarding and routing control. The controller can control the OpenFlow flow table in the OpenFlow switch by using a predetermined interface operation to achieve The purpose of controlling data forwarding is that the SDN architecture based on OpenFlow implements data forwarding on the OpenFlow switch and implements data forwarding control on the controller, thereby realizing the separation of the data forwarding plane and the control layer. The above OpenFlow protocol is a standard for describing information used for interaction between control plane devices (such as OF configuration points and controllers) and forwarding plane devices (such as OpenFlow switches), and interface standards for control plane devices and forwarding plane devices. The core part of the OpenFlow protocol is a collection of information structures for the OpenFlow protocol. The above OpenFlow flow table (also known as a tunnel information flow table) is composed of a plurality of flow entries, and each flow entry is a forwarding rule. The data packet entering the OpenFlow switch is obtained by querying the OpenFlow flow table to obtain the forwarded destination port. An OpenFlow flow table formed by cascading an OpenFlow flow table or multiple OpenFlow flow tables configured to configure a switch forwarding path. Figure 1 is a schematic diagram of a packet flow passing through the OpenFlow pipeline in the prior art. In Table 1, Table 0 and Table 1 to Table On are multiple OpenFlow flow tables, n is a positive integer, and multiple OpenFlow flow tables are cascaded. The pipeline is called the OpenFlow pipeline. Figure 2 shows the packet matching process based on each OpenFlow flow table in the prior art. Taking Table O as an example, the process includes: 1) finding the highest priority matching flow table entry in Table O; 2) applying the instruction set The instruction: modify the message or update the matching domain; update the action set; update the metadata; 3) after the matching is successful, send the matching data and the updated action set to the next flow table Tablel. The following describes the existing OpenFlow flow table as follows:

The OpenFlow flow table consists of the following fields, such as the matching field, counter, and instruction set shown in Table 1:

In Table 1, the match field (Match Fields) is the input keyword of the packet matching, which is used to match a flow entry; the priority is the priority of the matching rule in the flow entry; Counters The instruction is used to manage various messages. The instruction set refers to the operation instructions of the packet, including discarding and forwarding the packet to the specified port, setting the packet header field value, and adding the package label. The Action Set is associated with each message. It is passed between multiple flow tables in the OpenFlow pipeline and modified by the operation instructions of each flow table instruction set until the message ends through the OpenFlow pipeline processing. Action set. The current OpenFlow 1.3.2 specifies the set of actions that consist of 11 actions, namely: Copy TTL inwards: The action of copying the TTL to the inner layer is applied to the packet; pop: the operation of applying the popup label to the packet; push-vlan: the operation of pushing the vlan label to the packet; push-mpls: applying the packet to the packet Copy TTL outwards: copy TTL outwards: Apply TTL to the outer layer; decrement TTL: TTL value of the packet minus 1; set: apply set-field action to the packet; qos: match the packet Apply QoS actions, such as Set-queue; group: If a group action is specified, the actions in the related group container are applied in the order of this list; output: If no group action is specified, the message is forwarded according to the output action. The specified port; push PBB: Apply a PBB tag push action to the message. In order to use the business requirements of the IDC scenario (eg multi-tenancy, virtual machine migration) and compatibility with existing network protocols, the OpenFlow Management and Configuration Protocol released the first version (OF-CO FIG 1.0 & 1.1), OF-Config 1.1.1 The protocol defines the interface of the tunnel attributes such as VxLAN, NV-GRE, and IP-in-GRE (that is, the information about the tunnel type and the tunnel encapsulation is added to the attributes of the interface), and is used to process the tunnels such as VxLAN of the OpenFlow forwarding plane device. . The existing problems in the prior art are: The latest OpenFlow protocol (OpenFlow 1.3.2) does not define a tunnel processing action on the forwarding plane pipe of the above tunnel, that is, the tunnel processing for tunnel sealing and decapsulation is still a standard. The behavior outside the definition is not conducive to the service configuration control of the unified forwarding behavior model of the multi-vendor OpenFlow forwarding plane device, so as to accurately control the behavior of the forwarding plane device. In response to this problem, there is currently no effective solution. SUMMARY OF THE INVENTION In view of the above, the main object of the present invention is to provide a tunnel processing method and system, a control plane device, and a forwarding plane device, which can perform a unified forwarding behavior model for a forwarding plane device for tunnel processing of tunnel sealing and decapsulation. The business configuration controls to precisely control the behavior of the forwarding surface device. To achieve the above objective, the technical solution of the present invention is implemented as follows: A tunnel processing method, the method includes: configuring a set of universal tunnel encapsulation instructions and decapsulation instructions, respectively corresponding to pressing a specified encapsulation header action and popping a specified encapsulation The action of the header; according to the tunnel encapsulation instruction and the decapsulation instruction, respectively perform the corresponding action of injecting the specified encapsulation head and ejecting the specified encapsulation header. The performing the indenting of the specified encapsulation header specifically includes: pressing the encapsulation header of the length and content of the specified encapsulation header into the packet. The performing the action of popping the specified encapsulation header specifically includes: ejecting the outermost encapsulation header of the specified length from the message. The encapsulation head specifically includes a tunnel head, and/or an outer IP head, and/or an ether header. The method further includes: configuring an OpenFlow pipeline that is cascaded by multiple OpenFlow flow tables; any one of the OpenFlow flow tables is configured by multiple flow table entries, where each flow table entry includes at least a matching domain and an instruction set; The matching domain uses the tunnel ID as a matching key value, and the matching key value is filled in the appointment field of the Meta by the upper-level OpenFlow flow table entry; the instruction set includes at least the tunnel encapsulation instruction and the decapsulation instruction. The tunnel ID specifically includes: an interface ID that configures a tunnel attribute. A tunnel processing system, the system comprising: a control plane device, configured to configure a set of universal tunnel encapsulation instructions and decapsulation instructions, respectively corresponding to pressing a specified encapsulation head action and popping a specified encapsulation header; forwarding surface device, setting According to the tunnel encapsulation instruction and the decapsulation instruction, the corresponding action of injecting the specified encapsulation header and ejecting the specified encapsulation header are respectively performed. The forwarding plane device is configured to press the encapsulation header of the length and content of the specified encapsulation header into the packet when the operation of the specified encapsulation header is performed. The forwarding plane device is configured to: when performing the action of popping the specified encapsulation header, eject the outermost encapsulation header of the specified length from the packet. The control plane device is configured to configure the encapsulation head to specifically include a tunnel head, and/or an outer IP header, and/or an Ethernet header. The control plane device is configured to configure multiple OpenFlow flow tables, and any one of the OpenFlow flow tables is composed of multiple flow table entries, where each flow table entry includes at least a matching domain and an instruction set; wherein the matching domain is The tunnel ID is a matching key value, and the matching key value is filled into the Meta by the upper-level OpenFlow flow table entry. The instruction set includes: the tunnel encapsulation instruction and the decapsulation instruction; the forwarding plane device includes an OpenFlow pipeline that is cascaded by the multiple OpenFlow flow tables, and the packet that enters the forwarding plane device is based on The cascading OpenFlow flow tables on the OpenFlow pipeline are sequentially matched and executed. The tunnel ID specifically includes: an interface ID that configures a tunnel attribute. The control plane device includes: an OF configuration point, configured to: after configuring tunnel attribute information for a corresponding interface of a forwarding plane device, notify the controller of the configured tunnel attribute information; and the controller is configured to parse the tunnel attribute A flow table entry having an action of pushing a specified encapsulation header and/or popping a specified encapsulation header, and/or pre-configuring a tunnel encapsulation header is added to the OpenFlow flow table. The controller is configured to pre-select a cascading process of the multiple OpenFlow flow tables of the OpenFlow pipeline on the forwarding plane device, and notify the forwarding plane device; the forwarding plane device is set to In the case of a tunneling process that requires encapsulation or decapsulation, when the packet entering the forwarding plane device is sequentially matched and executed according to the cascading OpenFlow flow table on the OpenFlow pipeline, an OpenFlow flow table in the cascading process is performed. After the matching succeeds, the Meta with the tunnel ID is forwarded to the subsequent OpenFlow flow table that is cascaded with the OpenFlow flow table to continue matching. After the matching is successful, the specified encapsulation action and the pop-up specified encapsulation are performed according to the push-in in the flow table entry. The action of the header performs the encapsulation and decapsulation processing of the message tunnel header respectively. The forwarding plane device is configured to complete the encapsulation and decapsulation processing of the packet tunnel header when the packet entering the forwarding plane device is processed by the OpenFlow pipeline or the flow table instruction is the action action set Apply Actions. A control plane device, a control plane device, configured to configure a set of universal tunnel encapsulation instructions and decapsulation instructions, respectively corresponding to the action of pressing a specified encapsulation head action and popping a specified encapsulation header. A forwarding plane device, configured to perform a corresponding action of injecting a specified encapsulation header and ejecting a specified encapsulation header according to a tunnel encapsulation instruction and a decapsulation instruction, respectively. The present invention configures a set of general-purpose tunnel encapsulation instructions and decapsulation instructions, respectively corresponding to the action of pressing the specified encapsulation header action and popping the specified encapsulation header; respectively, according to the tunnel encapsulation instruction and the decapsulation instruction, respectively performing the corresponding push-in designation of the encapsulation header action and The action of specifying the package header is popped up. Since the present invention configures a set of general-purpose tunnel encapsulation instructions and decapsulation instructions, the service configuration control of the unified forwarding behavior model can be performed on the forwarding plane device to accurately control the behavior of the forwarding plane device, and correspondingly, the corresponding voltages are respectively executed. Into the specified package header action and pop the specified package header action, thus the existing OpenFlow protocol The extension is implemented to handle the tunnel processing actions on the forwarding plane of the tunnel, that is, the tunnel processing operations for tunnel encapsulation and decapsulation. BRIEF DESCRIPTION OF THE DRAWINGS FIG. 1 is a schematic diagram of a packet flow passing through an OpenFlow pipeline in the prior art; FIG. 2 is a schematic diagram of packet matching processing based on each OpenFlow flow table in the prior art; . DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS The implementation of the technical solution will be further described in detail below with reference to the accompanying drawings. In the existing standard actions, Push-vlan and Push-MPLS Push-PBB, their common semantics is to push a special encapsulated data header, but the encapsulation header is not general, or the generality is not strong, for tunnel encapsulation. For the encapsulation tunneling process, for each different packet type, a new push/pop action is required for each type of encapsulation, so the present invention abstracts a more generalized It is more versatile and suitable for tunneling and decapsulating tunnel processing actions. To avoid adding a new type of package, a new set of Push/Pop actions is required. Specifically, the present invention solves the above general encapsulation problem by extending a set of Push/Pop actions by extending the existing OpenFlow protocol, so as to be able to handle tunnel encapsulation and decapsulation tunneling operations of various message types, and the method of the present invention. Easy to expand and maintain. For the difference between the OpenFlow pipeline and the tunnel, the OpenFlow pipeline refers to: the OpenFlow pipeline includes an OpenFlow pipeline formed by cascading multiple OpenFlow flow tables, and the OpenFlow pipeline is used to configure the packet forwarding path of the forwarding plane device. The flow table is used to describe the tunnel attribute information. The tunnel is a service attribute. The tunnel attribute information can be used to execute the corresponding service. The tunnel processing method of the present invention includes the following contents: As shown in FIG. 3, the method includes the following steps: Step 101: Configure a set of universal tunnel encapsulation and decapsulation instructions, respectively corresponding to pressing a specified encapsulation header action and popping a specified encapsulation header. Actions. Here, the configured set of general-purpose tunnel encapsulation and decapsulation instructions may be saved in an instruction set of the OpenFlow flow table, so that the subsequent step 102 performs corresponding operations according to corresponding instructions in the instruction set, that is, according to the tunnel The instruction of the channel package corresponds to the action of pushing the specified package header, and the instruction of the tunnel decapsulation corresponds to the action of popping up the specified package header. The configuration can be implemented in the OF configuration point in the control plane device, and is added to the OpenFlow flow table by the controller in the control plane device. The controller sends the OpenFlow flow table to the forwarding plane device, such as an OpenFlow switch, and is configured on the OpenFlow switch. The instructions in the OpenFlow flow table perform the corresponding actions. Step 102: Perform, according to the tunnel encapsulation and the decapsulation instruction, respectively, a corresponding action of pressing the specified encapsulation head and popping the specified encapsulation header. In the solution consisting of the above step 101 102, wherein the indenting specifies a encapsulation header, indicating that a package header that is preset (specifying the length and content of the encapsulation header) is pressed into the message. The specified encapsulation header is displayed, indicating that the outermost encapsulation header of the specified length is ejected from the message. The encapsulation header includes a tunnel head and/or an outer IP header and/or an Ethernet header of a specific tunneling protocol. The controller in the control plane device performs service configuration on multiple OpenFlow flow tables according to whether the encapsulation header is encapsulated. The outer IP header or Ethernet header, configure other related actions to properly process the message. The forwarding plane device includes an OpenFlow pipeline formed by cascading a plurality of OpenFlow flow tables, and the OpenFlow pipeline is configured to configure a packet forwarding path of the forwarding plane device, and any OpenFlow flow table uses the tunnel ID as a matching key value, and the tunnel key The value is populated by the upper-level OpenFlow flow table entry onto the contract field of the metadata (Meta). Meta is set to pass specified information directly between OpenFlow flow tables. The tunnel ID can be an interface ID configured with the tunnel attribute. After the OF configuration point is configured with the tunnel attribute of the corresponding interface of the forwarding plane device, the configured tunnel attribute is notified to the controller, such as an OpenFlow controller, where the controller adds a specified encapsulation header and/or pops the specified encapsulation header. The action, and/or the flow table entry of the preset tunnel encapsulation header content to the OpenFlow flow table. Wherein, when a specific flow (a specific flow is a flow that needs to be encapsulated or decapsulated) needs to be encapsulated or decapsulated, the controller pre-configures the flow table process on the OpenFlow pipeline so that it can be in the process. After an OpenFlow flow table is successfully matched, the Meta with the tunnel ID is forwarded to the subsequent OpenFlow flow table that is cascaded with the OpenFlow flow table to continue matching. After the matching is successful, the tunnel encapsulation is performed according to the action in the flow table entry. Decapsulation processing. If the packet is processed by the OpenFlow pipeline or the flow table command is "Apply Actions", the encapsulation or decapsulation processing of the packet tunnel header is completed, that is, the packet has been added with a complete tunnel header or the tunnel header has been stripped. The tunnel processing system of the present invention includes the following: The control plane device is configured to configure a set of universal tunnel encapsulation instructions and decapsulation instructions, respectively corresponding to the action of pressing the specified encapsulation header action and popping the specified encapsulation header; the forwarding plane device is set to be according to the tunnel encapsulation instruction and the decapsulation instruction, respectively Perform the corresponding push-in to specify the package header action and pop the specified package header. The forwarding plane device is configured to press the encapsulation header of the length and content of the specified encapsulation header into the packet when performing the operation of injecting the specified encapsulation header. The forwarding plane device is configured to: when performing the action of popping the specified encapsulation header, eject the outermost encapsulation header of the specified length from the packet. The control plane device is configured to configure the encapsulation head to specifically include a tunnel head, and/or an outer IP header, and/or an Ethernet header. The control plane device is configured to configure multiple OpenFlow flow tables, and any one of the OpenFlow flow tables is composed of multiple flow table entries, where each flow table entry includes at least a matching domain and an instruction set; wherein the matching domain is matched by the tunnel ID. The key value and the matching key value are filled in the contracting field of the Meta by the upper-level OpenFlow flow table entry; the instruction set includes at least the tunnel encapsulation instruction and the decapsulation instruction; wherein the forwarding plane device comprises a plurality of OpenFlow flow table cascading The OpenFlow pipeline, the packets entering the forwarding plane device are sequentially matched and executed according to the cascading OpenFlow flow table on the OpenFlow pipeline. The tunnel ID specifically includes: an interface ID for configuring a tunnel attribute. The control plane device includes: an OF configuration point, configured to notify the controller of the configured tunnel attribute information after the tunnel attribute information is configured for the corresponding interface of the forwarding plane device; and the controller is configured to analyze the tunnel attribute information and add the The flow table entry that pushes the specified encapsulation header and/or pops up the specified encapsulation header, and/or presets the contents of the tunnel encapsulation header into the OpenFlow flow table. It should be noted here that the OF configuration point and the controller are preferably integrated in one device entity or separately, and there is an interactive interface between the OF configuration point and the controller. The controller is configured to pre-select the cascading process of the multiple OpenFlow flow tables of the OpenFlow pipeline on the forwarding plane device and notify the forwarding plane device; the forwarding plane device is set to be processed in a tunnel that needs to be encapsulated or decapsulated. After the packets entering the forwarding plane are matched and executed according to the continuation of the OpenFlow flow table on the OpenFlow pipeline, after the OpenFlow flow table in the cascading process is successfully matched, the Meta with the tunnel ID is forwarded to OpenFlow flow table The continuation of the subsequent OpenFlow flow table continues to match. After the matching succeeds, the encapsulation header action and the pop-up specified encapsulation header are performed according to the push-in in the flow table entry, and the encapsulation and decapsulation processing of the packet tunnel header is performed respectively. The forwarding plane device is configured to perform packet encapsulation and decapsulation processing of the packet tunnel header when the packet entering the forwarding plane device is processed by the OpenFlow pipeline or the flow table instruction is the execution action set Apply Actions. The control plane device of the present invention mainly includes the following contents: The control plane device is configured to configure a set of universal tunnel encapsulation instructions and decapsulation instructions, respectively corresponding to the action of pressing the specified encapsulation header action and popping the specified encapsulation header. The forwarding plane device of the present invention mainly includes the following content: The forwarding plane device is configured to perform a corresponding action of injecting a specified encapsulation header and ejecting a specified encapsulation header according to the tunnel encapsulation instruction and the decapsulation instruction. Application Example 1: This example is an example of an OpenFlow flow table entry, which is an entry of the OpenFlow flow table of the present invention as shown in Table 2 below.

Table 2

(1) The Match Fields entry of the OpenFlow flow table includes a tunnel identifier (ID) corresponding to the tunnel ID field in the matching Meta data;

(2) The instruction set (Instructions) of the OpenFlow flow table contains the 'write action' instruction. The action to be written has actions such as pushing the push tunnel header or popping the Pop tunnel header. Among them, tunnel refers to the tunnel.

(3) Pushing the specified package header, indicating that a package header with a preset (specifying the length and content of the package header) is pressed into the message, as shown in the note in Table 3.

(4) The specified encapsulation header pops up to eject the outermost encapsulation header of the specified length from the message, as shown in the annotation in Table 3.

(5) The action of pushing the specified encapsulation header or popping the specified encapsulation header can be performed when the flow table instruction ends with the Apply Actions or OpenFlow pipeline. Table 3 is a detailed explanation of the two actions of pushing the specified encapsulation head and popping the specified encapsulation header according to the present invention. The newly defined action for the preset nature tunnel processing is as shown in Table 3:

In the implementation of Table 3, in the control plane device configuration, if the control plane device consists of the integrated OF configuration point and the controller, the OF configuration point is configured with the tunnel attribute information and then processed by the controller, and the controller sends the flow table. The packet is forwarded to the forwarding plane device to perform the action of the flow table cascaded according to the pre-selected configuration. The main function is to perform the encapsulation of the specified encapsulation header and the specified encapsulation header, that is, the encapsulation corresponding to the packet tunnel header. Reconciliation encapsulation processing. For OpenFlow, all rules that comply with the OpenFlow protocol are organized in different OpenFlow flow tables, and are matched in the same OpenFlow flow table according to the priority of the rules. A forwarding plane device may include one or more OpenFlow flow tables, multiple OpenFlow flow tables, and multiple OpenFlow flow tables, which are numbered sequentially from 0. The tunnel processing of the packets entering the forwarding plane device on the OpenFlow pipeline is The pipelined cascading process, specifically, after the packets enter the forwarding plane device, they must be matched in order from the OpenFlow flow table 0. The OpenFlow flow table can be jumped from small to large in order, but cannot be flowed from an OpenFlow. The table forwards to the OpenFlow flow table with a smaller number. When the packet successfully matches a flow table entry rule, the statistics corresponding to the rule are first updated (such as the total number of successfully matched packets and the total number of bytes). Then, according to the instruction of the instruction set in the flow table entry rule, the corresponding operation is performed, for example, jumping to a subsequent OpenFlow flow table to continue processing, modifying or immediately executing the action set (Action Set) corresponding to the data packet. When the packet is already in the last OpenFlow flow table on the OpenFlow pipeline, all actions in its corresponding Action Set will be executed, including forwarding to a port, modifying a field of the packet, dropping the packet, encapsulating or decapsulating. Wait. Application Example 2: This example provides an action when a tunnel is a GRE according to an embodiment of the present invention. For details, refer to Table 4. When the specific tunnel attribute type is GRE, the above actions can be understood as follows:

Action Associated Data Description

Push GRE Ethertype Push a new GRE header header Ether type onto the packet. The Package GRE header Ethertype is used as the

Ethertpye for the resulting packet (Ethertype for the

IP payload). Only

Ethertype 0x0800 should

Be used.

Pop tunnel

Pop the outer-most GRE header

Header from the packet.

Decapsulating the GRE header Table 4 When the specific tunnel attribute is GRE, the corresponding action can be understood as follows:

(1) The GRE header is encapsulated to push the GRE header into the message.

(2) The PEP tunnel header indicates that the outermost GRE header is popped from the packet. The configuration of the GRE interface is used as an example to describe the process of configuring and controlling the forwarding of packets on the forwarding plane. The user or the upper-layer service plane (APP) can dynamically specify the interface of a topology node in the SDN network (physical interface or The created logical interface is configured. If the APP can master the routing information and the corresponding Address Resolution Protocol (ARP) information, the ARP includes its association with the APP with routing/ARP function, or the static configuration, the APP can use the GRE tunnel. The tunnel header encapsulation information, the outer IP header and the Ethernet header are sent to the control plane device, and are decomposed to the OF configuration point and the OpenFlow controller for processing, respectively creating/configuring the attributes of the interface and delivering the flow for the tunnel encapsulation. The table (executing the tunnel encapsulation action, which can be encapsulated to the Ethernet header all the time) to the forwarding plane device. If the APP cannot grasp the routing and ARP information, in the implementation, the control plane device (mainly the controller) is required to provide the routing function and the query function of the ARP module (which is planned in the software architecture of some vendors' controllers). The control plane device performs the conversion. For example, after the APP configures the GRE tunnel attribute of the interface through the OF configuration point, the corresponding controller is notified, and the controller queries the routing/ARP information locally or to the APP with the routing/ARP function, and then generates a flow table. The information is forwarded to the associated forwarding plane device, and is associated with the flow table and the corresponding route. When the route update causes the actual outbound interface to change, the flow table is updated, and the encapsulation information is modified (mainly, the outer layer of the encapsulation information is updated. ) and the action of the outgoing interface. Of course, when the OpenFlow pipeline is configured in the traditional router device forwarding manner and the OpenFlow pipeline is cascaded, the implementation may be simpler. The encapsulation information of the flow table entries in the OpenFlow flow table may include only the tunnel header and/or the IP header (depending on the tunnel type) For example, the GRE tunnel type should include the IP header. After Apply Actions performs the encapsulation action, it will continue to jump to the routing table with routing function or the next-level cascading pipeline to continue processing the outer IP. The routing and modification of the Ethernet action, since these actions are not standardized, and the extended implementation options are relatively large, the present invention only preferentially focuses on the encapsulation and decapsulation actions of the tunnel information. Application Example 3: This example provides packet encapsulation when the tunnel is GRE according to the embodiment of the present invention. For details, refer to Table 5. Table 5 is a basic format of a packet encapsulation header when the tunnel is GRE. When the tunnel is GRE, the format of the encapsulated packet in the GRE tunnel is:

Table 6 above is only a preferred embodiment of the present invention and is not intended to limit the scope of the present invention. Industrial Applicability As described above, with the above embodiments and preferred embodiments, for the tunnel processing of tunnel sealing and decapsulation, the service configuration control of the forwarding forwarding model can be performed on the forwarding plane device to accurately control the behavior of the forwarding plane device.

Claims

Claim

A tunnel processing method, comprising:

Configuring a set of universal tunnel encapsulation instructions and decapsulation instructions, respectively corresponding to pressing the specified encapsulation header action and popping the specified encapsulation header;

According to the tunnel encapsulation instruction and the decapsulation instruction, the corresponding action of injecting the specified encapsulation head and ejecting the specified encapsulation header are respectively performed.

The method according to claim 1, wherein performing the indenting of the specified encapsulation header comprises: pressing a encapsulation header that specifies a length and a content of the encapsulation header into the message.

The method of claim 1, wherein the performing the action of popping the specified encapsulation header comprises: ejecting the outermost encapsulation header of the specified length from the message.

The method according to claim 2 or 3, wherein the encapsulation head comprises specifically a tunnel head, and/or an outer layer IP header, and/or an Ethernet head.

5. The method according to claim 1, wherein the method further comprises: configuring an OpenFlow pipeline that is cascaded by a plurality of OpenFlow OpenFlow flow tables;

Any one of the OpenFlow flow tables is composed of a plurality of flow table entries, and each of the flow table entries includes at least a matching domain and an instruction set; wherein the matching domain uses the tunnel ID as a matching key value, and the matching key value is from the upper-level OpenFlow. The flow table entry is populated onto the appointment field of the Meta; the set of instructions includes at least the tunnel encapsulation instruction and the decapsulation instruction.

The method according to claim 5, wherein the tunnel ID specifically includes: an interface ID that configures a tunnel attribute.

7. A tunnel processing system, comprising:

The control plane device is configured to configure a set of universal tunnel encapsulation instructions and decapsulation instructions, respectively corresponding to the action of pressing the specified encapsulation head action and popping the specified encapsulation header;

The forwarding plane device is configured to perform a corresponding action of injecting the specified encapsulation header and ejecting the specified encapsulation header according to the tunnel encapsulation instruction and the decapsulation instruction.

The system according to claim 7, wherein the forwarding plane device is configured to press a packet header of a length and a content of the specified encapsulation header into the packet when the operation of the specified encapsulation header is performed.

The system according to claim 7, wherein the forwarding plane device is configured to: when performing the action of the pop-up specifying the encapsulation header, eject the outermost encapsulation header of the specified length from the message.

10. The system according to claim 8 or 9, wherein the control plane device is arranged to configure the package head to specifically comprise a tunnel head, and/or an outer IP header, and/or an Ethernet head.

11. The system according to claim 7, wherein the control plane device is configured to configure a plurality of OpenFlow flow tables, and any one of the OpenFlow flow tables is composed of a plurality of flow table entries, each of the flow table entries including at least a matching domain The instruction set; wherein the matching domain uses the tunnel ID as a matching key value, and the matching key value is filled in the appointment field of the Meta by the upper-level OpenFlow flow table entry; the instruction set includes at least the tunnel encapsulation instruction Reconciliation package instruction;

The forwarding plane device includes an OpenFlow channel that is cascaded by the multiple OpenFlow flow tables, and the packets that enter the forwarding plane device are matched and executed according to the cascading OpenFlow flow table on the OpenFlow pipeline.

The system of claim 11, wherein the tunnel ID specifically includes: an interface ID that configures a tunnel attribute.

The system according to claim 11, wherein the control plane device comprises:

The OF configuration point is configured to notify the controller of the configured tunnel attribute information after the tunnel attribute information is configured for the corresponding interface of the forwarding plane device.

The controller, configured to parse the tunnel attribute information, add a flow table entry having an action of pushing the specified encapsulation header and/or popping the specified encapsulation header, and/or pre-configuring the encapsulation header content into the OpenFlow flow table.

The system according to claim 11, wherein the controller is configured to pre-select a cascading process of the plurality of OpenFlow flow tables of the OpenFlow pipeline on the forwarding plane device and notify the forwarding plane Equipment

The forwarding plane device is configured to perform, in the case of a tunnel processing that needs to be encapsulated or decapsulated, when the packet entering the forwarding plane device is sequentially matched and executed according to the cascading OpenFlow flow table on the OpenFlow pipeline, After an OpenFlow flow table in the cascading process is successfully matched, the Meta with the tunnel ID is forwarded to the subsequent OpenFlow flow table that is cascaded with the OpenFlow flow table to continue matching. After the matching succeeds, according to the pressure in the flow table entry. The operation of specifying the encapsulation header and popping up the specified encapsulation header respectively perform encapsulation and decapsulation processing of the packet tunnel header.

The system according to claim 14, wherein the forwarding plane device is configured to complete the message when the packet entering the forwarding plane device is processed by the OpenFlow pipeline or the flow table instruction is the action action set Apply Actions. The encapsulation and decapsulation processing of the packet tunnel header.

16. A control plane device, the control plane device configured to configure a set of universal tunnel encapsulation instructions and decapsulation instructions, respectively corresponding to an action of injecting a specified encapsulation head action and popping a specified encapsulation header.

A forwarding plane device, configured to perform a corresponding action of injecting a specified encapsulation header and ejecting a specified encapsulation header according to a tunnel encapsulation instruction and a decapsulation instruction.