Recovery method and device for device management session, client and server

Abstract

The invention provides a recovery method and device for a device management session, a client and a server, and relates to the technical field of OMA (Open Mobile Alliance) DM (Device Management). Therecovery method includes the steps: generating a session recovery data packet for recovery of a first session of device management, wherein the session recovery data packet includes an execution command state and an execution result of the first session; saving the session recovery data packet, and reporting the session recovery data packet to the server; and receiving a management command data packet of a recovery process of the first session, sent by the server. The solution of the recovery method and device for a device management session realizes the interrupted recovery of in any situation in the device management session, reduces the traffic consumption of the repeated session, reduces the consumption of dynamic resources when the server waits, accelerates the entire management process of the device management session, and reduces the management pressure of the server.

Description

technical field [0001] The present invention belongs to the technical field of Open Mobile Alliance (OMA) Device Management (Device Management, DM), and in particular relates to a device management session recovery method, device, client and server. Background technique [0002] In the actual DM session interaction process, the process is often interrupted due to various reasons, such as device restart, network abnormality, etc. After the interruption, the client or server will resume the session process by retrying the connection, but no matter Whether it is a server or a client, in order to avoid consuming resources by waiting for a certain session process for a long time, the session waiting time is generally set, and once the time is exceeded, the entire process will end. Especially on the server side, since the number of managed devices is generally very large, it is impossible to set a long waiting time in a management task. Once the timeout expires, even if the client...

AI Technical Summary

Problems solved by technology

Especially on the server side, because the number of managed devices is generally very large, it is impossible to set a long waiting time in a management task. Once the timeout expires, even if the client retries the connection, the server cannot continue the unfinished management Task

Therefore, only a new management task can be re-initiated, which will lead to many unnecessary or repeated interaction processes

For example: the server needs to collect which applications are currently installed on the client. When there are many software installed on the terminal, the client needs to divide the data into multiple packets and transmit them to the server. Once there is a long-term interruption during the interaction process, the server can only restart Initiate a collection task, and the client can only report the installed application data from the beginning, and the previously reported data can only be repeatedly reported, resulting in traffic waste

Images