WO2009052732A1

WO2009052732A1 - Method, system and apparatus for terminal information protection

Info

Publication number: WO2009052732A1
Application number: PCT/CN2008/072661
Authority: WO
Inventors: Shouling Cui; Xiaoqian Chai; Kepeng Li; Linyi Tian
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2007-10-17
Filing date: 2008-10-10
Publication date: 2009-04-30
Also published as: CN102752741B; CN101415182A; JP2010516212A; CN102752741A; KR101118971B1; JP5447882B2; CN101415182B; KR20090087941A; JP5065416B2; JP2012065349A

Abstract

A method, a system and an apparatus are provided. The method includes: transmitting a lock instruction to a terminal from a first device management server, and wherein the instruction including lock information which instructs the terminal to lock all or part functions and carried by DM protocol; locking all or part of functions by the terminal according to the lock information. The solution makes a user lock functions on demands and provides the user good experience. A system for terminal information protection is also provided.

Description

Method, system and device for protecting terminal data

The embodiments of the present invention relate to the field of device management (DM), and in particular, to a method, system, and device for protecting terminal data in a DM. Background technique

The Open Mobile Alliance (ΟΜΑ) DM (hereinafter referred to as the DM specification) is the latest unified device management standard specification. The DM system provides a low-cost solution for third-party management and setting up wireless networks. The environment and configuration information of terminal devices (such as mobile phone terminals and functional objects in the terminal), solve the problems encountered during the use of these network devices, and perform software and firmware installation and upgrade operations through the wireless network (OTA) mode. And provide more personalized and personalized services to enhance the user experience.

With the heavy use of mobile terminals, a large number of important assets are concentrated on one mobile terminal. Once lost or forgotten, it will bring significant losses, for example, various data stored on the mobile terminal (including SMS, The impact of MMS, contacts, call logs, notepads, emails, photos, recordings, videos, etc.).

To solve these problems, the DM command is used to lock the terminal in the prior art. As shown in Figure 1, the DM server locks or unlocks the terminal by modifying the value of the TerminalSecurity/DeviceLock/LockLevel sub-node under the management tree in the terminal. If the value of the child node is true, the terminal is locked. If the value is false, the terminal is unlocked. In addition to the locking of the terminal, the DM server can also operate the TerminalSecurity/DeviceWipe node through the DM command, and issue a data erasure command to the node to instruct the terminal to erase all relevant data of the user saved by itself, including the expansion card. The data in .

Locking and unlocking of the terminal are implemented in the prior art, specifically, the terminal is locked. It is a lock on all functions; when unlocked, it can only be unlocked by the server that initiated the lock, and the user experience is poor. In addition, in the process of data erasing implemented in the prior art, only all data related to the user in the terminal can be erased, so that some useful data is also erased at the same time, the erasing effect is poor, and the user experience is also compared. difference.

Summary of the invention

The embodiment of the invention provides a method, a system and a device for protecting data of a terminal, so as to solve the problem that the authority control mechanism of the server existing in the prior art is unreasonable and the user experience is poor.

A method for protecting data of a terminal, the method comprising:

The first device management server sends a lock command to the terminal, where the lock command includes lock information indicating that the terminal locks all functions or locks some functions; and the command is carried by the device management DM protocol.

The terminal 4 locks all or part of the functions according to the locking command.

A method for protecting data of a terminal, the method comprising:

Saving the erasable data item of the terminal on the terminal management tree;

The device management server sends an erase command to the terminal according to the erasable data item, and the command is carried by the DM protocol;

The terminal erases the data item to be erased.

A system for protecting terminal data, the system comprising:

The first device management server includes a lock command issuing module, and is configured to send a lock command, where the command includes lock information indicating that the terminal locks all functions or locks some functions, and the command is carried by the device management DM protocol;

Terminal, including:

a first receiving module, configured to receive the locking command;

And a locking module, configured to lock all or part of the function according to the locking information. A system for protecting terminal data, the system comprising:

Device management server, including an erase command delivery module, for passing the DM protocol And issuing an erasing command, where the command carries an indication of one or more data items to be erased; the terminal includes:

a first receiving module, configured to receive an erase command issued by the device management server, and an erasing module, configured to erase a data item corresponding to the data item identifier.

Compared with the prior art, the embodiment of the present invention sends a lock information locking command including the lock information indicating that the terminal locks all functions or locks some functions to the terminal by the DM server, and the terminal locks the function indicated by the lock information. Users can lock as needed to make the user experience better. DRAWINGS

1 is a schematic diagram of a management tree structure for locking or unlocking a terminal in the prior art; FIG. 2 (a), FIG. 2 (b), FIG. 2 (c), FIG. 2 (d), and FIG. 2 (e) are A schematic diagram of a system structure for terminal data protection in the first embodiment of the present invention;

3 is a schematic flowchart of protecting terminal data in Embodiment 2 of the present invention; FIG. 4 is a schematic structural diagram of a terminal management tree according to an embodiment of the present invention;

FIG. 5 is a schematic flowchart of a terminal determining whether a DM server has an unlocking right according to Embodiment 3 of the present invention;

6 is a schematic flowchart of determining, by a terminal, whether a user has an unlocking right according to Embodiment 4 of the present invention;

7 is a schematic structural diagram of a terminal management tree in Embodiment 5 of the present invention;

8 is a schematic structural diagram of a terminal management tree in Embodiment 5 of the present invention;

9 is a schematic flowchart of a data item corresponding to a terminal erasing a data item identifier according to Embodiment 7 of the present invention;

FIG. 10 is a schematic structural diagram of a system for protecting data of a terminal according to Embodiment 9 of the present invention. detailed description

The invention will be described in detail below with reference to the accompanying drawings. As shown in FIG. 2( a ), FIG. 2 ( b ) and FIG. 2 ( c ), FIG. 2 is a schematic structural diagram of a system for protecting data of a terminal according to Embodiment 1 of the present invention, where the system includes: a first device management server 11 and a terminal 12 The first device management server 11 includes a lock command issuing module 21, configured to send a lock command, where the command includes lock information indicating that the terminal locks all functions or locks some functions; the terminal 12 includes a first receiving module. 31 and a locking module 32, wherein the first receiving module 31 is configured to receive the locking command; and the locking module 32 is configured to lock all or part of the function according to the locking information.

There are three situations in which information can be locked and partially locked:

The first case is as shown in FIG. 2( a ): the lock information is an identifier of whether all locks, and if the identifier is all locks, the lock module 32 is used to lock all functions; if the identifier is partially locked The lock module 32 is used to lock a preset function.

The second case is as shown in FIG. 2( b ): the lock information is a data item identifier corresponding to one or more data items to be locked; then the lock module 32 is configured to lock the data item corresponding to the identifier .

The first device management server 11 further includes an acquisition command issuing module 22 and a second receiving module 23, wherein the obtaining command issuing module 22 is configured to send an obtaining command to the terminal; and the second receiving module 23 is configured to receive the terminal reporting. The data item identifier; the terminal 12 further includes a storage module 33 and a reporting module 34, wherein the storage module 33 is configured to store a data item identifier corresponding to the data item that can be locked by itself; the reporting module 34 is configured to store the data item The data item identifier is reported to the first device management server 11.

The third case: the lock information is one of the IDs that are all locked, and/or the data item identifier corresponding to the data item to be locked. If the identifier is all locked, the locking module 32 is used to lock all functions; if the identifier is partially locked, the locking module 32 is used to lock a preset function; if the identifier is a data item identifier The locked information may also be a combination of all the lock identifiers and the data item identifiers, or a combination of the partial lock identifiers and the data item identifiers. In this embodiment, it is set whether the identifiers of all the locked identifiers have higher priority than the data item identifiers. , the locking module 32 can execute only all the locking labels The operation corresponding to the identification or partial locking is not performed, and the operation corresponding to the data item identification is not performed. After the above three locking processes, the DM server can instruct the terminal to unlock the locked function, that is, the so-called unlocking process in the embodiment of the present invention. In the embodiment of the present invention, the process of unlocking may be various, including but not limited to the following:

As shown in FIG. 2(c), if the lock command issuing module 21 is further configured to send a security password, the system further includes a second device management server 13 for delivering the data to the terminal 12. The terminal 12 further includes a first judging module 35 and an unlocking module 36, wherein the first judging module 35 is configured to determine the received security password and the first device management server delivered by the second device management server 13. The security passwords issued by the 11 are the same. When the same, the unlocking module 36 is triggered. The unlocking module 36 is configured to perform an unlocking operation.

2. As shown in FIG. 2(d), if the lock command issuing module 21 is further configured to send its own identifier, the terminal 12 further includes a second determining module 37, configured to use the second device management server. The identifier of 13 is compared with the identifier of the first device management server 11, and if the identifier is the same, the unlocking module 36 is instructed to perform an operation.

3. As shown in FIG. 2(e), if the lock command issuing module 21 is further configured to send an identifier that allows manual unlocking, the terminal further includes a third determining module 38, configured to receive the password. Compared with the preset password, if the password is the same, the unlocking module 36 is instructed to perform an operation.

If the lock command is sent to the unlocking password, the pre-set password is the issued unlock password.

If the lock command issuing module 21 is further configured to issue an identifier that allows unlocking with the local password, the preset password is a local password saved by the terminal itself.

The three unlocking methods shown in Fig. 2 (c), Fig. 2 (d) and Fig. 2 (e) can also be combined together, such as stepwise judgment according to the set priority conditions. When the set conditions are met, the terminal will be Unlock.

In the embodiment of the present invention, various commands and parameters sent by the DM server are carried by the DM protocol, and the parameters sent by the DM may be delivered together with the lock command or the unlock command, or may be the DM protocol. Issued separately. The method of the present invention is described in detail below in conjunction with specific embodiments.

The server involved in the embodiments of the present invention is a DM server. As shown in FIG. 3, it is a schematic flowchart of protecting terminal data in Embodiment 2 corresponding to Embodiment 1 of the present invention. In this embodiment, all or part of the functions of the DM server are first locked, and in the subsequent unlocking process, The function of the unlocked function is as follows: Step S301: The DM server sends a lock command to the terminal, where the command includes lock information, the lock information indicates that the terminal locks all functions, or locks some functions.

Step S302: After receiving the lock command, the terminal locks all functions or partial functions according to the lock information, and reports a response message indicating whether the lock is successful to the DM server.

In this embodiment and subsequent embodiments, the terminal locks all functions means: except for legally allowed sessions (eg, emergency call sessions) and DM sessions, the user will not be able to use the functions of the terminal, all external connections (such as Bluetooth) , USB connection, etc.) can not get the data of the terminal. The terminal locks part of the function means: The terminal or server predetermines the function to be locked when receiving the lock information, such as the call-in function, the legally allowed session, and the DM session, all other functions are locked. However, in order to subsequently enable the user to implement the unlocking process, the locked terminal can provide an input interface to receive the password entered by the user, which will be described in the subsequent embodiments.

There are three situations when implementing specific or partial functional locking:

The first case: the terminal and the server pre-agreed, when the terminal receives the lock information sent by the DM server as an all-locked identifier, if the identifier is all locked, the terminal locks all functions; if the identifier is part When locked, the terminal locks the preset function.

The second case: the lock information sent by the DM server to the terminal is the identifier of the data item that is to be locked. If the data item identifier includes all the data item identifiers that the terminal can lock, the terminal locks all functions; if the data item identifier The terminal identifies the data item corresponding to the identifier, and the terminal locks the data item corresponding to the identifier.

The third case: the lock information sent by the DM server to the terminal is one of the all locked identifiers, and/or the data item identifier corresponding to the data item to be locked. When locked If the information includes one of the above three types of identifiers, the operation is performed according to the first case or the second case; when the lock information includes one of the all locked identifiers and the data item identifier corresponding to the data item to be locked, due to Whether the priority of all the locked identifiers is higher than the data item identifier, the terminal only performs operations corresponding to whether the all locked identifiers are used.

Step S303: If the DM server also sends a security password to the terminal, the terminal can be unlocked as long as the DM server can correctly provide the security password during the unlocking process.

If the first DM server sends a security password when the terminal is locked, the second DM server that meets the access control authority (ACL) can initiate an unlocking command to the terminal, and if the unlocking command carries the correct security password, the terminal will Its own lock is released.

The DM server that originally issued the lock command and the user who knows the security password can also decode the terminal.

After the terminal is unlocked, a response message indicating whether the user is successfully unlocked is reported to the DM server. Step S304: The DM server sends an erasure command to the terminal, where the erasure command includes one or more data item identifiers corresponding to the data items to be erased.

Step S305: The terminal erases the data item corresponding to the identifier saved by the terminal, and reports to the DM server whether the response message is successfully erased.

In this embodiment, the data item to be erased is a data content information classification in the terminal, such as a short message, a multimedia message, an address book, a call record, a notepad, a mail, a photo, a recording, a video, a password, etc., and the terminal receives the wipe. In addition to the command carrying one or more identifiers indicating the data items to be erased, the terminal erases the data items to be erased.

Step S304 and step S305 and the foregoing steps S301 to S303 have no absolute sequence, and the erasing command may be issued before the terminal is locked, or may be executed after the terminal is locked.

The solution in the embodiment of the present invention may be implemented by using a terminal management tree. The commands sent by the DM server may be operations on nodes in the terminal management tree. The following sections describe the locking, unlocking, and erasing data of the terminal in detail.

As shown in FIG. 4, in order to implement a structure diagram of a terminal management tree in the embodiment of the present invention, the locking and solution of the terminal can be implemented by operating some or all of the nodes in FIG. Lock and erase data operations.

Embodiment 3 of the present invention describes a solution for realizing data protection for a terminal by locking and unlocking the terminal. As can be seen from FIG. 4, a Lock sub-node is generated under the Operation node, and the Lock sub-node is an executable node. The lock command issued by the DM server can be received, and the corresponding operation is performed. The description of the Lock sub-node is as shown in Table 1.

Table 1

After the lock command sent by the DM server is received by the terminal, the parameter information carried in the command is saved in each sub-node of the LockConfig node. These sub-nodes are described in detail below:

The LAWMO/LockConfig/IsFullLocked subnode is used to hold the lock information. The value of the IsFullLocked subnode is true or false. When the value is true, it indicates that the terminal will lock all functions. When it is false, it indicates that the terminal will lock some functions. The description of the IsFullLocked subnode is shown in Table 2.

Table 2

The LAWMO/LockConfig/Security Code sub-node is used to save the security password sent by the DM server, and is used to verify the identity of the DM server that needs to be unlocked. The number of occurrences of the child node is 0 or 1. If the DM server does not send a security password, the node may not exist. The description of the Security Code sub-node is shown in Table 3. Status Tree Occurrence Format Min.Access Types

REQUIRED ZeroorOne Character ( Chr ) No Get, Replace Table 3

The LAWMO/LockConfig/Server ID sub-node is used to save the ID of the DM server that issued the lock command. If the DM server subsequently requests to unlock the terminal, the AAA server may not need to verify the security password, as long as it passes through the server ID sub-node. The ID information determines that the terminal is required to be locked and the same DM server is required to be unlocked, and the unlocking operation is performed. The description of the Server ID sub-node is shown in Table 4.

Table 4

The LAWMO/Operation/UnLock sub-node is an executable node that receives the unlock command issued by the DM server and performs an unlock operation. The description of the UnLock subnode is shown in Table 5.

The LAWMO/Operation/UnLock/SecurityCode sub-node is used to match the security password in the received unlock command with the security password saved in LAWMO/LockConfig/SecurityCode to verify the unlocking authority of the DM server that issued the unlock command. The description of the UnLock/SecurityCode subnode is shown in Table 6.

Table 6 Through the description of several nodes in Tables 1 to 6, the locking and unlocking scheme of the third embodiment of the present invention is as follows:

S1. The first DM server sends a lock command to the LAWMO/Operation/Lock executable node of the terminal, where the lock command carries the lock information, the security password, and the ID information of the lock.

In this embodiment, the lock information, the security password, and the ID information of the user may be delivered together with the lock command, or may be directly sent by the DM server using the DM protocol.

If the first DM server wants to lock all the functions of the terminal and only allows the legally allowed session and the DM session, the lock information may be an identifier of whether or not all locks, the identifier may be a parameter of IsFullLocked, and its value is true. If the terminal needs to maintain the incoming call function, set the value of the issued IsFullLocked parameter to false.

After the first DM server locks the terminal, if you want to assign the unlocking authority to the second DM server, you need to send the SecurityCode parameter. When the second DM server unlocks the terminal, you need to provide SecurityCode to verify the permission.

If the first DM server does not set SecurityCode, you can set it to any other DM server to unlock the terminal, or any other DM server does not have the right to unlock. In addition, when the first DM server that issues the lock command initiates the unlock command again, the SecurityCode may not be provided, and the terminal may determine the authority of the first DM server through the recorded Server1D.

When the parameters of IsFullLocked, SecurityCode, and Server1D are delivered by the first DM server, and the parameters such as UnlockCode are sent later, the parameters can be directly delivered by the Replace command. The following is a specific implementation example:

<Item>

<LocURI>/LAWMO/LockConfig/IsFullLocked

</LocURI>

</Target> <Data>true</Data><!— IsFullLocked value~>

</Item>

<Item>

<LocURI>/LAWMO/LockConfig/SecurityCode

</LocURI>

</Target>

</Replace>

52. After receiving the lock command, the terminal assigns the parameter carried in the lock command to the corresponding node, and performs a lock operation according to the parameter.

After receiving the security password, the terminal assigns the value of the security password to the LAWMO/LockConfig/SecurityCode node. After receiving the lock information, the terminal assigns the lock information value to the LAWMO/LockConfig /IsFullLocked node. The terminal extracts the ID of the DM server that issued the lock command from the DM session, and assigns the ID value to the LAWMO/LockConfig/ServerlD node.

After receiving the Lock command, the terminal performs corresponding operations according to the parameters carried.

If the first DM server that sends the lock command to the terminal requests to be unlocked, the unlock command is sent to the LAMO/Operation/UnLock node of the terminal; otherwise, the second DM server needs to carry the security password when sending the unlock command to the terminal. .

The second DM server can send security passwords in two ways:

The Replace command directly delivers the parameters, and the second is carried by the data element in Exec. The specific implementations of the two schemes are as follows:

1. Directly issue parameters through the Replace command.

<LocURI>/LAWMO/Operation/UnLock/SecurityCode

</LocURI>

</Target>

</Item>

</Replace>

<Exec>

<Item>

<LocURI>/LAWMO/Operation/Unlock </LocURI>

</Target>

</Item>

</Exec>

</Sequence>

2. Carry the parameters with the Data element in the Exec command.

Methods as below:

<Exec>

<Item>

<LocURI>/LAWMO/Operation/Unlock </LocURI> </Target>

</Item>

</Exec>

S4. After receiving the unlocking command, the terminal determines whether the second DM server has an unlocking function. Permissions, if yes, perform an unlock operation, otherwise, refuse execution and return an error message.

The authentication process of the terminal to the DM server is shown in Figure 5. The process mainly includes the following steps:

Step S501: The terminal determines whether the ID of the second DM server that sends the unlock command is the same as the ID of the first DM server that sends the lock command. If yes, step S504 is performed. Otherwise, step S502 is performed.

The terminal extracts the ID of the second DM server that sends the unlocking command from the DM session. If the DM server that sends the command twice is the same, the second DM server has the unlocking authority by default, and the terminal directly performs the unlocking operation. If the server that issued the command is different, you need to continue to determine whether the second DM server that issued the unlock command has the unlock permission.

Step S502: The terminal determines whether the security password is carried in the lock command. If yes, step S503 is performed. Otherwise, step S504 is performed.

If the security password is saved in the LAMO/LockConfig/SecurityCode sub-node, the matching security password is required to be sent when the unlock command is sent. If the security password is not carried in the original lock command, the DM server can be unlocked by default. Permission, the terminal directly performs the unlock operation.

Of course, in other instances, you can also set: If the security command is not carried in the lock command, the default is that the DM server except the DM server that issued the lock command has no permission to unlock.

Step S503: Determine whether the security password carried in the unlocking command matches the security password carried in the locking command. If yes, go to step S504; otherwise, go to step S505.

If the second DM server that issued the unlocking command provides the security password, the second DM server that issues the unlocking command is considered to be the same as the security password carried in the locking command. Has unlock permission.

Step S504: The terminal performs an unlocking operation.

Step S505: The terminal maintains the original locked state.

Whether the terminal is unlocked or not, after the step S504 or the step S505 is performed, the terminal is The security password saved in the LAWMO/Operation/UnLock/SecurityCode node will be cleared to prevent it from being used by the next unlock command.

In S4, the second DM server is authenticated by comprehensively determining the DM server ID and the security password. This is only a case of the embodiment of the present invention. The terminal may also use other different judgment sequences, or may only use The second DM server is authenticated according to the DM server ID or the security password.

Through the description of the third embodiment, the process of locking the terminal by the first DM server and unlocking by the second DM server is completed. In the fourth embodiment of the present invention, a process for manually unlocking by a user is further provided, which mainly includes the following steps:

The DM server sends a lock command to the terminal, and the command includes an identifier that allows manual unlocking.

The process of issuing the lock command in this step is similar to that in the third embodiment. The DM server can also send the parameter information that is sent together with the lock command in the first step of the third embodiment, and the user can be implemented in this embodiment. Manually unlocking, the DM server can also be implemented to unlock according to the third embodiment.

The lock command may carry an identifier indicating whether manual unlocking is allowed, and the identifier indicates whether the terminal is allowed to manually unlock by inputting an unlock password by the user. The terminal saves the identifier to the LAWMO/LockConfig/AllowLocallyUnlock sub-node. If the identifier is true, the user is allowed to unlock the terminal. If the identifier is false, the user is not allowed to unlock the terminal. The description of the AllowLocallyUnlock subnode is shown in Table 7.

If the identifier is not carried in the lock command, it can be manually unlocked by default, or the manual unlock is not allowed by default.

Table 7

The DM server allows the user to manually unlock, and the lock command may also include a solution. Lock the password, the terminal saves the received unlock password to

In the LAWMO/LockConfig/UnLockCode sub-node, the unlock password is the check code when the user manually unlocks. If the user correctly inputs the unlock password to the terminal when unlocking, the user is considered to have the decoding right. The description of the LAWMO/LockConfig/UnLockCode sub-node is shown in Table 8.

Table 8 In addition to unlocking the terminal with the unlock password, the user can also use the terminal's local password to unlock. In this case, the lock command also carries an identifier that allows the unlocking with the local password, and the terminal saves the identifier in the LAWMO/LockConfig/LocalPwdAvailable sub-node. If the identifier is true, the user is allowed to input the local password. To unlock the terminal's LAW MO level; if the value is false, it means not allowed. The description of the LocalPwdAvailable subnode is shown in Table 9.

Table 9

S2. After receiving the unlocking command, the terminal determines whether the user who inputs the unlocking password has the right to unlock. If yes, the unlocking operation is performed. Otherwise, the execution is refused.

The authentication process of the terminal to the user is as shown in FIG. 6. The process mainly includes the following steps: Step S601: If the terminal determines that the identifier saved in the LAWMO/LockConfig/AllowLocallyUnlock sub-node is true, step S602 is performed, and if it is false, the process is performed. Step S607.

When the value is true, it means that the user is allowed to manually unlock by entering a password. When the value is false, it means that the user is not allowed to manually unlock, no matter what the user inputs to the terminal. The password will keep the terminal locked.

Step S602: The terminal determines whether the unlock password is saved. If yes, step S603 is performed; otherwise, step S604 is performed.

If the LAWMO/LockConfig/UnLockCode subnode value is blank, further determination is required to allow the user to unlock using the terminal's native password.

Step S603: The terminal determines whether the received unlock password input by the user matches the saved unlock password. If yes, step S606 is performed; otherwise, step S607 is performed.

The password matching involved in the various embodiments of the present invention can be considered as the same password.

The terminal can provide the user with a UI interface through which the user can enter a password, regardless of whether the terminal is in the full function lock state or in the state in which the set function is locked.

Step S604: The terminal determines whether the user is allowed to use the local password to unlock. If yes, step S605 is performed; otherwise, step S607 is performed.

Step S605: The terminal determines whether the received local password input by the user matches the saved local password. If yes, step S606 is performed; otherwise, step S607 is performed.

Step S606: The terminal is unlocked.

Step S607: The terminal remains in a locked state.

In S2, the user is manually unlocked by using the unlocking password unlocking and the local password unlocking. In the embodiment of the present invention, the terminal may also use other different order to judge, or only unlock according to the unlocking password or the local device. The way to unlock the password is to achieve manual unlocking.

The two processes for implementing terminal locking and unlocking described in Embodiment 3 and Embodiment 4 of the present invention are based on the terminal management tree described in FIG. 4. In fact, FIG. 4 is only one implementation of the solution of the present invention. In the case, the structure of the terminal management tree may also be the structure shown in FIG. 7. In this structure, the <Y>* child node under the LockConfig node is used instead of the LAWMO/LockConfig/IsFullLocked node in FIG. 4, LAWMO /LockConfig/ SecurityCode node, LAWMO/LockConfig/UnlockCode node, LAWMO/LockConfig/ServerlD node, LAWMO/LockConfig One or more of the /AllowLocallyUnlock node and the LAWMO/LockConfig/LocalPwdAvailable node, etc., of course, the present embodiment is not limited to the above several nodes.

Based on the management tree structure shown in FIG. 7, the process of implementing the locking and unlocking in the fifth embodiment of the present invention is similar to the process in the third embodiment and the fourth embodiment. When the DM server issues the locking command, it will be IsFullLocked, SecurityCode, UnlockCode, ServerlD,

One or more of the AllowLocallyUnlock and LocalPwdAvailable parameters are also sent to the terminal and saved in the <Y >* node. The terminal then sets the lock status according to these parameters and configures the terminal's unlock permission.

The specific delivery process can be described by the following procedure. The procedure only describes the process of the security password, and the other parameters are similar.

<Add>

<Item>

<Target><LocURI>LAWMO/LockConfig/SecurityCode</LocURI> </Target>

</Item>

</Add> Embodiments 3 through 5 provide various schemes for terminal data protection, corresponding to the system described in Embodiment 1.

In addition to the terminal data protection by means of locking the terminal as described in the foregoing embodiment, the sixth embodiment of the present invention further provides protection of the terminal data by locking the data item. So-called data items include, but are not limited to, short messages, contact information, and email. The list of data item information can be saved in the LAWMO/OperableContent/<X> node, as shown in Figure 4, and its content can be determined by the terminal. The description of the node is shown in Table 10.

Table 10 To achieve this capability, on the basis of Figure 4, a child node <X>* is generated under the Lock node, as shown in Figure 8. The X node stores the name of the data item that the DM server requires to lock. In this case, the IsFullLocked subnode may not be required under the LockConfig node.

The process of locking and unlocking the data items of the terminal item by item in the sixth embodiment of the present invention includes the following steps:

1. The DM server sends an acquisition command and obtains a data item that the terminal can lock.

The DM server can use the Get command to get the terminal management tree.

The value of the LAWMO/OperableContent/<X> node, the specific implementation process can be as follows:

(1) The DM server requests to obtain an identifier of the lockable data item.

<Get>

<Item>

<LocURI>/LAWMO/Operablecontent </LocURI>

</Target>

</Item>

</Get>

(2) The terminal returns the content under the OperableContent node to the DM server by using the Results command.

If the content under the OperableContent node is short message (SMS), address book

(AddressBook) and SIM card information (SIMCard), the message returned by the terminal to the DM server is as follows:

<MsgRef K/MsgRef <CmdRef 4</CmdRef

<Item>

<LocURI>/LAWMO/Operablecontent </LocURI> </Source>

<Data>SMS/AdressBook/SimCard/</Data>

</Item>

</Results>

In this embodiment, step 1 may not appear. For example, the data agreed by the terminal and the server, or the data items that have been standardized.

The DM server sends a lock command to the terminal, where the command includes one or more data item identifiers corresponding to the data items to be locked, and the terminal locks the data item corresponding to the identifier.

When the DM server issues a lock command, other parameters can be delivered according to the schemes of Embodiments 3, 4, and 5.

The DM server can use the data element in the Add command, the Replace command, or the Exec command to deliver the data item identifier. The process of delivering the data element in the Exec command and the process in the third embodiment is similar to the process in the third embodiment, and is not described here. The process of sending an identifier using the Add command is as follows:

<Add>

<Item>

</Target>

<Data>AdressBook</Data>

</Item>

</Add>

<Exec>

<Item>

<Target> <LocURI>/LAWMO/Operation/Lock</LocURI></Target>

</Item>

</Exec>

</Sequence> After receiving the lock command, the terminal determines whether there is a child node under the Lock node, or the content of the child node is empty, indicating that the DM server does not specify a data item to be locked, and the terminal may follow the third and fourth embodiments. The solution of the fifth is locked; if the terminal determines that the content of the child node under the Lock node is SMS and AddressBook, the terminal locks the SMS and AddressBook functions, that is, the terminal cannot send and receive text messages, and cannot view or modify the phone.

3. The terminal unlocks according to the unlock command issued by the DM server.

This unlocking process can be similar to the ones in the third, fourth and fifth embodiments.

The third embodiment and the sixth embodiment of the present invention respectively describe two schemes for performing full locking or partial locking on the terminal, and the two schemes can also be combined to realize full locking or partial locking of the terminal. E.g:

1. Set the IsFullLocked subnode to tristate, with values 0, 1, and 2, respectively. If the value is 0 or 1, it indicates that the lock information sent by the DM server is the identifier of the lock. The operation is performed according to the scheme of the third embodiment. When the value is 2, the lock information sent by the DM server is The data item identifier corresponding to the data item to be locked is performed according to the scheme of the sixth embodiment. At this time, the three identifiers in the issued lock information are in the relationship of "or"; when the values are 0 and 2 (or 1 and 2), at this time, whether the lock information of all the lock information and the data item identifier are "and" in the lock information, indicating that the lock information is the identifier of all (partial) lock, but the child under the lock node If one or more data item identifiers are added to the node <X>*, the schemes of the third embodiment and the sixth embodiment can be simultaneously performed. Further, if it is set whether the priority of the all-locked identifier is higher than the data item identifier, the operation may be performed according to the scheme of the third embodiment, and the scheme of the sixth embodiment is not executed.

However, if it is set whether the priority of all locked identifiers is lower than the data item identifier, press The operation of the embodiment 6 is performed, and the solution of the third embodiment is not executed.

In the seventh embodiment of the present invention, a solution for protecting data of a terminal by erasing the content of the terminal item by item is provided, and the solution includes:

1. The DM server obtains a data item that the terminal can erase.

The DM server can obtain the erasable data item of the terminal before issuing the erasing command, and the obtaining manner is similar to that in the sixth embodiment. In addition, this step may not appear. The data items are the same, that is, the values of the child nodes under the LAWMO/OperableContent node. Other nodes can also be generated under the terminal management tree to save data items that the terminal can erase.

2. The DM server sends an erasure command to the terminal, where the command carries one or more data item identifiers corresponding to the data items to be erased by the terminal.

The erase command issued by the DM server is to operate the LAWMO/Operation/wipe executable node under the terminal management tree. The description of the wipe node is shown in Table 11.

Table 11 There may also be a child node <X>* under the wipe node. This node holds the data item identifier corresponding to the data item that the DM server wishes to erase when executing the erase command. The description of the node is shown in Table 12.

Table 12

The DM server sends one or more data item identifiers corresponding to the data items to be erased by the terminal. There are two ways to deliver the parameters, one is to directly send the parameters through the Replace command, and the second is to use the data in the Exec. The element is carried, similar to the process of the sixth embodiment. 3. The terminal erases the data item corresponding to the data item identifier. As shown in FIG. 9, the process may include:

In step S901, if there is no X child node or the X child node value is null under the LAWMO/Operation/wipe node of the terminal, that is, the data item identifier corresponding to the data item to be erased by the terminal is not delivered, step S904 is performed, otherwise execution is performed. Step S902.

Step S902: The terminal determines whether the data item identifier that is erasable by the terminal includes the received data item identifier. If yes, step S903 is performed; otherwise, step S905 is performed.

Step S903: The terminal erases the data item corresponding to the received data item identifier. If the DM server sends a data item identifier to the terminal, the command is as follows:

<Exec>

<Item>

<LocURI>/LAWMO/Operation/Wipe </LocURI>

</Target>

<Data>AddressBook </Data>

</Item>

</Exec> The terminal erases the data corresponding to the phone book, and the erasing process ends.

Step S904: The terminal erases all data of the user according to the erasure command, including data on the storage space of the device, data on the extended storage medium, and even data on the SIM card.

Step S905: The terminal refuses to perform an erase operation.

Embodiment 7 of the present invention describes a scheme for realizing data protection for a terminal by erasing the content of the terminal item by item. For the seventh embodiment, there is an alternative, that is, a slight modification to the second step in the embodiment. In the second step of the seventh embodiment, the DM server sends an erase command to the terminal, and sends a data item identifier corresponding to the data item to be erased by one or more terminals; the difference of the alternative is that the DM server The terminal sends an erase command and delivers an indication of the data item to be erased on one or more terminals. The indication may be the name of the data item to be erased, the identifier of the data item to be erased, or the erasure indication of the erasable data item on the terminal management tree.

There are two ways for the DM server to deliver the indication. One is to directly send parameters through the Replace command, and the second is to use the data element in Exec. The specific method is similar to the procedure in the sixth embodiment.

After receiving the erase command, the terminal erases the data item to be erased.

In the terminal performing an erase operation, erasing the password is a more specific embodiment.

In addition to instructing the terminal to erase the password, the DM server can also instruct the terminal to modify or set the password.

The eighth embodiment of the present invention is a method for a terminal to erase and modify a password, and the method mainly includes the following steps:

1. The DM server sends an erase command to the terminal.

At this time, similar to the eighth embodiment, the DM server issues a command to erase the password on the terminal by operating the Wipe executable node. The LAWMO/LocalLock/ClearPwd sub-node can also be operated under the terminal management tree. The sub-node is used to erase the password on the terminal. The description of the sub-node is shown in Table 13.

Table 13

The instructions for the DM server to operate on the ClearPwd subnode are as follows:

<Exec>

<Item>

<LocURI>/LAWMO/LocalLock/ClearPwd </LocURI> </Target>

</Item>

</Exec> If you want to reconfigure a new password after erasing the password, you can operate the LAWMO/LocalLock/ChangerPwd sub-node under the terminal management tree. This sub-node is used to modify the password on the terminal. The description is shown in Table 14.

Table 14

The instructions for the DM server to operate on the ChangePwd subnode are as follows:

<Exec>

<Item>

<LocURI>/LAWMO/LocalLock/ChangePwd </LocURI>

</Target>

</Item>

</Exec>

2. After the DM server sends a new terminal password, the terminal replaces the original terminal password, and the received new terminal password is used as its own terminal password; or the terminal receives the new terminal password to overwrite the original terminal. password.

In Fig. 4, in addition to the description of each of the above nodes, a LAWMO/Operation/FactoryReset subnode can be generated under the terminal management tree. The child node is an executable node, and the DM server can operate the node to instruct the terminal to set its own parameter to the factory value. The description of the node is shown in Table 15.

Table 15 In addition, a LAWMO/State node can be generated, which is used to reflect whether the state of the current terminal is locked. According to different values, different states of the terminal are reflected. For example, when the value of the node is set to 0, the terminal is locked and locked for all functions. When the value of the node is 1, the terminal is locked and set. The function is locked. When the value of the node is 2, the terminal is in the unlocked state. When the value of the node is 3, the terminal is in other states.

The various aspects of the third embodiment to the eighth embodiment of the present invention can be combined to form a new one.

For the seventh embodiment and the eighth embodiment of the present invention, the ninth embodiment of the present invention further provides a system for protecting data of the terminal. As shown in FIG. 10, the system includes: a device management server 41, including an erasure command issuing module 51. The command is used to send an erase command, where the command carries one or more data item identifiers corresponding to data items to be erased, and the command is carried by the DM protocol; the terminal 42 includes a first receiving module 61 and an erasing module 62. The first receiving module 61 is configured to receive an erase command issued by the device management server 41, and the erasing module 62 is configured to erase the data item corresponding to the data item identifier.

The device management server 41 further includes an acquisition command issuing module 52 and a second receiving module 53, wherein the obtaining command issuing module 52 is configured to send an obtaining command to the terminal; and the second receiving module 53 is configured to receive data reported by the terminal. Item identifier. The terminal 42 further includes a storage module 63 and a reporting module 64, wherein the storage module 63 is configured to save the data item identifier corresponding to the data item that can be erased by itself; the reporting module 64 is configured to report the stored data item identifier. The server is managed by the device.

If the data item identifier includes a terminal password identifier, and the erasure command is sent by the module 51, the terminal further includes a setting module 65, configured to erase the original terminal password, and receive the The new terminal password is used as its own terminal password; or the terminal will overwrite the original terminal password with the new terminal password received.

Through the method and system described in the embodiments of the present invention, the user can lock some or all functions of the terminal according to requirements, and the permission control mechanism is more reasonable, and is more flexible in the unlocking process, which facilitates the user and reduces the pressure of the DM server; , allowing single or multiple erasure of the terminal's operable content, improving the erasing efficiency. Through the description of the above embodiments, those skilled in the art can clearly understand that the present invention can be implemented by hardware, or can be implemented by means of software plus necessary general hardware platform, and the technical solution of the present invention. It can be embodied in the form of a software product that can be stored in a non-volatile storage medium (which can be a CD-ROM, a USB flash drive, a mobile hard disk, etc.), including a number of instructions for making a computer device (may It is a personal computer, a server, or a network device, etc.) that performs the methods described in various embodiments of the present invention.

In conclusion, the above description is only a preferred embodiment of the present invention and is not intended to limit the scope of the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and scope of the present invention are intended to be included within the scope of the present invention.

Claims

Rights request

A method for protecting data of a terminal, the method comprising: the first device management server sends a lock command to the terminal, where the lock command includes indicating that the terminal locks all functions or locks some functions. Locking information, and the command is carried by the device management DM protocol;

The terminal 4 locks all or part of the function according to the lock command.

The method for protecting data of a terminal according to claim 1, wherein the lock information is an identifier of whether all of the locks are locked, and if the identifier is all locked, the terminal locks all functions; When the identification is partially locked, the terminal will lock some functions.

The method for protecting data of a terminal according to claim 1, wherein the lock information is a data item identifier corresponding to one or more data items to be locked, and the terminal corresponding data of the identifier Item lock.

The method for protecting the data of the terminal according to claim 3, wherein before the sending, by the first device management server, the lock command to the terminal, the method further includes:

The first device management server sends an acquisition command to the terminal;

The terminal sends the saved data item identifier corresponding to the data item that can be locked by itself to the first device management server.

The method for protecting data of a terminal according to claim 1, wherein the lock information is one of an identifier that is all locked, and/or a data item identifier corresponding to the data item to be locked;

If the identifier is all locked, the terminal locks all functions; if the identifier is partially locked, the terminal locks a preset function; if the identifier is a data item identifier, the terminal Locking the data item corresponding to the data item identifier.

The method for protecting data of a terminal according to claim 5, wherein whether the all-locked identifier has a higher priority than the data item identifier.

The method for protecting data of a terminal according to claim 1, 2, 3 or 5, wherein, if the first device management server further sends a security password to the terminal, the terminal according to the lock information After locking all or part of the functionality, it also includes:

And the second device management server sends an unlocking command and a security password to the terminal; if the terminal determines that the received security password sent by the second device management server is the same as the security password sent by the first device management server, performing the unlocking operation. .

The method for protecting data of a terminal according to claim 7, wherein, if the first device management server further sends its own identifier to the terminal, the method further includes:

The terminal compares the identifier of the second device management server that sends the unlock command with the identifier of the first device management server. If the identifiers are the same, the unlocking operation is performed.

The method for protecting data of a terminal according to claim 1, 2, 3 or 5, wherein if the first device management server further sends an identifier that allows manual unlocking to the terminal, the user is allowed to manually connect the terminal. Unlock.

The method for protecting data of a terminal according to claim 9, wherein, if the first device management server further sends an unlocking password to the terminal, the unlocking process includes: after the terminal receives the unlocking password input by the user, If it is determined that the unlock password is the same as the received unlock password, an unlocking operation is performed.

The method for protecting data of a terminal according to claim 9, wherein if the first device management server further sends an identifier to the terminal that is allowed to be unlocked by using the local password, the unlocking process includes:

After the terminal receives the local password input by the user, if it is determined that the local password is the same as the local password saved by itself, the terminal performs an unlocking operation.

12. A method for protecting data of a terminal, the method comprising: storing an erasable data item of the terminal on a terminal management tree;

And the device management server sends an erasing command to the terminal according to the erasable data item, and the command is carried by the DM protocol;

The terminal erases the data item to be erased.

The method for protecting data of a terminal according to claim 12, wherein the erasing command is sent to the terminal according to the erasable data item, and the feature is:

The device management server issues an erase command to the terminal, the erase command carrying an indication of one or more data items to be erased.

The method for protecting data of a terminal according to claim 13, wherein: the indication of the data item to be erased may be a data item identifier.

The method for protecting data of a terminal according to claim 13, wherein: the indication of the data item to be erased may be a name of the data item or an indication of whether the data item on the terminal management tree is erased.

The method for protecting the data of the terminal according to claim 12, wherein before the device management server sends the erasure command to the terminal, the method further includes:

The device management server sends an acquisition command to the terminal;

The terminal sends the data item identifier corresponding to the erasable data item saved by the terminal to the device management server.

The method for protecting data of a terminal according to claim 16, wherein the data item identifier comprises a terminal password identifier.

The method for protecting data of a terminal according to claim 17, wherein the device server sends a new terminal password, and after the terminal erases the original terminal password, the received new terminal password is used as its own. Terminal password; or

The terminal will overwrite the original terminal password with the new terminal password received.

A system for protecting data of a terminal, wherein the system includes: a first device management server, including a lock command issuing module, configured to send a lock command, where the command includes indicating that the terminal will perform all functions. Locking or locking information about partial functions, and the command is carried by the device management DM protocol;

Terminal, including:

a first receiving module, configured to receive the locking command;

And a locking module, configured to lock all or part of the function according to the locking information.

The system for protecting data of a terminal according to claim 19, wherein the lock information is an identifier of whether all of the locks are locked, and if the identifier is all locked, the lock module is configured to lock all functions. ;

If the identifier is partially locked, the locking module is configured to lock a preset function.

The system for protecting data of a terminal according to claim 19, wherein the lock information is a data item identifier corresponding to one or more data items to be locked; and the locking module is configured to: Identifies the corresponding data item lock.

The system for protecting data of a terminal according to claim 21, wherein the device management server further comprises:

Obtaining a command issuing module, configured to send an obtaining command to the terminal;

a second receiving module, configured to receive a data item identifier reported by the terminal;

The terminal further includes:

a storage module, configured to store a data item identifier corresponding to a data item that can be locked by itself;

The system for protecting data of a terminal according to claim 19, wherein the lock information is one of an identifier that is all locked, and/or a data item identifier corresponding to the data item to be locked;

If the identifier is all locked, the locking module is configured to lock all functions; if the identifier is partially locked, the locking module is configured to lock a preset function; if the identifier is The data item identifier is used by the locking module to lock the data item corresponding to the data item identifier.

The system for protecting data of a terminal according to claim 19, wherein the identifier of the all locked identifier has a higher priority than the data item identifier.

The system for protecting data of a terminal according to claim 19, wherein, if the lock command is sent to the module, the system further includes:

a second device management server, configured to send an unlock command and a security password to the terminal;

The terminal further includes a first determining module and an unlocking module, where:

The first determining module is configured to determine whether the received security password sent by the second device management server is the same as the security password sent by the first device management server, and when the same is the same, triggering the unlocking module;

The unlocking module is configured to perform an unlocking operation.

The system for protecting the data of the terminal according to claim 25, wherein, if the locking command is sent by the module, the module is further configured to send the identifier of the terminal,

The terminal further includes:

The second determining module is configured to compare the identifier of the second device management server with the identifier of the first device management server, and if the identifier is the same, instruct the unlocking module to perform an operation.

The system for protecting the data of the terminal according to claim 25, wherein, if the locking command is sent to the module, and the identifier is further used to enable the manual unlocking, the terminal further includes:

The third determining module is configured to compare the received password with a preset password, and if the password is the same, instruct the unlocking module to perform an operation.

The system for protecting the data of the terminal according to claim 27, wherein, if the lock command issuing module is further configured to send an unlock password, the preset password is the issued Unlock your password.

The system for protecting data of a terminal according to claim 27, wherein, if the lock command is sent to the module, and the identifier for unlocking with the local password is issued, the preset password is used. The local password saved for the terminal itself.

30. A system for protecting data of a terminal, the system comprising: a device management server, comprising: an erase command issuing module, configured to send an erase command by the DM protocol, where the command carries one or An indication of a plurality of data items to be erased; the terminal includes:

The system for protecting data of a terminal according to claim 30, wherein the device management server further comprises:

The terminal further includes:

a storage module, configured to save a data item identifier corresponding to the data item that can be erased by itself; Server.

The system for protecting data of a terminal according to claim 30, wherein, if the data item identifier includes a terminal password identifier, and the erasing command issuing module is configured to send a terminal password, The terminal also includes:

a setting module, configured to erase the original terminal password, and receive the new terminal password as its own terminal password; or