CN101772006A - Method and system for locking mobile terminal based on device management protocol - Google Patents

Abstract

The invention discloses a method and system for locking a mobile terminal based on a device management protocol, and relates to a server and a DM terminal based on the DM protocol. The method includes: the DM terminal pre-defines the extension of the application function that can be used for locking as a management object; When the application function needs to be locked, a lock request for the corresponding management object is sent to the server, and the corresponding application function is locked according to the lock command issued by the server. Based on the definition of the original LAWMO standard, the present invention enhances the scalability of the subsequent locking service of the terminal through the expansion of the <x> node, so that the locking of specific application functions in the terminal can be realized conveniently through the DM protocol.

Description

Method and system for locking mobile terminal based on device management protocol

technical field

The present invention relates to the implementation technology of Open Mobile Alliance (OMA, Open Mobile Alliance) Device Management (DM, Device Management) in the field of mobile communication, in particular to a method and system for locking a mobile communication terminal based on the DM protocol.

Background technique

With the increasingly rich and complex mobile data services, the service's dependence on terminals is getting higher and higher. As the carrier for users to use mobile services, mobile terminals have become an indispensable and important part of the mobile operation service system. In order to better enable the terminal to have the ability of rapid improvement to cope with the increasingly fierce market competition, and to perform remote management on terminal equipment more conveniently, efficiently and quickly, all operators and terminal manufacturers are committed to improving the remote management of terminal equipment. management ability.

The device management (DM, Device Management) technology of the Open Mobile Alliance (OMA, Open Mobile Alliance) mainly provides a management mechanism for distributed mobile communication devices, thereby optimizing user experience data and reducing operators' operating costs. It is used for management, diagnosis, information collection, and software management of terminal equipment. It manages parameter collection and/or configuration, firmware download, software download, installation and upgrade of terminal equipment and terminal software through the air (OTA, Over The Air) Bug fixes.

Recently, OMA has proposed a Locking and Writing Management Object (LAWMO, Locking and Writing Management Object) standard for terminal locking and erasing functions. In this standard, the management objects defined for the lock function include: <x>/Operations/FullLock and <x>/Operations/PartiallyLock, which define two functions of terminal full lock and partial lock. Specifically, OMA The definition of total locking and partial locking of the terminal is:

FullLock (all locked): the user cannot use the terminal at all (can only switch on and off);

PartiallyLock: The terminal can only answer incoming calls.

In this way, the locking of the DM terminal is limited to the above two operations, and the various application functions in the mobile terminal cannot be locked separately. Therefore, in actual use, the specific application function requirements on the user's locked terminal cannot be met. For example, the user wishes to only lock the short message application module, so that when the mobile phone is handed over to other people, the other party can only make calls, but cannot see the short messages on the mobile phone.

purpose of invention

The technical problem to be solved by the present invention is to provide a method and system for locking a mobile terminal based on a device management protocol, which can lock the application functions in the mobile terminal

In order to solve the above technical problems, the present invention provides a method for locking a mobile terminal based on a device management (DM) protocol, involving a DM protocol-based server and a DM terminal, the method comprising:

The DM terminal pre-defines the extension of the application function that can be used for locking as a management object; when the application function needs to be locked, it sends a lock request for the corresponding management object to the server, and locks the corresponding application function according to the lock command issued by the server .

Further, the DM terminal pre-defines the extension of application functions that can be used for locking as management objects, specifically including:

The DM terminal expands the application function to be a sub-node of the node for lock management in the DM management tree, and defines a lock ID for marking the locked object and a status ID for marking the locked state of the locked object under the sub-node.

Further, the DM terminal sends a locking request to the server through the locking function interface of the child node containing the management object locking identifier, and executes the locking according to the locking command issued by the server for the management object.

Further, the method also includes:

After the DM terminal is successfully locked, the locked status of the managed object is set to locked;

Or, when the lock is unsuccessful, the DM terminal continues to resend the lock request for the management object to the server, and locks the corresponding application function again according to the lock command returned by the server; or directly locks the corresponding application function again.

Further, the method also includes:

When the DM terminal needs to unlock the application function, it sends an unlock request for the corresponding management object to the server, and unlocks the corresponding application function according to the unlock command issued by the server.

In order to solve the above technical problems, the present invention provides a system for locking a mobile terminal based on a device management (DM) protocol, including a DM protocol-based server and a DM terminal, wherein:

The DM terminal is used to pre-define the extension of the application function that can be used for locking as a management object; when the application function needs to be locked, send a lock request for the corresponding management object to the server; lock the corresponding application function;

The server is configured to issue a lock command to the managed object after receiving the lock request.

Further, the DM terminal pre-defines the extension of the application function that can be used for locking as a management object, which means:

The application function is expanded to be a child node of the node used for lock management in the DM management tree, and a lock identifier for marking the locked object and a state identifier for marking the lock state of the locked object are defined under the child node.

further,

The DM terminal sends a locking request of the child node containing the management object locking identifier to the server through the locking function interface.

further,

After the DM terminal locks successfully, the lock state of the management object is set to lock; or, if the lock is unsuccessful, the DM terminal continues to resend the lock request for the management object to the server, and locks the corresponding lock again according to the lock command returned by the server. App function, or directly lock the corresponding app function again.

further,

When the DM terminal needs to unlock the application function, it sends an unlock request for the corresponding management object to the server, and unlocks the corresponding application function according to the unlock command issued by the server;

After receiving the unlock request, the server issues an unlock command for the managed object.

Compared with the prior art, the present invention solves the requirement that the user only needs to lock part of the application functions in the terminal through DM. Based on the definition of the original LAWMO standard, the present invention enhances the scalability of the subsequent locking service of the terminal through the expansion of the <x> node, so that the locking of specific application functions in the terminal can be realized conveniently through the DM protocol.

Description of drawings

Fig. 1 is the flow chart of the embodiment of the method for locking a mobile terminal based on the device management protocol of the present invention;

FIG. 2 is a structural block diagram of an embodiment of a system for locking a mobile terminal based on a device management protocol according to the present invention.

Detailed ways

The invention provides a method and system for locking a mobile terminal based on a device management protocol. The inventive idea is that the DM terminal defines extended application functions that can be used for locking as management objects; Lock request, lock the corresponding application function according to the lock command returned by the server.

The technical solutions of the present invention will be described in detail below in conjunction with the accompanying drawings and preferred embodiments. The following examples are only used to illustrate and explain the present invention, but not to limit the technical solution of the present invention.

As shown in Figure 1 is the flow of the embodiment of the method for locking a mobile terminal based on the device management protocol provided by the present invention, including:

Step 1: The DM terminal defines management objects for the application functions that can be used for locking;

The DM terminal defines the management objects that can be used for locking, and adds corresponding definitions in the management tree. Here, the SMS application module (sms) and the MMS application module (mms) are used as examples:

<x>/Operations

<x>/Operations/mms; expand the child nodes of the Operations node

<x>/Operations/mms/TobeLocked; define the mms module as a lockable object

<x>/Operations/mms/state; define whether the mms module is locked or not

<x>/Operations/sms; extend the child nodes of the Operations node

<x>/Operations/sms/TobeLocked; define the sms module as a lockable object

<x>/Operations/sms/state; defines whether the sms module is locked or not

Here, by extending the subnodes of the Operations node responsible for lock management in the DM management tree, the two subnodes FullLock/PartiallyLock are expanded into extensible <x> subnodes, representing different application modules, and in the <x> node Define the lock flag <ToBeLocked> to mark the child node as a lockable object, and define the state flag <state> under the <x> child node to mark the locked state of the object.

Step 2: When the DM terminal needs to lock the application function, it sends a lock request for the corresponding object to the server;

The user of the DM terminal can send a lock request of the <x> child node containing the lock identifier of the management object to the server through the webpage of the Internet (ie, the lock function interface).

Step 3: After receiving the request, the server issues a lock command to the lock child node corresponding to the object to be locked;

For example, to lock the mms module of the mobile phone, the server sends the exec command to the <x>/Operations/mms/TobeLocked node through the DM session.

Step 4: After receiving the command, the DM terminal performs a lock operation on the corresponding application function, and sets the lock state of the corresponding object to lock after the lock is successful.

For example, after the terminal receives the exec command, it executes the locking operation on the mms module, and sets the <x>/Operations/mms/state field as locked (for example, use 1 to indicate locked, use 0 to indicate unlocked).

After the DM terminal successfully locks the application function, it can still unlock the application function based on the DM protocol. The process is similar to the locking process, that is, the DM terminal first sends an unlock request to the server for the corresponding After the node corresponding to the object to be locked issues an unlock command, it performs an unlock operation on the corresponding application function, and sets the locked state of the corresponding object to unlocked after the unlock is successful.

When the terminal lock is unsuccessful, the lock state of the object is not changed. The terminal can take two ways to deal with the unsuccessful locking: one is to continue to resend the lock request for the object to the server, and lock the corresponding application function again according to the command returned by the server; the other is to directly target the corresponding object again App functions are locked.

As shown in Figure 2 is the embodiment of the system for locking mobile terminals based on the device management protocol of the present invention, the system includes a DM terminal (i.e. a terminal managed under the DM protocol) and a server, wherein:

The DM terminal is used to pre-define the management object for the application function that can be used for locking; when the application function needs to be locked, it sends a lock request for the corresponding object to the server, locks the corresponding application function according to the lock command returned by the server, and after the lock is successful Set the lock state of the object to locked;

The server is configured to issue a lock command to the lock node corresponding to the object to be locked after receiving the lock request.

The user of the DM terminal can send a locking request carrying the object name or identification to the server through a web page on the Internet (ie, the locking function interface). The server sends the exec command to the corresponding node through the DM session, that is, the lock command.

If the DM terminal fails to lock, it will continue to resend the lock request for the object to the server, and lock the corresponding application function again according to the command returned by the server; or directly lock the corresponding application function again.

When the DM terminal needs to unlock the application function, it sends an unlock request for the corresponding management object to the server, and unlocks the application function according to the unlock command issued by the server;

After receiving the unlock request, the server issues the unlock command for the managed object.

In summary, it can be seen from the above embodiments that the present invention is based on the definition of the original LAWMO standard, and through the expansion of the <x> node, the scalability of the subsequent locking service of the terminal is enhanced, so that the terminal can be conveniently implemented through the DM protocol. The locking of specific application functions solves the requirement that the user only needs to lock part of the application functions in the terminal through DM.

The above descriptions are only preferred embodiments of the present invention, and are not intended to limit the scope of the present invention. Any modification, equivalent substitution, improvement, etc. made within the spirit and principles of the present invention shall be included within the protection scope of the present invention.

Claims (10)

1. A method for locking a mobile terminal based on a device management (DM) protocol, relating to a server and a DM terminal based on the DM protocol, the method comprising: The DM terminal pre-defines the extension of the application function that can be used for locking as a management object; when the application function needs to be locked, it sends a lock request for the corresponding management object to the server, and according to the lock issued by the server The command locks the corresponding application function. 2. The method according to claim 1, wherein the DM terminal pre-defines the extension of the application function that can be used for locking as a management object, specifically including: The DM terminal expands the application function into a child node of a node used for lock management in the DM management tree, and defines a lock identifier for marking a locked object and a lock state for marking the locked object under the child node status identifier. 3. according to the method for claim 2, it is characterized in that, described DM terminal sends the described locking request that contains the described child node of described management object locking mark to described server through locking function interface, according to described server performing the locking with respect to the locking command delivered to the management object. 4. The method according to claim 3, further comprising: The DM terminal sets the locked state of the management object to locked after the locking is successful; Or, when the lock is unsuccessful, the DM terminal continues to resend the lock request for the management object to the server, and locks the corresponding application function again according to the lock command returned by the server; or directly locks the corresponding application function again. application functions. 5. The method according to any one of claims 1 to 4, further comprising: When the DM terminal needs to unlock the application function, it sends an unlock request for the corresponding management object to the server, and unlocks the corresponding application function according to the unlock command issued by the server. 6. A system for locking a mobile terminal based on a device management (DM) protocol, comprising a server and a DM terminal based on the DM protocol, wherein: The DM terminal is used to pre-define the extension of the application function that can be used for locking as a management object; when the application function needs to be locked, send a lock request for the corresponding management object to the server; The lock command locks the corresponding application function; The server is configured to issue the locking command to the managed object after receiving the locking request. 7. The system according to claim 6, wherein the DM terminal pre-defines the extension of the application function that can be used for locking as a management object, which means: The application function is expanded to be a child node of the node used for lock management in the DM management tree, and a lock ID for marking the locked object and a state ID for marking the lock state of the locked object are defined under the child node. 8. The system of claim 7, wherein: The DM terminal sends the locking request of the child node including the management object locking identifier to the server through a locking function interface. 9. The system of claim 8, wherein: After the locking is successful, the DM terminal sets the locking state of the management object to locked; or, when the locking is unsuccessful, the DM terminal continues to resend the management object to the server. lock the request, and lock the corresponding application function again according to the lock command returned by the server, or directly lock the corresponding application function again. 10. System according to any one of claims 6 to 9, characterized in that, When the DM terminal needs to unlock the application function, it sends an unlock request for the corresponding management object to the server, and unlocks the corresponding application function according to the unlock command issued by the server; After receiving the unlock request, the server issues the unlock command to the managed object.

Images