SYSTEM AND METHOD FOR DEVICE MANAGEMENT SECURITY OF TRAP MANAGEMENT OBJECT

• US 20100121967A1
• Filed: 04/03/2008
• Published: 05/13/2010
• Est. Priority Date: 04/06/2007
• Status: Active Grant

• Current Assignee: Samsung Electronics Co. Ltd.
• Original Assignee: Samsung Electronics Co. Ltd.
• Inventors: Keum, Ji-Eun, Jun, Hae-Young, Kim, Wuk
• Granted Patent: US 9,160,767 B2
• Time in Patent Office: Days
• US Class Current: 709/229
• CPC Class Codes: G06F 21/6272 by registering files or documents with a third party
• CPC Class Codes: G06F 2221/2115 Third party
• CPC Class Codes: H04L 41/28 Restricting access to network management systems or functions, e.g. using authorisation function to access network configuration
• CPC Class Codes: H04L 63/10 for controlling access to devices or network resources
• CPC Class Codes: H04L 63/20 for managing network security; network security policies in general filtering policies H04L63/0227

Abstract

The present invention relates to a system and method for device management security, and more particularly to a system and method for device management security of a trap management object (Trap MO), which can prevent a non-authorized device management server from indirectly controlling device management of a mobile terminal through use of the Trap MO defined in Open Mobile Alliance Device Management (OMA DM). To this end, when a DM client receives a request to register a notification target MO as a recipient node registration from a DM server, the DM client determines if the DM server has authority for both addition and execution and allows only an authorized DM server to register a recipient node in the Trap MO, so that only a DM server having authority for execution of an MO can execute the MO and control the device management of a mobile terminal. Accordingly, it is possible to enhance device management security of the mobile terminal against non-authorized DM servers.

Claims

1. A system for device management security of trap management object (Trap MO), the system comprising:

a device management (DM) server for transmitting an addition command to add a recipient node to the Trap MO; and

a DM client for determining if the DM server has authority to make the addition command by checking the Trap MO in the DM client when the DM client has received the addition command, determining if the DM server has authority to make an execution command by checking a notification target MO when the DM server has authority to make the addition command, and registering the recipient node in the Trap MO when the DM server has authority to make the execution command.

2. A device management (DM) client comprising:

a DM message transmission/reception block for receiving an addition command to add a recipient node to a trap management object (Trap MO) from a DM server;

an MO storage block for storing the Trap MO and a plurality of management objects (MOs) which are notification targets; and

a security management block for determining, when receiving the addition command, if the DM server has authority to make the addition command by checking the Trap MO, determining if the DM server has authority to make an execution command by checking the notification target MO, and registering the notification target MO as a recipient node in the Trap MO when the DM server has the authority to make the addition command and execution command.

3. A method for device management security of a trap management object (Trap MO), the method comprising the steps of:

receiving, by a device management (DM) client, an addition command to add a recipient node to the Trap MO from a DM server;

determining, by the DM client, if the DM server has authority to make the addition command by checking the Trap MO;

determining if the DM server has authority to make an execution command by checking a notification target MO when the DM server has authority to make the addition command; and

registering a recipient node in the Trap MO when the DM server has authority to make the execution command.

4. The method as claimed in claim 3, further comprising a step of transmitting a registration error message from the DM client to the DM server when the DM server does not have authority to make the addition command.

5. The method as claimed in claim 3, further comprising a step of transmitting a registration error message from the DM client to the DM server when the DM server does not have authority to make the execution command.

6. The method as claimed in claim 3, further comprising a step of transmitting a registration confirmation message to the DM server when the DM client registers the recipient node in the Trap MO.