KR100930463B1 - Header conversion system and control method - Google Patents

Abstract

The present invention relates to a header conversion system and a control method thereof, comprising: a browser requesting an HTTP document; A client converting the header information of the HTTP document into a binary code; And a proxy server for decoding the converted header information and transmitting the decoded header information to an internet network. The proxy server may further include a browser, a client, and a proxy server. A control method of a header conversion system comprising: when an HTTP document is requested by a user, determining whether the client supports an HTTP version; Parsing header information of the HTTP document, if the support is supported; Converting the parsed header information into a binary code; And decoding the converted header information and transmitting the decoded header information to an internet network.

As a result, by minimizing unnecessary HTTP header information in HTTP document request / response, the overall HTTP traffic can be reduced, thereby making the HTTP document movement in the wireless network more convenient in terms of time and cost.

ASCII, Binary Code, Request Line, Status Line, Header Field

Description

Header Transformation System and Control Method

The present invention relates to a header conversion system and a control method thereof. More particularly, the present invention relates to a header conversion system and a control method thereof capable of reducing HTTP traffic in a wireless network section by compressing and converting header information of an HTTP document. will be.

Hypertext is a computer related term coined by Theodor Nelson in the 1960s that combines the characteristics of a computer such as hyperlink and interactive. it means. That is, a text data file in which a phrase, a word, and a table of contents of a sentence are collected are related to each other, and may be suitable for efficient information retrieval because the nodes are composed of a network connected to each other. Here, the node refers to the most basic information unit of hypertext.

In addition, HTTP (Hypertext Transfer Protocol) is a communication protocol used to transfer documents between a web server and a user's Internet browser on the Internet, and is used to exchange hypertext documents on the Internet. Means to be used. For example, when specifying an Internet address, such as 'http: // www ....' means that the exchange of hypertext documents at the Internet address beginning with www should be handled by the http protocol.

On the other hand, since the wireless network has a limitation of bandwidth compared to the wired network, the conventional invention of requesting / transmitting an HTTP document has a problem that HTTP over-traffic occurs. There is a need for efforts to solve the HTTP over-traffic problem in the network.

Accordingly, an object of the present invention is to provide a header conversion system and a method of controlling the same, which can solve the overall HTTP traffic problem by compressing and reducing information that is always attached when moving and requesting an HTTP document in a wireless network. have.

delete

delete

According to the present invention, there is provided a system for converting and transmitting an HTTP protocol header in a wireless interval: the system parses a header of the HTTP document when an HTTP document is requested, and requests the parsed header information from the request line. A client classifying one of a request line and a status line into a header field and converting the binary code into a binary code and transmitting an HTTP document including the converted header to the wireless section; And a proxy server for receiving the HTTP document including the converted header, decoding the converted header, and transmitting the decoded header to an internet network.
Advantageously, the client encodes the request line into 4 bits if the request line is included in the parsed header, otherwise encodes the status line into 7 bits and encodes the header field of the parsed header into 6 bits. Characterized in that.
According to another aspect of the present invention, a system for converting and transmitting an HTTP protocol header in a wireless interval is provided: The system parses a header of the HTTP document and includes a request line in the parsed header. If a request line is not included in the parsed header information, the status line and the header field are converted to a binary code. A client for transmitting an HTTP document including a header to the wireless section; And a proxy server for receiving the HTTP document including the converted header, decoding the converted header, and transmitting the decoded header to an internet network.
Preferably, the client encodes bit information representing a method and HTTP version included in the request line when the parsed header includes a request line. Characterized in that.
Preferably, the client, when the parsed header does not include a request line (Request Line), the status line with a bit information representing the HTTP version, status code and reason phrases (Status Code & Reason Phrases) Characterized in that the encoding.
Preferably, the client encodes the header field into bit information representing a name of the header field.
According to another aspect of the present invention, a client of a header conversion system is provided: The client parses HTTP header information and classifies it into a request line, a status line, and a header field. The request line is encoded with a bit representing a method and an HTTP version, and the status line represents an HTTP version and a status code and reason phrase. Encoding by bits, and the header field is characterized by encoding the bits representing the name of the header field.
Preferably, the request line is encoded into 4 bits, the status line is encoded into 7 bits, and the header field is encoded into 6 bits.
According to yet another aspect of the present invention, there is provided a control method of a header conversion system including a client and a proxy server, the method comprising: when an HTTP document is requested by a user, the HTTP document; Parsing header information of the terminal; Classifying the parsed header information into one of a request line and a status line and a header field, converting the parsed header information into a binary code, and transmitting the converted header information; And receiving the HTTP document including the converted header information, decoding the header information, and transmitting the decoded header information to the Internet network.
Preferably, the converting of the header information into the binary code comprises: determining whether a request line is included in the header information; Request line encoding the header information when the request line is included, and status line encoding the header information when the request line is not included and only the status line; And encoding the header information with a header field.
Preferably, the request line encoding step is characterized by encoding to represent the method (method) and the HTTP version (version) using 4 bits.
Preferably, the step of encoding the status line, characterized in that the encoding to represent the HTTP version, the status code and reason phrases (Status Code & Reason Phrases) using 7 bits.
Advantageously, the step of encoding the header field comprises encoding to represent the name of the header field using 6 bits.

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

According to the present invention by the above means, it is possible to convert the HTTP header information always attached to the HTTP document request / response in the wireless network to a binary code (Binary Code).

Accordingly, by minimizing unnecessary HTTP header information in HTTP document request / response, it is possible to reduce the overall HTTP traffic, thereby making the HTTP document movement in the wireless network more convenient in terms of time and cost.

Hereinafter, with reference to the accompanying drawings will be described in detail with respect to the present invention.

1 is a block diagram of a header conversion system according to an embodiment of the present invention.

The header conversion system according to an embodiment of the present invention includes a browser 100, a client 300, and a proxy server 500.

The browser 100 is an application used to retrieve web / wap information from the wired / wireless internet and requests an HTTP document. The browser 100 itself does not include an Internet connection function. However, if software for Internet access such as Windows is set, the browser 100 can access a home page on a web / wap server of the world desired by simply starting the browser 100. have.

The client 300 converts the header information of an HTTP document into a binary code, wherein ASCII (American Standard Code for information interchange) is a 7-bit information exchange used internationally around a PC. As a code, numbers, letters, and special characters are numbered in order to use 8-bit data that is easy to process on a computer (also called ASCII code).

In addition, the client 300 parses the header information of the HTTP document, classifies it into a request line, a status line, and a header field, and encodes the classified header information. can do.

The encoding of the header information of the HTTP document by the client 300 will be described in more detail.

The client 300 may include header information classified into a request line, a status line, and a header field according to the format of the request line encoding, the status line encoding, And header field encoding.

Request line encoding is to encode the request line in the header information into 4 bits to express 8 types of methods and 2 types of HTTP versions. In this case, the request line encoding includes OPTION, GET, HEAD, POST, PUT, DELETE, TRAC, and CONNECT. It is represented by four bits to represent eight kinds of methods including CONNECT, and two kinds of HTTP versions including HTTP 1.0 and HTTP 1.1. Here, the four bits given for request line encoding are three bits for expressing eight kinds of methods (2 ³ = 8) and two kinds of HTTP versions. 1 bit (2 ¹ = 1). On the other hand, the Request Line encoding here excludes the Request-URI.

The terms related to HTTP described later are based on the Hypertext Transfer Protocol (HTTP) 1.0 and 1.1 prepared by the Institute of Electronics and Telecommunications. The same applies to the following).

Status Line encoding encodes a status line in header information into 7 bits to represent two types of HTTP versions and 40 types of status codes and reason phrases. will be. Here, Status-Code is a three-digit integer code as a result of understanding the Request message and to provide a service accordingly, and Reason-Phrase is short text for the status code. Used to provide a description of the form. On the other hand, the status code (Status-Code) is used by the automata (automata), the reason phrase (Reason-Phrase) is for use by human users.

The first digit of the Status-Code specifies the class of the response, the last two digits have no distinction, and the first digit can be five digits. That is, the configuration of the status code will be described.

『

? 1xx: Informational (Informational)? Request received and continue processing

? 2xx: Success? Successfully receive and interpret the request message and allow it

? 3xx: Redirection? Further action is required to complete the processing of the request

? 4xx: Client Error The request message is in the wrong format or cannot be processed correctly.

? 5xx: Server Error? When the server cannot process an apparently valid request message

』

In addition, examples of individual values of numeric status codes defined by HTTP / 1.1 and corresponding reason phrases (Reason-Phrase) will be described.

『

Status-Code = "100"; Continue

   | "101"; Switching Protocols

         | "200"; OK

         | "201"; Created

         | "202"; Accepted

         | "203"; Non-Authoritative Information

         | "204"; No Content

         | "205"; Reset Content

         | "206"; Partial Content

         | "300"; Multiple Choices

         | "301"; Moved Permanently

         | "302"; Moved Temporarily

         | "303"; See Other

         | "304"; Not Modified

         | "305"; Use Proxy

         | "400"; Bad Request

         | "401"; Unauthorized

         | "402"; Payment Required

         | "403"; Forbidden (Forbidden)

         | "404"; Not Found

         | "405"; Method Not Allowed

         | "406"; Not Acceptable

         | "407"; Proxy Authentication Required

         | "408"; Request Time-out

         | "409"; Conflict

         | "410"; Gone (content is gone)

         | "411"; Length Required

         | "412"; Precondition Failed

         | "413"; Request Entity Too Large

         "414"; Request-URI Too Large

         | "415"; Unsupported Media Type

         | "500"; Internal Server Error

         | "501"; Not Implemented

         | "502"; Bad Gateway

         | "503"; Service Unavailable

         | "504"; Gateway Time-out.

  | "505"; HTTP Version not supported

』

The reason statements listed above are only recommendations, and the reason statements can be replaced with local equivalents without affecting the protocol.

The 7 bits given for the above-mentioned status line encoding include 1 bit for representing two types of HTTP versions, 40 forty types of status codes and reason phrases (Status-Code & Reason-Phrases). 6 bits (2 ^6? 40) to represent.

Header field (Header Field) encoding is encoding with 6 bits to represent the names of 47 kinds of header fields. Here, the header field includes a request header field, a response header field, and an entity header field.

The Request header field allows the client to pass additional information about the request and the client itself to the server, and acts as request modifiers in the same sense as the parameters used when calling programming language methods. Can be. The request header field name is as described later.

『

request-header = Accept

                   | Accept-Charset

                   | Accept-Encoding

                   | Accept-Language

                   | Authorization

                   | From

                   | Host

                   | If-Modified-Since

                   | If-Match

                   | If-None-Match

                   | If-range

                   | If-Unmodified-Since

                   | Max-forwards

                   | Proxy-Authorization

                   | Range

                   | Referer

                   | User-Agent

』

The Response header field allows the server to convey additional information about the response that cannot be indicated in the status line. Information on how to further access the resource identified by the server and the Request-URI. To provide. The name of the response header field is as described later.

『

response-header = Age

   | Location

     | Proxy-Authenticate

  | Public

| Retry-after

| Server

  | Vary

| Warning

     | WWW-Authenticate

』

The entity header field defines optional meta information about a resource that can be identified through a request message if there is no body for the entity-body. The name of the entity header field is described below.

『

Entity-Header = Allow

  | Content-Base

       | Content-Encoding

  | Content-Language

| Content-length

  | Content-Location

| Content-MD5

| Content-range

| Content-Type

| ETag

| Expires

| Last-modified

| extension-header

』

On the other hand, there are a few more common header fields that can be applied to both request and response messages, but not to the entity being sent.

In order to express the names of the 47 kinds of header fields described above, 6 bits assigned for header field encoding are used (2 ^6? 47).

As described above, the proxy server 500 decodes the header information of the encoded HTTP document and transmits the header information to the Internet network. Thereafter, the request for the HTTP document may pass through the proxy server 500 to receive the requested HTTP document from a server in which each HTTP document is stored in the Internet.

2 is a flowchart illustrating a control method of a header conversion system according to an embodiment of the present invention.

Hereinafter, an operation procedure of a control method of a header conversion system according to an embodiment of the present invention will be described in detail with reference to FIG. 2.

When the user requests the HTTP document, it is determined whether the client 300 supports the HTTP document (S110).

If the HTTP document is supported, the header information of the HTTP document is parsed (S120). Here, when the header information of the HTTP document is parsed, it is classified into a request line, a status line, and a header field as described above.

The parsed header information is converted into a binary code (S130). Here, the conversion step will be described in detail later with reference to FIG. 3.

The header information of the converted HTTP document is decoded and transmitted to the internet network (S140). After that, the request for the HTTP document passes through the proxy server (Proxy Server, 500), and it has been described previously to receive the requested HTTP document from the server where each HTTP document is stored in the Internet.

3 is a more detailed flowchart of a control method of a header conversion system according to an embodiment of the present invention.

Hereinafter, an operation procedure of the control method of the header conversion system according to an embodiment of the present invention will be described in more detail with reference to FIG. 3.

When the user requests the HTTP document, it is determined whether the client 300 supports the HTTP document (S210), and parses the header information of the HTTP document to request a request line and a status line. ) And the header field (S220) are the same as described above with reference to FIG.

The step of converting the parsed header information into a binary code will be described in more detail over S231 to S234.

It is determined whether the request line is included in the parsed header information (S231).

If the request line is included in the parsed header information, the request line is encoded (S232). If the request line is not included in the parsed header information and only the status line is included, the header information is encoded (S233). ).

In the case of the S232 procedure or the S233 procedure, the header information is encoded in the header field (S234). The request line encoding, the state line encoding, and the header field encoding have been described above.

The header information of the converted HTTP document is decoded and transmitted to the internet network (S240). Thereafter, the procedure is the same as described above and will be omitted for convenience.

Although the above has been described with reference to a preferred embodiment of the present invention, those skilled in the art will be variously modified and changed within the scope of the invention without departing from the spirit and scope of the invention described in the claims below. I can understand that you can.

The present invention relates to a header conversion system and a control method thereof. More particularly, the present invention relates to a header conversion system and a control method thereof capable of reducing HTTP traffic in a wireless network section by compressing and converting header information of an HTTP document. will be.

According to the present invention by the above means, it is possible to convert the HTTP header information always attached at the time of HTTP document request / response in the wireless network to a binary code, thereby, unnecessary HTTP header at the time of HTTP document request / response By minimizing the information, you can reduce the overall HTTP traffic, making HTTP document movement over the wireless network more convenient in terms of time and cost.

1 is a block diagram of a header conversion system according to an embodiment of the present invention.

2 is a flowchart illustrating a control method of a header conversion system according to an embodiment of the present invention.

3 is a more detailed flowchart of a control method of a header conversion system according to an embodiment of the present invention.

<Description of Signs of Major Parts of Drawings>

100: Browser

300: Client

500: proxy server

Claims (15)

In the system for converting and transmitting the HTTP protocol header in the radio section, When the HTTP document is requested, the header of the HTTP document is parsed, and the parsed header information is classified into one of a request line and a status line and a header field and converted into binary code. A client for transmitting the HTTP document including the converted header to the wireless section; And And a proxy server for receiving the HTTP document including the converted header, decoding the converted header, and transmitting the decoded header to an internet network. The method of claim 1, The client encodes the request line into 4 bits if the request line is included in the parsed header, otherwise encodes the status line into 7 bits, and encodes the header field of the parsed header into 6 bits. Header conversion system. In the system for converting and transmitting the HTTP protocol header in the radio section, Parse the header of the HTTP document, and if the parsed header includes a request line, converts the request line and the header field into binary code, and does not include the request line in the parsed header information. A client converting a status line and the header field into a binary code, and transmitting an HTTP document including the converted header to the wireless section; And And a proxy server for receiving the HTTP document including the converted header, decoding the converted header, and transmitting the decoded header to an internet network. The method of claim 3, When the parsed header includes a request line, the client encodes bit information representing a method and an HTTP version included in the request line. Header conversion system. delete The method of claim 3, The client encodes the status line into an HTTP version and bit information representing a status code and reason phrases when the request line is not included in the parsed header. Header conversion system. The method of claim 3, And the client encodes the header field into bit information representing a name of the header field. In the client of the header conversion system, Parse HTTP header information into a request line, a status line, and a header field. The request line is encoded with a bit representing a method and an HTTP version, and the status line is encoded with a bit representing an HTTP version and a status code & reason phrases. and, And encoding the header field into bits representing a name of the header field. The method of claim 8, And the request line is encoded in 4 bits, the status line in 7 bits, and the header field in 6 bits. In the control method of the header conversion system including a client (Client) and a proxy server (Proxy Server), Parsing header information of the HTTP document when an HTTP document is requested by a user; Classifying the parsed header information into one of a request line and a status line and a header field, converting the parsed header information into a binary code, and transmitting the converted header information; And Receiving the HTTP document including the converted header information, decoding the header information, and transmitting the decoded header information to an internet network. delete The method of claim 10, The converting of the header information into the binary code may include: determining whether a request line is included in the header information; Request line encoding the header information when the request line is included, and status line encoding the header information when the request line is not included and only the status line; And And encoding the header information in a header field. The method of claim 12, The request line encoding step includes encoding using a 4 bit to represent a method (method) and the HTTP version (version). The method of claim 12, The status line encoding may include encoding the HTTP version and a status code & reason phrases using 7 bits. The method of claim 12, The encoding of the header field may include encoding the header field to represent the name of the header field using 6 bits.

Images