WO2021068973A1

WO2021068973A1 - Data communication method and device employing application layer protocol

Info

Publication number: WO2021068973A1
Application number: PCT/CN2020/120468
Authority: WO
Inventors: 单卫华; 刘加财
Original assignee: 华为技术有限公司
Priority date: 2019-10-12
Filing date: 2020-10-12
Publication date: 2021-04-15
Also published as: CN112653656B; CN112653656A

Abstract

The present application discloses a data communication method employing an application layer protocol. Two different application layer protocol channels are established between a client and a server. The client sends, via one of the application layer protocol channels, request data generated by an application to a network service of the server, and the server returns, via the other of the application layer protocol channels, response data generated by the network service to the application. Two independent application layer protocol channels are used to transmit request data and response data respectively, thus improving the efficiency of accessing network services for applications.

Description

Data communication method and device based on application layer protocol

Technical field

This application relates to the field of computer technology, and in particular to a data communication method based on an application layer protocol, and a client, server, and service providing system that execute the method.

Background technique

In the era of big data, with the rapid growth of the types of network services, the processing capacity of each network service has also expanded. Therefore, the traditional deployment of network services through a single server has been difficult to meet the needs of massive services. At present, mainstream network service processing architectures are all distributed, with multiple servers deployed with network services cooperating to process massive amounts of business. Under this architecture, the Hypertest Transfer Protocol (HTTP) and Hypertext Transfer Protocol Secure (HTTPS) are designed to be used between network services running on different servers, as well as between clients and services. Communication between terminals.

Take HTTP as an example. In a common HTTP-based communication process, after a transmission control protocol (TCP) connection is established between the HTTP client and the HTTP server, the HTTP client sends a network request to the HTTP server. HTTP After receiving the network request, the server sends response information to the HTTP client according to the network request. Subsequently, the request ends, and the TCP connection established for the request is disconnected. This scenario is also called a short connection. Although the HTTP protocol also supports long connections, that is, multiple rounds of network requests and corresponding response messages are completed in one TCP connection, the communication efficiency between the client and the server is still insufficient.

Summary of the invention

This application provides a data communication method based on an application layer protocol, which improves the communication efficiency between application programs and network services.

The first aspect of this application provides a data communication method based on an application layer protocol, which includes: a channel management module on the client side and a channel management module on the server side between an application program running on the client side and a network service running on the server side Establish the first application layer protocol channel and the second application layer protocol channel; the client's protocol stack sends the request data generated by the application program to the network service through the first application layer protocol channel; after obtaining the request data, the network service according to The request data generates response data; the protocol stack of the server sends the response data to the application through the second application layer protocol channel; wherein, the first application layer protocol channel and the second application layer protocol channel are based on different Transport layer protocol connection. The first application layer protocol channel and the second application layer protocol channel are connected based on different transport layer protocols, that is, in the process of establishing the first application layer protocol channel and the second application layer protocol channel, two different Transport layer protocol connection.

Through two different application layer protocol channels, the data transmission of the application to the network service is not limited to the processing progress of the previous data, which improves the access efficiency of the application to the network service, and improves the connection between the application and the network service. Communication efficiency.

In a possible implementation, the application layer protocol is HTTP or HTTPS.

In a possible implementation manner, the client's protocol stack sends the subsequent request data generated by the application to the network service through the first application layer protocol channel, and the generation time of the subsequent request data is after the generation time of the request data . When the client's protocol stack sends the subsequent request data, it does not need to wait to receive the response data corresponding to the request data.

In a possible implementation, the request data is generated by an executor running in the application program, and the method further includes: the client generates a request data identification ID for the request data, and transmits it in the first application layer protocol channel The request data ID of each request data is different; the protocol stack of the client sends the request data and the request data ID to the network service through the first application layer protocol channel, where the request data and the request data ID are carried in The same message.

After the network service generates response data according to the request data, the method further includes: the server protocol stack sends the response data and the request data ID to the client through the same message through the second application layer protocol channel; The client determines the executor according to the request data ID received from the second application layer protocol channel; the client sends the response data to the executor.

A request data ID is assigned to each request data, and the request data ID and response data are returned to the client together, so that the client can identify the target executor of the response data (the executor who generated the request data) according to the request data ID. This allows the network service to process the request data more flexibly. No matter how the request data is processed in various orders, the response data generated by the network service can be accurately returned to the target executor.

In a possible implementation, after receiving the channel establishment request message for establishing the first application layer protocol channel and the channel establishment request message for establishing the second application layer protocol channel, the data processing pool of the server is the first An application layer protocol channel allocates the first space, and the second application layer protocol channel allocates the second space; the data processing pool of the server records the correspondence between the first space and the second space; the server will start from the first space The request data received by an application layer protocol channel is stored in the first space; after the network service generates the response data, the data processing pool stores the response data in the second space according to the corresponding relationship of the record.

The server allocates an independent space for each application layer protocol channel. The first space is used to store the request data sent by the first application layer protocol channel, and the second space is used to store network services generated according to the request data in the first space. The response data in the second space is sent to the client through the second application layer protocol channel. Allocate independent space for the two application layer protocol channels, which improves the server's management accuracy of the data transmitted in the application layer protocol channels.

The second aspect of the present application provides a service providing system, which includes at least one client and at least one server. At least one client and at least one server establish a connection through a communication network. There are applications running on each client, and the applications access the network services running on the server. The client in the service providing system executes the method provided by the client in the method provided in the first aspect, and the client in the service providing system executes the method provided by the server in the method provided in the first aspect.

The third aspect of the present application provides a data communication method based on an application layer protocol executed by a client. The method includes: a channel management module of the client generates a first channel establishment request message, the first channel establishment request message includes a first channel type field, and the first channel type field indicates establishment based on the first channel establishment request message The first application layer protocol channel is the request type, and the first channel establishment request message is sent to the server; the channel management module of the client generates a second channel establishment request message, and the second channel establishment request message includes the second channel Type field, the second channel type field indicates that the second application layer protocol channel established based on the second channel establishment request message is a response type, and the second channel establishment request message is sent to the server; wherein, the first The application layer protocol channel and the second application layer protocol channel are connected based on different transport layer protocols; the client's application program generates request data, and the client's protocol stack receives the request data, and then sends the request data through the first application layer protocol channel To the network service running on the server, the client's protocol stack receives the response data corresponding to the request data through the second application layer protocol channel.

In a possible implementation, the method further includes: the client's data matching pool generates a request data ID for the request data; the client's protocol stack sends the request data and the request data ID to the request data through the first application layer protocol channel The network service; the client's protocol stack receives the response data corresponding to the request data and the request data ID through the second application layer protocol channel; the client's data matching pool is based on the request data ID received from the second application layer protocol channel , Determine the executor who generated the request data, and send the response data to the executor.

The fourth aspect of the present application provides a client, which executes any method provided in the third aspect when the client is running. The client includes: a channel management module configured to generate a first channel establishment request, the first channel establishment request includes a first channel type field, and the first channel type field indicates a first application established based on the first channel establishment request The layer protocol channel is the request type; a second channel establishment request is generated, the second channel establishment request includes a second channel type field, and the second channel type field indicates that the second application layer protocol channel established based on the second channel establishment request is Response type; wherein, the first application layer protocol channel and the second application layer protocol channel are connected based on different transport layer protocols. Optionally, the client further includes an application program for generating request data, and sending the request data to the protocol stack. The client also includes a protocol stack for sending the first channel establishment request to the server; sending the second channel establishment request to the server; sending the request data to the server through the first application layer protocol channel A network service running on the computer; the response data corresponding to the request data is received through the second application layer protocol channel.

In a possible implementation, the client further includes: a data matching pool for generating a request data ID for the request data, and recording the correspondence between the executor who generated the request data and the request data ID; The data ID is sent to the protocol stack. The protocol stack is configured to send the request data and the request data ID to the network service through the first application layer protocol channel; receive the response data corresponding to the request data and the request data ID through the second application layer protocol channel; The response data and the request data ID are sent to the data matching pool. The data matching pool is also used to determine the executor who generated the request data according to the corresponding relationship of the record and the request data ID; and send the response data to the executor.

The fifth aspect of the present application provides a client, that is, a computer, including a processor and a memory. The processor is configured to access instructions in the memory to execute any method provided in the third aspect.

The sixth aspect of the present application provides a non-transitory readable storage medium. When the instructions stored in the non-transitory readable storage medium are executed by a client, the client executes any of the instructions provided in the aforementioned third aspect. method. Program instructions are stored in the storage medium. The storage medium includes, but is not limited to, volatile memory, such as random access memory, and non-volatile memory, such as flash memory, hard disk drive (HDD), and solid state drive (SSD).

The seventh aspect of the present application provides a computer program product. When the instructions contained in the computer program product are executed by a client, the client executes any of the methods provided in the foregoing third aspect. The computer program product may be a software installation package. In the case where any method provided in the foregoing third aspect needs to be used, the computer program product can be downloaded and the instructions contained in the computer program product can be executed on the client.

The eighth aspect of the present application provides a data communication method based on an application layer protocol executed by a server. The method includes: the protocol stack of the server receives a first channel establishment request message, the first channel establishment request message includes a first channel type field, and the first channel type field indicates the establishment based on the first channel establishment request message. The first application layer protocol channel is the request type. The protocol stack of the server receives a second channel establishment request message, the second channel establishment request message includes a second channel type field, and the second channel type field indicates a second application layer established based on the second channel establishment request message The protocol channel is a response type; wherein, the first application layer protocol channel and the second application layer protocol channel are connected based on different transport layer protocols. Subsequently, the protocol stack of the server receives the request data through the first application layer protocol channel. The network service of the server generates response data according to the request data. The protocol stack of the server sends the response data to the application program that generates the request data through the second application layer protocol channel.

In a possible implementation manner, the method further includes: the protocol stack of the server receives the request data ID corresponding to the request data through the first application layer protocol channel. After generating the response data, the data processing pool of the server establishes the corresponding relationship between the response data and the request data ID. The protocol stack of the server sends the response data and the request data ID to the client that generates the request data through the second application layer protocol channel.

In a possible implementation manner, the data processing pool of the server allocates a first space for the first application layer protocol channel; and allocates a second space for the second application layer protocol channel. The channel management module of the server records the correspondence between the first space and the second space. The protocol stack of the server side stores the request data received from the first application layer protocol channel into the first space. According to the corresponding relationship of the record, the protocol stack of the server stores the response data in the second space.

The ninth aspect of the present application provides a server that executes any method provided in the eighth aspect when the server is running. The server includes: a channel management module for receiving a first channel establishment request, the first channel establishment request includes a first channel type field, and the first channel type field indicates a first application established based on the first channel establishment request The layer protocol channel is the request type; the second channel establishment request is received, the second channel establishment request includes a second channel type field, and the second channel type field indicates that the second application layer protocol channel established based on the second channel establishment request is Response type; wherein, the first application layer protocol channel and the second application layer protocol channel are connected based on different transport layer protocols. The server also includes a protocol stack for receiving request data through the first application layer protocol channel. Optionally, the server also includes a network service, which is used to generate response data according to the request data, and send the response data to the protocol stack. The protocol stack is also used to send the response data to the application program that generated the request data through the second application layer protocol channel.

In a possible implementation, the protocol stack is also used to receive the request data ID corresponding to the request data through the first application layer protocol channel; to send the response data and the request data through the second application layer protocol channel ID to the client that generated the requested data.

In a possible implementation manner, the server further includes a data processing pool for allocating a first space for the first application layer protocol channel and a second space for the second application layer protocol channel. The channel management module is used to record the corresponding relationship between the first space and the second space. The protocol stack is used to store the request data received from the first application layer protocol channel into the first space. The channel management module is used to store the response data in the second space according to the corresponding relationship of the record.

The tenth aspect of the present application provides a server, that is, a computer, including a processor and a memory. The processor is configured to access instructions in the memory to execute any method provided in the eighth aspect.

The eleventh aspect of the present application provides a non-transitory readable storage medium. When the instructions stored in the non-transitory readable storage medium are executed by a server, the server executes any of the aforementioned eighth aspects. One method. Program instructions are stored in the storage medium. The storage medium includes, but is not limited to, volatile memory, such as random access memory, and non-volatile memory, such as flash memory, HDD, and SSD.

The twelfth aspect of the present application provides a computer program product. When the instructions contained in the computer program product are executed by a server, the server executes any of the methods provided in the eighth aspect. The computer program product may be a software installation package. In the case of using any method provided in the eighth aspect, the computer program product can be downloaded and the instructions contained in the computer program product can be executed on the server.

Description of the drawings

In order to explain the technical methods of the embodiments of the present application more clearly, the following will briefly introduce the drawings that need to be used in the embodiments.

Figure 1 is the architecture diagram of the service provision system provided by this application;

Figure 2 is another architecture diagram of the service providing system provided by this application;

Figure 3 is a schematic diagram of the protocol stack used by the client and server provided by this application;

Figure 4 is a schematic diagram of a channel establishment request message provided by this application;

Figure 5 is a schematic diagram of a data transmission message provided by this application;

FIG. 6 is another schematic diagram of a channel establishment request message provided by this application;

FIG. 7 is another schematic diagram of the data transmission message provided by this application;

FIG. 8 is a schematic flowchart of the data communication method provided by this application;

9 is a schematic diagram of the application layer protocol header included in the channel establishment request message provided by this application;

Figure 10 is a schematic diagram of the service providing system in the channel establishment process provided by this application;

FIG. 11 is a schematic diagram of the service providing system in the data transmission process provided by this application;

FIG. 12 is a schematic diagram of the service providing system in the data transmission process provided by this application;

FIG. 13 is a schematic diagram of the service providing system in the data transmission process provided by this application;

FIG. 14 is a schematic diagram of the service providing system in the data transmission process provided by this application;

FIG. 15 is a schematic diagram of application layer protocol request/response from the application perspective provided by this application;

FIG. 16 is a schematic diagram of the structure of the client provided by this application;

Figure 17 is a schematic diagram of the structure of the server provided by this application.

Detailed ways

The technical methods in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application. In this application, there is no logical or sequential dependency among the "first", "second", and "nth".

In this application, referring to FIG. 1, the service providing system includes at least one client and at least one server. The client and the server are interconnected through a communication network, and the server provides a web service to the client. Among them, the client can be, for example, a smart phone (smart phone), a personal digital assistant (personal digital assistant, PDA), a tablet computer, a laptop computer (laptop computer), a personal computer (PC), Servers and other equipment. Common servers include personal computers or servers. The communication network between the client and the server can be a wired communication network or a wireless communication network, for example: the fifth-generation mobile communication technology (5th-Generation, 5G) system, long term evolution (LTE) ) System, wireless fidelity (wireless fidelity, WiFi).

In this application, transaction per second (TPS) refers to the number of requests that the service providing system can process per second, and can be used to measure the throughput of the service providing system.

Based on FIG. 2, the client 200 and the server 400 in the service providing system are further introduced. At least one application program (application program 204 to application program 20N) is running on the client 200, and N is an integer greater than or equal to 4. There is at least one actor running in each application, and the actor can be a thread or a callback function. While the application is running, the executor of the application sends an application layer protocol request to at least one network service (network service 404 to network service 40M) running on the server 400, where N is an integer greater than or equal to 4 to request The network service performs corresponding processing according to the request. Taking HTTP requests as an example, common processing types (request methods) include POST, GET, PUT, etc.

The channel management module 203 running on the client 200 and the channel management module 403 running on the server 400 cooperate to establish a request channel and a response channel between the client 200 and the server 400. The request channel and the response channel are two independent application layer protocol channels. The request channel is used to transmit the application layer protocol request generated by the client 200 to the server 400, and the response channel is used to transmit the application layer protocol response generated by the server 400 according to the application layer protocol request to the client 200. In the solution provided in this application, the protocol stack 201, the data matching pool 202, and the channel management module 203 can be packaged into a software development kit (SDK), and the application program 20N manages the protocol stack 201, the data matching pool 202 or the channel Access to the module 203 is achieved by calling the application program interface (API) of the SDK.

The data processing pool 402 running on the server 400 is used to store multiple request data carried in the application layer protocol request and the identification ID of each request data, and to process the application layer protocol request for the network service in the application layer protocol response generated Each response data configuration ID. The ID of a request data is the same as the ID of the response data generated based on the request data, that is, the ID corresponding to a certain request data carried in the application layer protocol request is also configured by the data processing pool 402 to the ID carried in the application layer protocol response The response data corresponding to the request data. The data matching pool 202 running on the client 200 is used to allocate and record the ID of each request data carried in the application layer protocol request, so as to identify the response data corresponding to each request data.

Hereinafter, the protocol stack 201 running on the client 200 and the protocol stack 401 running on the server 400 are introduced through FIG. 3. Protocol stack 201 and protocol stack 401 include processing mechanisms related to multi-layer protocols. In Figure 3, the link layer protocol includes the processing mechanism of the link layer protocol, the network layer protocol includes the processing mechanism of the network layer protocol, the transport layer protocol includes the processing mechanism of the transport layer protocol, and the application layer protocol includes the processing mechanism of the application layer protocol. When the application program expects to access the network service, the application program generates multiple request data. After the multiple request data is encapsulated in the application layer protocol body according to the duplex channel protocol provided by this application in the protocol stack 201, it is further added and transmitted in sequence The layer protocol header, the network layer protocol header, and the link layer protocol header are then transmitted to the protocol stack 401 through the communication network. Figure 5 shows the encapsulated data transmission message. Each data transmission message carries at least one piece of data (request data or response data) and a request data ID.

Similarly, as shown in FIG. 4, the channel establishment request message used in the process of creating the request channel and the response channel is also encapsulated and generated layer by layer by the protocol stack 201. Each application layer protocol request or each application layer protocol response is composed of a channel establishment request message and multiple data transmission messages. After the message is sent to the server 400, the protocol stack 401 parses the message in the order of link layer protocol, network layer protocol, transport layer protocol, and application layer protocol to obtain the duplex channel protocol header and the duplex channel control carried in the body. Field.

Common link layer protocols include ethernet protocol, common network layer protocols include internet protocol, common transport layer protocols include TCP, and common application layer protocols include HTTP and HTTPS. Figures 6 and 7 show channel establishment request messages and data transmission messages based on common protocols.

FIG. 8 illustrates the data communication method 600 provided by the present application. The method includes three parts, namely, a channel establishment part, a data transmission part, and a channel closing part.

First, the channel establishment part includes S600, S601, and S602, where S601 and S602 can be executed in any order.

S600: The channel management module 203 sends a channel establishment request to the protocol stack 201. The channel establishment request carries the duplex channel control field used to establish the request channel and the duplex channel control field of the response channel, the specific content of the duplex channel control field used to establish the request channel and the duplex channel control field of the response channel See the follow-up for details.

The channel management module 203 may also send the duplex channel control field for establishing the requested channel and the duplex channel control field for the response channel to the protocol stack 201 through two channel establishment requests, respectively.

S601: The protocol stack 201 sends a channel establishment request message for establishing a request channel to the protocol stack 401.

After S601, the protocol stack 401 parses the channel establishment request message received in S601, and sends the parsed duplex channel control field to the channel management module 403. The channel management module 203 and the channel management module 403 establish a request channel between the application 204 of the client 200 and the network service 404 of the server 400 according to the duplex channel control field, and the request channel is an application layer protocol channel.

Refer to Figure 4 and Figure 6 for the channel establishment request message. Specifically, as shown in FIG. 9, the application layer protocol header includes the original field of the application layer protocol, and also includes the duplex channel control field carried in the channel establishment request. The content other than the duplex channel control field in the channel establishment request message is encapsulated by the protocol stack 201. The duplex channel control field includes the duplex channel ID and channel type. Taking the HTTP protocol as the application layer protocol as an example, the original field includes the request line and the request header, and the request line includes information such as the request method, uniform resource locator (URL), and protocol version. The request method is usually POST, and the URL points to the web service 404. The request header includes the Connection field and the Content-Type field, for example:

Connection:keep-alive

Content-Type:text/event-stream

The duplex channel control field includes the Duplex-Channel-ID (duplex channel ID) field and the Duplex-Channel-Type (channel type) field, for example:

Duplex-Channel-ID:1

Duplex-Channel-Type:request

The channel management module 203 and the channel management module 403 also assign a channel ID (channel-ID) of 0 to the request channel, and record the corresponding relationship between the duplex channel ID and the channel ID. Take the mark as <1,<0,>> as an example, the ID of the duplex channel is 1 and the ID of the request channel of the duplex channel is 0.

S602: The protocol stack 201 sends a channel establishment request message for establishing another request channel to the protocol stack 401.

After S601, the protocol stack 401 parses the channel establishment request message received in S602, and sends the parsed duplex channel control field to the channel management module 403. The channel management module 203 and the channel management module 403 establish a response channel between the application 204 of the client 200 and the network service 404 of the server 400 according to the duplex channel control field, and the response channel is an application layer protocol channel.

The request channel established in S601 and the response channel established in S602 are two independent application layer protocol channels, which are independently embodied in that the two application layer protocol channels are connected based on different transport layer protocols. Taking the application layer protocol using HTTP and the transport layer using TCP as an example, the HTTP channel established in S601 and the HTTP channel established in S602 are based on different TCP connections.

An application layer protocol channel is based on a TCP connection and transmits application layer protocol requests/responses through multiple packets carrying the same transport layer protocol header, network layer protocol header, and link layer protocol header. The sequence number of the transport layer protocol header of each message transmitted in an application layer protocol channel (for example, when the transport layer protocol adopts a TCP connection) may be different. The request channel established in S601 and the response channel established in S602 form a pair of duplex channels, that is, the request channel established in S601 transmits application layer protocol requests, and the response channel established in S602 transmits corresponding application layer protocol responses.

Similar to S601, refer to Fig. 4 and Fig. 6 for the channel establishment request message used in S602. Specifically, as shown in FIG. 9, the application layer protocol header includes the original field of the application layer protocol, and also includes the duplex channel control field carried in the channel establishment request. The content other than the duplex channel control field in the channel establishment request message is encapsulated by the protocol stack 201. The duplex channel control field includes the duplex channel ID and channel type. Taking the HTTP protocol as the application layer protocol as an example, the original field includes the request line and the request header, the request line includes the request method, uniform resource locator (URL), the request method is usually POST, and the URL points to the web service 404 ; The request header includes the Connection field and the Content-Type field, for example:

Connection:keep-alive

Content-Type:text/event-stream

The Connection field and the Content-Type field can also have other values, which are only examples here.

Duplex-Channel-ID:1

Duplex-Channel-Type:response

The channel management module 203 and the channel management module 403 also assign a channel ID (channel-ID) of 1 to the request channel, and record the corresponding relationship between the duplex channel ID and the channel ID. Take the record as <1,<0,1>> as an example to express that the duplex channel ID is 1, the request channel ID of the duplex channel is 0, and the response channel ID of the duplex channel is 1. As shown in Figure 10, after S601 and S602 are executed, a space is created for the request channel and the response channel in the data processing pool 402 to store the request data and the response data. The two spaces are marked as <1,< 0>>, <1,<1>>. The channel management module 203 also records the correspondence between the application 204 and the duplex channel ID 1 to determine the duplex channel ID belonging to the application 204 when the application 204 initiates a channel closing request, see S615 for details.

The channel management module 403 can record the 5-tuple (source/destination network protocol (IP) address, source/destination media access control (MAC) address, port number) carried in the channel establishment request message and Correspondence between duplex channel ID/channel ID. For example, the channel management module 403 records the correspondence between quintuple 0 and duplex channel ID 1/channel ID 0, and records the correspondence between quintuple 1 and duplex channel ID 1/channel ID 1. Then the channel management module 403 can determine that the duplex channel ID corresponding to the packet including the quintuple 1 is 1 and the channel ID is 1, and the channel management module 403 can determine the duplex channel ID corresponding to the packet including the quintuple 0 Is 1 and the channel ID is 0. By recording the corresponding relationship between the quintuple and the duplex channel ID/channel ID, the channel management module 403 can determine the duplex channel ID and the corresponding channel ID corresponding to each message. The five-tuple of the message can be parsed by the protocol stack 401 and sent to the channel management module 403.

Optionally, after S601, the channel management module 403 may return a channel establishment success response through the request channel to indicate that the request channel is successfully established. Similarly, after S602, the channel management module 403 may return a channel establishment success response through the response channel to indicate that the response channel is successfully established. In this case, the Connection field of the two channel establishment request messages sent in S601 and S602 needs to be keep-alive, so as to prevent the request channel and the response channel from being closed after the successful channel establishment response is returned to the client 200.

The execution of the above S600 is initiated by the application 204. When the application 204 initiates an application layer protocol request for the network service 404 for the first time or when the application 204 initializes an application layer protocol channel between the application 204 and the network service 404, the application 204 triggers the channel management module 203 to execute S600.

After S601 and S602, the application layer protocol channel between the application 204 and the network service 404 is established, the application 204 can transmit the request data to the network service 404, and the data transmission part includes S603 to S614.

S603: The executor of the application 204 generates request data, and sends the request data to the data matching pool 202.

The request data includes the processing type. Optionally, the request data may also include data blocks to be processed.

Among them, the processing type indicates the operation type of the network service. For example, the processing type may be new to instruct the network service 404 to store the data block to be processed after receiving the data block to be processed; for another example, the processing type may be replacement to instruct the network service 404 to receive the data to be processed Then, replace a certain data block with the data to be processed; for another example, the processing type can be delete to instruct the network service 404 to delete a certain data block. In this case, the requested data may not contain the data to be processed Block; For another example, the processing type may be access to instruct the network service 404 to return a certain data block to the application 204. In this case, the requested data may not include the data block to be processed.

S604: The data matching pool 202 generates a corresponding request data ID for the request data, and stores the request data ID.

As shown in FIG. 11, the solid-line box 0 in the data matching pool in FIG. 11 refers to the requested data ID 0. The data matching pool 202 also records the correspondence between the executor who generated the requested data and the requested data ID.

After S604, the data matching pool 202 may notify the application program 204 to suspend the executor generating the requested data, and wait for the response data corresponding to the requested data to be returned. Other executors of the application 204 are not affected, and can continue to send request data to the data matching pool 202.

S605: The data matching pool 202 sends the request data and the generated request data ID to the protocol stack 201.

S606: The protocol stack 201 generates a data transmission message, and sends the generated data transmission message to the protocol stack 401 through the request channel.

The data transmission message is shown in FIG. 5 or FIG. 7, wherein the application layer protocol body carries the request data and the request data ID. In FIG. 11, the request data ID 0 and the request data are sent to the protocol stack 401 through the request channel, and other parts of the data transmission message are omitted in FIG. 11.

S607: The protocol stack 401 parses the data transmission message, and stores the parsed request data ID 0 and the request data in the space <1, <0>> opened up for the request channel in the data processing pool 402.

When multiple pairs of duplex channels are established in the service providing system, the protocol stack 401 can determine the data transmission message according to the content of the data transmission message (for example, a quintuple) in the process of parsing the data transmission message Corresponds to the request channel or response channel in which duplex channel. After determining the channel to which the data transmission message belongs, the protocol stack 401 may store the parsed request data ID and request data in the space corresponding to the channel to which the data transmission message belongs in the data processing pool 402.

S608: The network service 404 obtains the request data ID 0 and the request data from the space <1, <0>>.

S609: The network service 404 generates response data according to the request data.

The response data includes the processing information of the requested data, such as the timestamp of the requested data executed by the network service, and the type of the network service. When the processing type included in the request data is access, the response data may also include content such as the data block accessed according to the requested data, the length of the accessed data block, and so on.

S610, the network service 404 stores the request data ID 0 and the response data in the data processing pool 402 to open up the space <1, <1>> for the response channel, as shown in FIG. 11.

The network service 404 accesses the channel management module 403 to obtain the corresponding relationship of the channel ID, and determines that the request data ID 0 obtained from the space corresponding to the channel ID 0 and the response data corresponding to the request data need to be sent to the space corresponding to the channel ID 1. Alternatively, the network service 404 sends the request data ID 0 and the response data to the channel management module 403, and the channel management module 403 determines the request data ID 0 and the request data ID 0 and data obtained from the space corresponding to the channel ID 0 according to the recorded correspondence of the channel ID. The response data corresponding to the request data needs to be sent to the space corresponding to the channel ID 1, and the channel management module 403 stores the request data ID 0 and the response data in the data processing pool 402. The space opened for the response channel <1, <1>> .

S611: The protocol stack 401 obtains the request data ID and response data from the space <1, <1>> in the data processor 402, and generates a data transmission message according to the obtained request data ID and response data.

The data transmission message generated in S611 is shown in FIG. 5 or FIG. 7, where the application layer protocol body carries the response data and the request data ID. In FIG. 12, the request data ID 0 and the response data are sent to the protocol stack 201 through the response channel, and the other parts of the data transmission message are omitted.

After the protocol stack 401 generates the data transmission message carrying the response data, the space opened by the data processing pool 402 is the requested data ID/request data and the requested data ID stored in the space <1, <0>> and <1, <1>> /Response data can be deleted to save the storage space of the server 400.

S612: The protocol stack 401 sends the generated data transmission message to the protocol stack 201 through the response channel.

In S612, the protocol stack 401 generates an application layer protocol response based on the application layer protocol request transmitted from the request channel, and returns the application layer protocol response to the protocol stack 201 through the response channel. In addition to the data transmission message (carrying response data), the application layer protocol response should also include the application layer protocol header. Before the protocol stack 401 returns the first response data through the response channel, it should also return a message including the application layer protocol header to the protocol stack 201. Refer to FIG. 4 or FIG. 6 for the format of the message. The application layer protocol header of the message carries the same duplex channel control field as the application layer protocol header of the channel establishment request message in S602, and also includes the original field of the application layer protocol. The application layer carried by the message The original field of the protocol may be the same as the part of the channel establishment request message in S602. For details, refer to the type of application layer protocol. Taking the HTTP protocol as an example, the application layer protocol header carried in the message is the header of the HTTP response in FIG. 15.

S613: The protocol stack 201 parses the data transmission message, and stores the parsed request data ID 0 and response data into the data matching pool 202, as shown in FIG. 13.

S614: The data matching pool 202 determines that the destination of the response data is the executor of the request data generated in S603 through the correspondence between the executor and the request data ID recorded in S604, and sends the response data to the executor.

After S614, one request of the executor of the application 204 to the network service 404 is processed. In this process, because request data and response data are transmitted using different application layer protocol channels, they do not interfere with each other, that is, these two different application layer protocol channels form a pair of duplex channels. Compared with the existing HTTP connection technology, the application 204 can continuously send request data through the request channel, and the next request data transmission does not need to wait for the reception of the response data corresponding to the previous request data, which improves the TPS of the service provision system and realizes This allows applications to have more efficient access to network services.

Taking FIG. 14 as an example, the application 204 generates request data 0 and request data P. P is any integer greater than 0, that is, the application 204 may send other request data to the server between the request data 0 and the request data P 400. After the request data 0 and the request data P are generated, they are sent to the server 400 through the request channel, and there is no need to wait for the reception of any response data during the sending process of the request data 0 and the request data P. After the server 400 receives the request data 0 and the request data P, the network service 404 can process the request data in any order, and the request data that cannot be processed temporarily can be cached in the data processing pool 402. As shown in FIG. 14, the response data P is generated before the response data 0, and the response data P can be sent back to the client 200 through the response channel first. Correspondingly, the existing HTTP connection technology is first-in-first-out (FIFO), that is, the request data first sent to the network service is processed first, and the request data that first arrives at the network service is not processed. Before the processing is completed, the subsequent request data cannot be processed. In contrast, in the method provided by the present application, the order in which the network service 404 processes the requested data may not be restricted by the FIFO, the processing mechanism is more flexible, and the degree of fineness of access control is improved.

As shown in Figure 15, from the perspective of the application program 204, after the data communication method provided by this application is adopted, from the channel establishment to the channel closing, the application program 204 sends a continuous survival through the request channel, and the length is not limited ( The number of data transmission messages is not limited) HTTP request (take HTTP request as an example, it can also be other application layer protocol requests). The header of the HTTP request (response), that is, the aforementioned channel establishment request message, and the body of the HTTP request (response) is transmitted through one or more data transmission messages. Correspondingly, the application 204 receives a continuously alive HTTP response of unlimited length through the response channel. Load the duplex channel protocol of this solution on top of the existing application layer protocol. First, you can borrow the existing application layer protocol channel creation/closing management process to avoid duplication of design. Second, rely on the existing application layer protocol. The stability of the application layer protocol channel can ensure that each data can be transmitted correctly. Third, from the perspective of the application program, what is sent/received is still the application layer protocol request/response, which reduces application changes. More adaptable.

After S615 and subsequent steps, it is the channel closing part.

S615: The application 204 sends a channel closing request to the channel management module 203.

When the application program 204 determines that the executor running on it has no new request data to be sent to the network service 404, it sends a channel closing request to the channel management module 203.

After the channel management module 203 receives the channel closing request, if multiple duplex channels are established between the client 200 and the server 400, the channel management module 203 needs to follow the application 204 and the duplex channel ID recorded in the channel establishment section. The corresponding relationship between, the duplex channel ID 1 is carried in the channel closing request, and the channel closing request carrying this information is sent to the protocol stack 201.

S616: The protocol stack 201 generates a channel close request message according to the channel close request, and sends the channel close request message to the protocol stack 401 through the request channel.

In addition to the duplex channel ID, the channel closing request message also carries the channel closing identifier. For the structure of the channel close request message, please refer to the data transmission message in Figure 5 or Figure 7. The difference is that the channel close request message can carry a channel close identifier. For example, a pre-appointed special ID is used in the request data ID. The ID is different from any request data ID, for example, -1. The data part of the channel closing request message can carry the duplex channel ID.

S617: The protocol stack 401 parses the channel close request message, and sends the duplex channel ID carried in the channel close request message to the channel management module 403.

The protocol stack 401 parses the channel close request message to obtain the channel close identifier and the duplex channel ID. Through the channel closing identifier, the protocol stack 401 determines that the function of the message is to close a certain duplex channel, so the protocol stack 401 sends the parsed duplex channel ID to the channel management module 403.

S618: The channel management module 403 determines that all data in the space created for the duplex channel ID in the data processing pool 402 has been processed.

Specifically, after the channel management module 403 obtains the ID of the duplex channel that needs to be closed, for example, duplex channel 1, it confirms whether the data in the space created for duplex channel 1 in the data processing pool 402 has been processed, and That is, is there any unprocessed request data in <1,<0>> and whether there is response data in <1,<1>> that has not been sent to the client 200. If there is unprocessed request data in <1,<0>> or response data in <1,<1>> that has not been sent to the client 200, the channel management module 403 waits for the preset time to confirm again Whether the data in the space created for duplex channel 1 in the data processing pool 402 has been processed until the network service 404 has processed all the request data and all the response data is sent to the client 200 (refer to S608 to S612). If there is no unprocessed request data in <1,<0>> and no response data in <1,<1>> that has not been sent to the client 200, the previous request data sent through duplex channel 1 and the corresponding The response data of has all been processed. In the case of using the data communication method provided by this application, it may happen that the speed at which the application generates the requested data is faster than the speed at which the network service processes the requested data. Therefore, the application program cannot directly instruct the channel management module to close the duplex channel. Instead, the channel management module on the server side must determine that all data has been properly processed before the duplex channel can be officially closed.

Optionally, S618 can also be replaced by an action in which the application 204 confirms that the response data corresponding to the request data sent by the executor running on it has been returned before S615. That is, when the application program 204 confirms that the response data corresponding to the request data sent by the executor running on it has been received, it executes S615, that is, sends a channel close request to the protocol stack 201. In this case, S618 is not required.

S619: The channel management module 403 sends a channel closing response to the protocol stack 401. The channel closing response carries the duplex channel ID and the channel closing identifier.

S620: The protocol stack 401 generates a channel close response message according to the channel close response, and sends the channel close response message to the protocol stack 201 through the response channel.

The channel closing response message carries the duplex channel ID and the channel closing identifier. For the structure of the channel closing response message, please refer to the data transmission message in Figure 5 or Figure 7. The difference is that the request data ID part can carry the channel closing identifier, such as a pre-appointed special ID, which is different from any request Data ID. The data part of the channel closing response message can carry the duplex channel ID.

After S620, the channel management module 203 and the channel management module 403 close the channel 0 and the channel 1. The specific closing method may adopt the method of closing the application layer protocol channel in the prior art.

After S618, the channel management module 403 may notify the data processing pool 402 to release the space created for the duplex channel 1 to save the storage resources of the server 400. The channel management module 403 may also delete the previously recorded correspondence between the duplex channel ID 1 and the channel ID 0 and the channel ID 1. After S620, the channel management module 203 can delete the previously recorded correspondence between the application 204 and the duplex channel ID 1, and the corresponding relationship between the duplex channel ID 1 and the channel ID 0 and the channel ID 1.

Figure 16 provides a client 800. The client 800 includes a bus 803, a processor 801, a communication interface 802, and a memory 804. The processor 801, the memory 804, and the communication interface 802 communicate through a bus 803. The communication interface 802 is used to communicate with the outside, for example, sending a channel establishment request message or a data transmission message to the communication network.

The processor 801 may be a central processing unit (English: central processing unit, abbreviated: CPU). The memory 804 may include a volatile memory (English: volatile memory), such as a random access memory (English: random access memory, abbreviation: RAM). The memory 804 may also include a non-volatile memory (English: non-volatile memory), such as a read-only memory (English: read-only memory, abbreviation: ROM), flash memory, HDD or SSD.

The memory 804 stores executable instructions, and the processor 801 executes the executable instructions to execute the actions on the client side in the data communication method provided in FIG. 8. Specifically, the memory 804 stores executable instructions to run the aforementioned application program, channel management module, data matching pool, and protocol stack. The memory 804 may also include executable instructions required to run the client operating system. The operating system can be LINUX ^TM , UNIX ^TM , WINDOWS ^TM etc.

Figure 17 provides a server 1000. The server 1000 includes a bus 1003, a processor 1001, a communication interface 1002, and a memory 1004. The processor 1001, the memory 1004, and the communication interface 1002 communicate through a bus 1003. The communication interface 1002 is used for communicating with the outside, for example, receiving a channel establishment request message or a data transmission message from a communication network.

Wherein, the processor 1001 may be a CPU. The memory 1004 may include volatile memory, such as RAM. The memory 1004 may also include non-volatile memory, such as ROM, flash memory, HDD or SSD.

The memory 1004 stores executable instructions, and the processor 1001 executes the executable instructions to execute the server side actions in the data communication method provided in FIG. 8. Specifically, the memory 1004 stores executable instructions to run the aforementioned network service, channel management module, data matching pool, and protocol stack. The memory 1004 may also include executable instructions required to run the server operating system. The operating system can be LINUX ^TM , UNIX ^TM , WINDOWS ^TM etc.

The descriptions of the processes corresponding to each of the above drawings have their respective focuses. For parts that are not detailed in a certain process, please refer to the related descriptions of other processes.

In the above-mentioned embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented by software, it can be implemented in the form of a computer program product in whole or in part. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on the computer, the processes or functions according to the embodiments of the present invention are generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instruction may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instruction may be transmitted from a website, computer, server, or data center through a cable (Such as coaxial cable, optical fiber, digital subscriber line or wireless (such as infrared, wireless, microwave, etc.) transmission to another website site, computer, server or data center. The computer-readable storage medium can be accessed by a computer Any usable medium in the data storage device or a data storage device including one or more usable media integrated servers, data centers, etc. The usable medium can be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a DVD), Or semiconductor media (such as SSD) and so on.

Claims

A data communication method based on an application layer protocol, characterized in that it comprises:

Establish a first application layer protocol channel and a second application layer protocol channel between the application running on the client and the network service running on the server;

Sending the request data generated by the application program to the network service through the first application layer protocol channel;

The network service generates response data according to the request data;

Sending the response data to the application through the second application layer protocol channel;

Wherein, the first application layer protocol channel and the second application layer protocol channel are connected based on different transport layer protocols.
The data communication method according to claim 1, wherein the request data is generated by an executor running in the application program, and the method further comprises:

The client generates a request data identification ID for the request data;

Sending the request data ID to the network service through the first application layer protocol channel;

After the network service generates response data according to the request data, the method further includes:

Sending the request data ID to the client through the second application layer protocol channel;

The client determines the executor according to the request data ID received from the second application layer protocol channel;

The client sends the response data to the executor.
3. The data communication method according to claim 1 or 2, wherein the method further comprises:

Allocating a first space for the first application layer protocol channel on the server side, and allocating a second space for the second application layer protocol channel;

Record the correspondence between the first space and the second space;

Storing, by the server, the request data received from the first application layer protocol channel in the first space;

According to the recorded correspondence relationship, the server stores the response data generated by the network service in the second space.
A data communication method based on an application layer protocol, characterized in that it comprises:

A first channel establishment request message is generated, the first channel establishment request message includes a first channel type field, and the first channel type field indicates a first application layer protocol established based on the first channel establishment request message The channel is the request type;

Sending the first channel establishment request message to the server;

A second channel establishment request message is generated, the second channel establishment request message includes a second channel type field, and the second channel type field indicates a second application layer protocol established based on the second channel establishment request message The channel is the response type;

Wherein, the first application layer protocol channel and the second application layer protocol channel are connected based on different transport layer protocols;

Sending the second channel establishment request message to the server;

Sending the request data generated by the application program to the network service running on the server through the first application layer protocol channel;

Receiving response data corresponding to the request data through the second application layer protocol channel.
The data communication method according to claim 4, wherein the method further comprises:

Generating a request data ID for the request data;

Sending the request data ID to the network service through the first application layer protocol channel;

Receiving the request data ID through the second application layer protocol channel;

Determine the executor who generates the requested data according to the request data ID received from the second application layer protocol channel;

The response data is sent to the executor.
A client, characterized in that it includes:

The channel management module is configured to generate a first channel establishment request, the first channel establishment request includes a first channel type field, and the first channel type field indicates a first application layer protocol established based on the first channel establishment request The channel is a request type; a second channel establishment request is generated, the second channel establishment request includes a second channel type field, and the second channel type field indicates a second application layer protocol channel established based on the second channel establishment request Is a response type; wherein the first application layer protocol channel and the second application layer protocol channel are connected based on different transport layer protocols;

The protocol stack is used to send the first channel establishment request to the server; send the second channel establishment request to the server; send the request data generated by the application program to the server through the first application layer protocol channel A network service running on the server; receiving response data corresponding to the request data through the second application layer protocol channel.
The client according to claim 6, wherein:

The data matching pool is used to generate a request data ID for the request data, record the correspondence between the executor who generated the request data and the request data ID; send the request data ID to the protocol stack;

The protocol stack is configured to send the request data and the request data ID to the network service through the first application layer protocol channel; receive the response corresponding to the request data through the second application layer protocol channel Data and the requested data ID; sending the response data and the requested data ID to the data matching pool;

The data matching pool is also used to determine the executor who generated the requested data according to the correspondence between the records and the requested data ID; and send the response data to the executor.
A client is characterized by comprising a processor and a memory, and the processor executes instructions in the memory to execute the method according to claim 4 or 5.
A non-transitory readable storage medium, wherein when the instructions stored in the non-transitory readable storage medium are executed by a client, the client executes the method according to claim 4 or 5.
A computer program product, wherein when the instructions contained in the computer program product are executed by a client, the client executes the method according to claim 4 or 5.
A data communication method based on an application layer protocol, characterized in that it comprises:

Receive a first channel establishment request message, where the first channel establishment request message includes a first channel type field, and the first channel type field indicates a first application layer protocol established based on the first channel establishment request message The channel is the request type;

A second channel establishment request message is received, the second channel establishment request message includes a second channel type field, and the second channel type field indicates a second application layer protocol established based on the second channel establishment request message The channel is the response type;

Wherein, the first application layer protocol channel and the second application layer protocol channel are connected based on different transport layer protocols;

Receiving request data through the first application layer protocol channel;

The response data corresponding to the request data is sent to the application program that generates the request data through the second application layer protocol channel.
The data communication method of claim 11, further comprising:

Receiving the request data ID corresponding to the request data through the first application layer protocol channel;

After generating the response data, the method further includes:

Sending the request data ID to the client that generates the request data through the second application layer protocol channel.
The data communication method according to claim 11 or 12, further comprising:

Allocating a first space for the first application layer protocol channel;

Allocating a second space for the second application layer protocol channel;

Record the correspondence between the first space and the second space;

Storing the request data received from the first application layer protocol channel in the first space;

According to the recorded correspondence relationship, the response data is stored in the second space.
A server, which is characterized in that it includes:

The channel management module is configured to receive a first channel establishment request, where the first channel establishment request includes a first channel type field, and the first channel type field indicates a first application layer protocol established based on the first channel establishment request The channel is a request type; a second channel establishment request is received, the second channel establishment request includes a second channel type field, and the second channel type field indicates a second application layer protocol channel established based on the second channel establishment request Is a response type; wherein the first application layer protocol channel and the second application layer protocol channel are connected based on different transport layer protocols;

The protocol stack is configured to receive request data through the first application layer protocol channel; and send response data corresponding to the request data to the application program that generates the request data through the second application layer protocol channel.
The server according to claim 14, characterized in that it comprises:

The protocol stack is further configured to receive the request data ID corresponding to the request data through the first application layer protocol channel; and send the response data and the request data ID to generate the request data through the second application layer protocol channel. The client requesting data.
The server according to claim 14 or 15, characterized in that it further comprises:

A data processing pool, configured to allocate a first space for the first application layer protocol channel, and allocate a second space for the second application layer protocol channel;

The protocol stack is configured to store the request data received from the first application layer protocol channel in the first space;

The channel management module is configured to record the corresponding relationship between the first space and the second space, and store the response data in the second space according to the recorded corresponding relationship.
A server is characterized by comprising a processor and a memory, and the processor executes instructions in the memory to execute the method according to any one of claims 11 to 13.
A non-transitory readable storage medium, wherein when the instructions stored in the non-transitory readable storage medium are executed by a server, the server executes any one of claims 11 to 13 method.
A computer program product, characterized in that, when the instructions contained in the computer program product are executed by a server, the server executes the method according to any one of claims 11 to 13.