WO2012083806A1

WO2012083806A1 - Http-based communication method and system, http server and http client

Info

Publication number: WO2012083806A1
Application number: PCT/CN2011/083929
Authority: WO
Inventors: 石磊
Original assignee: 华为技术有限公司
Priority date: 2010-12-21
Filing date: 2011-12-14
Publication date: 2012-06-28
Also published as: CN102065143A; CN102065143B

Abstract

The present invention provides an HTTP-based communication method and system, an HTTP server and an HTTP client. The method comprises: a server receiving, through an HTTP permanent connection of a concurrency type, an HTTP request message sent by a client, wherein the HTTP request message comprises a header field of processing identification information; and the server returning, through the HTTP permanent connection of the concurrency type, an HTTP response message to the client, wherein the HTTP response message comprises the header field of the processing identification information.

Description

HTTP-based communication method and system, HTTP server, HTTP client This application claims the application number of 201010613201 . 0, the invention name is "HTTP-based communication method and system, HTTP server, HTTP" submitted on December 21, 2010. The priority of the Chinese application of the "client" is incorporated herein by reference in its entirety.

Technical field

The embodiments of the present invention relate to communication technologies, and in particular, to a Hypertext Transfer Protocol (HTTP)-based communication method and system, an HTTP server, and an HTTP client. Background technique

In a communication system, an interface between a server and a client may use a Hyper Text Transfer Protocol (HTTP)-based connection, that is, an HTTP connection, for example, an IP Multimedia Subsystem (IMS). The Sr interface between the Application Server (AS) and the Multimedia Resource Function Controller (MRFC). The HTTP connection may include two types of connections, one is an HTTP temporary connection, and the other is an HTTP permanent connection. Both of the above HTTP connections need to be established before the client initiates an HTTP request to the server. The former is removed after the server returns an HTTP response to the client, and the latter is removed when no message is sent on the HTTP connection established over a period of time. Therefore, in order to avoid duplicate HTTP connections and HTTP connections, the above interfaces can use HTTP permanent connections. HTTP persistent connections can include two types, one is a parallel permanent (HTTP) permanent connection, and the other is a pipelining type of HTTP permanent connection. When multiple users simultaneously initiate HTTP requests to the server through the client, the former needs to establish multiple HTTP permanent connections at the same time to implement HTTP requests for multiple users simultaneously in parallel. The latter only needs one pipeline type HTTP. A permanent connection enables sequential processing of HTTP requests from multiple users in a pipelined manner.

In the above prior art, if an HTTP-connected interface uses a parallel HTTP persistent connection, multiple HTTP permanent connections need to be established at the same time, so that HTTP requests of multiple users can be processed simultaneously in parallel, and interface configuration management and maintenance are added. Complexity; if an HTTP-connected interface uses a pipeline-type HTTP persistent connection, the HTTP request and the HTTP response need to be preserved, reducing the efficiency of the interface. Summary of the invention

The embodiments of the present invention provide an HTTP-based communication method and system, an HTTP server, and an HTTP client, which are used to reduce the complexity of interface configuration management and maintenance using an HTTP connection, and improve the efficiency of an interface using an HTTP connection.

An embodiment of the present invention provides an HTTP-based communication method, including:

The server receives the HTTP request message sent by the client by using a persistent type HTTP persistent connection, where the HTTP request message includes a processing identifier information header field;

The server returns to the client through the concurrent type HTTP persistent connection

An HTTP response message, where the HTTP response message includes the processing identifier information header field.

An embodiment of the present invention provides another HTTP-based communication method, including:

The client sends an HTTP request message to the server by using a persistent HTTP persistent connection, where the HTTP request message includes a processing identifier information header field;

The client receives the HTTP response message returned by the server by using the HTTP type persistent connection of the concurrent type, where the HTTP response message includes the processing identifier information header field.

An embodiment of the present invention further provides an HTTP server, including:

a receiving module, configured to receive, by using a concurrent type of HTTP permanent connection, an HTTP request message sent by the client, where the HTTP request message includes a processing identifier information header field;

And a sending module, configured to return an HTTP response message to the client by using the HTTP persistent connection of the concurrent type, where the HTTP response message includes the processing identifier information header field. An embodiment of the present invention further provides an HTTP client, including:

a sending module, configured to send an HTTP request message to the server by using a persistent HTTP persistent connection, where the HTTP request message includes a processing identifier information header field;

And a receiving module, configured to receive, by using the HTTP type persistent connection of the concurrent type, an HTTP response message returned by the server, where the HTTP response message includes the processing identifier information header field.

The embodiment of the invention further provides a communication system based on the hypertext transfer protocol HTTP, including a client and a server, wherein:

The client is configured to send an HTTP request message to the server by using a concurrent type of HTTP permanent connection, where the HTTP request message includes a processing identifier information header field, and receiving the server return by using the concurrent type HTTP permanent connection. The HTTP response message, where the HTTP response message includes the processing identifier information header field;

The server is configured to receive the HTTP request message sent by the client by using the concurrent type HTTP persistent connection, and return the HTTP response message to the client by using the concurrent type HTTP permanent connection.

According to the foregoing technical solution, the server of the embodiment of the present invention receives the HTTP request message that is sent by the client and includes the processing identifier information header field by using the HTTP type persistent connection of the concurrency type, so that the HTTP persistent connection of the concurrency type can be returned to the client. The above process identifies the HTTP response message in the header field, which enables multiple HTTP requests to be processed through a concurrent type of HTTP persistent connection, thereby reducing the complexity of interface configuration management and maintenance using HTTP connections, and improving the use of HTTP connections. The efficiency of the interface. DRAWINGS

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, a brief description of the drawings used in the embodiments or the prior art description will be briefly described below, obviously, The drawings in the above description are some embodiments of the present invention, and those skilled in the art can obtain other drawings based on these drawings without any creative work.

1 is a schematic flow chart of a method for communicating based on HTTP according to Embodiment 1 of the present invention;

2 is a schematic flowchart of another HTTP-based communication method according to Embodiment 2 of the present invention;

FIG. 3 is a schematic flow chart of a HTTP-based communication processing method according to Embodiment 3 of the present invention; FIG.

4 is a schematic structural diagram of an HTTP server according to Embodiment 4 of the present invention;

FIG. 5 is a schematic structural diagram of an HTTP client according to Embodiment 5 of the present invention;

FIG. 6 is a schematic structural diagram of an HTTP-based communication processing system according to Embodiment 6 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 a partial embodiment of the invention, and not all of the embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative efforts are within the scope of the present invention.

If an HTTP connection interface uses a parallel permanent HTTP connection, multiple HTTP persistent connections need to be established at the same time, so that HTTP requests of multiple users can be processed simultaneously in parallel, which increases the complexity of interface configuration management and maintenance. If an HTTP-connected interface uses a pipelining type of HTTP persistent connection, the HTTP request and the HTTP response need to be preserved, reducing the efficiency of the interface. Therefore, the embodiment of the present invention proposes another HTTP permanent connection, that is, a concurrence type HTTP permanent connection.

1 is a schematic flowchart of a communication method based on HTTP according to Embodiment 1 of the present invention, where As shown in FIG. 1, the HTTP-based communication method of this embodiment may include the following steps: Step 101: A server receives an HTTP request message sent by a client by using a concurrent type HTTP persistent connection, where the HTTP request message includes processing identifier information ( Transaction-Id) header field;

The HTTP request message may include, but is not limited to, a GET request message and an OPTIONS request message.

Specifically, the foregoing processing identifier information header field may be defined as a decimal positive integer, and the value ranges from 0 to 4294967295, and may be used for matching HTTP response messages and HTTP request messages on the HTTP type persistent connection of the concurrent type, and the specific form may be As follows:

Transaction-Id = "Transaction -Id" ":" 1*DIGIT

Those skilled in the art can understand that if there is a proxy device between the client and the server, the proxy device needs to be able to support transparent transmission of the above-mentioned processing identifier information header field.

Step 102: The server returns an HTTP response message to the client by using the HTTP persistent connection of the concurrency type, where the HTTP response message includes the processing identifier information header field.

The HTTP response message may include, but is not limited to, a GET response message, an OPTIONS response message.

Specifically, the foregoing HTTP response message may be a success response message, or may also be a failure response message.

Further, before the foregoing step 101, the method further includes the step of the server interacting with the client to establish the HTTP type permanent connection of the concurrent type. Specifically, the server receives the setup HTTP connection request message sent by the client, where the establishment HTTP connection request message includes a connection type (Connection-Type) header field, and the server establishes a connection with the client according to the connection type header field. A concurrent type of HTTP persistent connection.

Specifically, the connection type header field may be used to indicate a concurrency type or a pipeline type. If the connection type header field included in the setup HTTP connection request message sent by the client to the server indicates the concurrency type, a concurrent type HTTP persistent connection is established. If the client sends it to the server Establish a connection type header field contained in the HTTP connection request message indicating the pipeline type, and then establish a pipeline type HTTP permanent connection. The specific form can be as follows:

Connection-Type = "Connection-Type" ":" 1#(connection-type) connection-type = pipelining | concurrence

Alternatively, the foregoing connection type header field may also be used to indicate a concurrency type. If the connection type header field is included in the HTTP connection request message sent by the client to the server, a concurrent type HTTP permanent connection is established, if the client sends the server to the server. The connection type header field is not included in the establishment HTTP connection request message, and a pipeline type HTTP permanent connection is established. The specific form can be: 3⁄4 mouth:

Connection-Type = "Connection-Type" ":" 1#(connection-type) connection-type = concurrence

Those skilled in the art can understand that if there is a proxy device between the client and the server, the proxy device needs to be able to support transparent transmission of the above connection type header field.

Further, if the server does not support the above connection type header field, a 406 error message may be returned to the client, so that the client re-initiates the establishment of the header field that does not contain the connection type to the server.

The HTTP connection request message, according to the method in the prior art, establishes a pipeline type HTTP persistent connection or establishes multiple parallel HTTP permanent connections.

Further, when there are multiple users simultaneously requesting an HTTP request to the server through the client, the HTTP-based communication method provided by the embodiment can implement concurrent processing in a concurrent manner by establishing a persistent HTTP persistent connection. HTTP requests from users.

In this embodiment, the server receives the HTTP request message that is sent by the client and includes the processing identifier information header field by using the HTTP type persistent connection of the concurrency type, so that the concurrency type can be adopted.

The HTTP persistent connection returns an HTTP response message including the above-mentioned processing identification information header field to the above client, so that multiple HTTP requests can be processed through a concurrent type of HTTP permanent connection, thereby reducing interface configuration management and maintenance using HTTP connection. Complexity, and the efficiency of interfaces that use HTTP connections. FIG. 2 is a schematic flowchart of another HTTP-based communication method according to Embodiment 2 of the present invention. As shown in FIG. 2, the HTTP-based communication method in this embodiment may include the following steps: Step 201: A client passes a concurrency type. The HTTP persistent connection sends an HTTP request message to the server, where the HTTP request message includes a processing identifier information (Transaction-Id) header field; wherein the HTTP request message may include but is not limited to a GET request message and an OPTIONS request message.

Transaction-Id = "Transaction -Id" ":" 1*DIGIT

Step 202: The client receives the HTTP response message returned by the server by using the HTTP persistent connection of the concurrency type, where the HTTP response message includes the processing identifier information header field.

Further, before the foregoing step 101, the method further includes the step of the client interacting with the server to establish the HTTP type permanent connection of the concurrent type. Specifically, the client sends an HTTP connection request message to the server, where the HTTP connection request message includes a connection type (Connection-Type) header field, so that the server establishes the client with the connection type header field. A persistent connection between HTTP types.

Specifically, the foregoing connection type header field may be used to indicate a concurrency type or a pipeline type, if the connection type header field indication included in the HTTP connection request message sent by the client to the server is sent to the server. The concurrency type establishes a persistent type of HTTP persistent connection. If the connection type header field included in the HTTP connection request message sent by the client to the server indicates the pipeline type, a pipeline type HTTP permanent connection is established. The specific form can be as follows:

Alternatively, the foregoing connection type header field may also be used to indicate a concurrency type. If the connection type header field is included in the HTTP connection request message sent by the client to the server, a concurrent type HTTP permanent connection is established, if the client sends the server to the server. The connection type header field is not included in the establishment HTTP connection request message, and a pipeline type HTTP permanent connection is established. The specific form can be shown below:

Further, if the server does not support the connection type header field, a 406 error message may be returned to the client, so that the client re-initiates an HTTP connection request message that does not include the connection type header field to the server, according to the prior art. The method of establishing a pipeline type of HTTP permanent connection or establishing multiple HTTP parallel connections in parallel.

In this embodiment, the client sends an HTTP request message including a processing identifier information header field to the server through the HTTP type persistent connection of the concurrent type, so that the header type including the processing identifier information returned by the server is received through the HTTP type persistent connection of the concurrent type. HTTP response message, which can handle multiple HTTP requests through a concurrent HTTP persistent connection, which reduces the complexity of interface configuration management and maintenance using HTTP connections, and improves the complexity. The efficiency of the interface connected with HTTP.

The technical solution of the first embodiment of the present invention and the above-mentioned second embodiment of the present invention will be described in detail by taking the IMS as an example. FIG. 3 is a schematic flowchart of a HTTP-based communication processing method according to Embodiment 3 of the present invention. As shown in FIG. 3, the HTTP-based communication processing method in this embodiment may include the following steps:

Step 301: The MRFC sends an HTTP connection request message to the AS, where the HTTP connection request message includes a connection type header field, where the connection type header field indicates a concurrency type.

Step 302: The AS establishes an HTTP permanent connection of a concurrency type with the MRFC according to the connection type header field, and returns an HTTP connection response message to the MRFC.

Step 303: The MRFC sends a GET request message to the AS, where the GET request message includes a processing identifier information header field.

E.g:

GET http://154.48.0.80:80/PromptRecogAndPlayDTMF.vxml HTTP/1.1 Transaction-Id: 8118

Content-Length: 0

Host: 154.48.0.80:80

Cache-Control: max-age= 1800000, max-stale= 1200000

Step 304: The AS returns a GET response message to the MRFC, where the GET response message includes the foregoing processing identifier information header field.

E.g:

HTTP/1.1 200 OK

Transaction-Id: 8118

Content-Length: 14057

<?xml version="1.0" encoding="UTF-8"?>

....vxml body....

In this embodiment, the MRFC sends an HTTP request message including a processing identifier information header field to the AS through a concurrent type HTTP persistent connection, so that the AS can pass the above-mentioned concurrent type HTTP. The permanent connection returns an HTTP response message containing the above-mentioned processing identification information header field to the MRFC, so that multiple HTTP requests can be processed through a concurrent HTTP persistent connection, thereby reducing the complexity of the Sr interface configuration management and maintenance, and improving the complexity. The efficiency of the Sr interface.

It should be noted that, for the foregoing method embodiments, for the sake of simple description, they are all expressed as a series of action combinations, but those skilled in the art should understand that the present invention is not limited by the described action sequence. Because certain steps may be performed in other sequences or concurrently in accordance with the present invention. Further, those skilled in the art should also understand that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by the present invention.

In the above embodiments, the descriptions of the various embodiments are different, and the details are not described in detail in an embodiment, and the related descriptions of other embodiments can be referred to.

4 is a schematic structural diagram of an HTTP server according to Embodiment 4 of the present invention. As shown in FIG. 4, the HTTP server in this embodiment may include a receiving module 41 and a sending module 42. The receiving module 41 receives the HTTP request message sent by the client by using a persistent type HTTP persistent connection, where the HTTP request message includes a processing identifier information header field, and the sending module 42 returns the HTTP to the client by using the concurrent type HTTP permanent connection. In response to the message, the HTTP response message includes the foregoing processing identifier information header field.

The functions of the server in the first embodiment of the present invention and the AS in the third embodiment of the present invention can be implemented by the HTTP server provided by the embodiment of the present invention.

In this embodiment, the receiving module receives the HTTP request message that is sent by the client and includes the processing identifier information header field by using the HTTP type persistent connection of the concurrent type, so that the sending module can return the foregoing processing to the client by using the HTTP type permanent connection of the concurrent type. The HTTP response message identifying the information header field enables multiple HTTP requests to be processed through a concurrent type of HTTP persistent connection, thereby reducing the complexity of interface configuration management and maintenance using HTTP connections, and improving the interface using HTTP connections. s efficiency.

Further, the HTTP server of this embodiment may further include an establishing module 43, Interact with the above client to establish the HTTP type permanent connection of the above concurrency type. Specifically, the establishing module 43 is specifically configured to receive an HTTP connection request message sent by the client, where the HTTP connection request message includes a connection type header field, and is established between the client and the client according to the connection type header field. Concurrent type of HTTP permanent connection.

FIG. 5 is a schematic structural diagram of an HTTP client according to Embodiment 5 of the present invention. As shown in FIG. 5, the HTTP client in this embodiment may include a sending module 51 and a receiving module 52. The sending module 51 sends an HTTP request message to the server by using a persistent type HTTP persistent connection, where the HTTP request message includes a processing identifier information header field, and the receiving module 52 receives the HTTP response message returned by the server by using the concurrent type HTTP permanent connection. The foregoing HTTP response message includes the foregoing processing identifier information header field.

The functions of the client in the second embodiment of the present invention and the function of the MRFC in the third embodiment of the present invention can be implemented by the HTTP client provided by the embodiment of the present invention.

In this embodiment, the sending module sends the HTTP request message including the processing identifier information header field to the server through the concurrent type HTTP permanent connection, so that the receiving module can receive the foregoing processing identifier information returned by the server through the HTTP type persistent connection of the concurrent type. The HTTP response message of the header field enables multiple HTTP requests to be processed through a concurrent type of HTTP persistent connection, thereby reducing the complexity of interface configuration management and maintenance using HTTP connections, and improving the efficiency of interfaces using HTTP connections. .

Further, the HTTP client of this embodiment may further include an establishing module 53 for interacting with the server to establish the HTTP type permanent connection of the concurrency type. Specifically, the establishing module 53 is specifically configured to send an HTTP connection request message to the server, where the establishing the HTTP connection request message includes a connection type header field, so that the server establishes a connection with the client according to the connection type header field. A concurrent type of HTTP persistent connection.

FIG. 6 is a schematic structural diagram of an HTTP-based communication processing system according to Embodiment 6 of the present invention. As shown in FIG. 6, the HTTP-based communication processing system of this embodiment may include a client 61 and a server 62, where: The client 61 is configured to send an HTTP request message to the server 62 through a concurrent type of HTTP persistent connection, where the HTTP request message includes a processing identification information header field, and an HTTP response message returned by the concurrent type HTTP permanent connection receiving server 62. The foregoing HTTP response message includes the foregoing processing identifier information header field;

The server 62 is configured to receive the above HTTP request message sent by the client 61 through the HTTP type persistent connection of the concurrency type described above, and to the client through the HTTP type persistent connection of the concurrency type described above.

61 returns the above HTTP response message.

The function of the client in the second embodiment of the present invention and the function of the MRFC in the third embodiment of the present invention can be implemented by the client 61 in the HTTP-based communication processing system provided by the embodiment of the present invention; The functions of the AS in the third embodiment of the present invention can be implemented by the server 62 in the HTTP-based communication processing system provided by the embodiment of the present invention.

The HTTP persistent connection returns an HTTP response message including the above-mentioned processing identification information header field to the above client, so that multiple HTTP requests can be processed through a concurrent type of HTTP permanent connection, thereby reducing interface configuration management and maintenance using HTTP connection. Complexity, and the efficiency of interfaces that use HTTP connections.

Further, the client 61 in this embodiment may be further configured to interact with the server 62 to establish the HTTP type permanent connection of the concurrency type. Correspondingly, the server 62 may further be configured to interact with the client 61 to establish the foregoing. Concurrent type of HTTP permanent connection.

A person skilled in the art can understand that all or part of the steps of implementing the above method embodiments may be completed by using hardware related to program instructions, and the foregoing program may be stored in a computer readable storage medium, and the program is executed when executed. The foregoing steps include the steps of the foregoing method embodiments; and the foregoing storage medium includes: a medium that can store program codes, such as R〇M, RAM, a magnetic disk, or an optical disk.

Finally, it should be noted that the above embodiments are merely illustrative of the technical solutions of the present invention, and are not intended to be limiting thereof; although the present invention has been described in detail with reference to the foregoing embodiments, It should be understood that: the technical solutions described in the foregoing embodiments may be modified, or some of the technical features may be equivalently replaced; and the modifications or substitutions do not deviate from the essence of the corresponding technical solutions. The spirit and scope of the technical programme.

Claims

Claim

A communication method based on the Hypertext Transfer Protocol (HTTP), comprising: the server receiving an HTTP request message sent by the client by using a persistent type of HTTP persistent connection, where the HTTP request message includes a processing identifier information header field;

2. The method according to claim 1, further comprising: the server interacting with the client to establish an HTTP permanent connection of the concurrent type.

3. The method according to claim 2, wherein the server interacts with the client, and establishing the concurrent type of HTTP permanent connection comprises:

The server receives an establishment HTTP connection request message sent by the client, where the establishment HTTP connection request message includes a connection type header field;

The server establishes a persistent type of HTTP permanent connection with the client according to the connection type header field.

The method according to any one of claims 1 to 3, wherein the concurrent type of HTTP permanent connection is used for an Sr interface between a client and a server in an IP Multimedia Subsystem IMS.

A communication method based on the Hypertext Transfer Protocol (HTTP), comprising: the client sending an HTTP request message to the server through a concurrent type of HTTP persistent connection, where the HTTP request message includes a processing identifier information header field;

The method according to claim 5, further comprising: the client interacting with the server to establish an HTTP permanent connection of the concurrent type.

7. The method according to claim 6, wherein the client and the server To interact, establishing the HTTP type of the persistent connection of the concurrency type includes:

The client sends an HTTP connection request message to the server, where the connection HTTP connection request message includes a connection type header field, so that the server establishes a relationship with the client according to the connection type header field. Concurrent type of HTTP permanent connection.

The method according to any one of claims 5 to 7, wherein the concurrent type HTTP permanent connection is used for an Sr interface between a client and a server in an IP Multimedia Subsystem IMS.

9. A hypertext transfer protocol HTTP server, comprising:

And a sending module, configured to return an HTTP response message to the client by using the HTTP persistent connection of the concurrent type, where the HTTP response message includes the processing identifier information header field.

10. The HTTP server of claim 9, further comprising a setup module for interacting with the client to establish the concurrent type of HTTP persistent connection.

The HTTP server according to claim 10, wherein the establishment module is specifically used for

Receiving an HTTP connection request message sent by the client, where the HTTP connection request message includes a connection type header field, and establishing a concurrent type HTTP permanent connection with the client according to the connection type header field. .

12. A hypertext transfer protocol HTTP client, comprising:

The receiving module is configured to receive, by using the HTTP type persistent connection of the concurrent type, an HTTP response message returned by the server, where the HTTP response message includes the processing identifier information header field.

The client according to claim 12, further comprising an establishing module, configured to interact with the server to establish the concurrent type HTTP permanent connection.

The client according to claim 13, wherein the establishing module is specifically configured to be used

Sending an HTTP connection request message to the server, where the establishment HTTP connection request message includes a connection type header field, so that the server establishes a concurrency type with the client according to the connection type header field. HTTP permanent connection.

15. A communication system based on Hypertext Transfer Protocol (HTTP), characterized in that it comprises a client and a server, wherein:

16. The system of claim 15 wherein:

The client is further configured to interact with the server to establish an HTTP permanent connection of the concurrent type;

The server is further configured to interact with the client to establish an HTTP permanent connection of the concurrent type.