KR20090087941A - Method, system and apparatus for terminal information protection - Google Patents

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. ® KIPO & WIPO 2009

Description

METHOD, SYSTEM AND APPARATUS FOR TERMINAL INFORMATION PROTECTION

The present invention relates to device management (DM), and more particularly, to a method, system and apparatus for protecting terminal data in DM.

The DM specification of the Open Mobile Alliance (OMA) (hereinafter referred to as the DM specification) is a recent standard standard for device management. The DM system handles the low cost solution of managing and setting up the environment and configuration information of the terminal device to a third party, e.g. problems arising from the use of the terminal device, It provides mobile terminals and functional objects of terminals of a wireless network, which install and upgrade its firmware and software. The DM system provides a more user friendly and more personal service that enhances the user experience.

As mobile terminals are widely used, mobile terminals generally store a large amount of important user information. Once a terminal is lost or left, the user suffers a great loss. For example, data having a large influence such as a short message, a multimedia message, an address book, a call log, a note, an e-mail, a picture, a voice, and a video is stored in a mobile terminal.

In order to solve this problem, the conventional terminal is locked through the DM command. As shown in FIG. 1, the DM server changes the value of the TerminalSecurity / DeviceLock / LockLevel subnode under the management tree of the terminal to lock or unlock the terminal. If the value of the subnode is true, the terminal is locked. If the value of the subnode is false, the terminal is unlocked. In addition to locking the terminal, the DM server can run the TerminalSecurity / DeviceWipe node via a DM command. The DM server may send a data delete command to the node to delete all data related to the user in the data terminal including the data in the expansion card.

Conventionally, the terminal may be locked or unlocked. Specifically, when the terminal is locked, all functions of the terminal are locked and can only be unlocked by the server that locked the terminal, so the user experience is not good. In addition, when data deletion is performed according to the prior art, the user experience is not good because all data related to the user, including some useful data, is deleted at the terminal.

Embodiments of the present disclosure provide a terminal data protection method, system, and apparatus for reasonably managing access rights of a server with a better user experience.

The method of protecting terminal data includes: transmitting, by a first device management (DM) server, a lock command to a terminal; And in accordance with the locking command, the terminal fully locking or partially locking a function, wherein the locking command locks the terminal to instruct the terminal to fully lock or partially lock the function. Carries information and the lock command is carried through the DM protocol.

A terminal data protection method includes storing data items that a terminal can delete in a terminal management tree; Transmitting, by a device management server, a wipe command according to the deleteable data item to the terminal through a device management protocol; And deleting the data item to be deleted by the terminal.

The terminal data protection system includes a first device management server including a lock command transfer module; And a terminal, wherein the lock command transfer module delivers a lock command that carries lock information instructing the terminal to fully lock or partially lock a function, the lock command being carried through a device management protocol, and the terminal The first receiving module for receiving the lock command; And a lock module that completely locks or partially locks a function according to the lock information.

CLAIMS 1. A terminal data protection system, comprising: a device management server including a delete command delivery module for delivering a delete command via a device management protocol; And a terminal, wherein the command carries an ID of one or more data items to be deleted, the terminal comprising: a first receiving module for receiving the delete command sent by the device management server; And a wiping module for deleting a data item corresponding to the data item ID.

In the technical solution of the embodiment of the present specification, the DM server transmits a lock command to the terminal indicative of a full lock or partial lock of a function, and the terminal executes a lock operation according to the lock information. In the solution, the user can lock the terminal in the desired way, thus improving the user experience.

1 is a schematic diagram showing the structure of a management tree for locking or unlocking a terminal in the prior art.

2A, 2B, 2C, 2D and 2E are schematic diagrams showing the structure of a terminal data protection system according to a first embodiment of the present invention.

3 illustrates a procedure for protecting terminal data according to a second embodiment of the present specification.

4 is a schematic diagram illustrating a structure of a terminal management tree according to an embodiment of the present specification.

5 illustrates a procedure of determining whether a terminal has a lock release right in a DM server according to a third embodiment of the present specification.

6 illustrates a procedure of determining whether a terminal has an unlock right according to a fourth embodiment of the present specification.

7 is a schematic diagram illustrating a structure of a terminal management tree according to a fifth embodiment of the present specification.

8 is a schematic diagram illustrating a structure of a terminal management tree according to a sixth embodiment of the present specification.

9 illustrates a procedure of deleting, by a terminal, a data item corresponding to a data item ID according to a seventh embodiment of the present specification.

10 is a schematic diagram showing the structure of a terminal data protection system according to a ninth embodiment of the present specification.

Embodiments of the present invention will be described in detail with reference to the accompanying drawings.

2A, 2B, and 2C show a terminal data protection system according to a first embodiment of the present specification. The system includes a first DM server 11 and a terminal 12. The first DM server 11 includes a lock command transfer module 21 for delivering a lock command including lock information instructing the terminal to completely lock or partially lock a function. The terminal 12 includes a first receiving module 31 that receives a lock command and a locking module 32 that completely locks or partially locks a function according to the lock information.

Partial locks or fully locks can vary in three scenarios.

The first scenario is as shown in FIG. 2A. The lock information is an IsFullLocked flag. If the flag indicates full lock, the lock module 32 locks all functions, and if the flag indicates partial lock, the lock module 32 locks the preset functions.

The second scenario is as shown in FIG. 2B. The lock information includes the ID of one or more data items to be locked. The locking module 32 locks the data items identified by the ID.

The first DM server 11 further includes a get command delivering module 22 and a second receiving module 23. The acquisition command delivery module 32 delivers the acquired command to the terminal. The second receiving module 23 receives the data item ID reported by the terminal. The terminal further includes a storage module 33 for storing the ID of the data item which can be locked by the terminal and a reporting module 34 for reporting the stored data item ID to the first DM server 11.

In a third scenario, the lock information is an IsFullLocked flag and / or an ID of data items to be locked. If the flag indicates a complete lock, the lock module 32 locks all functions. If the flag indicates a partial lock, the lock module 32 locks the preset functions. If the lock information includes the IDs of the data items, the lock module 32 locks the data items identified by the IDs.

The lock information may be a combination of an IsFullLocked flag and a data item ID. In an embodiment herein, the IsFullLocked flag is set to take precedence over the data item ID. The lock module 32 may execute only the operation corresponding to the IsFullLocked flag without executing the operation corresponding to the data item ID.

After the terminal is locked by one of the three locking procedures described above, the DM server may instruct the terminal to unlock the locked function by the unlocking procedure according to the embodiment of the present specification. Although embodiments of the present specification provide a plurality of unlocking procedures including the following procedures, the plurality of unlocking procedures are not limited to the following procedures.

1. As shown in FIG. 2C, if the lock command delivery module 31 additionally delivers a security code, the system further includes a second DM server 13 that delivers the unlock command and security code; The terminal 12 further includes a first determining module 35 and an unlocking module 36. The first determination module 35 determines whether the security code received from the second DM server 13 matches the security code received from the first DM server, and if the security codes match, unlocking module 36. Start up. The unlock module 36 unlocks the locked functions.

2. As shown in FIG. 2D, if the lock command transfer module 21 additionally sends an identifier of the first DM server 11, the terminal 12 further includes a second determination module 37. . The second determining module compares the identifier of the second DM server 13 with the identifier of the first DM server 11 and instructs the unlock module to unlock the locked functions if the identifiers match.

3. As shown in FIG. 2E. If the lock command delivery module 21 additionally delivers an AllowLocallyUnlock flag, the terminal 12 further includes a third decision module 38. The third determining module 38 compares the received code with a preset code and instructs the unlocking module 36 to unlock the locked function if the codes match.

If the lock command delivery module 21 additionally delivers the unlock code, the preset code is the unlock code that was passed.

If the lock command delivery module 21 additionally delivers a LocalLocallyUnlock flag including a local password, the preset password is a local password stored by the terminal.

The unlocking solutions shown in Figures 2C, 2D, and 2E can be combined. For example, a decision may first be made according to the conditions of the sequence set, and the terminal is unlocked if the set conditions match.

In an embodiment herein, the commands and parameters passed by the DM server are carried over the DM protocol, the parameters can be passed with the lock or unlock commands by the DM server, and also separately over the DM protocol. Can be delivered.

Hereinafter, embodiments of the present disclosure will be described in detail.

The server described in the embodiments herein is a DM server. According to the first embodiment of the present specification, FIG. 3 is a schematic diagram showing a terminal data protection procedure of the second embodiment of the present specification. In the second embodiment, the DM server completely locks or partially locks the function of the terminal and unlocks the locked functions by the next unlocking process. The procedure includes the following steps.

S301. The DM server sends a lock command to the terminal. The command carries lock information that instructs the terminal to fully lock or partially lock the function.

S302. Upon receipt of the lock command, the terminal locks or partially locks the functions according to the lock information and sends a response to the DM server informing whether the lock operation was successful.

In all of the following embodiments, a full lockout means that the user cannot use any functionality of the terminal except for legislative sessions and DM sessions, such as emergency calls, and the terminal through an external connection such as Bluetooth and USB connection. This means that no data can be obtained from it. Partial locking means that the terminal or the server has pre-determined the functions of locking when the lock information is received. For example, all functions can be locked except for incoming calls, legally authorized sessions, and DM sessions. However, the locked terminal may provide an input interface for receiving a code input from the user so that the user can unlock the terminal. This is illustrated in the following examples.

In practice, full lock or partial lock functions may vary in three scenarios.

In the first scenario, if the lock information received from the terminal is an IsFullLocked flag, the terminal locks all functions if the flag indicates full lock, and the terminal locks a preset function if the flag indicates partial lock. And the server agree in advance.

In the second scenario, the lock information transmitted from the DM server to the terminal is an ID of data items to be locked. If the data item ID includes all data items that the terminal can lock, the terminal locks all functions. If the data item ID includes a portion of the data item that the terminal can lock, the terminal locks the data items according to the IDs.

The third scenario is the IsFullLocked flag and / or the ID of the data items to which the lock information transmitted from the DM server to the terminal is locked. If the lock information includes only a flag or only data item IDs, the terminal performs the lock operation according to the first scenario or the second scenario. If the lock information includes a flag and the ID of the data item to be locked, the terminal can only execute the operation according to the flag because the IsFullLocked flag takes precedence over the ID of the data item.

  S303. If the DM server also delivers the security code to the terminal, the DM server providing the appropriate security code can unlock the terminal with the next unlocking process.

If the first DM server delivers a security code when the first DM server locks the terminal, the second DM server issues an unlock command as long as the second DM server is included in an access control list (ACL). Can be sent to If the unlock command carries a suitable security code, the terminal can unlock the locked functions of the terminal.

The user who knows the DM server and security code that delivers the lock command can also unlock the terminal.

If the terminal is unlocked, the terminal sends a response message to the DM server informing whether the unlock operation is successful.

S304. The DM server sends a delete command to the terminal. The delete command carries the ID of one or more data items to be deleted.

S305. The terminal deletes the stored data items corresponding to the ID and sends a response to the DM server notifying whether the delete operation is successful.

In this embodiment, the data item to be deleted is the data content category of the terminal such as short message, multimedia message, address book, note, email, picture, audio, video, and code. When the terminal receives a delete command carrying an ID of one or more data items to be deleted, the terminal may delete one or more data items to be deleted.

Steps S304 and S305 can be executed before or after steps S301 and S302. The DM server may send the delete command before the terminal is locked or after the terminal is locked.

The solution provided in the embodiments of the present specification may be executed through a terminal management tree. The command delivered by the DM server may be an operation at a node of the terminal management tree. Locking, unlocking, and data deletion are described in detail below.

4 is a schematic diagram illustrating a structure of a terminal management tree of an embodiment of the present specification. By way of executing all or part of the nodes of FIG. 4, the terminal can be locked or unlocked and the terminal data can be deleted.

A terminal data protection method through terminal lock and unlock is provided in the third embodiment of the present specification. As shown in Fig. 4, a lock subnode is created under the operation. The Lock subnode is executable. The Lock subnode receives the lock command from the DM server and executes the operation according to the operation. Table 1 shows the Lock subnodes.

Table 1

Status Tree Occurence Format at least. Min. Acceess Types Required One Null Exec

When the terminal receives the lock command from the DM server, the terminal stores all parameters carried in the command under the LockConfig subnode. LockConfig contains the following subnodes; LAWMO / LockConfig / IsFullLocked, LAWMO / LockConfig / SecurityCode, LAWMO / LockDonfig / ServerID, LAWMO / Operation / Unlock, and LAWMO / Operation / Unlock / SecurityCode.

LAWMO / LockConfig / IsFullLocked is used to store lock information. The value of IsFullLocked is either true or false. If the value is true, the terminal locks the functions completely; if the value is false, the terminal partially locks the functions. Table 2 shows the IsFullLocked subnodes.

Table 2

Status Tree Occurence Format at least. Min. Acceess Types Required One Bool Get, Replace

LAWMO / LockConfig / SecurityCode is used to store the security code sent from the DM server, authenticating the DM server that requested the unlock. This subnode may have zero or one occurrences in the tree. If the DM server does not pass the security code, this subnode does not appear. Table 3 shows the SecurityCode subnode.

Table 3

Status Tree Occurence Format at least. Min. Acceess Types Required 0 or 1 Chr No Get, Replace

LAWMO / LockDonfig / ServerID is used to store the ID of the DM server carrying the lock command. If the DM server later requests unlocking, no security code is required. When the terminal determines that the DM server requesting the unlock is the same as the DM server requesting the lock according to the ID information stored in the server ID node, the terminal may execute the unlock operation. Table 4 shows the SeverID subnodes.

Table 4

Status Tree Occurence Format at least. Min. Acceess Types Required 0 or 1 Chr Get, Replace

The LAWMO / Operation / UnLock subnode is an executable node that receives the unlock command from the DM server and executes the unlock operation. Table 5 shows UnLock subnodes.

Table 5

Status Tree Occurence Format at least. Min. Acceess Types Required One Null Exec

LAWMO / Operation / UnLock / SecurityCode is used to match the security code carried in the received unlock command with the security code stored in LAWMO / LockConfig / SecurityCode to authenticate the DM server that sent the unlock command. Table 6 shows UnLock / SecurityCode

Table 6

Status Tree Occurence Format at least. Min. Acceess Types Required One Null Exec

According to the nodes of Tables 1-6, the locking or unlocking solution of the third embodiment of the present specification is as follows.

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

In this embodiment, the lock information, security code, and server ID can be delivered with a lock command, or can be delivered respectively by the DM server via the DM protocol.

If the DM server wishes to lock all functions of the terminal except the sessions authorized by the law and the DM sessions, the lock information may be a flag indicating full lock, in which the IsFullLocked parameter has a true value. If the DM server does not want to prohibit the terminal from receiving a call, the DM server may set the IsFulllocked flag to false.

When the first DM server locks the terminal, the DM server may also send a SecurityCode parameter if the DM server wants to grant the unlock right to the second DM server. When requesting the terminal to unlock, the second DM server must provide a SecurityCode for authentication.

If the first DM server does not set the SecurityCode, it may be set such that another DM server has the right to unlock or no other DM server has the right to unlock. In addition, when the first DM server that delivers the lock command delivers the unlock command to the terminal, the SecurityCode is unnecessary. The terminal may determine the rights of the first DM through the recorded ServerID.

If the first DM server passes IsFullLocked, SecurityCode, and ServerID and later UnLock parameters, the first DM server may pass the parameters through a Replace command. E.g:

<Replace>

  <CmdID> 4 </ CmdID>

    <Item>

      <Target>

        <LocURI> / LAWMO / LockConfig / IsFullLocked </ LocURI>

      </ Target>

      <Data> true </ Data> <!-Value of IsFullLocked->

    </ Item>

    <Item>

      <Target>

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

    </ Target>

    <Data> ABCD1234 </ Data> <!-Value of SecurityCode->

  </ Item>

</ Replace>

S2. When the terminal receives the lock command, the terminal writes the parameters carried in the command to the corresponding node and performs a lock operation according to the parameter.

When the terminal receives the security code, the terminal records the value of the security code in LAWMO / LockConfig / SecurityCode. When the terminal receives the lock information, the terminal writes the value of the lock information to the LAWMO / LockConfig / IsFullLocked node. The terminal extracts the ID of the DM server that delivers the lock information and records the ID value in the LAWMO / LockConfig / ServerID node.

When the terminal receives the lock command, the terminal executes a corresponding operation according to the parameter carried in the command.

S3. When the first DM server that delivers the lock command to the terminal requests the unlock, the first DM server immediately delivers the unlock command to the LAWMO / Operation / UnLock node of the terminal. Otherwise, if the second DM server sends an unlock command to the terminal, the security code must be carried.

The second DM server can deliver the security code in two approaches. One is to pass parameters directly through the Replace command. The other is to carry parameters as described below with data elements of the Exec instruction.

1. Pass parameters directly through the Replace command

<Sequence>

  <Replace>

    <CmdID> 4 </ CmdID>

      <Item>

        <Target>

        <LocURI> / LAWMO / Operation / UnLock / SecurityCode </ LocURI>

        </ Target>

        <Data> ABCD1234 </ Data> <!-Value of SecurityCode->

      </ Item>

  </ Replace>

  <Exec>

  <CmdID> 3 </ CmdID>

    <Item>

      <Target>

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

      </ Target>

    </ Item>

  </ Exec>

</ Sequence>

2. Carry parameters to the data elements of the Exec command

The command is:

<Exec>

  <CmdID> 3 </ CmdID>

    <Item>

      <Target>

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

      </ Target>

        <Data> ABCD1234 </ Data> <!-Value of SecurityCode->

    </ Item>

</ Exec>

S4. When the terminal receives the unlock command, the terminal determines whether the DM server has the right to unlock, and if so, the terminal executes the unlock operation or otherwise rejects the request and returns the error information.

The procedure of authenticating the DM server by the terminal is shown in FIG. 5. The procedure includes the following steps.

S501. The terminal determines whether the ID of the second DM server that delivers the unlock command is the same as the ID of the first DM server that delivers the lock command, and if it is the same, the procedure proceeds to step S504, otherwise proceeds to S502.

The terminal extracts the ID of the second DM server that delivers the unlocking information from the DM session. If two commands are sent from the same DM server, the second DM server has the unlock right by default, and the terminal immediately executes the unlock operation. If two commands were sent from the other DM server, the terminal continues to determine whether the second DM server has the right to unlock.

S502. The terminal checks whether the lock instruction carries a security code, and if it carries, the procedure proceeds to step S503, otherwise proceeds to S504.

If the LAWMO / LockConfig / SecurityCode subnode stores the security code, the corresponding security code must be carried by the unlock command. If the previous lock information does not carry a security code, then any DM server has the right to unlock by default and the terminal immediately executes the unlock operation.

In another embodiment, if the lock command does not carry a security code, a DM server other than the DM server that delivers the lock command may be set to not have the unlock right by default.

S503. The terminal determines whether the security code carried by the unlock command corresponds to the security code of the lock command, and if so, the procedure proceeds to step S504, otherwise proceeds to S505.

If the second DM server that delivers the unlock command provides the security code, the terminal writes the security code to LAWMO / Operation / UnLock / SecurityCode. In step S503, if the terminal determines that the security code is the same as the security code carried in the lock command, the terminal determines that the second DM server carrying the unlock command has the unlock right.

S504. The terminal executes the unlock operation.

S505. The terminal stays locked.

Regardless of whether the terminal is unlocked, at the end of step S504 or S505, the terminal erases the security code stored in LAWMO / Operation / UnLock / SecurityCode so that the security code is not used in the next unlock command.

In step S4, the terminal authenticates the second DM server by matching ServerID and SecurityCode, which is the only one approach to practicing this specification. Alternatively, the terminal can determine via another corresponding sequence, or can authenticate the second DM server in correspondence with only ServerID or only SecurityCode.

According to the third embodiment, a procedure is performed in which the first DM server locks the terminal and the second DM server unlocks the terminal. In the fourth embodiment of the present specification, the manual unlocking procedure by the user includes the following steps.

S1. The DM server sends a lock command to the terminal. The command carries the LocalLocallyUnlock flag.

At this stage, the lock command transfer procedure is the same as that of the third embodiment. The DM server may carry parameter information delivered with the lock command of step S1 of the third embodiment of the present specification. Therefore, in the fourth embodiment, both manual unlocking by the user and unlocking by the DM server of the third embodiment can be executed.

The lock command may carry an AllowLocallyUnlock flag that instructs the terminal whether to release the lock through manual entry of the unlock code. The terminal stores the flag in the LAWMO / LockConfig / AllowLocallyUnlock subnode. If the flag value is true, the user is allowed to unlock the terminal. If the flag value is false, the user is not allowed to unlock the terminal. Table 7 shows the AllowLocallyUnlock subnodes.

If the lock command does not carry a flag, manual unlock is allowed or disallowed by default.

Table 7

Status Tree Occurence Format at least. Access Types) Required 0 or 1 Bool Get, Replace

If the DM server allows manual unlock, the unlock command carries an unlock code. The terminal stores the received unlock code in the LAWMO / LockConfig / UnlockCode subnode. The unlock code is a verification code for manual unlock. If the user enters the unlock code appropriate for the terminal, the terminal considers the user to have the unlock right. Table 8 shows the LAWMO / LockConfig / UnlockCode subnodes.

Table 8

Status Tree Occurence Format at least. Access Types) Required One Chr Get, Replace

In addition to manual unlocking by the user by the unlock code, the user can unlock the terminal using the local password of the terminal. In this case, the lock command carries a LocalPwdAvailable flag. The terminal stores the flag in the LAWMO / LockConfig / LocalPwdAvailable subnode. If the flag is true, the user is allowed to unlock the LOWMO lock of the terminal with the terminal's local password. If the flag value is false, the user is not allowed to unlock the terminal with a local password. Table 9 shows LocalPwdAvailable subnodes.

Table 9

Status Tree Occurence Format at least. Access Types) Optional 0 or 1 Bool Get, Replace

S2. Upon receipt of the unlock command, the terminal determines whether the user who entered the unlock password has permission to unlock, and if so, the terminal executes an unlock operation, otherwise rejects the request.

The procedure for authenticating the user by the terminal is shown in FIG. The procedure includes the following steps.

S601. The terminal checks the flag stored in the LAWMO / LockConfig / AllowLocallyUnlock subnode, and if the flag value is true, the procedure proceeds to step S602, otherwise proceeds to S607.

If the flag value is true, the user is allowed to unlock the terminal by entering a password. If the flag value is false, the user is not allowed to unlock the terminal with a password. If the flag value is false, manual unlock is not allowed. Regardless of which password the user entered, the terminal stays locked.

S602. The terminal checks whether the unlock code is stored, and if so, the procedure proceeds to step S603, otherwise proceeds to step S604.

If LAWMO / LockConfig / UnlockCode is null, the terminal may further check whether the user is allowed to unlock the terminal with a local password.

S603. The terminal checks whether the unlock code input by the user corresponds to the stored unlock code. If corresponding, the procedure proceeds to step S606, otherwise proceeds to step S607.

In the embodiments herein, the codes are identical to one another if the codes correspond to one another.

Regardless of whether the terminal is fully or partially locked, the terminal provides a user interface (UI) so that a user can enter code through the interface.

S604. The terminal determines whether the user is allowed to unlock the terminal with a local password. If permitted, the procedure proceeds to step S605, otherwise proceeds to S607.

S605. The terminal checks whether the local password input by the user corresponds to the stored local password. If so, the procedure proceeds to step S606, otherwise proceeds to S607.

S606. The terminal executes the unlock operation.

S607. The terminal stays in the unlocked state.

In step S2, the terminal is manually unlocked using the unlock code and local password. In another embodiment of the present disclosure, the terminal may make a decision through another corresponding sequence, or may execute manual unlocking only by matching the unlock code or by matching the local password.

The locking and unlocking procedures of the third and fourth embodiments of the present specification are based on the terminal management tree of FIG. But. The terminal management tree of FIG. 4 represents only one implementation of the present specification. The structure of the terminal management tree may be as shown in FIG. In this structure, the <Y> * subnodes under LockConfig are one of LAWMO / LockConfig / IsFullLocked, LAWMO / LockConfig / SecurityCode, LAWMO / LockConfig / UnlockCode, LAWMO / LockConfig / ServerID, LAWMO / LockConfig / AllowLocallyUnlock, and LAWMO / LockConfig / LocalPwdAvailable It occupies more than one place.

In the locking and unlocking procedure according to the fifth embodiment similar to the third and fourth embodiments of the present specification, based on the management tree structure shown in FIG. , UnlockCode, ServerID, AllowLocallyUnlock, and LocalPwdAvailable parameters are passed to the terminal and stored in the <Y> * nodes. The terminal sets the lock state according to the parameters and configures the unlock right.

The delivery procedure may be described in the following program which describes only the SecurityCode delivery procedure. Other parameters may be passed in a similar procedure.

<Add>

  <CmdID> 2 </ CmdID>

  <Item>

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

      <Data> ABCD1234 </ Data> <!-Value of SecurityCode->

  </ Item>

</ Add>

According to the system according to the first embodiment of the present specification, various methods for protecting terminal data are provided in the third to fifth embodiments.

In addition to the foregoing terminal data protection through terminal lock, a sixth embodiment of the present disclosure provides a method of protecting terminal data by locking a data item. Data items include, but are not limited to, short messages, address books, and emails. The data item list is stored in the LAWMO / OperableContent / <X> node. As shown in Figure 4, the content is determined by the terminal. Table 10 shows LAWMO / OperableContent / <X> nodes.

Table 10

Status Tree Occurence Format Min Acceess Types Required 0 or 1 Chr Get

To realize the capability, based on FIG. 4, a <X> * subnode is created under the lock shown in FIG. The X node stores the names of the data items that the DM server has requested to lock. In this case, the IsFullLocked subnode is unnecessary under LockConfig.

The procedure for locking or unlocking the terminal data items of the sixth embodiment of the present specification one by one includes the following steps.

1. The DM server transmits a Get command to an acquisition data item that can be locked by the terminal.

The DM server may use the Get command to obtain a value of LAWMO / OperableContent / <X> in the terminal management tree. The specific process is as follows.

(1) The DM server requests to obtain an ID of a data item that can be locked.

<Get>

  <CmdID> 4 </ CmdID>

    <Item>

      <Target>

        <LocURI> / LAWMO / Operablecontent </ LocURI>

      </ Target>

    </ Item>

</ Get>

(2) The terminal returns the content under OperableContent to the DM server through a Result command.

If the content under OperableContent is a short message (SMS), an address book and a SIM card, the message is returned by the terminal to the DM server as follows.

<Results>

  <MsgRef> 1 </ MsgRef> <CmdRef> 4 </ CmdRef>

    <CmdID> 3 </ CmdID>

    <Item>

    <Source>

      <LocURI> / LAWMO / Operablecontent </ LocURI>

    </ Source>

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

    </ Item>

</ Results>

In an embodiment, step 1 may not occur. For example, a lockable data item may not be agreed by the terminal and the server, or may already be standardized.

2. The DM server sends a lock command to the terminal. The command carries the ID of one or more data items that the DM server wants to lock. The terminal may lock one or more data items corresponding to the ID.

If the DM server delivers a lock command, as in the third, fourth, and fifth embodiments of the present specification, other parameters may be passed along with the command.

The DM server can convey the ID of the data item via Add, Replace, or Exec's data elements. Direct delivery through Replace and delivery through the data elements of Exec are similar to the delivery procedure of the third embodiment. The transfer of data item ID through Add is as follows.

<Sequence>

  <Add>

    <CmdID> 3 </ CmdID>

  <Item>

    <Target>

      <LocURI> / LAWMO / Operation / Lock / para2 </ LocURI>

    </ Target>

      <Data> AdressBook </ Data>

  </ Item>

  </ Add>

  <Exec>

    <CmdID> 3 </ CmdID>

  <Item>

    <Target>

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

    </ Target>

  </ Item>

  </ Exec>

</ Sequence>

Upon receiving the lock command, the terminal checks whether the subnode is under Lock or whether the subnode of Lock is null. If so, the terminal determines that the DM server has not specified a data item to be locked. The terminal may execute the lock operation in the same way as the solution of the third, fourth and fifth embodiments. If the terminal finds that the subnode content under Lock is SMS and address book, the terminal locks the SMS and address book functions so that the terminal cannot send or receive a short message and cannot view or change the address book.

3. The terminal performs the unlock operation according to the unlock command received from the DM server.

The unlocking procedure is the same as in the third, fourth, and fifth embodiments herein.

The third and sixth embodiments provide two methods of full lock or partial lock of the terminal. Both methods may also be a combination of full lock or partial lock execution of the terminal. For example,

Three values, 0, 1, and 2, are set to the IsFullLocked subnode. If the value is 0 or 1, the lock information delivered by the DM server is an IsFullLocked flag, and the procedure is executed according to the third embodiment. If the value is 2, the lock information delivered by the DM server is the ID of the data item to be locked, and the procedure is executed according to the sixth embodiment. In this case, the IDs of the flag and data item are in an "Or" relationship. If the values are 0 and 2 (or 1 and 2), the lock information passed contains the locks of the one or more data items added to the <X> * subnodes under Lock, indicating full lock (or partial lock). (IsFullLocked) Combination of " And " relationship between flags and data item IDs. In this case, both the procedures according to the third and sixth embodiments are executed. In addition, if the IsFullLocked flag takes precedence over the data item IDs, the procedure is executed according to the third embodiment, and the procedure according to the sixth embodiment is not executed.

However, if the priority of the IsFullLocked flag is lower than the data item IDs, the procedure is executed according to the sixth embodiment, and the procedure according to the third embodiment is not executed.

A method of protecting terminal data by deleting terminal content according to a seventh embodiment of the present specification includes the following steps.

1. The DM server obtains a data item that can be deleted by the terminal.

Before delivering the delete command, similar to the obtaining procedure of the sixth embodiment, the DM server may obtain a deleteable data item of the terminal. Alternatively, this step may not occur.

The data item that can be deleted may be the same as the lockable data item of the sixth embodiment, and both are subnode values under LAWMO / OperableContent. Alternatively, other nodes may be created in the terminal management tree to store the terminal's erasable data items.

2. The DM server sends a delete command to the terminal. The delete command carries one or more data items to be deleted.

The delete command carried by the DM server executes the LAWMO / Opearion / Wipe executable node of the terminal management tree. Table 11 shows Wipe nodes.

Table 11

Status Tree Occurence Format Min. Acceess Types Required One Null Exec

<X> * Subnodes exist under Wipe and store the IDs of data items that the DM server wishes to delete. Table 12 shows <X> * subnodes.

Table 12

Status Tree Occurence Format Min. Acceess Types Optional 0 or 1 Null Get

As in the sixth embodiment, the DM server transmits IDs of one or more data items to be deleted in two modes. One is to pass the ID of the data item directly through the Replace command, and the other is to carry the ID in the data element of the Exec command.

3. The terminal deletes the data item corresponding to the data item ID. As shown in FIG. 9, the procedure includes the following.

S901. If the X subnode is not under LAWMO / Operation / Wipe of the terminal or if the X subnode is null, the ID of the data item to be deleted is not carried and the procedure proceeds to step S904, otherwise proceeds to S902.

S902. The terminal determines whether the erasable data item ID is the received data item ID, and if so, the procedure proceeds to step S903, otherwise proceeds to S905.

S903. The terminal deletes the data item corresponding to the received data item ID.

For example, the DM server delivers a data item ID to the terminal through the following command.

<Exec>

  <CmdID> 3 </ CmdID>

    <Item>

      <Target>

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

      </ Target>

        <Data> AddressBook </ Data>

    </ Item>

</ Exec>

The terminal then deletes the address book data. The deletion procedure appears last.

S904. According to the delete command, the terminal deletes all data including all data of the device storage location, data of the extended storage media, and data of the Subscriber Identify Module (SIM) card.

S905. The terminal rejects the delete request.

In the seventh embodiment, the terminal data protection method is protected by deleting the terminal content. Alternative solutions of the method according to the seventh embodiment are possible. It is a slight modification of the second stage. In the second step of the seventh embodiment, the DM server also transmits to the terminal the ID of the data item to be deleted in addition to the delete command. In an alternative solution, the DM server delivers to the terminal an indicator of the data item to be deleted in addition to the delete command.

The indicator may be the name of the data item to be deleted, or may be an ID of the data item, or may be an IsWipe flag of the deleteable data item in the terminal management tree.

As in the sixth embodiment, the DM server may deliver the indicator in two states. One is to pass directly through Replace, and the other is to carry the indicator in the Exec's data element.

Upon receipt of the delete command, the terminal deletes the data item to be deleted.

In the delete operation, the deletion of the password is a particular embodiment of the present specification. The DM server may instruct the terminal to delete the password and may instruct the terminal to change or set the password.

According to an eighth embodiment of the present specification, a method of deleting or changing a password to a terminal includes the following steps.

1. The DS server sends a delete command to the terminal.

As in the seventh embodiment, the DM server sends a Clear Password command to the Wipe erasable node. Alternatively, the DM server may run the LAWMO / LocalLock / ClearPwd subnode of the terminal management tree. The subnode deletes the terminal's password. Table 13 shows its subnodes.

Table 13

Status Tree Occurrence Format Min Access Types Optional One Null Exec

The DM server runs the ClearPwd subnode with the following command:

<Exec>

  <CmdID> 3 </ CmdID>

    <Item>

      <Target>

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

      </ Target>

    </ Item>

</ Exec>

If the DM server wants to set a new password for the terminal, the DM server executes the LAWMO / LocalLock / ChangePwd subnode of the terminal management tree. Table 14 shows its subnodes.

Table 14

Status Tree Occurrence Format Min Access Types Optional One Null Exec

The DM server runs the ChangePwd subnode with the following command:

<Exec>

  <CmdID> 3 </ CmdID>

    <Item>

      <Target>

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

      </ Target>

        <Data> ABC123 </ Data> <!-New password for terminal->

    </ Item>

</ Exec>

2. The DM server delivers the new terminal password and the terminal deletes the old password and uses the new password as the terminal password. Or, the terminal overwrites the new terminal password with the old terminal password.

In the management tree shown in FIG. 4, in addition to the aforementioned nodes, a LAWMO / Operation / FactoryReset subnode may be created. This subnode is executable. The DM server can run this node and instruct the terminal to change the parameter settings of the terminal to factory settings. Table 15 shows FactoryReset nodes.

Table 15

Status Tree Occurrence Format Min Access Types Required One Null Exec

In addition, a LAWMO / State node can be created to show whether the terminal is currently locked. Different values of State reflect different states of the terminal. For example, when the State value is 0, the terminal is locked and all functions are locked. When the State value is 1, the terminal is locked and the set functions are locked. When the value is 2, the terminal is not locked. When the value is 3, the terminal is in a different state.

The methods provided in the third to eighth embodiments can be combined in a new way.

Corresponding to the method of the seventh and eighth embodiments, a terminal data protection system is provided according to the ninth embodiment in the present bottle. As shown in FIG. 10, the system includes a DM server 41 and a terminal 42. The DM server 41 includes a delete command transfer module 51 which delivers, via the DM protocol, a delete command carrying an ID of one or more data items to be deleted. The terminal 42 includes a first receiving module 61 for receiving a delete command transmitted from the DM server 41 and a deleting module 62 for deleting the data item according to the ID of the data item.

The DM server 41 includes an acquisition command delivery module 52 and a second receiving module 53. The obtaining command delivery module 52 delivers the acquired command to the terminal, and the second receiving module 53 receives the ID of the data item reported by the terminal. The terminal 42 further includes a storage module 63 and a reporting module 64. The storage module 63 stores the ID of the data item that can be deleted by the terminal, and the reporting module 64 reports the ID of the stored data item to the DM server 41.

If the data item ID includes the terminal password ID and the delete command transfer module 51 passes the terminal password, the terminal 41 sets a new terminal password received after the old terminal password is erased as the terminal password ( setting module 65) or overwrites the old password received by the terminal with the old password.

In a method and system according to an embodiment of the present disclosure, a user may lock all or part of the terminal function as needed. Privileges are controlled in a more rational way and the unlocking procedure is more flexible. The burden on the DM server is low and the user is more convenient. In addition, since the contents of one or more viable terminals are deleted, the deletion efficiency is high.

Those skilled in the art will appreciate that the embodiments described herein can be implemented by hardware and software and by any general hardware platform required. The technical solution of the present specification may be embodied as a software product stored in a nonvolatile storage medium. The storage medium may be a compact disk read-only memory (CD-ROM), a USB disk, or a mobile hard disk. The software product includes a number of instructions that enable a computer device, such as a personal computer, server, or network device, to execute the methods provided in the embodiments herein.

Although the specification describes some exemplary embodiments. The present specification is not limited to these embodiments. It will be apparent to those skilled in the art that the present specification can be variously changed and changed without departing from the scope of the present specification. This specification encompasses modifications and variations provided within the scope of protection defined by the following claims or their equivalents.

Claims (32)

As a terminal data protection method, Transmitting, by a first Device Management (DM) server, a lock command to a terminal; And In accordance with the locking command, the terminal fully locking or partially locking a function Including, The lock command carries lock information instructing the terminal to fully lock or partially lock the function, the lock command being carried over a DM protocol, How to protect your device data. The method of claim 1, The lock information is an IsFullLocked flag, the terminal locks all functions if the flag indicates a full lock, and the terminal locks only a part of the function if the flag indicates a partial lock, How to protect your device data. The method of claim 1, The lock information is an ID of one or more data items to be locked, and the terminal locks a data item corresponding to the ID. How to protect your device data. The method of claim 3, Before the step of delivering a lock command to the terminal, Transmitting, by the first device management server, a get command to the terminal; And Transmitting a corresponding ID of a data item that can be locked by the terminal to the first device management server; Terminal data protection method further comprising. The method of claim 1, The lock information is an IsFullLocked flag and / or ID of the data item to be locked, If the IsFullLocked flag indicates a full lock, the terminal locks all functions. If the IsFullLocked flag indicates a partial lock, the terminal locks a preset function. The lock information indicates a data item ID. The terminal locks the data item corresponding to the data item ID. How to protect your device data. The method of claim 5, IsFullLocked flag has a priority over a data item ID, How to protect your device data. The method according to any one of claims 1, 2, 3 or 5, If the first device management server additionally delivers a security code to the terminal, After the step of fully or partially locking the function, Transmitting, by a second device management server, an unlock command and a security code to the terminal; And If the security code received from the second device management server is the same as the security code transmitted from the first device management server, executing the unlock operation by the terminal. Terminal data protection method further comprising. The method of claim 7, wherein If the first device management server additionally delivers the ID of the first device management server to the terminal,  The ID of the second device management server to which the terminal transmits the unlock command is compared with the ID of the first device management server, and the ID of the second device management server and the ID of the first device management server are the same. If the terminal executes the unlock operation Terminal data protection method further comprising. The method according to any one of claims 1, 2, 3, and 5, If the first device management server additionally sends a flag to allow the terminal to manually unlock, the user is allowed to manually unlock the terminal, How to protect your device data. The method of claim 9, If the first device management server additionally delivers an unlock code to the terminal, The unlocking procedure may include: receiving, by the terminal, an unlocking code input from the user; and if the inputted unlocking code is the same as the unlocking code received from the first device management server, executing the unlocking. Process, How to protect your device data. The method of claim 9, If the first device management server additionally delivers a flag for allowing the terminal to unlock with a local password, The unlocking procedure may include: receiving, by the terminal, a local password input from the user; and if it is determined that the input local password is the same as the local password stored from the terminal, executing the unlocking. How to protect your device data. As a terminal data protection method, Storing a data item that the terminal can delete in a terminal management tree; Transmitting, by a device management server, a wipe command according to the data item to be deleted to the terminal through a DM protocol; And Deleting the data item to be deleted by the terminal; Terminal data protection method comprising a. The method of claim 12, The step of transmitting a delete command according to the data item that can be deleted to the terminal, includes the step of transmitting the delete command to the terminal to carry an indicator of one or more data items to be deleted by the device management server. How to protect your device data. The method of claim 13, The indicator of one or more data items to be deleted is a data item ID. How to protect your device data. The method of claim 13, The indicator of one or more data items to be deleted is a name of a data item or an IsWipe flag of a data item of the terminal management tree. How to protect your device data. The method of claim 12, Before the step of transmitting the wipe command to the terminal, Transmitting, by the device management server, a get command to the terminal; And Transmitting, by the terminal, the stored ID of the data item that the terminal can delete to the device management server; Terminal data protection method further comprising. The method of claim 16, The ID of the data item comprises a terminal password ID, terminal data protection method. The method of claim 17, The device management server delivers a new terminal password, and the terminal erases the existing terminal password and sets the received new terminal password as the password of the terminal; Overwriting the new terminal password received by the terminal on the existing terminal password, How to protect your device data. As a terminal data protection system, A first device management server including a lock command transfer module; And Including a terminal, The lock command transfer module delivers a lock command that carries lock information instructing the terminal to completely lock or partially lock a function, The lock command is carried through a device management protocol, The terminal includes a first receiving module for receiving the lock command; And a locking module for completely locking or partially locking a function according to the locking information. Terminal data protection system. The method of claim 19, The lock information is an IsFullLocked flag, and the lock module locks all functions when the flag indicates a full lock, and locks the lock module with a preset function when the flag indicates a partial lock. , Terminal data protection system. The method of claim 19, The lock information is an ID of one or more data items to be locked, and wherein the locking module locks a data item corresponding to the ID, Terminal data protection system. The method of claim 21, An acquisition command transfer module for transmitting, by the first device management server, a get command to the terminal; And a second receiving module for receiving a data item ID reported by the terminal. A storage module for storing, by the terminal, an ID of a data item that can be locked by the terminal; And a reporting module for reporting the ID of the data item stored in the first device management server. Terminal data protection system. The method of claim 19, The lock information is an IsFullLocked flag and / or ID of the data item to be locked, If the IsFullLocked flag indicates a full lock, the lock module locks all functions; if the IsFullLocked flag indicates a partial lock, the lock module locks a preset function, and the lock information When configured as a data item ID, the locking module locks the data item corresponding to the ID of the data item. Terminal data protection system. 20. The terminal data protection system of claim 19, wherein the IsFullLocked flag has priority over a data item ID. The method of claim 19, If the lock command delivery module additionally delivers a security code, A second device management server for delivering an unlocking command and a security code to the terminal; The terminal further includes a first determination module and an unlocking module, The first determination module determines whether the security code received from the second device management server is the same as the security code received from the first device management server, and if the security codes are the same, activates the unlocking module, The unlock module performs an unlock operation, Terminal data protection system. The method of claim 25, If the lock command delivery module additionally delivers the ID of the first device management server, The terminal further includes a second determination module, The second determining module compares the ID of the second device management server with the ID of the first device management server and releases the lock if the ID of the second device management server and the ID of the first device management server are the same. Instructing the unlocking module to execute the operation, Terminal data protection system. The method of claim 25, If the lock command delivery module additionally delivers a flag to allow manual unlocking, The terminal further includes a third determination module, The third determining module compares the received code with a preset code and instructs the unlock module to execute the unlock operation if the received code and the preset code are the same; Terminal data protection system. The method of claim 27, If the lock command delivery module further delivers an unlock code, the preset password is the forwarded unlock code; Terminal data protection system. The method of claim 27, And if the lock command transfer module further sends a flag to allow unlocking with a local password, the preset code is a terminal password stored by the terminal. As a terminal data protection system, A device management server including a delete command transfer module transferring a delete command through a device management protocol; And a terminal, The command carries an ID of one or more data items to be deleted, The terminal includes a first receiving module for receiving the delete command sent by a device management server; And a wiping module for deleting a data item corresponding to the data item ID. Terminal data protection system. The method of claim 30, The device management server may include: a get command delivering module for transferring a get command to the terminal; And a second receiving module for receiving an ID of a data item reported from the terminal. The terminal may include a storage module for storing an ID of a data item that the terminal can delete; And a reporting module for reporting the stored data item ID to the device management server. Terminal data protection system. The method of claim 30, If the data item ID includes a terminal password ID and the delete command transfer module additionally delivers a terminal password, The terminal may further include a setting module for deleting an existing terminal password and setting the received new terminal password as a terminal password, or wherein the terminal overwrites the received new terminal password with the existing terminal password. , Terminal data protection system.

Images