CN103747502B - The processing method and system of a kind of GTP tunnel - Google Patents

Abstract

The present invention discloses the processing method and system of a kind of GTP tunnel, is related to technical field of communication network, and the autgmentability for solving the problems, such as GTP tunnel end points is poor.The embodiment of the present invention is obtained by Openflow controllers sets up GTP tunnel request, and Openflow controllers are the equipment for possessing the chain of command function in GTP tunnel end points；Openflow controllers ask to set up GTP tunnel by setting up GTP tunnel, wherein setting up GTP tunnel request includes generating the relevant parameter of GTP tunnel, and the Openflow interchangers of target extension are the equipment as the data surface function of possessing in GTP tunnel in GTP tunnel end points；The relevant parameter of GTP tunnel is sent to Openflow controllers the Openflow interchangers of target extension.Scheme provided in an embodiment of the present invention is used when being adapted for data transfer.

Description

GTP tunnel processing method and system

Technical Field

The present invention relates to the field of communication network technologies, and in particular, to a method and a system for processing a GTP tunnel.

Background

A General Packet Radio Service tunneling protocol (GTP) is an important protocol of a Mobile Core network (including General Packet Radio Service (GPRS)/Universal Mobile Telecommunications System (UMTS)/Evolved data Core network (EPC)), and is used for a plurality of interfaces of the Mobile Core network. GTP is mainly applied to tunnel management, mobility management, and data transmission. GTP is at the application layer of the protocol stack and includes three variants, the general packet radio service technology tunneling protocol Control plane (GTP Control, GTP-C), the general packet radio service technology tunneling protocol data plane (GTP User, GTP-U), and GTP' (GTP Prime). Wherein, GTP-C is the control part of GTP and is responsible for the establishment, deletion and update of a GTP-U tunnel and the verification of the accessibility of the gateway of the mobile core network. The GTP-U is responsible for carrying data, and finishes overlay transmission of the service data between a pair of tunnel endpoints by encapsulating and decapsulating the service data. GTP' is used to transport charging data between the mobile core network and the charging gateway.

The GTP tunnel needs to complete the encapsulation and decapsulation of the service data at the tunnel start and end points. The tunnel endpoint may be considered an application layer gateway. Existing GTP protocols tend to have GTP-C and GTP-U experience the same nodes, i.e. prior art GTP tunnel endpoints include the functionality 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, the establishment of the GTP tunnel has two segments, one segment is a GTP tunnel between a Radio Network Controller (RNC) and a GPRS service Support Node (SGSN); one segment is a GTP tunnel between the SGSN and the GPRS Support Node (GGSN). User Equipment (UE) sends a Packet Data Protocol context (PDPcontext) activation request to an RNC, the RNC generates a GTP tunnel establishment request carrying an IP address of the SGSN according to the PDP context activation request and sends the GTP tunnel establishment request to the SGSN, after the SGSN receives the GTP tunnel request, on one hand, the SGSN generates and sends the GTP tunnel establishment request carrying the IP address of the GGSN to the GGSN, on the other hand, the RNC feeds back a first GTP tunnel establishment response carrying parameters (such as a GTP tunnel version number, a GTP tunnel identifier and the like) of a GTP tunnel between the RNC and the SGSN; and after receiving the request for establishing the GTP tunnel sent by the SGSN, the GGSN feeds back a second GTP tunnel establishment response to the SGSN through the request for establishing the GTP tunnel, where the second GTP tunnel establishment response carries parameters (such as a GTP tunnel version number, a GTP tunnel identifier, and the like) of the GTP tunnel between the GGSN and the SGSN. After negotiating the parameters of the GTP tunnel between the RNC and the SGSN and negotiating the parameters of the GTP tunnel between the SGSN and the GGSN, the RNC and the SGSN together establish the GTP tunnel between the RNC and the SGSN and the GGSN together establish the GTP tunnel between the SGSN and the GGSN.

However, the GTP tunnel established in the prior art is commonly negotiated and established for the endpoints at both ends of the GTP tunnel. When the existing technology is adopted to establish a GTP tunnel, the endpoints at two ends of the GTP tunnel need to exchange related signaling to jointly negotiate to complete the establishment; when the existing technology is used to modify or delete a GTP tunnel, the endpoints at both ends of the GTP tunnel need to interact with related signaling to jointly negotiate to complete the modification or deletion of the GTP tunnel, thereby increasing the complexity of processing the GTP tunnel.

Disclosure of Invention

Embodiments of the present invention provide a method and a system for processing a GTP tunnel, which are used to solve the problem of reducing the complexity of processing the GTP tunnel.

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

the method comprises the steps that an Openflow controller obtains a GTP tunnel request for establishing a general packet radio service technology tunnel protocol, wherein the Openflow controller is equipment with a control surface function in a GTP tunnel endpoint;

the Openflow controller establishes a GTP tunnel through the establish GTP tunnel request, wherein the request for establishing the GTP tunnel comprises generating relevant parameters of the GTP tunnel, the relevant parameters of the GTP tunnel comprise a first GTP routing flow table entry and a next hop encapsulation parameter record entry, the first GTP routing flow table entry is a flow table entry used when the target extended Openflow switch transfers data, the first GTP routing flow table entry at least comprises a GPRS tunneling protocol data plane Version number GTP-U Version, a GPRS tunneling protocol data plane tunnel endpoint identification GTP-U TEID, the next hop encapsulation parameter record entry is a flow table entry used when the target extended Openflow switch encapsulates data, the target-extended Openflow switch is used as a device in the GTP tunnel with a data plane function in the GTP tunnel endpoint;

and 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.

In another embodiment of the present invention, the Openflow controller, through the GTP tunnel setup request, establishes a GTP tunnel, including:

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

the Openflow controller acquires available network link parameters, wherein the available network link parameters at least comprise an IP address and a port number corresponding to the target-extended Openflow switch;

the Openflow controller determines parameters for establishing the GTP tunnel according to the available network link parameters, wherein the parameters for establishing the GTP tunnel comprise IP addresses at two ends, port numbers at two ends, GTP-UVerson and GTP-U TEID (user equipment identity) corresponding to the GTP tunnel;

and the Openflow controller generates a first GTP routing flow table entry and a next hop encapsulation parameter record entry according to the available network link parameter and the parameter for establishing the GTP tunnel.

In another embodiment of the present invention, the relevant parameters of the GTP tunnel further include a second GTP routing flow table entry, where the second GTP routing flow table entry is a flow table entry used when a standard Openflow switch transmits data, and the standard Openflow switch is all standard Openflow switches managed by the Openflow controller;

after the Openflow controller obtains the available network link parameters of the target-extended Openflow switch, the method further includes:

the Openflow controller generates the second GTP routing flow table entry according to the parameter for establishing the GTP tunnel;

and the Openflow controller sends the second GTP routing flow table entry to a standard Openflow switch, so that the standard Openflow switch can transmit 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 establish GTP tunnel, the method further includes:

the Openflow controller obtains decision result information, wherein the decision result information is used for indicating specific processing to data corresponding to a specific service, and the specific processing is in any one of the following forms: transcoding the data corresponding to the specific service, performing flow isolation on the data corresponding to the specific service, and sending an alert reminding message to User Equipment (UE) or performing advertisement video insertion on 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;

and 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 further comprises:

the Openflow controller receives the policy and charging rule function unit PCRF and sends the policy information to the Openflow controller;

and the Openflow controller generates a first strategy GTP routing flow table entry, a next hop encapsulation parameter strategy recording entry and a second strategy GTP routing flow table entry according to the available network link parameters and the strategy information.

In another embodiment of the present invention, the method further comprises:

the Openflow controller acquires a GTP tunnel modification request; modifying a GTP tunnel through the GTP tunnel modification request, wherein the GTP tunnel modification request comprises generation of relevant parameters for updating the GTP tunnel, the relevant parameters for updating the GTP tunnel comprise a first GTP routing flow table updating entry, a next hop encapsulation parameter updating record entry and a second GTP routing flow table updating entry, the first GTP routing flow table updating entry is a flow table entry used when the target extended Openflow switch transmits data, the next hop encapsulation parameter updating record entry is a flow table entry used when the target extended Openflow switch encapsulates data, and the second GTP routing flow table updating entry is a flow table entry used when a standard Openflow switch transmits data; correspondingly sending the relevant parameters of the updated GTP tunnel to the target-extended Openflow switch and the standard Openflow switch; or,

the Openflow controller acquires a GTP tunnel deletion request, wherein the GTP tunnel deletion request comprises an identifier indicating deletion of a GTP tunnel; deleting the corresponding GTP tunnel through the identification for deleting the GTP tunnel; and notifying 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 parameters corresponding to the GTP tunnel deletion request.

On the other hand, an embodiment of the present invention provides a system for processing a GTP tunnel, where the system includes an Openflow controller and a target-extended Openflow switch, where the Openflow controller is a device having a control plane function in a GTP tunnel endpoint, and the target-extended Openflow switch is a device having a data plane function in the GTP tunnel endpoint in the GTP tunnel, and the system includes:

the Openflow controller is used for acquiring a request for establishing a general packet radio service technology tunnel protocol (GTP) tunnel; establishing a GTP tunnel through the GTP tunnel establishing request, wherein the GTP tunnel establishing request comprises relevant parameters for generating the GTP tunnel, the relevant parameters of the GTP tunnel comprise a first GTP routing flow table entry and a next hop encapsulation parameter recording entry, the first 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 at least comprises a general packet radio service technology (GPRS) tunnel protocol data plane Version number GTP-U Version, a GPRS tunnel protocol data plane tunnel endpoint identification (GTP-U TEID), and the next hop encapsulation parameter recording entry is a flow table entry used when the target extended Openflow switch encapsulates data; sending the relevant parameters of the GTP tunnel to an Openflow switch of target expansion;

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

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; acquiring available network link parameters, wherein the available network link parameters at least comprise an IP address and a port number corresponding to the target-extended Openflow switch; determining parameters for establishing the GTP tunnel according to the available network link parameters, wherein the parameters for establishing the GTP tunnel comprise a source IP address, a destination IP address, a source port number, a destination port number, a GTP-U Version and a GTP-U TEID corresponding to the GTP tunnel; and generating a first GTP routing flow table entry and a next hop encapsulation parameter record entry according to 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 further include a second GTP routing flow table entry, where the second GTP routing flow table entry is a flow table entry used when a standard Openflow switch transmits data, and the standard Openflow switch is all standard Openflow switches managed by the Openflow controller;

the Openflow controller is further configured to generate the second GTP routing flow table entry according to the parameter for establishing the GTP tunnel; sending the second GTP routing flow table entry to the standard Openflow switch;

the system further comprises: a target standard Openflow switch, wherein the target standard Openflow switch is the standard Openflow switch participating in transmission of data in the GTP tunnel;

the Openflow controller is further configured to acquire decision result information, where the decision result information is used to instruct to perform specific processing on data corresponding to a specific service, where the specific processing is in any one of the following forms: transcoding the data corresponding to the specific service, performing flow isolation on the data corresponding to the specific service, and sending an alert reminding message to User Equipment (UE) or performing advertisement video insertion on the data corresponding to the specific service; generating a specific GTP routing flow table entry for the data corresponding to the specific service according to the decision result information; selecting a target standard Openflow switch for the GTP tunnel; sending the specific GTP routing flow table entry to the target standard Openflow switch;

and the target standard Openflow switch is used for receiving 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 policy information sent by a policy and charging rule function unit PCRF; generating 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 according to the available network link parameters and the policy information, sending the first policy GTP routing flow table entry and the next hop encapsulation parameter policy record entry to the target-extended Openflow switch, and sending the second policy GTP routing flow table entry to the standard Openflow switch;

the target-extended Openflow switch is further configured 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 further configured to receive the second policy GTP routing flow table entry sent by the Openflow controller;

the Openflow controller is further configured to acquire a GTP tunnel modification request; modifying a GTP tunnel through the GTP tunnel modification request, wherein the GTP tunnel modification request comprises generation of relevant parameters for updating the GTP tunnel, the relevant parameters for updating the GTP tunnel comprise a first GTP routing flow table updating entry, a next hop encapsulation parameter updating record entry and a second GTP routing flow table updating entry, the first GTP routing flow table updating entry is a flow table entry used when the target extended Openflow switch transmits data, the next hop encapsulation parameter updating record entry is a flow table entry used when the target extended Openflow switch encapsulates data, and the second GTP routing flow table updating entry is a flow table entry used when a standard Openflow switch transmits data; sending the relevant parameters for updating the GTP tunnel to the target-extended Openflow switch and the standard Openflow switch; acquiring a GTP tunnel deletion request; deleting the corresponding GTP tunnel according to the GTP tunnel deletion request; notifying 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 parameters corresponding to the GTP tunnel deletion request;

the target-extended Openflow switch is further configured to receive the relevant parameters of the updated GTP tunnel sent by the Openflow controller; transmitting data according to the relevant parameters of the updated GTP tunnel; receiving a first GTP tunnel deletion notification sent by the Openflow controller, wherein the first GTP tunnel deletion notification includes a GTP tunnel deletion identifier, and the first GTP tunnel deletion notification is a signaling indicating that the target extended Openflow switch deletes the GTP tunnel; deleting the GTP tunnel corresponding to the identifier of the deleted GTP tunnel through the first notification for deleting the GTP tunnel;

the target standard Openflow switch is further configured to receive the relevant parameters of the updated GTP tunnel sent by the Openflow controller; transmitting data according to the relevant parameters of the updated GTP tunnel; receiving a second GTP tunnel deletion notification sent by the Openflow controller, where the second GTP tunnel deletion notification includes a GTP tunnel deletion identifier, and the second GTP tunnel deletion notification is a signaling that indicates the target standard Openflow switch to delete the GTP tunnel; and deleting the GTP tunnel corresponding to the identifier of the deleted GTP tunnel through the notification of deleting the GTP tunnel by the second step.

In the GTP tunnel processing method and system provided in the embodiments of the present invention, an Openflow controller is used to obtain a GTP tunnel request for establishing a gprs tunneling protocol, where the Openflow controller is a device having a control plane function in a GTP tunnel endpoint; the Openflow controller establishes a GTP tunnel through a GTP tunnel establishment request, wherein the GTP tunnel establishment request comprises relevant parameters for generating the GTP tunnel, the relevant parameters of the GTP tunnel comprise a first GTP routing flow table entry and a next hop encapsulation parameter recording entry, the first GTP routing flow table entry is a flow table entry used when a target expanded Openflow switch transmits data, the first GTP routing flow table entry at least comprises a general packet radio service technology (GPRS) tunnel protocol data plane Version number GTP-U Version, a GPRS tunnel protocol data plane tunnel endpoint identifier (GTP-UTEID), the next hop encapsulation parameter recording entry is a flow table entry used when the target expanded Openflow switch encapsulates data, and the target expanded Openflow switch is a device with a data plane function in a GTP tunnel endpoint in the GTP tunnel; and 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 prior art that GTP tunnel endpoints usually bear the functions of building, modifying, deleting and routing forwarding of a GTP tunnel, so that when the GTP tunnel is built, modified and deleted, two end point devices corresponding to the GTP tunnel to be processed need to jointly negotiate to complete the processing of the GTP tunnel to be processed, thereby increasing the complexity of processing the GTP tunnel, the control plane and the forwarding plane of the GTP tunnel endpoint are separated to obtain an Openflow controller and an extended Openflow switch.

Drawings

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to these drawings without creative efforts.

Fig. 1 is a diagram illustrating a GTP protocol control plane and data plane separation architecture based on Openflow according to an embodiment of the present invention;

fig. 2 is a schematic diagram of a flow table entry field for extending an Openflow protocol in the GTP tunnel processing method provided in the embodiment of the present invention;

fig. 3 is a flowchart of a GTP tunnel processing method according to an embodiment of the present invention;

fig. 4 is a flowchart of another method for an Openflow controller to establish a GTP tunnel in the GTP tunnel processing method provided in the embodiment of the present invention;

fig. 5 is a field schematic diagram of a first GTP routing flow table entry in the GTP tunnel processing method according to the embodiment of the present invention;

fig. 6 is a field schematic diagram of a next hop encapsulation parameter record entry in the GTP tunnel processing method according to the embodiment of the present invention;

fig. 7 is a field schematic diagram of a second GTP routing flow table entry in the GTP tunnel processing method according to the embodiment of the present invention;

fig. 8 is a flowchart of another GTP tunnel processing method according to an embodiment of the present invention;

fig. 9 is a flowchart of another GTP tunnel processing method according to an embodiment of the present invention;

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

fig. 10(b) is a flowchart of a method for processing a GTP tunnel based on an EPC network according to an embodiment of the present invention;

fig. 10(c) is a flowchart of another GTP tunnel processing method based on the EPC network according to the embodiment of the present invention;

fig. 11 is a flowchart of a method for processing another GTP tunnel based on the EPC network according to the embodiment of the present invention;

fig. 12(a) is an architecture diagram of a GTP tunnel endpoint control plane and a data plane separated in a 2G/3G network according to the GTP tunnel processing method provided in the embodiment of the present invention;

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

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

fig. 14 is a schematic structural diagram of a GTP tunnel processing system according to an embodiment of the present invention;

fig. 15 is a schematic structural diagram of another GTP tunnel processing system according to an embodiment of the present invention.

Detailed Description

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

Fig. 1 is a diagram of Openflow-based GTP protocol control plane and data plane separation architecture, in fig. 1,

the GTP function node 110 is a conventional GTP function node integrating a control plane and a data plane, where 102 is a control plane function module and 101 is a data plane function module. 101, according to standard GTP-U protocol, completing the encapsulation and decapsulation operations of service data and packet forwarding. 102 is responsible for the establishment of GTP tunnels. 102, in the process of establishing a tunnel, when negotiating with a GTP function node integrated with other control plane and data plane, a standard GTP-C protocol needs to be used, and when negotiating with a GTP control plane function node (pure GTP-C function node) 103, the standard GTP-C protocol may be used for negotiation, or other protocols may be used for negotiation, such as NAS signaling.

103 is an independently arranged GTP control function node. 103 correspond to one or more specific GTP-U data forwarding function nodes, e.g. 106. 103 negotiate a setup procedure for the GTP-U tunnel via 106. 103 may be integrated with other network functions.

105 and 106 are independently arranged GTP forwarding function nodes for encapsulating and decapsulating service data. 105 and 106 are extended OpenFlow switches that comply with the standard OpenFlow protocol, while being able to match the TEID and version of GTP-U and route packets accordingly. The extended OpenFlow controller can issue flow table entries (first GTP routing flow table entries and next hop encapsulation parameter record entries) including GTP protocol parameters to 105 and 106. 105 and 106 are connected to 104 via a secure channel. 105, and 106 may also forward data as standard Openflow switches.

104 is a fusion node of a GTP-C function and an Openflow controller, and is an Openflow controller. And after receiving the GTP tunnel establishment, modification and deletion request sent by 103 or receiving the GTP tunnel establishment, modification and deletion request sent by 108, the GTP tunnel establishment, modification and deletion are completed by 104. And meanwhile, 104 sends the relevant parameters of the GTP tunnel to the expanded OpenFlow switches 105 and 106 in the form of OpenFlow flow table entries, so as to complete the establishment of the GTP tunnel data plane route. 104 may issue GTP tunnel routes (first GTP route flow table entries and next hop encapsulation parameter record entries) only to 105 and 106, or may issue Openflow flow table entries (second GTP route flow table entries) to one or more standard Openflow switches 107 at the same time. 104 may issue only OpenFlow flow table entries to 107.

108 is a Policy and Charging Rules Function (PCRF) or a fine traffic data flow Policy control Function node. 108 may trigger 104 the establishment, modification, or deletion of GTP tunnels and different underlying routing paths based on user service attributes, such as audio, video, intranet, extranet, high definition, transcoding required, etc. 108 may also require 104 the establishment of a particular transmission route based on user attributes, such as roaming users, in-network user interworking, gold medal and silver medal users, operating system version, etc.

108 and 104 can be independently arranged or the functions can be combined as required.

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 architecture in which the GTP protocol control plane is separated from the data plane, network elements such as 103, 104, 108, and 109 may be deployed in the same network as the GTP forwarding function node, or may be deployed in a network different from the GTP forwarding function node. 103. 104, 108 and 109 may be installed directly on the hardware platform or may be installed on a general-purpose platform in the form of a virtual machine. 103. 104, 108 and 109 can be deployed separately or centrally to a data center as desired. The embodiment is not limited.

In the architecture of separating the GTP control plane from the data plane, the control plane interface has complete backward compatibility, and can ensure the intercommunication with the traditional network and the intercommunication in the roaming scene.

Referring to fig. 1, it can be seen that the Openflow protocol is used to separate the control plane and the forwarding plane of the GTP tunnel endpoint; correspondingly, an Openflow controller and an extended Openflow switch are obtained, the Openflow controller is used for establishing a GTP tunnel, modifying the GTP tunnel and deleting the GTP tunnel, and the extended Openflow switch is used for transmitting data through the GTP tunnel established by the Openflow controller.

Specifically, an Openflow protocol is adopted to logically separate the GTP-C and GTP-U functions of a GTP tunnel endpoint, and to set and separate the GTP-C and GTP-U functional network elements of the GTP tunnel endpoint. After the control plane and the forwarding plane of the GTP tunnel endpoint are separated by using the Openflow protocol, a GTP control function network element (i.e., an Openflow controller) is responsible for GTP tunnel establishment, modification, and deletion, and a GTP forwarding function network element (i.e., an extended Openflow switch) is responsible for GTP packet forwarding. Wherein the extended Openflow switch further comprises encapsulation and decapsulation operations for GTP data packets.

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

The method comprises the steps that the control surface and the forwarding surface of a general packet radio service technology tunnel protocol GTP tunnel endpoint are separated by adopting an Openflow protocol to obtain an Openflow controller and an expanded Openflow switch; the Openflow controller is used for establishing a GTP tunnel, modifying the GTP tunnel and deleting the GTP tunnel, and the extended Openflow switch is used for transmitting data through the GTP tunnel established by the Openflow controller. By adopting 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 forwarding of GTP-U packets (types of service data), fig. 2 shows an extension of the Openflow protocol, so that the Openflow protocol supports GTP-U Version number Version and GTP-U Tunnel Endpoint Identifier (TEID) in the flow table entry matching field. Openflow switches that support GTP-U TEID forwarding need to be able to match 3-bit GTP-U Version and 32-bit GTP-U TEID.

In fig. 2, an ingress port 201, a source MAC address 202, a destination MAC address 203, a virtual local area network identifier 204, a multi-protocol label switching label 205, a multi-protocol label switching Traffic Class 206 (Traffic Class, TC), a source IP address 207, a destination IP address 208, a transmission control protocol/service data packet protocol/flow control transmission protocol source port number 209, a transmission control protocol/service data packet protocol/flow control transmission protocol destination port number 210 are all matching fields existing in the Openflow protocol in the prior art, and tunnel end points 211GTP-U version number and 212GTP-U are extended matching fields.

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

Fig. 3 illustrates a GTP tunnel processing method, which is as follows:

301, the Openflow controller obtains a GTP tunnel establishment request, and the Openflow controller is a device having a control plane function in a GTP tunnel endpoint.

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

For example, 2G/3G is taken as an example for explanation, there may be two ways for the Openflow controller to obtain the GTP tunnel establishment request.

The first mode is as follows: the Openflow controller obtains a GTP tunnel establishment process initiated by User Equipment (UE), where the UE sends an attach request to a base station, the base station sends the attach request to an MME, the MME generates a GTP tunnel establishment request through the attach request, sends the GTP tunnel establishment request to an 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 for triggering the Openflow controller to generate a GTP tunnel establishment request.

302, the Openflow controller requests establishment of a GTP tunnel by establishing a GTP tunnel, the method comprises the steps of establishing a GTP tunnel request, wherein the GTP tunnel request comprises relevant parameters for generating a GTP tunnel, the relevant parameters of the GTP tunnel comprise a first GTP routing flow table entry and a next hop encapsulation parameter recording entry, the first GTP routing flow table entry is a flow table entry used when a target expanded Openflow switch transmits data, the first GTP routing flow table entry at least comprises a general packet radio service technology tunnel protocol data plane Version number GTP-U Version, a general packet radio service technology tunnel protocol data plane tunnel endpoint identification GTP-U TEID, the next hop encapsulation parameter recording entry is a flow table entry used when the target expanded Openflow switch encapsulates data, and a source GTP tunnel endpoint and a target GTP tunnel endpoint are target expanded Openflow switches with data plane functions in the GTP tunnel endpoints.

Firstly, an Openflow controller needs to select an Openflow switch for expanding a target of a GTP tunnel; and then the Openflow controller acquires available network link parameters, wherein the available network link parameters at least comprise IP addresses and port numbers corresponding to the Openflow switch of the target extension. The Openflow controller determines parameters for building the GTP tunnel according to the available network link parameters, wherein the parameters for building the GTP tunnel comprise IP addresses at two ends, port numbers at two ends, GTP-U Version and GTP-U TEID corresponding to the GTP tunnel; and generating a first GTP routing flow table entry and a next hop encapsulation parameter record entry through the available network link parameters and the parameters for establishing the GTP tunnel.

Specifically, the Openflow controller first selects the end points at both ends for each GTP tunnel. Taking 2G/3G as an example, the Openflow controller needs to establish two GTP tunnels, one between the RNC and the SGSN and one between the SGSN and the GGSN. The Openflow controller fuses control planes on the SGSN and the GGSN, so that the Openflow controller selects one of SGSN-data (SGSN only with a data plane) and GGSN-data (GGSN only with the data plane) as an Openflow switch of the target extension. Then the Openflow controller obtains available network link parameters, wherein the available network link parameters at least comprise IP addresses, port numbers, GTP-U Version and GTP-U TEID corresponding to the SGSN-data and the GGSN-data; and generating a first GTP routing flow table entry and a next hop encapsulation parameter record entry through the available network link parameters and the parameters for establishing the GTP tunnel.

It should be noted that, because the control plane of the RNC is not fused 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 together for establishment; the control surfaces of the SGSN and the GGSN are fused into the Openflow controller, and when the Openflow controller establishes the GTP tunnel between the SGSN and the GGSN, the Openflow controller only needs to acquire relevant information (available network link parameters, parameters for establishing the GTP tunnel and the like) for establishing the GTP tunnel by itself to independently complete the establishment of the GTP tunnel between the SGSN and the GGSN.

The fields of the first GTP routing flow table entry may refer to fig. 5. From fig. 5, it can be seen that the first GTP routing flow table entry should include at least 501 the source IP address, 502 the destination IP address, 503 the source port number, 504 the destination port number, 505 the GTP-U version number, and 506 the GTP-U tunnel endpoint identification.

The fields of the next hop encapsulation parameter record entry may refer to fig. 6. From the description of fig. 6, it can be seen that the next-hop encapsulation parameter record entry includes 601 the hashed HashID identification, 602 the source IP address, 603 the destination IP address, 604 the source port number, 605 the destination port number, and 606 the GTP-U TEID used by the next-hop tunnel. And the Hash ID is used for the Openflow switch of the target extension to retrieve the TEID used by the next hop tunnel according to the received GTP-U data packet header information.

303, the Openflow controller sends the relevant parameter 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 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 the SGSN may include: a source IP address (IP address of RNC), a destination IP address (IP address of SGSN), a source port number (port number of RNC), a destination port number (port number of SGSN), a GTP-U version number, and a GTP-U tunnel endpoint identification. The first GTP routing flow table entry sent to the GGSN may include: a source IP address (IP address of SGSN), a destination IP address (IP address of GGSN), a source port number (port number of SGSN), a destination port number (port number of GGSN), a GTP-U version number and a GTP-U tunnel endpoint identification. The Openflow controller sends the relevant next hop encapsulation parameter record entry to the source GTP endpoint, such as the SGSN, in the next GTP tunnel. The next hop encapsulation parameter record entry sent to the SGSN may include a Hash ID, a source IP address (IP address of SGSN), a destination IP address (IP address of GGSN), a source port number (port number of SGSN), a destination port number (port number of GGSN), and a GTP-U TEID used by the next hop tunnel (GTP tunnel identifier between SGSN and GGSN). Vice versa, and will not be described in detail herein.

It can be understood that the target-extended Openflow switch uses the first GTP routing flow table entry to transmit the packet, and uses the next hop encapsulation parameter record entry to complete the encapsulation of the packet. Specifically, when any one Openflow switch with an extended target receives a data packet, a GTP protocol is used to decapsulate the data packet to obtain packet header information of the data packet, the packet header information is matched with a first GTP routing flow table entry stored locally to obtain a first GTP routing flow table entry matched with the packet header information, and a next operation on the data packet is obtained through operation information (Action) in the matched first GTP routing flow table entry. And when the next step of operation is to send the packet to the next port and to encapsulate the packet by using a GTP protocol (which can be regarded as information for continuously transmitting data through a GTP tunnel, which indicates that the target-extended Openflow switch needs to continuously transmit data through the next GTP tunnel), matching the packet header information of the target-extended Openflow switch with the Hash ID in the next hop encapsulation parameter record entry to obtain a next hop encapsulation parameter record entry matched with the packet header information, and then encapsulating the decapsulated packet again according to the information in the matched next hop encapsulation parameter record entry. And after the encapsulation, continuing to send down the data according to the operation information in the first GTP routing flow table entry.

The control surface and the forwarding surface of the GTP tunnel endpoint are separated to obtain the Openflow controller and the extended Openflow switch, the Openflow controller in the invention can be used for establishing the GTP tunnels among the GTP tunnel endpoints, and the GTP tunnels established by the Openflow controller are convenient for the Openflow controller to complete the modification or deletion of the previously established GTP tunnels, so that the complexity of GTP tunnel processing is reduced.

Corresponding to the description in step 302, optionally, the Openflow controller may receive the policy information sent by the 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 through the available network link parameters and the policy information. And the corresponding Openflow controller sends the first strategy GTP routing flow table entry and the next hop encapsulation parameter strategy recording entry to the Openflow switch with the expanded target, and sends the second strategy GTP routing flow table entry to the standard Openflow switch.

Optionally, the Openflow controller is further configured to generate a second GTP routing flow table entry according to the parameter for establishing the GTP tunnel, and send the second GTP routing flow table entry to the standard Openflow switch (the standard Openflow switch may transmit a GTP data packet through the second GTP routing flow table entry issued by the Openflow controller, and it is not necessary to perform operations such as encapsulation or decapsulation on the GTP data packet using a GTP protocol), where the second GTP routing flow table entry is a flow table entry used when the standard Openflow switch transmits data. A standard Openflow switch is all Openflow switches managed by an Openflow controller. It can be seen that the Openflow controller sends the generated second GTP routing flow table entry to all the standard Openflow switches managed. And whenever the target standard Openflow switch identifies the second GTP routing flow table entry corresponding to the received packet, matching the information (such as the destination IP address) in the packet header information with all the second GTP routing flow table entries stored locally, so as to obtain the corresponding second GTP routing flow table entry.

Specifically, the field format of the second GTP routing flow table entry may refer to fig. 7. As described in fig. 7, it can be seen that the second GTP routing flow table entry includes one or more of: 701 a source IP address, 702 a destination IP address, 703 a source port number, and 704 a 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 obtains the GTP tunnel establishment request, the method further includes:

304, the Openflow controller obtains the decision result information.

The decision result information is used for explaining that data corresponding to a specific service is subjected to specific processing, and the specific processing includes, but is not limited to, any one of the following forms: transcoding data corresponding to a specific service, performing traffic isolation on the data corresponding to the specific service, sending a warning reminder message to User Equipment (UE) or performing advertisement video insertion on the data corresponding to the specific service, and the like.

The Openflow controller may obtain the decision result information in two ways:

in a first manner, the Openflow controller receives decision result information sent by the PCRF.

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

305, the Openflow controller generates a specific GTP routing flow table entry for the 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, where the location of the network middleware is inside GSM, UMTS, or EPC, the deployment mode may be independent host deployment or cloud center deployment, and the function of the specific GTP routing flow table entry completes processing and operation on the service data in the GTP-U tunnel in the core network, such as transcoding the user voice and video data before entering the terminal, and inserting a specific message presentation form before the service data, including but not limited to advertisement content or reminder, alert content, etc. provided by an operator or a third party.

The network middleware may be a transcoding server, media insertion, firewall, DPI, etc.

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

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

It will be appreciated that the Openflow controller sends a specific GTP routing flow table entry to all target standard Openflow switches selected.

The function of the specific GTP routing flow table entry is the same as that of the second GTP routing flow table entry, and the included fields are also the same, except that the specific GTP routing flow table entry has a higher priority than the flow table entry of the second GTP routing flow table entry, for example, when a certain target standard Openflow switch locally stores the specific GTP routing flow table entry and the second GTP routing flow table entry with the same matching strength, the target standard Openflow switch transmits data by using the specific GTP routing flow table entry with the higher priority of the flow table entry.

As shown in fig. 8, in another embodiment of the present invention, the present invention further provides a GTP tunnel processing method, which includes:

the Openflow controller obtains a modify GTP tunnel request 801.

The manner of acquiring the GTP tunnel modification request by the Openflow controller is the same as the manner of acquiring the GTP tunnel establishment request, which is not described herein again.

The Openflow controller re-establishes the GTP tunnel by modifying the GTP tunnel request 802.

And the related parameters for updating the GTP tunnel comprise a first 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 a flow table entry used when the target-extended Openflow switch transmits data, the next hop encapsulation parameter update record entry is a flow table entry used when the target-extended Openflow switch transmits data, and the second updated GTP routing flow table entry is a flow table entry used when the target-standard Openflow switch transmits data.

The reestablishing of the GTP tunnel by the Openflow controller by modifying the GTP tunnel request specifically includes: and the Openflow controller acquires the updated available network link parameters, wherein the updated available network link parameters at least comprise updated IP addresses and port numbers corresponding to the Openflow switch of the target extension. The Openflow controller determines parameters for reestablishing a GTP tunnel according to the updated available network link parameters, the parameters for reestablishing the GTP tunnel comprise IP addresses at two ends, port numbers at two ends, GTP-U Version and GTP-U TEID corresponding to the GTP tunnel, and then a first updated GTP routing flow table entry and a next hop encapsulation parameter update record entry are generated according to the updated available network link parameters and the parameters for reestablishing the GTP tunnel, the first updated GTP routing flow table entry is a flow table entry used when the expanded Openflow switch transmits data, and the next hop encapsulation parameter update record entry comprises an updated Hash ID, an updated source IP address, an updated destination IP address, an updated source port number, an updated destination port number and an 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 the standard Openflow switch transmits data. And after the Openflow controller acquires the updated available network link parameters and generates the parameters for reestablishing the GTP tunnel, the Openflow controller generates a second updated GTP routing flow table entry according to the available network link parameters and the parameters for generating the reestablishing the GTP tunnel.

It should be noted that, as 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. 7, which are not described in detail herein.

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

And 803, the Openflow controller sends the relevant parameters for updating the 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.

And 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 control surface and the forwarding surface of the GTP tunnel endpoint are separated to obtain the Openflow controller and the extended Openflow switch, the Openflow controller in the invention can be used for establishing the GTP tunnels among the GTP tunnel endpoints, and the GTP tunnels established by the Openflow controller are convenient for the Openflow controller to complete the modification or deletion of the previously established GTP tunnels, so that the complexity of GTP tunnel processing is reduced.

As shown in fig. 9, in another embodiment of the present invention, the present invention further provides a GTP tunnel processing method, which includes:

and 901, the Openflow controller acquires a GTP tunnel deleting request, where the GTP tunnel deleting request includes an identifier indicating deleting a GTP tunnel.

The specific format of the indication to delete the identity of the GTP tunnel is not limited in this step.

The manner of acquiring the GTP tunnel deletion request by the Openflow controller is the same as the manner of acquiring the GTP tunnel establishment request, which is not described herein again.

The Openflow controller requests to delete the corresponding GTP tunnel through the GTP tunnel deletion 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 parameters corresponding to the GTP tunnel deletion request.

The target-expanded Openflow switch deletes a first GTP routing flow table entry and a next hop encapsulation parameter policy record entry, and the target standard Openflow switch deletes a second GTP routing flow table entry.

The control surface and the forwarding surface of the GTP tunnel endpoint are separated to obtain the Openflow controller and the extended Openflow switch, the Openflow controller in the invention can be used for establishing the GTP tunnels among the GTP tunnel endpoints, and the GTP tunnels established by the Openflow controller are convenient for the Openflow controller to complete the modification or deletion of the previously established GTP tunnels, so that the complexity of GTP tunnel processing is reduced.

In another embodiment of the present invention, the present invention provides a method for transmitting data based on Openflow, where it is to be noted that the method is based on an EPC network. Fig. 10(a) is an architecture diagram of a GTP tunnel endpoint control plane separated from a data plane in an EPC network. Fig. 10(b) is a method for processing a GTP tunnel in an EPC network, where in one form of the method, a UE initiates a GTP tunnel establishment, modification, and deletion process, where the establishment process is only described here, and a specific flow 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.

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

In 1003, the MME generates a GTP tunnel setup request according to the content in the attach request, and sends the GTP tunnel setup request to the S-GW.

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

Here, in this step, referring to the S-GW (GTP tunnel endpoint) in fig. 10(a), the control plane and the data plane are not separated, and here, the S-GW has the same function as the related art, that is, has both the control function and the forwarding function.

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

And the Openflow controller selects the used target expansion Openflow switch as an exit terminal node of the GTP tunnel, and sends the negotiated GTP parameters including a source IP address, a destination IP address, source and destination port numbers and the TEID to the S-GW.

1006, the GTP parameters used by the S-GW and the base station are transmitted by 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.

Here, in this step, referring to the S-GW (GTP tunnel endpoint) in fig. 10(a), the control plane and the data plane are not separated, and here, the S-GW has the same function as in the related art. As another embodiment of the present invention, the control plane and data plane of the S-GW can be separated, where S-GW-data (data plane with only S-GW) is the target extended Openflow switch.

Since here the control plane and forwarding plane of the S-GW are not yet separated, the GTP tunnel between the S-GW and the base station is established by their own negotiation. If the control plane of the S-GW is separated from the forwarding gateway and the control plane of the S-GW is fused to the Openflow controller, the Openflow controller negotiates a GTP tunnel between the S-GW and the base station with the base station.

It should be noted that, in this embodiment, step 1005 may be executed first, and then step 1006 may be executed; alternatively, step 1005 and step 1006 may be performed simultaneously. For convenience of description, step 1005 is first performed and then step 1006 is performed in fig. 10 (b).

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

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

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

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

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

Fig. 10(c) shows a GTP tunnel processing method, where the PCRF initiates the GTP tunnel establishment, modification, and deletion processes, where the establishment process is only described here, and the specific flow is as follows:

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

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

Specifically, the Openflow controller selects an Openflow switch for target expansion of a GTP tunnel, and simultaneously sends a source and destination IP address, source and destination port number, and a tunnel identifier TEID used by the GTP tunnel to the S-GW.

1003', 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 issues a first GTP routing flow table entry and a next hop encapsulation parameter recording entry to the target-extended Openflow switch.

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

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

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

Based on the methods described in fig. 10(b) and fig. 10(c), as shown in fig. 11, the present invention further provides another GTP tunnel processing method, which specifically includes the following steps:

1101, after establishing a GTP tunnel between the S-GW and the base station, the base station transmits the user data request information to the S-GW.

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

1103, the application server sends the service data a to the Openflow switch of the target extension according to the user data request information.

And 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 recording entry to obtain service data B, and then forwards the service data B to the second target standard Openflow switch.

Specifically, the Openflow switch with the expanded target decapsulates the service data a using a GTP protocol to obtain service data a 'and header information of the service data a, obtains a first GTP routing flow table entry and a next hop encapsulation parameter recording entry corresponding to the service data a through the header information, encapsulates the service data a' using the GTP protocol through the next hop encapsulation parameter recording entry to obtain service data B, and transmits the service data B through 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.

The step is an optional step, and when the service data a is video data or a section of advertisement or traffic warning needs to be inserted before the user watches the service data a, the second target standard Openflow switch sends the service data a to the network middleware according to a second GTP routing flow table entry issued by the Openflow controller.

It can be understood that, the second target standard Openflow switch matches one second GTP routing flow table entry and the specific GTP routing flow table entry with the same matching strength according to the packet header information of the service data B, and then the second target standard Openflow switch transmits the service data B by using the specific GTP routing flow table entry with the higher priority of the flow table entry.

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 service data a.

And 1108, the first target standard Openflow switch sends the service data a to the S-GW.

1109, the S-GW carries out GTP protocol encapsulation on the service data A to obtain 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 the service data a to the UE.

The control surface and the forwarding surface of the GTP tunnel endpoint are separated to obtain the Openflow controller and the extended Openflow switch, the Openflow controller in the invention can be used for establishing the GTP tunnels among the GTP tunnel endpoints, and the later Openflow controller can conveniently modify or delete the previously established GTP tunnels through the GTP tunnels established by the Openflow controller, so that the complexity of GTP tunnel processing is reduced; and the Openflow controller can plan the service data in advance, so that some specific information is added to the GTP data packet in the transmission process, thereby increasing the additional information of the service data and improving the adjustment capability of the service data transmission path.

As another embodiment of the present invention, a GTP tunnel processing method of fig. 10 (b)/fig. 10(c) and fig. 11 may be included. The method can refer to the descriptions in fig. (b)/fig. 10(c) and fig. 11, and the description thereof is omitted here.

In another embodiment of the present invention, the present invention provides a method for transmitting data based on Openflow, where it is to be noted that the method is based on a 2G/3G network. Fig. 12(a) is an architecture diagram of the GTP tunnel endpoint control plane separated from the data plane in the 2G/3G network. Fig. 12(b) is a method for processing a GTP tunnel in a 2G/3G network, where one form of the method is that a UE initiates a GTP tunnel establishment, modification, and deletion process, and here, only the establishment process is described, and a specific flow is as follows:

1201, the UE sends a Packet Data Protocol context (PDP context) activation request to a Radio Network Controller (RNC), and the RNC sends the PDP context activation request to the Openflow Controller.

1202, the Openflow controller selects a corresponding Openflow switch of the target extension for establishing the GTP tunnel through the PDP context activation request.

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

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

1203, the Openflow controller obtains the available network link parameters, determines the parameters for establishing the GTP tunnel, and then establishes the GTP tunnel.

Specifically, the Openflow controller establishes a GTP tunnel between SGSN-data and GGSN-data according to the negotiation of a source IP address, a destination IP address, a source port number, a destination port number and a TEID of an available GTP tunnel maintained by the control plane of the 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, the source port number and the destination port number, and the TEID maintained by the SGSN control plane.

And 1204, the Openflow controller sends the corresponding first GTP routing flow table entry and next hop encapsulation parameter record entry to the Openflow switch of the target extension.

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

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

And 1206, the Openflow controller acquires the decision result information and generates a specific GTP routing flow table entry.

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

Based on the method described in fig. 12(b), as shown in fig. 13, the present invention further provides another GTP tunnel processing method, which specifically includes the following steps:

1301, after the Openflow controller establishes the GTP tunnel, the RNC sends the user data request information to the Openflow switch of the first target extension.

It is understood that the Openflow switch of the first target extension 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.

And 1303, the application server sends the service data a to the Openflow switch of the second target extension according to the user data request information.

It is understood that the Openflow switch of the second target extension in this step may be GGSN-data.

And 1304, the second target-extended Openflow switch performs GTP protocol encapsulation on the service data a according to 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.

And the service data B is the service data A encapsulated by adopting a GTP-U protocol.

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

The step is an optional step, and when the service data a is video data or a section of advertisement or traffic warning needs to be inserted before the user watches the service data a, the second target standard Openflow switch sends the service data a to the network middleware according to a second GTP routing flow table entry issued by the Openflow controller.

And 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, and decapsulates the service data B to obtain the service data a.

1308, the first target standard Openflow switch sends the service data a to the Openflow switch extended by the first target.

1309, the Openflow switch expanded by the first target performs GTP protocol encapsulation on the service data a to obtain service data B ', and sends the service data B' to the RNC.

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

The control surface and the forwarding surface of the GTP tunnel endpoint are separated to obtain the Openflow controller and the extended Openflow switch, the Openflow controller in the invention can be used for establishing the GTP tunnels among the GTP tunnel endpoints, and the later Openflow controller can conveniently modify or delete the previously established GTP tunnels through the GTP tunnels established by the Openflow controller, so that the complexity of GTP tunnel processing is reduced; and the Openflow controller can plan the service data in advance, so that some specific information is added to the GTP data packet in the transmission process, thereby increasing the additional information of the service data and improving the adjustment capability of the service data transmission path.

It should be noted that, as another embodiment of the present invention, a GTP tunnel processing method of fig. 12(b) and fig. 13 may be included. The method can refer to the descriptions in fig. 12(b) and fig. 13, and is not described in detail here.

As shown in fig. 14, an embodiment of the present invention provides a GTP tunnel processing system 14, where the system 14 includes: an Openflow controller 1401, and an Openflow switch 1402 with an extended target, where the Openflow controller 1401 is a device having a control plane function in a GTP tunnel endpoint, and the Openflow switch 1402 is a device having a data plane function in a GTP tunnel endpoint in the GTP tunnel.

An Openflow controller 1401, configured to obtain a GTP tunnel establishment request; establishing a GTP tunnel by establishing a GTP tunnel request, wherein the establishing of the GTP tunnel request comprises generating relevant parameters of the GTP tunnel, the relevant parameters of the GTP tunnel comprise a first GTP routing flow table entry and a next hop encapsulation parameter recording entry, the first GTP routing flow table entry is a flow table entry used when the target extended Openflow switch 1402 transmits data, the first GTP routing flow table entry at least comprises a general packet radio service technology tunnel protocol data plane Version number GTP-U Version, a general packet radio service technology tunnel protocol data plane tunnel endpoint identifier GTP-U TEID, and the next hop encapsulation parameter recording entry is a flow table entry used when the target extended Openflow switch 1402 encapsulates data; sending relevant parameters of the GTP tunnel to the Openflow switch 1402 for target expansion;

the target-extended Openflow switch 1402 is configured to receive an Openflow controller 1401 sent to a first GTP routing flow table entry and/or a next hop encapsulation parameter record entry; and transmitting data according to the first GTP routing flow table entry and the next hop encapsulation parameter record entry.

Further, the Openflow controller is specifically configured to select an Openflow switch 1402 for target expansion of a GTP tunnel; acquiring available network link parameters, wherein the available network link parameters at least comprise an IP address and a port number corresponding to the Openflow switch 1402 with the target expansion; determining parameters for building a GTP tunnel according to the available network link parameters, wherein the parameters for building the GTP tunnel comprise a source IP address, a destination IP address, a source port number, a destination port number, GTP-UVerson and a GTP-U TEID corresponding to the GTP tunnel; and generating a first GTP routing flow table entry and a next hop encapsulation parameter record entry through the available network link parameters and the parameters for establishing the GTP tunnel.

The relevant parameters of the GTP tunnel further include a second GTP routing flow table entry, the second GTP routing flow table entry is a 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 further configured to generate a second GTP routing flow table entry by using the parameter for establishing the GTP tunnel; sending the second GTP routing flow table entry to a standard Openflow switch;

further, the system 14 further comprises a target standard Openflow switch 1403. The target standard Openflow switch is a standard Openflow switch participating in transmission of data in a GTP tunnel.

The Openflow controller 1401 is further configured to obtain decision result information, where the decision result information is used to instruct to perform specific processing on data corresponding to a specific service, where the specific processing is in any one of the following forms: transcoding data corresponding to a specific service, performing flow isolation on the data corresponding to the specific service, and sending an alert reminding message to User Equipment (UE) or performing advertisement video insertion on the data corresponding to the specific service; generating a specific GTP routing flow table entry for data corresponding to the specific service according to the decision result information; and selecting a target standard Openflow switch 1403 for the GTP tunnel; sending the specific GTP routing flow table entry to the target standard Openflow switch 1403;

target standard Openflow switch 1403, which is used to receive a specific GTP routing flow table entry sent by Openflow controller 1401.

Further, the Openflow controller is further configured to receive policy information sent by the policy and charging rule function unit PCRF; generating a first strategy GTP routing flow table entry, a next hop encapsulation parameter strategy recording entry and a second strategy GTP routing flow table entry through available network link parameters and strategy information, sending the first strategy GTP routing flow table entry and the next hop encapsulation parameter strategy recording entry to an Openflow switch 1402 with an expanded target, and sending the second strategy GTP routing flow table entry to a standard Openflow switch;

the target-expanded Openflow switch 1402 is further configured to receive a first policy GTP routing flow table entry and a next hop encapsulation parameter policy record entry sent by the Openflow controller 1401;

the target standard Openflow switch 1403 is further configured to receive a second policy GTP routing flow table entry sent by the Openflow controller 1401;

further, the Openflow controller 1401 is further configured to obtain a GTP tunnel modification request; modifying the GTP tunnel by modifying a GTP tunnel request, wherein the modifying the GTP tunnel request comprises generating relevant parameters for updating the GTP tunnel, the relevant parameters for updating the GTP tunnel comprise a first 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 a flow table entry used when the target-extended Openflow switch 1402 transmits data, the next hop encapsulation parameter update record entry is a flow table entry used when the target-extended Openflow switch 1402 encapsulates data, and the second updated GTP routing flow table entry is a flow table entry used when the standard Openflow switch transmits data; sending the relevant parameters for updating the GTP tunnel to the Openflow switch 1402 and the standard Openflow switch of the target extension; acquiring a GTP tunnel deletion request; deleting the corresponding GTP tunnel by a GTP tunnel deletion request; and notifying the target extended Openflow switch 1402 and/or the target standard Openflow switch 1403, so that the target extended Openflow switch 1402 and the target standard Openflow switch 1403 delete the parameter corresponding to the GTP tunnel deletion request.

The target-extended Openflow switch 1402 is further configured to receive relevant parameters for updating the GTP tunnel sent by the Openflow controller 1401; transmitting data according to the relevant parameters for updating the GTP tunnel; receiving a notification of deleting a GTP tunnel sent by the Openflow controller 1401, where the notification of deleting the GTP tunnel includes an identifier of deleting the GTP tunnel, and the notification of deleting the GTP tunnel is a signaling indicating the Openflow switch 1402 expanded by the target to delete the GTP tunnel; and deleting the GTP tunnel corresponding to the identifier of the deleted GTP tunnel through the notification of the first deleted GTP tunnel.

The target standard Openflow switch 1402 is further configured to receive relevant parameters for updating the GTP tunnel sent by the Openflow controller 1401; transmitting data according to the relevant parameters for updating the GTP tunnel; receiving a notification of deleting a GTP tunnel sent by the Openflow controller 1401, where the notification of deleting the GTP tunnel includes an identifier of deleting the GTP tunnel, and the notification of deleting the GTP tunnel is a signaling indicating that the target standard Openflow switch 1403 deletes the GTP tunnel; and deleting the GTP tunnel corresponding to the identifier of the deleted GTP tunnel through the notification of the second deleted GTP tunnel.

The control surface and the forwarding surface of the GTP tunnel endpoint are separated to obtain the Openflow controller and the extended Openflow switch, the Openflow controller in the invention can be used for establishing the GTP tunnels among the GTP tunnel endpoints, and the later Openflow controller can conveniently modify or delete the previously established GTP tunnels through the GTP tunnels established by the Openflow controller, so that the complexity of GTP tunnel processing is reduced; and planning the service data in advance, so that some specific information is added to the GTP data packet in the transmission process, thereby increasing the additional information of the service data and improving the adjustment capability of the service data transmission path.

It will be clear to those skilled in the art that, for convenience and simplicity of description, the foregoing division of the functional modules is merely used as an example, and in practical applications, the above function distribution may be performed by different functional modules according to needs, that is, the internal structure of the device is divided into different functional modules to perform all or part of the above described functions. For the specific working processes of the system, the apparatus and the unit described above, reference may be made to the corresponding processes in the foregoing method embodiments, and details are not described here again.

In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other manners. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the modules or units is only one logical division, and there may be other divisions when actually implemented, for example, a plurality of units or components may be combined or may be integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, a network device, or the like) or a processor (processor) to execute all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.

The above description is only for the specific embodiments of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present invention, and all the changes or substitutions should be covered within the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the appended claims.

Claims (10)

1. A GTP tunnel processing method is characterized by comprising the following steps:

the method comprises the steps that an Openflow controller obtains a GTP tunnel request for establishing a general packet radio service technology tunnel protocol, wherein the Openflow controller is equipment with a control surface function in a GTP tunnel endpoint;

the Openflow controller establishes a GTP tunnel through the GTP tunnel establishment request, wherein the GTP tunnel establishment request comprises relevant parameters for generating the GTP tunnel, the relevant parameters of the GTP tunnel comprise a first GTP routing flow table entry and a next hop encapsulation parameter record entry, 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 at least comprises a general packet radio service technology tunnel protocol data plane Version number GTP-U Version, a general packet radio service technology tunnel protocol data plane tunnel endpoint identifier

A GTP-U TEID, wherein the next hop encapsulation parameter recording item is a flow table item used when the target extended Openflow switch encapsulates data, and the target extended Openflow switch is a device which is used as a data plane function in the GTP tunnel and is provided with a GTP tunnel endpoint;

and 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.

2. The method for processing the GTP tunnel according to claim 1, wherein the Openflow controller requests to establish the GTP tunnel through the establishment of the GTP tunnel, including:

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

the Openflow controller acquires available network link parameters, wherein the available network link parameters at least comprise an IP address and a port number corresponding to the target-extended Openflow switch;

the Openflow controller determines parameters for establishing the GTP tunnel according to the available network link parameters, wherein the parameters for establishing the GTP tunnel comprise IP addresses at two ends, port numbers at two ends, GTP-UVerson and GTP-U TEID (user equipment identity) corresponding to the GTP tunnel;

and the Openflow controller generates a first GTP routing flow table entry and a next hop encapsulation parameter record entry according to the available network link parameter and the parameter for establishing the GTP tunnel.

3. The method for processing the GTP tunnel according to claim 2, wherein the relevant parameters of the GTP tunnel further include a second GTP routing flow table entry, the second GTP routing flow table entry is a flow table entry used when a standard Openflow switch transmits data, and the standard Openflow switch is all standard Openflow switches managed by the Openflow controller;

after the Openflow controller obtains the available network link parameters of the target-extended Openflow switch, the method further includes:

the Openflow controller generates the second GTP routing flow table entry according to the parameter for establishing the GTP tunnel;

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

4. The method for handling the GTP tunnel according to claim 2 or 3, wherein after the Openflow controller requests to establish the GTP tunnel through the establishing the GTP tunnel, the method further includes:

the Openflow controller obtains decision result information, wherein the decision result information is used for indicating specific processing to data corresponding to a specific service, and the specific processing is in any one of the following forms: transcoding the data corresponding to the specific service, performing flow isolation on the data corresponding to the specific service, and sending an alert reminding message to User Equipment (UE) or performing advertisement video insertion on 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;

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

5. The method of GTP tunnel treatment according to claim 4, further comprising:

the Openflow controller receives the policy and charging rule function unit PCRF and sends the policy information to the Openflow controller;

and the Openflow controller generates a first strategy GTP routing flow table entry, a next hop encapsulation parameter strategy recording entry and a second strategy GTP routing flow table entry according to the available network link parameters and the strategy information.

6. The method of handling a GTP tunnel according to claim 1, further comprising:

the Openflow controller acquires a GTP tunnel modification request; modifying a GTP tunnel through the GTP tunnel modification request, wherein the GTP tunnel modification request comprises generation of relevant parameters for updating the GTP tunnel, the relevant parameters for updating the GTP tunnel comprise a first GTP routing flow table updating entry, a next hop encapsulation parameter updating record entry and a second GTP routing flow table updating entry, the first GTP routing flow table updating entry is a flow table entry used when the target extended Openflow switch transmits data, the next hop encapsulation parameter updating record entry is a flow table entry used when the target extended Openflow switch encapsulates data, and the second GTP routing flow table updating entry is a flow table entry used when a standard Openflow switch transmits data; correspondingly sending the relevant parameters of the updated GTP tunnel to the target-extended Openflow switch and the standard Openflow switch; or,

the Openflow controller acquires a GTP tunnel deletion request, wherein the GTP tunnel deletion request comprises an identifier indicating deletion of a GTP tunnel; deleting the corresponding GTP tunnel through the identification for deleting the GTP tunnel; and notifying 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 parameters corresponding to the GTP tunnel deletion request.

7. A GTP tunnel processing system, the system including an Openflow controller and a target-extended Openflow switch, where the Openflow controller is a device having a control plane function in a GTP tunnel endpoint, and the target-extended Openflow switch is a device having a data plane function in the GTP tunnel endpoint in the GTP tunnel, the system including:

the Openflow controller is used for acquiring a request for establishing a general packet radio service technology tunnel protocol (GTP) tunnel; establishing a GTP tunnel through the GTP tunnel establishment request, wherein the GTP tunnel establishment request comprises relevant parameters for generating the GTP tunnel, the relevant parameters for the GTP tunnel comprise a first GTP routing flow table entry and a next hop encapsulation parameter recording entry, the first GTP routing flow table entry is a flow table entry used when a target extended Openflow switch transmits data, the first GTP routing flow table entry at least comprises a general packet radio service technology (GPRS) tunnel protocol data plane version number GTP-UVerson, a GPRS tunnel protocol data plane tunnel endpoint identification GTP-U TEID, and the next hop encapsulation parameter recording entry is a flow table entry used when the target extended Openflow switch encapsulates data; sending the relevant parameters of the GTP tunnel to an Openflow switch of target expansion;

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

8. The system for processing a GTP tunnel according to claim 7,

the Openflow controller is further configured to select an Openflow switch for the target extension of the GTP tunnel; acquiring available network link parameters, wherein the available network link parameters at least comprise an IP address and a port number corresponding to the target-extended Openflow switch; determining parameters for establishing the GTP tunnel according to the available network link parameters, wherein the parameters for establishing the GTP tunnel comprise a source IP address, a destination IP address, a source port number, a destination port number, a GTP-U Version and a GTP-U TEID corresponding to the GTP tunnel; and generating a first GTP routing flow table entry and a next hop encapsulation parameter record entry according to the available network link parameters and the parameters for establishing the GTP tunnel.

9. The GTP tunnel processing system of claim 8, wherein the relevant parameters of the GTP tunnel further include a second GTP routing flow table entry, the second GTP routing flow table entry is a flow table entry used when a standard Openflow switch transmits data, and the standard Openflow switch is all standard Openflow switches managed by the Openflow controller;

the Openflow controller is further configured to generate the second GTP routing flow table entry according to the parameter for establishing the GTP tunnel; sending the second GTP routing flow table entry to the standard Openflow switch;

the system further comprises: a target standard Openflow switch, wherein the target standard Openflow switch is the standard Openflow switch participating in transmission of data in the GTP tunnel;

the Openflow controller is further configured to acquire decision result information, where the decision result information is used to instruct to perform specific processing on data corresponding to a specific service, where the specific processing is in any one of the following forms: transcoding the data corresponding to the specific service, performing flow isolation on the data corresponding to the specific service, and sending an alert reminding message to User Equipment (UE) or performing advertisement video insertion on the data corresponding to the specific service; generating a specific GTP routing flow table entry for the data corresponding to the specific service according to the decision result information; selecting a target standard Openflow switch for the GTP tunnel; sending the specific GTP routing flow table entry to the target standard Openflow switch;

and the target standard Openflow switch is used for receiving the specific GTP routing flow table entry sent by the Openflow controller.

10. The system for processing a GTP tunnel according to claim 9,

the Openflow controller is further configured to receive policy information sent by the policy and charging rule functional unit PCRF; generating 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 through available network link parameters and the policy information, sending the first policy GTP routing flow table entry and the next hop encapsulation parameter policy record entry to the target-extended Openflow switch, and sending the second policy GTP routing flow table entry to the standard Openflow switch;

the target-extended Openflow switch is further configured 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 further configured to receive the second policy GTP routing flow table entry sent by the Openflow controller;

the Openflow controller is further configured to acquire a GTP tunnel modification request; modifying a GTP tunnel through the GTP tunnel modification request, wherein the GTP tunnel modification request comprises generation of relevant parameters for updating the GTP tunnel, the relevant parameters for updating the GTP tunnel comprise a first GTP routing flow table updating entry, a next hop encapsulation parameter updating record entry and a second GTP routing flow table updating entry, the first GTP routing flow table updating entry is a flow table entry used when the target extended Openflow switch transmits data, the next hop encapsulation parameter updating record entry is a flow table entry used when the target extended Openflow switch encapsulates data, and the second GTP routing flow table updating entry is a flow table entry used when a standard Openflow switch transmits data; sending the relevant parameters for updating the GTP tunnel to the target-extended Openflow switch and the standard Openflow switch; acquiring a GTP tunnel deletion request; deleting the corresponding GTP tunnel according to the GTP tunnel deletion request; notifying 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 parameters corresponding to the GTP tunnel deletion request;

the target-extended Openflow switch is further configured to receive the relevant parameters of the updated GTP tunnel sent by the Openflow controller; transmitting data according to the relevant parameters of the updated GTP tunnel; receiving a first GTP tunnel deletion notification sent by the Openflow controller, wherein the first GTP tunnel deletion notification includes a GTP tunnel deletion identifier, and the first GTP tunnel deletion notification is a signaling indicating that the target extended Openflow switch deletes the GTP tunnel; deleting the GTP tunnel corresponding to the identifier of the deleted GTP tunnel through the first notification for deleting the GTP tunnel;

the target standard Openflow switch is further configured to receive the relevant parameters of the updated GTP tunnel sent by the Openflow controller; transmitting data according to the relevant parameters of the updated GTP tunnel; receiving a second GTP tunnel deletion notification sent by the Openflow controller, where the second GTP tunnel deletion notification includes a GTP tunnel deletion identifier, and the second GTP tunnel deletion notification is a signaling that indicates the target standard Openflow switch to delete the GTP tunnel; and deleting the GTP tunnel corresponding to the identifier of the deleted GTP tunnel through the notification of deleting the GTP tunnel by the second step.