CN107517136B - Method, device and system for realizing heartbeat keep-alive - Google Patents
Method, device and system for realizing heartbeat keep-alive Download PDFInfo
- Publication number
- CN107517136B CN107517136B CN201610427724.3A CN201610427724A CN107517136B CN 107517136 B CN107517136 B CN 107517136B CN 201610427724 A CN201610427724 A CN 201610427724A CN 107517136 B CN107517136 B CN 107517136B
- Authority
- CN
- China
- Prior art keywords
- heartbeat
- strategy
- alive
- keep
- mode
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/10—Active monitoring, e.g. heartbeat, ping or trace-route
-
- 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
- H04L67/143—Termination or inactivation of sessions, e.g. event-controlled end of session
- H04L67/145—Termination 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
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D30/00—Reducing energy consumption in communication networks
- Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks
Abstract
The invention provides a method, a device and a system for realizing heartbeat keep-alive, which are used for detecting whether the running mode of client equipment changes or not; under the condition that the change of the operation mode is detected, the heartbeat strategy corresponding to the changed operation mode is determined in the heartbeat keep-alive strategies configured according to the preset conditions, and the heartbeat strategy is executed, wherein the heartbeat keep-alive strategies are used for indicating the heartbeat strategy corresponding to each operation mode, so that the problem that the flow and the electric quantity consumption of a client are large due to the fact that the client needs frequent heartbeat keep-alive between the client and a server in the mobile communication field based on an XMPP protocol is solved, and the effect of reducing the flow and the electric quantity consumption of the client is achieved.
Description
Technical Field
The invention relates to the field of communication, in particular to a method, a device and a system for realizing heartbeat keep-alive.
Background
Extensible Messaging and Presence Protocol (XMPP) is an open instant Messaging Protocol based on Extensible Markup Language (XML), which can be used for XML data stream type transmission in service type real-time communication, presentation and demand response services, and occupies a large share in the instant Messaging market by virtue of its great flexibility and openness.
However, XMPP protocol is always vulnerable to the mobile field, one of the important reasons is the problem of large traffic consumption, where heartbeat keep-alive between the client and the server accounts for a large proportion, and the XMPP protocol provides Ping and Pong messages as a pair of heartbeat back-and-forth messages, each message having on average more than 100 bytes (this is only a message of an application layer, and does not include a message header of a lower layer such as a protocol layer), if heartbeat is once every 10 seconds, there is at least nearly 50K of traffic per hour, and the heartbeat is bidirectional, and the server also initiates heartbeat keep-alive to the client at certain intervals, and also puts pressure on the server to process messages. However, the heartbeat keep-alive is necessary, because in a mobile environment, a user frequently goes on and off the line and frequently drops off the line, and whether the other party is on the line can be detected only by the heartbeat keep-alive mode.
Aiming at the problem that the client flow and the electric quantity consumption are large due to the fact that the XMPP protocol needs frequent heartbeat keep-alive between the client and the server in the mobile communication field in the related technology, an effective solution is not provided at present.
Disclosure of Invention
The embodiment of the invention provides a heartbeat keep-alive realization method, a heartbeat keep-alive realization device and a heartbeat keep-alive realization system, which are used for at least solving the problem that the client flow and the electric quantity consumption are larger due to the fact that the client and a server need frequent heartbeat keep-alive in the mobile communication field based on an XMPP protocol in the related technology.
According to an embodiment of the present invention, a method for implementing heartbeat keep-alive is provided, including: detecting whether the operation mode of the client device is changed; and under the condition that the change of the operation mode is detected, determining a heartbeat strategy corresponding to the changed operation mode in heartbeat keep-alive strategies configured according to preset conditions, and executing the heartbeat strategy, wherein the heartbeat keep-alive strategies are used for indicating the heartbeat strategy corresponding to each operation mode.
Optionally, the preset condition includes a configuration condition and/or a usage habit of the user within a preset time period: wherein the configuration condition includes at least one of: each network mode, and the corresponding service time and service frequency of each network mode; the usage habits include at least one of: each network mode, the time period for using each network mode, and the service cycle corresponding to the network mode.
Further, optionally, before detecting whether the operation mode of the client device is changed, the method further includes: configuring a heartbeat keep-alive strategy according to preset conditions; under the condition that the preset condition is the configuration condition, respectively configuring heartbeat strategies in each operation mode according to each network mode, the corresponding service time and the corresponding service frequency of each network mode to obtain heartbeat keep-alive strategies; wherein, the network mode includes: an operator network or a publicly accessible network; the operation mode is an operation state applied to the configuration condition.
Optionally, configuring the heartbeat keep-alive policy according to the preset condition includes: under the condition that the preset condition is the use habit, generating corresponding data processing models respectively according to each network mode in the use habit, the time period for using each network mode and/or the use period corresponding to the network mode; and configuring a corresponding heartbeat strategy according to the data processing model to obtain a heartbeat keep-alive strategy.
Optionally, before detecting whether the operation mode of the client device is changed, the method further includes: sending the heartbeat keep-alive strategy to a server; receiving response information returned by the server, wherein the response information at least comprises the following information: whether a capability set of heartbeat keep-alive policies is supported, and/or authentication parameters.
Optionally, determining a heartbeat policy corresponding to the changed operation mode in the heartbeat keep-alive policies configured according to the preset conditions, and executing the heartbeat policy includes: matching a heartbeat strategy corresponding to the changed running mode according to the heartbeat keep-alive strategy; under the condition that the heartbeat strategy corresponding to the running mode before the change is a first heartbeat strategy and the heartbeat strategy corresponding to the running mode after the change is a second heartbeat strategy, switching the first heartbeat strategy to the second heartbeat strategy; a second heartbeat policy is executed.
Further, optionally, the executing the second heartbeat policy includes: executing heartbeat keep-alive operation according to a second heartbeat strategy; sending the second heartbeat policy to a server; and receiving heartbeat keep-alive operation switching response information returned by the server, wherein the heartbeat keep-alive operation switching response information is used for indicating the server to execute switching operation of the heartbeat keep-alive strategy according to the second heartbeat strategy.
According to another embodiment of the present invention, there is provided a device for implementing heartbeat keep-alive, including: the detection module is used for detecting whether the operation mode of the client equipment is changed; and the strategy switching module is used for determining a heartbeat strategy corresponding to the changed operation mode in heartbeat keep-alive strategies configured according to preset conditions under the condition that the operation mode is detected to be changed, and executing the heartbeat strategy, wherein the heartbeat keep-alive strategies are used for indicating the heartbeat strategy corresponding to each operation mode.
Optionally, the preset condition includes a configuration condition and/or a usage habit of the user within a preset time period: wherein the configuration condition includes at least one of: each network mode, and the corresponding service time and service frequency of each network mode; usage habits include at least one of: each network mode, the time period for using each network mode, and the service cycle corresponding to the network mode.
Further, optionally, the apparatus further comprises: the configuration module is used for configuring a heartbeat keep-alive strategy according to preset conditions before detecting whether the operation mode of the client equipment is changed; the first configuration unit is used for configuring the heartbeat strategies in each operation mode according to each network mode, the corresponding service time and the corresponding service frequency of each network mode respectively under the condition that the preset condition is the configuration condition, so as to obtain the heartbeat keep-alive strategies; wherein, the network mode includes: an operator network or a publicly accessible network; the operation mode is an operation state applied to the configuration condition.
Optionally, the configuration module includes: the generation unit is used for respectively generating corresponding data processing models according to each network mode in the use habit, the time period for using each network mode and/or the use period corresponding to the network mode under the condition that the preset condition is the use habit; and the second configuration unit is used for configuring the corresponding heartbeat strategy according to the data processing model to obtain a heartbeat keep-alive strategy.
Optionally, the apparatus further comprises: the sending module is used for sending the heartbeat keep-alive strategy to the server before detecting whether the operation mode of the client equipment is changed; a receiving module, configured to receive response information returned by the server, where the response information at least includes the following: whether a capability set of heartbeat keep-alive policies is supported, and/or authentication parameters.
Optionally, the policy switching module includes: the matching unit is used for matching the heartbeat strategy corresponding to the changed operation mode according to the heartbeat keep-alive strategy; the switching unit is used for switching the first heartbeat strategy to the second heartbeat strategy under the condition that the heartbeat strategy corresponding to the running mode before change is the first heartbeat strategy and the heartbeat strategy corresponding to the running mode after change is the second heartbeat strategy; and the execution unit is used for executing the second heartbeat strategy.
Further, optionally, the execution unit includes: the execution subunit is used for executing the heartbeat keep-alive operation according to a second heartbeat strategy; a sending unit, configured to send the second heartbeat policy to a server; and the receiving unit is used for receiving heartbeat keep-alive operation switching response information returned by the server, wherein the heartbeat keep-alive operation switching response information is used for indicating the server to execute the switching operation of the heartbeat keep-alive strategy according to the second heartbeat strategy.
According to another embodiment of the present invention, a system for implementing heartbeat keep-alive is provided, including: the client is used for configuring heartbeat keep-alive strategies according to preset conditions, sending the heartbeat keep-alive strategies to the server through a login process, receiving response information returned by the server and supporting the heartbeat keep-alive strategies, matching the heartbeat strategies corresponding to the changed operation modes in the heartbeat keep-alive strategies under the condition that the operation modes are detected to be changed, and executing the heartbeat strategies; and the server is used for receiving the heartbeat keep-alive strategy sent by the client, returning response information supporting the heartbeat keep-alive strategy and receiving a heartbeat strategy switching indication sent by the client under the condition that the running mode of the client is changed.
According to still another embodiment of the present invention, there is also provided a storage medium. The storage medium is configured to store program code for performing the steps of: detecting whether the operation mode of the client device is changed; and under the condition that the change of the operation mode is detected, determining a heartbeat strategy corresponding to the changed operation mode in heartbeat keep-alive strategies configured according to preset conditions, and executing the heartbeat strategy, wherein the heartbeat keep-alive strategies are used for indicating the heartbeat strategy corresponding to each operation mode.
Optionally, the storage medium is further arranged to store program code for performing the steps of: before detecting whether the operation mode of the client device is changed, the method further comprises: configuring a heartbeat keep-alive strategy according to preset conditions; under the condition that the preset condition is the configuration condition, respectively configuring heartbeat strategies in each operation mode according to each network mode, the corresponding service time and the corresponding service frequency of each network mode to obtain heartbeat keep-alive strategies; wherein, the network mode includes: an operator network or a publicly accessible network; the operation mode is an operation state applied to the configuration condition.
Further, optionally, configuring the heartbeat keep-alive policy according to a preset condition includes: under the condition that the preset condition is the use habit, generating corresponding data processing models respectively according to each network mode in the use habit, the time period for using each network mode and/or the use period corresponding to the network mode; and configuring a corresponding heartbeat strategy according to the data processing model to obtain a heartbeat keep-alive strategy.
Optionally, the storage medium is further arranged to store program code for performing the steps of: before detecting whether the operation mode of the client device is changed, the method further comprises: sending the heartbeat keep-alive strategy to a server; receiving response information returned by the server, wherein the response information at least comprises the following: whether a capability set of heartbeat keep-alive policies is supported, and/or authentication parameters.
Optionally, the storage medium is further arranged to store program code for performing the steps of: determining a heartbeat strategy corresponding to the changed operation mode in the heartbeat keep-alive strategies configured according to preset conditions, and executing the heartbeat strategy comprises the following steps: matching a heartbeat strategy corresponding to the changed operation mode according to the heartbeat keep-alive strategy; under the condition that the heartbeat strategy corresponding to the running mode before the change is a first heartbeat strategy and the heartbeat strategy corresponding to the running mode after the change is a second heartbeat strategy, switching the first heartbeat strategy to the second heartbeat strategy; a second heartbeat policy is executed.
Further, optionally, the storage medium is further arranged to store program code for performing the steps of: executing the second heartbeat policy includes: executing heartbeat keep-alive operation according to a second heartbeat strategy; sending the second heartbeat policy to a server; and receiving heartbeat keep-alive operation switching response information returned by the server, wherein the heartbeat keep-alive operation switching response information is used for indicating the server to execute the switching operation of the heartbeat keep-alive strategy according to the second heartbeat strategy.
By the invention, whether the operation mode of the client device is changed or not is detected; under the condition that the change of the operation mode is detected, the heartbeat strategy corresponding to the changed operation mode is determined in the heartbeat keep-alive strategies configured according to preset conditions, and the heartbeat strategy is executed, wherein the heartbeat keep-alive strategies are used for indicating the heartbeat strategy corresponding to each operation mode, so that the problem that the flow and the electric quantity consumption of a client are large due to the fact that frequent heartbeat keep-alive is needed between the client and a server in the mobile communication field based on an XMPP protocol can be solved, and the effect of reducing the flow and the electric quantity consumption of the client is achieved.
Drawings
The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the invention and together with the description serve to explain the invention without limiting the invention. In the drawings:
fig. 1 is a block diagram of a hardware structure of a mobile terminal implementing a heartbeat keep-alive method according to an embodiment of the present invention;
FIG. 2 is a flow chart of a method for implementing heartbeat keep-alive according to an embodiment of the invention;
fig. 3 is a block diagram of a device for implementing heartbeat keep-alive according to an embodiment of the present invention;
FIG. 4 is a block diagram of a system for implementing heartbeat keep-alive according to an embodiment of the invention;
FIG. 5 is a flow chart of an XMPP client login server in an implementation system of heartbeat keep-alive according to an embodiment of the present invention;
fig. 6 is a schematic flow diagram of performing heartbeat keep-alive between an XMPP client and a server in an implementation system of heartbeat keep-alive according to a user-defined heartbeat scenario according to an embodiment of the present invention.
Detailed Description
The invention will be described in detail hereinafter with reference to the accompanying drawings in conjunction with embodiments. It should be noted that the embodiments and features of the embodiments in the present application may be combined with each other without conflict.
It should be noted that the terms "first," "second," and the like in the description and claims of the present invention and in the drawings described above are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order.
Example 1
The method embodiment provided by embodiment 1 of the present application may be executed in a mobile terminal, a computer terminal, or a similar computing device. Taking the mobile terminal as an example, fig. 1 is a block diagram of a hardware structure of the mobile terminal of the method for implementing heartbeat keep-alive according to the embodiment of the present invention. As shown in fig. 1, the mobile terminal 10 may include one or more (only one shown) processors 102 (the processor 102 may include, but is not limited to, a processing device such as a microprocessor MCU or a programmable logic device FPGA), a memory 104 for storing data, and a transmitting device 106 for communication functions. It will be understood by those skilled in the art that the structure shown in fig. 1 is only an illustration and is not intended to limit the structure of the electronic device. For example, the mobile terminal 10 may also include more or fewer components than shown in FIG. 1, or have a different configuration than shown in FIG. 1.
The memory 104 can be used to store software programs and modules of application software, such as program instructions/modules corresponding to the implementation method of heartbeat keep alive in the embodiment of the present invention, and the processor 102 executes various functional applications and data processing by running the software programs and modules stored in the memory 104, that is, implementing the method described above. The memory 104 may include high speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 104 may further include memory located remotely from the processor 102, which may be connected to the mobile terminal 10 via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The transmission device 106 is used for receiving or transmitting data via a network. Specific examples of the network described above may include a wireless network provided by a communication provider of the mobile terminal 10. In one example, the transmission device 106 includes a Network adapter (NIC) that can be connected to other Network devices through a base station to communicate with the internet. In one example, the transmission device 106 can be a Radio Frequency (RF) module, which is used to communicate with the internet in a wireless manner.
In this embodiment, a method operating in the mobile terminal is provided, and fig. 2 is a flowchart of a method for implementing heartbeat keep-alive according to an embodiment of the present invention, as shown in fig. 2, the flowchart includes the following steps:
step S202, detecting whether the operation mode of the client device is changed;
and step S204, under the condition that the change of the operation mode is detected, determining a heartbeat strategy corresponding to the changed operation mode in heartbeat keep-alive strategies configured according to preset conditions, and executing the heartbeat strategy, wherein the heartbeat keep-alive strategies are used for indicating the heartbeat strategy corresponding to each operation mode.
In the related technology, in the field of mobile communication, frequent heartbeat keep-alive between an XMPP client and a server causes high flow and electric quantity consumption and also causes certain pressure on the server, and the heartbeat keep-alive is a necessary means for detecting the online state of the other party.
With reference to steps S202 to S204, at the client side, the method for implementing heartbeat keep-alive according to the embodiment of the present application introduces a set of customizable, extensible, adaptive, and visual analysis configuration models based on the extensible property of the XMPP protocol to solve the above problems.
Namely, a dynamic variable heartbeat strategy is made according to the requirements and the use scenes of the client, and the heartbeat keep-alive frequency can be properly improved under the condition that the network environment is good (such as a Wi-Fi environment) or the user needs to use frequently (such as working hours in the daytime), so that the quality of communication service is ensured; and under the condition that the flow is sensitive (for example, mobile data is used) or the use is less (for example, at night), the heartbeat keep-alive frequency is reduced, the client can save the flow and the electric quantity, and the server can relieve the pressure.
The heartbeat keep-alive implementation method provided by the embodiment of the application has the following characteristics:
the method for realizing the heartbeat keep-alive is characterized in that A, a set of analysis configuration models are provided to adapt to the use habits of specific users or the switching of use scenes and other conditions;
b, the heartbeat keep-alive implementation method can dynamically adjust the heartbeat keep-alive frequency according to different scene mode strategies and different time periods;
and C, the implementation method of the heartbeat keep-alive can record various behavior habits of the user and adjust the heartbeat strategy in a self-adaptive mode.
In the method for implementing heartbeat keep-alive provided by the embodiment of the application, whether the operation mode of the client device changes or not is detected; under the condition that the change of the operation mode is detected, the heartbeat strategy corresponding to the changed operation mode is determined in the heartbeat keep-alive strategies configured according to the preset conditions, and the heartbeat strategy is executed, wherein the heartbeat keep-alive strategies are used for indicating the heartbeat strategy corresponding to each operation mode, so that the problem that the flow and the electric quantity consumption of a client are large due to the fact that frequent heartbeat keep-alive is needed between the client and a server in the mobile communication field based on an XMPP protocol can be solved, and the effect of reducing the flow and the electric quantity consumption of the client is achieved.
Optionally, the preset condition includes a configuration condition and/or a usage habit of the user in a preset time period: wherein the configuration condition includes at least one of: each network mode, and the use time and the use frequency corresponding to each network mode; the usage habits include at least one of: each network mode, the time period for using each network mode, and the service cycle corresponding to the network mode.
In the method for implementing heartbeat keep-alive provided by the embodiment of the present application, the way of obtaining the preset condition before configuring the heartbeat keep-alive policy may include receiving a configuration condition manually input by a user, or obtaining, by a client, a use habit of the user in a preset period, and obtaining a corresponding data processing model by obtaining the use habit.
Further, optionally, before detecting whether the operation mode of the client device is changed in step S202, the method for implementing heartbeat keep-alive provided in the embodiment of the present application further includes:
step S200, configuring a heartbeat keep-alive strategy according to preset conditions;
step1, under the condition that the preset condition is the configuration condition, configuring the heartbeat strategy in each operation mode according to each network mode, the corresponding service time and the corresponding service frequency of each network mode respectively to obtain a heartbeat keep-alive strategy;
Wherein, the network mode includes: an operator network or a publicly accessible network; the operation mode is an operation state applied to the configuration condition.
Optionally, the configuring the heartbeat keep-alive policy according to the preset condition in step S200 includes:
step 1', when the preset condition is the use habit, generating corresponding data processing models according to each network mode in the use habit, the time period for using each network mode and/or the use cycle corresponding to the network mode;
step 2', configuring a corresponding heartbeat strategy according to the data processing model to obtain a heartbeat keep-alive strategy.
Optionally, before detecting whether the operation mode of the client device is changed in step S204, the method for implementing heartbeat keep-alive provided in the embodiment of the present application further includes:
step1, sending the heartbeat keep-alive strategy to the server;
step2, receiving response information returned by the server, wherein the response information at least comprises the following: whether a capability set of heartbeat keep-alive policies is supported, and/or authentication parameters.
Optionally, in step S206, determining a heartbeat policy corresponding to the changed operation mode in the heartbeat keep-alive policies configured according to the preset condition, and executing the heartbeat policy includes:
Step1, matching the heartbeat strategy corresponding to the changed operation mode according to the heartbeat keep-alive strategy;
step2, under the condition that the heartbeat strategy corresponding to the running mode before the change is a first heartbeat strategy and the heartbeat strategy corresponding to the running mode after the change is a second heartbeat strategy, switching the first heartbeat strategy to the second heartbeat strategy;
step3, a second heartbeat policy is executed.
Further, optionally, the executing the second heartbeat policy in Step3 in Step S206 includes:
step A, executing heartbeat keep-alive operation according to a second heartbeat strategy;
step B, sending the second heartbeat strategy to a server;
and step C, receiving heartbeat keep-alive operation switching response information returned by the server, wherein the heartbeat keep-alive operation switching response information is used for indicating the server to execute the switching operation of the heartbeat keep-alive strategy according to the second heartbeat strategy.
Through the above description of the embodiments, those skilled in the art can clearly understand that the method according to the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but the former is a better implementation mode in many cases. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which is stored in a storage medium (e.g., ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal device (e.g., a mobile phone, a computer, a server, or a network device) to execute the method according to the embodiments of the present invention.
Example 2
In this embodiment, a device for implementing heartbeat keep-alive is further provided, and the device is used to implement the foregoing embodiments and preferred embodiments, which have already been described and are not described again. As used below, the term "module" may be a combination of software and/or hardware that implements a predetermined function. Although the means described in the embodiments below are preferably implemented in software, an implementation in hardware, or a combination of software and hardware is also possible and contemplated.
Fig. 3 is a block diagram of a structure of an apparatus for implementing heartbeat keep-alive according to an embodiment of the present invention, as shown in fig. 3, the apparatus includes: a detection module 32 and a policy switching module 34, wherein,
a detection module 32, configured to detect whether an operation mode of the client device changes;
and the policy switching module 34 is configured to, when it is detected that the operation mode changes, determine a heartbeat policy corresponding to the changed operation mode from the heartbeat keep-alive policies configured according to preset conditions, and execute the heartbeat policy, where the heartbeat keep-alive policy is used to indicate a heartbeat policy corresponding to each operation mode.
In the apparatus for implementing heartbeat keep-alive provided by the embodiment of the application, because the heartbeat keep-alive strategy is configured according to the preset condition, the heartbeat keep-alive strategy is used for indicating the heartbeat strategy corresponding to each operation mode; detecting whether the operation mode is changed; under the condition that the change of the operation mode is detected, the heartbeat strategy corresponding to the changed operation mode is matched in the heartbeat keep-alive strategies, and the heartbeat strategy is executed, so that the problem that the flow and the electric quantity consumption of a client are large due to the fact that frequent heartbeat keep-alive is needed between the client and a server in the mobile communication field based on an XMPP protocol can be solved, and the effect of reducing the flow and the electric quantity consumption of the client is achieved.
Optionally, the preset condition includes a configuration condition and/or a usage habit of the user within a preset time period: wherein the configuration condition includes at least one of: each network mode, and the use time and the use frequency corresponding to each network mode; usage habits include at least one of: each network mode, the time period for using each network mode, and the service cycle corresponding to the network mode.
Further, optionally, the device for implementing heartbeat keep-alive provided in the embodiment of the present application further includes:
the configuration module is used for configuring a heartbeat keep-alive strategy according to a preset condition before detecting whether the operation mode of the client equipment is changed;
the first configuration unit is used for configuring the heartbeat strategies in each operation mode according to each network mode, the corresponding service time and the corresponding service frequency of each network mode respectively under the condition that the preset condition is the configuration condition, so as to obtain the heartbeat keep-alive strategies; wherein, the network mode includes: an operator network or a publicly accessible network; the operation mode is an operation state applied to the configuration condition.
Optionally, the configuration module includes:
the generation unit is used for respectively generating corresponding data processing models according to each network mode in the use habit, the time period for using each network mode and/or the use period corresponding to the network mode under the condition that the preset condition is the use habit;
And the second configuration unit is used for configuring the corresponding heartbeat strategy according to the data processing model to obtain the heartbeat keep-alive strategy.
Optionally, the apparatus for implementing heartbeat keep-alive provided in this embodiment of the present application further includes:
the sending module is used for sending the heartbeat keep-alive strategy to the server before detecting whether the operation mode of the client device is changed;
a receiving module, configured to receive response information returned by the server, where the response information at least includes the following: whether a capability set of heartbeat keep-alive policies is supported, and/or authentication parameters.
Optionally, the policy switching module 34 includes:
the matching unit is used for matching the heartbeat strategy corresponding to the changed running mode according to the heartbeat keep-alive strategy;
the switching unit is used for switching the first heartbeat strategy to the second heartbeat strategy under the condition that the heartbeat strategy corresponding to the running mode before change is the first heartbeat strategy and the heartbeat strategy corresponding to the running mode after change is the second heartbeat strategy;
and the execution unit is used for executing the second heartbeat strategy.
Further, optionally, the execution unit includes:
the execution subunit is used for executing the heartbeat keep-alive operation according to a second heartbeat strategy;
A sending unit, configured to send the second heartbeat policy to the server;
and the receiving unit is used for receiving heartbeat keep-alive operation switching response information returned by the server, wherein the heartbeat keep-alive operation switching response information is used for indicating the server to execute the switching operation of the heartbeat keep-alive strategy according to the second heartbeat strategy.
It should be noted that, the above modules may be implemented by software or hardware, and for the latter, the following may be implemented, but not limited to: the modules are all positioned in the same processor; alternatively, the modules are respectively located in different processors in any combination.
Example 3
Fig. 4 is a structural block diagram of a system for implementing heartbeat keep-alive according to an embodiment of the present invention, and as shown in fig. 4, the dynamic heartbeat keep-alive system includes: client 42 and server 44, with client 42 communicatively coupled to server 44, wherein,
the client 42 is configured to configure a heartbeat keep-alive strategy according to a preset condition, send the heartbeat keep-alive strategy to the server 44 through a login process, receive response information returned by the server 44 and supporting the heartbeat keep-alive strategy, match a heartbeat strategy corresponding to a changed operation mode in the heartbeat keep-alive strategy when detecting that the operation mode is changed, and execute the heartbeat strategy;
And the server 44 is configured to receive the heartbeat keep-alive policy sent by the client 42, return response information supporting the heartbeat keep-alive policy, and receive a heartbeat policy switching indication sent by the client 42 when the running mode of the client 42 is changed.
Based on the above system, the client 42 and the server 44 in the embodiment of the present application are shown in fig. 4, wherein
The client 42 includes: the system comprises a configuration module, a sensing module, a heartbeat management module and a communication module.
(1) A configuration module: the configuration module is located at the client, and the user needs to configure the heartbeat strategy according to the requirement of the user. For example, it can be divided by network environment, Wi-Fi environment and mobile data environment; the device can be divided into a working mode and a leisure mode according to a use mode; the time periods may be divided into daytime working time periods and nighttime time periods.
(2) A perception module: the configuration module is located at the client, because the user configures heartbeat policies, such as different policies of a Wi-Fi network and a mobile data network, in the configuration module, the daytime working time period and the nighttime time period are different policies, and the switching of the network mode or the time period needs to be notified by relying on the sensing module. For example, a client running on an Android or iOS platform, the underlying operating system may notify the upper layer application of a change in a network mode or a time period, and thus, may be implemented.
(3) A heartbeat management module: the module is located at the client and has the function of dynamically adjusting the heartbeat strategy in real time according to the configuration data of the user (needing to interact with the configuration module) and the notification of the perception module.
(4) A communication module: the module is positioned at the client and is responsible for sending and receiving heartbeat messages with the server.
The concrete improvement is as follows: in the login process, the client 42 extends the XMPP existing protocol in the message of capability negotiation with the server 44, adds a parameter to indicate whether the client 42 supports the "dynamic heartbeat" function, and if the server 44 also supports the "dynamic heartbeat", needs to remember the new characteristics of the client 42 and store the characteristics in the session context with the client 42. For the client 42, the user can configure the heartbeat policy, and can configure the policy according to a network scenario, for example, in a Wi-Fi scenario, heartbeat keep-alive is performed at 10 second intervals, and a mobile data scenario is performed at 30 second intervals; or configured according to time periods, such as heartbeat keep alive at 10 second intervals during the day and keep alive at 30 second intervals during the night.
Furthermore, since the heartbeat is bi-directional, server 44 will also initiate a heartbeat to the client, so the heartbeat policy configured at client 42 needs to be synchronized to server 44. Therefore, the heartbeat message between the client 42 and the server 44 also needs to be extended, a parameter is added to the XMPP Ping message to indicate the heartbeat frequency currently in use, and a "heartbeat management module" is added to the server 44, and is responsible for initiating a heartbeat keep-alive procedure to the client 42 at the same frequency, and the current heartbeat parameter needs to be saved in the context associated with the client 42.
Based on the above, the client 42 in the dynamic heartbeat keep-alive system provided in the embodiment of the present application provides a set of customizable, extensible, adaptive, and visual configuration models; by extending the XMPP protocol, the cooperative work of the client 42 and the server 44 is realized, and the heartbeat strategy is synchronously changed in real time.
Wherein, the flow of the client 42 in the process of implementing dynamic heartbeat keep-alive is as follows:
the XMPP client first logs in the server 44, and then initiates a login process, see fig. 5, including a complete login process;
wherein, the second stream pair message in the flow is used as capability agreement, and the message is extended, and an attribute parameter is added in the featureset, for example, "dynamic heartbeat" indicates that the server 44 supports the "dynamic heartbeat" function at the client 42;
when the server 44 and the client 42 perform capability negotiation, and the client 42 is found to support the "dynamic heartbeat" function, the feature is saved in the context session with the client 42;
at the client 42, a user can configure parameters such as a heartbeat strategy, a scene mode, heartbeat interval time and the like autonomously;
the client 42 initiates a heartbeat keep-alive request to the server 44 according to the current heartbeat policy, see fig. 6, for example, the current network environment is Wi-Fi, and the client 42 initiates heartbeat keep-alive to the server 44 at the configured 10 second interval;
When the client 42 detects that the network environment is switched to the mobile data mode in real time, the client 42 initiates heartbeat keep-alive to the server 44 according to a 30-second interval configured in advance by the user;
wherein during daytime operation, the client 42 is frequently used, and initiates heartbeat keep-alive to the server 44 at 10 second intervals configured by the user;
at night, the client 42 switches to the configured 30-second interval according to the change of the current time and initiates heartbeat keep-alive to the server 44;
with the above method, the server 44 needs to support the "dynamic heartbeat" function, and when performing capability negotiation with the client 42, the featuremessages is extended, and an attribute, such as "dynamic heartbeat", is added to indicate that the server 44 supports the "dynamic heartbeat" function, and it needs to be able to store the current heartbeat frequency of each session.
The client 42 needs to support a "dynamic heartbeat" function, and a user can configure parameters such as a heartbeat policy, a scene mode, and a heartbeat interval time autonomously.
In summary, in the dynamic heartbeat keep-alive system provided in the embodiment of the present application, in a scene where the flow is sensitive or in a standby state, a user can reduce the heartbeat keep-alive frequency through configuration, and the purposes of reducing the flow and saving the electric quantity at the client are achieved. In addition, under the Wi-Fi environment or the condition that the user needs to use frequently, the user can improve heartbeat keep-alive frequency through configuration, and better communication experience is brought.
Fig. 4 shows a typical application scenario, where an XMPP client first logs in to a server, the server establishes a corresponding session data area for each client, and messages sent by the client are forwarded to another client through the server, which is also based on the XMPP protocol.
In order to support the dynamic heartbeat function, the client has the following modules which need to be added or modified: the system comprises a configuration module, a sensing module, a heartbeat management module and a communication module. The user firstly configures the heartbeat strategy in the configuration module, and the sensing module informs the heartbeat management module in real time when the condition that the network mode or the time period needs to be switched is met. And secondly, the heartbeat management module decides the currently applicable heartbeat strategy according to the data of the configuration module and the notification of the sensing module, and then triggers the communication module to keep the heartbeat alive with the server.
The modules of the server which need to be added or modified are as follows: a heartbeat management module and a communication module. And after receiving the heartbeat strategy synchronized by the client, the heartbeat management module changes the heartbeat of the server in real time.
Here, fig. 5 shows the process of client 42 logging into server 44, where STREAM functions like querying server 44, and server 44 returns the characteristics of server 44 to client 42, such as SASL policy, iq-auth, zlib compression, xmpp-bind, etc. In the second pair of STREAM messages, server 44 may extend the FEATURESs field to add a "dynamic heartbeat" parameter to inform server 44 that client 42 supports the "dynamic heartbeat" function.
Fig. 6 shows a process of conducting heartbeat keep-alive between the XMPP client 42 and the server 44 according to a heartbeat scenario defined by a user, where the client 42 needs to support various scenario modes of "dynamic heartbeat" configured by the user and a corresponding heartbeat interval, and the client 42 adjusts the heartbeat interval in real time according to a current usage scenario (a network state, a time period, etc.), and conducts a keep-alive process with the server 44.
Taking the example of fig. 5, the user configures the heartbeat policy as follows: in the working period of the day, the heartbeat frequency of the Wi-Fi network is 10 seconds, the mobile data network is 30 seconds, and in the night period, the heartbeat frequency of the Wi-Fi network is 60 seconds no matter what network is. Firstly, in the daytime, the client sends heartbeat messages to the server at the heartbeat frequency of 10 seconds, if the client is switched to the mobile data network, the sensing module informs the heartbeat management module at the first time, the heartbeat management module acquires the user configuration data for 30 seconds, and immediately controls the communication module to change the heartbeat frequency to 30 seconds. And when entering a night time period (the night time period configured by the user), the sensing module also informs the heartbeat management module, the heartbeat management module acquires the user configuration data for 60 seconds, and immediately controls the communication module to change the heartbeat frequency into the heartbeat frequency of 60 seconds.
Example 4
The embodiment of the invention also provides a storage medium. Alternatively, in this embodiment, the storage medium may be configured to store program codes for performing the following steps:
s1, detecting whether the operation mode of the client device is changed;
s2, under the condition that the operation mode is detected to be changed, determining a heartbeat strategy corresponding to the changed operation mode in heartbeat keep-alive strategies configured according to preset conditions, and executing the heartbeat strategy, wherein the heartbeat keep-alive strategies are used for indicating the heartbeat strategy corresponding to each operation mode.
Optionally, the storage medium is further arranged to store program code for performing the steps of:
s1, before detecting whether the operation mode of the client device is changed, the method further includes: configuring a heartbeat keep-alive strategy according to preset conditions; under the condition that the preset condition is the configuration condition, respectively configuring heartbeat strategies in each operation mode according to each network mode, the corresponding service time and the corresponding service frequency of each network mode to obtain heartbeat keep-alive strategies; wherein, the network mode includes: an operator network or a publicly accessible network; the operation mode is an operation state applied to the configuration condition.
Optionally, in this embodiment, the storage medium may include, but is not limited to: a U-disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a removable hard disk, a magnetic or optical disk, and other various media capable of storing program codes.
Optionally, in this embodiment, the configuring, by the processor, the heartbeat keep-alive policy according to a preset condition according to the program code stored in the storage medium includes: under the condition that the preset condition is the use habit, generating corresponding data processing models respectively according to each network mode in the use habit, the time period for using each network mode and/or the use period corresponding to the network mode; and configuring a corresponding heartbeat strategy according to the data processing model to obtain a heartbeat keep-alive strategy.
Optionally, in this embodiment, before the processor executes, according to program codes stored in the storage medium, to detect whether the operation mode of the client device changes, the method further includes: sending the heartbeat keep-alive strategy to a server; receiving response information returned by the server, wherein the response information at least comprises the following information: whether a capability set of heartbeat keep-alive policies is supported, and/or authentication parameters.
Optionally, in this embodiment, the executing, by the processor according to the program code stored in the storage medium, a heartbeat policy corresponding to the changed operation mode in the heartbeat keep-alive policies configured according to the preset condition, and the executing the heartbeat policy includes: matching a heartbeat strategy corresponding to the changed running mode according to the heartbeat keep-alive strategy; under the condition that the heartbeat strategy corresponding to the running mode before the change is a first heartbeat strategy and the heartbeat strategy corresponding to the running mode after the change is a second heartbeat strategy, switching the first heartbeat strategy to the second heartbeat strategy; a second heartbeat policy is executed.
Optionally, in this embodiment, the executing, by the processor, the second heartbeat policy according to the program code stored in the storage medium includes: executing heartbeat keep-alive operation according to a second heartbeat strategy; sending the second heartbeat policy to a server; and receiving heartbeat keep-alive operation switching response information returned by the server, wherein the heartbeat keep-alive operation switching response information is used for indicating the server to execute switching operation of the heartbeat keep-alive strategy according to the second heartbeat strategy.
Optionally, for a specific example in this embodiment, reference may be made to the examples described in the above embodiment and optional implementation, and this embodiment is not described herein again.
It will be apparent to those skilled in the art that the modules or steps of the present invention described above may be implemented by a general purpose computing device, they may be centralized in a single computing device or distributed across a network of multiple computing devices, and alternatively, they may be implemented by program code executable by a computing device, such that they may be stored in a memory device and executed by a computing device, and in some cases, the steps shown or described may be executed out of order, or separately as individual integrated circuit modules, or multiple modules or steps thereof may be implemented as a single integrated circuit module. Thus, the present invention is not limited to any specific combination of hardware and software.
The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
Claims (13)
1. A method for realizing heartbeat keep-alive is characterized by comprising the following steps:
Detecting whether the operation mode of the client device is changed;
under the condition that the operation mode is detected to be changed, determining a heartbeat strategy corresponding to the changed operation mode in heartbeat keep-alive strategies configured according to preset conditions, and executing the heartbeat strategy, wherein the heartbeat keep-alive strategies are used for indicating the heartbeat strategy corresponding to each operation mode;
the preset conditions comprise configuration conditions and use habits of a user in a preset time period:
the configuration conditions are the use time and the use frequency corresponding to each network mode;
the using habit is a time period for using each network mode and a using period corresponding to the network mode.
2. The method of claim 1, wherein prior to detecting whether the operating mode of the client device has changed, the method further comprises:
configuring a heartbeat keep-alive strategy according to preset conditions;
under the condition that the preset condition is the configuration condition, configuring heartbeat strategies in each operation mode according to the use time and the use frequency corresponding to each network mode respectively to obtain the heartbeat keep-alive strategies;
Wherein the network mode comprises: an operator network or a publicly accessible network; the operation mode is an operation state applied to the configuration condition.
3. The method of claim 2, wherein configuring the heartbeat keep-alive strategy according to a preset condition comprises:
under the condition that the preset condition is the use habit, generating corresponding data processing models respectively according to the time periods of using each network mode in the use habit and/or the use cycles corresponding to the network modes;
and configuring a corresponding heartbeat strategy according to the data processing model to obtain the heartbeat keep-alive strategy.
4. The method of claim 1, wherein prior to the detecting whether the operating mode of the client device has changed, the method further comprises:
sending the heartbeat keep-alive strategy to a server;
receiving response information returned by the server, wherein the response information at least comprises the following information: whether to support a capability set of the heartbeat keep-alive policy, and/or an authentication parameter.
5. The method according to any one of claims 1 to 4, wherein determining a heartbeat policy corresponding to the changed operation mode among heartbeat keep-alive policies configured according to a preset condition, and executing the heartbeat policy comprises:
Matching the heartbeat strategy corresponding to the changed running mode according to the heartbeat keep-alive strategy;
under the condition that the heartbeat strategy corresponding to the running mode before change is a first heartbeat strategy and the heartbeat strategy corresponding to the running mode after change is a second heartbeat strategy, switching the first heartbeat strategy to the second heartbeat strategy;
executing the second heartbeat policy.
6. The method of claim 5, wherein the executing the second heartbeat policy comprises:
executing heartbeat keep-alive operation according to the second heartbeat strategy;
sending the second heartbeat policy to a server;
and receiving heartbeat keep-alive operation switching response information returned by the server, wherein the heartbeat keep-alive operation switching response information is used for indicating that the server executes the switching operation of the heartbeat keep-alive strategy according to the second heartbeat strategy.
7. A heartbeat keep-alive implementing device is characterized by comprising:
the detection module is used for detecting whether the operation mode of the client equipment is changed;
the strategy switching module is used for determining a heartbeat strategy corresponding to the changed operation mode in heartbeat keep-alive strategies configured according to preset conditions under the condition that the operation mode is detected to be changed, and executing the heartbeat strategy, wherein the heartbeat keep-alive strategies are used for indicating the heartbeat strategy corresponding to each operation mode;
The preset conditions comprise configuration conditions and use habits of a user in a preset time period:
the configuration conditions are the use time and the use frequency corresponding to each network mode;
the using habit is a time period for using each network mode, and a using period corresponding to the network mode.
8. The apparatus of claim 7, further comprising:
the configuration module is used for configuring a heartbeat keep-alive strategy according to preset conditions before detecting whether the operation mode of the client equipment is changed;
the first configuration unit is configured to configure heartbeat strategies in each operation mode according to the use time and the use frequency corresponding to each network mode respectively to obtain the heartbeat keep-alive strategies when the preset condition is the configuration condition;
wherein the network mode comprises: an operator network or a publicly accessible network; the operation mode is an operation state applied to the configuration condition.
9. The apparatus of claim 8, wherein the configuration module comprises:
a generating unit, configured to generate, when the preset condition is the usage habit, a corresponding data processing model according to the time period for using each network mode in the usage habit and/or a usage cycle corresponding to the network mode, respectively;
And the second configuration unit is used for configuring a corresponding heartbeat strategy according to the data processing model to obtain the heartbeat keep-alive strategy.
10. The apparatus of claim 7, further comprising:
the sending module is used for sending the heartbeat keep-alive strategy to a server before the operation mode of the client equipment is detected to be changed;
a receiving module, configured to receive response information returned by the server, where the response information at least includes the following: whether to support a capability set of the heartbeat keep-alive policy, and/or an authentication parameter.
11. The apparatus according to any one of claims 7 to 10, wherein the policy switching module comprises:
the matching unit is used for matching the heartbeat strategy corresponding to the changed operation mode according to the heartbeat keep-alive strategy;
the switching unit is used for switching the first heartbeat strategy to the second heartbeat strategy under the condition that the heartbeat strategy corresponding to the running mode before change is a first heartbeat strategy and the heartbeat strategy corresponding to the running mode after change is a second heartbeat strategy;
and the execution unit is used for executing the second heartbeat strategy.
12. The apparatus of claim 11, wherein the execution unit comprises:
the execution subunit is used for executing the heartbeat keep-alive operation according to the second heartbeat strategy;
a sending unit, configured to send the second heartbeat policy to a server;
and the receiving unit is used for receiving heartbeat keep-alive operation switching response information returned by the server, wherein the heartbeat keep-alive operation switching response information is used for indicating the server to execute the switching operation of the heartbeat keep-alive strategy according to the second heartbeat strategy.
13. A heartbeat keep-alive implementation system, comprising: a client and a server, the client communicatively coupled to the server, wherein,
the client is used for configuring a heartbeat keep-alive strategy according to preset conditions, sending the heartbeat keep-alive strategy to the server through a login process, receiving response information returned by the server and supporting the heartbeat keep-alive strategy, matching the heartbeat strategy corresponding to the changed operation mode in the heartbeat keep-alive strategy under the condition that the operation mode is detected to be changed, and executing the heartbeat strategy;
The server is used for receiving the heartbeat keep-alive strategy sent by the client, returning response information supporting the heartbeat keep-alive strategy and receiving a heartbeat strategy switching instruction sent by the client under the condition that the running mode of the client is changed;
the preset conditions comprise configuration conditions and use habits of a user in a preset time period:
the configuration conditions are the use time and the use frequency corresponding to each network mode;
the using habit is a time period for using each network mode, and a using period corresponding to the network mode.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610427724.3A CN107517136B (en) | 2016-06-16 | 2016-06-16 | Method, device and system for realizing heartbeat keep-alive |
| PCT/CN2017/088300 WO2017215614A1 (en) | 2016-06-16 | 2017-06-14 | Method, device and system for realising heart beat keepalive |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610427724.3A CN107517136B (en) | 2016-06-16 | 2016-06-16 | Method, device and system for realizing heartbeat keep-alive |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107517136A CN107517136A (en) | 2017-12-26 |
| CN107517136B true CN107517136B (en) | 2022-08-16 |
Family
ID=60663345
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610427724.3A Active CN107517136B (en) | 2016-06-16 | 2016-06-16 | Method, device and system for realizing heartbeat keep-alive |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN107517136B (en) |
| WO (1) | WO2017215614A1 (en) |
Families Citing this family (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108390910B (en) * | 2018-01-17 | 2021-03-16 | 吉浦斯信息咨询（深圳）有限公司 | Power saving method and device for pushing SDK and computer readable medium |
| CN109327346A (en) * | 2018-07-27 | 2019-02-12 | 上海电享信息科技有限公司 | A kind of client palmic rate dynamic control method and system |
| CN110755061A (en) * | 2018-07-27 | 2020-02-07 | 九阳股份有限公司 | Heartbeat detection method of household appliance and household appliance |
| CN110943875A (en) * | 2018-09-21 | 2020-03-31 | 武汉安天信息技术有限责任公司 | User network relation determining method, network-based user mutual relation determining method and related device |
| CN109347929B (en) * | 2018-09-27 | 2023-08-22 | 中国平安人寿保险股份有限公司 | Heartbeat simulation detection method and device based on lightweight interface and storage medium |
| CN110753086A (en) * | 2019-09-12 | 2020-02-04 | 华为技术有限公司 | Heartbeat awakening method for application and terminal equipment |
| CN110868742A (en) * | 2019-11-22 | 2020-03-06 | 上海商米科技集团股份有限公司 | Network switching method and device |
| CN111083665B (en) * | 2019-12-05 | 2023-09-19 | 上海旗旌科技有限公司 | Method and equipment for double-master control interactive communication |
| CN111556555A (en) * | 2020-04-29 | 2020-08-18 | 杭州涂鸦信息技术有限公司 | Low-power-consumption keep-alive method and system for network camera and gateway |
| CN112039894B (en) * | 2020-08-31 | 2023-01-10 | 北京天融信网络安全技术有限公司 | Network access control method, device, storage medium and electronic equipment |
| CN112311629B (en) * | 2020-10-30 | 2022-04-26 | 广州华多网络科技有限公司 | Data processing method, device, server and computer readable storage medium |
| CN112448851A (en) * | 2020-11-20 | 2021-03-05 | 天翼电子商务有限公司 | Elastic heart rate communication design method of distributed system |
| CN114697377B (en) * | 2022-04-07 | 2023-09-05 | 深信服科技股份有限公司 | Keep-alive method, keep-alive system, keep-alive device and readable storage medium for client products |
| CN117336213B (en) * | 2023-12-01 | 2024-02-27 | 四川才子软件信息网络有限公司 | Subsystem monitoring method, system and equipment |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103581950A (en) * | 2013-11-15 | 2014-02-12 | 中国联合网络通信集团有限公司 | Electronic device and heartbeat message transmitting method and system |
| CN104468187A (en) * | 2014-10-27 | 2015-03-25 | 百度在线网络技术（北京）有限公司 | Heartbeat cycle acquisition method and device |
Family Cites Families (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8731542B2 (en) * | 2005-08-11 | 2014-05-20 | Seven Networks International Oy | Dynamic adjustment of keep-alive message intervals in a mobile network |
| CN102843250B (en) * | 2011-06-21 | 2018-01-19 | 中兴通讯股份有限公司 | The adaptive approach and device of a kind of heart beat cycle |
| CN104135460B (en) * | 2013-05-03 | 2017-11-24 | 华为软件技术有限公司 | A kind of push channel keepalive method and push server |
| CN104243719B (en) * | 2013-06-08 | 2017-09-01 | 中国移动通信集团公司 | The heart beat cycle of long connection determines mthods, systems and devices in mobile communications network |
| CN104703146B (en) * | 2013-12-09 | 2019-03-08 | 腾讯科技（深圳）有限公司 | Information-pushing method, client and system |
| CN104144159B (en) * | 2014-06-26 | 2016-04-13 | 腾讯科技（深圳）有限公司 | Intelligent heartbeat keepalive method and intelligent heartbeat keep-alive system |
| CN104333465B (en) * | 2014-10-31 | 2019-06-11 | 北京奇安信科技有限公司 | A kind of method, apparatus and system of eartbeat interval setting |
| CN105610913A (en) * | 2015-12-22 | 2016-05-25 | 用友网络科技股份有限公司 | Heartbeat keep-alive method and apparatus for long connection in communication network |
-
2016
- 2016-06-16 CN CN201610427724.3A patent/CN107517136B/en active Active
-
2017
- 2017-06-14 WO PCT/CN2017/088300 patent/WO2017215614A1/en active Application Filing
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103581950A (en) * | 2013-11-15 | 2014-02-12 | 中国联合网络通信集团有限公司 | Electronic device and heartbeat message transmitting method and system |
| CN104468187A (en) * | 2014-10-27 | 2015-03-25 | 百度在线网络技术（北京）有限公司 | Heartbeat cycle acquisition method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107517136A (en) | 2017-12-26 |
| WO2017215614A1 (en) | 2017-12-21 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107517136B (en) | Method, device and system for realizing heartbeat keep-alive | |
| EP3550892B1 (en) | Method for network slice selection, user equipment, and network device | |
| CN113596937B (en) | Communication method and system of wearable device and related device | |
| CN110474975B (en) | Heartbeat processing method and device of application program, electronic equipment and storage medium | |
| JP6226348B2 (en) | Method for transmitting heartbeat message and portable terminal | |
| CN106851799B (en) | Method and device for sending heartbeat packet in long connection | |
| KR20160060723A (en) | Service agent method, modem and terminal | |
| CN108712485A (en) | A kind of resource subscription method and apparatus of internet of things equipment | |
| CN105451216A (en) | Multimode dual-card terminal SIM card switching method and multimode dual-card terminal device | |
| CN109150808B (en) | Communication method, device and system | |
| CN104469970B (en) | A kind of method and apparatus reconnecting data network | |
| CN110691398B (en) | Network interaction method, system, equipment and storage medium of intelligent equipment | |
| CN112671904B (en) | Method and device for transmitting equipment state information, storage medium and electronic device | |
| CN106851790B (en) | Power consumption change control method and system and mobile terminal | |
| EP3073681A1 (en) | Social network information pushing method and apparatus | |
| US20210409149A1 (en) | Method and device for transmitting data, system, and storage medium | |
| CN113965904A (en) | Device registration method, device and storage medium | |
| CN109245974A (en) | Household electrical appliance distribution method, apparatus and computer readable storage medium | |
| CN114286431B (en) | Method and device for starting low-power mode, storage medium and electronic device | |
| CN105101295B (en) | A kind of heartbeat message sending method and device | |
| CN114125023B (en) | Method and device for determining data connection, storage medium and electronic device | |
| US20220109607A1 (en) | Customer premises equipment configuration management method and apparatus | |
| CN111105789A (en) | Awakening word obtaining method and device | |
| CN112491583A (en) | Data acquisition and analysis method and device | |
| CN107872824B (en) | Wireless service processing method, device, equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| 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 |