CN103747502A - Method and system for processing GTP tunnel - Google Patents

Abstract

The invention discloses a GTP tunnel processing method and system, relates to the technical field of communication networks, and is used to solve the problem of poor scalability of GTP tunnel endpoints. In the embodiment of the present invention, an Openflow controller is used to obtain a request to establish a GTP tunnel. The Openflow controller is a device with a control plane function in a GTP tunnel endpoint; the Openflow controller requests to establish a GTP tunnel by establishing a GTP tunnel, wherein the establishment of a GTP tunnel request includes generating a GTP tunnel. For the relevant parameters of the tunnel, the target-extended Openflow switch is a device with a data plane function in the GTP tunnel endpoint; the Openflow controller sends the relevant parameters of the GTP tunnel to the target-extended Openflow switch. The solutions provided by the embodiments of the present invention are suitable for use in data transmission.

Description

A processing method and system for a GTP tunnel

technical field

The invention relates to the technical field of communication networks, in particular to a GTP tunnel processing method and system.

Background technique

General Packet Radio Service Tunneling Protocol (General Packet Radio Service Tunneling Protocol, GTP) is a mobile core network (including General Packet Radio Service (General Packet Radio Service, GPRS) / Universal Mobile Telecommunications System (Universal Mobile Telecommunications System, UMTS) / evolution An important protocol of the data core network (Evolved Packet Core, EPC)), which is used in multiple interfaces of the mobile core network. GTP is mainly used in tunnel management, mobility management and data transmission. GTP is at the application layer of the protocol stack, which includes three variants, namely the General Packet Radio Service Technology Tunneling Protocol Control Plane (GTP Control, GTP-C), and the General Packet Radio Service Technology Tunneling Protocol Data Plane (GTP User, GTP-U ) and GTP' (GTP Prime). Among them, GTP-C is the control part of GTP, responsible for the establishment, deletion and update of GTP-U tunnels, and verifying the reachability of the mobile core network gateway. GTP-U is responsible for data bearer, and completes overlay transmission of service data between a pair of tunnel endpoints by encapsulating and decapsulating service data. GTP' is used to transmit charging data between the mobile core network and the charging gateway.

The GTP tunnel needs to complete the encapsulation and decapsulation of service data at the start and end of the tunnel. Tunnel endpoints can be thought of as application layer gateways. The existing GTP protocol often makes GTP-C and GTP-U go through the same node, that is, the GTP tunnel endpoint in the prior art includes the functions of the GTP tunnel control plane and the GTP tunnel data plane. Taking the establishment of a GTP tunnel in a 2G/3G network as an example, there are two sections for the establishment of a GTP tunnel. Tunnel; one segment is a GTP tunnel between SGSN and GPRS Support Node (Gateway GPRS Support Node, GGSN). The user equipment (UserEquipment, UE) sends a packet data protocol context (Packet Data Protocol context, PDP context) activation request to the RNC, and the RNC generates a GTP tunnel establishment request carrying the IP address of the SGSN according to the PDP context activation request, and will establish the GTP tunnel The GTP tunnel request is sent to the SGSN. After receiving the GTP tunnel request, the SGSN generates and sends to the GGSN a request for establishing a GTP tunnel carrying the IP address of the GGSN on the one hand, and feeds back the first GTP tunnel establishment response to the RNC on the other hand. The parameters of the GTP tunnel between RNC and SGSN (such as GTP tunnel version number, GTP tunnel identifier, etc.) are carried in the response of establishing a GTP tunnel; The request to feed back the second GTP tunnel establishment response to the SGSN, where the second GTP tunnel establishment response carries the parameters of the GTP tunnel between the GGSN and the SGSN (such as the GTP tunnel version number, the GTP tunnel identifier, etc.). When the parameters of the GTP tunnel between the RNC and the SGSN have been negotiated between the RNC and the SGSN, and the parameters of the GTP tunnel between the SGSN and the GGSN have been negotiated between the SGSN and the GGSN, it indicates that the RNC and the SGSN have jointly established the relationship between the RNC and the SGSN. The GTP tunnel between the SGSN and the GGSN jointly establishes the GTP tunnel between the SGSN and the GGSN.

However, the GTP tunnel established in the prior art is established through negotiation between the two endpoints of the GTP tunnel. When the existing technology is used to establish a GTP tunnel, the two endpoints of the GTP tunnel need to interact with related signaling to complete the establishment; when the existing technology is used to modify or delete the GTP tunnel, the two endpoints of the GTP tunnel need to interact and communicate The modification or deletion of the GTP tunnel is completed through joint negotiation of signaling, thus increasing the complexity of processing the GTP tunnel.

Contents of the invention

Embodiments of the present invention provide a GTP tunnel processing method and system for solving the problem of reducing the complexity of GTP tunnel processing.

On the one hand, an embodiment of the present invention provides a method for processing a GTP tunnel, including:

The Openflow controller acquires a request for establishing a General Packet Radio Service Technology Tunneling Protocol GTP tunnel, and the Openflow controller is a device with a control plane function in the GTP tunnel endpoint;

The Openflow controller establishes a GTP tunnel through the establishment of the GTP tunnel request, wherein the establishment of the GTP tunnel request includes generating relevant parameters of the GTP tunnel, and the relevant parameters of the GTP tunnel include a first GTP routing flow table entry and a next hop Encapsulating parameter record entries, the first GTP routing flow table entry is a flow table entry used when the target extended Openflow switch transmits data, and the first GTP routing flow table entry includes at least the general packet radio service technology tunneling protocol data plane version No. GTP-U Version, General Packet Radio Services Technology Tunneling Protocol data plane tunnel endpoint identifier GTP-UTEID, the next hop encapsulation parameter record entry is the flow table entry used when the target extended Openflow switch encapsulates data, and the The Openflow switch of the target extension is a device having the data plane function in the GTP tunnel endpoint as the GTP tunnel;

The Openflow controller sends the relevant parameters of the GTP tunnel to the target extended Openflow switch, so that the target extended Openflow switch records according to the first GTP routing flow table entry and the next hop encapsulation parameter Entry transfer data.

In another embodiment of the present invention, the Openflow controller requests to establish a GTP tunnel through the establishment of a GTP tunnel, including:

The Openflow controller selects an Openflow switch for the target extension of the GTP tunnel;

The Openflow controller acquires available network link parameters, and the available network link parameters include at least the IP address and port number corresponding to the Openflow switch of the target extension;

The Openflow controller determines parameters for establishing the GTP tunnel through the available network link parameters, and the parameters for establishing the GTP tunnel include IP addresses at both ends, port numbers at both ends, GTP- U Version, GTP-U TEID;

The Openflow controller generates a first GTP routing flow table entry and a next-hop encapsulation parameter record entry based on the available network link parameters and the parameters for establishing the GTP tunnel.

In another embodiment of the present invention, the relevant parameters of the GTP tunnel also include a second GTP routing flow table entry, and the second GTP routing flow table entry is a flow table entry used by a standard Openflow switch to transmit data, so The standard Openflow switches are all standard Openflow switches managed by the Openflow controller;

After the Openflow controller obtains the available network link parameters of the Openflow switch of the target extension, it also includes:

The Openflow controller generates the second GTP routing flow table entry through the parameter of establishing the GTP tunnel;

The Openflow controller sends the second GTP routing flow table entry to a standard Openflow switch, so that the standard Openflow switch transmits data according to the second GTP routing flow table entry.

In another embodiment of the present invention, after the Openflow controller requests to establish a GTP tunnel through the establishment of a GTP tunnel, the method further includes:

The Openflow controller acquires decision result information, and the decision result information is used to indicate specific processing for data corresponding to a specific service, and the specific processing is in any of the following forms: transcoding the data corresponding to the specific service . Performing traffic isolation for the data corresponding to the specific service, sending a warning reminder message to the user equipment UE, or performing advertisement video insertion for the data corresponding to the specific service;

The Openflow controller generates a specific GTP routing flow table entry for the data corresponding to the specific service according to the decision result information;

The Openflow controller selects a target standard Openflow switch for the GTP tunnel;

The Openflow controller sends the specific GTP routing flow table entry to the target standard Openflow switch.

In another embodiment of the present invention, the method also includes:

The Openflow controller receives the policy information sent by the policy and charging rule functional unit PCRF;

The Openflow controller generates a first policy GTP routing flow table entry, a next hop encapsulation parameter policy record entry, and a second policy GTP routing flow table entry based on the available network link parameters and the policy information.

In another embodiment of the present invention, the method also includes:

The Openflow controller acquires a request to modify the GTP tunnel; request to modify the GTP tunnel through the modified GTP tunnel request, wherein the request to modify the GTP tunnel includes generating relevant parameters for updating the GTP tunnel, and the relevant parameters for updating the GTP tunnel include a first updated GTP route A flow table entry, a next hop encapsulation parameter update record entry, and a second updated GTP routing flow table entry, the first updated GTP routing flow table entry is a flow table entry used when the target extended Openflow switch transmits data, so The next hop encapsulation parameter update record entry is a flow table entry used when the target extended Openflow switch encapsulates data, and the second updated GTP routing flow table entry is a flow table entry used when the standard Openflow switch transmits data ; Correspondingly sending the related parameters of the updated GTP tunnel to the target extended Openflow switch and the standard Openflow switch; or,

The Openflow controller acquires a delete GTP tunnel request, wherein the delete GTP tunnel request includes an identifier indicating to delete the GTP tunnel; deletes the corresponding GTP tunnel through the delete GTP tunnel identifier; notifies the target extended Openflow switch And/or the target standard Openflow switch, so that the target extended Openflow switch and the target standard Openflow switch correspondingly delete parameters corresponding to the GTP tunnel corresponding to the delete GTP tunnel request.

On the other hand, an embodiment of the present invention provides a system for processing a GTP tunnel, the system includes an Openflow controller and an Openflow switch for target extension, wherein the Openflow controller is a control plane function equipped with a GTP tunnel endpoint The device, the Openflow switch of the target extension is as the device having the data plane function in the GTP tunnel endpoint in the GTP tunnel, including:

The Openflow controller is configured to obtain a request for establishing a General Packet Radio Service Technology Tunneling Protocol (GTP) tunnel; request to establish a GTP tunnel through the establishment of a GTP tunnel request, wherein the establishment of a GTP tunnel request includes generating relevant parameters of the GTP tunnel, and the GTP The relevant parameters of the tunnel include the first GTP routing flow table entry and the next hop encapsulation parameter record entry, the first GTP routing flow table entry is the flow table entry used when the Openflow switch of the target extension transmits data, and the first GTP The routing flow table entry includes at least the GPRS Tunneling Protocol data plane version number GTP-U Version, the GPRS Tunneling Protocol data plane tunnel endpoint identifier GTP-U TEID, and the next hop encapsulation parameter record entry is all The flow table entry used when the Openflow switch of the target extension is encapsulated; the relevant parameters of the GTP tunnel are sent to the Openflow switch of the target extension;

The Openflow switch of the target extension is used to receive the first GTP routing flow table entry and/or the next-hop encapsulation parameter record entry sent by the Openflow controller; and according to the first GTP routing flow table The entry and the encapsulation parameter of the next hop record entry transfer data.

In another embodiment of the present invention, the Openflow controller is further configured to select an Openflow switch for the target extension of the GTP tunnel; obtain available network link parameters, and the available network link parameters are at least Include the IP address and port number corresponding to the Openflow switch of the target extension; determine the parameters for establishing the GTP tunnel through the available network link parameters, and the parameters for establishing the GTP tunnel include the source corresponding to the GTP tunnel IP address, destination IP address, source port number, destination port number, GTP-U Version, GTP-U TEID; Generate the first GTP routing flow table by the parameters of the available network link and the parameters of establishing the GTP tunnel entry and next hop encapsulation parameter record entry.

In another embodiment of the present invention, the relevant parameters of the GTP tunnel also include a second GTP routing flow table entry, and the second GTP routing flow table entry is a flow table entry used by a standard Openflow switch to transmit data, so The standard Openflow switches are all standard Openflow switches managed by the Openflow controller;

The Openflow controller is also configured to generate the second GTP routing flow table entry through the parameter of establishing the GTP tunnel; send the second GTP routing flow table entry to the standard Openflow switch;

The system also includes: a target standard Openflow switch, wherein the target standard Openflow switch is the standard Openflow switch participating in the transmission of data in the GTP tunnel;

The Openflow controller is also used to obtain decision result information, the decision result information is used to indicate specific processing of data corresponding to a specific business, and the specific processing is in any of the following forms: Perform data transcoding, perform traffic isolation for the data corresponding to the specific service, send a warning reminder message to the user equipment UE, or perform advertisement video insertion for the data corresponding to the specific service; The corresponding data generates a specific GTP routing flow table entry; and selects a target standard Openflow switch for the GTP tunnel; sends the specific GTP routing flow table entry to the target standard Openflow switch;

The target standard Openflow switch is configured to receive the specific GTP routing flow table entry sent by the OPenflow controller.

In another embodiment of the present invention, the Openflow controller is further configured to receive the policy information sent by the policy and charging rule functional unit PCRF; generate the first A policy GTP routing flow table entry, a next hop encapsulation parameter policy record entry, and a second policy GTP routing flow table entry, and sending the first policy GTP routing flow table entry and the next hop encapsulation parameter policy record entry to The Openflow switch of the target extension sends the second policy GTP routing flow table entry to the standard Openflow switch;

The Openflow switch of the target extension is also used to receive the first policy GTP routing flow table entry and the next-hop encapsulation parameter policy record entry sent by the Openflow controller;

The target standard Openflow switch is also used to receive the second strategy GTP routing flow table entry sent by the Openflow controller;

The Openflow controller is also used to obtain a request to modify the GTP tunnel; modify the GTP tunnel through the request to modify the GTP tunnel, wherein the request to modify the GTP tunnel includes generating relevant parameters for updating the GTP tunnel, and the relevant parameters for updating the GTP tunnel include the first An updated GTP routing flow table entry, a next hop encapsulation parameter update record entry and a second updated GTP routing flow table entry, the first updated GTP routing flow table entry is the flow used when the target extended Openflow switch transmits data Table entry, the next hop encapsulation parameter update record entry is a flow table entry used when the target extended Openflow switch encapsulates data, and the second updated GTP routing flow table entry is used when the standard Openflow switch transmits data The flow table entry; Send the relevant parameters of the updated GTP tunnel to the Openflow switch of the target extension and the standard Openflow switch; Obtain the delete GTP tunnel request; Delete the corresponding GTP tunnel through the delete GTP tunnel request; Notify The target extended Openflow switch and/or the target standard Openflow switch, so that the target extended Openflow switch and the target standard Openflow switch correspondingly delete parameters corresponding to the GTP tunnel corresponding to the delete GTP tunnel request;

The Openflow switch of the target extension is also used to receive the relevant parameters of the updated GTP tunnel sent by the Openflow controller; and transmit data according to the relevant parameters of the updated GTP tunnel; receive the first parameter sent by the Openflow controller A notification to delete the GTP tunnel, wherein the first notification to delete the GTP tunnel includes an identifier to delete the GTP tunnel, and the first notification to delete the GTP tunnel is an Openflow switch indicating the target extension delete the signaling of the GTP tunnel; and delete the GTP tunnel corresponding to the identifier of the deleted GTP tunnel through the first notification of deleting the GTP tunnel;

The target standard Openflow switch is also used to receive the relevant parameters of the updated GTP tunnel sent by the Openflow controller; and transmit data according to the relevant parameters of the updated GTP tunnel; receive the second parameter sent by the Openflow controller Delete the notification of the GTP tunnel, wherein, the second notification of deleting the GTP tunnel includes the identifier of the GTP tunnel deletion, and the second notification of deleting the GTP tunnel is to instruct the target standard Openflow switch to delete the GTP tunnel. signaling of the GTP tunnel; and deleting the GTP tunnel corresponding to the identifier of the deleted GTP tunnel through the second notification of deleting the GTP tunnel.

The processing method and system of a kind of GTP tunnel provided by the embodiment of the present invention obtains and establishes the general packet radio service technology tunneling protocol GTP tunnel request through the Openflow controller, and the Openflow controller is a device with the control plane function in the GTP tunnel endpoint; Openflow The controller requests to establish a GTP tunnel by establishing a GTP tunnel, wherein the establishment of a GTP tunnel request includes generating relevant parameters of the GTP tunnel, and the relevant parameters of the GTP tunnel include the first GTP route flow table entry and the next hop encapsulation parameter record entry, the first GTP route The flow table entry is the flow table entry used when the target extended Openflow switch transmits data. The first GTP routing flow table entry includes at least the version number of the general packet radio service technology tunneling protocol data plane GTP-U Version, the general packet radio service technology tunneling protocol The data plane tunnel endpoint identifier is GTP-U TEID, and the next hop encapsulation parameter record entry is the flow table entry used when the target extended Openflow switch encapsulates data. The target extended Openflow switch is the data plane that has the GTP tunnel endpoint in the GTP tunnel Functional equipment; the Openflow controller sends the relevant parameters of the GTP tunnel to the target extended Openflow switch, so that the target extended Openflow switch transmits data according to the first GTP routing flow table entry and the next hop encapsulation parameter record entry. Compared with the GTP tunnel endpoints in the prior art, they are often responsible for the establishment, modification, deletion and routing forwarding functions of the GTP tunnel. Therefore, when establishing, modifying, and deleting the GTP tunnel, it is necessary to negotiate with the endpoint devices corresponding to the GTP tunnel to be processed. Completing the processing of the GTP tunnel to be processed, thereby increasing the complexity of processing the GTP tunnel. Compared with the present invention, the control plane and the forwarding plane of the GTP tunnel endpoint are separated to obtain an Openflow controller and an expanded Openflow switch. Adopting the Openflow controller among the present invention can set up the GTP tunnel between each GTP tunnel end point, by adopting the GTP tunnel that the Openflow controller builds, it is also convenient for the Openflow controller to finish modifying or deleting the GTP tunnel established before, thereby realizing To reduce the complexity of handling GTP tunnels.

Description of drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the following will briefly introduce the drawings that need to be used in the description of the embodiments or the prior art. Obviously, the accompanying drawings in the following description are only These are some embodiments of the present invention. For those skilled in the art, other drawings can also be obtained according to these drawings without any creative effort.

Fig. 1 is a kind of Openflow-based GTP protocol control plane and data plane separation architecture diagram provided by the embodiment of the present invention;

Fig. 2 is the schematic diagram of the flow table entry field that Openflow protocol is extended in the processing method of GTP tunnel that the embodiment of the present invention provides;

FIG. 3 is a flowchart of a GTP tunnel processing method provided by an embodiment of the present invention;

Fig. 4 is the flow chart of another method that Openflow controller establishes GTP tunnel in the processing method of GTP tunnel provided by the embodiment of the present invention;

5 is a schematic diagram of the fields of the first GTP routing flow table entry in the GTP tunnel processing method provided by the embodiment of the present invention;

6 is a schematic diagram of the field of the next hop encapsulation parameter record entry in the GTP tunnel processing method provided by the embodiment of the present invention;

7 is a schematic diagram of the fields of the second GTP routing flow table entry in the GTP tunnel processing method provided by the embodiment of the present invention;

FIG. 8 is a flowchart of another GTP tunnel processing method provided by an embodiment of the present invention;

FIG. 9 is a flowchart of another GTP tunnel processing method provided by an embodiment of the present invention;

Fig. 10(a) is an architecture diagram of the separation of the control plane and the data plane of the GTP tunnel endpoint in the EPC network of the GTP tunnel processing method provided by the embodiment of the present invention;

Fig. 10(b) is a flowchart of a processing method of a GTP tunnel based on an EPC network provided by an embodiment of the present invention;

Fig. 10(c) is a flow chart of another processing method of a GTP tunnel based on an EPC network provided by an embodiment of the present invention;

11 is a flowchart of another GTP tunnel processing method based on an EPC network provided by an embodiment of the present invention;

Fig. 12(a) is a structure diagram of the separation of the control plane and the data plane of the GTP tunnel endpoint in the 2G/3G network of the GTP tunnel processing method provided by the embodiment of the present invention;

Fig. 12(b) is a flowchart of a processing method of a GTP tunnel based on a 2G/3G network provided by an embodiment of the present invention;

FIG. 13 is a flowchart of another GTP tunnel processing method based on a 2G/3G network provided by an embodiment of the present invention;

FIG. 14 is a schematic structural diagram of a GTP tunnel processing system provided by an embodiment of the present invention;

Fig. 15 is a schematic structural diagram of another GTP tunnel processing system provided by an embodiment of the invention.

Detailed ways

The following will clearly and completely describe the technical solutions in the embodiments of the present invention with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only some, not all, embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by persons of ordinary skill in the art without creative efforts fall within the protection scope of the present invention.

Figure 1 is an architecture diagram of the separation of the control plane and the data plane of the GTP protocol based on Openflow. In Figure 1,

110 is a traditional GTP function node integrating control plane and data plane, wherein 102 is a control plane function module, and 101 is a data plane function module. 101 completes encapsulation and decapsulation of service data and data packet forwarding according to the standard GTP-U protocol. 102 is responsible for the establishment of the GTP tunnel. 102 During the establishment of the tunnel, when negotiating with other GTP function nodes integrated with the control plane and data plane, the standard GTP-C protocol needs to be used. When negotiating with the GTP control plane function node (pure GTP-C function node) 103, you can The standard GTP-C protocol is used for negotiation, and other protocols, such as NAS signaling, can also be used for negotiation.

103 is an independently set GTP control function node. 103 corresponds to one or more specific GTP-U data forwarding function nodes, such as 106 . 103 is the GTP-U tunnel negotiation establishment process through 106 . 103 can be integrated with other network functions.

105 and 106 are independently set GTP forwarding function nodes for encapsulating and decapsulating service data. 105 and 106 are extended OpenFlow switches, which comply with the standard OpenFlow protocol, and can match the TEID and version of GTP-U and route data packets accordingly. The extended OpenFlow controller can deliver flow table entries including GTP protocol parameters (first GTP routing flow table entry and next hop encapsulation parameter record entry) to 105 and 106 . 105 and 106 are connected with 104 through a safe channel. 105 and 106 can also forward data as standard Openflow switches.

104 is the integration node of the GTP-C function and the OpenFlow controller, which is the OpenFlow controller. 104 completes the establishment, modification, and deletion of the GTP tunnel after receiving the establishment, modification, and deletion request sent by 103 or the establishment, modification, and deletion request sent by 108 . At the same time, 104 sends the relevant parameters of the GTP tunnel to the extended OpenFlow switches 105 and 106 in the form of OpenFlow flow table entries, and completes the establishment of the GTP tunnel data plane route. 104 can only issue GTP tunnel routes to 105 and 106 (the first GTP routing flow table entry and the next hop encapsulation parameter record entry), and can also issue OpenFlow flow table entries to one or more standard Openflow switches 107 at the same time (the first GTP routing flow table entry) Two GTP routing flow table entries). 104 may also only deliver OpenFlow flow table entries to 107 .

108 is a policy and charging rules function unit (Policy and Charging Rules Function, PCRF) or a fine-grained service data flow policy control function node. 108 can trigger 104 to establish, modify or delete GTP tunnels and different underlying routing paths according to user service attributes, such as audio, video services, internal network services, external network services, high-definition services, and transcoding services. 108 may also request 104 to establish a specific transmission route according to user attributes, such as roaming users, intra-network users, gold and silver users, and operating system versions.

108 and 104 can be set independently, or the functions can be combined and set according to needs.

109 is a node that integrates the functions of the Openflow controller and the PCRF, and has the functions of the Openflow controller and the PCRF.

In the separation architecture of the GTP protocol control plane and data plane, network elements 103, 104, 108, and 109 can be deployed in the same network as the GTP forwarding function node, or can be deployed in a network different from the GTP forwarding function node. 103, 104, 108, and 109 can be installed directly on the hardware platform, or can be installed on a common platform in the form of a virtual machine. 103, 104, 108, and 109 can be deployed separately, or can be deployed in a centralized manner in the data center as required. This embodiment is not limited.

In the separation architecture of the control plane and the data plane of the GTP protocol, the control plane interface has complete backward compatibility, which can ensure intercommunication with traditional networks and intercommunication in roaming scenarios.

Referring to Figure 1, it can be seen that the control plane and the forwarding plane of the GTP tunnel endpoint are separated by using the Openflow protocol; correspondingly, an Openflow controller and an extended Openflow switch are obtained, and the Openflow controller is used to establish a GTP tunnel, modify a GTP tunnel, and delete a GTP Tunnel, the extended Openflow switch is used to transmit data through the GTP tunnel established by the Openflow controller.

Specifically, the Openflow protocol is used to logically separate the GTP-C and GTP-U functions of the GTP tunnel endpoints, and the GTP-C and GTP-U functional network element configurations of the GTP tunnel endpoints are separated. After using the Openflow protocol to separate the control plane and the forwarding plane of the GTP tunnel endpoint, the GTP control function network element (that is, the Openflow controller) is responsible for the establishment, modification and deletion of the GTP tunnel, and the GTP forwarding function network element (that is, the extended Openflow switch) is responsible for the GTP Packet forwarding. The extended Openflow switch also includes encapsulation and decapsulation of GTP data packets.

The GTP tunnel endpoint can be an application layer gateway. For example, the GTP tunnel endpoint can be a Serving Gateway (S-GW) or a Packet Data Network Gateway (P-GW) in the EPC network; or the GTP tunnel endpoint can be SGSN and GGSN in the Global System of Mobile communication (GSM)/UMTS network.

The present invention separates the control plane and the forwarding plane of the general packet radio service technology tunneling protocol GTP tunnel endpoint by adopting the Openflow protocol to obtain an Openflow controller and an extended Openflow switch; wherein, the Openflow controller is used to establish a GTP tunnel and modify a GTP tunnel and delete the GTP tunnel, the extended Openflow switch is used to transmit data through the GTP tunnel established by the Openflow controller. By using the Openflow controller to establish, modify or delete the GTP tunnel, the complexity of processing the GTP tunnel can be reduced. .

It should be noted that, in order to support the forwarding of GTP-U data packets (types of business data) in the present invention, Fig. 2 shows an extension to the Openflow protocol, so that it supports the GTP-U version number in the flow table entry matching field Version and GTP-U tunnel endpoint identifier (Tunnel Endpoint Identifier, TEID). Openflow switches that support GTP-U TEID forwarding need to be able to match 3-bit GTP-UVersion and 32-bit GTP-U TEID.

Among them, in Figure 2, 201 entry port, 202 source MAC address, 203 destination MAC address, 204 virtual local area network identification, 205 MPLS label, 206 MPLS traffic classification (Traffic Class, TC), 207 source IP Address, 208 destination IP address, 209 transmission control protocol/service data packet protocol/flow control transmission protocol source port number, 210 transmission control protocol/service data packet protocol/flow control transmission protocol destination port number, all are Openflow in the prior art The matching field in which the protocol exists, and the 211GTP-U version number and 212GTP-U tunnel endpoint identifier are extended matching fields.

Optionally, in addition to extending these two matching fields, the present invention can also match any other field from 201 to 210 in the data packet header, so as to determine the forwarding operation to be performed.

Fig. 3 describes a processing method of a GTP tunnel, the method is as follows:

301. The Openflow controller obtains a GTP tunnel establishment request, and the Openflow controller is a device capable of controlling a plane function at an endpoint of the GTP tunnel.

In this step, the GTP tunnel establishment request includes QoS parameters and other user parameters, wherein the other user parameters may include the network type and cell number where the user is located.

Wherein, taking 2G/3G as an example for illustration, the Openflow controller may obtain the GTP tunnel establishment request in two ways.

The first method is: the Openflow controller obtains the process of establishing a GTP tunnel initiated by the user equipment (User Equipment, UE), wherein, the UE sends an attach request to the base station, and the base station sends the attach request to the MME, and the MME generates an attach request through the attach request A GTP tunnel establishment request is sent to the S-GW, and then the S-GW sends the GTP tunnel establishment request to the Openflow controller.

The second way is: the Openflow controller receives a trigger instruction sent by the PCRF, and the trigger instruction is used to trigger the Openflow controller to generate a GTP tunnel establishment request.

302. The Openflow controller requests to establish a GTP tunnel by establishing a GTP tunnel, wherein the request for establishing a GTP tunnel includes generating relevant parameters of the GTP tunnel, and the relevant parameters of the GTP tunnel include a first GTP routing flow table entry and a next-hop encapsulation parameter record entry. A GTP routing flow table entry is a flow table entry used when the target extended Openflow switch transmits data. The first GTP routing flow table entry includes at least the general packet radio service technology tunneling protocol data plane version number GTP-U Version, general packet radio service Technology Tunneling Protocol data plane tunnel endpoint identifier GTP-U TEID, the next hop encapsulation parameter record entry is the flow table entry used by the target extended Openflow switch to encapsulate data, the source GTP tunnel endpoint and the destination GTP tunnel endpoint both have GTP tunnel endpoints The target extension of the data plane function in the Openflow switch.

First, the Openflow controller needs to select the Openflow switch used for the target extension of the GTP tunnel; then the Openflow controller obtains available network link parameters, and the available network link parameters include at least the IP address and port number corresponding to the Openflow switch of the target extension. The Openflow controller determines the parameters for establishing a GTP tunnel through the available network link parameters. The parameters for establishing a GTP tunnel include IP addresses at both ends of the GTP tunnel, port numbers at both ends, GTP-U Version, and GTP-U TEID; Generate the first GTP routing flow table entry and the next-hop encapsulation parameter record entry based on the route parameters and the parameters for establishing the GTP tunnel.

Specifically, the Openflow controller first selects two endpoints for each GTP tunnel. Taking 2G/3G as an example, the Openflow controller needs to establish two GTP tunnels, one is the GTP tunnel between the RNC and the SGSN, and the other is the GTP tunnel between the SGSN and the GGSN. Among them, the Openflow controller integrates the control planes on SGSN and GGSN, so that the Openflow controller selects one of SGSN-data (SGSN with only data plane) and GGSN-data (GGSN with only data plane) as the target extension Openflow switch. Then the Openflow controller obtains the available network link parameters, which at least include the IP address, port number, GTP-U Version, and GTP-U TEID corresponding to the SGSN-data and GGSN-data; through the available network link parameters And the parameters for establishing the GTP tunnel generate the first GTP routing flow table entry and the next hop encapsulation parameter record entry.

It should be noted that since the control plane of the RNC is not integrated into the Openflow controller, when the Openflow controller establishes a GTP tunnel between the RNC and the SGSN, the Openflow controller and the RNC need to negotiate to establish it; the control plane of the SGSN and the GGSN Both are integrated into the Openflow controller. When the Openflow controller establishes the GTP tunnel between the SGSN and the GGSN, the Openflow controller only needs to obtain the relevant information of establishing the GTP tunnel (available network link parameters, parameters for establishing the GTP tunnel, etc.) Independently complete the establishment of the GTP tunnel between the SGSN and the GGSN.

For the fields of the first GTP routing flow entry, refer to FIG. 5 . According to Figure 5, it can be seen that the first GTP routing flow table entry should at least include 501 source IP address, 502 destination IP address, 503 source port number, 504 destination port number, 505GTP-U version number and 506GTP-U tunnel Endpoint ID.

For the fields of the next hop encapsulation parameter record entry, refer to FIG. 6 . According to Figure 6, it can be seen that the next hop encapsulation parameter record entry includes 601 hash HashID identifier, 602 source IP address, 603 destination IP address, 604 source port number, 605 destination port number and 606 the next hop tunnel used GTP-U TEID. The Hash ID is used by the Openflow switch for target extension to retrieve the TEID used by the next-hop tunnel based on the received GTP-U packet header information.

303. The Openflow controller sends the relevant parameters of the GTP tunnel to the target-extended Openflow switch, so that the target-extended Openflow switch transmits data according to the first GTP routing flow table entry and the next-hop encapsulation parameter record entry.

Specifically, when the data information is from the RNC to the SGSN and then to the GGSN, the Openflow controller sends the relevant first GTP routing flow table entry to the destination GTP endpoint in the GTP tunnel, such as the SGSN and the GGSN. Wherein, the first GTP routing flow table entry sent to SGSN may include: source IP address (IP address of RNC), destination IP address (IP address of SGSN), source port number (port number of RNC), destination port number ( SGSN port number), GTP-U version number, and GTP-U tunnel endpoint identifier. The first GTP routing flow table entry sent to the GGSN may include: source IP address (the IP address of the SGSN), the destination IP address (the IP address of the GGSN), the source port number (the port number of the SGSN), and the destination port number (the port number), GTP-U version number, and GTP-U tunnel endpoint identifier. The Openflow controller sends the relevant next-hop encapsulation parameter record entry to the source GTP endpoint in the next GTP tunnel, such as the SGSN. Among them, the next hop encapsulation parameter record entry sent to SGSN may include Hash ID, source IP address (IP address of SGSN), destination IP address (IP address of GGSN), source port number (port number of SGSN), destination port number (the port number of the GGSN) and the GTP-U TEID (the GTP tunnel identifier between the SGSN and the GGSN) used by the next-hop tunnel. And vice versa, so I won't go into details here.

It can be understood that the target extended Openflow switch uses the first GTP routing flow table entry to transmit the data packet, and uses the next hop encapsulation parameter record entry to complete the encapsulation of the data packet. Specifically, when any target-extended Openflow switch receives a data packet, it uses the GTP protocol to decapsulate the data packet to obtain the header information of the data packet, and through the header information and the locally stored first GTP routing flow table entry Matching is performed to obtain the first GTP routing flow table entry matching the packet header information, and the next step operation for the data packet is obtained through the operation information (Action) in the matching first GTP routing flow table entry. When the next step is to send to the next port, and use the GTP protocol for encapsulation (it can be regarded as the information to continue to transmit data through the GTP tunnel, indicating that the Openflow switch of the target extension needs to use the next GTP tunnel to continue to transmit data), set the The Openflow switch of the target extension uses the header information to match the Hash ID in the next hop encapsulation parameter record entry, obtains the next hop encapsulation parameter record entry that matches the header information, and then records the entry according to the matched next hop encapsulation parameter record entry The information in is to re-encapsulate the decapsulated data packet. After re-encapsulation, continue to send data according to the operation information in the first GTP routing flow table entry.

The present invention separates the control plane and the forwarding plane of the GTP tunnel endpoints to obtain an Openflow controller and an expanded Openflow switch. The Openflow controller in the present invention can be used to establish GTP tunnels between each GTP tunnel endpoint, and the Openflow controller is used to establish The GTP tunnel is also convenient for the Openflow controller to modify or delete the previously established GTP tunnel, thereby reducing the complexity of processing the GTP tunnel.

Corresponding to the description in step 302, optionally, the Openflow controller can receive the policy information sent by the PCRF; the Openflow controller generates the first policy GTP routing flow table entry and the next hop encapsulation parameter through the available network link parameters and policy information A policy record entry and a second policy GTP routing flow table entry. The corresponding Openflow controller sends the first policy GTP routing flow table entry and the next hop encapsulation parameter policy record entry to the target extended Openflow switch, and sends the second policy GTP routing table entry to the standard Openflow switch.

Optionally, the Openflow controller is also configured to generate a second GTP routing flow table entry through the parameters for establishing the GTP tunnel, and send the second GTP routing flow table entry to the standard Openflow switch (the standard Openflow switch sends the GTP routing flow table entry through the Openflow controller The second GTP routing flow table entry of the GTP routing table entry is enough to transmit the GTP data packet, and there is no need to use the GTP protocol to encapsulate or decapsulate the GTP data packet), the second GTP routing flow table entry is the flow table used by the standard Openflow switch to transmit data entry. Standard Openflow switches are all Openflow switches managed by the Openflow controller. It can be seen that the Openflow controller sends the generated second GTP routing flow table entries to all managed standard Openflow switches. Then whenever the target standard Openflow switch recognizes the second GTP routing flow table entry corresponding to the received data packet, according to the information in the header information of the data packet (such as the destination IP address, etc.) and all the second GTP routing flow table entries stored locally Matching is performed, so as to obtain the corresponding second GTP routing flow table entry.

Specifically, reference may be made to FIG. 7 for the field format of the second GTP routing flow table entry. According to FIG. 7 , it can be seen that the second GTP routing flow table entry includes one or more of: 701 source IP address, 702 destination IP address, 703 source port number and 704 destination port number.

As shown in FIG. 4, in another embodiment of the present invention, after step 301 in FIG. 3, that is, after the Openflow controller acquires the request to establish a GTP tunnel, it also includes:

304. The Openflow controller acquires decision result information.

The decision result information is used to explain the specific processing of the data corresponding to a specific business. The specific processing includes but is not limited to any of the following forms: transcoding data corresponding to a specific business, traffic isolation for data corresponding to a specific business, sending data to user equipment (User Equipment, UE) to send warning reminder messages or perform advertising video insertion for data corresponding to specific services.

Among them, the Openflow controller can obtain decision result information in two ways:

In the first way, the Openflow controller receives the decision result information sent by the PCRF.

In the second way, the Openflow controller receives the detection result generation strategy of an external network element (such as DPI).

305. The Openflow controller generates a specific GTP routing flow table entry for a specific service according to the decision result information.

It should be noted that the specific GTP routing flow table entry is used to instruct the target standard Openflow switch to send the transmitted service data to the network middleware. The network middleware is located inside GSM, UMTS or EPC, and the deployment method can be independent host deployment Or cloud center deployment, its function is to complete the processing and operation of business data in the GTP-U tunnel in the core network, such as transcoding user voice and video data before entering the terminal, inserting specific message presentation forms before business data including but not Limited to video, audio, text and other advertising content or reminders and warnings provided by operators or third parties.

Network middleware can be transcoding server, media insertion, firewall, DPI, etc.

306. The Openflow controller selects a target standard Openflow switch for the GTP tunnel.

307. The Openflow controller sends the specific GTP routing flow table entry to the target standard Openflow switch.

It can be understood that the Openflow controller sends specific GTP routing flow table entries to all selected target standard Openflow switches.

The specific GTP routing flow table entry has the same function as the second GTP routing flow table entry, and includes the same fields. The difference is that the specific GTP routing flow table entry has a higher priority than the second GTP routing flow table entry. For example, when a target standard Openflow switch locally stores a specific GTP routing flow table entry and a second GTP routing flow table entry with the same matching strength, then the target standard Openflow switch adopts the specific GTP routing flow table entry with higher flow entry priority. Routing flow table entries to transmit data.

As shown in Figure 8, in another embodiment of the present invention, the present invention also provides a processing method of a GTP tunnel, the method is as follows:

801. The Openflow controller acquires a GTP tunnel modification request.

Wherein, the manner in which the Openflow controller acquires the request to modify the GTP tunnel is the same as the manner in which the request to establish the GTP tunnel is acquired, and will not be repeated here.

802. The Openflow controller requests to re-establish the GTP tunnel by modifying the GTP tunnel.

Wherein, re-establishing the GTP tunnel includes generating and updating relevant parameters of the GTP tunnel, and the relevant parameters of updating the GTP tunnel include a first updated GTP routing flow table entry, a next-hop encapsulation parameter updating record entry, and a second updated GTP routing flow table entry. The first update GTP routing flow table entry is the flow table entry used when the target extended Openflow switch transmits data, the next hop encapsulation parameter update record entry is the flow table entry used when the target extended Openflow switch transmits data, and the second update GTP The routing flow table entry is the flow table entry used when the target standard Openflow switch transmits data.

The Openflow controller requests to re-establish the GTP tunnel by modifying the GTP tunnel, which specifically includes: the Openflow controller obtains the updated available network link parameters, and the updated available network link parameters include at least the updated IP address corresponding to the target extended Openflow switch ,The port number. The Openflow controller determines parameters for re-establishing the GTP tunnel according to the updated available network link parameters, and the parameters for re-establishing the GTP tunnel include IP addresses at both ends, port numbers at both ends, and GTP-U corresponding to the GTP tunnel. Version, GTP-U TEID, then generate the first update GTP routing flow table entry and the next hop encapsulation parameter update record entry by the updated available network link parameters and the parameters of re-establishing the GTP tunnel, first update the GTP routing flow table The entry is the flow table entry used by the extended Openflow switch to transmit data. The next hop encapsulation parameter update record entry includes the updated Hash ID, the updated source IP address, the updated destination IP address, and the updated source port number. , the updated destination port number, and the updated GTP-U TEID used by the next-hop tunnel.

Optionally, the relevant parameters of the GTP tunnel further include a second updated GTP routing flow table entry, where the second updated GTP routing flow table entry is a flow table entry used when a standard Openflow switch transmits data. After the Openflow controller obtains the updated available network link parameters and generates parameters for re-establishing the GTP tunnel, the Openflow controller generates a second updated GTP routing flow table entry by using the available network link parameters and generating parameters for re-establishing the GTP tunnel.

It should be noted that for the fields of the first updated GTP routing flow table entry, the next hop encapsulation parameter update record entry, and the second updated GTP routing flow table entry, reference may be made to FIG. 5, FIG. 6 and FIG. A repeat.

Optionally, the Openflow controller receives the updated policy information sent by the PCRF. The Openflow controller generates a first update policy GTP routing flow table entry, a next hop encapsulation parameter policy record entry, and a second update policy GTP routing flow table entry according to available network link parameters and policy information.

803. The Openflow controller sends the relevant parameters of the updated GTP tunnel to the target-extended Openflow switch, so that the target-extended Openflow switch transmits data according to the first updated GTP routing flow table entry and the next-hop encapsulation parameter update record entry.

804. The Openflow controller sends the second updated GTP routing flow table entry to the standard Openflow switch, so that the standard Openflow switch transmits data according to the second updated GTP routing flow table entry.

The present invention separates the control plane and the forwarding plane of the GTP tunnel endpoints to obtain an Openflow controller and an expanded Openflow switch. The Openflow controller in the present invention can be used to establish GTP tunnels between each GTP tunnel endpoint, and the Openflow controller is used to establish The GTP tunnel is also convenient for the Openflow controller to modify or delete the previously established GTP tunnel, thereby reducing the complexity of processing the GTP tunnel.

As shown in Figure 9, in another embodiment of the present invention, the present invention also provides a processing method of a GTP tunnel, the method is as follows:

901. The Openflow controller acquires a GTP tunnel deletion request, where the GTP tunnel deletion request includes an identifier indicating to delete the GTP tunnel.

In this step, the specific format of the identifier indicating to delete the GTP tunnel is not limited.

Wherein, the manner in which the Openflow controller obtains the request to delete the GTP tunnel is the same as the manner in which the request to establish the GTP tunnel is obtained, and details are not repeated here.

902. The Openflow controller deletes the corresponding GTP tunnel through the delete GTP tunnel request, and notifies the target extended Openflow switch and the target standard Openflow switch, so that the target extended Openflow switch and the target standard Openflow switch correspondingly delete the request corresponding to the deletion of the GTP tunnel The parameters corresponding to the GTP tunnel.

Wherein, the target extended Openflow switch deletes the first GTP routing flow table entry and the next hop encapsulation parameter policy record entry, and the target standard Openflow switch deletes the second GTP routing flow table entry.

The present invention separates the control plane and the forwarding plane of the GTP tunnel endpoints to obtain an Openflow controller and an expanded Openflow switch. The Openflow controller in the present invention can be used to establish GTP tunnels between each GTP tunnel endpoint, and the Openflow controller is used to establish The GTP tunnel is also convenient for the Openflow controller to modify or delete the previously established GTP tunnel, thereby reducing the complexity of processing the GTP tunnel.

In another embodiment of the present invention, the present invention provides a method for transmitting data based on Openflow, wherein, it should be noted that the method is based on the EPC network. Figure 10(a) is an architecture diagram of the separation of the control plane and the data plane of the GTP tunnel endpoint in the EPC network. Figure 10(b) shows the processing method of the GTP tunnel in the EPC network. In one form of this method, the UE initiates the process of establishing, modifying, and deleting the GTP tunnel. Here, only the establishment process is described. The specific process is as follows:

1001. The UE sends an attach request to the base station.

The attach request includes service data information, authentication information, and the like.

1002. The base station sends the attach request to a mobility management entity (Mobility Management Entity, MME).

1003. The MME generates a GTP tunnel establishment request based on the content in the attach request, and sends the GTP tunnel establishment request to the S-GW.

1004. The S-GW sends the GTP tunnel establishment request to the Openflow controller.

Among them, in this step, referring to the S-GW (GTP tunnel endpoint) in Figure 10(a), the control plane and the data plane are not separated. Here, the S-GW has the same function as in the prior art, that is, it also has a control function and forwarding function.

1005. The Openflow controller selects an Openflow switch for target extension of the GTP tunnel.

The Openflow controller selects the target extended Openflow switch as the egress endpoint of the GTP tunnel, and sends the TEID to the S-GW according to the negotiated GTP parameters including source IP address and destination IP address, source and destination port numbers.

1006, the GTP parameters used by the S-GW and the base station are transmitted through the MME, so that the S-GW and the base station negotiate to establish a GTP tunnel between the S-GW and the base station.

Wherein, in this step, refer to the S-GW (GTP tunnel endpoint) in Fig. 10(a) without separating the control plane and the data plane, where the S-GW has the same function as that in the prior art. As another embodiment of the present invention, the control plane and the data plane of the S-GW can be separated, and the S-GW-data (only equipped with the data plane of the S-GW) is used as an Openflow switch for target expansion.

Since the control plane and the forwarding plane of the S-GW have not been separated here, the GTP tunnel between the S-GW and the base station is negotiated and established by themselves. If the control plane of the S-GW is separated from the forwarding invention, and the control plane of the S-GW is integrated into the Openflow controller, the Openflow controller and the base station negotiate the GTP tunnel between the S-GW and the base station.

It should be noted that, in this implementation, step 1005 may be performed first, and then step 1006 may be performed; or step 1005 and step 1006 may be performed simultaneously. For the convenience of description, in FIG. 10( b ), step 1005 is executed first, and then step 1006 is executed as an example for illustration.

1007, the Openflow controller establishes the GTP tunnel between the S-GW and the Openflow switch of the target extension, and delivers the first GTP routing flow table entry and the next hop encapsulation parameter record entry to the target extension of the egress termination point of the GTP tunnel Openflow switch.

It can be understood that, since the control plane and the forwarding plane of the S-GW have not been separated in this step, the Openflow controller and the S-GW need to negotiate the GTP tunnel between the S-GW and the target extended Openflow switch.

1008. The Openflow controller generates a second GTP routing flow table entry, and issues it to the standard Openflow switch.

1009. The Openflow controller obtains decision result information, and generates a specific GTP routing flow table entry.

1010. The Openflow controller selects a target standard Openflow switch for the GTP tunnel, and sends the specific GTP routing flow table entry to the target standard Openflow switch.

The processing method of a kind of GTP tunnel shown in Fig. 10 (c), this method is initiated by PCRF GTP tunnel establishes, revises, deletes the process, here only explains with the establishment process, and specific flow is as follows:

1001', the PCRF triggers the Openflow controller to generate a GTP tunnel establishment request.

1002', the Openflow controller selects an Openflow switch for the target extension of the GTP tunnel.

Specifically, the Openflow controller selects the Openflow switch to which the target of the GTP tunnel is extended, and at the same time, sends the source and destination IP addresses, source and destination port numbers, and tunnel identifier TEID used by the GTP tunnel to the S-GW.

1003', the GTP parameters used by the S-GW and the base station are transmitted through the MME, so that the S-GW and the base station negotiate to establish a GTP tunnel between the S-GW and the base station.

1004', the Openflow controller establishes a GTP tunnel between the S-GW and the target-extended Openflow switch, and delivers the first GTP routing flow table entry and the next-hop encapsulation parameter record entry to the target-extended Openflow switch.

1005', the Openflow controller generates a second GTP routing flow table entry, and issues it to the standard Openflow switch.

1006', the Openflow controller obtains decision result information, and generates a specific GTP routing flow table entry.

1007', the Openflow controller selects a target standard Openflow switch for the GTP tunnel, and sends the specific GTP routing flow table entry to the target standard Openflow switch.

Based on the methods described above in Figure 10(b) and Figure 10(c), as shown in Figure 11, the present invention also provides another GTP tunnel processing method, which is specifically as follows:

1101. After the GTP tunnel between the S-GW and the base station is established, the base station sends user data request information to the S-GW.

1102. The S-GW routes the user data request information to the application server corresponding to the service through the target standard Openflow switch and the target extended Openflow switch.

1103. The application server sends service data A to the target extended Openflow switch according to the user data request information.

1104. The target extended Openflow switch processes the service data A through the first GTP routing flow table entry and the next hop encapsulation parameter record entry to obtain service data B, and then forwards the service data B to the second target standard Openflow switch.

Specifically, the target extended Openflow switch decapsulates the service data A using the GTP protocol to obtain the service data A' and the header information of the service data A, and obtains the first GTP routing flow table entry corresponding to the service data A through the header information and the next hop encapsulation parameter record entry, the business data A' is encapsulated by the GTP protocol through the next hop encapsulation parameter record entry, and the service data B is obtained, and then the service data B is transmitted through the operation information of the first GTP routing flow table entry .

1105. The second target standard Openflow switch sends the service data B to the network middleware.

This step is an optional step. When the service data A is video data or it is necessary to insert an advertisement or traffic warning before the user watches the service data A, the second target standard Openflow switch is based on the second GTP route issued by the Openflow controller The flow table entry sends business data A to the network middleware.

It can be understood that, according to the packet header information of the service data B, the second target standard Openflow switch matches a second GTP routing flow table entry and a specific GTP routing flow table entry with the same matching degree, then the second target standard Openflow switch adopts the flow A specific GTP routing flow table entry with a higher entry priority is used to transmit service data B.

1106. The network middleware performs specific processing on the service data B, and sends the service data B after the specific processing to the first target standard Openflow switch.

1107. The first target standard Openflow switch receives the service data B after the specific processing, and decapsulates the service data B to obtain the service data A.

1108. The first target standard Openflow switch sends the service data A to the S-GW.

1109. The S-GW encapsulates the service data A with the GTP protocol to obtain the service data B', and sends the service data B' to the base station.

1110. The base station decapsulates the service data B' to obtain service data A, and then sends service data A to the UE.

The present invention separates the control plane and the forwarding plane of the GTP tunnel endpoints to obtain an Openflow controller and an expanded Openflow switch. The Openflow controller in the present invention can be used to establish GTP tunnels between each GTP tunnel endpoint, and the Openflow controller is used to establish The GTP tunnel is also convenient for the Openflow controller to complete the modification or deletion of the previously established GTP tunnel, thereby reducing the complexity of processing the GTP tunnel; and the business data can be planned in advance through the Openflow controller, so that the GTP data Some specific information is added during the transmission of the packet, so that additional information of the business data can be added and the ability to adjust the transmission path of the business data can be improved.

It should be noted that, as another embodiment of the present invention, a GTP tunnel processing method shown in FIG. 10(b)/FIG. 10(c) and FIG. 11 may be included. For this method, reference may be made to the description in Fig. (b)/Fig. 10(c) and Fig. 11 , and details will not be repeated here.

In another embodiment of the present invention, the present invention provides a method for transmitting data based on Openflow, wherein, it should be noted that the method is based on a 2G/3G network. Fig. 12(a) is an architecture diagram of the separation of the control plane and the data plane of the GTP tunnel endpoint in the 2G/3G network. Figure 12(b) shows the processing method of the GTP tunnel in the 2G/3G network. In one form of this method, the UE initiates the process of establishing, modifying and deleting the GTP tunnel. Here, only the establishment process is used for illustration. The specific process is as follows:

1201. The UE sends a packet data protocol context (Packet Data Protocol context, PDP context) activation request to a radio network controller (Radio Network Controller, RNC), and the RNC sends the PDP context activation request to the Openflow controller.

1202. The Openflow controller selects a corresponding target extended Openflow switch for establishing a GTP tunnel through the PDP context activation request.

As shown in Figure 12(a), the target extended Openflow switch in this step includes SGSN-data and GGSN-data.

Both the SGSN-data and the GGSN-data may be Openflow switches supporting the target extension of GTP-U.

1203. The Openflow controller acquires available network link parameters, determines parameters for establishing a GTP tunnel, and then establishes a GTP tunnel.

Specifically, the Openflow controller negotiates to establish the GTP tunnel between SGSN-data and GGSN-data according to the available GTP tunnel source IP address and destination IP address, source port number, destination port number and TEID maintained by the control planes of SGSN and GGSN.

The Openflow controller negotiates with the RNC to establish a GTP tunnel between the RNC and the SGSN according to the available source IP address and destination IP address, source port number, destination port number and TEID maintained by the SGSN control plane.

1204. The Openflow controller delivers the corresponding first GTP routing flow table entry and next-hop encapsulation parameter record entry to the target extended Openflow switch.

Specifically, the Openflow controller sends the corresponding first GTP routing flow table entry and next-hop encapsulation parameter record entry to the SGSN-data and GGSN-data respectively.

1205. The Openflow controller generates a second GTP routing flow table entry, and sends it to the standard Openflow switch.

1206. The Openflow controller obtains decision result information, and generates a specific GTP routing flow table entry.

1207. The Openflow controller selects a target standard Openflow switch for the GTP tunnel, and sends the specific GTP routing flow table entry to the target standard Openflow switch.

Based on the method described in Figure 12(b) above, as shown in Figure 13, the present invention also provides another GTP tunnel processing method, which is specifically as follows:

1301. After the Openflow controller establishes the GTP tunnel, the RNC sends user data request information to the first extended Openflow switch.

It can be understood that the first extended Openflow switch in this step may be SGSN-data.

1302. The first target extended Openflow switch routes the user data request information to the application server corresponding to the service through the first target standard Openflow switch, the second target standard Openflow switch, and the second target extended Openflow switch.

1303. The application server sends the service data A to the second target extended Openflow switch according to the user data request information.

It can be understood that, in this step, the second target extended Openflow switch may be GGSN-data.

1304, the Openflow switch of the second target extension encapsulates the service data A with the GTP protocol according to the first GTP routing flow table entry and the next hop encapsulation parameter record entry, obtains the service data B, and then forwards the service data B to the second target standard Openflow switch.

The service data B is the service data A encapsulated by the GTP-U protocol.

1305. The second target standard Openflow switch sends the service data B to the network middleware.

This step is an optional step. When the service data A is video data or it is necessary to insert an advertisement or traffic warning before the user watches the service data A, the second target standard Openflow switch is based on the second GTP route issued by the Openflow controller The flow table entry sends business data A to the network middleware.

1306. The network middleware performs specific processing on the service data B, and sends the service data B after the specific processing to the first target standard Openflow switch.

1307. The first target standard Openflow switch receives the service data B after the specific processing, decapsulates the service data B, and obtains the service data A.

1308. The first target standard Openflow switch sends the service data A to the first target extended Openflow switch.

1309. The first extended Openflow switch encapsulates the service data A with the GTP protocol to obtain service data B', and sends the service data B' to the RNC.

1310. The RNC decapsulates the service data B' to obtain the service data A, and then sends the service data A to the UE.

The present invention separates the control plane and the forwarding plane of the GTP tunnel endpoints to obtain an Openflow controller and an expanded Openflow switch. The Openflow controller in the present invention can be used to establish GTP tunnels between each GTP tunnel endpoint, and the Openflow controller is used to establish The GTP tunnel is also convenient for the Openflow controller to complete the modification or deletion of the previously established GTP tunnel, thereby reducing the complexity of processing the GTP tunnel; and the business data can be planned in advance through the Openflow controller, so that the GTP data Some specific information is added during the transmission of the packet, so that additional information of the business data can be added and the ability to adjust the transmission path of the business data can be improved.

It should be noted that, as another embodiment of the present invention, a GTP tunnel processing method shown in FIG. 12( b ) and FIG. 13 may be included. For this method, reference may be made to the descriptions in FIG. 12( b ) and FIG. 13 , and details will not be repeated here.

As shown in Fig. 14, the embodiment of the present invention provides a processing system 14 of a GTP tunnel, the system 14 includes: an Openflow controller 1401, an Openflow switch 1402 with target extension, wherein the Openflow controller 1401 is equipped with a control plane in a GTP tunnel endpoint function, the target extended Openflow switch 1402 is a device in the GTP tunnel that has the data plane function in the GTP tunnel endpoint.

The Openflow controller 1401 is configured to obtain a request to establish a GTP tunnel; request to establish a GTP tunnel by establishing a GTP tunnel, wherein the request to establish a GTP tunnel includes generating relevant parameters of the GTP tunnel, and the relevant parameters of the GTP tunnel include the first GTP routing flow table entry and the following One-hop encapsulation parameter record entry, the first GTP routing flow table entry is the flow table entry used when the target extended Openflow switch 1402 transmits data, the first GTP routing flow table entry includes at least the version number of the general packet radio service technology tunneling protocol data plane GTP-U Version, General Packet Radio Services Technology Tunneling Protocol data plane tunnel endpoint identifier GTP-U TEID, and the next-hop encapsulation parameter record entry is the flow table entry used when the Openflow switch 1402 of the target extension is encapsulating data; Parameters are sent to the target extended Openflow switch 1402;

The Openflow switch 1402 of the target extension is used to receive the first GTP routing flow table entry and/or the next hop encapsulation parameter record entry sent by the Openflow controller 1401; and according to the first GTP routing flow table entry and the next hop encapsulation parameter record Entry transfer data.

Further, the Openflow controller is specifically used to select the Openflow switch 1402 for the target extension of the GTP tunnel; obtain available network link parameters, the available network link parameters include at least the IP address and port number corresponding to the Openflow switch 1402 for target expansion ; Determine the parameters for establishing the GTP tunnel through the available network link parameters. The parameters for establishing the GTP tunnel include the source IP address, destination IP address, source port number, destination port number, GTP-U Version, and GTP-U TEID corresponding to the GTP tunnel; The first GTP routing flow table entry and the next-hop encapsulation parameter record entry are generated by using available network link parameters and parameters for establishing a GTP tunnel.

Wherein, the relevant parameters of the GTP tunnel also include the second GTP routing flow table entry, the second GTP routing flow table entry is the flow table entry used when the standard Openflow switch transmits data, and the standard Openflow switch is all standard Openflow switches managed by the Openflow controller .

The Openflow controller 1401 is also configured to generate a second GTP routing flow table entry by establishing parameters of the GTP tunnel; send the second GTP routing flow table entry to a standard Openflow switch;

Further, the system 14 also includes a target standard Openflow switch 1403 . The target standard Openflow switch is a standard Openflow switch that participates in transmitting data in the GTP tunnel.

The Openflow controller 1401 is also used to obtain decision result information. The decision result information is used to instruct specific processing of data corresponding to a specific business. The specific processing is in any of the following forms: transcoding data corresponding to a specific business, Traffic isolation for data corresponding to the business, sending a warning reminder message to the user equipment UE or performing advertisement video insertion for data corresponding to a specific business; generating a specific GTP routing flow table entry for data corresponding to a specific business according to the decision result information; and selecting for The target standard Openflow switch 1403 of the GTP tunnel; the specific GTP routing flow table entry is sent to the target standard Openflow switch 1403;

The target standard Openflow switch 1403 is configured to receive the specific GTP routing flow table entry sent by the OPenflow controller 1401 .

Further, the Openflow controller is also used to receive the policy information sent by the policy and charging rule functional unit PCRF; through the available network link parameters and policy information, generate the first policy GTP routing flow table entry, the next hop encapsulation parameter policy Record the entry and the second policy GTP routing flow table entry, and send the first policy GTP routing flow table entry and the next hop encapsulation parameter policy record entry to the Openflow switch 1402 of the target extension, and send the second policy GTP routing flow table entry For standard Openflow switches;

The Openflow switch 1402 of the target extension is also used to receive the first policy GTP routing flow table entry and the next hop encapsulation parameter policy record entry sent by the Openflow controller 1401;

The target standard Openflow switch 1403 is also used to receive the second policy GTP routing flow table entry sent by the Openflow controller 1401;

Further, the Openflow controller 1401 is also used to obtain a request to modify the GTP tunnel; request to modify the GTP tunnel by modifying the GTP tunnel, wherein the request to modify the GTP tunnel includes generating and updating relevant parameters of the GTP tunnel, and updating the relevant parameters of the GTP tunnel includes the first update GTP routing flow table entry, next hop encapsulation parameter update record entry and the second update GTP routing flow table entry, the first update GTP routing flow table entry is the flow table entry used when the Openflow switch 1402 for target expansion transmits data, and the next The jump encapsulation parameter update record entry is the flow table entry used when the target extended Openflow switch 1402 encapsulates data, and the second update GTP routing flow table entry is the flow table entry used when the standard Openflow switch transmits data; the relevant parameters of the GTP tunnel will be updated Send to the Openflow switch 1402 and the standard Openflow switch of the target extension; Obtain the delete GTP tunnel request; Delete the corresponding GTP tunnel by deleting the GTP tunnel request; Notify the Openflow switch 1402 of the target extension and/or the target standard Openflow switch 1403, so that the target extension The Openflow switch 1402 and the target standard Openflow switch 1403 correspondingly delete the parameter corresponding to the GTP tunnel corresponding to the delete GTP tunnel request.

The Openflow switch 1402 of the target extension is also used to receive the relevant parameters of the updated GTP tunnel sent by the Openflow controller 1401; and transmit data according to the relevant parameters of the updated GTP tunnel; receive the notification of the first deletion of the GTP tunnel sent by the Openflow controller 1401, Wherein, the first notification of deleting the GTP tunnel includes the identifier of the deletion GTP tunnel, and the first notification of deleting the GTP tunnel is signaling indicating that the Openflow switch 1402 of the target extension deletes the GTP tunnel; The GTP tunnel corresponding to the identifier of the GTP tunnel.

The target standard Openflow switch 1402 is also used to receive the relevant parameters of the updated GTP tunnel sent by the Openflow controller 1401; and transmit data according to the relevant parameters of the updated GTP tunnel; receive the second notification of deleting the GTP tunnel sent by the Openflow controller 1401, wherein , the second notification of deleting the GTP tunnel includes the identifier of the deletion of the GTP tunnel, and the second notification of deleting the GTP tunnel is signaling indicating that the target standard Openflow switch 1403 deletes the GTP tunnel; and the GTP tunnel is deleted through the second notification of deleting the GTP tunnel The identifier corresponding to the GTP tunnel.

The present invention separates the control plane and the forwarding plane of the GTP tunnel endpoints to obtain an Openflow controller and an expanded Openflow switch. The Openflow controller in the present invention can be used to establish GTP tunnels between each GTP tunnel endpoint, and the Openflow controller is used to establish The GTP tunnel is also convenient for the Openflow controller to complete the modification or deletion of the previously established GTP tunnel, thereby reducing the complexity of processing the GTP tunnel; and planning the business data in advance so that the GTP data packet is transmitted during transmission. Add some specific information, so as to increase the additional information of the service data and improve the adjustment ability of the service data transmission path.

Those skilled in the art can clearly understand that for the convenience and brevity of description, only the division of the above-mentioned functional modules is used as an example for illustration. In practical applications, the above-mentioned function allocation can be completed by different functional modules according to needs. The internal structure of the device is divided into different functional modules to complete all or part of the functions described above. For the specific working process of the above-described system, device, and unit, reference may be made to the corresponding process in the foregoing method embodiments, and details are not repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed system, device and method can be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of the modules or units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components can be Incorporation may either be integrated into another system, or some features may be omitted, or not implemented. In another point, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of devices or units may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or may be distributed to multiple network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, each unit may exist separately physically, or two or more units may be integrated into one unit. The above-mentioned integrated units can be implemented in the form of hardware or in the form of software functional units.

If the integrated unit is realized in the form of a software function unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the essence of the technical solution of the present invention or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium , including several instructions to make a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor (processor) execute all or part of the steps of the method described in each embodiment of the present invention. The aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), magnetic disk or optical disk and other media that can store program codes. .

The above is only a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Anyone skilled in the art can easily think of changes or substitutions within the technical scope disclosed in the present invention. Should be covered within the protection scope of the present invention. Therefore, the protection scope of the present invention should be determined by the protection scope of the claims.

Claims (10)

1. A processing method of a GTP tunnel, characterized in that, comprising: The Openflow controller acquires a request for establishing a General Packet Radio Service Technology Tunneling Protocol GTP tunnel, and the Openflow controller is a device with a control plane function in the GTP tunnel endpoint; The Openflow controller establishes a GTP tunnel through the establishment of the GTP tunnel request, wherein the establishment of the GTP tunnel request includes generating relevant parameters of the GTP tunnel, and the relevant parameters of the GTP tunnel include a first GTP routing flow table entry and a next hop Encapsulating parameter record entries, the first GTP routing flow table entry is a flow table entry used when the target extended Openflow switch transmits data, and the first GTP routing flow table entry includes at least the general packet radio service technology tunneling protocol data plane version No. GTP-U Version, General Packet Radio Services Technology Tunneling Protocol data plane tunnel endpoint identifier GTP-UTEID, the next hop encapsulation parameter record entry is the flow table entry used when the target extended Openflow switch encapsulates data, and the The Openflow switch of the target extension is a device having the data plane function in the GTP tunnel endpoint as the GTP tunnel; The Openflow controller sends the relevant parameters of the GTP tunnel to the target extended Openflow switch, so that the target extended Openflow switch records according to the first GTP routing flow table entry and the next hop encapsulation parameter Entry transfer data. 2. the processing method of GTP tunnel according to claim 1, is characterized in that, described Openflow controller sets up GTP tunnel by described setting up GTP tunnel request, comprising: The Openflow controller selects an Openflow switch for the target extension of the GTP tunnel; The Openflow controller acquires available network link parameters, and the available network link parameters include at least the IP address and port number corresponding to the Openflow switch of the target extension; The Openflow controller determines parameters for establishing the GTP tunnel through the available network link parameters, and the parameters for establishing the GTP tunnel include IP addresses at both ends, port numbers at both ends, GTP- U Version, GTP-U TEID; The Openflow controller generates a first GTP routing flow table entry and a next-hop encapsulation parameter record entry based on the available network link parameters and the parameters for establishing the GTP tunnel. 3. the processing method of GTP tunnel according to claim 2, is characterized in that, the relevant parameter of described GTP tunnel also comprises the second GTP routing flow table entry, and described second GTP routing flow table entry is standard Openflow switch transmission The flow table entries used for data, the standard Openflow switches are all standard Openflow switches managed by the Openflow controller; After the Openflow controller obtains the available network link parameters of the Openflow switch of the target extension, it also includes: The Openflow controller generates the second GTP routing flow table entry through the parameter of establishing the GTP tunnel; The Openflow controller sends the second GTP routing flow table entry to a standard Openflow switch, so that the standard Openflow switch transmits data according to the second GTP routing flow table entry. 4. according to the processing method of the GTP tunnel described in claim 2 or 3, it is characterized in that, after described Openflow controller is set up GTP tunnel by described setting up GTP tunnel request, described method also comprises: The Openflow controller acquires decision result information, and the decision result information is used to indicate specific processing for data corresponding to a specific service, and the specific processing is in any of the following forms: transcoding the data corresponding to the specific service . Performing traffic isolation for the data corresponding to the specific service, sending a warning reminder message to the user equipment UE, or performing advertisement video insertion for the data corresponding to the specific service; The Openflow controller generates a specific GTP routing flow table entry for the data corresponding to the specific service according to the decision result information; The Openflow controller selects a target standard Openflow switch for the GTP tunnel; The Openflow controller sends the specific GTP routing flow table entry to the target standard Openflow switch. 5. the processing method of GTP tunnel according to claim 4, is characterized in that, described method also comprises: The Openflow controller receives the policy information sent by the policy and charging rule functional unit PCRF; The Openflow controller generates a first policy GTP routing flow table entry, a next hop encapsulation parameter policy record entry, and a second policy GTP routing flow table entry based on the available network link parameters and the policy information. 6. the processing method of GTP tunnel according to claim 1, is characterized in that, described method also comprises: The Openflow controller acquires a request to modify the GTP tunnel; request to modify the GTP tunnel through the modified GTP tunnel request, wherein the request to modify the GTP tunnel includes generating relevant parameters for updating the GTP tunnel, and the relevant parameters for updating the GTP tunnel include a first updated GTP route A flow table entry, a next hop encapsulation parameter update record entry, and a second updated GTP routing flow table entry, the first updated GTP routing flow table entry is a flow table entry used when the target extended Openflow switch transmits data, so The next hop encapsulation parameter update record entry is a flow table entry used when the target extended Openflow switch encapsulates data, and the second updated GTP routing flow table entry is a flow table entry used when the standard Openflow switch transmits data ; Correspondingly sending the related parameters of the updated GTP tunnel to the target extended Openflow switch and the standard Openflow switch; or, The Openflow controller acquires a delete GTP tunnel request, wherein the delete GTP tunnel request includes an identifier indicating to delete the GTP tunnel; deletes the corresponding GTP tunnel through the delete GTP tunnel identifier; notifies the target extended Openflow switch And/or the target standard Openflow switch, so that the target extended Openflow switch and the target standard Openflow switch correspondingly delete parameters corresponding to the GTP tunnel corresponding to the delete GTP tunnel request. 7. A processing system of a GTP tunnel, characterized in that, the system includes an Openflow controller, an Openflow switch for target expansion, wherein the Openflow controller is a device possessing a control plane function in a GTP tunnel endpoint, and the target The extended Openflow switch is a device having the data plane function in the GTP tunnel endpoint in the GTP tunnel, including: The Openflow controller is configured to obtain a request for establishing a General Packet Radio Service Technology Tunneling Protocol (GTP) tunnel; request to establish a GTP tunnel through the establishment of a GTP tunnel request, wherein the establishment of a GTP tunnel request includes generating relevant parameters of the GTP tunnel, and the GTP The relevant parameters of the tunnel include the first GTP routing flow table entry and the next hop encapsulation parameter record entry, the first GTP routing flow table entry is the flow table entry used when the Openflow switch of the target extension transmits data, and the first GTP The routing flow table entry includes at least the GPRS Tunneling Protocol data plane version number GTP-U Version, the GPRS Tunneling Protocol data plane tunnel endpoint identifier GTP-U TEID, and the next hop encapsulation parameter record entry is all The flow table entry used when the Openflow switch of the target extension is encapsulated; the relevant parameters of the GTP tunnel are sent to the Openflow switch of the target extension; The Openflow switch of the target extension is used to receive the first GTP routing flow table entry and/or the next-hop encapsulation parameter record entry sent by the Openflow controller; and according to the first GTP routing flow table The entry and the encapsulation parameter of the next hop record entry transfer data. 8. the processing system of GTP tunnel according to claim 7, is characterized in that, The Openflow controller is also used to select the Openflow switch used for the target extension of the GTP tunnel; obtain available network link parameters, and the available network link parameters include at least the Openflow switch corresponding to the target extension IP address, port number; determine the parameters for establishing the GTP tunnel through the available network link parameters, and the parameters for establishing the GTP tunnel include source IP address, destination IP address, and source port number corresponding to the GTP tunnel , purpose port number, GTP-U Version, GTP-U TEID; generate the first GTP routing flow table entry and the next hop encapsulation parameter record entry by the available network link parameters and the parameters for establishing the GTP tunnel. 9. The processing system of the GTP tunnel according to claim 8, wherein the relevant parameters of the GTP tunnel also include a second GTP routing flow table entry, and the second GTP routing flow table entry is a standard Openflow switch transmission The flow table entries used for data, the standard Openflow switches are all standard Openflow switches managed by the Openflow controller; The Openflow controller is also configured to generate the second GTP routing flow table entry through the parameter of establishing the GTP tunnel; send the second GTP routing flow table entry to the standard Openflow switch; The system also includes: a target standard Openflow switch, wherein the target standard Openflow switch is the standard Openflow switch participating in the transmission of data in the GTP tunnel; The Openflow controller is also used to obtain decision result information, the decision result information is used to indicate specific processing of data corresponding to a specific business, and the specific processing is in any of the following forms: Perform data transcoding, perform traffic isolation for the data corresponding to the specific service, send a warning reminder message to the user equipment UE, or perform advertisement video insertion for the data corresponding to the specific service; The corresponding data generates a specific GTP routing flow table entry; and selects a target standard Openflow switch for the GTP tunnel; sends the specific GTP routing flow table entry to the target standard Openflow switch; The target standard Openflow switch is configured to receive the specific GTP routing flow table entry sent by the OPenflow controller. 10. The processing system of the GTP tunnel according to claim 7 or 9, characterized in that, The Openflow controller is also used to receive policy information sent by the policy and charging rule functional unit PCRF; through the available network link parameters and the policy information, generate a first policy GTP routing flow table entry, next hop Encapsulating parameter policy record entries and second policy GTP routing flow table entries, and sending the first policy GTP routing flow table entries and the next hop encapsulation parameter policy record entries to the Openflow switch of the target extension, and sending the The second policy GTP routing flow table entry is sent to the standard Openflow switch; The Openflow switch of the target extension is also used to receive the first policy GTP routing flow table entry and the next-hop encapsulation parameter policy record entry sent by the Openflow controller; The target standard Openflow switch is also used to receive the second strategy GTP routing flow table entry sent by the Openflow controller; The Openflow controller is also used to obtain a request to modify the GTP tunnel; modify the GTP tunnel through the request to modify the GTP tunnel, wherein the request to modify the GTP tunnel includes generating relevant parameters for updating the GTP tunnel, and the relevant parameters for updating the GTP tunnel include the first An updated GTP routing flow table entry, a next hop encapsulation parameter update record entry and a second updated GTP routing flow table entry, the first updated GTP routing flow table entry is the flow used when the target extended Openflow switch transmits data Table entry, the next hop encapsulation parameter update record entry is a flow table entry used when the target extended Openflow switch encapsulates data, and the second updated GTP routing flow table entry is used when the standard Openflow switch transmits data The flow table entry; Send the relevant parameters of the updated GTP tunnel to the Openflow switch of the target extension and the standard Openflow switch; Obtain the delete GTP tunnel request; Delete the corresponding GTP tunnel through the delete GTP tunnel request; Notify The target extended Openflow switch and/or the target standard Openflow switch, so that the target extended Openflow switch and the target standard Openflow switch correspondingly delete parameters corresponding to the GTP tunnel corresponding to the delete GTP tunnel request; The Openflow switch of the target extension is also used to receive the relevant parameters of the updated GTP tunnel sent by the Openflow controller; and transmit data according to the relevant parameters of the updated GTP tunnel; receive the first parameter sent by the Openflow controller A notification to delete the GTP tunnel, wherein the first notification to delete the GTP tunnel includes an identifier to delete the GTP tunnel, and the first notification to delete the GTP tunnel is an Openflow switch indicating the target extension delete the signaling of the GTP tunnel; and delete the GTP tunnel corresponding to the identifier of the deleted GTP tunnel through the first notification of deleting the GTP tunnel; The target standard Openflow switch is also used to receive the relevant parameters of the updated GTP tunnel sent by the Openflow controller; and transmit data according to the relevant parameters of the updated GTP tunnel; receive the second parameter sent by the Openflow controller Delete the notification of the GTP tunnel, wherein, the second notification of deleting the GTP tunnel includes the identifier of the GTP tunnel deletion, and the second notification of deleting the GTP tunnel is to instruct the target standard Openflow switch to delete the GTP tunnel. signaling of the GTP tunnel; and deleting the GTP tunnel corresponding to the identifier of the deleted GTP tunnel through the second notification of deleting the GTP tunnel.

Images