CN107295003B - Data transmission method, device and system - Google Patents

Data transmission method, device and system Download PDF

Info

Publication number
CN107295003B
CN107295003B CN201710582935.9A CN201710582935A CN107295003B CN 107295003 B CN107295003 B CN 107295003B CN 201710582935 A CN201710582935 A CN 201710582935A CN 107295003 B CN107295003 B CN 107295003B
Authority
CN
China
Prior art keywords
server
serialization
client
http
data
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
Application number
CN201710582935.9A
Other languages
Chinese (zh)
Other versions
CN107295003A (en
Inventor
殷舒
刘胜
陈正
余兴华
汤成山
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Union Mobile Pay Co Ltd
Original Assignee
Union Mobile Pay Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Union Mobile Pay Co Ltd filed Critical Union Mobile Pay Co Ltd
Priority to CN201710582935.9A priority Critical patent/CN107295003B/en
Publication of CN107295003A publication Critical patent/CN107295003A/en
Application granted granted Critical
Publication of CN107295003B publication Critical patent/CN107295003B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/24—Negotiation of communication capabilities
    • 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/01—Protocols
    • H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • 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/14—Session management
    • 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/01—Protocols

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Communication Control (AREA)
  • Computer And Data Communications (AREA)

Abstract

The invention provides a data transmission method, a device and a system, wherein the system comprises a client and a server; the client is used for: serializing the request data in a first serialization way to obtain serialized request data; generating a first hypertext transfer protocol (HTTP) request message, wherein the first HTTP request message carries the serialized request data and an identifier representing the first serialization mode; sending the first HTTP request message to a server; the server is used for: receiving the first HTTP request message sent by the client; obtaining the identifier from the first HTTP request message, and judging whether the server supports the first serialization mode represented by the identifier; and when the server side supports the first serialization mode, acquiring the request data from the first HTTP request message according to the first serialization mode.

Description

Data transmission method, device and system
Technical Field
The present invention relates to the field of communications technologies, and in particular, to a data transmission method, apparatus, and system.
Background
With the continuous development of internet technology, more and more message serialization modes can be supported by clients and servers, and different serialization modes supported by different clients and servers may be different. However, when the client and the server perform data interaction, the data must be encapsulated and analyzed in the same serialization manner.
In order to realize the unification of the serialization modes, the technical scheme adopted by the prior art is as follows: the client and the server perform one message interaction before initiating data interaction, negotiate a message serialization mode supported by both sides, and perform data interaction by using the negotiated serialization mode in the subsequent data interaction. However, the unification of the serialization mode through the message negotiation requires one more message interaction before the data interaction, which increases the network load and seriously affects the efficiency of the data interaction between the client and the server.
Disclosure of Invention
The invention provides a data transmission method, a data transmission device and a data transmission system, which are used for solving the technical problem of large network loading capacity caused by the fact that a client and a server need to negotiate a message serialization mode before data interaction in the prior art.
A first aspect of an embodiment of the present invention provides a data transmission system, including a client and a server;
the client is used for: serializing the request data in a first serialization way to obtain serialized request data; generating a first Hyper Text Transfer Protocol (HTTP) request message, wherein the first HTTP request message carries the serialized request data and an identifier representing the first serialization manner; sending the first HTTP request message to a server;
the server is used for: receiving the first HTTP request message sent by the client; obtaining the identifier from the first HTTP request message, and judging whether the server supports the first serialization mode represented by the identifier; and when the server side supports the first serialization mode, obtaining the request data from the first HTTP request message according to the first serialization mode.
In the scheme, the client and the server do not need to negotiate a message serialization mode before data interaction, but the client directly sends a request message carrying request data to the server; when the server receives the request message sent by the client, the serialization mode of the client can be determined by identifying the identifier carried by the request message, and the request message is subjected to deserialization processing when the server supports the serialization mode, so that the request data sent by the client is obtained. The technical problem of large network complex load caused by the fact that the client and the server need to negotiate the message serialization mode before data interaction is solved, and data interaction efficiency of the client and the server is improved. Moreover, the server in the scheme can support a serialization mode commonly used in the field, so that a plurality of message serialization modes do not need to be developed for the client to be connected with different servers, and the development cost of the server is saved.
Optionally, the server is further configured to: after the request data are obtained, processing the request data to obtain response data; serializing the response data in the first serialization way to obtain serialized response data; generating a first HTTP response message, wherein the first HTTP response message carries the serialized response data; sending the first HTTP response message to the client; the client is further configured to: receiving the first HTTP response message sent by the server; and obtaining the response data from the first HTTP response message according to the first serialization mode. By the method, the server can adopt the serialization mode to respond to the client when supporting the serialization mode that the client serializes the request data, and the scheme of data transmission between the client and the server is further improved.
Optionally, the identifier representing the first serialization manner is located in a request line of the first HTTP request packet, or located in a request header of the first HTTP request packet, or located in a request body of the first HTTP request packet. By the method, the client and the server can carry a serialization mode of carrying out serialization processing on data by the client in a message carrying communication data, a negotiation process of the serialization mode is not needed before data interaction, and a scheme for carrying out data transmission between the client and the server is perfected.
Optionally, the identifier representing the first serialization manner is located in a Uniform Resource Locator (URL) in a request line of the first HTTP request packet in a form of a suffix or in a form of a path parameter. By the method, the size of the message can be reduced, the network load is further reduced, and the efficiency of data transmission between the client and the server is improved.
Optionally, the server is further configured to: when the server side does not support the first serialization way, the server side determines at least one serialization way supported by the server side; generating a second HTTP response message, wherein the second HTTP response message carries an identifier representing at least one serialization mode supported by the server; sending the second HTTP response message to the client; the client is further configured to: receiving the second HTTP response message sent by the server, and acquiring the at least one serialization mode supported by the server from the second HTTP response message; determining a serialization mode commonly supported by the client and the server; serializing the request data in a second serialization way to obtain serialized request data, wherein the second serialization way is any one of serialization ways supported by the client and the server together; generating a second HTTP request message, wherein the second HTTP request message carries the serialized request data and an identifier representing the second serialization way; and sending the second HTTP request message to the server. In this mode, if the server does not support the first serialization mode, the server can feed back the serialization modes supported by the server to the client, and the client selects the serialization mode supported by both the client and the server from the serialization modes fed back by the server to initiate data interaction again.
A second aspect of the embodiments of the present invention provides a data transmission method, which is applied to a client, and the method includes: the client carries out serialization processing on the request data in a first serialization mode to obtain serialized request data; the client generates a first HTTP request message, wherein the first HTTP request message carries the serialized request data and an identifier representing the first serialization mode; and the client sends the first HTTP request message to a server.
Optionally, the identifier representing the first serialization manner is located in a request line of the first HTTP request packet, or located in a request header of the first HTTP request packet, or located in a request body of the first HTTP request packet.
Optionally, the identifier representing the first serialization manner is located in a URL in a request line of the first HTTP request packet in a form of a suffix or in a form of a path parameter.
Optionally, after the client sends the first HTTP request packet to the server, the method further includes: the client receives a response message returned by the server, and determines that the response message carries serialized response data according to a state code in a state line of the response message; and the client acquires response data from the response message according to the first serialization mode.
Optionally, after the client sends the first HTTP request packet to the server, the method further includes: the client receives a response message sent by the server, and determines that the response message carries an identifier representing at least one serialization mode supported by the server according to a state code in a state line of the response message; the client acquires at least one serialization mode supported by the server from the response message; the client determines a serialization mode commonly supported by the client and the server; the client carries out serialization processing on the request data in a second serialization way to obtain serialized request data, wherein the second serialization way is any one of serialization ways supported by the client and the server together; the client generates a second HTTP request message, wherein the second HTTP request message carries the serialized request data and an identifier representing the second serialization mode; and the client sends the second HTTP request message to the server.
A third aspect of the embodiments of the present invention provides a data transmission method, which is applied to a server, and the method includes: the server receives a first HTTP request message sent by a client, wherein the first HTTP request message carries serialized request data and an identifier representing a first serialization way for the client to perform serialization processing on the request data; the server side obtains the identifier from the first HTTP request message, and judges whether the server side supports the first serialization mode represented by the identifier; and if the server side supports the first serialization mode, the server side obtains the request data from the first HTTP request message according to the first serialization mode.
Optionally, the identifier representing the first serialization manner is located in a request line of the first HTTP request packet, or located in a request header of the first HTTP request packet, or located in a request body of the first HTTP request packet.
Optionally, the identifier representing the first serialization manner is located in a URL in a request line of the first HTTP request packet in a form of a suffix or in a form of a path parameter.
Optionally, after the server obtains the request data, the method further includes: the server processes the request data to obtain response data; the server carries out serialization processing on the response data in the first serialization mode to obtain serialized response data; the server generates a first HTTP response message, wherein the first HTTP response message carries the serialized response data; and the server side sends the first HTTP response message to the client side.
Optionally, after the server determines whether the server supports the first serialization manner, the method further includes: if the server side does not support the first serialization way, the server side determines at least one serialization way supported by the server side; the server generates a second HTTP response message, wherein the second HTTP response message carries an identifier representing at least one serialization mode supported by the server; and the server side sends the second HTTP response message to the client side.
A fourth aspect of the present invention provides a data transmission device, including: a processing unit to: serializing the request data in a first serialization way to obtain serialized request data; generating a first HTTP request message, wherein the first HTTP request message carries the serialized request data and an identifier representing the first serialization mode; a transmitting unit configured to: and sending the first HTTP request message to a server.
Optionally, the apparatus further comprises: a receiving unit configured to: after the sending unit sends the first HTTP request message to the server, receiving a response message returned by the server; the processing unit is further to: determining that the response message carries serialized response data according to a state code in a state line of the response message; and acquiring response data from the response message according to the first serialization mode.
Optionally, the apparatus further comprises: a receiving unit configured to: after the sending unit sends the first HTTP request message to the server, receiving a response message sent by the server; the processing unit is further to: determining that the response message carries an identifier representing at least one serialization mode supported by the server according to a state code in a state line of the response message; acquiring at least one serialization mode supported by the server from the response message; determining a serialization mode commonly supported by the device and the server; serializing the request data in a second serialization way to obtain serialized request data, wherein the second serialization way is any one of serialization ways supported by the device and the server side; generating a second HTTP request message, wherein the second HTTP request message carries the serialized request data and an identifier representing the second serialization way; the sending unit is further configured to: and sending the second HTTP request message to the server.
Optionally, the identifier representing the first serialization manner is located in a request line of the first HTTP request packet, or located in a request header of the first HTTP request packet, or located in a request body of the first HTTP request packet.
Optionally, the identifier representing the first serialization manner is located in a URL in a request line of the first HTTP request packet in a form of a suffix or in a form of a path parameter.
A fifth aspect of the embodiments of the present invention provides a data transmission device, including: a receiving unit configured to: receiving a first HTTP request message sent by a client, wherein the first HTTP request message carries serialized request data and an identifier representing a first serialization way for the client to perform serialization processing on the request data; a processing unit to: obtaining the identifier from the first HTTP request message, and judging whether the device supports the first serialization mode represented by the identifier; and when the device supports the first serialization mode, acquiring the request data from the first HTTP request message according to the first serialization mode.
Optionally, the processing unit is further configured to: processing the request data to obtain response data; serializing the response data in the first serialization way to obtain serialized response data; generating a first HTTP response message, wherein the first HTTP response message carries the serialized response data; the apparatus further comprises a transmitting unit configured to: and sending the first HTTP response message to the client.
Optionally, the processing unit is further configured to: when the device does not support the first serialization way, determining at least one serialization way supported by the device; generating a second HTTP response message, wherein the second HTTP response message carries an identifier representing at least one serialization mode supported by the device; the apparatus further comprises a transmitting unit configured to: and sending the second HTTP response message to the client.
Optionally, the identifier representing the first serialization manner is located in a request line of the first HTTP request packet, or located in a request header of the first HTTP request packet, or located in a request body of the first HTTP request packet.
Optionally, the identifier representing the first serialization manner is located in a URL in a request line of the first HTTP request packet in a form of a suffix or in a form of a path parameter.
A sixth aspect of the present invention provides a client, including: the system comprises at least one processor, a memory and a communication interface, wherein the memory and the communication interface are in communication connection with the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the at least one processor executes the data transmission method provided by the second aspect of the embodiment of the present invention by executing the instructions stored in the memory using the communication interface.
A seventh aspect of the embodiments of the present invention provides a server, including: the system comprises at least one processor, a memory and a communication interface, wherein the memory and the communication interface are in communication connection with the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the at least one processor executes the instructions stored by the memory to perform the method for data transmission provided by the third aspect of the embodiment of the present invention by using the communication interface.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without inventive exercise.
FIG. 1 is a flowchart illustrating a method for a client and a server to negotiate a serialization method in the prior art;
fig. 2 is a schematic diagram of a data transmission system according to an embodiment of the present invention;
fig. 3 is a flowchart of a data transmission method according to an embodiment of the present invention;
fig. 4 is a flowchart of a data transmission method according to an embodiment of the present invention;
fig. 5 is a schematic structural diagram of a data transmission apparatus according to an embodiment of the present invention;
fig. 6 is a schematic structural diagram of a data transmission apparatus according to an embodiment of the present invention;
fig. 7 is a schematic structural diagram of a client according to an embodiment of the present invention;
fig. 8 is a schematic structural diagram of a server according to an embodiment of the present invention.
Detailed Description
The technical solutions of the present invention are described in detail below with reference to the drawings and the specific embodiments, and it should be understood that the specific features in the embodiments and the embodiments of the present invention are not intended to limit the technical solutions of the present invention, but may be combined with each other without conflict.
It is to be understood that the terms first, second, and the like in the description of the embodiments of the invention are used for distinguishing between the descriptions and not necessarily for describing a sequential or chronological order. "plurality" in the description of the embodiments of the present invention means two or more.
The term "and/or" in the embodiment of the present invention is only one kind of association relationship describing an associated object, and indicates that three relationships may exist, for example, a and/or B may indicate: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" herein generally indicates that the former and latter related objects are in an "or" relationship.
At present, a plurality of message serialization modes which can be supported by a client and a server are available, the serialization modes supported by different clients and servers may be different, but the client and the server need to package and analyze data in the same serialization mode to successfully complete data interaction. In order to implement the unification of the serialization modes, the technical solutions adopted in the prior art are generally: after a client establishes a Transmission Control Protocol (TCP) connection with a server and before the client initiates data interaction with a server, a message interaction is performed first to negotiate a message serialization mode supported by both parties, and data interaction is performed using the negotiated serialization mode in subsequent data interaction.
Fig. 1 is a specific implementation process of a negotiation serialization manner in the prior art, which specifically includes:
step 101, after the client and the server establish a TCP connection, the client sends an HTTP request to the server, and an Accept field in a request header carries a serialization mode list supported by the client.
Step 102, after receiving the HTTP request, the server reads an Accept field to obtain a serialization mode list supported by the client;
and 103, comparing the serialization modes supported by the client and the serialization modes supported by the server, and selecting one or more serialization modes supported by both sides.
And step 104, the server returns an HTTP response to the client, and the Accept field in the response header carries the selected serialization mode.
And 105, the client acquires the negotiated serialization mode after receiving the response sent back by the server, and adopts one of the negotiated serialization modes in the subsequent data exchange process with the server.
In the method for implementing serialization unification through negotiation, the server and the client must perform a message interaction before formal data interaction, that is, execute the above steps 101 to 105. The method greatly increases the load of the network, and particularly seriously influences the efficiency of data interaction between the client and the server under the multi-user high concurrent access scene.
Example one
The embodiment of the invention provides a data transmission method, which is used for solving the technical problem that in the prior art, a client and a server need to negotiate a message serialization mode before data interaction, so that the network loading capacity is large.
Before introducing the data transmission method, a data transmission system for implementing the data transmission method is introduced, wherein the system can comprise a plurality of service terminals and a plurality of client terminals, and any one client terminal and any one service terminal can be connected and communicated through a network. For example, referring to fig. 2, the system includes a client 21, a client 22, a client 23, a server 24, a server 25, and a server 26, where the client 21, the client 22, the client 23, the server 24, the server 25, and the server 26 can implement interconnection and communication through a network, where the server 24, the server 25, and the server 26 can all support a serialization manner commonly used in the art, and the serialization manner supported by the server includes, but is not limited to, the following: JS Object Markup (JSON), Extensible Markup Language (XML), Remote Procedure Call Protocol (RPC), Hessian (Hessian), burlp, Action Message Format, and the like.
The data transmission method provided by the embodiment of the invention can be suitable for data interaction between any server and any client in the system, and before the data transmission method provided by the embodiment of the invention is executed, TCP connection is established between the client and the server which carry out the data interaction. Next, the data transmission method provided by the embodiment of the present invention will be described in detail by taking an example of data interaction between the client 21 and the server 24.
Referring to fig. 3, a method for providing data transmission according to an embodiment of the present invention includes:
in step 301, the client 21 performs serialization processing on the request data in a first serialization manner to obtain serialized request data.
Specifically, the client 21 supports at least one serialization manner, and the serialization manners supported by the client 21 include, but are not limited to, the following: JSON, XML, RPC, Hessian, Burlap, and Action Message Format, and the first serialization mode may be any one of serialization modes supported by the client 21.
Step 302, the client 21 generates a first HTTP request packet, where the first HTTP request packet carries the serialized request data and the identifier representing the first serialization manner.
Specifically, the client 21 may encapsulate the serialized request data in the text of the first HTTP request packet, and bear an identifier representing a first serialization manner in which the client 21 serializes the request data on a preset field of the first HTTP request packet.
The preset field may be located in a request line of the first HTTP request packet, may also be located in a request header of the first HTTP request packet, and may also be located in a request body of the first HTTP request packet, which is not specifically limited in this embodiment of the present invention. For example, an "Accept-Encoding" field in the request header of the first HTTP request packet may be designated as the preset field.
Step 303, the client 21 sends the first HTTP request message to the server 24.
Step 304, the server 24 receives the first HTTP request packet sent by the client 21, and determines whether the server 24 supports the first serialization manner represented by the identifier.
Specifically, after receiving a first HTTP request message sent by the client 21, the server 24 obtains the identifier from the preset field in the first HTTP request message, and then learns a serialization manner, i.e., a first serialization manner, when the client 21 generates the first HTTP request message; and then matching the first serialization manner with the serialization manner supported by the server 24.
If the server 24 supports the first serialization manner, step 305 is executed:
step 305, the server 24 obtains the request data from the first HTTP request message according to the first serialization manner.
Specifically, after the server 24 determines that the server 24 supports the first serialization method, the server 24 performs deserialization processing on the first HTTP request packet by using a deserialization method corresponding to the first serialization method, so as to obtain the request data.
In the above scheme, the client 21 and the server 24 may not need to negotiate a message serialization manner before data interaction, but the client 21 directly sends a request message carrying request data to the server 24, and adds an identifier representing the serialization manner in which the client 21 serializes the request data into a preset field of the request message; when the server 24 receives the request message sent by the client 21, the serialization mode of the client 21 can be determined by identifying the identifier on the preset field of the request message, and the request message is deserialized when the server 24 supports the serialization mode, so that the request data sent by the client 21 is obtained. Because the server 24 in the present solution can support a serialization manner commonly used in the field, for most request messages sent by the client 21, the server 24 can perform deserialization processing to obtain request data, that is, for most data interactions, a negotiation process of a message serialization manner before interaction may not be performed, so that the technical problem of a large network loading amount due to the fact that the client 21 and the server 24 need to negotiate the message serialization manner before data interaction is solved, and the data interaction efficiency of the client 21 and the server 24 is improved.
Moreover, because the server 24 in the present solution can support a serialization manner commonly used in the field, it is not necessary to develop a plurality of message serialization manners for the client 21 to interface with different servers 24, thereby saving the development cost of the server 24.
Optionally, referring to fig. 3, after step 305, the method further includes:
step 306: the server 24 generates a first HTTP response packet according to the request data and the first serialization manner.
Specifically, the server 24 processes the request data to obtain response data; the server 24 serializes the response data in the first serialization manner to obtain serialized response data; the client 21 encapsulates the serialized response data in the text of the first HTTP response packet, and carries a status code representing that the server 24 has successfully responded to the request of the client 21 in a status line of the first HTTP response packet, so that the client 21 can know that the data request is successful when receiving the first HTTP response packet.
Step 307: the server 24 sends the first HTTP response message to the client 21.
Step 308: the client 21 receives the first HTTP response packet sent by the server 24, and obtains the response data from the first HTTP response packet according to the first serialization manner.
Specifically, after receiving the first HTTP response packet and sending the first HTTP response packet to the client 21, the client 21 learns that the server 24 has successfully responded to the request of the client 21 through the status code in the status line of the first HTTP response packet, and then performs deserialization processing on the first HTTP response packet by using the deserialization method corresponding to the first serialization method to obtain the response data.
Of course, in the specific implementation process, a case of data request failure due to other reasons except for the reason that the server 24 does not support the serialization manner in which the client 21 serializes the request data may also occur, for example, the server 24 cannot find the resource requested by the client 21 and thus the server 24 cannot return the corresponding response data, in this case, the server may still return the response message, but the message does not carry the response data corresponding to the request data, and the response message may be used to notify the user of the data request failure, the specific reason of the data request failure, and the like. Since this part is well known to those skilled in the art, the embodiments of the present invention will not be described in detail.
By the method, when the server 24 supports a serialization mode in which the client 21 serializes the request data, the client 21 can respond by the serialization mode, and a scheme for data transmission between the client 21 and the server 24 is further improved.
Optionally, the identifier representing the first serialization manner is located in a Uniform Resource Locator (URL) in a request line of the first HTTP request packet. Wherein the form of the identification in the URL includes, but is not limited to, the following two:
in item 1, the identifier is located in a URL in a request line of the first HTTP request message in the form of a suffix.
For example, the first serialization manner is XML, and the request line of the first HTTP request packet may be: POST/HTTP:// www.xxx.com/arg1/arg2.xml HTTP/1.1 (CRLF). Wherein, HTTP:// www.xxx.com/arg1/arg2 is URL, ". xml" is the mark for representing the first serialization mode, "POST" is the request method, and "HTTP/1.1" is the protocol and protocol version used by the request.
Certainly, in a specific implementation process, the request method, the URL, the protocol used by the request, and the protocol version carried in the first HTTP request packet may also have other possible values, and the foregoing example is only used to illustrate that the identifier is located in the URL in a suffix form, and cannot be used to limit the request method, the URL, the protocol used by the request, and the protocol version.
In the second type, the identifier is located in a URL in a request line of the first HTTP request message in the form of a path parameter.
For example, the first serialization manner is XML, and the request line of the first HTTP request packet may be: POST/HTTP:// www.xxx.com/arg1/arg2/xml/HTTP/1.1 (CRLF). Wherein, HTTP:// www.xxx.com/arg1/arg2 is URL, "/xml/" is the mark for representing the first serialization mode, "POST" is the request method, and "HTTP/1.1" is the protocol and protocol version used by the request.
Certainly, in a specific implementation process, the request method, the URL, the protocol used by the request, and the protocol version carried in the first HTTP request packet may also have other possible values, and the foregoing example is only used to illustrate that the identifier is located in the URL in the form of a path parameter, and cannot be used to limit the request method, the URL, the protocol used by the request, and the protocol version.
In the prior art, the serialization identifiers carried in the message are all on the 'Accept-Encoding' field of the message header, and at least 20 bytes are needed (for example, 'Accept-Encoding: XXX \ n'), and the method saves at least 15 bytes compared with the prior art by carrying the serialization identifiers on the URL. Therefore, the size of the message can be reduced by the method, the network load is further reduced, and the efficiency of data interaction between the client 21 and the server 24 is improved.
Of course, in the specific implementation process of the embodiment of the present invention, in a rare case, a case that the server 24 does not support the first serialization manner may occur, and a solution of the embodiment of the present invention when the server 24 does not support the first serialization manner is described next.
Optionally, after determining whether the server 24 supports the first serialization way characterized by the identifier in step 304, if the server 24 does not support the first serialization way, the server 24 may feed back the supported serialization ways to the client 21, so that the client 21 selects the serialization way supported by both the client 21 and the server 24 from the serialization ways fed back by the server 24 to initiate data interaction again. Referring to fig. 4, the method specifically implements a process including steps 309 to 321:
step 309: the server 24 determines at least one serialization manner supported by the server 24.
In a specific implementation process, the at least one serialization manner that the server 24 obtains and is supported by the server 24 may be all serialization manners supported by the server 24, or may be a partial serialization manner in all serialization manners supported by the server 24, which is not specifically limited in this embodiment of the present invention.
Step 310: the server 24 generates a second HTTP response packet, where the second HTTP response packet carries an identifier representing the at least one serialization manner.
Specifically, the server 24 encapsulates the identifier representing the at least one serialization manner in the second HTTP response packet, where the identifier of the at least one serialization manner may be located in a state line of the second HTTP response packet or in a response header of the second HTTP response packet, which is not limited in this embodiment of the present invention. The status line of the second HTTP response packet also carries a status code indicating that the server 24 has failed to successfully respond to the request of the client 21, so that when the client 21 receives the second HTTP response packet, it can be known according to the status code that the server 24 does not support the first serialization method, which results in that the server 24 fails to successfully respond to the request of the client 21, and the second HTTP response packet carries an identifier indicating at least one serialization method supported by the server 24.
Step 311: the server 24 sends the second HTTP response message to the client 21.
Step 312: the client 21 receives the second HTTP response packet sent by the server 24, and learns the at least one serialization manner supported by the server 24 from the second HTTP response packet.
Specifically, after receiving the second HTTP response packet and sending the second HTTP response packet to the client 21, the client 21 learns that the server 24 cannot successfully respond to the request of the client 21 through the status code in the status line of the second HTTP response packet, and obtains an identifier representing at least one serialization manner supported by the server 24 from the second HTTP response packet, so as to learn the at least one serialization manner supported by the server 24.
Step 313: the client 21 matches the at least one serialization way with the serialization ways supported by the client 21, and determines the serialization ways supported by both the client 21 and the server 24.
In a specific implementation process, if the client 21 can support multiple serialization manners, and there is a serialization manner that is the same as the serialization manner of the service feedback in other serialization manners supported by the client 21 except for the first serialization manner, the client 21 determines the same serialization manner as a serialization manner supported by both the client 21 and the server 24; if the client 21 only supports the first serialization manner, or the client 21 supports multiple serialization manners but there is no serialization manner that is the same as the serialization manner of the service feedback in other serialization manners supported by the client 21 except the first serialization manner, the client 21 informs the user to select at least one serialization manner from the serialization manners of the service feedback to develop the client 21, so that the client 21 has the serialization manner that is commonly supported by the server 24, and determines the selected at least one serialization manner as the serialization manner that is commonly supported by the client 21 and the server 24.
Step 314: the client 21 performs serialization processing on the request data in a second serialization manner to obtain serialized request data, where the second serialization manner is any one of serialization manners commonly supported by the client 21 and the server 24.
Step 315: the client 21 generates a second HTTP request packet, where the second HTTP request packet carries the serialized request data and an identifier representing the second serialization manner.
Step 316: the client 21 sends the second HTTP request message to the server 24.
Step 317: the server 24 receives the second HTTP request packet sent by the client 21, acquires the identifier representing the second serialization manner from the second HTTP request packet, and determines whether the server 24 supports the second serialization manner represented by the identifier, if the server 24 supports the second serialization manner, step 318 is executed:
step 318: the server 24 obtains the request data from the second HTTP request message according to the second serialization manner.
In a specific implementation process, in the step 317, after receiving the second HTTP request packet sent by the client 21, the server 24 may directly execute the step 318 without executing the step of determining whether the server 24 supports the second serialization manner represented by the identifier. Whether the server 24 executes the step of determining whether the server 24 supports the second serialization manner characterized by the identifier may be selected according to actual needs, and embodiments of the present invention are not limited specifically.
Step 319: and the server 24 generates a third HTTP response packet according to the request data and the second serialization manner.
Step 320: the server 24 sends the third HTTP response packet to the client 21.
Step 321: the client 21 receives the third HTTP response packet sent by the server 24, and obtains the response data from the third HTTP response packet according to the second serialization manner.
The specific implementation manner of the steps 314 to 321 can refer to the steps 301 to 308, and the embodiment of the present invention is not described again.
In this embodiment, after the server 24 receives the request message from the client 21, if the server 24 does not support the serialization method of the request message sent by the client 21, the server 24 returns at least one serialization method supported by the server 24 to the client 21, and then the client 21 selects the serialization method supported by both the client 21 and the server 24 from the at least one serialization method supported by the server 24 to initiate data interaction again. By the method, the network load can be reduced, the success rate of data interaction can be guaranteed, and the scheme for data transmission between the client 21 and the server 24 is further improved.
Example two
An embodiment of the present invention provides a data transmission method, which is applied to a client performing data transmission in the first embodiment, where the method includes:
the client carries out serialization processing on the request data in a first serialization mode to obtain serialized request data;
the client generates a first HTTP request message, wherein the first HTTP request message carries the serialized request data and an identifier representing the first serialization mode;
and the client sends the first HTTP request message to a server.
Optionally, the identifier representing the first serialization manner is located in a request line of the first HTTP request packet, or located in a request header of the first HTTP request packet, or located in a request body of the first HTTP request packet.
Optionally, the identifier representing the first serialization manner is located in a URL in a request line of the first HTTP request packet in a form of a suffix or in a form of a path parameter.
Optionally, after the client sends the first HTTP request packet to the server, the method further includes:
the client receives a response message returned by the server, and determines that the response message carries serialized response data according to a state code in a state line of the response message;
and the client acquires response data from the response message according to the first serialization mode.
Optionally, after the client sends the first HTTP request packet to the server, the method further includes:
the client receives a response message sent by the server, and determines that the response message carries an identifier representing at least one serialization mode supported by the server according to a state code in a state line of the response message;
the client acquires at least one serialization mode supported by the server from the response message; the client determines a serialization mode commonly supported by the client and the server;
the client carries out serialization processing on the request data in a second serialization way to obtain serialized request data, wherein the second serialization way is any one of serialization ways supported by the client and the server together;
the client generates a second HTTP request message, wherein the second HTTP request message carries the serialized request data and an identifier representing the second serialization mode;
and the client sends the second HTTP request message to the server.
EXAMPLE III
A third embodiment of the present invention provides a data transmission method, which is applied to a server that performs data transmission in the first embodiment, and the method includes:
the server receives a first HTTP request message sent by a client, wherein the first HTTP request message carries serialized request data and an identifier representing a first serialization way for the client to perform serialization processing on the request data;
the server side obtains the identifier from the first HTTP request message, and judges whether the server side supports the first serialization mode represented by the identifier;
and if the server side supports the first serialization mode, the server side obtains the request data from the first HTTP request message according to the first serialization mode.
Optionally, the identifier representing the first serialization manner is located in a request line of the first HTTP request packet, or located in a request header of the first HTTP request packet, or located in a request body of the first HTTP request packet.
Optionally, the identifier representing the first serialization manner is located in a URL in a request line of the first HTTP request packet in a form of a suffix or in a form of a path parameter.
Optionally, after the server obtains the request data, the method further includes:
the server processes the request data to obtain response data; the server carries out serialization processing on the response data in the first serialization mode to obtain serialized response data;
the server generates a first HTTP response message, wherein the first HTTP response message carries the serialized response data;
and the server side sends the first HTTP response message to the client side.
Optionally, after the server determines whether the server supports the first serialization manner, the method further includes:
if the server side does not support the first serialization way, the server side determines at least one serialization way supported by the server side;
the server generates a second HTTP response message, wherein the second HTTP response message carries an identifier representing at least one serialization mode supported by the server;
and the server side sends the second HTTP response message to the client side.
Example four
A fourth embodiment of the present invention provides a data transmission device, which is configured to implement the data transmission method provided in the second embodiment. Referring to fig. 5, the data transmission apparatus includes:
a processing unit 401 configured to: serializing the request data in a first serialization way to obtain serialized request data; generating a first HTTP request message, wherein the first HTTP request message carries the serialized request data and an identifier representing the first serialization mode;
a sending unit 402, configured to: and sending the first HTTP request message to a server.
Optionally, the apparatus further comprises:
a receiving unit 403, configured to: after the sending unit 402 sends the first HTTP request packet to the server, receiving a response packet returned by the server;
the processing unit 401 is further configured to: determining that the response message carries serialized response data according to a state code in a state line of the response message; and acquiring response data from the response message according to the first serialization mode.
Optionally, the apparatus further comprises:
a receiving unit 403, configured to: after the sending unit 402 sends the first HTTP request packet to the server, receiving a response packet sent by the server;
the processing unit 401 is further configured to: determining that the response message carries an identifier representing at least one serialization mode supported by the server according to a state code in a state line of the response message; acquiring at least one serialization mode supported by the server from the response message; determining a serialization mode commonly supported by the device and the server; serializing the request data in a second serialization way to obtain serialized request data, wherein the second serialization way is any one of serialization ways supported by the device and the server side; generating a second HTTP request message, wherein the second HTTP request message carries the serialized request data and an identifier representing the second serialization way;
the sending unit 402 is further configured to: and sending the second HTTP request message to the server.
Optionally, the identifier representing the first serialization manner is located in a request line of the first HTTP request packet, or located in a request header of the first HTTP request packet, or located in a request body of the first HTTP request packet.
Optionally, the identifier representing the first serialization manner is located in a URL in a request line of the first HTTP request packet in a form of a suffix or in a form of a path parameter.
The specific implementation manner of the operation performed by each unit may refer to the specific implementation manner of each corresponding step performed by the client in the second embodiment, and details of the embodiment of the present invention are not described again.
EXAMPLE five
A fifth embodiment of the present invention provides a data transmission device, configured to implement the data transmission method provided in the third embodiment. Referring to fig. 6, the data transmission apparatus includes:
a receiving unit 501, configured to: receiving a first HTTP request message sent by a client, wherein the first HTTP request message carries serialized request data and an identifier representing a first serialization way for the client to perform serialization processing on the request data;
a processing unit 502 for: obtaining the identifier from the first HTTP request message, and judging whether the device supports the first serialization mode represented by the identifier; and when the device supports the first serialization mode, acquiring the request data from the first HTTP request message according to the first serialization mode.
Optionally, the processing unit 502 is further configured to: processing the request data to obtain response data; serializing the response data in the first serialization way to obtain serialized response data; generating a first HTTP response message, wherein the first HTTP response message carries the serialized response data;
the apparatus further comprises a sending unit 503 configured to: and sending the first HTTP response message to the client.
Optionally, the processing unit 502 is further configured to: when the device does not support the first serialization way, determining at least one serialization way supported by the device; generating a second HTTP response message, wherein the second HTTP response message carries an identifier representing at least one serialization mode supported by the device;
the apparatus further comprises a sending unit 503 configured to: and sending the second HTTP response message to the client.
Optionally, the identifier representing the first serialization manner is located in a request line of the first HTTP request packet, or located in a request header of the first HTTP request packet, or located in a request body of the first HTTP request packet.
Optionally, the identifier representing the first serialization manner is located in a URL in a request line of the first HTTP request packet in a form of a suffix or in a form of a path parameter.
The specific implementation manner of the operation performed by each unit may refer to the specific implementation manner of each corresponding step performed by the server in the third embodiment, and details of the embodiment of the present invention are not described again.
EXAMPLE six
An embodiment of the present invention provides a client, and referring to fig. 7, the client includes:
at least one processor 601; and the number of the first and second groups,
a memory 602, a communication interface 603 communicatively coupled to the at least one processor; wherein the content of the first and second substances,
the memory 602 stores instructions executable by the at least one processor 601, and the at least one processor 601 executes the instructions stored in the memory 602 to perform the data transmission method provided by the second embodiment using the communication interface 603.
EXAMPLE seven
The seventh embodiment of the present invention provides a server, and with reference to fig. 8, the server includes:
at least one processor 701; and the number of the first and second groups,
a memory 702, a communication interface 703 communicatively coupled to the at least one processor; wherein the content of the first and second substances,
the memory 702 stores instructions executable by the at least one processor 701, and the at least one processor 701 executes the method for transmitting data provided by the third embodiment of the present invention by using the communication interface 703 through executing the instructions stored in the memory 702.
One or more technical solutions provided in the embodiments of the present invention have at least the following technical effects or advantages:
1. for most request messages sent by the client, the server can perform deserialization processing to obtain request data, so that the negotiation process of a message serialization mode before interaction is not needed for most data interaction, the technical problem of large network complex load caused by the fact that the message serialization mode needs to be negotiated before the data interaction between the client and the server is solved, and the data interaction efficiency between the client and the server is improved.
2. For request messages sent by a few clients, if the server side does not support the serialization mode of the request messages sent by the client side, the server side returns at least one serialization mode supported by the server side to the client side, and then the client side selects the serialization mode supported by the client side and the server side together from the at least one serialization mode supported by the server side to initiate data interaction again.
3. Because the server in the embodiment of the invention can support the serialization mode commonly used in the field, the embodiment of the invention can be used for connecting different servers without developing various message serialization modes aiming at the client, thereby saving the development cost of the server.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
It will be apparent to those skilled in the art that various changes and modifications may be made in the present invention without departing from the spirit and scope of the invention. Thus, if such modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to include such modifications and variations.

Claims (12)

1. A data transmission system is characterized by comprising a client and a server;
the client is used for: serializing the request data in a first serialization way to obtain serialized request data; generating a first hypertext transfer protocol (HTTP) request message, wherein the first HTTP request message carries the serialized request data and an identifier representing the first serialization mode; sending the first HTTP request message to a server;
the server is used for: receiving the first HTTP request message sent by the client; obtaining the identifier from the first HTTP request message, and judging whether the server supports the first serialization mode represented by the identifier; when the server side supports the first serialization mode, the request data are obtained from the first HTTP request message according to the first serialization mode;
wherein the server is further configured to: when the server side does not support the first serialization way, the server side determines at least one serialization way supported by the server side; generating a second HTTP response message, wherein the second HTTP response message carries an identifier representing at least one serialization mode supported by the server; sending the second HTTP response message to the client;
the client is further configured to: receiving the second HTTP response message sent by the server, and acquiring the at least one serialization mode supported by the server from the second HTTP response message; determining a serialization mode commonly supported by the client and the server; serializing the request data in a second serialization way to obtain serialized request data, wherein the second serialization way is any one of serialization ways supported by the client and the server together; generating a second HTTP request message, wherein the second HTTP request message carries the serialized request data and an identifier representing the second serialization way; and sending the second HTTP request message to the server.
2. The system of claim 1, wherein the server is further configured to:
after the request data are obtained, processing the request data to obtain response data; serializing the response data in the first serialization way to obtain serialized response data; generating a first HTTP response message, wherein the first HTTP response message carries the serialized response data; sending the first HTTP response message to the client;
the client is further configured to: receiving the first HTTP response message sent by the server; and obtaining the response data from the first HTTP response message according to the first serialization mode.
3. The system of claim 2, wherein the identification is located in a request line of the first HTTP request message, or in a request header of the first HTTP request message, or in a request body of the first HTTP request message.
4. The system of claim 3, wherein the identification is located in a Uniform Resource Locator (URL) in a request line of the first HTTP request message in the form of a suffix or in the form of a path parameter.
5. A data transmission method is applied to a client, and the method comprises the following steps:
the client carries out serialization processing on the request data in a first serialization mode to obtain serialized request data;
the client generates a first HTTP request message, wherein the first HTTP request message carries the serialized request data and an identifier representing the first serialization mode;
the client sends the first HTTP request message to a server;
after the client sends the first HTTP request packet to the server, the method further includes:
the client receives a response message sent by the server, and determines that the response message carries an identifier representing at least one serialization mode supported by the server according to a state code in a state line of the response message;
the client acquires at least one serialization mode supported by the server from the response message;
the client determines a serialization mode commonly supported by the client and the server;
the client carries out serialization processing on the request data in a second serialization way to obtain serialized request data, wherein the second serialization way is any one of serialization ways supported by the client and the server together;
the client generates a second HTTP request message, wherein the second HTTP request message carries the serialized request data and an identifier representing the second serialization mode;
and the client sends the second HTTP request message to the server.
6. The method of claim 5, wherein after the client sends the first HTTP request message to a server, the method further comprises:
the client receives a response message returned by the server, and determines that the response message carries serialized response data according to a state code in a state line of the response message;
and the client acquires response data from the response message according to the first serialization mode.
7. A data transmission method is applied to a server side, and the method comprises the following steps:
the server receives a first HTTP request message sent by a client, wherein the first HTTP request message carries serialized request data and an identifier representing a first serialization way for the client to perform serialization processing on the request data;
the server side obtains the identifier from the first HTTP request message, and judges whether the server side supports the first serialization mode represented by the identifier;
if the server side supports the first serialization mode, the server side obtains the request data from the first HTTP request message according to the first serialization mode;
after the server determines whether the server supports the first serialization method, the method further includes:
if the server side does not support the first serialization way, the server side determines at least one serialization way supported by the server side;
the server generates a second HTTP response message, wherein the second HTTP response message carries an identifier representing at least one serialization mode supported by the server;
and the server side sends the second HTTP response message to the client side.
8. The method of claim 7, wherein after the server obtains the requested data, the method further comprises:
the server processes the request data to obtain response data;
the server carries out serialization processing on the response data in the first serialization mode to obtain serialized response data;
the server generates a first HTTP response message, wherein the first HTTP response message carries the serialized response data;
and the server side sends the first HTTP response message to the client side.
9. A data transmission apparatus, comprising:
a processing unit to: serializing the request data in a first serialization way to obtain serialized request data; generating a first HTTP request message, wherein the first HTTP request message carries the serialized request data and an identifier representing the first serialization mode;
a transmitting unit configured to: sending the first HTTP request message to a server;
wherein the apparatus further comprises:
a receiving unit configured to: after the sending unit sends the first HTTP request message to the server, receiving a response message sent by the server;
the processing unit is further to: determining that the response message carries an identifier representing at least one serialization mode supported by the server according to a state code in a state line of the response message; acquiring at least one serialization mode supported by the server from the response message; determining a serialization mode commonly supported by the device and the server; serializing the request data in a second serialization way to obtain serialized request data, wherein the second serialization way is any one of serialization ways supported by the device and the server side; generating a second HTTP request message, wherein the second HTTP request message carries the serialized request data and an identifier representing the second serialization way;
the sending unit is further configured to: and sending the second HTTP request message to the server.
10. The apparatus of claim 9, wherein the apparatus further comprises:
a receiving unit configured to: after the sending unit sends the first HTTP request message to the server, receiving a response message returned by the server;
the processing unit is further to: determining that the response message carries serialized response data according to a state code in a state line of the response message; and acquiring response data from the response message according to the first serialization mode.
11. A data transmission apparatus, comprising:
a receiving unit configured to: receiving a first HTTP request message sent by a client, wherein the first HTTP request message carries serialized request data and an identifier representing a first serialization way for the client to perform serialization processing on the request data;
a processing unit to: obtaining the identifier from the first HTTP request message, and judging whether the device supports the first serialization mode represented by the identifier; when the device supports the first serialization mode, obtaining the request data from the first HTTP request message according to the first serialization mode;
wherein the processing unit is further to:
when the device does not support the first serialization way, determining at least one serialization way supported by the device; generating a second HTTP response message, wherein the second HTTP response message carries an identifier representing at least one serialization mode supported by the device;
the apparatus further comprises a transmitting unit configured to: and sending the second HTTP response message to the client.
12. The apparatus as recited in claim 11, said processing unit to further:
processing the request data to obtain response data; serializing the response data in the first serialization way to obtain serialized response data; generating a first HTTP response message, wherein the first HTTP response message carries the serialized response data;
the apparatus further comprises a transmitting unit configured to: and sending the first HTTP response message to the client.
CN201710582935.9A 2017-07-17 2017-07-17 Data transmission method, device and system Active CN107295003B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201710582935.9A CN107295003B (en) 2017-07-17 2017-07-17 Data transmission method, device and system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201710582935.9A CN107295003B (en) 2017-07-17 2017-07-17 Data transmission method, device and system

Publications (2)

Publication Number Publication Date
CN107295003A CN107295003A (en) 2017-10-24
CN107295003B true CN107295003B (en) 2020-01-07

Family

ID=60101525

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201710582935.9A Active CN107295003B (en) 2017-07-17 2017-07-17 Data transmission method, device and system

Country Status (1)

Country Link
CN (1) CN107295003B (en)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104348877B (en) * 2013-08-06 2018-09-18 腾讯科技（深圳）有限公司 A kind of method and device sending Http request messages
CN110728009A (en) * 2018-06-28 2020-01-24 北京京东尚科信息技术有限公司 Simulation method, device and system
WO2020037607A1 (en) * 2018-08-23 2020-02-27 华为技术有限公司 Data transmission method and apparatus
CN112286698A (en) * 2019-07-23 2021-01-29 北京地平线机器人技术研发有限公司 Remote procedure call method and device and remote procedure call execution method

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7051042B2 (en) * 2003-05-01 2006-05-23 Oracle International Corporation Techniques for transferring a serialized image of XML data
CN101446983B (en) * 2009-01-12 2011-02-02 腾讯科技（深圳）有限公司 Method, system and equipment for realizing web page acquisition by mobile terminal
CN102148855A (en) * 2010-11-23 2011-08-10 华为技术有限公司 Content acquisition and delivery methods and devices
CN104956645B (en) * 2013-01-16 2018-04-27 华为技术有限公司 URL parameter insertion and addition in self adaptation stream
US9977817B2 (en) * 2014-10-20 2018-05-22 Conduent Business Services, Llc Matching co-referring entities from serialized data for schema inference
CN104360862A (en) * 2014-11-20 2015-02-18 浪潮通用软件有限公司 Xml serialization model realization method based on attribute label and configuration file in Net platform
CN104660708B (en) * 2015-03-13 2018-01-12 黄庆宇 A kind of Mobile solution information push method and system based on HTTP
CN106487851B (en) * 2015-08-31 2019-06-18 北京国双科技有限公司 Web wrapper information transferring method, apparatus and system
CN106777292B (en) * 2016-12-29 2019-11-15 北京神州绿盟信息安全科技股份有限公司 A kind of Data Serialization method and device

Also Published As

Publication number Publication date
CN107295003A (en) 2017-10-24

Similar Documents

Publication Publication Date Title
CN107295003B (en) Data transmission method, device and system
CN109815025B (en) Service model calling method, device and storage medium
CN111447185B (en) Push information processing method and related equipment
CN111176858A (en) Data request processing method and device
CN110324405B (en) Message sending method, device, system and computer readable storage medium
US9219774B2 (en) Exchange of callback information
CN109327511B (en) Data request method and server based on HTTP (hyper text transport protocol)
CN108833565A (en) A kind of method, apparatus of monitoring server, server and storage medium
CN105099769B (en) Abnormal operation processing method, equipment and the system of business platform
CN114172929A (en) Communication method, device and gateway
CN107332854B (en) Message serialization negotiation method and service providing equipment
US9832198B2 (en) Service-based message access layer frame and implementation method thereof
CN113342503B (en) Real-time progress feedback method, device, equipment and storage medium
US9762535B2 (en) Information processing apparatus, system, method and medium
CN105281940B (en) Method, equipment and system for HELLO message interaction based on NETCONF protocol
EP2445171A1 (en) File transfer protocol client and implementing method thereof
CN107454141A (en) Solve the method and computer-readable recording medium of port collision
CN111756844A (en) Multi-language message agent method and device
CN108512694B (en) Server log analysis method and device
CN107819599A (en) Message processing method and device
CN107370731B (en) Method and device for realizing communication between different applications based on natural language
CN110636114B (en) Customer service access method, access system, service system and cloud platform
CN112631638B (en) Terminal application updating method and device, storage medium and electronic equipment
CN114679436A (en) Session management method, server and computer readable storage medium
CN110134461B (en) Universal processing method and device for data interaction

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