WO2014110754A1

WO2014110754A1 - Method for transmitting http packet, encoding device, and decoding device

Info

Publication number: WO2014110754A1
Application number: PCT/CN2013/070595
Authority: WO
Inventors: 范维光; 张静荣; 庞伶俐; 郑潇潇; 肖暄
Original assignee: 华为技术有限公司
Priority date: 2013-01-17
Filing date: 2013-01-17
Publication date: 2014-07-24
Also published as: CN104081747A; CN104081747B

Abstract

Disclosed are a method and a device for transmitting an HTTP packet. The method comprises: determining a value of each bit in a code header bitmap, the value of each bit indicating whether a value of a corresponding code header to be transmitted of the bit is the same as a value of a corresponding code header in a recorded HTTP packet; and generating and transmitting, according to the value of each bit, an HTTP packet to be transmitted that comprises the code header bitmap, so that a receiver of the HTTP packet to be transmitted is enabled to determine, according to the code header bitmap and the recorded HTTP packet, a first code header where a value of a code header in the HTTP packet to be transmitted is the same as the value of the corresponding code header in the recorded HTTP packet, and the value of the first code header. The method and the device for transmitting an HTTP packet according to the embodiments of the present invention can reduce wireless air-interface resources occupied by the same field in the continuous HTTP packets, thereby improving resource utilization.

Description

Method for transmitting HTTP message, encoding device and decoding device

The present invention relates to the field of communications, and in particular, to a method, an encoding device, and a decoding device for transmitting an HTTP message in the communication field. Background technique

HyperText Transfer Protocol (HyperText Transfer Protocol) is a widely used protocol on the Internet, such as web browsing, HTTP Progressive Download, Live Streaming, and Social Networking. Services, such as "SNS", and Weibo, use the HTTP protocol, which constitutes a mainstream application on the mobile Internet.

The HTTP protocol works in the Request-Response mode, that is, the client or terminal sends an HTTP Request (HTTP Request) message to the server to request the resource, and the server sends an HTTP Response (HTTP Response) message to the client or the terminal. Respond to a request from a client or terminal.

In the HTTP request/response (Request/Response) message, there are several header fields, including the acceptable language, acceptable encoding, user agent, browser type, cookie, etc., and these fields. It may be constant for a user, or at least for a period of time. For example, in a user's four consecutive HTTP access (GET) request messages, the Accept, User Agent, Host, Pragma, and Cookie fields in the HTTP header are identical, the first line of the HTTP message, and the HTTP message. The first few characters of the requested Uniform Resource Identifier ("URI") are also the same as "/client/", and the version number of the HTTP message is "ΗΤΤΡ/1.Γ".

Currently, the data of the HTTP layer is the payload of the Transmission Control Protocol ("TCP") / Internet Protocol ("IP") layer, HTTP layer data plus TCP header and IP. The header constitutes an IP packet that is transmitted over the Internet. The IP packet is transmitted as a payload in the wireless network, and the HTTP layer data (including all fields in the header) is transmitted in plain text in the wireless network. However, in general, consecutive HTTP messages contain a large number of identical fields in the header. These are redundant information and occupy a large amount of valuable wireless air interface resources. Summary of the invention

The invention provides a method for transmitting an HTTP message, an encoding device and a decoding device, which can reduce the wireless air interface resource occupied by the same field in the continuous HTTP message.

The first aspect provides a method for transmitting an HTTP packet, where the method includes: determining a value of each bit of the coding header part map, where the values of the bits are respectively indicated as corresponding to the bit Whether the value of the transmitted coding header is the same as the value of the corresponding coding header in the recorded HTTP message; according to the value of each bit, generating and transmitting the to-be-transmitted picture including the coding header part map The HTTP address of the HTTP packet to be transmitted, so that the receiver of the HTTP packet to be transmitted determines the value of the encoding header in the HTTP packet to be transmitted according to the encoding header part map and the recorded HTTP packet. The first encoding header of the corresponding encoding header in the recorded HTTP packet has the same value and the value of the first encoding header.

With reference to the first aspect, in a first possible implementation manner of the first aspect, the method further includes: determining a value in an encoding header to be transmitted and a corresponding encoding header in the recorded HTTP packet a second encoding header having a different value, and a value of the second encoding header; determining a header encoding of the second encoding header, the header encoding being used to refer to the second encoding header; And generating, according to the value of each bit, the HTTP message to be transmitted, including the code header part map, includes: according to the value of each bit, the header code of the second coding header And the value of the second encoding header is generated, and the HTTP packet to be transmitted is generated and transmitted.

In conjunction with the first possible implementation of the first aspect, in a second possible implementation of the first aspect, the method further includes: determining a first compression indication and a first number of bytes, the first compression indication The value indicating the second encoding header is compressed, and the first byte number is associated with the first identical number of bytes, where the first identical number of bytes is the value of the second encoding header to be transmitted. And the number of bytes consecutive to the value of the corresponding encoding header in the recorded HTTP packet; wherein, the value according to the bit, the header encoding of the second encoding header, and the first The value of the second encoding header, the generating and transmitting the HTTP packet to be transmitted, including: according to the value of each bit, the header encoding of the second encoding header, the first compression indication, and the One byte, generating and transmitting the HTTP message to be transmitted.

With reference to the first possible implementation manner of the first aspect, in a third possible implementation manner of the first aspect, the method further includes: determining a second compression indication, and the first HTTP packet in the recorded HTTP report Sequence information in the text, where the second compression indication is used to indicate that the value of the second encoding header and the corresponding encoding header in the first HTTP packet corresponding to the order information are taken The value is the same. The HTTP message to be transmitted is generated and transmitted according to the value of the bit, the header code of the second encoding header, and the value of the second encoding header. The HTTP message to be transmitted is generated and transmitted according to the value of each bit, the header code of the second encoding header, the second compression indication, and the order information.

With reference to the first aspect, in a fourth possible implementation manner of the first aspect, the method further includes: determining a third compression indication and a second byte number, where the third compression indication is used to indicate a universal resource identifier to be transmitted The URI is compressed, and the second number of bytes is associated with a second identical number of bytes, the second identical number of bytes being the same number of bytes of the URI to be transmitted and the URI in the recorded HTTP message And generating, according to the value of each bit, the HTTP message to be transmitted, including the code header part map, includes: determining, according to the value of each bit, the third compression indication, and The second byte number generates and transmits the HTTP message to be transmitted.

With reference to the first aspect, in a fifth possible implementation manner of the first aspect, the method further includes: determining whether the HTTP version number information to be transmitted is the same as the version number information in the recorded HTTP packet; And generating, according to the value of the bit, the HTTP packet to be transmitted, including the part of the encoding header, to be transmitted, including: the HTTP version number information to be transmitted and the recorded HTTP packet When the version number information is the same, the HTTP message to be transmitted is generated and transmitted according to the value of each bit, and the HTTP message to be transmitted includes the code header part map; the HTTP version number to be transmitted. When the information is different from the version number information in the recorded HTTP packet, the HTTP message to be transmitted is generated and transmitted according to the value of each bit and the HTTP version number information to be transmitted. The HTTP packet includes the encoding header portion map and the HTTP version number information to be transmitted.

With reference to the first aspect, in a sixth possible implementation manner of the first aspect, the generating, by using the value of the bit, the HTTP packet to be transmitted that includes the coded part part map is generated and transmitted, including: And generating, according to the value of each bit, a protocol data unit PDU packet including a type field, where the type field is used to indicate that the PDU packet is a header encoded and compressed HTTP message.

With reference to the first aspect, or any one of the first to the sixth possible implementation manners of the first aspect, in a seventh possible implementation manner of the first aspect, the method further includes: When the HTTP packet is transmitted for the first time, the encoding header value, URI, and HTTP version number information of the HTTP packet transmitted for the first time are recorded. When the HTTP packet is not transmitted for the first time, the recorded packet is updated according to the HTTP packet to be transmitted. HTTP message. With the seventh possible implementation of the first aspect, in an eighth possible implementation manner of the first aspect, the updating the recorded HTTP packet according to the HTTP packet to be transmitted includes: If the value of the encoding header of the transmitted HTTP packet is the same as the value of the encoding header of the recorded HTTP packet, the encoding header of the recorded HTTP packet and the value thereof are kept unchanged; or if If the value of the encoding header of the HTTP packet to be transmitted is different from the value of the encoding header of the HTTP packet, the value of the encoding header in the recorded HTTP packet is replaced by the value to be transmitted. The encoding header of the HTTP packet takes the value; or if the recorded HTTP packet has an encoding header that the HTTP packet to be transmitted does not have, the encoding header of the recorded HTTP packet is maintained and its encoding is maintained. The value is unchanged; or if the HTTP message to be transmitted has an encoding header that the recorded HTTP packet does not have, the HTTP message to be transmitted has the encoding that the recorded HTTP packet does not have. The header and its value; or if the HTTP message to be transmitted If the version number information is the same as the version number information of the recorded HTTP message, the version number information of the recorded HTTP message is kept unchanged; or if the version number information of the HTTP message to be transmitted and the recorded number are If the version number of the HTTP packet is different, the version number information of the HTTP packet is replaced with the version number of the HTTP packet to be transmitted.

The second aspect provides a method for transmitting an HTTP packet, where the method includes: acquiring a value of each bit of the encoded header portion map in the received HTTP packet; The value of a bit is indicated as the value of the first encoding header to be decoded corresponding to the first bit is the same as the value of the corresponding encoding header in the recorded HTTP packet, and the recorded value is recorded. The encoding header corresponding to the first bit in the HTTP packet and the value thereof are respectively determined as values of the first encoding header and the first encoding header.

With reference to the second aspect, in a first possible implementation manner of the second aspect, the method further includes: determining, by the second bit of the coding header part, that the second bit is corresponding to the second bit to be decoded When the value of the second encoding header is different from the value of the corresponding encoding header in the recorded HTTP packet, determining, according to the header encoding in the received HTTP packet, the header encoding refers to the The second encoding header.

In conjunction with the first possible implementation of the second aspect, in a second possible implementation of the second aspect, the method further includes: determining, according to the first compression indication and the first byte in the received HTTP packet And determining a first identical number of bytes associated with the first number of bytes, wherein the first compression indication is used to indicate that the value of the second encoding header is compressed; according to the first identical number of bytes, Will The number of bytes is determined as the value to be decoded of the second encoding header.

With reference to the first possible implementation of the second aspect, in a third possible implementation manner of the second aspect, the method further includes: determining, according to the second compression indication and the sequence information in the received HTTP packet, a first HTTP packet corresponding to the sequence information in the recorded HTTP packet, where the second compression indication is used to indicate the value of the second encoding header and the corresponding encoding in the first HTTP packet. The value of the header is the same; the value of the corresponding encoding header in the first HTTP packet is determined as the value of the second encoding header.

With reference to the second aspect, in a fourth possible implementation manner of the second aspect, the method further includes: determining, according to the third compression indication and the second byte number in the received HTTP packet, the second word a second identical number of bytes associated with the number of sections, wherein the third compressed indication is used to indicate that the URI to be decoded is compressed; according to the second identical number of bytes, corresponding to the URI of the recorded HTTP message The second consecutive byte of the same number of bytes is determined as the URL to be decoded in the received HTTP message.

With reference to the second aspect, in a fifth possible implementation manner of the second aspect, the method further includes: when determining that the received HTTP packet does not have the HTTP version number information, in the recorded HTTP packet The version number information is determined as the version number information of the received HTTP message.

With reference to the second aspect, in a sixth possible implementation manner of the second aspect, the method further includes: receiving a protocol data unit PDU packet including a type field, where the type field is used to indicate that the PDU packet is header encoded and Compressed HTTP ^ text.

With reference to the second aspect, or any one of the first to the sixth possible implementation manners of the second aspect, in a seventh possible implementation manner of the second aspect, the method further includes: When the HTTP packet is transmitted for the first time, the encoding header value, URI, and HTTP version number information of the HTTP packet transmitted for the first time are recorded. When the HTTP packet is not transmitted for the first time, the recorded HTTP packet is updated according to the received HTTP packet. Message.

With the seventh possible implementation of the second aspect, in an eighth possible implementation manner of the second aspect, the updating the recorded HTTP packet according to the received HTTP packet includes: The value of the encoding header of the HTTP packet is the same as the value of the encoding header of the recorded HTTP packet, and the encoding header of the recorded HTTP packet and the value thereof are kept unchanged; or if the received The value of the encoding header of the HTTP packet is different from the value of the encoding header of the recorded HTTP packet, and the value of the encoding header in the recorded HTTP packet is replaced by the received HTTP packet. Encoding header value; or if the recorded HTTP message has the received If the encoding header that the HTTP packet does not have, keep the encoding header of the recorded HTTP packet and its value unchanged; or if the received HTTP packet has an encoding that the recorded HTTP packet does not have a header, where the received HTTP message has an encoding header that does not have the recorded HTTP packet and its value; or if the received HTTP packet has the version number information and the recorded HTTP packet If the version number information of the document is the same, the version number information of the recorded HTTP packet is kept unchanged; or if the version number information of the received HTTP packet is different from the version number information of the recorded HTTP packet, The version number information in the recorded HTTP packet is replaced with the version number information of the received HTTP packet.

The third aspect provides an apparatus for encoding an HTTP packet, where the encoding apparatus includes: a first determining module, configured to determine a value of each bit of the code header part map, where the values of the bits are respectively Determining whether the value of the encoding header to be transmitted corresponding to the bit is the same as the value of the corresponding encoding header in the recorded HTTP packet; the transmitting module, configured to determine the per-determination according to the first determining module The value of the bit is generated, and the HTTP message to be transmitted including the code header part map is generated and transmitted, so that the receiver of the HTTP message to be transmitted according to the code header part map and the recorded HTTP Determining, by the packet, the first encoding header in the HTTP packet to be transmitted and the value of the corresponding encoding header in the recorded HTTP packet, and the first encoding header value.

With reference to the third aspect, in a first possible implementation manner of the third aspect, the encoding apparatus further includes: a second determining module, configured to determine a value in the encoding header to be transmitted and the recorded HTTP packet a second encoding header having a different value of the corresponding encoding header, and a value of the second encoding header; a third determining module, configured to determine the second encoding header determined by the second determining module a header encoding, the header encoding is used to refer to the second encoding header; wherein the transmitting module is configured to: determine, according to the value of each bit determined by the first determining module, the third determining module The header of the second encoding header and the value of the second encoding header determined by the second determining module generate and transmit the HTTP packet to be transmitted.

In conjunction with the first possible implementation of the third aspect, in a second possible implementation manner of the third aspect, the encoding apparatus further includes: a fourth determining module, configured to determine the first compression indication and the first byte The first compression indication is used to indicate that the value of the second encoding header is compressed, and the first number of bytes is associated with the first identical number of bytes, where the first identical number of bytes is to be transmitted. a second number of bytes; wherein the transmission module is configured to: determine each bit according to the first determining module The value of the header, the header encoding of the second encoding header determined by the third determining module, the first compression indication determined by the fourth determining module, and the first number of bytes, generating and transmitting the HTTP to be transmitted Message.

In conjunction with the first possible implementation of the third aspect, in a third possible implementation of the third aspect, the encoding apparatus further includes: a fifth determining module, configured to determine the second compression indication and the first HTTP The order information in the recorded HTTP message, where the second compression indication is used to indicate the value of the second encoding header and the corresponding encoding in the first HTTP packet corresponding to the order information. The value of the header is the same; the transmission module is configured to: determine, according to the value of each bit determined by the first determining module, a header code of the second encoding header determined by the third determining module, The second compression indication determined by the fifth determining module and the sequence information generate and transmit the HTTP message to be transmitted.

With the third aspect, in a fourth possible implementation manner of the third aspect, the encoding apparatus further includes: a sixth determining module, configured to determine a third compression indication and a second byte number, where the third compression indication is used Generating a universal resource identifier URI to be transmitted, the second byte number being associated with a second identical number of bytes, the second identical number of bytes being a URI to be transmitted and the recorded HTTP message The URIs are consecutively the same number of bytes; wherein, the transmission module is configured to: determine, according to the value of each bit determined by the first determining module, the third compression indication determined by the sixth determining module, and the second The number of bytes, the HTTP message to be transmitted is generated and transmitted.

With reference to the third aspect, in a fifth possible implementation manner of the third aspect, the encoding apparatus further includes: a seventh determining module, configured to determine the HTTP version number information to be transmitted and the recorded HTTP packet Whether the version number information is the same; wherein, the transmission module is configured to: when the seventh determining module determines that the HTTP version number information to be transmitted is the same as the version number information in the recorded HTTP message, according to the each bit The value of the bit is generated, and the HTTP message to be transmitted is generated and transmitted, where the HTTP file to be transmitted includes the code header portion map; and the seventh determining module determines the HTTP version number information to be transmitted and the recorded When the version number information in the HTTP packet is different, the HTTP packet to be transmitted is generated and transmitted according to the value of each bit and the HTTP version number information to be transmitted, and the HTTP packet to be transmitted includes the Encoding the header part map and the HTTP version number information to be transmitted.

With reference to the third aspect, in a sixth possible implementation manner of the third aspect, the transmitting module is configured to: generate and transmit a protocol data unit PDU packet including a type field according to the value of each bit, the type The field is used to indicate that the PDU packet is a header encoded and compressed HTTP packet. Text.

With reference to the third aspect, or any one of the first to the sixth possible implementation manners of the third aspect, in a seventh possible implementation manner of the third aspect, the encoding apparatus further includes: a recording module, configured to record, during the first transmission of the HTTP packet, an encoding header value, a URI, and an HTTP version number information of the first transmitted HTTP packet; and an update module, configured to: when not transmitting the HTTP packet for the first time, according to the The HTTP message to be transmitted updates the recorded HTTP message.

With the seventh possible implementation of the third aspect, in an eighth possible implementation manner of the third aspect, the updating module is configured to: if the encoding header of the HTTP packet to be transmitted takes the value and the If the encoding header of the HTTP packet is the same, the encoding header of the recorded HTTP packet is kept unchanged; or if the encoding header of the HTTP packet to be transmitted is the value and the If the value of the encoding header of the HTTP packet is different, the value of the encoding header in the recorded HTTP packet is replaced with the value of the encoding header of the HTTP packet to be transmitted; or if the recording is performed. The HTTP packet has an encoding header that is not included in the HTTP packet to be transmitted, and the encoding header of the recorded HTTP packet is kept unchanged; or if the HTTP packet to be transmitted has the If the encoded HTTP packet does not have an encoding header, the HTTP header to be transmitted has an encoding header that the recorded HTTP packet does not have and its value; or if the HTTP packet to be transmitted Version number information and the recorded If the version number information of the HTTP packet is the same, the version number information of the HTTP packet is kept unchanged; or the version number information of the HTTP packet to be transmitted and the version number information of the recorded HTTP packet The version number information in the recorded HTTP packet is replaced with the version number information of the HTTP packet to be transmitted.

The fourth aspect provides a decoding apparatus for an HTTP packet, where the decoding apparatus includes: an obtaining module, configured to acquire a value of each bit of the encoded header part map in the received HTTP packet; The module, the value of the first bit of the coded part location map obtained by the acquiring module is a value of the first encoding header to be decoded corresponding to the first bit and the recorded HTTP packet When the values of the corresponding encoding headers in the text are the same, the encoding header corresponding to the first bit in the recorded HTTP packet and the value thereof are respectively determined as the first encoding header and the The value of the first encoding header.

With reference to the fourth aspect, in a first possible implementation manner of the fourth aspect, the decoding apparatus further includes: a second determining module, configured to obtain, by the acquiring module, the second bit of the encoding header part map The value indication is the value of the second encoding header to be decoded corresponding to the second bit and the recorded value When the value of the corresponding encoding header in the recorded HTTP packet is different, the second encoding header indicated by the header encoding is determined according to the header encoding in the received HTTP packet.

With reference to the first possible implementation of the fourth aspect, in a second possible implementation manner of the fourth aspect, the decoding apparatus further includes: a third determining module, configured to be used according to the first part of the received HTTP packet a compression indication and a first number of bytes, determining a first identical number of bytes associated with the first number of bytes, wherein the first compression indication is used to indicate that the value of the second encoding header is compressed; And a determining module, configured to determine, according to the first identical number of bytes determined by the third determining module, the counted to be the value of the second encoding header to be decoded.

In conjunction with the first possible implementation of the fourth aspect, in a third possible implementation manner of the fourth aspect, the decoding apparatus further includes: a fifth determining module, configured to be used according to the first part of the received HTTP packet Determining, by the second compression indication, the first HTTP message corresponding to the order information in the recorded HTTP message, where the second compression indication is used to indicate the value of the second coding header and the first The value of the corresponding encoding header in the HTTP packet is the same; the sixth determining module is configured to determine the value of the corresponding encoding header in the first HTTP packet determined by the fifth determining module as the second The value of the encoding header.

With reference to the fourth aspect, in a fourth possible implementation manner of the fourth aspect, the decoding apparatus further includes: a seventh determining module, configured to: according to the third compression indication and the second byte in the received HTTP packet And determining a second identical number of bytes associated with the second number of bytes, wherein the third compression indication is used to indicate that the URI to be decoded is compressed; and the eighth determining module is configured to determine, according to the seventh determining module The second identical number of bytes determines the corresponding consecutive second identical number of bytes in the URI of the recorded HTTP message as the URI to be decoded in the received HTTP message.

With reference to the fourth aspect, in a fifth possible implementation manner of the fourth aspect, the decoding apparatus further includes: a ninth determining module, configured to: when it is determined that the received HTTP packet does not have the HTTP version number information, The version number information in the recorded HTTP packet is determined as the version number information of the received HTTP packet.

With reference to the fourth aspect, in a sixth possible implementation manner of the fourth aspect, the decoding apparatus further includes: a receiving module, configured to receive a protocol data unit PDU packet including a type field, where the type field is used to indicate the PDU packet HTTP headers that are header encoded and compressed.

With reference to the fourth aspect or any one of the first to the sixth possible implementation manners of the fourth aspect, in a seventh possible implementation manner of the fourth aspect, the decoding device further The method includes: a recording module, configured to record an encoding header value, a URI, and an HTTP version number information of an HTTP packet transmitted for the first time when the HTTP packet is first transmitted; and an update module, when the HTTP packet is not transmitted for the first time, Updating the recorded HTTP message according to the received HTTP message.

In conjunction with the seventh possible implementation of the fourth aspect, in an eighth possible implementation manner of the fourth aspect, the updating module is configured to: if the encoded header of the received HTTP packet takes a value and the recorded The encoding header of the HTTP packet has the same value, and the encoding header of the recorded HTTP packet is kept unchanged; or if the encoding header of the received HTTP packet is the value and the recorded value If the encoding header of the HTTP packet is different, the value of the encoding header in the recorded HTTP packet is replaced with the encoding header value of the received HTTP packet; or if the recorded HTTP is recorded. The packet has an encoding header that is not included in the received HTTP packet, and the encoding header of the recorded HTTP packet is kept unchanged; or if the received HTTP packet has the recorded HTTP If the encoded header does not have a packet header, the received HTTP packet has an encoding header that does not have the recorded HTTP packet and its value; or if the received HTTP packet has the version number information and The version of the recorded HTTP message If the number information is the same, the version number information of the recorded HTTP message is kept unchanged; or if the version number information of the received HTTP message is different from the version number information of the recorded HTTP message, The version number information in the recorded HTTP packet is replaced with the version number information of the received HTTP packet.

A fifth aspect provides an apparatus for encoding an HTTP message, the encoding apparatus comprising: a processor, a memory, a bus, and a transmitter; wherein the processor, the memory, and the transmitter are connected by the bus, and the memory is used by the memory And storing, by the processor, the instruction stored in the memory, by the processor, for determining a value of each bit of the code header portion map, where the value of each bit is indicated as the bit The value of the corresponding encoding header to be transmitted is the same as the value of the corresponding encoding header in the recorded HTTP packet; the processor is further configured to generate, according to the value of each bit, the Encoding an HTTP message to be transmitted in the header part map; the processor is further configured to control the sender to send the HTTP message to be transmitted to the receiver, so that the receiver according to the code header part map and the Determining, by the recorded HTTP packet, the first encoding header of the value of the encoding header in the HTTP packet to be transmitted and the value of the corresponding encoding header in the recorded HTTP packet, and The value of the first encoding header.

A sixth aspect provides a decoding apparatus for an HTTP message, the decoding apparatus comprising: a processor, a memory, and a bus; wherein the processor and the memory are connected by the bus, the memory is used to store an instruction, the processor Calling the instruction stored in the memory through the bus to use Obtaining a value of each bit of the coding header part map in the received HTTP packet; the processor is further configured to: use the value of the first bit of the coding header part map as the first bit When the value of the first encoding header to be decoded is the same as the value of the corresponding encoding header in the recorded HTTP packet, the first HTTP bit in the recorded HTTP packet is corresponding. The encoding header and its value are respectively determined as values of the first encoding header and the first encoding header.

Based on the foregoing technical solution, the method for transmitting an HTTP message, the encoding device, and the decoding device in the embodiment of the present invention indicate, by using the value of the bit of the encoding header portion map, the encoding header to be transmitted corresponding to the bit. The value is the same as the value of the corresponding encoding header in the recorded HTTP packet, and the encoding header with the same value and its value are not transmitted, thereby reducing the occupation of the same field in the continuous HTTP packet. Wireless air interface resources, thereby improving resource utilization efficiency. DRAWINGS

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings to be used in the embodiments of the present invention will be briefly described below. Obviously, the drawings described below are only some embodiments of the present invention. Other drawings may also be obtained from those of ordinary skill in the art in view of the drawings.

FIG. 1 is a schematic flowchart of a method for transmitting an HTTP message according to an embodiment of the present invention. FIG. 2 is another schematic flowchart of a method for transmitting an HTTP message according to an embodiment of the present invention.

FIG. 3 is still another schematic flowchart of a method for transmitting an HTTP message according to an embodiment of the present invention.

FIG. 4 is still another schematic flowchart of a method for transmitting an HTTP message according to an embodiment of the present invention.

FIG. 5 is still another schematic flowchart of a method for transmitting an HTTP message according to an embodiment of the present invention.

FIG. 6 is still another schematic flowchart of a method for transmitting an HTTP message according to an embodiment of the present invention.

FIG. 7 is still another schematic flowchart of a method for transmitting an HTTP message according to an embodiment of the present invention.

FIG. 8 is a schematic flowchart of a method for transmitting an HTTP message according to an embodiment of the present invention. FIG. 9 is another schematic flowchart of a method for transmitting an HTTP packet according to an embodiment of the present invention; FIG. 10 is still another schematic flowchart of a method for transmitting an HTTP message according to an embodiment of the present invention. FIG. 10 is still another schematic flowchart of a method for transmitting an HTTP message according to an embodiment of the present invention. Still another schematic flowchart 13 of a method for transmitting an HTTP message is a schematic flowchart of a method for transmitting an HTTP message according to an embodiment of the present invention. FIG. 14 is a method for transmitting an HTTP message according to an embodiment of the present invention. Still another schematic flowchart 15 is a schematic flowchart of a method for reporting coding compression capability according to an embodiment of the present invention. 16 is a schematic flow chart of a method of relocation according to an embodiment of the present invention.

FIG. 17 is another schematic flowchart of a method for relocation according to an embodiment of the present invention.

FIG. 18 is still another schematic flowchart of a method for relocation according to an embodiment of the present invention.

Figure 19 is a schematic block diagram of an encoding device in accordance with an embodiment of the present invention.

Figure 20 is another schematic block diagram of an encoding apparatus in accordance with an embodiment of the present invention.

Figure 21 is still another schematic block diagram of an encoding apparatus according to an embodiment of the present invention.

Figure 22 is still another schematic block diagram of an encoding apparatus in accordance with an embodiment of the present invention.

Figure 23 is still another schematic block diagram of an encoding apparatus in accordance with an embodiment of the present invention.

Figure 24 is still another schematic block diagram of an encoding apparatus according to an embodiment of the present invention.

Figure 25 is still another schematic block diagram of an encoding apparatus according to an embodiment of the present invention.

Figure 26 is a schematic block diagram of a decoding device in accordance with an embodiment of the present invention.

Figure 27 is another schematic block diagram of a decoding device in accordance with an embodiment of the present invention.

28 is still another schematic block diagram of a decoding apparatus according to an embodiment of the present invention.

FIG. 29 is still another schematic block diagram of a decoding apparatus according to an embodiment of the present invention.

Figure 30 is still another schematic block diagram of a decoding device in accordance with an embodiment of the present invention.

Figure 31 is still another schematic block diagram of a decoding device in accordance with an embodiment of the present invention.

Figure 32 is still another schematic block diagram of a decoding device in accordance with an embodiment of the present invention.

Figure 33 is a schematic block diagram of an encoding apparatus according to another embodiment of the present invention.

FIG. 34 is a schematic block diagram of a decoding apparatus according to another embodiment of 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 a part of the embodiments of the present invention, and not all embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present invention without making creative labor are within the scope of the present invention.

It should be understood that the technical solution of the embodiments of the present invention can be applied to various communication systems, for example: Global System of Mobile communication ("GSM") system, code division multiple access (Code Division Multiple Access) Called "CDMA") system, Wideband Code Division Multiple Access ("WCDMA") system, General Packet Radio Service ("General Packet Radio Service"), Long Term Evolution ( Long Term Evolution, called "LTE" system, LTE frequency division duplex (Frequency Division Duplex) system, LTE time division duplex (Time Division Duplex, "TDD"), general purpose A mobile communication system (Unicom Mobile Telecommunication System, referred to as "UMTS") or a Worldwide Interoperability for Microwave Access ("Wireless" called "WiMAX") communication system.

FIG. 1 is a schematic flowchart of a method 100 for transmitting an HTTP message according to an embodiment of the present invention. The method 100 may be performed by an encoding device, which may be a user equipment, such as a UE, or the like. The device, for example, a radio network controller (Radio Network Controller, referred to as "RNC"), an evolved base station (Evolved Node B, called "eNB"), and the like. As shown in FIG. 1, the method 100 includes:

S110. Determine a value of each bit of the coding part location map, where the value of each bit is respectively indicated by the value of the coding header to be transmitted corresponding to the bit and the corresponding coding in the recorded HTTP text. Whether the value of the head is the same;

S120, generating, according to the value of each bit, an HTTP message to be transmitted that includes the code header part map, so that the receiver of the HTTP message to be transmitted is based on the code header part map and Determining, by the recorded HTTP packet, the first encoding header of the encoding header in the HTTP packet to be transmitted and the value of the corresponding encoding header in the recorded HTTP packet, and the first The value of the encoding header.

Specifically, for example, the encoding device may first compare the HTTP message to be transmitted with the recorded The value of each bit of the graph. For example, when the value is the same, the corresponding bit position is the first value, and when the value is different, the corresponding bit position is the second value, so that the value of each bit can be respectively indicated as the corresponding bit to be transmitted. The value of the encoding header is the same as the value of the corresponding encoding header in the recorded HTTP packet. The bit of the encoding header part map has a correspondence with the encoding header in the HTTP packet. Preferably, each bit corresponds to an encoding header in the HTTP packet.

When the value of the first encoding header to be transmitted is the same as the value of the corresponding encoding header in the recorded HTTP packet, the first encoding header and the value of the first encoding header are not transmitted; When the value of the second encoding header to be transmitted is different from the value of the corresponding encoding header in the recorded HTTP packet, the second encoding header and the value of the second encoding header need to be transmitted. . Therefore, the encoding device may generate and transmit a file to be transmitted including the code header portion map according to the value of each bit, thereby facilitating the receiver of the HTTP message to be transmitted according to the code header. The part map and the recorded HTTP message may determine a first encoding header in which the value of the encoding header to be transmitted is the same as the value of the corresponding encoding header in the recorded HTTP packet, and the first The value of an encoding header.

For example, if the value of the encoding header Host to be transmitted is the same as the value of the corresponding encoding header Host in the recorded HTTP packet, the encoding device may correspond to the encoding header Host in the encoding header portion map. If the bit position is 1, the value of the encoding header Host and the encoding header Host is no longer transmitted; the receiver of the HTTP packet may according to the correspondence between the bit position in the encoding header part and the encoding header. Determining that the encoding header corresponding to the bit is Host; on the other hand, the receiver of the HTTP packet can determine the encoding header Host corresponding to the bit in the HTTP packet to be transmitted according to the bit being 1. The value is the same as the value of the encoding header Host in the recorded HTTP packet. The receiver can use the value of the encoding header Host in the recorded HTTP packet as the HTTP packet to be transmitted. The value of the encoding header Host in .

For another example, if the value of the encoding header Accept to be transmitted is different from the value of the corresponding encoding header Accept in the recorded HTTP packet, the encoding header portion map may be corresponding to the encoding header Accept. The bit position is 0. At this time, the value of the encoding header Accept and the encoding header Accept needs to be transmitted.

Therefore, the method for transmitting an HTTP message in the embodiment of the present invention indicates, by using the value of the bit of the encoding header part map, the value of the encoding header to be transmitted corresponding to the bit, and the recorded HTTP packet. Whether the values of the corresponding encoding headers in the text are the same, and the same encoding values are not transmitted. The header and its value can reduce the wireless air interface resources occupied by the same field in consecutive HTTP packets, thereby improving resource utilization efficiency.

It should be understood that, in the embodiment of the present invention, the bit may also have a one-to-many relationship with the encoding header. For example, the value of one bit may represent multiple encoding headers to be transmitted corresponding to the bit. The value is the same as the value of the corresponding multiple encoding headers in the recorded HTTP packet; the bit may have a many-to-one relationship with the encoding header, for example, the value of multiple bits is used. The value of an encoding header to be transmitted corresponding to the multiple bits is the same as the value of the corresponding encoding header in the recorded HTTP packet, and the embodiment of the present invention is not limited thereto.

It should be understood that the sender and the receiver of the HTTP packet may be pre-configured with the correspondence between the bit of the encoding header part map and the encoding header in the HTTP packet, but the embodiment of the present invention is not limited thereto. this.

It should be understood that, in the embodiment of the present invention, the encoding device is a sender of an HTTP packet, and the HTTP packet may be an HTTP request packet or an HTTP response packet, and the embodiment of the present invention is not limited thereto. Specifically, the encoding device may be a packet data convergence protocol ("Packet Data Convergence Protocol") in the sender of the HTTP message, or may be a new coding compression layer in the sender. Embodiments of the invention are not limited thereto.

It should also be understood that, in the embodiment of the present invention, the common headers in the HTTP Request/Response message are encoded, and the common headers for encoding are at most 30, so that the headers can be encoded as 0-9. 11 - 12, 14 - 31 , where 10, 13 are not involved in coding because they are confused with line feeds (Line, LF, OxOA) and Carriage Return (CR, OxOD); these are encoded heads. For the encoding header, for example, the more common encoding headers are: Accept, Host, Referer, User-Agent, Cookie, etc.

In the embodiment of the present invention, the code header map may be used to define a header map, for example, may be set to a total of 32 bits. Starting from the lowest bit of the code header map, each bit can represent one of the foregoing encoding headers. If the encoding header of the HTTP Request packet is the same as the Accept field of the previously recorded HTTP Request packet (Accept field) If the value is "*/*\r\n"), the corresponding bit in the encoding header part map can be set to 1, otherwise set to 0; for the encoding header whose corresponding bit is set to 1, the plaintext no longer needs to be transmitted. The encoding header part map can be placed in front of the Request-Line of the HTTP message (Request-Line is the IP header, the first line after the TCP header, ending with a carriage return, a newline character), that is, the HTTP data is the most front. In the embodiment of the present invention, the encoding header of the encoding header to be transmitted and the corresponding encoding header of the recorded HTTP text may be transmitted in plaintext, or may be further encoded and compressed. To further improve the utilization rate of resources, a detailed description will be made below with reference to FIGS. 2 to 4.

As shown in FIG. 2, the method 100 further includes:

S130. Determine a second encoding header whose value in the encoding header to be transmitted is different from a value of a corresponding encoding header in the recorded HTTP packet, and a value of the second encoding header.

S140. Determine a header encoding of the second encoding header, where the header encoding is used to refer to the second encoding header.

And generating, according to the value of each bit, the HTTP packet to be transmitted that includes the code header part map, including:

S121: Generate and transmit the HTTP message to be transmitted according to the value of each bit, the header code of the second encoding header, and the value of the second encoding header.

Specifically, in the embodiment of the present invention, the second encoding header, together with the colon ":" and the space "," can be replaced by an encoding. For example, the encoding header User-Agent can be encoded as

29, a total of 12 bytes of "User-Agent:" can be replaced with a byte "OxlD", which can further improve the resource utilization rate.

In S121, the HTTP message to be transmitted that is generated and transmitted may include: an encoding header part map and a header encoding of the second encoding header; the HTTP message to be transmitted may further include a second encoding header. The value, or the HTTP packet to be transmitted, may also indicate the value of the second encoding header. The embodiment of the present invention is not limited thereto. That is, the value of the second encoding header may be directly transmitted in plaintext, or the value of the encoding header to be transmitted and the value of the recorded encoding header may be compared character by character, and consecutive consecutive bytes are performed. Encoding compression processing. For example, as shown in FIG. 3, the method 100 further includes:

S150. Determine a first compression indication, where the value of the second compression header is compressed, and the first number of bytes is associated with the first identical number of bytes. The first identical number of bytes is the same number of bytes of the value of the second encoding header to be transmitted and the value of the corresponding encoding header in the recorded HTTP packet;

And generating, according to the value of each bit, the header code of the second encoding header, and the value of the second encoding header, the HTTP packet to be transmitted, including:

5122, according to the value of each bit, the header code of the second coding header, the first Compressing the indication and the first number of bytes, generating and transmitting the HTTP message to be transmitted.

Specifically, when the value of the second encoding header to be transmitted and the value of the corresponding encoding header in the recorded HTTP packet are consecutively in the first range, the The two bytes of a compression indication "and the first byte number" represent consecutive equal bytes, that is, two bytes are compressed to represent the first identical number of bytes, and the second encoding header to be transmitted The remaining characters in the value of the part can still be transmitted in plain text.

That is, in S122, the HTTP message to be transmitted generated and transmitted may include: an encoding header part map, a header encoding of the second encoding header, a first compression indication, and the first byte number; the to-be-transmitted The HTTP message may further include the remaining non-contiguous characters in the value of the second encoding header, or the HTTP message to be transmitted may further indicate the value of the second encoding header by other means, which is implemented by the present invention. The example is not limited to this.

For example, the definition of OxFF is the first compression indication, and the first byte number is the difference between the first identical number of bytes and 3, assuming that the coding header to be transmitted and its value is "User-Agent: mozilla/4.0", The value of the corresponding encoding header in the recorded HTTP packet and its value is "User-Agent: mozilla/3.0", then the encoding header User-Agent to be transmitted is followed by the colon ":" and spaces. " , , can be replaced by a byte "OxlD"; the first 8 characters "mozilla /" in the value of the encoding header User-Agent to be transmitted and the corresponding encoding header in the recorded HTTP message If the corresponding 8 characters in the value are identical, the 8 characters can be replaced by "OxFF 0x05", and the subsequent 3 characters "4.0" in the value to be transmitted are transmitted in plain text or original text.

For example, the first range is more than 3 bytes and less than 258 bytes. If the corresponding bytes are not consecutively more than 3 consecutive, the original byte is transmitted; on the other hand, if the corresponding byte exceeds 258 consecutive words If the sections are the same, the first 258 bytes are replaced by OxFF OxFF, and the corresponding bytes can be re-judged and processed by the same rules.

Therefore, the method for transmitting an HTTP message in the embodiment of the present invention can not only encode and compress the exact same encoding header and its value, but also perform encoding and compression transmission for not completely the same value, thereby being significant The wireless air interface resource occupied by the same field in the continuous HTTP packet is reduced, thereby improving resource utilization efficiency.

It should be understood that, in the embodiment of the present invention, the first number of bytes is associated with the first identical number of bytes, that is, the first number of bytes has a mapping relationship with the first identical number of bytes, for example, the first number of bytes is The function of the first identical number of bytes, the first number of bytes and the first identical number of bytes may also be equal, and the embodiment of the present invention is not limited thereto. It should be understood that, in various embodiments of the present invention, the size of the sequence numbers of the above processes does not mean the order of execution, and the order of execution of each process should be determined by its function and internal logic, and should not be taken to the embodiments of the present invention. The implementation process constitutes any limitation.

In the embodiment of the present invention, on the one hand, the sender and the receiver of the HTTP message may only store the most recent value of each coding header, and only determine whether the current value of the coding header is the same as the previous one. The received encoding headers have the same value. If they are the same, the corresponding encoding header portion map can be set to 1, and the encoding header is no longer transmitted. If different, the corresponding encoding header portion map can be set to 0. The current value of the encoding header and the previous value of the encoding header are compared byte by byte for compression.

On the other hand, the sender of the HTTP message and the record of the receiver can also store multiple values of each coding header, and determine whether the current value of the coding header is corresponding to the HTTP message in the predetermined order. Whether the value of the encoding header is the same, in particular, whether the current value of the encoding header is the same as the value of the corresponding encoding header in the newly transmitted HTTP packet. Similarly, if they are the same, the corresponding code header map can be set to 1, and the code header is no longer transmitted; if different, the corresponding code header map can be set to 0.

In the embodiment of the present invention, when multiple values of each encoding header are stored in the records of the sender and the receiver of the HTTP message, for example, the most recent M of each encoding header is stored in the record (M is an integer) For example, M takes a value of 5), where the Mth is the farthest one, the first one is the nearest one, and so on, the encoding device can first determine whether the current value of the encoding header is the same as the previous one. The received ears of the coding header have the same value. If they are the same, the corresponding coding head part map is set to 1, and the coding header is no longer transmitted; if different, the corresponding coding header part is set to 0, and then Compared with the previous M-1 values, if the same is found, the encoded byte indication in the encoding header is the same as the value stored in the record, for example, User-Agent header value and record. The third one is the same, the user-agent line is replaced by OxlD 0x03; if the same is not found in the first M records, the encoding device can also compare byte by byte with the first one in the record for compression. .

Therefore, in the embodiment of the present invention, optionally, as shown in FIG. 4, the method 100 further includes: S160. Determine a second compression indication and sequence information of the first HTTP packet in the recorded HTTP packet. The second compression indication is used to indicate that the value of the second encoding header is the same as the value of the corresponding encoding header in the first HTTP packet corresponding to the order information;

The generating and transmitting the HTTP message to be transmitted according to the value of the bit, the header code of the second coding header, and the value of the second coding header, including: S123. Generate and transmit the HTTP message to be transmitted according to the value of each bit, the header code of the second coding header, the second compression indication, and the sequence information.

Specifically, for example, the value of the bit in the coding header part indicates the value of the coding header to be transmitted corresponding to the bit and the corresponding coding header in the latest HTTP message recorded. When the value is different, the encoding device may determine the second compression indication and the order information of the first HTTP packet in the recorded HTTP packet, where the second compression indication is used to indicate the second encoding header. The value is the same as the value of the corresponding encoding header in the first HTTP packet corresponding to the order information, so that the encoding device can obtain the header of the second encoding header according to the value of each bit. And the second compression indication and the sequence information, generating and transmitting the HTTP message to be transmitted.

That is, in S123, the HTTP message to be transmitted generated and transmitted may include: an encoding header part map, a header encoding of the second encoding header, a second compression indication, and the order information; the HTTP packet to be transmitted. The text may also include the value of the second encoding header, or the HTTP packet to be transmitted may further indicate the value of the second encoding header by other means, and the embodiment of the present invention is not limited thereto.

It should be understood that the embodiment of the present invention is only limited to the value of the coding header to be transmitted and the latest embodiment recorded. For example, the value of the bit in the coding header part indicates that the value of the corresponding coding header to be transmitted is corresponding to the corresponding coding header in the recorded HTTP message having the first order. When the value is different, the encoding device may also determine the second compression indication and the order information of the first HTTP packet in the recorded HTTP packet, where the HTTP packet indicated by the first sequence may be the recorded HTTP. Any HTTP packet in the packet.

It should be understood that the value of the bit in the coding header part indicates that the value of the coding header to be transmitted corresponding to the bit and the value of the corresponding coding header in the latest HTTP message recorded. When the same, the encoding device can no longer transmit the encoding header and its value.

Therefore, the method for transmitting an HTTP message in the embodiment of the present invention indicates, by using the value of the bit of the encoding header part map, the value of the encoding header to be transmitted corresponding to the bit, and the recorded HTTP packet. Whether the value of the corresponding encoding header in the text is the same, and the encoding header with the same value and its value are not transmitted, so that the wireless air interface resources occupied by the same field in the continuous HTTP packet can be reduced, thereby improving resources. Use efficiency.

It should be understood that, in the embodiment of the present invention, the encoding apparatus may also first determine whether the current value of the encoding header is the same as the value of the corresponding encoding header in the HTTP message of the predetermined order, so as to be The value of each bit of the coded header portion map is not limited to this embodiment.

The coding method of the coding header and its value is described in detail above with reference to FIG. 1 to FIG. 4. The coding method of the URI, version number information and the like included in the HTTP message will be described below with reference to FIG. 5 to FIG.

As shown in FIG. 5, the method 100 for transmitting an HTTP packet according to an embodiment of the present invention further includes:

S170. Determine a third compression indication, where the third compression indication is used to indicate that the universal resource identifier URI to be transmitted is compressed, and the second number of bytes is associated with the second identical number of bytes. The second identical number of bytes is the number of consecutive consecutive URIs of the URI to be transmitted and the URI in the recorded HTTP message;

S124. Generate, and transmit, according to the value of each bit, the third compression indication, and the second number of bytes, the HTTP message to be transmitted.

Specifically, similar to the encoding compression scheme of the value of the second encoding header to be transmitted, for the URI to be transmitted, when the URI to be transmitted and the value of the corresponding URI in the recorded HTTP packet are consecutively the same When the number of bytes is in the second range, the two bytes of "third compression indication" and "second byte number" can be used to represent consecutive equal bytes, that is, two bytes are compressed to represent the second identical The bytes are bytes, and the remaining characters in the URI to be transmitted can still be transmitted in plaintext.

That is, in S124, the HTTP message to be transmitted that is generated and transmitted may include: an encoding header part map, a third compression indication, and the second byte number; the HTTP message to be transmitted may further include a to-be-transmitted The remaining non-contiguous characters in the URI. It should be understood that the HTTP packet to be transmitted may further include a header encoding of the second encoding header, and may further include a first compression indication and the first byte number, etc., and the HTTP packet to be transmitted may also pass other The mode indicates the value of the second coding header, etc., and the embodiment of the present invention is not limited thereto. For example, the URI to be transmitted and the URI of the record are compared character by character. If the corresponding byte has at least 3 consecutive or more consecutive 258 or less, the two bytes are represented by "compression indication OxFF""N-3". Consecutively equal bytes, where N is the number of consecutive identical bytes, and spaces before the URI participate in compression. For example, the URI of the previous request is " /client/qj wl5_MB_201107275457.gif , and the requested URI is " /client/jnzg— MB— 201107142728.jpg", where "/client/" has the same 9 consecutive characters, then The 9 characters of the URI of the second request may be replaced by OxFF 0x06, and there are no more than 3 consecutive identical characters in the subsequent characters, and the original characters are transmitted; if the corresponding bytes are not consecutive If three or more are the same, the original text is transmitted; if the corresponding byte has more than 258 consecutive bytes, the first 258 bytes are replaced by OxFF OxFF, and the corresponding bytes are judged and processed by the same rule.

It should be understood that, in the embodiment of the present invention, the “first range” and the “second range” may be the same or different, and the embodiment of the present invention is not limited thereto. It should be understood that, in the embodiment of the present invention, the "first compression indication", the "second compression indication", and the "third compression indication" may be the same. For example, each compression indication is OxFF, and each compression indication may also be different. Or partially identical, the embodiment of the present invention is not limited thereto.

In the embodiment of the present invention, optionally, as shown in FIG. 6, the method 100 further includes:

S180. Determine whether the HTTP version number information to be transmitted is the same as the version number information in the recorded HTTP message.

When the HTTP version number information to be transmitted is the same as the version number information in the recorded HTTP message, the HTTP message to be transmitted is generated and transmitted according to the value of each bit. The transmitted HTTP message includes the coding header part map;

5126, when the HTTP version number information to be transmitted is different from the version number information in the recorded HTTP message, generating and transmitting the value according to the value of each bit and the HTTP version number information to be transmitted. The HTTP message to be transmitted includes the code header part map and the HTTP version number information to be transmitted.

Specifically, in the embodiment of the present invention, when the HTTP version number information to be transmitted is the same as the version number information in the recorded HTTP message, the HTTP version number information may not be transmitted; otherwise, when the HTTP version to be transmitted is When the number information is different from the version number information in the recorded HTTP message, the HTTP version number information needs to be transmitted.

That is, in S125, the HTTP file to be transmitted generated and transmitted may include an encoding header part map, but may not include the HTTP version number information to be transmitted. In S126, the HTTP packet to be transmitted is generated and transmitted. The encoding header part map and the HTTP version number information to be transmitted may be included; it should be understood that the HTTP message to be transmitted may further include a header encoding of the second encoding header, a first compression indication, a first byte number, The third compression indication or the third byte number, etc., the HTTP message to be transmitted may also indicate the value of the second coding header, etc. by other means, and the embodiment of the present invention is not limited thereto. Therefore, the method for transmitting an HTTP message in the embodiment of the present invention indicates, by using the value of the bit of the encoding header part map, the value of the encoding header to be transmitted corresponding to the bit, and the recorded HTTP packet. Whether the value of the corresponding encoding header in the text is the same, and the encoding header with the same value and its value are not transmitted, so that the wireless air interface resources occupied by the same field in the continuous HTTP packet can be reduced, thereby improving resources. Use efficiency.

In the embodiment of the present invention, as shown in FIG. 7, the HTTP message to be transmitted, including the code header part map, is generated and transmitted according to the value of each bit, and includes:

And according to the value of each bit, a protocol data unit PDU packet including a type field is generated and transmitted, and the type field is used to indicate that the PDU packet is a header encoded and compressed HTTP message.

Specifically, in the PDCP data transmission process of the packet data convergence protocol, the sender may indicate that the data packet is an HTTP message that has been encoded and compressed by the HTTP header by adding indication information in the header portion of the PDCP. To this end, the PDCP protocols 25.323 and 36.323 can be modified, and a new PDU type field can be added. For example, as shown in Table 1, this type field is used to indicate that the current PDU is encoded and compressed by the HTTP header.

Table 1

The PDU type field may take values of "011", "100", "101", etc. When the PDU type field has a value of "011", it may indicate that the data has been encoded and compressed by the HTTP header; When the value is "100", it can be expressed as a PDCP data PDU and is subjected to HTTP header encoding and compression. When the PDU type field is "101", it can be expressed as a PDCP SeqNum PDU and has been HTTP header encoded and compression.

It should be understood that the foregoing values of the PDU type field and their meanings are only examples, and the embodiment of the present invention is not limited thereto.

In the embodiment of the present invention, optionally, as shown in FIG. 7, the method 100 further includes:

S190, when encoding the HTTP packet for the first time, recording the encoding header value, URI, and HTTP version number information of the first transmitted HTTP packet;

S195: Update the recorded HTTP message according to the HTTP message to be transmitted when the HTTP message is not transmitted for the first time. It should be understood that, in the embodiment of the present invention, the first transmission of the HTTP Request message after the UE transitions from the RRCJDLE state to the RRC_Connected state may be referred to as the first transmission of the HTTP message; the UE is in the serving radio network subsystem (Serving Radio Network Subsystem) , the cylinder is called "SRNS". The relocation is completed. The first HTTP HTTP transmission message is received after the start of the HTTP HTTP HEADER CODING AND COMPRESSION message. It can also be called the first transmission of the HTTP message. . It should be understood that the HTTP Response packet transmitted for the first time is also referred to as the first transmission of the HTTP packet, and the embodiment of the present invention is not limited thereto.

In the embodiment of the present invention, optionally, updating the recorded HTTP message according to the HTTP message to be transmitted includes:

If the value of the encoding header of the HTTP packet to be transmitted is the same as the value of the encoding header of the recorded HTTP packet, the encoding header of the recorded HTTP packet and the value thereof are kept unchanged; Or

If the value of the encoding header of the HTTP packet to be transmitted is different from the value of the encoding header of the HTTP packet, the value of the encoding header in the recorded HTTP packet is replaced with the value of the encoding header. The value of the encoding header of the transmitted HTTP packet; or

If the recorded HTTP packet has an encoding header that is not included in the HTTP packet to be transmitted, the encoding header of the recorded HTTP packet is kept unchanged; or

If the HTTP packet to be transmitted has an encoding header that is not included in the recorded HTTP packet, the HTTP header to be transmitted has an encoding header that is not included in the recorded HTTP packet and is obtained. Value; or

If the version number information of the HTTP packet to be transmitted is the same as the version number information of the recorded HTTP packet, the version number information of the recorded HTTP packet is kept unchanged; or

If the version number information of the HTTP packet to be transmitted is different from the version number of the HTTP packet, the version number information of the recorded HTTP packet is replaced with the HTTP packet to be transmitted. Version number information.

It should be understood that the encoding apparatus may perform the update processing on the recorded HTTP message according to one or more of the foregoing rules, but the embodiment of the present invention is not limited thereto.

It should also be understood that, in the scheme for recording a plurality of HTTP 艮 messages according to the present invention, when the number of recorded HTTP messages is less than a preset value, the HTTP message to be transmitted is recorded; when the recorded HTTP message is recorded When the number of the packets is equal to the preset value, the latest HTTP packet in the recorded HTTP packet is updated according to the HTTP packet to be transmitted, and may be according to one of the above rules or A plurality of updates are performed on the latest HTTP packet that has been recorded, but the embodiment of the present invention is not limited thereto.

The test is performed on the live network data. The result shows that the method of transmitting HTTP packets according to the embodiment of the present invention compresses the uplink data by 67% of the HTTP Request message and accounts for 17% of the total uplink data. For the message, the data compressed by the upstream accounted for 75% of the HTTP Request 4, accounting for 19% of the total uplink data.

It should be understood that, in various embodiments of the present invention, the size of the sequence numbers of the above processes does not mean the order of execution, and the order of execution of each process should be determined by its function and internal logic, and should not be taken to the embodiments of the present invention. The implementation process constitutes any limitation.

1 to 7, a method for transmitting an HTTP message according to an embodiment of the present invention is described in detail from the perspective of an encoding apparatus. Hereinafter, an embodiment according to the present invention will be described from the perspective of a decoding apparatus with reference to FIG. 8 to FIG. The method of transmitting HTTP messages.

FIG. 8 is a schematic flowchart of a method 200 for transmitting an HTTP message, which may be performed by a decoding device, which may be a user equipment, such as a UE, etc., or a network, according to an embodiment of the present invention. Equipment, such as RNC, eNB, etc. As shown in FIG. 8, the method 200 includes:

S210: Obtain a value of each bit of the coding header part map in the received HTTP packet. S220. The value of the first bit in the coding header part indication is indicated by the first bit. When the value of the first encoding header to be decoded is the same as the value of the corresponding encoding header in the recorded HTTP packet, the encoding header corresponding to the first bit in the recorded HTTP packet is used. The part and its value are respectively determined as values of the first coding header and the first coding header.

Specifically, the decoding apparatus may obtain, according to the received HTTP packet, a value of each bit of the encoded header part map in the received HTTP packet, where the value of each bit is indicated as the bit respectively. The value of the corresponding encoding header to be decoded is the same as the value of the corresponding encoding header in the recorded HTTP packet. For example, when the bit is the first value, it may represent the encoding header to be decoded. The value is the same as the value of the corresponding encoding header in the recorded HTTP packet; When the bit is the second value, it can indicate that the value is different. The bit of the coding header part map has a correspondence relationship with the coding header in the HTTP message. Preferably, each bit corresponds to one coding header in the HTTP message.

Therefore, the value of the first bit in the coding header portion is indicated as the value of the first coding header to be decoded corresponding to the first bit and the corresponding coding header in the recorded HTTP message. When the value of the part is the same, the encoding header corresponding to the first bit in the recorded HTTP packet and the value thereof may be determined as the first encoding header and the first encoding header, respectively. The value.

For example, the receiver of the HTTP text can determine the encoding header Host and the value corresponding to the bit in the received HTTP packet according to the bit position of the encoding header part map, and the encoding in the HTTP packet. The host and the value of the header are the same, so that the receiver can use the encoding header Host and its value in the recorded HTTP packet as the corresponding encoding header and its value in the HTTP packet received this time.

Therefore, the method for transmitting an HTTP packet in the embodiment of the present invention determines the value of the encoding header to be decoded corresponding to the bit according to the value of the bit of the encoding header portion map, and the recorded HTTP packet. Whether the values of the corresponding coding headers in the text are the same, so that the coding header and its value in the received HTTP message can be determined according to the coding header part map, thereby reducing the occupation of the same field in the continuous HTTP message. Wireless air interface resources and can improve resource utilization efficiency.

It should also be understood that, in the embodiment of the present invention, the decoding device is a receiver of an HTTP message,

The HTTP packet can be either an HTTP request message or an HTTP response message. The embodiment of the present invention is not limited thereto. Specifically, the decoding device may be a packet data convergence protocol ("Packet Data Convergence Protocol") in the receiver of the HTTP message, or may be a new coding compression layer in the receiver. Embodiments of the invention are not limited thereto.

In the embodiment of the present invention, optionally, as shown in FIG. 9, the method 200 further includes:

S230. The value of the second bit in the coding part location map is indicated as corresponding to the second bit. When the value of the second encoding header to be decoded is different from the value of the corresponding encoding header in the recorded HTTP packet, the header encoding finger is determined according to the header encoding in the received HTTP packet. The second encoding header of the generation.

For example, in the embodiment of the present invention, for the second encoding header together with the colon ":" and the space ",", the encoding may be replaced by, for example, the encoding header User-Agent may be encoded as 29, A total of 12 bytes of "User-Agent:" can be replaced with one byte "OxlD". Therefore, the decoding device can determine the byte as the encoding header User-Agent according to the byte "OxlD", and Subsequent colons ":" and spaces ",,.

It should be understood that the second encoding header can also be transmitted in plaintext, in which case the transmitted information can be obtained without decoding.

In the embodiment of the present invention, the value of the second encoding header may be directly transmitted in plaintext, or the value of the encoding header to be transmitted and the value of the encoded encoding header to be transmitted may be compared character by character. The same byte is encoded and compressed. At this time, for example, as shown in FIG. 10, the decoding method 200 further includes:

S240. Determine, according to the first compression indication and the first number of bytes in the received HTTP packet, a first identical number of bytes associated with the first number of bytes, where the first compression indication is used to indicate the The value of the second encoding header is compressed;

S250. Determine, according to the first identical number of bytes, a byte of the corresponding consecutive first identical number of bytes in the value of the corresponding encoding header in the recorded HTTP packet as the second encoding header. The value to be decoded.

For example, the decoding device can read the code header portion map, and take the value of the corresponding HTTP header record for the bit of 1; the decoding device can read the first line of the HTTP message body, that is, Request-Line, if When the OxFF character is encountered, the value N of the following byte is read, and then N+3 bytes are taken in the corresponding position in the recorded URI; if there is no HTTP version number information in the first line, the recorded HTTP version number information is taken. For example, the decoding device reads the first byte of each line of the HTTP message. If the byte is the encoding of the HTTP header, the character recovers the header and the colon ":" and the space "", for example, User-Agent is encoded as 29, the first byte is "User-Agent:" if it is "OxlD"; For subsequent bytes, if OxFF character is encountered, the value of the next byte is read N Then, take N+3 bytes at the position corresponding to the value of the recorded encoding header, otherwise take the received original text; if the byte is not the encoding of the HTTP header, the line directly takes the original text, and does not need to be decompressed. In the embodiment of the present invention, optionally, as shown in FIG. 11, the method 200 further includes: S260, determining, according to the second compression indication and the sequence information in the received HTTP packet, the recorded HTTP packet. a first HTTP packet corresponding to the sequence information, where the second compression indication is used to indicate that the value of the second encoding header is the same as the value of the corresponding encoding header in the first HTTP packet;

S270. Determine a value of the corresponding encoding header in the first HTTP packet as a value of the second encoding header.

In the embodiment of the present invention, optionally, as shown in FIG. 12, the method 200 further includes: S280, determining, according to the third compression indication and the second byte number in the received HTTP packet, the second a second identical number of bytes associated with the number of bytes, wherein the third compressed indication is used to indicate that the URI to be decoded is compressed;

S290. Determine, according to the second identical number of bytes, a corresponding consecutive second identical number of bytes in the URI of the recorded HTTP message as the URI to be decoded in the received HTTP message.

In the embodiment of the present invention, when there is no HTTP version number information in the HTTP packet received by the decoding device, it indicates that the received HTTP version number information is the same as the version number information in the recorded HTTP packet, thereby The version number information of the received HTTP packet is determined as the version number information of the received HTTP packet. Conversely, when the HTTP version number information exists in the received HTTP packet, the HTTP version number information of the received HTTP packet is displayed. The version number information of the received HTTP packet is the version number information of the HTTP packet transmitted.

Therefore, as shown in FIG. 13, the method 200 further includes:

S300, when determining that the received HTTP packet does not have the HTTP version number information, determining the version number information in the recorded HTTP packet as the version number of the received HTTP packet, in the embodiment of the present invention, The receiving end may determine, according to the PDU type field of the PDCP header, whether the PDCP PDU is compressed by HTTP header encoding, and the type field may be used to indicate the Whether the PDU packet is HTTP ^ encoded with header encoding compression. For packets that are encoded and compressed by HTTP, they are decoded or decompressed.

It should be understood that, in the embodiment of the present invention, the HTTP message is compressed by encoding the HTTP message; similarly, the HTTP message is decompressed by decoding the HTTP file, but the present invention is implemented. The example is not limited to this.

Specifically, in the embodiment of the present invention, as shown in FIG. 13, the method 200 further includes:

S310. Receive a protocol data unit PDU packet including a type field, where the type field is used to indicate that the PDU packet is a header encoded and compressed HTTP.

It should be understood that the encoding method described from the perspective of the encoding device corresponds to the decoding method described from the perspective of the decoding device, and is not described herein again.

In the embodiment of the present invention, as shown in FIG. 14, the method 200 further includes:

S320, when encoding the HTTP packet for the first time, recording the encoding header value, URI, and HTTP version number information of the first transmitted HTTP packet;

S330: Update the recorded HTTP packet according to the received HTTP packet when the HTTP packet is not transmitted for the first time.

Optionally, the updating the recorded HTTP packet according to the received HTTP packet includes:

If the value of the encoding header of the received HTTP packet is the same as the value of the encoding header of the recorded HTTP packet, the encoding header of the recorded HTTP packet is kept unchanged; or

If the value of the encoding header of the received HTTP packet is different from the value of the encoding header of the recorded HTTP packet, the value of the encoding header in the recorded HTTP packet is replaced by the received value. The encoding header of the HTTP packet takes the value; or

If the recorded HTTP packet has an encoding header that the received HTTP packet does not have, the encoding header of the recorded HTTP packet is kept unchanged; or

If the received HTTP packet has an encoding header that is not included in the recorded HTTP packet, record the received HTTP packet with an encoding header that the recorded HTTP packet does not have and its value; Or

If the version number information of the received HTTP packet is the same as the version number information of the recorded HTTP packet, the version number information of the recorded HTTP packet is kept unchanged; or

If the version number of the received HTTP packet and the version of the recorded HTTP packet If the number information is different, the version number information in the recorded HTTP packet is replaced with the version number information of the received HTTP packet.

It should be understood that, in the embodiment of the present invention, the first transmission of the HTTP Request message after the UE transitions from the RRC JDLE state to the RRC_Connected state may be referred to as the first transmission of the HTTP message; the UE is in the serving radio network subsystem (Serving Radio Network Subsystem) , the cylinder is called "SRNS". The relocation is completed. The first HTTP HTTP transmission message is received after the start of the HTTP HTTP HEADER CODING AND COMPRESSION message. It can also be called the first transmission of the HTTP message. . It should be understood that the HTTP response packet transmitted for the first time is also referred to as the first transmission of the HTTP packet, and the embodiment of the present invention is not limited thereto.

In the embodiment of the present invention, when the receiver cannot correctly decode and decompress the received data, the receiver may construct a PDCP PDU, and request the sender to transmit the recorded URI, the HTTP version number, the encoding header value, and the like. After receiving the request PDU, the sender may send the recorded URI, HTTP version number, encoding header value and other information to the receiver. If the receiver determines that the overall efficiency is lower than if the HTTP header encoding is not used, the header encoding compression may be suspended.

It should also be understood that, in various embodiments of the present invention, the size of the sequence numbers of the above processes does not imply a sequence of execution orders, and the order of execution of the processes should be determined by its function and internal logic, and should not be implemented by the present invention. The implementation of the examples constitutes any limitation.

In the embodiment of the present invention, in order to implement the HTTP header encoding and compression function, a process involving the UE capability reporting of the control plane and the network configuration to enable the function is required.

For example, as shown in FIG. 15, in S410, the UE reports to the network device whether the HTTP header coding and compression capability report is supported, and the network device is, for example, an RNC, or the network device is an eNB. The embodiment of the present invention is not limited thereto; in S420, if the network device also supports the HTTP header encoding and compression function, the network The device can configure the user equipment to enable the HTTP header coding and compression algorithm (Enable HTTP header coding and compression algorithm);

In S430, the UE may reply to the network device (Enable HTTP header coding and compression algorithm Response) to report the encoding result of the HTTP header and the startup result of the compression function.

In the embodiment of the present invention, the handover in the normal RNC does not involve process modification, for inter-RNC handover, but not with SRNS relocation, and the source RNC supports HTTP header coding and compression, and the target RNC does not. In the scenario of supporting HTTP header encoding and compression, the source RNC decides to perform inter-RNC handover without SRNS relocation, and through the background configuration query to the target RNC does not support HTTP header encoding and compression, the source RNC may go to the UE. The STOP HTTP HEADER CODING AND COMPRESSION message is sent to inform the UE to stop using the HTTP header encoding and compression function; after that, the source RNC, the target RNC, and the UE jointly perform the handover procedure.

In the embodiment of the present invention, in the SRNS relocation process, the PDCP entity on the network side is transferred from the source RNC to the target RNC, and can be divided into three cases: 1) Both the source RNC and the target RNC support HTTP header coding and Compression function; 2) The source RNC supports HTTP header encoding and compression, the target RNC does not support HTTP header encoding and compression; 3) The source RNC does not support HTTP header encoding and compression, and the target RNC supports HTTP header encoding and compression. Compression function.

1) Both the source RNC and the target RNC support HTTP header coding and compression. In this scenario, the SRNS relocation process is shown in Figure 16.

In S510, the source RNC sends a relocation request (RELOCATION REQUIRED) message to the core network CN, and the information element IE "Source RNC To Target RNC Transparent Container" of the relocation request message may be added with the HTTP header encoding compression enabled. IE "HTTP header coding and compression on-going", and the IE "HTTP header coding and compression context" of the previous encoding header.

In S520, the CN sends a relocation request (RELOCATION REQUEST) message to the target RNC, where the relocation request message may include an IE "Source RNC To Target RNC Transparent Container" in the RELOCATION REQUIRED message.

In S530, the target RNC sends a relocation request response (RELOCATION) to the CN.

REQUEST ACKNOWLEDGE ) message, the IE "Target" of the relocation request reply message IE "Target RNC support HTTP header coding and compression" can be added to RNC To Source RNC Transparent Container".

In S540, the CN sends a relocation command (RELOCATION COMMAND) message to the source RNC, where the relocation command message may include an IE "Target RNC To Source RNC Transparent Container" in the RELOCATION REQUEST ACKNOWLEDGE message.

Therefore, the source RNC can know that the target RNC also supports the HTTP header encoding and compression function, so that the related network element can perform the relocation process.

2) The source RNC supports the HTTP header encoding and compression function. The target RNC does not support the HTTP header encoding and compression function. In this scenario, the SRNS relocation process is shown in Figure 17.

In S610, the source RNC sends a relocation request (RELOCATION REQUIRED) message to the CN, and the IE "Source RNC To Target RNC Transparent Container" of the relocation request message may add an IE "HTTP header" that has started HTTP header encoding compression. Coding and compression on-going" , and the IE "HTTP header coding and compression context" of the previously encoded header value information.

In S620, the CN sends a Relocation Request (RELOCATION REQUEST) message to the target RNC, which may include an IE "Source RNC To Target RNC Transparent Container" in the RELOCATION REQUIRED message.

In S630, the target RNC sends a RELOCATION REQUEST ACKNOWLEDGE message to the CN. In the IE "Target RNC To Source RNC Transparent Container" of the relocation request response message, an IE "Target RNC NOT support HTTP" may be added. Header coding and compression" , or IE "Target RNC support HTTP header coding and compression" may not be included in IE "Target RNC To Source RNC Transparent Container".

In S640, the CN sends a relocation command (RELOCATION COMMAND) message to the source RNC, which may include an IE "Target RNC To Source RNC Transparent Container" in the RELOCATION REQUEST ACKNOWLEDGE message.

In S650, the source RNC sends a Stop ACK HTTP HEADER CODING AND COMPRESSION message to the UE, informing the UE to stop using the HTTP header encoding and compression function. Thereby, each related network element performs a relocation process.

For the above process, the existing message can be modified without any modification. Instead, the source RNC can query the background configuration to obtain information about whether the target RNC supports the function, and then the source RNC receives the CN relocation command (RELOCATION COMMAND) message. After that, the UE can directly send a message to the UE to stop the HTTP header encoding and compression (STOP HTTP HEADER CODING AND COMPRESSION), and notify the UE to stop using the HTTP header encoding and compression function.

3) The source RNC does not support HTTP header encoding and compression. The target RNC supports HTTP header encoding and compression. In this scenario, the SRNS relocation process is shown in Figure 18.

In S710, the source RNC sends a relocation request (RELOCATION REQUIRED) message to the CN, where the IE "Source radio access Capability" in the IE "Source RNC To Target RNC Transparent Container" of the relocation request message is in the IE "PDCP capability" , you can add IE "HTTP header coding and compression capability".

In S720, the CN sends a Relocation Request (RELOCATION REQUEST) message to the target RNC, which may include an IE "Source RNC To Target RNC Transparent Container" in the RELOCATION REQUIRED message.

In S730, the target RNC sends a RELOCATION REQUEST ACKNOWLEDGE message to the CN, which may include the IE "Target RNC To Source RNC Transparent Container".

In S740, the CN sends a Relocation Command (RELOCATION COMMAND) message to the target RNC, which may include the IE "Target RNC To Source RNC Transparent Container" in the RELOCATION REQUEST ACKNOWLEDGE message.

In S750, after the re-location process is performed by the relevant network element, since both the network device and the UE support the HTTP header encoding and compression function, the target RNC sends a start HTTP header encoding and compression function (START HTTP HEADER CODING AND COMPRESSION) to the UE. The message informs the UE to start using HTTP header encoding and compression.

For the above process, the existing message can be modified. For example, after the relocation process is completed, the new RNC sends a capability query message to the UE, and the UE replies to its own capability, and carries whether to support HTTP header coding and compression. Information, if the UE supports the function, the new RNC sends a START HTTP HEADER CODING AND COMPRESSION message to the UE, informing the UE to start using the HTTP header encoding. And compression.

It should be understood that when the user equipment and the network device record multiple HTTP messages, the network configuration initiates an HTTP header coding and compression algorithm, and the target RNC sends the UE to the UE. The HTTP HTTP header encoding and compression function (START HTTP HEADER CODING AND COMPRESSION ) message can carry the configuration parameter M, and M represents the number of values of the encoding header stored in the record.

Therefore, the method for transmitting an HTTP message in the embodiment of the present invention indicates, by using the value of the bit of the encoding header part map, the value of the encoding header to be transmitted corresponding to the bit, and the recorded HTTP packet. The value of the corresponding encoding header in the text is the same, and the encoding headers with the same value are not transmitted, so that the wireless air interface resources occupied by the same field in the continuous HTTP packet can be reduced, thereby improving resource utilization efficiency.

The method for transmitting an HTTP message according to an embodiment of the present invention is described in detail above with reference to FIG. 1 to FIG. 18. The encoding device and decoding of an HTTP message according to an embodiment of the present invention will be described in detail below with reference to FIG. 19 to FIG. Device.

Fig. 19 shows a schematic block diagram of an encoding device 800 in accordance with an embodiment of the present invention. As shown in Fig. 19, the encoding device 800 includes:

The first determining module 810 is configured to determine a value of each bit of the coding header part map, where the value of each bit is respectively indicated as the value of the coding head to be transmitted corresponding to the bit and the recorded value Whether the value of the corresponding encoding header in the HTTP packet is the same;

The transmitting module 820 is configured to generate, according to the value of each bit determined by the first determining module 810, an HTTP packet to be transmitted that includes the encoding header part map, to facilitate the HTTP packet to be transmitted. The receiving end of the text determines the value of the encoding header in the HTTP packet to be transmitted and the corresponding encoding header in the recorded HTTP packet according to the encoding header part map and the recorded HTTP packet. The first encoding header having the same value and the value of the first encoding header.

Therefore, the encoding apparatus of the HTTP packet in the embodiment of the present invention indicates the value of the encoding header to be transmitted corresponding to the bit by using the value of the bit of the encoding header part map, and the recorded HTTP packet. The value of the corresponding encoding header in the text is the same, and the encoding headers with the same value are not transmitted, so that the wireless air interface resources occupied by the same field in the continuous HTTP packet can be reduced, thereby improving resource utilization efficiency.

In the embodiment of the present invention, optionally, as shown in FIG. 20, the encoding apparatus 800 further includes: a second determining module 830, configured to determine a value in the encoding header to be transmitted and the recorded value a second encoding header having a different value of the corresponding encoding header in the HTTP packet, and a value of the second encoding header;

a third determining module 840, configured to determine a header encoding of the second encoding header determined by the second determining module 830, where the header encoding is used to refer to the second encoding header;

The transmission module 820 is configured to: determine, according to the value of the bit determined by the first determining module 810, a header code of the second encoding header determined by the third determining module 840, and the second determining The value of the second encoding header determined by the module 830 is generated and transmitted, and the HTTP packet to be transmitted is generated and transmitted.

In the embodiment of the present invention, optionally, as shown in FIG. 21, the encoding apparatus 800 further includes: a fourth determining module 850, configured to determine a first compression indication and a first number of bytes, where the first compression indication is used The value indicating the second encoding header is compressed, and the first byte number is associated with the first identical number of bytes, where the first identical number of bytes is the value of the second encoding header to be transmitted. And the transmission module 820 is configured to: determine, according to the value of the each bit determined by the first determining module 810, the header code of the second encoding header determined by the third determining module 840, The first compression indicator determined by the fourth determining module 850 and the first number of bytes generate and transmit the HTTP message to be transmitted.

In the embodiment of the present invention, optionally, as shown in FIG. 22, the encoding apparatus 800 further includes: a fifth determining module 860, configured to determine a second compression indication, and the first HTTP packet is in the recorded HTTP report. The order information in the text, where the second compression indication is used to indicate that the value of the second encoding header is the same as the value of the corresponding encoding header in the first HTTP packet corresponding to the order information;

The transmission module 820 is configured to: determine, according to the value of the bit determined by the first determining module 810, a header code of the second encoding header determined by the third determining module 840, and the fifth determining The second compression indication determined by the module 860 and the sequence information generate and transmit the HTTP message to be transmitted.

In the embodiment of the present invention, optionally, as shown in FIG. 23, the encoding apparatus 800 further includes: a sixth determining module 870, configured to determine a third compression indication and a second number of bytes, where the third compression indication is used The universal resource identifier URI indicating that the second Byte is to be transmitted is associated with the second identical number of bytes, the second identical number of bytes being the URI to be transmitted and the recorded HTTP message. The URIs are consecutively the same number of bytes; The transmission module 820 is configured to: generate, according to the value of the each bit determined by the first determining module 810, the third compression indication determined by the sixth determining module 870, and the second number of bytes. Transmit the HTTP ^ message to be transmitted.

In the embodiment of the present invention, optionally, as shown in FIG. 24, the encoding apparatus 800 further includes: a seventh determining module 880, configured to determine the HTTP version number information to be transmitted and the recorded

Whether the version number information in the HTTP packet is the same;

The transmission module 820 is configured to:

When the seventh determining module 880 determines that the HTTP version number information to be transmitted is the same as the version number information in the recorded HTTP message, the HTTP to be transmitted is generated and transmitted according to the value of each bit. a packet, the HTTP message to be transmitted includes the code header portion map;

When the seventh determining module 880 determines that the HTTP version number information to be transmitted is different from the version number information in the recorded HTTP message, the value of each bit and the HTTP version number to be transmitted are determined according to the value of the bit number. The HTTP message to be transmitted is generated and transmitted, and the HTTP message to be transmitted includes the code header part map and the HTTP version number information to be transmitted.

In the embodiment of the present invention, optionally, the transmission module 820 is configured to:

In the embodiment of the present invention, optionally, as shown in FIG. 25, the encoding apparatus 800 further includes: a recording module 890, configured to record the HTTP transmitted for the first time when transmitting the HTTP packet for the first time.

4 encoding the encoding header value, URI and HTTP version number information;

The update module 895 is configured to update the recorded HTTP message according to the HTTP message to be transmitted when the HTTP message is not transmitted for the first time.

In the embodiment of the present invention, the update module 895 is optionally used to:

If the recorded HTTP packet has an encoding header that the HTTP packet to be transmitted does not have And maintaining the encoding header of the recorded HTTP packet and its value unchanged; or if the HTTP packet to be transmitted has an encoding header that the recorded HTTP packet does not have, The transmitted HTTP packet has an encoding header that the recorded HTTP packet does not have and its value; or

It should be understood that the encoding apparatus 800 of the HTTP message according to the embodiment of the present invention may correspond to the sender of the method for transmitting the HTTP message in the embodiment of the present invention, and the above and other operations of the respective modules in the encoding apparatus 800 and/or For the purpose of implementing the corresponding processes of the respective methods in FIG. 1 to FIG. 18, the functions are not described herein.

As shown in FIG. 26, an embodiment of the present invention further provides a decoding apparatus, where the decoding apparatus 900 includes:

The earphone 5Uf block 910 is configured to obtain the value of each bit position of the coded header part map in the received HTTP message;

The first determining module 920 is configured to: the value of the first bit of the coded part location map obtained by the acquiring module 910 is the value of the first encoding header to be decoded corresponding to the first bit When the value of the corresponding encoding header in the recorded HTTP packet is the same, the encoding header corresponding to the first bit in the recorded HTTP packet and the value thereof are respectively determined as the first The encoding header and the value of the first encoding header.

Therefore, the decoding apparatus of the HTTP packet in the embodiment of the present invention determines the value of the encoding header to be decoded corresponding to the bit according to the value of the bit of the encoding header part map, and the recorded HTTP packet. Whether the values of the corresponding coding headers in the text are the same, so that the coding header and its value in the received HTTP message can be determined according to the coding header part map, thereby reducing continuous HTTP. The wireless air interface resources occupied by the same field in the packet can improve the resource usage efficiency.

In the embodiment of the present invention, optionally, as shown in FIG. 27, the decoding apparatus 900 further includes: a second determining module 930, configured to acquire, by the acquiring module 910, the second bit of the encoding header part map If the value of the second encoding header corresponding to the second bit is different from the value of the corresponding encoding header in the recorded HTTP packet, according to the received

The header encoding in the HTTP message determines the second encoding header that the header encoding refers to.

In the embodiment of the present invention, optionally, as shown in FIG. 28, the decoding apparatus 900 further includes: a third determining module 940, configured to: according to the first compression indication and the first byte in the received HTTP packet And determining a first identical number of bytes associated with the first number of bytes, wherein the first compression indication is used to indicate that the value of the second encoding header is compressed;

a fourth determining module 950, configured to determine, according to the first identical number of bytes determined by the third determining module 940, a corresponding consecutive first identical word in the value of the corresponding encoding header in the recorded HTTP packet The byte of the number of sections is determined as the value to be decoded of the second encoding header.

In the embodiment of the present invention, optionally, as shown in FIG. 29, the decoding apparatus 900 further includes: a fifth determining module 960, configured to determine, according to the second compression indication and the sequence information in the received HTTP packet, a first HTTP packet corresponding to the sequence information in the recorded HTTP packet, where the second compression indication is used to indicate the value of the second encoding header and the corresponding encoding in the first HTTP packet. The value of the head is the same;

The sixth determining module 970 is configured to determine, by the fifth determining module 960, a value of a corresponding encoding header in the first HTTP packet as a value of the second encoding header.

In the embodiment of the present invention, optionally, as shown in FIG. 30, the decoding apparatus 900 further includes: a seventh determining module 980, configured to: according to the third compressed indication and the second byte in the received HTTP packet a second identical number of bytes associated with the second number of bytes, wherein the third compressed indication is used to indicate that the URI to be decoded is compressed;

The eighth determining module 990 is configured to determine, according to the second identical number of bytes determined by the seventh determining module 980, a corresponding consecutive second identical number of bytes in the URI of the recorded HTTP message. The URI to be decoded in the received HTTP message.

In the embodiment of the present invention, optionally, as shown in FIG. 31, the decoding apparatus 900 further includes: a ninth determining module 991, configured to: when it is determined that the received HTTP packet does not have the HTTP version number information, The version number information in the recorded HTTP packet is determined as the version number information of the received HTTP packet. In the embodiment of the present invention, optionally, as shown in FIG. 31, the decoding apparatus 900 further includes: a receiving module 992, configured to receive a protocol data unit PDU packet including a type field, where the type field is used to indicate the PDU packet HTTP headers that are header encoded and compressed.

In the embodiment of the present invention, optionally, as shown in FIG. 32, the decoding apparatus 900 further includes: a recording module 993, configured to record the HTTP transmitted for the first time when transmitting the HTTP packet for the first time.

4 encoding the encoding header value, URI and HTTP version number information;

The update module 994 is configured to update the recorded HTTP message according to the received HTTP message when the HTTP message is not transmitted for the first time.

In the embodiment of the present invention, optionally, the update module 994 is configured to:

And if the version number information of the received HTTP packet is different from the version number information of the recorded HTTP packet, the version number information in the recorded HTTP packet is replaced with the version number of the received HTTP packet. information.

It should be understood that the decoding apparatus 900 of the HTTP message according to the embodiment of the present invention may correspond to the receiver of the method for transmitting the HTTP message in the embodiment of the present invention, and the above and other operations of the respective modules in the decoding apparatus 900 and/or For the purpose of implementing the corresponding processes of the respective methods in FIG. 1 to FIG. 18, the functions are not described herein.

Therefore, the decoding apparatus of the HTTP packet according to the embodiment of the present invention determines the value of the encoding header to be decoded corresponding to the bit according to the value of the bit of the encoding header part map, and the recorded value Whether the value of the corresponding encoding header in the HTTP packet is the same, so that the encoding header and its value in the received HTTP packet can be determined according to the encoding header part map, thereby reducing the number of consecutive HTTP packets. The wireless air interface resources occupied by the same field can improve the efficiency of resource usage.

In the embodiment of the present invention, as shown in FIG. 33, the present invention further provides an encoding apparatus 1000, which includes a processor 1100, a memory 1200, a bus system 1300, and a transmitter 1400. The processor 1100, the memory 1200, and the transmitter 1400 are connected by a bus system 1300. The memory 1200 is used to store instructions. The processor 1100 calls the instruction stored in the memory 1200 through the bus system 1300, and is used to: determine The value of each bit of the coding header part map, and the value of each bit is respectively indicated as the value of the coding header to be transmitted corresponding to the bit and the corresponding coding header in the recorded HTTP message. The processor 1100 is further configured to: generate, according to the value of each bit, an HTTP message to be transmitted that includes the coded part location map; the processor 1100 is further configured to control the The sender 1400 sends the HTTP message to be transmitted to the receiver, so that the receiver determines, according to the code header part map and the recorded HTTP message, the code header in the HTTP message to be transmitted. The first encoding header having the same value as the corresponding encoding header in the recorded HTTP packet and the value of the first encoding header.

It should be understood that, in the embodiment of the present invention, the processor 1100 may be a central processing unit (a central processing unit (CPU), and the processor 1100 may also be another general-purpose processor, a digital signal processor (DSP). ), application specific integrated circuits (ASICs), off-the-shelf programmable gate arrays (FPGAs) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, and the like. The general purpose processor may be a microprocessor or the processor or any conventional processor or the like.

The memory 1200 can include read only memory and random access memory and provides instructions and data to the processor 1100. A portion of the memory 1200 can also include a non-volatile random access memory. For example, the memory 1200 can also store information of the device type.

The bus system 1300 may include a power bus, a control bus, a status signal bus, and the like in addition to the data bus. However, for the sake of clarity, the various buses are marked as total in the figure. Line system 1300.

In the implementation process, each step of the above method may be completed by an integrated logic circuit of the hardware in the processor 1100 or an instruction in the form of software. The steps of the method disclosed in the embodiments of the present invention may be directly implemented as hardware processor execution completion, or may be performed by a combination of hardware and software modules in the processor. The software modules can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like. The storage medium is located in the memory 1200. The processor 1100 reads the information in the memory 1200 and completes the steps of the above method in combination with hardware. To avoid repetition, it will not be described in detail here.

Optionally, as an embodiment, the processor 1100 is configured to: determine an encoding header header to be transmitted, and a value of the second encoding header; determine a header encoding of the second encoding header, the header The part code is used to refer to the second encoding header; wherein, according to the value of each bit, the HTTP message to be transmitted including the encoding header part map is generated and transmitted, including: according to each The value of the bit, the header of the second encoding header, and the value of the second encoding header generate and transmit the HTTP message to be transmitted.

Optionally, as an embodiment, the processor 1100 is configured to: determine a first compression indication and a first number of bytes, where the first compression indication is used to indicate that the value of the second encoding header is compressed, the first One byte number is associated with the first identical number of bytes, the first identical number of bytes being the second number of bytes to be transmitted; wherein, according to the value of each bit, the second code The header code of the header and the value of the second encoding header, generating and transmitting the HTTP message to be transmitted, including: according to the value of each bit, the header encoding of the second encoding header And the first compression indication and the first number of bytes, generating and transmitting the HTTP message to be transmitted.

Optionally, as an embodiment, the processor 1100 is configured to: determine a second compression indication, and order information of the first HTTP packet in the recorded HTTP packet, where the second compression indication is used to indicate The value of the second encoding header is the same as the value of the corresponding encoding header in the first HTTP packet corresponding to the order information; where the value is determined according to the bit, the second encoding The header code of the header and the value of the second encoding header, generating and transmitting the HTTP message to be transmitted, including: according to the value of each bit, the header encoding of the second encoding header And the second compression indication and the sequence information, generating and transmitting the HTTP message to be transmitted.

Optionally, as an embodiment, the processor 1100 is configured to: determine a third compression indication to And a second number of bytes, the third compressed indication is used to indicate that the universal resource identifier URI to be transmitted is compressed, and the second number of bytes is associated with the second identical number of bytes, and the second identical number of bytes is The value of each bit to be transmitted, and the HTTP message to be transmitted including the code header part map is generated and transmitted, including: according to the value of each bit, the third compression indication, and the second The number of bytes, the HTTP message to be transmitted is generated and transmitted.

Optionally, as an embodiment, the processor 1100 is configured to: determine whether the HTTP version number information to be transmitted is the same as the version number information in the recorded HTTP packet; wherein, according to the each bit The value of the HTTP packet to be transmitted, including the encoding part header map, is generated and transmitted, and includes: when the HTTP version number information to be transmitted is the same as the version number information in the recorded HTTP packet, according to the The value of each bit is generated and transmitted, and the HTTP message to be transmitted includes the code header part map; the HTTP version number information to be transmitted and the recorded HTTP message When the version number information in the text is different, the HTTP packet to be transmitted is generated and transmitted according to the value of the bit and the HTTP version number to be transmitted, and the HTTP packet to be transmitted includes the encoding header. The part map and the HTTP version number information to be transmitted.

Optionally, as an embodiment, the processor 1100, according to the value of each bit, generates and transmits an HTTP message to be transmitted that includes the coded part location map, including: according to each bit bit The value is generated, and a protocol data unit PDU packet including a type field is used, and the type field is used to indicate that the PDU packet is a header encoded and compressed HTTP.

Optionally, as an embodiment, the memory 1200 is configured to: when encoding the HTTP packet for the first time, record the encoding header value, the URI, and the HTTP version number information of the first transmitted HTTP text; and not transmit the HTTP packet for the first time. And updating the recorded HTTP packet according to the HTTP packet to be transmitted.

Optionally, as an embodiment, the memory 1200 updates the recorded HTTP packet according to the HTTP packet to be transmitted, including:

If the value of the encoding header of the HTTP packet to be transmitted is different from the value of the encoding header of the recorded HTTP packet, the value of the encoding header in the recorded HTTP packet is replaced by the value. The value of the encoding header of the HTTP packet to be transmitted; or

It should be understood that the encoding apparatus 1000 of the HTTP message according to the embodiment of the present invention may correspond to the sender of the method for transmitting the HTTP message and the encoding apparatus 800 in the embodiment of the present invention, and the above-mentioned sum of each module in the encoding apparatus 1000 For the purpose of implementing the corresponding processes of the respective methods in FIG. 1 to FIG. 18, other operations and/or functions are not described herein.

As shown in FIG. 34, the present invention also provides a decoding apparatus 2000, which includes a processor 2100, a memory 2200, and a bus system 2300. The processor 2100 and the memory 2200 are connected by a bus system 2300 for storing instructions. The processor 2100 calls the instruction stored in the memory 2200 through the bus system 2300 to: obtain the received HTTP. The value of each bit of the coded header part map in the message; the value of the first bit of the code header part map is indicated by the first bit of the first bit to be decoded corresponding to the first bit When the value is the same as the value of the corresponding encoding header in the recorded HTTP packet, the encoding header corresponding to the first bit in the recorded HTTP packet and its value are respectively determined. The value of the first encoding header and the first encoding header.

It should be understood that, in the embodiment of the present invention, the processor 2100 may be a central processing unit (a central processing unit (CPU), and the processor 2100 may also be another general-purpose processor, a digital signal processor (DSP). ), application specific integrated circuits (ASICs), off-the-shelf programmable gate arrays (FPGAs) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, and the like. The general purpose processor may be a microprocessor or the processor or any conventional processor or the like.

The memory 2200 can include read only memory and random access memory and provides instructions and data to the processor 2100. A portion of the memory 2200 can also include a non-volatile random access memory. For example, the memory 2200 can also store information of the device type.

The bus system 2300 can include, in addition to the data bus, a power bus, a control bus, and a status signal bus. However, for clarity of description, various buses are labeled as bus system 2300 in the figure.

In the implementation process, each step of the foregoing method may be completed by an integrated logic circuit of the hardware in the processor 2100 or an instruction in the form of software. The steps of the method disclosed in the embodiments of the present invention may be directly implemented as hardware processor execution completion, or may be performed by a combination of hardware and software modules in the processor. The software modules can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like. The storage medium is located in the memory 2200, and the processor 2100 reads the information in the memory 2200 and completes the steps of the above method in combination with the hardware. To avoid repetition, it will not be described in detail here.

Optionally, as an embodiment, the processor 2100 is configured to:: the value of the second bit in the coding part location map indicates that the second coding bit to be decoded is corresponding to the second bit When the value is different from the value of the corresponding encoding header in the recorded HTTP packet, the second encoding header indicated by the header encoding is determined according to the header encoding in the received HTTP packet.

Optionally, as an embodiment, the processor 2100 is configured to: determine, according to the first compression indication in the received HTTP packet and the first number of bytes, a first identity associated with the first number of bytes a number of bytes, wherein the first compression indication is used to indicate that the value of the second encoding header is compressed; according to the first identical number of bytes, the corresponding encoding header in the recorded HTTP packet is taken The corresponding consecutive first identical number of bytes in the value is determined as the value of the second encoding header to be decoded. Optionally, as an embodiment, the processor 2100 is configured to: determine, according to the second compression indication and the sequence information in the received HTTP packet, the first corresponding to the sequence information in the recorded HTTP packet An HTTP packet, where the second compression indication is used to indicate that the value of the second encoding header is the same as the value of the corresponding encoding header in the first HTTP packet; The value of the corresponding encoding header is determined as the value of the second encoding header.

Optionally, as an embodiment, the processor 2100 is configured to: determine, according to the third compression indication in the received HTTP packet and the second byte number, a second identity associated with the second byte number a number of bytes, wherein the third compression indication is used to indicate that the URI to be decoded is compressed; according to the second identical number of bytes, the corresponding consecutive second identical number of bytes in the URI of the recorded HTTP message Byte, determined as the URI to be decoded in the received HTTP message.

Optionally, as an embodiment, the processor 2100 is configured to: when it is determined that the received HTTP packet does not have the HTTP version number information, determine the version number information in the recorded HTTP packet as the received Version number information of the HTTP packet.

Optionally, as an embodiment, the decoding apparatus 2000 further includes a receiver 2400, configured to: receive a protocol data unit PDU packet including a type field, where the type field is used to indicate that the PDU packet is a header. Encoded and compressed HTTP ^ text.

Optionally, as an embodiment, the memory 2200 is configured to: when encoding the HTTP packet for the first time, record the encoding header value, the URI, and the HTTP version number information of the first transmitted HTTP text; and not transmit the HTTP packet for the first time. And updating the recorded HTTP packet according to the received HTTP packet.

Optionally, as an embodiment, the memory 2200 updates the recorded HTTP packet according to the received HTTP packet, including:

If the received HTTP packet has an encoding header that the recorded HTTP packet does not have And recording the encoded header of the received HTTP message but having the recorded HTTP packet and the value thereof; or

It should be understood that the decoding apparatus 2000 of the HTTP message according to the embodiment of the present invention may correspond to the receiver and the decoding apparatus 900 of the method for transmitting an HTTP message in the embodiment of the present invention, and the above-mentioned sum of each module in the decoding apparatus 2000 For the purpose of implementing the corresponding processes of the respective methods in FIG. 1 to FIG. 18, other operations and/or functions are not described herein.

Therefore, the decoding apparatus of the HTTP packet in the embodiment of the present invention determines the value of the encoding header to be decoded corresponding to the bit according to the value of the bit of the encoding header part map, and the recorded HTTP packet. Whether the values of the corresponding coding headers in the text are the same, so that the coding header and its value in the received HTTP message can be determined according to the coding header part map, thereby reducing the occupation of the same field in the continuous HTTP message. Wireless air interface resources and can improve resource utilization efficiency.

In addition, the terms "system" and "network" are often used interchangeably herein. The term "and/or," in this context is merely an association that describes an associated object, indicating that there can be three relationships, for example, A and / or B, which can mean: A exists separately, and both A and B exist, alone There are three cases of B. In addition, the character "," in this paper, indicates that the contextual object is an "or" relationship.

It should be understood that in the embodiment of the present invention, "B corresponding to A" means that B is associated with A, and B can be determined based on A. However, it should be understood that determining B according to A does not mean that B is determined only on the basis of A, but also based on A and/or other information.

Those of ordinary skill in the art will appreciate that the elements and algorithm steps of the various examples described in connection with the embodiments disclosed herein can be implemented in electronic hardware, computer software or a combination of both, in order to clearly illustrate hardware and software. Interchangeability, the composition and steps of the various examples have been generally described in terms of function in the above description. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods for implementing the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present invention. A person skilled in the art can clearly understand that, for the convenience of the description and the cleaning process, the specific working processes of the system, the device and the unit described above can refer to the corresponding processes in the foregoing method embodiments, and details are not described herein again.

In the several embodiments provided herein, it should be understood that the disclosed systems, devices, and methods may be implemented in other ways. 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. In addition, the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, or an electrical, mechanical or other form of connection. The components displayed for the unit may or may not be physical units, ie may be located in one place, or may be distributed over multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the embodiments of the present invention.

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 contributes in essence or 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 removable hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and the like, which can store program codes. .

The above is only the specific embodiment of the present invention, but the scope of the present invention is not limited thereto, and any equivalent person can be easily conceived within the technical scope of the present invention. Modifications or substitutions are intended to be included within the scope of the invention. Therefore, the scope of the invention should be determined by the scope of the claims.

Claims

Rights request

1. A method of transmitting HTTP messages, characterized by including:

Determine the value of each bit of the encoding header bitmap. The value of each bit is respectively indicated by the value of the encoding header to be transmitted corresponding to the bit and the value in the recorded HTTP message. Whether the values of the corresponding encoding headers are the same;

According to the value of each bit, the HTTP message to be transmitted including the encoding header bitmap is generated and transmitted, so that the recipient of the HTTP message to be transmitted can receive the HTTP message according to the encoding header bitmap. bitmap and the recorded HTTP message, determine the first code whose encoding header value in the HTTP message to be transmitted is the same as the value of the corresponding encoding header in the recorded HTTP message header and the value of the first encoding header.

2. The method according to claim 1, characterized in that, the method further includes: determining that the value in the encoding header to be transmitted is different from the value of the corresponding encoding header in the recorded HTTP message. The second encoding header, and the value of the second encoding header;

Determine the header code of the second coded header, the header code being used to refer to the second coded header;

Wherein, generating and transmitting an HTTP message to be transmitted including the encoded header bitmap according to the value of each bit includes:

The HTTP text to be transmitted is generated and transmitted according to the value of each bit, the header encoding of the second encoding header, and the value of the second encoding header.

3. The method according to claim 2, characterized in that, the method further includes: determining a first compression indication and a first number of bytes, the first compression indication being used to represent the second encoding header The value is compressed, the first number of bytes is associated with the first number of identical bytes, and the first number of identical bytes is the value of the second encoding header to be transmitted and the recorded The value of the corresponding encoding header in the HTTP message is the same number of consecutive bytes;

Wherein, the HTTP message to be transmitted is generated and transmitted according to the value of each bit, the header encoding of the second encoding header and the value of the second encoding header, The method includes: generating and transmitting the HTTP packet to be transmitted according to the value of each bit, the header encoding of the second encoding header, the first compression indication and the first number of bytes. arts.

4. The method according to claim 2, characterized in that, the method further includes: determining the second compression indication and the order information of the first HTTP message in the recorded HTTP message, wherein, The second compression indication is used to represent the value and phase of the second encoding header. The value of the corresponding encoding header in the first HTTP message corresponding to the sequence information is the same; wherein, according to the value of each bit, the header of the second encoding header encoding and the value of the second encoding header, generating and transmitting the HTTP message to be transmitted, including: according to the value of each bit, the header encoding of the second encoding header, The second compression indication and the sequence information are used to generate and transmit the HTTP message to be transmitted.

5. The method according to claim 1, characterized in that, the method further comprises: determining a third compression indication and a second number of bytes, the third compression indication being used to represent a universal resource identifier URI to be transmitted Compressed, the second number of bytes is associated with the second number of identical bytes, and the second number of identical bytes is the URI to be transmitted and the URI in the recorded HTTP message that are continuously the same bytes number;

The HTTP message to be transmitted is generated and transmitted according to the value of each bit, the third compression indication and the second number of bytes.

6. The method according to claim 1, wherein the method further includes: determining whether the HTTP version number information to be transmitted is the same as the version number information in the recorded HTTP message;

When the HTTP version number information to be transmitted is the same as the version number information in the recorded HTTP message, the HTTP message to be transmitted is generated and transmitted according to the value of each bit, The HTTP message to be transmitted includes the encoding header bitmap;

When the HTTP version number information to be transmitted is different from the version number information in the recorded HTTP message, according to the value of each bit and the HTTP version number information to be transmitted, a Transmit the HTTP message to be transmitted, where the HTTP message to be transmitted includes the encoding header bitmap and the HTTP version number information to be transmitted.

7. The method according to claim 1, characterized in that, generating and transmitting the HTTP text to be transmitted including the encoding header bitmap according to the value of each bit, includes: According to the value of each bit, a protocol data unit PDU packet including a type field is generated and transmitted, where the type field is used to indicate that the PDU packet is a header-encoded and compressed HTTP message.

8. The method according to any one of claims 1 to 7, characterized in that the method further includes:

When the HTTP message is transmitted for the first time, the encoding header value, URI and HTTP version number information of the HTTP message transmitted for the first time are recorded;

When the HTTP message is not transmitted for the first time, the recorded HTTP message is updated according to the HTTP message to be transmitted.

9. The method according to claim 8, characterized in that, updating the recorded HTTP message according to the HTTP message to be transmitted includes:

If the encoding header value of the HTTP message to be transmitted is the same as the encoding header value of the recorded HTTP message, then the encoding header and the value of the recorded HTTP message are retained. unchanged; or

If the encoding header value of the HTTP message to be transmitted is different from the encoding header value of the recorded HTTP message, replace the encoding header value in the recorded HTTP message. Value for the encoding header of the HTTP message to be transmitted; or

If the recorded HTTP message has an encoding header that the HTTP message to be transmitted does not have, then keep the encoding header of the recorded HTTP message and its value unchanged; or

If the HTTP message to be transmitted has an encoding header that the recorded HTTP message does not have, record the encoding header that the HTTP message to be transmitted has but the recorded HTTP message does not have. part and its value; or

If the version number information of the HTTP message to be transmitted is the same as the version number information of the recorded HTTP message, then keep the version number information of the recorded HTTP message unchanged; or if the version number information to be transmitted is the same. If the version number information of the transmitted HTTP message is different from the version number information of the recorded HTTP message, replace the version number information in the recorded HTTP message with the version number information of the HTTP message to be transmitted. Version number information.

10. A method of transmitting HTTP messages, characterized by including:

Obtain the value of each bit of the encoding header bitmap in the received HTTP message; the value of the first bit of the encoding header bitmap indicates the corresponding first bit to be decoded When the value of the first encoding header is the same as the value of the corresponding encoding header in the recorded HTTP message, the encoding corresponding to the first bit in the recorded HTTP message is The header and its value are respectively determined as the first encoding header and the value of the first encoding header.

11. The method according to claim 10, characterized in that, the method further comprises: indicating that the value of the second bit in the encoding header bitmap is the corresponding to-be-decoded bit of the second bit. When the value of the second encoding header is different from the value of the corresponding encoding header in the recorded HTTP message, determine what the header encoding refers to based on the header encoding in the received HTTP message. The second encoding header.

12. The method according to claim 11, characterized in that, the method further includes: determining, according to the first compression indication and the first byte number in the received HTTP message, the number of the first byte. The first identical number of bytes associated with the number, wherein the first compression indication is used to indicate that the value of the second encoding header is compressed;

According to the first same number of bytes, the corresponding first consecutive number of bytes of the same number of bytes among the values of the corresponding encoding headers in the recorded HTTP message is determined as the second encoding header. The value to be decoded.

13. The method according to claim 11, characterized in that, the method further includes: determining, according to the second compression indication and sequence information in the received HTTP message, that the recorded HTTP message corresponds to The first HTTP message corresponding to the sequence information, wherein the second compression indication is used to represent the value of the second encoding header and the value of the corresponding encoding header in the first HTTP message. same;

The value of the corresponding encoding header in the first HTTP message is determined as the value of the second encoding header.

14. The method according to claim 10, characterized in that, the method further includes: determining, according to the third compression indication and the second number of bytes in the received HTTP message, the number of the second byte. A second identical number of bytes associated with the number, wherein the third compression indication is used to indicate that the URI to be decoded is compressed;

According to the second identical number of bytes, the corresponding second consecutive identical number of bytes in the URI of the recorded HTTP message is determined as the URI to be decoded in the received HTTP message.

15. The method according to claim 10, characterized in that, the method further includes: when it is determined that there is no HTTP version number information in the received HTTP message, converting the version number in the recorded HTTP message to The number information is determined as the version number information of the received HTTP message.

16. The method according to claim 10, characterized in that, the method further comprises: receiving a protocol data unit PDU packet including a type field, the type field is used to indicate the The PDU packet is a header-encoded and compressed HTTP text.

17. The method according to any one of claims 10 to 16, characterized in that the method further includes:

When the HTTP message is not transmitted for the first time, the recorded HTTP message is updated according to the received HTTP message.

18. The method according to claim 17, characterized in that, updating the recorded HTTP message according to the received HTTP message includes:

If the encoded header value of the received HTTP message is the same as the encoded header value of the recorded HTTP message, then the encoded header value of the recorded HTTP message and its value are kept unchanged. change; or

If the encoding header value of the received HTTP message is different from the encoding header value of the recorded HTTP message, then replace the encoding header value in the recorded HTTP message with The value of the encoding header of the received HTTP message; or

If the recorded HTTP message has an encoding header that the received HTTP message does not have, then keep the encoding header of the recorded HTTP message and its value unchanged; or

If the received HTTP message has an encoding header that the recorded HTTP message does not have, record the encoding header that the received HTTP message has but the recorded HTTP message does not have and its value; or

If the version number information of the received HTTP message is the same as the version number information of the recorded HTTP message, then keep the version number information of the recorded HTTP message unchanged; or if the received If the version number information of the HTTP message is different from the version number information of the recorded HTTP message, the version number information in the recorded HTTP message is replaced with the version number information of the received HTTP message. .

19. An HTTP message encoding device, characterized by including:

The first determination module is used to determine the value of each bit of the encoding header bit map. The value of each bit is respectively indicated by the value of the encoding header to be transmitted corresponding to the bit and the value that has been transmitted. Whether the values of the corresponding encoding headers in the recorded HTTP messages are the same;

A transmission module, configured to generate and transmit the HTTP text to be transmitted including the encoding header bitmap according to the value of each bit determined by the first determination module, so as to facilitate the transmission The receiver of the transmitted HTTP message determines the value of the encoding header in the HTTP message to be transmitted and the recorded HTTP message based on the encoding header bit map and the recorded HTTP message. The first encoding header whose value is the same as the corresponding encoding header in and the value of the first encoding header.

20. The encoding device according to claim 19, characterized in that the encoding device further includes:

The second determination module is used to determine the second encoding header whose value in the encoding header to be transmitted is different from the value of the corresponding encoding header in the recorded HTTP message, and the second encoding header. The value of the part;

A third determination module, configured to determine the header code of the second coded header determined by the second determination module, where the header code is used to refer to the second coded header;

Wherein, the transmission module is configured to: based on the value of each bit determined by the first determination module, the header coding of the second coding header determined by the third determination module and the The second determination module determines the value of the second encoding header, generates and transmits the HTTP message to be transmitted.

21. The encoding device according to claim 20, characterized in that the encoding device further includes:

The fourth determination module is used to determine the first compression indication and the first number of bytes. The first compression indication is used to indicate that the value of the second encoding header is compressed. The first number of bytes and the first number of bytes are A same number of bytes is associated, and the first same number of bytes means that the value of the second encoding header to be transmitted is continuously the same as the value of the corresponding encoding header in the recorded HTTP message. The number of bytes; wherein, the transmission module is configured to: based on the value of each bit determined by the first determination module, the header of the second encoding header determined by the third determination module Using the partial encoding, the first compression indication determined by the fourth determination module, and the first number of bytes, the HTTP message to be transmitted is generated and transmitted.

22. The encoding device according to claim 20, characterized in that the encoding device further includes:

The fifth determination module is used to determine the second compression indication and the order information of the first HTTP message in the recorded HTTP message, wherein the second compression indication is used to represent the second encoding header. The value of is the same as the value of the corresponding encoding header in the first HTTP text corresponding to the order information; Wherein, the transmission module is configured to: based on the value of each bit determined by the first determination module, the header encoding of the second encoding header determined by the third determination module, the The second compression indication and the order information determined by the fifth determination module generate and transmit the HTTP message to be transmitted.

23. The encoding device according to claim 19, characterized in that the encoding device further includes:

The sixth determination module is used to determine a third compression indication and a second number of bytes. The third compression indication is used to indicate that the universal resource identifier URI to be transmitted is compressed. The second number of bytes is the same as the second number of bytes. The number of bytes is related, and the second number of identical bytes is the number of bytes that the URI to be transmitted is continuously the same as the URI in the recorded HTTP message;

Wherein, the transmission module is configured to: based on the value of each bit determined by the first determination module, the third compression indication and the second number of bytes determined by the sixth determination module , generate and transmit the HTTP message to be transmitted.

24. The encoding device according to claim 19, characterized in that the encoding device further includes:

The seventh determination module is used to determine whether the HTTP version number information to be transmitted is the same as the version number information in the recorded HTTP message;

Among them, the transmission module is used for:

When the seventh determination module determines that the HTTP version number information to be transmitted is the same as the version number information in the recorded HTTP message, based on the value of each bit, generate and transmit the The HTTP message to be transmitted, the HTTP message to be transmitted includes the encoding header bitmap;

When the seventh determination module determines that the HTTP version number information to be transmitted is different from the version number information in the recorded HTTP message, according to the value of each bit and the HTTP version number information to be transmitted, HTTP version number information, generate and transmit the HTTP message to be transmitted, the HTTP message to be transmitted includes the encoding header bitmap and the HTTP version number information to be transmitted

25. The encoding device according to claim 19, characterized in that the transmission module is used for:

According to the value of each bit, a protocol data unit including a type field is generated and transmitted

PDU packet, the type field is used to indicate that the PDU packet is header-encoded and compressed HTTP message.

26. The encoding device according to any one of claims 19 to 25, characterized in that the encoding device further includes:

The recording module is used to record the encoding header value, URI and HTTP version number information of the HTTP message transmitted for the first time when the HTTP message is transmitted for the first time;

The update module is configured to update the recorded HTTP message according to the HTTP message to be transmitted when the HTTP message is not transmitted for the first time.

27. The encoding device according to claim 26, characterized in that the update module is used for:

28. A decoding device for HTTP messages, characterized by including:

Obtain block, used to obtain the value of each bit of the encoding header bitmap in the received HTTP message;

The first determination module is configured to indicate that the value of the first bit of the encoding header bitmap obtained by the acquisition module is the value of the first encoding header to be decoded corresponding to the first bit. When the value of the corresponding encoding header in the recorded HTTP message is the same, the recorded The encoding header corresponding to the first bit in the HTTP message and its value are respectively determined as the first encoding header and the value of the first encoding header.

29. The decoding device according to claim 28, characterized in that the decoding device further includes:

The second determination module is configured to indicate that the value of the second bit of the encoding header bit map obtained by the acquisition module is the value of the second encoding header to be decoded corresponding to the second bit. When the value of the corresponding encoding header in the recorded HTTP message is different, the second encoding header that the header encoding refers to is determined based on the header encoding in the received HTTP message.

30. The decoding device according to claim 29, characterized in that, the decoding device further includes:

A third determining module, configured to determine a first identical number of bytes associated with the first number of bytes based on the first compression indication and the first number of bytes in the received HTTP message, wherein the The first compression indication is used to indicate that the value of the second encoding header is compressed;

The fourth determination module is configured to determine, according to the first number of identical bytes determined by the third determination module, the corresponding first consecutive identical value among the values of the corresponding encoding header in the recorded HTTP message. The number of bytes is determined as the value to be decoded of the second encoding header.

31. The decoding device according to claim 29, characterized in that the decoding device further includes:

The fifth determination module is configured to determine the first HTTP message corresponding to the sequence information in the recorded HTTP message according to the second compression indication and the sequence information in the received HTTP message, wherein, The second compression indication is used to indicate that the value of the second encoding header is the same as the value of the corresponding encoding header in the first HTTP message;

A sixth determination module, configured to determine the value of the corresponding encoding header in the first HTTP message determined by the fifth determination module as the value of the second encoding header.

32. The decoding device according to claim 28, characterized in that the decoding device further includes:

A seventh determination module, configured to determine a second identical number of bytes associated with the second number of bytes based on the third compression indication and the second number of bytes in the received HTTP message, wherein the The third compression indication is used to indicate that the URI to be decoded is compressed;

The eighth determination module is configured to, according to the second identical number of bytes determined by the seventh determination module, obtain the corresponding second consecutive identical number of bytes in the URI of the recorded HTTP message, Determined to be the URI to be decoded in the received HTTP message.

33. The decoding device according to claim 28, characterized in that the decoding device further includes:

A ninth determination module, configured to determine the version number information in the recorded HTTP message as the version number of the received HTTP message when it is determined that there is no HTTP version number information in the received HTTP message. information.

34. The decoding device according to claim 28, characterized in that the decoding device further includes:

A receiving module, configured to receive a protocol data unit PDU packet including a type field, where the type field is used to indicate that the PDU packet is a header-encoded and compressed HTTP text.

35. The decoding device according to any one of claims 28 to 34, characterized in that the decoding device further includes:

The update module is configured to update the recorded HTTP message according to the received HTTP message when the HTTP message is not transmitted for the first time.

36. The decoding device according to claim 35, characterized in that the update module is used for:

If the version number information of the received HTTP message is the same as the version number information of the recorded HTTP message, then keep the version number information of the recorded HTTP message unchanged; or If the version number information of the received HTTP message is different from the version number information of the recorded HTTP message, replace the version number information in the recorded HTTP message with the received HTTP message. The version number information of the document.

37. An HTTP message encoding device, characterized by including: a processor, a memory, a bus and a transmitter;

Wherein, the processor, the memory and the transmitter are connected through the bus, the memory is used to store instructions, and the processor calls the instructions stored in the memory through the bus, so as to Used to determine the value of each bit of the encoding header bitmap. The value of each bit is respectively indicated by the value of the encoding header to be transmitted corresponding to the bit and the recorded HTTP message. Whether the values of the corresponding encoding headers in are the same;

The processor is also configured to generate an HTTP message to be transmitted including the encoded header bitmap according to the value of each bit;

The processor is also configured to control the sender to send the HTTP message to be transmitted to the receiver, so that the receiver determines based on the encoding header bit map and the recorded HTTP message. The first encoding header whose value in the HTTP message to be transmitted is the same as the value of the corresponding encoding header in the recorded HTTP message and the value of the first encoding header .

38. An HTTP message decoding device, characterized by including: a processor, a memory and a bus;

Wherein, the processor and the memory are connected through the bus, the memory is used to store instructions, and the processor calls the instructions stored in the memory through the bus to obtain the received The value of each bit of the encoding header bitmap in the HTTP message;

The processor is further configured to indicate that the value of the first bit of the encoding header bitmap is the value of the first encoding header to be decoded corresponding to the first bit and the recorded HTTP packet. When the values of the corresponding coding headers in the text are the same, the coding header corresponding to the first bit in the recorded HTTP text and its value are respectively determined to be the first coding header. part and the value of the first encoding header.