CN109391656B - Method and device for recovering equipment management session, client and server - Google Patents
Method and device for recovering equipment management session, client and server Download PDFInfo
- Publication number
- CN109391656B CN109391656B CN201710676037.XA CN201710676037A CN109391656B CN 109391656 B CN109391656 B CN 109391656B CN 201710676037 A CN201710676037 A CN 201710676037A CN 109391656 B CN109391656 B CN 109391656B
- Authority
- CN
- China
- Prior art keywords
- session
- data packet
- recovery
- execution result
- client
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
- H04L67/146—Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer And Data Communications (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention provides a method, a device, a client and a server for recovering an equipment management session, which relate to the technical field of open mobile alliance equipment management, and the method comprises the following steps: generating a session recovery data packet for recovering a first session of device management, the session recovery data packet including an execution command status and an execution result of the first session; saving the session recovery data packet and reporting to a server; and receiving a management command data packet of the recovery flow of the first session, which is sent by the server. The scheme of the invention realizes the recovery of the interruption in the equipment management session under any condition, reduces the flow consumption of repeated sessions, reduces the consumption of dynamic resources when the server waits, accelerates the whole management process of the equipment management session and reduces the management pressure of the server.
Description
Technical Field
The present invention belongs to the technical field of Open Mobile Alliance (OMA) Device Management (DM), and in particular, to a method, an apparatus, a client and a server for recovering a Device Management session.
Background
In an actual DM session interaction process, process interruption due to various reasons often occurs, such as device restart, network exception, and the like, after interruption, a client or a server may resume the session process by retrying a connection, but no matter the server or the client, in order to avoid resource consumption caused by waiting for a certain session flow for a long time, a session waiting time is generally set, and once the time is exceeded, the entire process is ended. In particular, since the number of devices to be managed is generally large on the server side, it is impossible to set an excessively long waiting time for one management task, and even if the client retries connection after a timeout, the server cannot continue an incomplete management task. So that a new management task can only be reinitiated once, which results in many unnecessary or repeated interaction processes. For example: the server needs to collect applications installed at the client currently, when the terminal has many installed software, the client needs to divide the data into multiple packets and transmit the packets to the server, once a long time of interruption occurs in the interaction process, the server can only restart the collection task, the client can only report the installed application data from the beginning, the previously reported data can only be reported repeatedly, and the traffic waste is caused.
Disclosure of Invention
The invention aims to provide a method, a device, a client and a server for recovering a device management session, so that the problem that the device management session needs to be restarted after the device management session is interrupted, and a plurality of unnecessary or repeated interactive processes are caused is solved.
In order to achieve the above object, an embodiment of the present invention provides a method for recovering a device management session, which is applied to a client side, and the method includes:
generating a session recovery data packet for recovering a first session of device management, the session recovery data packet including an execution command status and an execution result of the first session;
saving the session recovery data packet and reporting to a server;
and receiving a management command data packet of the recovery flow of the first session, which is sent by the server.
Wherein, prior to generating a session recovery packet for recovering the first session of device management, the method further comprises:
receiving a management command data packet sent by a server in a first session managed by equipment;
executing the management command data packet, and storing an execution result data packet of the first session generated when the management command data packet is executed; wherein the execution result packet includes: a first session ID of the first session, and an execution command status and an execution result of the first session;
sending the execution result data packet to a server;
and deleting the execution result data packet after receiving the confirmation data packet of the execution result data packet sent by the server.
Wherein, prior to generating a session recovery packet for recovering the first session of device management, the method further comprises:
receiving a notification message which is sent by a server in a second session managed by the equipment and used for indicating the recovery of the first session; wherein the notification message comprises: first flow recovery flag information, a first session ID of the first session, and a second session ID of the second session;
wherein the step of generating a session recovery packet for recovering the first session of the device management comprises:
judging whether the first session can be recovered or not according to the first session ID; and if so, generating the session recovery data packet according to the first flow mark information, the second session ID, the execution command state and the execution result of the first session.
Wherein the step of determining whether the first session can be resumed comprises:
and if the execution result data packet containing the first session ID can be acquired, judging that the first session can be recovered, otherwise, not recovering the first session.
Wherein the step of generating a session recovery data packet for a first session of device management comprises:
judging whether a first session managed by the equipment is interrupted or not;
when the first session is determined to be interrupted, judging whether an initiator of the first session is a client or not;
when the initiator of the first session is determined to be the client, acquiring an execution result data packet of the first session;
initiating a third session and generating a session recovery packet for indicating recovery of the first session, the session recovery packet including an execution result packet of the first session, second process recovery flag information, and a third session ID of the third session.
Wherein the step of judging whether the first session managed by the device is interrupted comprises:
and if the confirmation data packet is not received within the preset time after the execution result data packet of the first session is reported, or if the ending data packet is not received within the preset time after the execution result data packet of the first session is reported, determining that the first session is interrupted.
The embodiment of the invention also provides a method for recovering the equipment management session, which is applied to the server side and comprises the following steps:
receiving a session recovery data packet which is sent by a client and used for recovering a first session of equipment management, wherein the session recovery data packet comprises an execution command state and an execution result of the first session;
and sending a management command data packet of the first session recovery flow according to the session recovery data packet.
Before receiving a session recovery packet sent by a client for recovering a first session of device management, the method further includes:
receiving an execution result data packet of a first session reported by a client, wherein the execution result data packet comprises: a first session ID of the first session, and an execution command status and an execution result of the first session;
saving an execution result data packet of a first session, and deleting a management command which is successfully executed currently from unexecuted commands of the first session according to the execution command state and the execution result of the first session;
and judging whether the first session has an unexecuted management command, if so, sending a management command data packet of the unexecuted management command, and if not, sending an end data packet of the first session.
Wherein, the step of receiving a session recovery packet for recovering the first session managed by the device sent by the client comprises:
receiving a session recovery data packet of the first session, which is reported by the client in the second session and used for indicating the recovery equipment to manage; wherein the session recovery packet comprises: first flow recovery flag information, a second session ID of the second session, and an execution result packet of the first session.
Wherein, the step of sending the management command data packet of the first session recovery flow according to the session recovery data packet comprises:
judging whether the first session can be recovered or not according to the ID of the first session; if yes, acquiring an unexecuted management command in the first session according to the first session ID;
acquiring a management command data packet of the first session recovery flow according to the unexecuted management command in the first session and the ID of the second session;
and sending the management command data packet of the first session recovery flow to the client in the second session.
Wherein, before the step of receiving a session recovery packet for recovering the first session of device management sent by the client, the method further comprises:
judging whether a first session managed by the equipment is interrupted or not;
when the first session is determined to be interrupted, judging whether an initiator of the first session is a server or not;
when the initiator of the first session is determined to be a server, acquiring an unexecuted management command in the first session;
initiating a third session and generating a notification message for indicating recovery of the first session, wherein the notification message comprises a first session ID of the first session, a third session ID of the third session, and second flow recovery flag information;
and sending the notification message to the client.
Wherein the step of judging whether the first session managed by the device is interrupted comprises:
and determining that the first session is interrupted when an execution result data packet corresponding to the management command data packet sent by the client is not received within a preset time length after the management command data packet of the first session is sent.
Wherein, the step of sending the management command data packet of the first session recovery flow according to the session recovery data packet comprises:
acquiring a management command data packet of the first session recovery flow according to the unexecuted management command in the first session and the third session ID;
and sending the management command data packet of the first session recovery flow to the client in the third session.
An embodiment of the present invention further provides a device for recovering a device management session, which is applied to a client side, and the device includes:
the device management system comprises a generation module, a processing module and a processing module, wherein the generation module is used for generating a session recovery data packet for recovering a first session managed by equipment, and the session recovery data packet comprises an execution command state and an execution result of the first session;
the storage module is used for storing the session recovery data packet and reporting the session recovery data packet to a server;
and the first receiving module is used for receiving a management command data packet of the recovery process of the first session, which is sent by the server.
Wherein the apparatus further comprises:
the second receiving module is used for receiving a management command data packet sent by the server in the first session managed by the equipment;
the execution module is used for executing the management command data packet and storing an execution result data packet of the first session generated when the management command data packet is executed; wherein the execution result packet includes: a first session ID of the first session, and an execution command status and an execution result of the first session;
the sending module is used for sending the execution result data packet to a server;
and the deleting module is used for deleting the execution result data packet after receiving the confirmation data packet of the execution result data packet sent by the server.
Wherein the apparatus further comprises:
a third receiving module, configured to receive a notification message sent by a server in a second session of device management and used to instruct to resume the first session; wherein the notification message comprises: first flow recovery flag information, a first session ID of the first session, and a second session ID of the second session;
wherein the generating module comprises:
a first judging submodule, configured to judge whether the first session can be recovered according to the first session ID; and if so, generating the session recovery data packet according to the first flow mark information, the second session ID, the execution command state and the execution result of the first session.
Wherein the first judgment sub-module includes:
and the judging unit is used for judging that the first session can be recovered if the execution result data packet containing the first session ID can be obtained, and otherwise, the first session cannot be recovered.
Wherein the generating module comprises:
the second judgment submodule is used for judging whether the first session managed by the equipment is interrupted or not;
a third judging submodule, configured to judge whether an initiator of the first session is a client when it is determined that the first session is interrupted;
the obtaining submodule is used for obtaining an execution result data packet of the first session when the initiator of the first session is determined to be the client;
and the triggering module is used for initiating a third session and generating a session recovery data packet for indicating recovery of the first session, wherein the session recovery data packet comprises an execution result data packet of the first session, second process recovery flag information and a third session ID of the third session.
Wherein the second judgment sub-module includes:
and a determining unit, configured to determine that the first session is interrupted when no acknowledgement packet is received within a preset time period after reporting the execution result packet of the first session, or determine that the first session is interrupted when an end packet is not received within a preset time period after reporting the execution result packet of the first session.
The embodiment of the invention also provides a client, which comprises a memory, a processor and a computer program which is stored on the memory and can run on the processor; wherein the processor implements the method as described above when executing the program.
Embodiments of the present invention also provide a computer-readable storage medium, on which a computer program is stored, where the program, when executed by a processor, implements the steps in the method as described above.
The embodiment of the present invention further provides a device for recovering a device management session, which is applied to a server side, wherein the device includes:
the device management system comprises a first receiving module, a second receiving module and a processing module, wherein the first receiving module is used for receiving a session recovery data packet which is sent by a client and used for recovering a first session managed by equipment, and the session recovery data packet comprises an execution command state and an execution result of the first session;
and the first sending module is used for sending the management command data packet of the first session recovery flow according to the session recovery data packet.
Wherein the apparatus further comprises:
a second receiving module, configured to receive an execution result data packet of the first session, where the execution result data packet includes: a first session ID of the first session, and an execution command status and an execution result of the first session.
The storage module is used for storing an execution result data packet of the first session and deleting the management command which is successfully executed currently from the unexecuted command of the first session according to the execution command state and the execution result of the first session;
the first judging module is used for judging whether the first session has an unexecuted management command, if so, sending a management command data packet of the unexecuted management command, and if not, sending an end data packet of the first session.
Wherein the first receiving module comprises:
the receiving submodule is used for receiving a session recovery data packet which is reported by the client in the second session and is used for indicating the first session managed by the recovery equipment; wherein the session recovery packet comprises: first flow recovery flag information, a second session ID of the second session, and an execution result packet of the first session.
Wherein the first transmitting module comprises:
a first judgment sub-module: the first session ID is used for judging whether the first session can be recovered or not; if yes, acquiring an unexecuted management command in the first session according to the first session ID;
a first obtaining sub-module, configured to obtain a management command data packet of the first session recovery flow according to an unexecuted management command in the first session and the second session ID;
and the first sending submodule is used for sending the management command data packet of the first session recovery flow to the client in the second session.
Wherein the apparatus further comprises:
the second judgment module is used for judging whether the first session managed by the equipment is interrupted or not;
a first obtaining module, configured to obtain an unexecuted management command in the first session when it is determined that an initiator of the first session is a server;
the trigger module is used for initiating a third session and generating a notification message for indicating the recovery of the first session, wherein the notification message comprises a first session ID of the first session, a third session ID of the third session and second flow recovery flag information;
and the second sending module is used for sending the notification message to the client.
Wherein the second judging module comprises:
and the determining submodule is used for determining that the first session is interrupted when an execution result data packet corresponding to the management command data packet sent by the client is not received within a preset time length after the management command data packet of the first session is sent.
Wherein the first transmitting module comprises:
a second obtaining sub-module, configured to obtain, according to the unexecuted management command in the first session and the third session ID, a management command data packet of the first session recovery flow;
and the second sending submodule is used for sending the management command data packet of the first session recovery flow to the client in a third session.
The embodiment of the invention also provides a server, which comprises a memory, a processor and a computer program which is stored on the memory and can run on the processor; wherein the processor implements the method as described above when executing the program.
Embodiments of the present invention also provide a computer-readable storage medium, on which a computer program is stored, where the program, when executed by a processor, implements the steps in the method as described above.
The technical scheme of the invention at least has the following beneficial effects:
the embodiment of the invention saves the sent and received data packets in the process of the equipment management session, and restores the equipment management session by establishing a new session flow according to the saved data packets when the equipment management session is interrupted, thereby avoiding the traffic consumption caused by re-execution of the executed management command in the equipment management session; the embodiment of the invention can recover any interruption condition of the equipment management session without retry, thereby reducing the consumption of dynamic resources when the server waits; in addition, the recovery mechanism of the embodiment of the invention can complete the whole session process more quickly and reduce the management pressure of the server.
Drawings
Fig. 1 is a basic diagram of a recovery method of a device management session according to an embodiment of the present invention;
fig. 2 is another basic diagram of a recovery method of a device management session according to an embodiment of the present invention;
fig. 3 is a schematic diagram of a recovery apparatus for device management session according to an embodiment of the present invention;
FIG. 4 is a schematic diagram of another component of a device management session recovery apparatus according to an embodiment of the present invention;
FIG. 5 is a schematic diagram illustrating a recovery flow of a device management session initiated by a client according to an embodiment of the present invention;
FIG. 6 is a diagram illustrating a recovery flow of a server-initiated device management session according to an embodiment of the present invention;
fig. 7 is a schematic flow chart of data saving in a device management session according to an embodiment of the present invention.
Detailed Description
In order to make the technical problems, technical solutions and advantages of the present invention more apparent, the following detailed description is given with reference to the accompanying drawings and specific embodiments.
The embodiment of the invention provides a recovery method, a recovery device, a client and a server for equipment management, aiming at solving the problem of resource waste caused by session interruption by restarting equipment management session in the prior art.
As shown in fig. 1, an embodiment of the present invention provides a method for recovering device management, applied to a client side, where the method includes:
and step 15, generating a session recovery data packet for recovering the first session managed by the equipment, wherein the session recovery data packet comprises the execution command state and the execution result of the first session.
And step 16, storing the session recovery data packet and reporting to a server.
And step 17, receiving a management command data packet of the recovery flow of the first session sent by the server.
Specifically, the session recovery packet includes: standard content generated according to the related specification of the OMA DM protocol, and content indicating that the device management session is a recovery flow as follows:
wherein, Alert 1226 is a general Alert (Generic Alert) Type defined in the DM protocol, and indicates that this DM session is an ongoing recovery task by adding a Type (Type) org.
Meanwhile, the data packet also contains data (unsensed session data) which is not successfully transmitted when the recovered session is interrupted.
In this embodiment of the present invention, before a client generates a session recovery packet for recovering a first session of device management, the method for recovering a device management session further includes:
and 11, receiving a management command data packet sent by the server in the first session of equipment management.
Step 12, executing the management command data packet, and storing an execution result data packet of the first session generated when the management command data packet is executed; wherein the execution result packet includes: a first session ID of the first session, and an execution command status and an execution result of the first session.
And step 13, sending the execution result data packet to a server.
And 14, deleting the execution result data packet after receiving the confirmation data packet of the execution result data packet sent by the server.
Specifically, the steps 11 to 14 are an execution process in which the client receives a management command data packet issued by the server in the device management session process, and the client first stores the management command data packet after receiving the management command data packet, so as to avoid that the management command to be executed cannot be confirmed when the client executes again after the execution fails; then executing the management command data packet, acquiring and storing an execution command state and an execution result, and deleting the management command data packet when the execution command state shows that the execution is successful, thereby releasing the memory of the client; forming an execution result data packet by using the execution command state, the execution result and the session ID of the equipment management session, and sending the execution result data packet to a server; and finally, when a confirmation data packet sent by the server is received, deleting the execution result data packet, thereby releasing the memory of the client. The execution result data packet is stored, so that the device management session can be recovered according to the stored execution result data packet after the device management session is interrupted, thereby avoiding traffic consumption and management pressure of the server caused by session resumption.
When the execution result data packet is transmitted, if the complete data cannot be transmitted in a single time, the execution result data packet is transmitted in multiple packets, and when all data are successfully transmitted and a confirmation data packet and a new management command data packet are received, the execution result data packet is deleted.
The embodiment of the present invention provides the following two ways to generate a session recovery packet for recovering the first session managed by the device:
the first method is as follows: when the initiator of the first session is a server, before step 11, the method for recovering the device management session further includes:
receiving a notification message which is sent by a server in a second session managed by the equipment and used for indicating the recovery of the first session; wherein the notification message comprises: the first flow recovery flag information, a first session ID for the first session, and a second session ID for the second session.
The step 11 specifically comprises:
judging whether the first session can be recovered or not according to the first session ID; and if so, generating the session recovery data packet according to the first flow mark information, the second session ID, the execution command state and the execution result of the first session.
Specifically, the step of determining whether the first session can be resumed includes:
and if the execution result data packet containing the first session ID can be acquired, judging that the first session can be recovered, otherwise, not recovering the first session.
The second method comprises the following steps: when the initiator of the first session is the client, the step 11 specifically includes:
step 111, determining whether the first session of device management is interrupted.
Specifically, the specific method for determining whether the first session managed by the device is interrupted is as follows: and the client side does not receive the confirmation data packet within the preset time length after reporting the execution result data packet of the first session, or determines that the first session is interrupted when the end data packet is not received within the preset time length after reporting the execution result data packet of the first session.
Step 112, when it is determined that the first session is interrupted, determining whether an initiator of the first session is a client.
Specifically, when a device management session is initiated, an initiator generates a session ID of the device management session, and simultaneously generates an initiation flag information, and when the client includes the initiation flag information, the initiator of the device management session is a client, otherwise, the initiator is a server.
Step 113, when it is determined that the initiator of the first session is the client, obtaining an execution result data packet of the first session.
Step 114, initiating a third session, and generating a session recovery packet for indicating to recover the first session, where the session recovery packet includes an execution result packet of the first session, second procedure recovery flag information, and a third session ID of the third session.
Specifically, the execution result data packet of the first session is a first session ID, an execution command state, and an execution result that are stored by the client in the first session; the second process recovery flag information is a flag for identifying that the session recovery data packet is a data packet of a recovery process; the third session ID is a session ID of a third session of the recovery procedure of the first session.
In the above embodiments of the present invention, the client can implement interruption of the device management session due to the client and recovery of interruption of the device management session due to the server, and repeated retries are not required, so that consumption of dynamic resources when the server waits is reduced.
It should be noted that, after receiving the session recovery data packet, the server first performs related operations such as authentication, so as to ensure that the data sent by the client is legal and safe.
As shown in fig. 2, an embodiment of the present invention further provides a method for recovering a device management session, where the method is applied to a server side, and the method includes:
and step 24, receiving a session recovery data packet which is sent by the client and used for recovering the first session of the device management, wherein the session recovery data packet comprises the execution command state and the execution result of the first session.
And 25, sending a management command data packet of the first session recovery flow according to the session recovery data packet.
In this embodiment of the present invention, before receiving a session recovery packet for recovering a first session managed by a device, the method further includes:
step 21, receiving an execution result data packet of the first session reported by the client, where the execution result data packet includes: a first session ID of the first session, and an execution command status and an execution result of the first session.
The execution result data packet of the first session is an execution result data packet generated by the client according to the management command data packet issued by the server.
Step 22, saving the data packet of the execution result of the first session, and deleting the management command that has been successfully executed currently from the unexecuted command of the first session according to the status of the execution command and the execution result of the first session.
Specifically, if the execution result data packet is sent in multiple packets, the management command that has been successfully executed is deleted when the execution result data packet is completely sent and the execution command status is successful, so that only the management command that has not been executed is always stored in the server.
Step 23, determining whether there is an unexecuted management command in the first session, if yes, sending a management command data packet of the unexecuted management command, and if not, sending an end data packet of the first session.
Specifically, in an embodiment of the present invention, the step 24 includes:
receiving a session recovery data packet of the first session, which is reported by the client in the second session and used for indicating the recovery equipment to manage; wherein the session recovery packet comprises: first flow recovery flag information, a second session ID of the second session, and an execution result packet of the first session.
When the initiator of the first session is a client and the client detects that the first session is interrupted, the session recovery data packet generated in the process of the first session is actively recovered.
In this embodiment of the present invention, after receiving a session recovery data packet reported when the client actively recovers the first session, step 25 includes:
step 251, determining whether the first session can be recovered according to the first session ID; and if so, acquiring the unexecuted management command in the first session according to the first session ID.
Wherein the server determines that the first session is recoverable when detecting an unexecuted management command of the first session, and otherwise, the first session is not recoverable.
Step 252, obtaining the management command data packet of the first session recovery flow according to the management command that is not executed in the first session and the second session ID.
Wherein the management command packet includes a second session ID of the second session and a first management command hit by the unexecuted management.
Step 253, sending the management command data packet of the first session recovery flow to the client in the second session.
Further, in this embodiment of the present invention, if the initiator of the first session is a server, before step 21, the method further includes:
it is determined whether the first session managed by the device is interrupted.
Wherein, the step of judging whether the first session managed by the device is interrupted specifically comprises:
and determining that the first session is interrupted when an execution result data packet corresponding to the management command data packet sent by the client is not received within a preset time length after the management command data packet of the first session is sent.
And when the first session is determined to be interrupted, judging whether the initiator of the first session is a server or not.
When the equipment management session is initiated, an initiator generates a session ID of the equipment management session, and simultaneously generates an initiation mark information, when the server contains the initiation mark information, the initiator of the equipment management session is a client, otherwise, the initiator is the server.
And when the initiator of the first session is determined to be the server, acquiring the management command which is not executed in the first session.
When the first session is initiated, the client stores all the management commands of the first session, and when each management command is received and an execution result data packet representing the successful execution of the management command is received, the management command is deleted, so that only the unexecuted management commands are always stored on the server.
Initiating a third session and generating a notification message for indicating recovery of the first session, wherein the notification message comprises a first session ID of the first session, a third session ID of the third session, and second process recovery flag information.
The notification message is used for notifying the client, the device management session with the session ID of the first session ID needs to be recovered, and the recovered session ID is the third session ID.
And sending the notification message to the client.
Specifically, when the first session is initiated by the server, the step 25 includes:
and acquiring a management command data packet of the first session recovery flow according to the unexecuted management command in the first session and the third session ID.
And sending the management command data packet of the first session recovery flow to the client in the third session.
The above embodiment of the present invention is a method for recovering a server side in a device management session recovery process, including: the recovery method when the server initiatively initiates the session and the recovery method according to the session recovery data packet initiatively sent by the client, thereby realizing the recovery of the interruption of any condition of the equipment management session and reducing the management pressure and the consumption of dynamic resources of the server.
As shown in fig. 3, an embodiment of the present invention further provides an apparatus for recovering a device management session, which is applied to a client side, where the apparatus includes:
the generating module 31 is configured to generate a session recovery data packet for recovering the first session managed by the device, where the session recovery data packet includes an execution command status and an execution result of the first session.
And the storage module 32 is configured to store the session recovery data packet and report the session recovery data packet to the server.
The first receiving module 33 is configured to receive a management command data packet of the recovery procedure of the first session sent by the server.
In the embodiment of the present invention, the apparatus further includes:
and the second receiving module is used for receiving the management command data packet sent by the server in the first session managed by the equipment.
The execution module is used for executing the management command data packet and storing an execution result data packet of the first session generated when the management command data packet is executed; wherein the execution result packet includes: a first session ID of the first session, and an execution command status and an execution result of the first session.
The sending module is used for sending the execution result data packet to a server;
and the deleting module is used for deleting the execution result data packet after receiving the confirmation data packet of the execution result data packet sent by the server. The deleting module 37 realizes real-time update of the storage information of the client, so that the client only stores the latest execution result data packet, thereby saving the memory space of the client.
Further, in an embodiment of the present invention, the apparatus further includes:
a third receiving module, configured to receive a notification message sent by a server in a second session of device management and used to instruct to resume the first session; wherein the notification message comprises: the first flow recovery flag information, a first session ID for the first session, and a second session ID for the second session.
Specifically, in the embodiment of the present invention, the generating module includes:
a first judging submodule, configured to judge whether the first session can be recovered according to the first session ID; and if so, generating the session recovery data packet according to the first flow mark information, the second session ID, the execution command state and the execution result of the first session.
Wherein the first judgment sub-module includes:
and the judging unit is used for judging that the first session can be recovered if the execution result data packet containing the first session ID can be obtained, and otherwise, the first session cannot be recovered.
Specifically, in this embodiment of the present invention, the generating module further includes:
and the second judgment submodule is used for judging whether the first session managed by the equipment is interrupted or not.
And the third judgment submodule is used for judging whether the initiator of the first session is the client or not when the first session is determined to be interrupted.
And the obtaining submodule is used for obtaining the execution result data packet of the first session when the initiator of the first session is determined to be the client.
And the triggering module is used for initiating a third session and generating a session recovery data packet for indicating recovery of the first session, wherein the session recovery data packet comprises an execution result data packet of the first session, second process recovery flag information and a third session ID of the third session.
Specifically, the second judgment sub-module includes:
and a determining unit, configured to determine that the first session is interrupted when no acknowledgement packet is received within a preset time period after reporting the execution result packet of the first session, or determine that the first session is interrupted when an end packet is not received within a preset time period after reporting the execution result packet of the first session.
In the foregoing embodiment of the present invention, the first determining submodule is configured to, when the server initiates a recovery process, determine whether the client can recover the first session according to the first session ID received by the third receiving module, and if the client can recover the first session, resend the execution command state and the execution result that are sent in the first session in failure to the server, thereby implementing recovery of the first session. The second judgment submodule, the third judgment value module, the acquisition submodule and the trigger submodule are used for determining whether the initiator of the first session is the client side, if so, the client side actively initiates the third session, and the first session is recovered.
Embodiments of the present invention also provide a client, including a memory, a processor, and a computer program stored on the memory and executable on the processor; wherein the processor implements the method as described above when executing the program.
Embodiments of the present invention also provide a computer-readable storage medium, on which a computer program is stored, where the program, when executed by a processor, implements the steps in the method as described above.
As shown in fig. 4, an embodiment of the present invention further provides an apparatus for recovering a device management session, which is applied to a server side, where the apparatus includes:
the first receiving module 41 is configured to receive a session recovery data packet sent by the client and used for recovering the first session managed by the device, where the session recovery data packet includes an execution command status and an execution result of the first session.
A first sending module 42, configured to send a management command data packet of the first session recovery procedure according to the session recovery data packet.
In an embodiment of the present invention, the apparatus further includes:
a second receiving module, configured to receive an execution result data packet of the first session, where the execution result data packet includes: a first session ID of the first session, and an execution command status and an execution result of the first session.
And the storage module is used for storing the execution result data packet of the first session and deleting the management command which is successfully executed currently from the unexecuted command of the first session according to the execution command state and the execution result of the first session.
The first judging module is used for judging whether the first session has an unexecuted management command, if so, sending a management command data packet of the unexecuted management command, and if not, sending an end data packet of the first session.
Specifically, the first receiving module 41 includes:
the receiving submodule is used for receiving a session recovery data packet which is reported by the client in the second session and is used for indicating the first session managed by the recovery equipment; wherein the session recovery packet comprises: first flow recovery flag information, a second session ID of the second session, and an execution result packet of the first session.
Specifically, the first sending module 42 includes:
a first judgment sub-module: the first session ID is used for judging whether the first session can be recovered or not; and if so, acquiring the unexecuted management command in the first session according to the first session ID.
And the first obtaining submodule is used for obtaining the management command data packet of the first session recovery flow according to the unexecuted management command in the first session and the second session ID.
And the first sending submodule is used for sending the management command data packet of the first session recovery flow to the client in the second session.
Further, in an embodiment of the present invention, the apparatus further includes:
and the second judgment module is used for judging whether the first session managed by the equipment is interrupted.
Specifically, the determining module includes a determining submodule, configured to determine that the first session is interrupted when an execution result data packet corresponding to the management command data packet sent by the client is not received within a preset time period after the management command data packet of the first session is sent.
A first obtaining module, configured to obtain, when it is determined that an initiator of the first session is a server, a management command that is not executed in the first session.
And the triggering module is used for initiating a third session and generating a notification message for indicating the recovery of the first session, wherein the notification message comprises a first session ID of the first session, a third session ID of the third session and second flow recovery flag information.
And the second sending module is used for sending the notification message to the client.
In the above embodiment of the present invention, the second determining module, the first obtaining module, the triggering module, and the sending module are specifically applied to that, when the initiator of the first session is a server, the server actively initiates a third session for recovering the first session.
Specifically, the first sending module 41 includes:
and the second obtaining submodule is used for obtaining the management command data packet of the first session recovery flow according to the unexecuted management command in the first session and the third session ID.
And the second sending submodule is used for sending the management command data packet of the first session recovery flow to the client in a third session.
The embodiment of the invention also provides a server, which comprises a memory, a processor and a computer program which is stored on the memory and can run on the processor; wherein the processor implements the method as described above when executing the program.
Embodiments of the present invention also provide a computer-readable storage medium, on which a computer program is stored, where the program, when executed by a processor, implements the steps in the method as described above.
As shown in fig. 5, a recovery procedure of a device management session initiated by a client according to an embodiment of the present invention is as follows:
Step 503, the client waits for receiving the acknowledgement data packet or the end data packet sent by the server.
In step 505, the client waits for receiving the notification message sent by the server.
And step 507, the client saves the session recovery data packet of the first session recovery flow and sends the session recovery data packet to the server.
In step 509, the server obtains the management command that is not executed by the first session, and executes step 511.
In step 510, the server sends an end packet to end the first session.
The client ends the first session when receiving the end data packet; and when the session recovery data packet is received, executing a corresponding management command according to the session recovery data packet.
As shown in fig. 6, a recovery procedure of a device management session initiated by a server in an embodiment of the present invention is as follows:
601, the server judges whether the first session managed by the device is interrupted; and judging that the first session is interrupted if an execution result data packet generated when the client executes the management command data packet is not received within a preset time length after the server sends the management command data packet, otherwise, judging that the first session is not interrupted. When the first session is interrupted, step 602 is executed, otherwise, step 603 is executed.
Step 604, the server obtains the unexecuted management command of the first session.
In step 607, the server sends a notification message to the client.
Step 609, the client generates a session recovery data packet of the recovery flow of the first session according to the first session ID, the third session ID, the execution command status of the first session, and the execution result.
Step 611, the client reports the session recovery data packet to the server.
Step 612, the server generates a management command data packet of the recovery flow of the first session according to the session recovery data packet.
Step 613, the server issues the management command data packet and the confirmation data packet of the session recovery data packet to the client.
As shown in fig. 7, in the device management session, the data saving process of the client and the server is as follows:
step 71, when initiating the device management session, the server stores all management commands of the device management session.
Step 72, the server issues the first management command of the management commands.
And 73, the client receives and stores the management command, and deletes the execution command state and the execution result generated when the management command is executed last time.
Step 74, the client executes the management command.
Step 75, the client saves the execution command state and execution result generated when executing the management command, and deletes the management command.
In step 76, the client sends the status of the execution command and the execution result, and an execution result data packet generated by the session ID of the device management session.
And 77, the server receives the execution result data packet and deletes the issued management command which is successfully executed.
In the above embodiment of the present invention, after the client executes the management command data packet, the generated execution result data packet is stored, and after the device management session is interrupted, the device management session is recovered according to the stored execution result data packet, thereby avoiding repeatedly executing the executed management command, achieving faster completion of the whole device management session process, and reducing the management pressure of the server; and after receiving the execution result data packet, the server deletes the currently successfully executed management command, so that the currently unexecuted management command is always stored in the server, and after the equipment management session is interrupted, the unexecuted management command is acquired according to the session ID, so that the equipment management session is recovered, and the traffic consumption of repeated sessions is reduced.
According to the embodiment of the invention, no matter the session is interrupted due to the client or the server, the session recovery is realized without repeated retry, so that the consumption of dynamic resources when the server waits is reduced.
It should be noted that, in the foregoing embodiment of the present invention, in the process of executing a command or receiving and sending data by a client, if a session is interrupted, such as a network outage or a device power outage, and if the device management session is triggered by a server, the server waits for issuing a notification message of a recovery task; if the device management session flow is initiated by the client, actively initiating a recovery task after connecting the active network, namely: in the recovery process of the device management session, the principle of who initiates and who recovers is followed.
While the foregoing is directed to the preferred embodiment of the present invention, it will be understood by those skilled in the art that various changes and modifications may be made without departing from the spirit and scope of the invention as defined in the appended claims.
Claims (30)
1. A recovery method of a device management session, applied to a client side, is characterized in that the method comprises:
generating a session recovery data packet for recovering the first session managed by the device according to an execution result data packet of the first session stored before the first session is interrupted, wherein the execution result data packet of the first session is always stored without receiving a confirmation data packet of the execution result data packet sent by the server and comprises an execution command state and an execution result of the first session, and the session recovery data packet comprises the execution command state and the execution result of the first session;
saving the session recovery data packet and reporting to a server;
and receiving a management command data packet of the recovery flow of the first session, which is sent by the server.
2. The method of claim 1, wherein prior to generating the session recovery packet for recovering the first session for device management, the method further comprises:
receiving a management command data packet sent by a server in a first session managed by equipment;
executing the management command data packet, and storing an execution result data packet of the first session generated when the management command data packet is executed; wherein the execution result packet further includes: a first session ID for the first session;
sending the execution result data packet to a server;
and deleting the execution result data packet after receiving the confirmation data packet of the execution result data packet sent by the server.
3. The method of claim 2,
before generating the session recovery packet for recovering the first session of device management, the method further comprises:
receiving a notification message which is sent by a server in a second session managed by the equipment and used for indicating the recovery of the first session; wherein the notification message comprises: first flow recovery flag information, a first session ID of the first session, and a second session ID of the second session;
the step of generating a session recovery packet for recovering the first session of device management comprises:
judging whether the first session can be recovered or not according to the first session ID; and if so, generating the session recovery data packet according to the first flow mark information, the second session ID, the execution command state and the execution result of the first session.
4. The method of claim 3, wherein the step of determining whether the first session can be resumed comprises:
and if the execution result data packet containing the first session ID can be acquired, judging that the first session can be recovered, otherwise, not recovering the first session.
5. The method of claim 2, wherein generating the session recovery packet for the device managed first session comprises:
judging whether a first session managed by the equipment is interrupted or not;
when the first session is determined to be interrupted, judging whether an initiator of the first session is a client or not;
when the initiator of the first session is determined to be the client, acquiring an execution result data packet of the first session;
initiating a third session and generating a session recovery packet for indicating recovery of the first session, the session recovery packet including an execution result packet of the first session, second process recovery flag information, and a third session ID of the third session.
6. The method of claim 5, wherein the step of determining whether the first session managed by the device is interrupted comprises:
and if the confirmation data packet is not received within the preset time after the execution result data packet of the first session is reported, or if the ending data packet is not received within the preset time after the execution result data packet of the first session is reported, determining that the first session is interrupted.
7. A recovery method of a device management session is applied to a server side, and is characterized in that the method comprises the following steps:
receiving a session recovery data packet of a first session, which is generated and sent by a client according to an execution result data packet of the first session stored before interruption of the first session, and is used for recovering device management, wherein the execution result data packet of the first session is always stored by the client under the condition that an acknowledgement data packet of the execution result data packet sent by a server is not received, the session recovery data packet comprises an execution command state and an execution result of the first session, and the session recovery data packet comprises the execution command state and the execution result of the first session;
and sending a management command data packet of the first session recovery flow according to the session recovery data packet.
8. The method of claim 7, wherein before receiving a session recovery packet for recovering the device managed first session, the session recovery packet is generated and sent by the client according to an execution result packet of the first session saved before the first session is interrupted, the method further comprises:
receiving an execution result data packet of a first session reported by a client, wherein the execution result data packet further comprises: a first session ID for the first session;
saving an execution result data packet of a first session, and deleting a management command which is successfully executed currently from unexecuted commands of the first session according to the execution command state and the execution result of the first session;
and judging whether the first session has an unexecuted management command, if so, sending a management command data packet of the unexecuted management command, and if not, sending an end data packet of the first session.
9. The method according to claim 8, wherein the step of receiving the session recovery packet for restoring the device managed first session, generated and transmitted by the client according to the execution result packet of the first session saved before the first session interruption, comprises:
receiving a session recovery data packet of the first session, which is reported by the client in the second session and used for indicating the recovery equipment to manage; wherein the session recovery packet comprises: first flow recovery flag information, a second session ID of the second session, and an execution result packet of the first session.
10. The method of claim 9, wherein the step of sending the management command packet of the first session recovery procedure according to the session recovery packet comprises:
judging whether the first session can be recovered or not according to the ID of the first session; if yes, acquiring an unexecuted management command in the first session according to the first session ID;
acquiring a management command data packet of the first session recovery flow according to the unexecuted management command in the first session and the ID of the second session;
and sending the management command data packet of the first session recovery flow to the client in the second session.
11. The method according to claim 8, wherein before the step of generating and transmitting, by the receiving client, the session recovery packet for recovering the device managed first session from the execution result packet of the first session saved before the first session interruption, the method further comprises:
judging whether a first session managed by the equipment is interrupted or not;
when the first session is determined to be interrupted, judging whether an initiator of the first session is a server or not;
when the initiator of the first session is determined to be a server, acquiring an unexecuted management command in the first session;
initiating a third session and generating a notification message for indicating recovery of the first session, wherein the notification message comprises a first session ID of the first session, a third session ID of the third session, and second flow recovery flag information;
and sending the notification message to the client.
12. The method of claim 11, wherein the step of determining whether the first session managed by the device is interrupted comprises:
and determining that the first session is interrupted when an execution result data packet corresponding to the management command data packet sent by the client is not received within a preset time length after the management command data packet of the first session is sent.
13. The method of claim 11, wherein the step of sending the management command packet of the first session recovery procedure according to the session recovery packet comprises:
acquiring a management command data packet of the first session recovery flow according to the unexecuted management command in the first session and the third session ID;
and sending the management command data packet of the first session recovery flow to the client in the third session.
14. An apparatus for recovering device management session, applied to a client side, the apparatus comprising:
a generating module, configured to generate a session recovery data packet for recovering the first session managed by the device according to an execution result data packet of the first session saved before the first session is interrupted, where the execution result data packet of the first session is always saved without receiving a confirmation data packet of the execution result data packet sent by the server, and includes an execution command state and an execution result of the first session, and the session recovery data packet includes the execution command state and the execution result of the first session;
the storage module is used for storing the session recovery data packet and reporting the session recovery data packet to a server;
and the first receiving module is used for receiving a management command data packet of the recovery process of the first session, which is sent by the server.
15. The apparatus of claim 14, further comprising:
the second receiving module is used for receiving a management command data packet sent by the server in the first session managed by the equipment;
the execution module is used for executing the management command data packet and storing an execution result data packet of the first session generated when the management command data packet is executed; wherein the execution result packet further includes: a first session ID for the first session;
the sending module is used for sending the execution result data packet to a server;
and the deleting module is used for deleting the execution result data packet after receiving the confirmation data packet of the execution result data packet sent by the server.
16. The apparatus of claim 15,
the device further comprises:
a third receiving module, configured to receive a notification message sent by a server in a second session of device management and used to instruct to resume the first session; wherein the notification message comprises: first flow recovery flag information, a first session ID of the first session, and a second session ID of the second session;
the generation module comprises:
a first judging submodule, configured to judge whether the first session can be recovered according to the first session ID; and if so, generating the session recovery data packet according to the first flow mark information, the second session ID, the execution command state and the execution result of the first session.
17. The apparatus of claim 16, wherein the first determining submodule comprises:
and the judging unit is used for judging that the first session can be recovered if the execution result data packet containing the first session ID can be obtained, and otherwise, the first session cannot be recovered.
18. The apparatus of claim 15, wherein the generating module comprises:
the second judgment submodule is used for judging whether the first session managed by the equipment is interrupted or not;
a third judging submodule, configured to judge whether an initiator of the first session is a client when it is determined that the first session is interrupted;
the obtaining submodule is used for obtaining an execution result data packet of the first session when the initiator of the first session is determined to be the client;
and the triggering module is used for initiating a third session and generating a session recovery data packet for indicating recovery of the first session, wherein the session recovery data packet comprises an execution result data packet of the first session, second process recovery flag information and a third session ID of the third session.
19. The apparatus of claim 18, wherein the second determination submodule comprises:
and a determining unit, configured to determine that the first session is interrupted when no acknowledgement packet is received within a preset time period after reporting the execution result packet of the first session, or determine that the first session is interrupted when an end packet is not received within a preset time period after reporting the execution result packet of the first session.
20. A client comprising a memory, a processor, and a computer program stored on the memory and executable on the processor; characterized in that the processor, when executing the program, implements the method according to any of claims 1-6.
21. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the steps of the method according to any one of claims 1 to 6.
22. An apparatus for recovering device management session, applied to a server side, the apparatus comprising:
a first receiving module, configured to receive a session recovery data packet, which is generated and sent by a client according to an execution result data packet of a first session stored before a first session is interrupted, and is used for recovering the first session managed by a device, where the execution result data packet of the first session is always stored by the client without receiving a confirmation data packet of the execution result data packet sent by a server, and includes an execution command state and an execution result of the first session, and the session recovery data packet includes the execution command state and the execution result of the first session;
and the first sending module is used for sending the management command data packet of the first session recovery flow according to the session recovery data packet.
23. The apparatus of claim 22, further comprising:
a second receiving module, configured to receive an execution result data packet of the first session, where the execution result data packet further includes: a first session ID for the first session;
the storage module is used for storing an execution result data packet of the first session and deleting the management command which is successfully executed currently from the unexecuted command of the first session according to the execution command state and the execution result of the first session;
the first judging module is used for judging whether the first session has an unexecuted management command, if so, sending a management command data packet of the unexecuted management command, and if not, sending an end data packet of the first session.
24. The apparatus of claim 23, wherein the first receiving module comprises:
the receiving submodule is used for receiving a session recovery data packet which is reported by the client in the second session and is used for indicating the first session managed by the recovery equipment; wherein the session recovery packet comprises: first flow recovery flag information, a second session ID of the second session, and an execution result packet of the first session.
25. The apparatus of claim 24, wherein the first sending module comprises:
a first judgment sub-module: the first session ID is used for judging whether the first session can be recovered or not; if yes, acquiring an unexecuted management command in the first session according to the first session ID;
a first obtaining sub-module, configured to obtain a management command data packet of the first session recovery flow according to an unexecuted management command in the first session and the second session ID;
and the first sending submodule is used for sending the management command data packet of the first session recovery flow to the client in the second session.
26. The apparatus of claim 23, further comprising:
the second judgment module is used for judging whether the first session managed by the equipment is interrupted or not;
a first obtaining module, configured to obtain an unexecuted management command in the first session when it is determined that an initiator of the first session is a server;
the trigger module is used for initiating a third session and generating a notification message for indicating the recovery of the first session, wherein the notification message comprises a first session ID of the first session, a third session ID of the third session and second flow recovery flag information;
and the second sending module is used for sending the notification message to the client.
27. The apparatus of claim 26, wherein the second determining module comprises:
and the determining submodule is used for determining that the first session is interrupted when an execution result data packet corresponding to the management command data packet sent by the client is not received within a preset time length after the management command data packet of the first session is sent.
28. The apparatus of claim 26, wherein the first sending module comprises:
a second obtaining sub-module, configured to obtain, according to the unexecuted management command in the first session and the third session ID, a management command data packet of the first session recovery flow;
and the second sending submodule is used for sending the management command data packet of the first session recovery flow to the client in a third session.
29. A server comprising a memory, a processor, and a computer program stored on the memory and executable on the processor; characterized in that the processor, when executing the program, implements the method according to any of claims 7-13.
30. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the steps of the method according to any one of claims 7-13.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710676037.XA CN109391656B (en) | 2017-08-09 | 2017-08-09 | Method and device for recovering equipment management session, client and server |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710676037.XA CN109391656B (en) | 2017-08-09 | 2017-08-09 | Method and device for recovering equipment management session, client and server |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109391656A CN109391656A (en) | 2019-02-26 |
| CN109391656B true CN109391656B (en) | 2021-10-08 |
Family
ID=65415384
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710676037.XA Active CN109391656B (en) | 2017-08-09 | 2017-08-09 | Method and device for recovering equipment management session, client and server |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109391656B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110784943B (en) * | 2019-10-30 | 2021-07-27 | 中国联合网络通信集团有限公司 | Processing method and device for VoWiFi voice service disconnection and reconnection |
Citations (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1852534A (en) * | 2005-08-10 | 2006-10-25 | 华为技术有限公司 | Data backing-up and recovering method and system |
| WO2008078889A1 (en) * | 2006-12-27 | 2008-07-03 | Daegu Gyeongbuk Institute Of Science And Technology | Method of controlling the session for the oma dm protocol |
| CN101227418A (en) * | 2007-01-19 | 2008-07-23 | 华为技术有限公司 | System, apparatus and method for implementing amalgamation IP message |
| CN101409614A (en) * | 2007-10-12 | 2009-04-15 | 华为技术有限公司 | Data synchronization method, system and equipment |
| CN102111427A (en) * | 2009-12-25 | 2011-06-29 | 中兴通讯股份有限公司 | Device management session recovery method and system |
| CN102541662A (en) * | 2010-12-29 | 2012-07-04 | 华为终端有限公司 | Software processing control method and mobile terminal |
| CN103270734A (en) * | 2010-11-05 | 2013-08-28 | 高通股份有限公司 | Segmented data transfer with resume capability |
| CN103621113A (en) * | 2011-02-11 | 2014-03-05 | 交互数字专利控股公司 | Systems, methods and apparatus for managing machine-to-machine (m2m) entities |
| CN104508663A (en) * | 2012-07-27 | 2015-04-08 | 微软公司 | Automatic transaction retry after session failure |
| CN105812313A (en) * | 2014-12-29 | 2016-07-27 | 阿里巴巴集团控股有限公司 | Method and server for restoring session, and method and server for generating session credential |
| EP3151481A1 (en) * | 2015-09-30 | 2017-04-05 | Ricoh Company, Ltd. | Communication terminal, communication system, and output method |
| CN106687976A (en) * | 2014-07-11 | 2017-05-17 | Pcms控股公司 | Systems and methods for virtualization based secure device |
| CN206364832U (en) * | 2016-06-10 | 2017-07-28 | 北京数盾信息科技有限公司 | One kind is based on safety management and information feedback system under GDOI agreements |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040044799A1 (en) * | 2002-09-03 | 2004-03-04 | Nokia Corporation | Method, device and system for synchronizing of data providing for the handling of an interrupted synchronization process |
| CN105340356A (en) * | 2013-08-02 | 2016-02-17 | 英特尔Ip公司 | SUPL session persistence across power cycles |
-
2017
- 2017-08-09 CN CN201710676037.XA patent/CN109391656B/en active Active
Patent Citations (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1852534A (en) * | 2005-08-10 | 2006-10-25 | 华为技术有限公司 | Data backing-up and recovering method and system |
| WO2008078889A1 (en) * | 2006-12-27 | 2008-07-03 | Daegu Gyeongbuk Institute Of Science And Technology | Method of controlling the session for the oma dm protocol |
| CN101227418A (en) * | 2007-01-19 | 2008-07-23 | 华为技术有限公司 | System, apparatus and method for implementing amalgamation IP message |
| CN101409614A (en) * | 2007-10-12 | 2009-04-15 | 华为技术有限公司 | Data synchronization method, system and equipment |
| CN102111427A (en) * | 2009-12-25 | 2011-06-29 | 中兴通讯股份有限公司 | Device management session recovery method and system |
| CN103270734A (en) * | 2010-11-05 | 2013-08-28 | 高通股份有限公司 | Segmented data transfer with resume capability |
| CN102541662A (en) * | 2010-12-29 | 2012-07-04 | 华为终端有限公司 | Software processing control method and mobile terminal |
| CN103621113A (en) * | 2011-02-11 | 2014-03-05 | 交互数字专利控股公司 | Systems, methods and apparatus for managing machine-to-machine (m2m) entities |
| CN104508663A (en) * | 2012-07-27 | 2015-04-08 | 微软公司 | Automatic transaction retry after session failure |
| CN106687976A (en) * | 2014-07-11 | 2017-05-17 | Pcms控股公司 | Systems and methods for virtualization based secure device |
| CN105812313A (en) * | 2014-12-29 | 2016-07-27 | 阿里巴巴集团控股有限公司 | Method and server for restoring session, and method and server for generating session credential |
| EP3151481A1 (en) * | 2015-09-30 | 2017-04-05 | Ricoh Company, Ltd. | Communication terminal, communication system, and output method |
| CN206364832U (en) * | 2016-06-10 | 2017-07-28 | 北京数盾信息科技有限公司 | One kind is based on safety management and information feedback system under GDOI agreements |
Non-Patent Citations (2)
| Title |
|---|
| "Incorporating OMA Lightweight M2M protocol in IoT/M2M standard architecture";Christian Antonia Lusiarta Putera等;《2015 IEEE 2nd World Forum on Internet of Things (WF-IoT)》;20160121;第1-6页 * |
| "入式OMA-DM系统架构及关键技术研究与设计";程方等;《电视技术》;20110427;第35卷(第3期);第57-60页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109391656A (en) | 2019-02-26 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP3386150B1 (en) | Terminal failure processing method, device and system | |
| JP7234402B2 (en) | Secondary link monitoring method for vehicle communication, vehicle communication terminal, electronic device and computer program | |
| CN108259618B (en) | Synchronous data interaction processing method and device | |
| KR101419579B1 (en) | Method for enabling faster recovery of client applications in the event of server failure | |
| CN107645517B (en) | Data pushing method and device | |
| CN112118171A (en) | Message intercommunication system, method, device, computer equipment and readable storage medium | |
| CN108134713B (en) | Communication method and device | |
| CN113905005A (en) | Client state updating method and device for instant messaging | |
| CN107645357B (en) | Recovery method and device for incomplete transmitted file | |
| CN113746910A (en) | H5 page reconnection server method, terminal and readable storage medium | |
| CN113986501A (en) | Real-time database API (application program interface) uninterrupted calling method, system, storage medium and server | |
| CN109391656B (en) | Method and device for recovering equipment management session, client and server | |
| CN112860408A (en) | Process keep-alive method, device and system in cloud reality machine and storage medium | |
| CN110809262A (en) | Internet of things equipment operation and maintenance management method based on COAP protocol | |
| CN108521342B (en) | Cluster management method and device | |
| JP2016066303A (en) | Server device, redundant configuration server system, information taking-over program and information taking-over method | |
| JP4882537B2 (en) | Request control method by timer cooperation | |
| CN109474579B (en) | Network reconnection method and device | |
| CN108667682B (en) | Connection synchronization method, device and medium based on secure gateway deep packet detection | |
| CN111756826A (en) | DLM lock information transmission method and related device | |
| CN114553944A (en) | Early warning message pushing method and system | |
| CN110446221B (en) | Railway private network communication guarantee method and system | |
| CN103441872A (en) | Failure recovery method, device and communication system of user side equipment | |
| CN114125021A (en) | Terminal information issuing system based on Netty message drive | |
| CN106411570A (en) | Method for realizing SCTP (streaming control transmission protocol) protocol hot backup, system and server host |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |