WO2017049971A1

WO2017049971A1 - Packet transmission method and gateway

Info

Publication number: WO2017049971A1
Application number: PCT/CN2016/086551
Authority: WO
Inventors: 蔡仕江
Original assignee: 华为技术有限公司
Priority date: 2015-09-22
Filing date: 2016-06-21
Publication date: 2017-03-30
Also published as: CN105245446B; CN105245446A

Abstract

Disclosed are a packet transmission method and a gateway for solving a problem in which an equipment has to be upgraded to support Hypertext Transfer Protocol 2.0 (HTTP 2.0). The method comprises: acquiring, by a gateway, a packet transmitted by a user equipment, wherein the packet carries upgrade information for upgrading the user equipment to support HTTP 2.0, and the upgrade information comprises the following key fields: a connection field, an upgrade field, and a setting field; analyzing and identifying, by the gateway, the upgrade information; modifying, by the gateway, the key fields in the upgrade information, respectively, and after identifying, by a server end, the received packet as a packet associated with HTTP 1.x, responding, to the user equipment, with an HTTP 1.x confirmation message.

Description

Message sending method and gateway

The present application claims priority to Chinese Patent Application No. 201510608336.0, entitled "A Message Delivery Method and Gateway", filed on September 22, 2015, the entire contents of which is incorporated herein by reference. in.

Technical field

The present invention relates to the field of communications, and in particular, to a message sending method and a gateway.

Background technique

The father of the World Wide Web (English: World Wide Web, English abbreviation: WWW), Tim Benas-Lee, proposed the Hypertext Transport Protocol (English: Hypertext Transport Protocol, HTTP) in 1990. The basic protocol of WWW. The so-called hypertext is compared to traditional text. Traditional texts, whether textbooks or computer text files, are linear. Readers must read pages one by one in order to read them. The reader has no choice. Unlike hypertext, hypertext is not a linear structure, but a nonlinear mesh structure. When reading, readers don't have to read down in a sequential manner when reading linear articles, but instead selectively read the parts of interest.

Currently, HTTP1.x uses multiple quintuples to connect to the server to obtain data. When the user requests data GET to reach the gateway device, the gateway performs DPI (English: Deep packet inspection, Chinese: deep packet inspection) analysis to obtain accurate accounting information of the user. . After HTTP2.0, there are different stream IDs in the same quintuple to transmit data. The GET in different stream IDs matches the corresponding rules, and it is precisely because this quintuple has many streams of different service data, the same message. There are also multiple streams of data in it, which leads to more precise and finer service control. The gateway is not practical based on the quintuple and requires a comprehensive upgrade of the base stream ID.

HTTP 2.0 brings upgrades to server and gateway device synchronization. Especially when the server also supports HTTP2.0, the gateway is passive, because many versions of the current network may still be earlier versions, and HTTP2.0 is not fully supported. Currently, it takes a lot of time to use the online device version upgrade to support HTTP2.0. Manpower and time period.

Summary of the invention

The invention provides a message sending method and a gateway, which are used to solve the problem of upgrading the device version brought by the HTTP2.0 upgrade.

A first aspect of the present invention provides a packet sending method, including:

The gateway obtains the packet sent by the user equipment, where the packet carries the upgrade information of the hypertext transfer protocol HTTP2.0 protocol of the user equipment, where the upgrade information includes the following key fields: a connection field, an upgrade field, and a setting. Field

The gateway parses and identifies the upgrade information;

The gateway modifies the key fields in the upgrade information separately, so that the server identifies the received message as an HTTP1.x protocol message and then responds to the user equipment with HTTP1.x. Confirmation message of the agreement.

With reference to the first aspect of the present invention, in a first implementation manner of the first aspect of the present disclosure, the modifying, by the gateway, the keyword segments in the upgrade information separately includes:

The gateway inverts the character strings corresponding to the key fields respectively.

With reference to the first aspect of the present invention, in a second implementation manner of the first aspect of the present disclosure, the modifying, by the gateway, the keyword segments in the upgrade information separately includes:

The gateway deletes the key field.

With reference to the first aspect of the present invention, or the first implementation manner of the first aspect, or the second implementation manner of the first aspect, in a third implementation manner of the first aspect of the present invention, the gateway analysis and identification The upgrade information specifically includes:

The gateway records the key segment and performs deep packet detection DPI analysis.

A second aspect of the present invention provides a gateway, including:

An obtaining unit, configured to obtain a packet sent by the user equipment, where the packet carries the upgrade information of the Hypertext Transfer Protocol (HTTP2.0) of the user equipment, where the upgrade information includes the following key fields: a connection field, Upgrade fields and set fields;

An identification unit, configured to parse and identify the upgrade information;

a modifying unit, configured to modify the key fields in the upgrade information separately, so that the server identifies the received message as an HTTP1.x protocol message and then responds to the user equipment with the HTTP1 A confirmation message for the .x protocol.

With reference to the second aspect of the present invention, in a first implementation manner of the second aspect of the present invention, the modifying unit is specifically configured to invert a character string corresponding to the key field.

In conjunction with the second aspect of the present invention, in a second implementation manner of the second aspect of the present disclosure, the modifying unit is specifically configured to delete the key field.

With reference to the second aspect of the present invention, or the first implementation manner of the second aspect, or the second implementation manner of the second aspect, in the third implementation manner of the second aspect of the present invention, the The key segment is recorded, and DPI analysis is performed for deep packet inspection.

It can be seen from the above technical solution that the present invention has the following advantages: the gateway obtains the packet sent by the user equipment, and the packet carries the upgrade information of the hypertext transfer protocol HTTP2.0 protocol of the user equipment, and the upgrade information The key field includes: a connection field, an upgrade field, and a setting field; the gateway parses and identifies the upgrade information; the gateway separately modifies the key fields in the upgrade information, so that the server side The received message is identified as a message of the HTTP 1.x protocol and then acknowledges the HTTP1.x protocol confirmation message to the user equipment. Therefore, the information that the user equipment wants to upgrade to HTTP2.0 is dropped back to HTTP1.x, so that the user equipment can not perceive and still continue the service, and can allow the user to continue the service and control the user flow.

DRAWINGS

FIG. 1 is a schematic flowchart diagram of an embodiment of a packet sending method according to the present invention;

2 is a schematic flowchart diagram of another embodiment of a method for sending a packet according to the present invention;

FIG. 3 is a schematic flowchart diagram of another embodiment of a packet sending method according to the present invention;

4 is a schematic structural diagram of an embodiment of a gateway provided by the present invention;

FIG. 5 is a schematic structural diagram of another embodiment of a gateway provided by the present invention.

detailed description

The technical solutions in the embodiments of the present invention are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present invention. It is obvious that the described embodiments are only a part of the embodiments of the present invention, but not all embodiments. All other embodiments obtained by a person skilled in the art based on the embodiments of the present invention without creative efforts are within the scope of the present invention.

It should be understood that although the terms first, second, etc. may be used in the embodiments of the present invention to describe each Users or terminals, but users or terminals should not be limited to these terms. These terms are only used to distinguish users or terminals from each other. For example, the first user may also be referred to as a second user without departing from the scope of the embodiments of the present invention. Similarly, the second user may also be referred to as a first user; similarly, the second user may also be This is not limited by the embodiment of the present invention.

For the convenience of the reader, the knowledge field and application scenarios involved in the present invention are briefly introduced:

The working process of HTTP is a typical client/server working mode, the client is the WWW browser, and the server is the WWW server. The HTTP working process uses the request/response handshake method: 1 the client connects, the two parties establish a TCP connection; 2 the client makes the request; 3 the server processes the request, returns the response; 4 the server closes the connection.

The main features of HTTP are as follows:

1) Simple and fast

HTTP itself is both simple and efficient in handling large numbers of requests. After the client connects to the server, the information that the client must pass is just the request method and path. Because HTTP is simple, the HTTP server program is small and simple. Therefore, the communication speed via HTTP is very fast, and the time overhead is much smaller than other protocols.

2) No connection

HTTP is a connectionless protocol. It means limiting each connection to only one request, the client submits a request after connecting to the server, and disconnects immediately after the client receives the response. With this connectionless protocol, the server won't wait for it when there is no request, and the server will not hold the original request after completing a request. Using a connectionless protocol is like writing a letter. Once you write a good letter, it will be fine. The other party has a new message and another letter. Keeping the connection agreement is similar to making a call. The two sides took turns to talk about a lot of words before they hang up. The phone line is always occupied during the conversation. For connectionless protocols, the server side is easier to implement and can take advantage of online resources.

3) No state

HTTP is a stateless protocol: each request, the content, status, and completion of the response are not retained as historical data for use in the next phase. It is both an advantage and a disadvantage. On the one hand, because there is no state, the protocol has no ability to remember things. If subsequent transaction processing requires prior processing For information, then this information must be saved outside the agreement. A lack of state means that the required front information must be reproduced, which inevitably leads to more information being transmitted per connection. On the other hand, it is precisely because of the lack of state that HTTP is less cumbersome, running faster, and the server responds faster.

4) Content negotiation

When the server is able to provide multiple representation responses to the client's request, a content negotiation mechanism is required to enable the web server to pick out the resource entity with the most appropriate form of expression that satisfies the user's requirements. Because many times the source server or the intermediate server providing the cache does not have a unified optimal resource form standard, and the client browser does not necessarily have the ability to handle all entity types.

5) Easy to expand

As a publicly available usage protocol, HTTP has good scalability, and it transmits more than just hypertext data. Based on this, the application developer's research and development requirements can easily increase the request method and response state, and run it in the user-customized system. The expanded server can respond to the original standard browser, and can also distinguish the dedicated client program developed by the user and respond accordingly.

HTTP protocol development

After the establishment of the WWW Alliance, the IETF (English: Internet Engineering Task Force) group was further developed to further improve and publish the HTTP protocol. So far, the HTTP protocol has gone through three phases of 0.9, 1.0, and 1.1.

1) HTTP/0.9 features:

1 a simple and fast protocol for various data information;

2 has a typical statelessness;

3 no connectivity;

4 can not use content negotiation;

5 Cannot display and process images.

2) HTTP/1.0 features:

1 single fast;

2 stateless;

3 no connectivity;

4 can not use content negotiation;

5 Added meta information: add a piece of information, that is, information information, in front of the main data. It enables the server to provide information about the transfer of data. For example, what type of object is being transferred, in which language it is written, and so on;

6 supports a variety of content forms, such as pictures, audio, and so on.

3) HTTP/1.1 features:

1Continuous connection: Allows a browser requesting a web page to initiate a connection to download multiple files from the server;

2 is still stateless, but provides state control;

3 new resource request has been added: OPTIONS, PUT, DELETE and TRACE have been added based on the original GET, HEAD and POST methods;

4 identity authentication: a simple "question-answer" basic access authorization method. The process is to first send an identity authentication request to the client by the server, and then the customer sends a confirmation message;

5 use the content negotiation mechanism;

6 Cache mechanism: Temporarily save the contents of the previous client request and the response of the web server corresponding to the request in the memory or physical memory of the machine, so that it can be utilized when processing a new client request.

3) Introduction to HTTP/2.0:

HTTP 2.0, Hypertext Transfer Protocol 2.0, is the next generation HTTP protocol. It was developed by the IETF's Hypertext Transfer Protocol Bis (httpbis) working group. It is the first update since the release of http1.1 in 1999. HTTP 2.0 conducted its first collaborative collaboration test in August 2013. HTTP/2.0 provides HTTP semantically optimized transport.

An HTTP/2.0 connection is made through a TCP connection (application-level protocol [TCP] running above). The client is the TCP connection initiator. Logical structure of the HTTP/2.0 protocol: framing, streams, and application mapping. The client can initiate an HTTP2.0 negotiation upgrade. If the server supports the HTTP2.0 protocol, the server will answer the HTTPOK 100OK confirmation, otherwise it will directly answer the 100OK confirmation of HTTP1.x. The client can also directly initiate an HTTP 2.0 request message, and the server must respond to the HTTP 2.0 request.

The present invention provides a packet sending method, which is mainly executed by a gateway; 1. An embodiment of a message sending method provided by the present invention includes:

The gateway obtains the packet sent by the user equipment, where the packet carries the upgrade information of the Hypertext Transfer Protocol (HTTP2.0) of the user equipment, where the upgrade information includes the following key fields: a connection field, an upgrade field, and an upgrade field. , setting the field;

It should be noted that the user equipment initiates a TCP connection, establishes a TCP connection with the server, and the gateway acquires a packet sent by the user equipment, where the packet carries the upgrade information of the hypertext transfer protocol HTTP2.0 protocol of the user equipment, The upgrade information includes the following key fields: connection field Connection, upgrade field Upgrade, and setting field HTTP2-Setting.

102. The gateway parses and identifies the upgrade information.

It should be noted that the gateway identifies the key field in the upgrade information, records the keyword information, and performs DPI and content charging.

103. The gateway separately modifies the key fields in the upgrade information, so that the server identifies the received message as an HTTP1.x protocol message and then responds to the user equipment with the HTTP1. A confirmation message for the .x protocol.

It should be noted that the gateway separately modifies the key fields in the upgrade information, for example, respectively, the Connection, Upgrade, and HTTP2-Setting fields in the HTTP header field are reversed or the sequence of the strings is scrambled; or Delete the Connection, Upgrade, and HTTP2-Setting fields. If you choose to delete the device, you need to add the deleted key fields to the HTTP header field before the server responds to the HTTP1.x acknowledgment message from the user device to ensure TCP. The correctness of the sequence.

In the embodiment of the present invention, the gateway obtains the packet sent by the user equipment, where the packet carries the upgrade information of the Hypertext Transfer Protocol (HTTP2.0) of the user equipment, where the upgrade information includes the following key fields: a field, an upgrade field, and a setting field; the gateway parses the upgrade information; the gateway separately modifies the key fields in the upgrade information, so that the server identifies the received message A message confirming the HTTP 1.x protocol is sent to the user equipment after the message of the HTTP 1.x protocol. Therefore, the information that the user equipment wants to upgrade to HTTP2.0 is dropped back to HTTP1.x, so that the user equipment can not perceive and still continue the service, and can allow the user to continue the service and control the user flow.

Referring to FIG. 2, another embodiment of a packet sending method provided by the present invention includes:

The gateway obtains the packet sent by the user equipment, where the packet carries the upgrade information of the hypertext transfer protocol HTTP2.0 protocol of the user equipment, where the upgrade information includes the following key fields: a connection field, an upgrade field. , setting the field;

202. The gateway parses and identifies the upgrade information.

Steps

201 and 202 refer to the related descriptions in

steps

101 and 102, and details are not described herein again.

203. The gateway reverses the character string corresponding to the key field, so that the server identifies the received message as the HTTP1.x protocol message and then responds to the user equipment with HTTP1. A confirmation message for the x protocol.

It should be noted that the gateway inverts the character strings corresponding to the key fields respectively, for example, respectively, the Connection, Upgrade, and HTTP2-Setting fields in the HTTP header field are reversed; for example, the system is passing HTTP. The Upgrade request is modified to ensure the correctness of the data transfer. The HTTP to HTTP 2.0 upgrade header field is in the following format:

GET/default.htm HTTP/1.1

Host:server.example.com

Connection:Upgrade,HTTP2-Settings

Upgrade: h2c

HTTP2-Settings: <base64url encoding of HTTP/2SETTINGS payload>

The gateway UGW needs to identify the Connection, Upgrade, and HTTP2-Setting fields in the above example and reverse it:

GET/default.htm HTTP/1.1

Host:server.example.com

noitcennoC:Upgrade,HTTP2-Settings

edargpU:h2c

sgnitteS-2PTTH: <base64url encoding of HTTP/2SETTINGS payload>

In the above embodiment, the string order of the Connection, Upgrade, and HTTP2-Setting fields can be disturbed, or a few letters can be added/reduced, and the same effect can be achieved.

In the embodiment of the present invention, the gateway obtains the packet sent by the user equipment, where the packet carries the upgrade information of the Hypertext Transfer Protocol (HTTP2.0) of the user equipment, where the upgrade information includes the following key fields: Field, upgrade field, setting field; the gateway parsing identifies the liter Level information; the gateway inverts the character string corresponding to the key field, respectively, so that the server recognizes the received message as an HTTP1.x protocol message and then responds to the user equipment with HTTP1. A confirmation message for the .x protocol. Therefore, the information that the user equipment wants to upgrade to HTTP2.0 is dropped back to HTTP1.x, so that the user equipment can not perceive and still continue the service, and can allow the user to continue the service and control the user flow.

Referring to FIG. 3, another embodiment of a packet sending method provided by the present invention includes:

301. The gateway obtains a packet sent by the user equipment, where the packet carries the upgrade information of the Hypertext Transfer Protocol (HTTP2.0) of the user equipment, where the upgrade information includes the following key fields: a connection field, an upgrade field, and an upgrade field. , setting the field;

302. The gateway parses and identifies the upgrade information.

Steps

301 and 302 refer to the related descriptions in

steps

101 and 102, and details are not described herein again.

303. The gateway deletes the key field, so that the server identifies the received message as an HTTP1.x protocol message and then responds to the user equipment with an acknowledgement message of the HTTP1.x protocol.

It should be noted that the gateway deletes the key field, for example, deletes the Connection, Upgrade, and HTTP2-Setting fields in the HTTP header field; for example, the system ensures the correctness of data transmission after modifying the HTTP Upgrade request. The HTTP to HTTP 2.0 upgrade header field is in the following format:

GET/default.htm HTTP/1.1

Host:server.example.com

Connection:Upgrade,HTTP2-Settings

Upgrade: h2c

HTTP2-Settings: <base64url encoding of HTTP/2SETTINGS payload>

The gateway UGW needs to identify the Connection, Upgrade, and HTTP2-Setting fields in the above example and delete it:

GET/default.htm HTTP/1.1

Host:server.example.com

After selecting the deletion mode, the TCP layer needs to maintain the serial numbers on the left and right sides:

After the gateway UGW modifies the HTTP request header field initiated by the user equipment UE, the TCP sequence will follow The change, therefore, the gateway UGW needs to ensure the correctness of the TCP sequence to avoid protocol-level errors.

In the embodiment of the present invention, the gateway obtains the packet sent by the user equipment, where the packet carries the upgrade information of the Hypertext Transfer Protocol (HTTP2.0) of the user equipment, where the upgrade information includes the following key fields: a field, an upgrade field, and a setting field; the gateway parses the upgrade information; the gateway deletes the key field, so that the server identifies the received message as an HTTP1.x protocol message. The acknowledgment message of the HTTP1.x protocol is then replied to the user equipment. Therefore, the information that the user equipment wants to upgrade to HTTP2.0 is dropped back to HTTP1.x, so that the user equipment can not perceive and still continue the service, and can allow the user to continue the service and control the user flow.

For the sake of understanding, the packet sending method in the embodiment of the present invention is specifically described in a specific application scenario:

The user equipment initiates a TCP connection, establishes a TCP connection with the server, and the gateway obtains the packet sent by the user equipment, where the packet carries the upgrade information of the hypertext transfer protocol HTTP2.0 protocol of the user equipment, and the upgrade information includes the following information. Key field: Connection field Connection, upgrade field Upgrade, setting field HTTP2-Setting.

The gateway identifies the key fields in the upgrade information, records the keyword information, and performs DPI and content charging.

The gateway inverts the character string corresponding to the key field, so that the server recognizes the received message as a packet of the HTTP 1.x protocol, and then responds to the user equipment with the HTTP 1.x protocol. Confirmation message. For example, the Connection, Upgrade, and HTTP2-Setting fields in the HTTP header field are reversed respectively; for example, the system ensures the correctness of data transmission by modifying the HTTP Upgrade request, and the HTTP to HTTP 2.0 upgrade header field is in the following format. :

GET/default.htm HTTP/1.1

Host:server.example.com

Connection:Upgrade,HTTP2-Settings

Upgrade: h2c

HTTP2-Settings: <base64url encoding of HTTP/2SETTINGS payload>

The gateway UGW needs to identify the Connection, Upgrade, and HTTP2-Setting fields in the above example. Points and reverses it:

GET/default.htm HTTP/1.1

Host:server.example.com

noitcennoC:Upgrade,HTTP2-Settings

edargpU:h2c

sgnitteS-2PTTH: <base64url encoding of HTTP/2SETTINGS payload>

Or you can also mess up the string order of the Connection, Upgrade, and HTTP2-Setting fields, or increase/decrease a few letters to achieve the same effect.

After the gateway reverses the above Connection, Upgrade, and HTTP2-Setting fields, the packet is sent to the server. The server identifies the received packet as the HTTP1.x protocol packet and then responds to the user equipment with HTTP1. The confirmation message of the x protocol, ie HTTP1.x 200OK.

The method for sending a message is described above. The structure of the gateway will be described from the perspective of the device. Referring to FIG. 4, the gateway includes:

The obtaining unit 401 is configured to obtain a packet sent by the user equipment, where the packet carries the upgrade information of the hypertext transfer protocol HTTP2.0 protocol of the user equipment, where the upgrade information includes the following key field: a connection field. , upgrade fields, set fields;

The identifying unit 402 is configured to parse and identify the upgrade information;

The modifying unit 403 is configured to modify the key fields in the upgrade information to enable the server to identify the received message as a packet of the HTTP 1.x protocol and then respond to the user equipment. A confirmation message for the HTTP1.x protocol.

In the embodiment of the present invention, the obtaining unit 401 obtains the packet sent by the user equipment, where the packet carries the upgrade information of the hypertext transfer protocol HTTP2.0 protocol of the user equipment, where the upgrade information includes the following key segments. a connection field, an upgrade field, and a setting field; the identification unit 402 parses and identifies the upgrade information; the modifying unit 403 separately modifies the key fields in the upgrade information, so that the server receives the report. After the message is identified as a message of the HTTP 1.x protocol, the user device is replied to the HTTP1.x protocol confirmation message. Therefore, the information that the user equipment wants to upgrade to HTTP2.0 is dropped back to HTTP1.x, so that the user equipment can not perceive and still continue the service, and can allow the user to continue the service and control the user flow.

Based on the gateway in the above embodiment, optionally, in one embodiment, the modifying unit The 403 is specifically configured to invert the character string corresponding to the key field, so that the server identifies the received message as an HTTP1.x protocol message and then responds to the user equipment with the HTTP1.x. Confirmation message of the agreement.

Based on the gateway in the foregoing embodiment, optionally, in an implementation manner, the modifying unit 403 is specifically configured to delete the key field, so that the server identifies the received message as HTTP1. The message of the x protocol is replied to the user equipment with an acknowledgement message of the HTTP 1.x protocol.

Based on the gateway in the foregoing embodiment, optionally, in an implementation manner, the identifying unit 402 is specifically configured to record the key segment and perform deep packet detection DPI analysis.

The embodiment shown in FIG. 4 illustrates the specific structure of the gateway from the perspective of the functional unit. The specific structure of the gateway is described from the hardware point of view below with reference to the embodiment shown in FIG. 5:

As shown in FIG. 5, the gateway includes a receiver 501, a transmitter 502, a processor 503, and a memory 504. Memory 504 can include read only memory and random access memory and provides instructions and data to processor 503. A portion of the memory 504 can also include a non-volatile random access memory.

Memory 504 stores the following elements, executable modules or data structures, or subsets thereof, or their extended sets:

Operation instructions: include various operation instructions for implementing various operations.

Operating system: Includes a variety of system programs for implementing various basic services and handling hardware-based tasks.

The gateway according to an embodiment of the present invention may have more or less components than those shown in FIG. 5, may combine two or more components, or may have different component configurations or settings, and each component may include one Hardware, software, or a combination of hardware and software, including multiple signal processing and/or application specific integrated circuits.

In the embodiment of the present invention, the processor 503 is configured to perform the following operations:

Obtaining a packet sent by the user equipment, where the packet carries the upgrade information of the Hypertext Transfer Protocol (HTTP2.0) of the user equipment, where the upgrade information includes the following key fields: a connection field, an upgrade field, and a setting field. ;

Parsing and identifying the upgrade information;

Modifying the key fields in the upgrade information separately so that the server side will receive The received message is identified as a message of the HTTP 1.x protocol and then acknowledges the HTTP1.x protocol confirmation message to the user equipment.

In the embodiment of the present invention, the processor 503 obtains the packet sent by the user equipment, where the packet carries the upgrade information of the hypertext transfer protocol HTTP2.0 protocol of the user equipment, where the upgrade information includes the following key segments. a connection field, an upgrade field, and a setting field; the processor 503 parses and identifies the upgrade information, and separately modifies the key fields in the upgrade information, so that the server identifies the received message. A message confirming the HTTP 1.x protocol is sent to the user equipment after the message of the HTTP 1.x protocol. Therefore, the information that the user equipment wants to upgrade to HTTP2.0 is dropped back to HTTP1.x, so that the user equipment can not perceive and still continue the service, and can allow the user to continue the service and control the user flow.

Optionally, in an implementation manner, the processor 503 is specifically configured to:

The character string corresponding to the key segment is inverted, so that the server recognizes the received message as an HTTP1.x protocol message and then acknowledges the HTTP1.x protocol confirmation message to the user equipment. .

The key segment is deleted, so that the server recognizes the received message as a packet of the HTTP 1.x protocol, and then responds to the user equipment with an acknowledgement message of the HTTP 1.x protocol.

Record the key fields and perform deep packet inspection DPI analysis.

The related descriptions of the above-mentioned devices can be understood by referring to the related descriptions and effects of the method embodiments, and no further description is made herein.

A person skilled in the art can clearly understand that for the convenience and brevity of the description, the specific working process of the system, the device and the unit described above can refer to the corresponding process in the foregoing method embodiment, and details are not described herein again.

In the several embodiments provided by the present application, it should be understood that the disclosed system, apparatus, and method may be implemented in other manners. For example, the device embodiments described above are merely illustrative. For example, the division of the unit is only a logical function division. In actual implementation, there may be another division manner, for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed. Another point that is shown or discussed between each other The coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.

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

In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above integrated unit can be implemented in the form of hardware or in the 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 standalone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention, which is essential or contributes to the prior art, or all or part of the technical solution, may be embodied in the form of a software product stored in a storage medium. A number of instructions are included to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present invention. The foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like. .

The above embodiments are only used to illustrate the technical solutions of the present invention, and are not intended to be limiting; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art will understand that The technical solutions described in the embodiments are modified, or the equivalents of the technical features are replaced by the equivalents of the technical solutions of the embodiments of the present invention.

Claims

A message sending method, comprising:

The gateway obtains the packet sent by the user equipment, where the packet carries the upgrade information of the hypertext transfer protocol HTTP2.0 protocol of the user equipment, where the upgrade information includes the following key fields: a connection field, an upgrade field, and a setting. Field

The gateway parses and identifies the upgrade information;

The gateway modifies the key fields in the upgrade information separately, so that the server identifies the received message as an HTTP1.x protocol message and then responds to the user equipment with HTTP1.x. Confirmation message of the agreement.
The method according to claim 1, wherein the modifying, by the gateway, the keyword segments in the upgrade information separately comprises:

The gateway inverts the character strings corresponding to the key fields respectively.
The method according to claim 1, wherein the modifying, by the gateway, the keyword segments in the upgrade information separately comprises:

The gateway deletes the key field.
The method according to any one of claims 1 to 3, wherein the gateway parsing and identifying the upgrade information specifically includes:

The gateway records the key segment and performs deep packet detection DPI analysis.
A gateway, comprising:

An obtaining unit, configured to obtain a packet sent by the user equipment, where the packet carries the upgrade information of the Hypertext Transfer Protocol (HTTP2.0) of the user equipment, where the upgrade information includes the following key fields: a connection field, Upgrade fields and set fields;

An identification unit, configured to parse and identify the upgrade information;

a modifying unit, configured to modify the key fields in the upgrade information separately, so that the server identifies the received message as an HTTP1.x protocol message and then responds to the user equipment with the HTTP1 A confirmation message for the .x protocol.
The gateway according to claim 5, wherein the modifying unit is specifically configured to invert a character string corresponding to the key segment.
The gateway according to claim 5, wherein said modifying unit is specifically configured to The key field is deleted.
The gateway according to any one of claims 5 to 7, wherein the identification unit is specifically configured to record the key field and perform deep packet detection DPI analysis.