CN112565337B - Request transmission method, server, client, system and electronic equipment - Google Patents
Request transmission method, server, client, system and electronic equipment Download PDFInfo
- Publication number
- CN112565337B CN112565337B CN202011232891.5A CN202011232891A CN112565337B CN 112565337 B CN112565337 B CN 112565337B CN 202011232891 A CN202011232891 A CN 202011232891A CN 112565337 B CN112565337 B CN 112565337B
- Authority
- CN
- China
- Prior art keywords
- request
- target conversion
- server
- layer
- gateway
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/565—Conversion or adaptation of application format or content
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer And Data Communications (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The invention provides a request transmission method, a server, a client, a system and electronic equipment, and belongs to the technical field of computers. In the method, a client can perform format conversion on a first request to obtain a second request, the second request is sent to a server, the data size of the second request is smaller than that of the first request, a gateway layer in the server performs format reduction on the second request to obtain the first request, the first request is sent to service layers, the number of the service layers is larger than that of the gateway layers, and the service layers execute corresponding processing operation according to the first request to obtain a processing result. Therefore, the resource consumed during the request transmission can be reduced, and the transmission efficiency can be improved. Meanwhile, the gateway layer is established in advance, and the second request is restored into the first request based on the gateway layer and then is sent to the service layer for response, so that the code of the service layer does not need to be changed, the transmission efficiency can be improved, the transmission cost is reduced, and the implementation cost is reduced.
Description
Technical Field
The invention belongs to the technical field of computers, and particularly relates to a request transmission method, a server, a client, a system and electronic equipment.
Background
With continuous iteration of services, parameters in requests sent by a client to a server become more and more, and further the requests become longer and longer.
When the request is too long, the transmission efficiency is low, more resources are consumed in the transmission process, and the implementation cost is high. Therefore, a request transmission method is needed to solve these problems.
Disclosure of Invention
The invention provides a request transmission method, a server, a client, a system and electronic equipment, which are used for solving the problems of more resources consumed by request transmission and higher implementation cost.
According to a first aspect of the present invention, there is provided a request transmission method applied to a system including a client and a server, where a gateway layer and a business layer are deployed, the method including:
the client converts the format of the first request to obtain a second request;
the client sends the second request to the server, and the data size of the second request is smaller than that of the first request;
the gateway layer performs format reduction on the second request to obtain the first request;
the gateway layer sends the first request to the service layers, and the number of the service layers is larger than that of the gateway layers;
and the service layer executes corresponding processing operation according to the first request to obtain a processing result.
According to a second aspect of the present invention, there is provided a request transmission method applied to a server, where a gateway layer and a service layer are deployed, the method including:
the gateway layer receives a second request sent by a client, wherein the second request is obtained by the client through format conversion according to a first request, and the data size of the second request is smaller than that of the first request;
the gateway layer performs format reduction on the second request to obtain the first request;
the gateway layer sends the first request to the service layers, and the number of the service layers is larger than that of the gateway layers;
and the service layer executes corresponding processing operation according to the first request to obtain a processing result.
According to a third aspect of the present invention, there is provided a request transmission method applied to a client, the method including:
carrying out format conversion on the first request to obtain a second request;
and sending the second request to a server, wherein the data size of the second request is smaller than that of the first request.
According to a fourth aspect of the present invention, there is provided a request transmission system comprising: the system comprises a client and a server, wherein a gateway layer and a service layer are deployed in the server;
the client is used for carrying out format conversion on the first request to obtain a second request;
the client is further used for sending the second request to the server; the data size of the second request is smaller than the data size of the first request;
the gateway layer is used for carrying out format reduction on the second request to obtain the first request;
the gateway layer is further configured to send the first request to the service layer; the number of the service layers is greater than that of the gateway layers;
and the service layer is used for executing corresponding processing operation according to the first request to obtain a processing result.
According to a fifth aspect of the present invention, there is provided a server, comprising: a gateway layer and a service layer;
the gateway layer is used for receiving a second request sent by the client; the second request is obtained by the client terminal through format conversion according to the first request, and the data size of the second request is smaller than that of the first request;
the gateway layer is further configured to perform format reduction on the second request to obtain the first request;
the gateway layer is further configured to send the first request to the service layer; wherein the number of the service layers is greater than the number of the gateway layers;
and the service layer is used for executing corresponding processing operation according to the first request to obtain a processing result.
According to a sixth aspect of the present invention, there is provided a client, comprising:
the conversion module is used for carrying out format conversion on the first request to obtain a second request;
the sending module is used for sending the second request to a server; wherein the data size of the second request is smaller than the data size of the first request.
In yet another aspect of the present invention, there is also provided a computer-readable storage medium having stored therein instructions, which, when run on a computer, cause the computer to execute the request transmission method of the second aspect described above.
In yet another aspect of the present invention, there is also provided a computer-readable storage medium having stored therein instructions, which, when run on a computer, cause the computer to execute the request transmission method of the third aspect described above.
In yet another aspect of the present invention, there is also provided a computer program product containing instructions which, when run on a computer, cause the computer to perform the request transmission method according to the second aspect described above.
In yet another aspect of the present invention, there is also provided a computer program product containing instructions which, when run on a computer, cause the computer to perform the request transmission method according to the third aspect.
Aiming at the prior art, the invention has the following advantages:
the client can perform format conversion on the first request to obtain a second request, and send the second request to the server, wherein the data size of the second request is smaller than that of the first request, then, a gateway layer in the server performs format reduction on the second request to obtain the first request, and sends the first request to the service layer, wherein the number of the service layers is larger than that of the gateway layers, and the service layer executes corresponding processing operation according to the first request to obtain a processing result. Therefore, the first request is converted into the second request with smaller data size for transmission, so that the resource consumed during the request transmission can be reduced, and the transmission efficiency can be improved. Meanwhile, the gateway layer is established in advance, the second request is restored into the first request based on the gateway layer and then is sent to the service layer for response, so that the code of the service layer does not need to be changed, and the number of the service layers is not more than that of the gateway layers, so that the processing amount spent on establishing the gateway layer is less than the code change amount of the service layer to a certain extent under the condition of realizing request restoration. Therefore, the transmission efficiency can be improved, the transmission cost is reduced, and the implementation cost is reduced.
The foregoing description is only an overview of the technical solutions of the present invention, and the embodiments of the present invention are described below in order to make the technical means of the present invention more clearly understood and to make the above and other objects, features, and advantages of the present invention more clearly understandable.
Drawings
Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiments. The drawings are only for purposes of illustrating the preferred embodiments and are not to be construed as limiting the invention. Also, like reference numerals are used to refer to like parts throughout the drawings. In the drawings:
fig. 1 is a flowchart illustrating steps of a request transmission method according to an embodiment of the present invention;
FIG. 2 is a flow chart illustrating steps of another method for request transmission according to an embodiment of the present invention;
FIG. 3 is a schematic diagram of a transition provided by an embodiment of the present invention;
FIG. 4 is a flowchart illustrating steps of a method for transmitting a request according to another embodiment of the present invention;
FIG. 5 is a schematic diagram of a structure provided by an embodiment of the present invention;
FIG. 6 is a schematic diagram of another configuration provided by an embodiment of the present invention;
fig. 7 is a block diagram of a request transmission system according to an embodiment of the present invention;
fig. 8 is a block diagram of a server according to an embodiment of the present invention;
fig. 9 is a block diagram of a client according to an embodiment of the present invention;
fig. 10 is a schematic structural diagram of an electronic device according to an embodiment of the present invention.
Detailed Description
Exemplary embodiments of the present invention will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the invention are shown in the drawings, it should be understood that the invention can be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art.
Fig. 1 is a flowchart of steps of a request transmission method provided in an embodiment of the present invention, where the method may be applied to a system including a client and a server, and a gateway layer and a service layer may be deployed in the server, as shown in fig. 1, the method may include:
Step 102, the client sends the second request to the server; the data size of the second request is smaller than the data size of the first request.
In the embodiment of the present invention, the client may also be referred to as an APP front end, and may be used to provide Application (APP) front end services. The server, which may also be referred to as a service backend, may be used to provide services to clients. For example, the server may be a background server corresponding to the APP. The first request can be a request which needs to be sent to the server by the client, the first request is determined according to the operation of the client by the user, and the first request can be used for requesting the service from the server. The information carried by the second request and the information carried by the first request can be the same, and the request structures can be different, so that the data size of the second request can be smaller than that of the first request, the resource consumed during request transmission is reduced, and the transmission efficiency is improved. For example, the first request may be a GET request carrying request parameters in the form of URLs, and the second request may be a POST request carrying compressed request parameters, where the compressed request parameters are carried by a request body (body).
And 103, the gateway layer performs format reduction on the second request to obtain the first request.
And step 104, the gateway layer sends the first request to the service layers, wherein the number of the service layers is larger than that of the gateway layers.
In the embodiment of the present invention, the gateway layer may be a virtual service that is preset to implement the reduction of the second request into the first request and send the first request to the service layer. By way of example, it may be an executable software program. The service layer may be configured to respond to the received first request, and further provide a corresponding service for the functions supported by the client, so that each function supported by the client can be performed normally. Furthermore, in the embodiment of the present invention, the second request is restored to the first request and then sent to the service layer for processing, so that the service layer can still process the first request according to the original request processing logic while improving the transmission efficiency and reducing the transmission cost. Compared with the mode of modifying the service layer and directly processing the service layer according to the second request, the embodiment of the invention does not need to modify the processing logic of the service layer, thereby reducing the implementation cost to a certain extent.
Further, since there are many functions supported by the client, there are many service layers in the server. For example, assuming that the functions supported by the client include private chat, group chat, comment, video playing, video sharing, and video sharing, the server may include a plurality of business layers supporting the functions. And if the codes of all service layers in the server are modified in advance, each service layer is provided with a restoring logic for restoring the second request into the first request. In this way, the first request can be converted into the second request for transmission, and the second request can be directly restored by the service layer. However, the number of service layers is often large, which results in a large amount of modification and high cost for the service end. In the embodiment of the invention, only a gateway layer is needed to be added, and the code of the service layer is not needed to be changed, so that the transmission efficiency can be improved, the transmission cost is reduced, meanwhile, the invasion to the service layer is reduced to the greatest extent, and the implementation cost is reduced. It should be noted that the number of service layers and the number of gateway layers may be set according to actual requirements, which is not limited in the embodiment of the present invention. Optionally, the number of service layers may be 1, so that implementation cost can be maximally saved.
And 105, the service layer executes corresponding processing operation according to the first request to obtain a processing result.
In the embodiment of the invention, the service layer can execute the processing operation corresponding to the first request to obtain the processing result and make the corresponding response according to the processing result. The processing operation corresponding to the first request may be determined by the role of the first request. For example, assuming that the first request is for obtaining video data of video a, the service layer may search for the video data of video a and return the video data to the client.
In summary, in the request transmission method provided in the embodiment of the present invention, the client may perform format conversion on the first request to obtain a second request, and send the second request to the server, where the data size of the second request is smaller than the data size of the first request, then, the gateway layer in the server performs format reduction on the second request to obtain the first request, and sends the first request to the service layer, where the number of the service layers is greater than the number of the gateway layers, and the service layer executes corresponding processing operation according to the first request to obtain a processing result. Therefore, the first request is converted into the second request with smaller data size for transmission, so that the resource consumed during the request transmission can be reduced, and the transmission efficiency can be improved. Meanwhile, the gateway layer is established in advance, the second request is restored into the first request based on the gateway layer and then is sent to the service layer for response, so that the code of the service layer does not need to be changed, and the number of the service layers is not more than that of the gateway layers, so that the processing amount spent on establishing the gateway layer is less than the code change amount of the service layer to a certain extent under the condition of realizing request restoration. Therefore, the transmission efficiency can be improved, the transmission cost can be reduced, and the implementation cost can be reduced.
Furthermore, in the embodiment of the present invention, by reducing the resources required to be consumed in transmitting the request, the traffic and the bandwidth required for transmission can be further reduced, and thus the traffic and the bandwidth resources can be saved.
Further, fig. 2 is a flowchart of steps of another request transmission method provided in an embodiment of the present invention, where the method may be applied to a client, and as shown in fig. 2, the method may include:
Step 202, sending the second request to a server, where the data size of the second request is smaller than the data size of the first request.
In summary, in the request transmission method provided in the embodiment of the present invention, the client may perform format conversion on the first request to obtain the second request, and send the second request to the server, where a data size of the second request is smaller than a data size of the first request, so that resources required to be consumed in transmitting the request may be reduced and transmission efficiency may be improved by converting the first request into the second request with a smaller data size for transmission.
Optionally, the operation of performing format conversion on the first request to obtain the second request may be implemented by the following steps a to B:
and step A, selecting a target conversion mode from preset optional conversion modes.
In this embodiment of the present invention, the selectable conversion manner may be a preset manner for converting the first request into the second request. An optional conversion mode may correspond to a conversion mode under a conversion protocol or a conversion mode under a conversion version. That is, the conversion modes characterized by different optional conversion modes have different conversion protocols, or the versions of the conversion modes characterized by different optional conversion modes are different. When the target conversion mode is selected from the preset selectable conversion modes, the conversion configuration information may be read first, and then the selectable conversion mode corresponding to the conversion configuration information may be determined as the target conversion mode. The conversion configuration information may be set by the user according to actual requirements.
And B, carrying out format conversion on the first request according to the target conversion mode to obtain a second request, wherein the second request carries a target conversion identifier corresponding to the target conversion mode.
In the embodiment of the present invention, the target conversion identifier may be used to uniquely identify a target conversion manner, and the representation form of the target conversion identifier may be a number, a character, a combination thereof, or the like. And converting by a target conversion mode, so that the conversion mode can meet the requirements of users. Meanwhile, the second request carries the target conversion identifier corresponding to the target conversion mode, so that the server can conveniently acquire the conversion mode used in the conversion in the subsequent steps, and further conveniently select the corresponding recovery mode.
Optionally, the first request may include a request path and request parameters. The request paths are used for pointing to corresponding service layers in the server, and the service layers pointed by different request paths are different. The request parameters may include parameters required by the service layer in response to the first request, such as parameters for performing authentication, parameters indicating the required content of the request, and so on. The second request may include a first flag bit, a header, and a body. Optionally, converting the format of the first request according to a target conversion manner, and obtaining the second request may include sub-step B1 to sub-step B1:
substep B1: and extracting a request path and request parameters in the first request.
Substep B2: and taking the request path as a designated zone bit of a second request to be generated, taking the target conversion identifier as a head of the second request to be generated, taking the request parameter as a body of the second request to be generated according to the target conversion mode, and compressing the body to obtain the second request.
In the embodiment of the present invention, the first request may be analyzed first, and then the request path and the request parameter may be extracted from the analyzed first request. The designated flag bit can be preset according to actual requirements and is used for storing the position of the request path. In the embodiment of the invention, the request path is independently stored, so that the path information can be conveniently and rapidly acquired when a second request is sent to the service layer according to the request path, and the sending efficiency is further improved. Meanwhile, the target conversion identifier is used as a header (header) of the second request to be generated, so that the server side in the subsequent step can conveniently acquire the conversion mode used in the conversion, and further conveniently select the corresponding reduction mode.
Further, when the request parameter is used as a body of the second request to be generated, the processing modes corresponding to different target conversion modes are different. Optionally, the selectable conversion manner may include a first selectable conversion manner and a second selectable conversion manner, and a processing manner corresponding to the first selectable conversion manner may be to directly use the request parameter as a body. The processing mode corresponding to the second optional conversion mode may be that the request parameter is used as a body according to a Key-Value pair (KV) form. Specifically, the operation of using the request parameter as a body may include: substep (1): and when the target conversion mode is the first optional conversion mode, directly taking the request parameter as a body. Therefore, the amount of change of the content in the request parameters can be reduced as much as possible by directly putting the request parameters into the device, and further parameter errors are avoided. Substep (2): and when the target conversion mode is a second optional conversion mode, combining the parameter name of each parameter in the request parameters and the corresponding parameter value into a key value pair, and taking the key value pair as a body. Therefore, the data carried in the body can be more orderly by putting the data in a key value pair mode, and the data is convenient to transmit.
Further, a compression mode used may be defined in the target conversion mode. For example, fig. 3 is a schematic diagram of a conversion provided by the embodiment of the present invention, as shown in fig. 3, 01 denotes a first request, where the content in the block shown in 01 is a partial content of the first request. And 02 denotes the converted second request. 02a denotes the designated flag of the second request, and the content in the box denoted 02a shows part of the content of the request path. 02b represents the header of the second request, wherein "Content-Encoding" is a field in the target translation identifier for representing the compression method used by the target translation method. For example, it is assumed that the compression method supported by the target conversion method is gzip compression algorithm or brotli compression algorithm. The value of the Content-Encoding field may be "gzip/br" as shown in fig. 3. Accordingly, when compressing the body according to the target conversion manner, one of the compression manners supported by the target conversion manner may be selected for compression, for example, the body may be compressed according to a gzip compression algorithm, or the body may be compressed according to a brotli compression algorithm. Further, assuming that the target conversion manner is a first optional conversion manner with a Version of "1.0", the identifier corresponding to the first optional conversion manner may be "Convert-Version: 1.0". Further, 02c denotes a compressed body, and the content in the box shown in 02c shows a part of the content of the request parameter.
It should be noted that sometimes a client may need to directly send a POST request to a server, in this case, the server may directly receive and process the POST request without restoring. Therefore, in the embodiment of the present invention, the target conversion identifier may be added to the second request when the server needs to perform the restoration, so that the server can conveniently know whether the restoration needs to be performed, and further, unnecessary restoration operations are prevented from being performed.
It should be noted that, the designated flag may also store a network protocol version adopted by the first request, which is not limited in this embodiment of the present invention. For example, assume that the first request is a GET request with a size of 1634 bytes (byte) with a network protocol version of HTTP/1.1:
“http://mpaas.iqiyi.com/control/1.0/locateapp_k＝b398b8ccbaeacca840073a7ee9b7e7e6&app_v＝11.3.0&app_gv＝&app_t＝0&platform_id＝10&dev_os＝4.4.2&dev_ua＝H60-L01&net_sts＝1&qyid＝4e3d2c2d72eac2d7818ccfa5f791efa51104&imei＝25352a6b26d4721fc80b7980a7e2a758&aid＝c3e829014537e725&mac＝9c:c1:72:f9:f7:bb&scrn_scale＝2&lang＝zh_CN&app_lm＝cn&oaid＝7feb9dfb-ffff-7ff3-dbaf-4fb7ff1912bc&psp_uid＝&psp_sub_uid＝&psp_cki＝&psp_status＝1&secure_v＝1&secure_p＝GPhone&cupid_id＝357143042125630&cupid_v＝3.45.004&core＝1&api_v＝10.7&profile＝％7B％22group％22％3A％221％2C2％22％2C％22counter％22％3A2％2C％22hy_id％22％3A％22％22％2C％22recall_firstdate％22％3A％22-1％22％2C％22first_time％22％3A％2220170823％22％7D&unlog_sub＝0&cust_count＝&dev_hw＝％7B％22mem％22％3A％22430.6MB％22％2C％22cpu％22％3A1708800％2C％22gpu％22％3A％22％22％7D&net_ip＝％7B％22province％22％3A％22％E6％B1％9F％E8％A5％BF％22％2C％22area％22％3A％22％E5％8D％8E％E4％B8％9C％22％2C％22respcode％22％3A0％2C％22timeout％22％3A0％2C％22cc％22％3A％22％E7％A7％BB％E5％8A％A8％22％2C％22city％22％3A％22％E4％B9％9D％E6％B1％9F％22％2C％22country％22％3A％22％E4％B8％AD％E5％9B％BD％22％7D&scrn_sts＝1&scrn_res＝720,1184&scrn_dpi＝320&psp_vip＝0&client_ip＝％7B％22province％22％3A％22％E6％B1％9F％E8％A5％BF％22％2C％22area％22％3A％22％E5％8D％8E％E4％B8％9C％22％2C％22respcode％22％3A0％2C％22timeout％22％3A0％2C％22cc％22％3A％22％E7％A7％BB％E5％8A％A8％22％2C％22city％22％3A％22％E4％B9％9D％E6％B1％9F％22％2C％22country％22％3A％22％E4％B8％AD％E5％9B％BD％22％7D&province_id＝14004&service_filter＝&used_skinid＝-1&youth_model＝0&no_rec＝0&xas＝1&gps＝115.954512,29.66844&gps_st＝3”
converting the first request to a second request, i.e., after converting to a POST request, the request may include:
and (3) specifying a flag bit: POST HTTP:// mpaas. iqiiyi. com/control/1.0/locate HTTP/1.1
Body: compressed character stream;
heads (heads):
Content-Encoding:gzip
Convert-Version:1.0。
where the size of the converted second request may be 989 bytes, it can be seen that the amount of data occupied by the request is reduced by about 45%. Accordingly, the processing resources consumed by transmitting the second request may be less than the processing resources consumed by transmitting the first request. Meanwhile, in the embodiment of the invention, the length of the request can be shortened by converting the first request into the second request. Therefore, the problem that the request fails due to data loss caused by the fact that the request data is intercepted in the sending process due to the overlong request can be solved.
Fig. 4 is a flowchart of steps of another request transmission method according to an embodiment of the present invention, where the method may be applied to a server, and a gateway layer and a service layer may be deployed in the server. As shown in fig. 4, the method may include:
And step 302, the gateway layer performs format reduction on the second request to obtain the first request.
And step 304, the service layer executes corresponding processing operation according to the first request to obtain a processing result.
In summary, in the request transmission method provided in the embodiment of the present invention, the gateway layer in the server may receive the second request sent by the client, and perform format reduction on the second request to obtain the first request. The second request is obtained by the client terminal through format conversion according to the first request, and the data size of the second request is smaller than that of the first request. And finally, the service layer can execute corresponding processing operation according to the first request to obtain a processing result. Therefore, the first request is converted into the second request with smaller data size for transmission, so that the resource consumed during the request transmission can be reduced, and the transmission efficiency can be improved. Meanwhile, the gateway layer is established in advance, the second request is restored into the first request based on the gateway layer and then is sent to the service layer for response, so that the code of the service layer does not need to be changed, and the number of the service layers is not more than that of the gateway layers, so that the processing amount spent on establishing the gateway layer is less than the code change amount of the service layer to a certain extent under the condition of realizing the request restoration. Therefore, the transmission efficiency can be improved, the transmission cost can be reduced, and the implementation cost can be reduced.
Optionally, the gateway layer and the service layer may be deployed in the same server; alternatively, the gateway layer and the service layer may be deployed in different servers in the same local area network. The server running the gateway layer may be called a front-end processor (Nginx), and the service layer may run in the same server as the gateway layer, so that the gateway layer transmits the first request to the service layer inside the device, and further, transmission resources consumed when the gateway layer sends the first request to the service layer are reduced to the greatest extent.
It should be noted that the processing logic executed by the front-end processor may be implemented by the lua script. The service layer and the gateway layer operate in different server scenes, the server operating the gateway layer can be called a service worker node, and after restoration is completed, the front-end processor can send a second request to the service worker node configured by the upstream.
Further, in an actual application scenario, the client is often far away from the server and located in a different local area network, and therefore, a large amount of transmission resources are often consumed in the process of directly sending the first request to the server by the client. The embodiment of the invention deploys the gateway layer and the service layer in different servers in the same local area network. Because the gateway layer and the service layer are in the same local area network, the transmission resource consumed by the gateway layer for sending the first request to the service layer is less than the transmission resource consumed by the client for directly sending the first request to the service layer. Therefore, the gateway layer can be operated by using a special server, and the transmission resource can be saved while the server can provide sufficient resources to operate the gateway layer.
Optionally, the second request may be obtained by the client performing format conversion on the first request according to the target conversion mode, and the second request may carry a target conversion identifier corresponding to the target conversion mode. Specifically, the implementation process of the conversion performed by the client may refer to the description in the related step.
Correspondingly, the gateway layer performs format reduction on the second request to obtain the first request, which can be realized through the following steps C to E:
and step C, extracting the target conversion identifier contained in the second request.
In the embodiment of the invention, the gateway layer can analyze the second request, and then read the content of the designated zone bit in the analyzed second request, so as to obtain the target conversion identifier.
And D, determining a target conversion mode according to the target conversion identifier.
And E, carrying out format reduction on the second request according to the target conversion mode to obtain the first request.
In the embodiment of the present invention, the process of restoring the second request to the first request may be understood as an inverse operation of the conversion operation performed by the client. In order to ensure that the second request can be correctly restored to the first request, in the embodiment of the present invention, the gateway layer may restore the target conversion manner indicated by the target conversion identifier. Optionally, according to the target conversion manner, performing format reduction on the second request to obtain the first request may be implemented by the following sub-steps E1 to E2:
sub-step E1: and decompressing the content in the body of the second request according to a reduction algorithm corresponding to the target conversion mode, and extracting the request parameter according to the decompressed content.
In this step, the compression algorithm used in the conversion may be determined according to the target conversion identifier. For example, assuming that the value of the content-encoding field in the target transform identifier is "gzip", the compression algorithm used may be determined to be gzip compression algorithm, and assuming that the value of the content-encoding field in the target transform identifier is "br", the compression algorithm used may be determined to be brotli compression algorithm. Accordingly, the gateway layer can decompress the data by using a restoration algorithm corresponding to the compression algorithm used in the conversion.
Further, when extracting the request parameter from the decompressed content, the corresponding putting mode may be determined according to the conversion mode indicated by the target conversion identifier, and the extracting mode may be determined according to the putting mode. For example, when the putting mode is direct putting, the content obtained after decompression may be directly extracted as the request parameter. When the input mode is a key value pair mode, each key value pair can be extracted from the content obtained after decompression, and then the content in all the key value pairs is combined to obtain the request parameter.
Sub-step E2: and extracting a request path from the designated zone bit of the second request, and generating the first request according to the request parameter and the request path within the default request length supported by the server.
In the embodiment of the present invention, the default request length may be the maximum length of the request that can be supported by the server, and if the request exceeds the default request length, the request is truncated to ensure that the request length is specific within the default request length, and a value in the designated flag bit may be read to obtain the request path. And then combining the request parameters and the request path to obtain a first request. Wherein the length of the combined request does not exceed the default request parameter length. Optionally, in this embodiment of the present invention, before performing sub-step D2, the length of the default request parameter supported by the server may be increased, specifically, the configuration parameter of the server may be set, so as to set the default request length as the maximum length supported by the server. In this way, the probability of the first request being truncated can be reduced, thereby ensuring the integrity of the first request.
Optionally, fig. 5 is a schematic structural diagram provided in an embodiment of the present invention, and as shown in fig. 5, the client, that is, the APP front end, may include an APP service layer and an APP network library, where the first request may be generated by the APP service layer, and the operation of converting the first request into the second request may be implemented by the APP network library. Therefore, conversion can be realized without changing the APP service layer, and the realization cost can be reduced. The server, namely, the service back end, can implement restoration through the front-end processor gateway layer, and send the first request obtained after restoration to the back-end service layer.
Further, fig. 6 is another schematic structural diagram provided in the embodiment of the present invention, as shown in fig. 6, the client may be a mobile terminal 01, and for example, the mobile terminal 01 may send the POST request obtained after the conversion to a front-end processor 03 running a gateway layer according to a domain name of a network and other servers 02 in the network, such as a relay server and a Load Balancing (LB) server. The domain name used by the mobile terminal 01 may be "mpass. Further, after the gateway layer completes the restoration, the GET request obtained by the restoration may be sent to the service server cluster 04, where one service server may correspond to one service layer. Further, GET requests transmitted to each service server in the spoke cluster can be passed through the front-end processor (NGINX: 80) with the port of "80" to the process (jetty: 8080) for processing.
Optionally, in the embodiment of the present invention, a failure rate of a manner of directly sending the first request and a failure rate of a request transmission method provided by the embodiment of the present invention may also be counted. For example, in a scenario where the first request is directly sent, the sampled data may be: total number of transmissions: 39856, wherein the number of failures: 302, accordingly, the failure rate is 302/39856 ═ 0.76%. In a scenario where the request transmission method provided by the embodiment of the present invention is used, the sampled data may be: total number of transmissions: 73333, wherein the number of failures: 332, the failure rate was 302/39856 ═ 0.45% accordingly
It can be seen that the failure rate is reduced from 0.76% to 0.45% and by about 40% compared to the direct transmission method. Therefore, the first request is converted into the second request to be sent, and the data volume required to be transmitted is reduced, so that the failure rate caused by overlong request is reduced.
Fig. 7 is a block diagram of a request transmission system according to an embodiment of the present invention, and as shown in fig. 7, the system 70 may include: a client 701 and a server 702, where a gateway layer and a service layer are deployed in the server;
the client 701 is configured to perform format conversion on the first request to obtain a second request;
the client 701 is further configured to send the second request to the server 702; the data size of the second request is smaller than the data size of the first request;
the gateway layer is used for carrying out format reduction on the second request to obtain the first request;
the gateway layer is further configured to send the first request to the service layer; the number of the service layers is greater than that of the gateway layers;
and the service layer is used for executing corresponding processing operation according to the first request to obtain a processing result.
In summary, in the system provided in the embodiment of the present invention, the client may perform format conversion on the first request to obtain a second request, and send the second request to the server, where a data size of the second request is smaller than a data size of the first request, then, a gateway layer in the server performs format reduction on the second request to obtain the first request, and sends the first request to the service layer, where the number of the service layers is greater than the number of the gateway layers, and the service layer executes corresponding processing operations according to the first request to obtain a processing result. Therefore, the first request is converted into the second request with smaller data size for transmission, so that the resource consumed during the request transmission can be reduced, and the transmission efficiency can be improved. Meanwhile, the gateway layer is established in advance, the second request is restored into the first request based on the gateway layer and then is sent to the service layer for response, so that the code of the service layer does not need to be changed, and the number of the service layers is not more than that of the gateway layers, so that the processing amount spent on establishing the gateway layer is less than the code change amount of the service layer to a certain extent under the condition of realizing request restoration. Therefore, the transmission efficiency can be improved, the transmission cost is reduced, and the implementation cost is reduced.
Fig. 8 is a block diagram of a server according to an embodiment of the present invention, and as shown in fig. 8, the server 80 may include:
a gateway layer 801 and a service layer 802;
the gateway layer 801 is configured to receive a second request sent by a client; the second request is obtained by the client through format conversion according to the first request, and the data size of the second request is smaller than that of the first request;
the gateway layer 801 is further configured to perform format restoration on the second request to obtain the first request;
the gateway layer 801 is further configured to send the first request to the service layer; wherein the number of the service layers is greater than the number of the gateway layers;
the service layer 802 is configured to execute a corresponding processing operation according to the first request to obtain a processing result.
Optionally, the second request is obtained by the client performing format conversion on the first request according to a target conversion mode; the second request carries a target conversion identifier corresponding to the target conversion mode;
the gateway layer 801 is specifically configured to:
extracting the target conversion identifier contained in the second request;
determining a target conversion mode according to the target conversion identifier;
and according to the target conversion mode, carrying out format reduction on the second request to obtain the first request.
Optionally, the gateway layer 801 is further specifically configured to:
decompressing the content in the request body of the second request according to the reduction algorithm corresponding to the target conversion mode, and extracting the request parameter from the decompressed content;
and extracting a request path from the designated zone bit of the second request, and generating the first request according to the request parameter and the request path within the default request length supported by the server.
Optionally, the server 80 further includes: and the increasing module is used for setting the default request length as the maximum length supported by the server.
Optionally, the server 80 is a server; the gateway layer 801 and the service layer 802 are deployed in the same server; alternatively, the gateway layer 802 and the service layer 802 are deployed in different servers in the same lan.
In summary, in the server provided in the embodiment of the present invention, the gateway layer may receive the second request sent by the client, and perform format restoration on the second request to obtain the first request. The second request is obtained by the client terminal through format conversion according to the first request, and the data size of the second request is smaller than that of the first request. And finally, the service layer can execute corresponding processing operation according to the first request to obtain a processing result. Therefore, the first request is converted into the second request with smaller data size for transmission, so that the resource consumed during the request transmission can be reduced, and the transmission efficiency can be improved. Meanwhile, the gateway layer is established in advance, the second request is restored into the first request based on the gateway layer and then is sent to the service layer for response, so that the code of the service layer does not need to be changed, and the number of the service layers is not more than that of the gateway layers, so that the processing amount spent on establishing the gateway layer is less than the code change amount of the service layer to a certain extent under the condition of realizing request restoration. Therefore, the transmission efficiency can be improved, the transmission cost is reduced, and the implementation cost is reduced.
Fig. 9 is a block diagram of a client according to an embodiment of the present invention, and as shown in fig. 9, the client 90 may include:
a conversion module 901, configured to perform format conversion on the first request to obtain a second request;
a sending module 902, configured to send the second request to a server; wherein the data size of the second request is smaller than the data size of the first request.
Optionally, the conversion module 901 is specifically configured to:
selecting a target conversion mode from preset optional conversion modes;
and according to the target conversion mode, carrying out format conversion on the first request to obtain a second request, wherein the second request carries a target conversion identifier corresponding to the target conversion mode.
Optionally, the conversion module 901 is further specifically configured to:
extracting a request path and request parameters in the first request;
and taking the request path as a designated zone bit of a second request to be generated, taking the target conversion identifier as a header of the second request to be generated, taking the request parameter as a request body of the second request to be generated according to the target conversion mode, and compressing the request body to obtain the second request.
In summary, the client provided in the embodiments of the present invention may perform format conversion on the first request to obtain the second request, and send the second request to the server, where a data size of the second request is smaller than a data size of the first request, so that resources required to be consumed when the request is transmitted may be reduced by converting the first request into the second request with a smaller data size for transmission, and transmission efficiency is improved.
For the above device embodiment, since it is basically similar to the method embodiment, the description is simple, and for relevant points, reference may be made to the partial description of the method embodiment.
The embodiment of the present invention further provides an electronic device, as shown in fig. 10, which includes a processor 1001, a communication interface 1002, a memory 1003 and a communication bus 1004, wherein the processor 1001, the communication interface 1002 and the memory 1003 complete mutual communication through the communication bus 1004,
a memory 1003 for storing a computer program;
the processor 1001 is configured to implement the request transmission method in any of the embodiments when executing the program stored in the memory 1003.
The communication bus mentioned in the above terminal may be a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, or the like. The communication bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown, but this is not intended to represent only one bus or type of bus.
The communication interface is used for communication between the terminal and other equipment.
The Memory may include a Random Access Memory (RAM) or a non-volatile Memory (non-volatile Memory), such as at least one disk Memory. Optionally, the memory may also be at least one memory device located remotely from the processor.
The Processor may be a general-purpose Processor, and includes a Central Processing Unit (CPU), a Network Processor (NP), and the like; the Integrated Circuit may also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic device, or discrete hardware components.
In yet another embodiment of the present invention, a computer-readable storage medium is further provided, which has instructions stored therein, and when the instructions are executed on a computer, the instructions cause the computer to execute the request transmission method described in any of the above embodiments.
In yet another embodiment, the present invention further provides a computer program product containing instructions which, when run on a computer, cause the computer to perform the request transmission method described in any of the above embodiments.
In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the invention to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website site, computer, server, or data center to another website site, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that incorporates one or more of the available media. The usable medium may be a magnetic medium (e.g., floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.
It is noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
All the embodiments in the present specification are described in a related manner, and the same and similar parts among the embodiments may be referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the system embodiment, since it is substantially similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment.
The above description is only for the preferred embodiment of the present invention, and is not intended to limit the scope of the present invention. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention shall fall within the protection scope of the present invention.
Claims (14)
1. A request transmission method is applied to a system comprising a client and a server, wherein a gateway layer and a business layer are deployed in the server, and the method comprises the following steps:
the client selects a target conversion mode from preset optional conversion modes; extracting a request path and request parameters in the first request; taking the request path as a designated zone bit of a second request to be generated, taking a target conversion identifier corresponding to the target conversion mode as a head of the second request to be generated, taking the request parameter as a request body of the second request to be generated according to the target conversion mode, and compressing the request body to obtain the second request; the second request carries the target conversion identifier; defining a used compression mode in the target conversion mode;
the client sends the second request to the server, and the data size of the second request is smaller than that of the first request;
the gateway layer performs format reduction on the second request to obtain the first request;
the gateway layer sends the first request to the service layers, and the number of the service layers is larger than that of the gateway layers;
and the service layer executes corresponding processing operation according to the first request to obtain a processing result.
2. A request transmission method is applied to a client, and comprises the following steps:
selecting a target conversion mode from preset optional conversion modes;
extracting a request path and request parameters in the first request;
taking the request path as a designated zone bit of a second request to be generated, taking a target conversion identifier corresponding to the target conversion mode as a head of the second request to be generated, taking the request parameter as a request body of the second request to be generated according to the target conversion mode, and compressing the request body to obtain the second request; the second request carries the target conversion identifier; defining a used compression mode in the target conversion mode;
and sending the second request to a server, wherein the data size of the second request is smaller than that of the first request.
3. A request transmission method is applied to a server, wherein a gateway layer and a service layer are deployed in the server, and the method comprises the following steps:
the gateway layer receives a second request sent by a client, wherein the second request is that the client selects a target conversion mode from preset optional conversion modes; extracting a request path and request parameters in the first request; the request path is used as a designated zone bit of a second request to be generated, a target conversion identifier corresponding to the target conversion mode is used as a head of the second request to be generated, the request parameter is used as a request body of the second request to be generated according to the target conversion mode, and the request body is compressed; the second request carries the target conversion identifier; defining a used compression mode in the target conversion mode; the data size of the second request is smaller than the data size of the first request;
the gateway layer carries out format reduction on the second request to obtain the first request;
the gateway layer sends the first request to the service layers, and the number of the service layers is larger than that of the gateway layers;
and the service layer executes corresponding processing operation according to the first request to obtain a processing result.
4. The method of claim 3, wherein the gateway layer performs format recovery on the second request to obtain the first request, comprising:
extracting the target conversion identifier contained in the second request;
determining a target conversion mode according to the target conversion identifier;
and according to the target conversion mode, carrying out format reduction on the second request to obtain the first request.
5. The method of claim 4, wherein the performing format reduction on the second request according to the target conversion manner to obtain the first request comprises:
decompressing the content in the request body of the second request according to the reduction algorithm corresponding to the target conversion mode, and extracting the request parameter from the decompressed content;
and extracting a request path from the designated zone bit of the second request, and generating the first request according to the request parameter and the request path within the default request length supported by the server.
6. The method of claim 5, wherein before extracting a request path from the designated flag of the second request and generating the first request according to the request parameter and the request path within a default request length supported by the server, the method further comprises:
and setting the default request length as the maximum length supported by the server.
7. The method according to any one of claims 3 to 6, wherein the server is a server;
the gateway layer and the service layer are deployed in the same server; or,
the gateway layer and the service layer are deployed in different servers in the same local area network.
8. A request transmission system, the system comprising: the system comprises a client and a server, wherein a gateway layer and a service layer are deployed in the server;
the client is used for extracting a request path and request parameters in the first request; taking the request path as a designated zone bit of a second request to be generated, taking a target conversion identifier corresponding to a target conversion mode as a head of the second request to be generated, taking the request parameter as a request body of the second request to be generated according to the target conversion mode, and compressing the request body to obtain the second request; the second request carries the target conversion identifier; defining a used compression mode in the target conversion mode;
the client is further used for sending the second request to the server; the data size of the second request is smaller than the data size of the first request;
the gateway layer is used for carrying out format reduction on the second request to obtain the first request;
the gateway layer is further configured to send the first request to the service layer; the number of the service layers is greater than that of the gateway layers;
and the service layer is used for executing corresponding processing operation according to the first request to obtain a processing result.
9. A client, the client comprising:
the conversion module is used for selecting a target conversion mode from preset optional conversion modes; extracting a request path and request parameters in the first request; taking the request path as a designated zone bit of a second request to be generated, taking a target conversion identifier corresponding to the target conversion mode as a head of the second request to be generated, taking the request parameter as a request body of the second request to be generated according to the target conversion mode, and compressing the request body to obtain the second request, wherein the target conversion identifier is carried in the second request; defining a used compression mode in the target conversion mode;
the sending module is used for sending the second request to a server; wherein the data size of the second request is smaller than the data size of the first request.
10. A server, characterized in that the server comprises: a gateway layer and a service layer;
the gateway layer is used for receiving a second request sent by the client; the second request is that the client extracts a request path and request parameters in the first request; the request path is used as a designated zone bit of a second request to be generated, a target conversion identifier corresponding to a target conversion mode is used as a head of the second request to be generated, the request parameter is used as a request body of the second request to be generated according to the target conversion mode, and the request body is compressed; the second request carries the target conversion identifier; defining a used compression mode in the target conversion mode; the data size of the second request is smaller than the data size of the first request;
the gateway layer is further configured to perform format reduction on the second request to obtain the first request;
the gateway layer is further configured to send the first request to the service layer; wherein the number of the service layers is greater than the number of the gateway layers;
and the service layer is used for executing corresponding processing operation according to the first request to obtain a processing result.
11. The electronic equipment is characterized by comprising a processor, a communication interface, a memory and a communication bus, wherein the processor and the communication interface are used for realizing the communication between the processor and the memory through the communication bus;
a memory for storing a computer program;
a processor for implementing the method steps of claim 2 when executing a program stored in the memory.
12. An electronic device is characterized by comprising a processor, a communication interface, a memory and a communication bus, wherein the processor and the communication interface are used for realizing mutual communication by the memory through the communication bus;
a memory for storing a computer program;
a processor for implementing the method steps of any one of claims 3 to 7 when executing a program stored in the memory.
13. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the method of claim 2.
14. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the method according to any one of claims 3-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011232891.5A CN112565337B (en) | 2020-11-06 | 2020-11-06 | Request transmission method, server, client, system and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011232891.5A CN112565337B (en) | 2020-11-06 | 2020-11-06 | Request transmission method, server, client, system and electronic equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112565337A CN112565337A (en) | 2021-03-26 |
| CN112565337B true CN112565337B (en) | 2022-09-30 |
Family
ID=75041907
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011232891.5A Active CN112565337B (en) | 2020-11-06 | 2020-11-06 | Request transmission method, server, client, system and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112565337B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114285834A (en) * | 2021-12-24 | 2022-04-05 | 山石网科通信技术股份有限公司 | A message transmission method, device and terminal equipment |
| CN117724865B (en) * | 2023-12-13 | 2024-11-19 | 行吟信息科技(武汉)有限公司 | Service execution method, device, equipment and medium |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2008103565A1 (en) * | 2007-02-23 | 2008-08-28 | Microsoft Corporation | Dispatching client requests to appropriate server-side methods |
| CN107172012A (en) * | 2017-04-18 | 2017-09-15 | 北京思特奇信息技术股份有限公司 | A kind of message format conversion method and system |
| CN107645508A (en) * | 2017-10-16 | 2018-01-30 | 深圳市买买提乐购金融服务有限公司 | A kind of data handling system, method, client and server |
| CN110109766A (en) * | 2019-05-23 | 2019-08-09 | 贵阳块数据城市建设有限公司 | Data request method, device, system, data forwarding device and storage medium |
| CN110247926A (en) * | 2019-06-28 | 2019-09-17 | 北京奇艺世纪科技有限公司 | A kind of exchange method and system |
| CN111628956A (en) * | 2019-02-28 | 2020-09-04 | 阿里巴巴集团控股有限公司 | Format conversion method, device and system for network request transmission data |
Family Cites Families (18)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7412495B2 (en) * | 2002-04-26 | 2008-08-12 | Sun Microsystems, Inc. | Method, system, and article of manufacture for a server side application |
| ES2264853B1 (en) * | 2004-06-24 | 2007-12-16 | Vodafone España, S.A. | SYSTEM AND METHOD OF ASSETING IDENTITIES IN A TELECOMMUNICATIONS NETWORK. |
| US9432433B2 (en) * | 2006-06-09 | 2016-08-30 | Qualcomm Incorporated | Enhanced block-request streaming system using signaling or block creation |
| DE102007040405B3 (en) * | 2007-08-27 | 2009-03-05 | Fujitsu Siemens Computers Gmbh | Method and device for generating and / or using a generic web service |
| CN101383837A (en) * | 2007-09-07 | 2009-03-11 | 华为技术有限公司 | Extensible Markup Language Document Management Request Method and Management Method and Related Devices |
| JP2013232697A (en) * | 2012-04-27 | 2013-11-14 | Sony Corp | Content transfer device and content transfer method, content reproduction device and content reproduction method, content distribution system, and computer program |
| EP3016393A1 (en) * | 2014-10-30 | 2016-05-04 | Alcatel Lucent | Apparatuses, content distribution server, presentation device, methods and computer programs for providing information related to a service configuration for a service provided in a network |
| US10200499B1 (en) * | 2015-01-30 | 2019-02-05 | Symantec Corporation | Systems and methods for reducing network traffic by using delta transfers |
| CN107544991B (en) * | 2016-06-23 | 2020-10-23 | 滴滴（中国）科技有限公司 | Method and device for processing access request by server |
| CN107959548B (en) * | 2017-11-14 | 2020-09-01 | 北京思特奇信息技术股份有限公司 | Method and system for processing service request |
| CN108200165B (en) * | 2017-12-29 | 2019-07-02 | Oppo广东移动通信有限公司 | request transmission system, method, device and storage medium |
| CN109327511B (en) * | 2018-09-18 | 2021-05-28 | 网宿科技股份有限公司 | A data request method and server based on HTTP protocol |
| CN110225099B (en) * | 2019-05-20 | 2023-10-24 | 中国平安财产保险股份有限公司 | Data processing method, front-end client, back-end server and storage medium |
| CN110213290B (en) * | 2019-06-14 | 2022-05-20 | 华云数据控股集团有限公司 | Data acquisition method, API gateway and storage medium |
| CN111314434B (en) * | 2020-01-20 | 2022-08-19 | 浪潮云信息技术股份公司 | Request processing method and server |
| CN111314459B (en) * | 2020-02-13 | 2022-06-03 | 北京奇艺世纪科技有限公司 | Service request method, device, electronic equipment and storage medium |
| CN111614757A (en) * | 2020-05-20 | 2020-09-01 | 中国建设银行股份有限公司 | Message interaction method, device, equipment and medium for client and server |
| CN111600909B (en) * | 2020-06-24 | 2023-06-23 | 腾讯科技（深圳）有限公司 | Data processing method, device, protocol conversion equipment and storage medium |
-
2020
- 2020-11-06 CN CN202011232891.5A patent/CN112565337B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2008103565A1 (en) * | 2007-02-23 | 2008-08-28 | Microsoft Corporation | Dispatching client requests to appropriate server-side methods |
| CN107172012A (en) * | 2017-04-18 | 2017-09-15 | 北京思特奇信息技术股份有限公司 | A kind of message format conversion method and system |
| CN107645508A (en) * | 2017-10-16 | 2018-01-30 | 深圳市买买提乐购金融服务有限公司 | A kind of data handling system, method, client and server |
| CN111628956A (en) * | 2019-02-28 | 2020-09-04 | 阿里巴巴集团控股有限公司 | Format conversion method, device and system for network request transmission data |
| CN110109766A (en) * | 2019-05-23 | 2019-08-09 | 贵阳块数据城市建设有限公司 | Data request method, device, system, data forwarding device and storage medium |
| CN110247926A (en) * | 2019-06-28 | 2019-09-17 | 北京奇艺世纪科技有限公司 | A kind of exchange method and system |
Non-Patent Citations (2)
| Title |
|---|
| Xiangxu Yu ; Christos G. Bampis ; Praful Gupta ; Alan Conrad Bovik."Predicting the Quality of Images Compressed After Distortion in Two Steps".《 IEEE Transactions on Image Processing》.2019,全文. * |
| 徐计 ; 王国胤 ; 于洪."基于粒计算的大数据处理".《计算机学报》.2014,全文. * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112565337A (en) | 2021-03-26 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP2806602A1 (en) | Feature extraction device, network traffic identification method, device and system. | |
| CN108092956B (en) | Method and device for acquiring compression dictionary | |
| CN112565337B (en) | Request transmission method, server, client, system and electronic equipment | |
| KR20150016207A (en) | Service process control method and network device | |
| CN106936441A (en) | A kind of data compression method and device | |
| CN111436029B (en) | Method, system and related equipment for carrying out charging processing on network slice example | |
| US11991061B2 (en) | Processing local area network diagnostic data | |
| CN108093036B (en) | Method and device for acquiring resources | |
| CN104518968A (en) | Message processing method and transparent proxy server | |
| CN111314124A (en) | Network problem analysis method, device, equipment and storage medium for high-speed rail network | |
| CN113204683B (en) | Information reconstruction method and device, storage medium and electronic equipment | |
| CN108595574B (en) | Database cluster connection method, device, equipment and storage medium | |
| CN111885667B (en) | Network resource allocation method and system | |
| CN115826845A (en) | Method and device for allocating storage resources, storage medium, and electronic device | |
| KR101451956B1 (en) | Cloud service system, apparatus for providing cloud service and method using the same | |
| CN117807344A (en) | Method and device for constructing IP database | |
| JP7584204B2 (en) | Apparatus, method and program for data processing | |
| WO2022166591A1 (en) | Method and apparatus for playing live streaming resource, and storage medium and electronic device | |
| US20040107293A1 (en) | Program obtainment method and packet transmission apparatus | |
| CN116321078A (en) | Multimedia service sharing system, method, device, network element and medium | |
| KR102173015B1 (en) | Control plane apparatus, user plane apparatus and method for processing packet using the same | |
| CN115277837B (en) | Agent-based redirection method and device | |
| TWI838107B (en) | A network function virtualization orchestrator system, method and computer-readable medium thereof based on mobile network slicing function | |
| JP6298013B2 (en) | Policy control system and policy control method | |
| CN103051679A (en) | Data transmission method, interface equipment and cloud optimal control equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |