CN106506601B - Data transmission method and device - Google Patents

Data transmission method and device Download PDF

Info

Publication number
CN106506601B
CN106506601B CN201610892175.7A CN201610892175A CN106506601B CN 106506601 B CN106506601 B CN 106506601B CN 201610892175 A CN201610892175 A CN 201610892175A CN 106506601 B CN106506601 B CN 106506601B
Authority
CN
China
Prior art keywords
service data
client
data
pushed
pushing
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
CN201610892175.7A
Other languages
Chinese (zh)
Other versions
CN106506601A (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.)
Beijing Qihoo Technology Co Ltd
Original Assignee
Beijing Qihoo Technology 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 Beijing Qihoo Technology Co Ltd filed Critical Beijing Qihoo Technology Co Ltd
Priority to CN201610892175.7A priority Critical patent/CN106506601B/en
Publication of CN106506601A publication Critical patent/CN106506601A/en
Application granted granted Critical
Publication of CN106506601B publication Critical patent/CN106506601B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/14Session management
    • H04L67/143Termination or inactivation of sessions, e.g. event-controlled end of session
    • H04L67/145Termination or inactivation of sessions, e.g. event-controlled end of session avoiding end of session, e.g. keep-alive, heartbeats, resumption message or wake-up for inactive or interrupted session
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/50Network services
    • H04L67/55Push-based network services

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Health & Medical Sciences (AREA)
  • Cardiology (AREA)
  • General Health & Medical Sciences (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

The invention discloses a data transmission method and device, relates to the technical field of internet, and aims to solve the problem that the real-time performance of the existing management and control mode for a client is poor. The method of the invention comprises the following steps: the server establishes socket long connection with the client; when service updating is monitored, actively pushing updated service data to the client through the socket long connection, wherein the service data are tasks or strategies to be executed by the client; and monitoring the relevant process of the pushed service data in real time. The method and the device are applied to the process of managing and controlling the client side by the server.

Description

Data transmission method and device
Technical Field
The present invention relates to the field of internet technologies, and in particular, to a method and an apparatus for data transmission.
Background
In the prior art, a server manages and controls a client in a passive mode. Specifically, the management policy is that the client periodically polls the server in the heartbeat interval mode, that is, the client periodically sends a request to the server to obtain information such as a task or a policy from the server. The implementation of the management strategy of the periodic polling requires that the client establishes a new connection with the server before sending a request each time, and then sends the request to the server, so that the server issues a task or a strategy, and releases the connection after the issuance is completed.
Under the passive management and control mode, when a server has a new task or policy, the new task or policy is generally issued to the client only when waiting for a request of the client, and the real-time performance of acquiring the new task or policy by the client is poor; in addition, since the server is passive, it is not possible to acquire information such as process behavior information and an operation registry of the client in real time. In summary, the existing management and control method has poor real-time performance.
Disclosure of Invention
In view of the above, the present invention has been made to provide a method and apparatus for data transmission that overcomes or at least partially solves the above problems.
To solve the above technical problem, in one aspect, the present invention provides a data transmission method, including:
the server establishes socket long connection with the client;
when service updating is monitored, actively pushing updated service data to the client through the socket long connection, wherein the service data are tasks or strategies to be executed by the client;
and monitoring the relevant process of the pushed service data in real time.
In another aspect, the present invention provides an apparatus for data transmission, including:
the system comprises an establishing unit, a receiving unit and a sending unit, wherein the establishing unit is used for establishing socket long connection between a server and a client;
the pushing unit is used for actively pushing updated service data to the client through the socket long connection when service update is monitored, wherein the service data is a task or a strategy to be executed by the client;
and the monitoring unit is used for monitoring the related process of the pushed service data in real time.
By means of the technical scheme, the data transmission method and the data transmission device provided by the invention can firstly establish long socket connection between the server and the client; then, when service updating is monitored, actively pushing updated service data to the client through socket long connection, wherein the service data are tasks or strategies to be executed by the client; and the progress of the pushed service data can be monitored in real time through the socket long connection. Compared with the prior art, the server can actively push the corresponding updated service data to the client when monitoring the service update, and the long connection can keep the continuous connection between the client and the service because the long connection is established between the server and the client, so that the server does not need to acquire the service data when the client sends a request to the server, and the real-time performance of the service data can be ensured. In addition, because the server and the client can be continuously connected, the server can monitor the process of service pushing in real time, and the real-time performance of client management and control is improved.
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 a method for data transmission according to an embodiment of the present invention;
fig. 2 is a flow chart of another method for data transmission according to an embodiment of the present invention;
fig. 3 is a flowchart of another method for data transmission according to an embodiment of the present invention;
FIG. 4 is a block diagram illustrating an apparatus for data transmission according to an embodiment of the present invention;
fig. 5 is a block diagram illustrating another apparatus for data transmission according to an embodiment of the present invention.
Detailed Description
Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may 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 disclosure to those skilled in the art.
In order to solve the problem that the real-time performance of the existing management and control method for the client is poor, an embodiment of the present invention provides a data transmission method, as shown in fig. 1, the method includes:
101. the server establishes a socket long connection with the client.
It should be noted that, in the present embodiment, management and control of the server to the client are targeted, and therefore, establishing a connection between the server and the client is a basis for implementing management and control of the server to the client. In this embodiment, a long socket connection is established between the server and the client, and the long socket connection is different from a short heartbeat polling socket connection between the existing server and the client. The socket short connections used in the prior art do not maintain a continuous connection between the client and the server, since the connection is closed after each data transmission is finished; after the socket long connection is established, the continuous connection between the client and the server can be maintained, and the connection between the client and the server is maintained by sending a data packet at regular time instead of closing the connection after the data transmission is finished each time, so that the connection does not need to be reestablished when the data transmission is carried out next time. The establishment of the socket long connection between the client and the server is the basis for the realization of real-time control of the client by the server. The specific process of establishing the socket long connection between the server and the client is the same as that in the prior art.
In addition, compared with the existing socket short connection mode, the method for establishing the socket long connection can save the resource consumption and time consumption of establishing new connection for multiple times when data is transmitted for multiple times, and is friendly to a firewall under the condition that the server is isolated from the client side by the firewall. Because in the socket short connection mode, new connections need to be established continuously, and when the number of the new connections exceeds a certain number, the firewall may be broken.
102. And when monitoring that the service is updated, actively pushing the updated service data to the client through the socket long connection.
And when the server monitors that the service is updated inside, the server pushes the updated service data to the client in real time. The server can push the updated service data to the client in real time because the client is in long socket connection with the server, and the updated service data can be pushed without waiting for polling of the client as in the prior art. The server pushes the updated service data to the client in time, and the client can acquire the updated service data in time, so that the real-time performance of pushing and acquiring the service data is ensured, and the updated service data can play a role in time. The service data mainly refers to tasks or policies included in the service, and these service data are tasks or policies that the client needs to execute. In addition, it should be noted that the server includes different services, the different services correspond to different service blocks, and the push service data is pushed by a unified push block inside the server.
103. And monitoring the relevant process of the pushed service data in real time.
After the updated service data is pushed to the client, in order to know the executed relevant information of the pushed service data in the transmission process and on the client side in real time, the relevant process of the pushed service data needs to be monitored in real time. The specific relevant process of the pushed service data mainly comprises the following steps: firstly, the condition of the pushed service data in the transmission process specifically means whether the pushed service data is normally carried out in the transmission process, and since the pushed service data may include a plurality of data packets, a failure may occur in the transmission of some data packets in the transmission process, which results in that the client cannot obtain the complete service data, real-time monitoring is required to ensure that the problem is found in time and is solved in time. Secondly, the related process of the pushed business data in the client specifically refers to the execution condition of tasks or policies contained in the business data, and the monitoring of the related process of the business data in the client is to better manage and control the client.
In the data transmission method provided by this embodiment, a long socket connection can be established between the server and the client; then, when service updating is monitored, actively pushing updated service data to the client through socket long connection, wherein the service data are tasks or strategies to be executed by the client; and the progress of the pushed service data can be monitored in real time through the socket long connection. Compared with the prior art, in the embodiment, when monitoring the service update, the server can actively push the corresponding updated service data to the client, and because the long connection is established between the server and the client, the long connection can keep the continuous connection between the client and the service, the server does not need to acquire the service data when the client sends a request to the server, so that the real-time performance of the service data can be ensured. In addition, because the server and the client can be continuously connected, the server can monitor the process of service pushing in real time, and the real-time performance of client management and control is improved.
Further, as a refinement and an extension of the method shown in fig. 1, another embodiment of the present invention further provides a method for data transmission. As shown in fig. 2, the method includes:
201. the server establishes a socket long connection with the client.
The implementation of this step is the same as that of step 101 in fig. 1, and is not described here again.
202. And when monitoring that the service is updated, actively pushing the updated service data to the client through the socket long connection.
The implementation of this step is the same as that of step 102 in fig. 1, and is not described here again.
203. And detecting whether the confirmation response is received.
After the updated service data is pushed to the client, in order to ensure the reliability of data transmission, that is, to ensure that the client really receives the service data pushed by the server, this embodiment ensures the reliability of data transmission through an Acknowledgement (ACK) mechanism, where the ACK mechanism is that when the sender sends a custom message to the receiver, the receiver replies an ACK to the sender after receiving the message, and the sender knows that the receiver really receives the message after receiving the ACK. In this embodiment, the server is a sender and the client is a receiver, so that the server detects whether an acknowledgement response, that is, whether an ACK is received, where the acknowledgement response is a response sent by the client to acknowledge receipt of the service data.
It should be noted that, in this embodiment, the implementation of the ACK response mechanism is implemented by modifying an existing websocket standard protocol.
204. And if the confirmation response is not received within the preset time period, the business data is pushed again.
Judging the detection result of the step 203, if receiving the confirmation response, indicating that the client receives the service data pushed by the server, so that the pushing of the service data can be terminated; if the acknowledgement response is not received within the preset time period, which indicates that the client does not receive the service data pushed by the server, the updated service data needs to be pushed to the client again until the acknowledgement response can be received. The preset time period can be freely set according to the actual application condition.
205. And distributing different clients to corresponding monitoring areas according to preset rules.
The preset rule is a uniform hash distribution principle, that is, all the clients are uniformly distributed into different monitoring areas to monitor the process of the service data pushed to the client through the different monitoring areas, and the specific implementation manner of monitoring the process of the service data pushed to the client is the same as the implementation manner of step 103 in fig. 1, which is not described herein again. In addition, the client sides are uniformly distributed into different monitoring areas, so that the efficiency of pushing service data and monitoring the service data to the client sides by the server can be improved.
Further, as a refinement and an extension of the method shown in fig. 1 and fig. 2, another embodiment of the present invention further provides a method for data transmission. As shown in fig. 3, the method includes:
301. the server establishes a socket long connection with the client.
The implementation of this step is the same as that of step 101 in fig. 1, and is not described here again.
302. And receiving a data request sent by the client through the socket long connection.
In addition to the mode in which the server in fig. 1 can push updated service data to the client, the present embodiment provides another mode, specifically, the client may also actively send a data request to the server through the socket long connection, where the data request is a request for the client to obtain service data from the server. The data request is not limited to the service data after the service update is requested. Because the client and the server are in socket long connection, the client can send data requests at any time. Therefore, after the client sends a data request to the server, the server can receive the data request sent by the client through the established socket long connection.
303. And returning a first confirmation response to the client.
After the server receives the data request sent by the client, in order to inform the client that the data request is confirmed to be received, a first confirmation response needs to be returned to the client, so that the client can judge whether to resend the data request to the server according to whether the first confirmation response is received. In this embodiment, the first acknowledgement response is returned by the ue, also because an ACK response mechanism is added. The answering mechanism is the same as in step 203 of fig. 2. The first acknowledgment response corresponds to the acknowledgment response in step 203 of fig. 2.
304. And analyzing the data request and determining an acquisition address of the service data corresponding to the data request.
After receiving a data request sent by a client, a server needs to push corresponding service data to the client, and since the service data in the server is pushed by a pushing plate and the service data needing to be pushed is in different service plates, after the data request is obtained, the data request needs to be analyzed, and it is determined that the data request contains different services and corresponding service data. After determining the service corresponding to the data request and the corresponding service data, the corresponding service plate can be found according to the corresponding service and the corresponding service data, addresses of different service plates in the server are different, and then the address of the corresponding service plate is determined as the acquisition address of the service data corresponding to the data request.
305. And acquiring the service data corresponding to the data request, and pushing the service data corresponding to the data request to the client.
After the acquisition address of the service data corresponding to the data request is determined, the service data corresponding to the data request can be acquired according to the corresponding acquisition address. Specifically, the method comprises the following steps: and the pushing plate in the server sends the corresponding data request to the corresponding service plate according to the corresponding acquisition address, and then the service plate returns the service data corresponding to the data request to the pushing plate according to the data request. And the pushing plate pushes the service data corresponding to the data request to the corresponding client after acquiring the service data corresponding to the data request.
306. Detecting whether a second acknowledgement response is received.
In the same manner as the implementation manner of step 203 in fig. 2, an ACK response mechanism is used, and after the pushing plate in the server pushes the service data of the corresponding data request to the client, it is detected whether a second acknowledgement response is received, where the second acknowledgement response is a response sent by the client to acknowledge the service data corresponding to the data request. The second acknowledgement response is the same as the acknowledgement response in step 203 in fig. 2, and whether the detection side receives the second acknowledgement response is also for ensuring the reliability of the service data transmission.
307. And if the second confirmation response is not received within the preset time period, the business data corresponding to the data request is pushed again.
The implementation of this step is the same as that of step 204 in fig. 2, and is not described here again.
Further, as an implementation of the foregoing embodiments, another embodiment of the embodiments of the present invention further provides a data transmission apparatus, which is used to implement the methods described in fig. 1, fig. 2, and fig. 3. As shown in fig. 4, the apparatus includes: a setup unit 401, a push unit 402 and a monitoring unit 403.
An establishing unit 401, configured to establish a socket long connection between a server and a client;
the pushing unit 402 is configured to actively push updated service data to the client through a socket long connection when service update is monitored, where the service data is a task or a policy that the client needs to execute;
and a monitoring unit 403, configured to monitor a relevant process of the pushed service data in real time.
Further, as shown in fig. 5, the apparatus further includes:
the detecting unit 404 is configured to detect whether a confirmation response is received after actively pushing the updated service data to the client through the socket long connection, where the confirmation response is a response sent by the client to confirm that the service data is received;
a terminating unit 405, configured to terminate pushing of the service data if the acknowledgement is received;
a re-pushing unit 406, configured to re-push the service data if the acknowledgement is not received within the preset time period.
Further, the monitoring unit 403 is configured to:
and allocating different clients to corresponding monitoring areas according to preset rules so as to monitor the related processes of the service data pushed to the clients through the different monitoring areas.
Further, as shown in fig. 5, the apparatus further includes:
a sending unit 407, configured to receive, through a socket long connection, a data request sent by a client, where the data request is a request for the client to obtain corresponding service data from a server;
a returning unit 408, configured to return a first acknowledgement response to the client, where the first acknowledgement response is a response of the server acknowledging that the data request is received;
the pushing unit 402 is further configured to push the service data corresponding to the data request to the client.
Further, as shown in fig. 5, the apparatus further includes:
the analysis unit 409 is configured to analyze the data request before pushing the service data corresponding to the data request to the client;
a determining unit 410, configured to determine an obtaining address of service data corresponding to the data request;
the obtaining unit 411 is configured to obtain service data corresponding to the data request.
Further, the apparatus further comprises:
the detecting unit 404 is further configured to detect whether a second acknowledgement response is received after the service data corresponding to the data request is pushed to the client, where the second acknowledgement response is a response sent by the client to acknowledge the service data corresponding to the data request;
the terminating unit 405 is further configured to terminate the pushing of the service data if the second acknowledgement response is received;
the re-pushing unit 406 is further configured to, if the second acknowledgement is not received within the preset time period, re-push the service data corresponding to the data request.
The data transmission device provided by this embodiment can establish a socket long connection between the server and the client; then, when service updating is monitored, actively pushing updated service data to the client through socket long connection, wherein the service data are tasks or strategies to be executed by the client; and the progress of the pushed service data can be monitored in real time through the socket long connection. Compared with the prior art, in the embodiment, when monitoring the service update, the server can actively push the corresponding updated service data to the client, and because the long connection is established between the server and the client, the long connection can keep the continuous connection between the client and the service, the server does not need to acquire the service data when the client sends a request to the server, so that the real-time performance of the service data can be ensured. In addition, because the server and the client can be continuously connected, the server can monitor the process of service pushing in real time, and the real-time performance of client management and control is improved.
In the foregoing embodiments, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.
It will be appreciated that the relevant features of the method and apparatus described above are referred to one another. In addition, "first", "second", and the like in the above embodiments are for distinguishing the embodiments, and do not represent merits of the embodiments.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
The algorithms and displays presented herein are not inherently related to any particular computer, virtual machine, or other apparatus. Various general purpose systems may also be used with the teachings herein. The required structure for constructing such a system will be apparent from the description above. Moreover, the present invention is not directed to any particular programming language. It is appreciated that a variety of programming languages may be used to implement the teachings of the present invention as described herein, and any descriptions of specific languages are provided above to disclose the best mode of the invention.
In the description provided herein, numerous specific details are set forth. It is understood, however, that embodiments of the invention may be practiced without these specific details. In some instances, well-known methods, structures and techniques have not been shown in detail in order not to obscure an understanding of this description.
Similarly, it should be appreciated that in the foregoing description of exemplary embodiments of the invention, various features of the invention are sometimes grouped together in a single embodiment, figure, or description thereof for the purpose of streamlining the disclosure and aiding in the understanding of one or more of the various inventive aspects. However, the disclosed method should not be interpreted as reflecting an intention that: that the invention as claimed requires more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive aspects lie in less than all features of a single foregoing disclosed embodiment. Thus, the claims following the detailed description are hereby expressly incorporated into this detailed description, with each claim standing on its own as a separate embodiment of this invention.
Those skilled in the art will appreciate that the modules in the device in an embodiment may be adaptively changed and disposed in one or more devices different from the embodiment. The modules or units or components of the embodiments may be combined into one module or unit or component, and furthermore they may be divided into a plurality of sub-modules or sub-units or sub-components. All of the features disclosed in this specification (including any accompanying claims, abstract and drawings), and all of the processes or elements of any method or apparatus so disclosed, may be combined in any combination, except combinations where at least some of such features and/or processes or elements are mutually exclusive. Each feature disclosed in this specification (including any accompanying claims, abstract and drawings) may be replaced by alternative features serving the same, equivalent or similar purpose, unless expressly stated otherwise.
Furthermore, those skilled in the art will appreciate that while some embodiments described herein include some features included in other embodiments, rather than other features, combinations of features of different embodiments are meant to be within the scope of the invention and form different embodiments. For example, in the following claims, any of the claimed embodiments may be used in any combination.
The various component embodiments of the invention may be implemented in hardware, or in software modules running on one or more processors, or in a combination thereof. Those skilled in the art will appreciate that a microprocessor or Digital Signal Processor (DSP) may be used in practice to implement some or all of the functions of some or all of the components in the title of the invention (e.g., a data transfer device) according to an embodiment of the invention. The present invention may also be embodied as apparatus or device programs (e.g., computer programs and computer program products) for performing a portion or all of the methods described herein. Such programs implementing the present invention may be stored on computer-readable media or may be in the form of one or more signals. Such a signal may be downloaded from an internet website or provided on a carrier signal or in any other form.
It should be noted that the above-mentioned embodiments illustrate rather than limit the invention, and that those skilled in the art will be able to design alternative embodiments without departing from the scope of the appended claims. In the claims, any reference signs placed between parentheses shall not be construed as limiting the claim. The word "comprising" does not exclude the presence of elements or steps not listed in a claim. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. The invention may be implemented by means of hardware comprising several distinct elements, and by means of a suitably programmed computer. In the unit claims enumerating several means, several of these means may be embodied by one and the same item of hardware. The usage of the words first, second and third, etcetera do not indicate any ordering. These words may be interpreted as names.

Claims (12)

1. A method of data transmission, the method comprising:
the server establishes socket long connection with the client;
when service updating is monitored, actively pushing updated service data to the client through the socket long connection, wherein the service data are tasks or strategies to be executed by the client;
monitoring the relevant process of the pushed service data in real time, wherein the relevant process of the pushed service data comprises the following steps: whether the pushed service data is normally executed in the transmission process and/or the execution condition of the tasks or strategies contained in the pushed service data.
2. The method of claim 1, wherein after the proactively pushing updated traffic data to the client over the socket long connection, the method further comprises:
detecting whether a confirmation response is received, wherein the confirmation response is a response which is sent by a client and confirms that the service data is received;
if the confirmation response is received, the pushing of the service data is terminated;
and if the confirmation response is not received within a preset time period, the service data is pushed again.
3. The method of claim 1, wherein the monitoring the progress of the pushed service data in real time comprises:
and allocating different clients to corresponding monitoring areas according to preset rules so as to monitor the related processes of the service data pushed to the clients through the different monitoring areas.
4. The method of claim 1, further comprising:
receiving a data request sent by the client through the socket long connection, wherein the data request is a request for the client to acquire corresponding service data from a server;
returning a first confirmation response to the client, wherein the first confirmation response is a response of the server for confirming that the data request is received; and the number of the first and second electrodes,
and pushing the service data corresponding to the data request to the client.
5. The method according to claim 4, wherein before the pushing the service data corresponding to the data request to the client, the method further comprises:
analyzing the data request;
determining an acquisition address of the service data corresponding to the data request;
and acquiring the service data corresponding to the data request.
6. The method according to claim 4, wherein after the pushing the service data corresponding to the data request to the client, the method further comprises:
detecting whether a second confirmation response is received, wherein the second confirmation response is a response which is sent by the client and confirms that the service data corresponding to the data request is received;
if the second confirmation response is received, the pushing of the service data is terminated;
and if the second confirmation response is not received within a preset time period, pushing the service data corresponding to the data request again.
7. An apparatus for data transmission, the apparatus comprising:
the system comprises an establishing unit, a receiving unit and a sending unit, wherein the establishing unit is used for establishing socket long connection between a server and a client;
the pushing unit is used for actively pushing updated service data to the client through the socket long connection when service update is monitored, wherein the service data is a task or a strategy to be executed by the client;
a monitoring unit, configured to monitor a relevant process of the pushed service data in real time, where the relevant process of the pushed service data includes: whether the pushed service data is normally executed in the transmission process and/or the execution condition of the tasks or strategies contained in the pushed service data.
8. The apparatus of claim 7, further comprising:
the detection unit is used for detecting whether a confirmation response is received or not after the updated service data is actively pushed to the client through the socket long connection, wherein the confirmation response is a response sent by the client and confirming that the service data is received;
a terminating unit, configured to terminate the pushing of the service data if the acknowledgement is received;
and the re-pushing unit is used for re-pushing the service data if the confirmation response is not received within a preset time period.
9. The apparatus of claim 7, wherein the monitoring unit is configured to:
and allocating different clients to corresponding monitoring areas according to preset rules so as to monitor the related processes of the service data pushed to the clients through the different monitoring areas.
10. The apparatus of claim 7, further comprising:
the sending unit is used for receiving a data request sent by the client through the socket long connection, wherein the data request is a request for the client to obtain corresponding service data from a server;
a returning unit, configured to return a first acknowledgement response to the client, where the first acknowledgement response is a response of the server to acknowledge receipt of the data request;
the pushing unit is further configured to push the service data corresponding to the data request to the client.
11. The apparatus of claim 10, further comprising:
the analysis unit is used for analyzing the data request before the business data corresponding to the data request is pushed to the client;
a determining unit, configured to determine an acquisition address of service data corresponding to the data request;
and the acquisition unit is used for acquiring the service data corresponding to the data request.
12. The apparatus of claim 10, further comprising:
the detection unit is further configured to detect whether a second acknowledgement response is received after the service data corresponding to the data request is pushed to the client, where the second acknowledgement response is a response sent by the client to acknowledge receipt of the service data corresponding to the data request;
the termination unit is further used for terminating the pushing of the service data if the second confirmation response is received;
and the re-pushing unit is further configured to re-push the service data corresponding to the data request if the second acknowledgement response is not received within a preset time period.
CN201610892175.7A 2016-10-12 2016-10-12 Data transmission method and device Active CN106506601B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201610892175.7A CN106506601B (en) 2016-10-12 2016-10-12 Data transmission method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201610892175.7A CN106506601B (en) 2016-10-12 2016-10-12 Data transmission method and device

Publications (2)

Publication Number Publication Date
CN106506601A CN106506601A (en) 2017-03-15
CN106506601B true CN106506601B (en) 2020-05-15

Family

ID=58293649

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201610892175.7A Active CN106506601B (en) 2016-10-12 2016-10-12 Data transmission method and device

Country Status (1)

Country Link
CN (1) CN106506601B (en)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108228210B (en) * 2017-12-08 2021-06-04 平安科技(深圳)有限公司 Resource updating method and system
CN110012115A (en) * 2019-05-06 2019-07-12 广州华多网络科技有限公司 The update method and system of direct broadcasting room pushed information
CN112054985B (en) * 2019-06-06 2024-01-19 全球能源互联网研究院有限公司 Data interaction method and system for mobile terminal and field detection test equipment
CN110430197A (en) * 2019-08-08 2019-11-08 王小聪 A kind of transaction data synchronization method of block chain network

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101360127A (en) * 2008-09-10 2009-02-04 金蝶软件(中国)有限公司 File updating method and transmission system
CN101820447A (en) * 2010-03-31 2010-09-01 青岛海信宽带多媒体技术有限公司 Software upgrading method and upgrading device
CN102271123A (en) * 2010-06-01 2011-12-07 阿里巴巴集团控股有限公司 Communication method, system and equipment
CN103297511A (en) * 2013-05-15 2013-09-11 百度在线网络技术(北京)有限公司 Client/ server scheduling method and system under highly dynamic environment
CN105426186A (en) * 2015-11-13 2016-03-23 上海斐讯数据通信技术有限公司 Method and system for obtaining application software update data of terminal through server

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1306755C (en) * 2003-01-16 2007-03-21 华为技术有限公司 Service testing device and method
CN101472290B (en) * 2007-12-29 2010-07-14 中国移动通信集团公司 Flow control method and apparatus for mobile data business platform performance test
CN102420805B (en) * 2010-09-27 2014-07-23 阿里巴巴集团控股有限公司 Method, system and device for communication by virtue of socket connection
CN104519129A (en) * 2014-12-16 2015-04-15 京信通信系统(中国)有限公司 Data transmission method, device and system

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101360127A (en) * 2008-09-10 2009-02-04 金蝶软件(中国)有限公司 File updating method and transmission system
CN101820447A (en) * 2010-03-31 2010-09-01 青岛海信宽带多媒体技术有限公司 Software upgrading method and upgrading device
CN102271123A (en) * 2010-06-01 2011-12-07 阿里巴巴集团控股有限公司 Communication method, system and equipment
CN103297511A (en) * 2013-05-15 2013-09-11 百度在线网络技术(北京)有限公司 Client/ server scheduling method and system under highly dynamic environment
CN105426186A (en) * 2015-11-13 2016-03-23 上海斐讯数据通信技术有限公司 Method and system for obtaining application software update data of terminal through server

Also Published As

Publication number Publication date
CN106506601A (en) 2017-03-15

Similar Documents

Publication Publication Date Title
US11228638B2 (en) Systems and methods for seamless host migration
CN106506601B (en) Data transmission method and device
US20210176143A1 (en) Monitoring wireless access point events
CN108512885B (en) Method, system and storage medium for network packet processing
US20100180037A1 (en) Method and apparatus for optimizing and prioritizing the creation of a large number of VPN tunnels
US20050180419A1 (en) Managing transmission control protocol (TCP) connections
WO2014056344A1 (en) Method and device for monitoring
JP2009544259A (en) Method and apparatus for policy enforcement in a wireless communication system
JP6849795B2 (en) Communication method and equipment
CN103501347A (en) Resource distribution method and device
CN113630908B (en) Method for releasing mission critical data communication, user equipment and server
CN110597631B (en) Resource management method, monitoring server, proxy server, and storage medium
JP2012522417A5 (en)
JP2014041404A (en) Terminal service monitoring device
CN107231567B (en) Message transmission method, device and system
WO2017165999A1 (en) Network service implementation method, service controller, and communication system
CN114363204A (en) Request monitoring method, network device and storage medium
CN110474807B (en) Log processing method and device
CN114489730A (en) Remote upgrading method, terminal equipment and computer readable storage medium
CN112073558A (en) Method and device for accessing Internet of things, Internet of things equipment and storage medium
CN108011944B (en) Method for reducing http request failure on Android
CN113411228A (en) Network condition determining method and server
JP2010238101A (en) Device, method, program and system of load distribution
EP3038290A1 (en) Method and device for application management
JP6181591B2 (en) Address payout method, address payout system, address payout server device, and address payout program

Legal Events

Date Code Title Description
C06 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