TECHNIQUES FOR MANAGING DEVICES NOT DIRECTLY ACCESSIBLE TO DEVICE MANAGEMENT SERVER

• US 20110238806A1
• Filed: 03/21/2011
• Published: 09/29/2011
• Est. Priority Date: 03/29/2010
• Status: Active Grant

• Current Assignee: Samsung Electronics Co. Ltd. (Samsung Group)
• Original Assignee: Samsung Electronics Co. Ltd. (Samsung Group)
• Inventors: BHAT, Kong Posh, NGUYEN, Nhut
• Granted Patent: US 10,051,074 B2
• Time in Patent Office: Days
• US Class Current: 709/223
• CPC Class Codes: H04L 41/0233 Object-oriented techniques, for representation of network management data, e.g. common object request broker architecture [CORBA]
• CPC Class Codes: H04L 41/08 Configuration management of networks or network elements address allocation H04L61/50
• CPC Class Codes: H04L 61/2589 over a relay server, e.g. traversal using relay for network address translation [TURN]
• CPC Class Codes: H04L 67/125 involving control of end-device applications over a network
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: H04L 67/56 Provisioning of proxy services store-and-forward switching systems in data switching networks H04L12/54
• CPC Class Codes: H04W 4/50 Service provisioning or reconfiguring

Abstract

Methods and devices for managing devices not directly accessible to device management server are provided. A device for communicating a Location Update Alert message to a Device Management (DM) Server via a DM Gateway includes a memory for storing code of a DM client and a plurality of DM MOs, each of the plurality of DM MOs including one or more nodes, a processor for executing the code of the DM client stored in the memory, a communications unit for receiving and sending messages for the DM client, and the DM client for communicating a Location Update Alert message to the DM Server via the DM Gateway upon detecting a change in an address of the device, based on a LocationUpdate node of at least one of the plurality of DM MOs.

Claims

1. A device for performing Device Management (DM) Gateway bootstrapping, the device comprising:

a memory for storing code of a DM client and a plurality of DM Management Objects (MOs), each of the plurality of DM MOs including one or more nodes;

a processor for executing the code of the DM client stored in the memory;

a communications unit for receiving and sending messages for the DM client; and

the DM client for performing the DM Gateway bootstrapping based on at least one node included in at least one of the plurality of DM MOs.

2. The device of claim 1, wherein the at least one of the plurality of DM MOs, that includes the node based on which the DM client performs the DM Gateway bootstrapping, comprises a DM Account (DMAcc) MO.

3. The device of claim 1, wherein the at least one of the plurality of DM MOs, that includes the node based on which the DM client performs the DM Gateway bootstrapping, or the at least one node based on which the DM client performs the DM Gateway bootstrapping, is referenced in a DMAcc MO.

4. The device of claim 1, wherein the at least one of the plurality of DM MOs, that includes the node based on which the DM client performs the DM Gateway bootstrapping, does not comprise a DM Account (DMAcc) MO.

5. The device of claim 1, wherein the at least one node comprises a DMGateway node.

6. The device of claim 5, wherein the DMGateway node comprises the properties:

7. The device of claim 1, wherein the at least one node comprises a Mode node that identifies whether a DM Gateway is operating in one of a Transparent Mode, a Transparent Mode, and a Protocol Adaptation Mode,

wherein, when in the Transparent Mode, the DM Gateway maintains a mapping between the local/private and global/public identity of the device to assist a DM Server in sending a notification to the DM Client,

wherein, when in the Proxy Mode, the DM Gateway manages the device on behalf of another DM Server, and

wherein, when in the Protocol Adaptation Mode, the DM Gateway manages non-Open Mobile Alliance (OMA)-DM devices on behalf of another DM Server.

8. The device of claim 7, wherein the Mode node comprises the properties:

9. The device of claim 7, wherein the at least one node comprises an DMGateway node that is a parent node to the Mode node.

10. The device of claim 1, wherein the at least one node comprises a RefreshInterval node that specifies an interval within which the device and the DM Gateway must exchange a communication in order for the DM Gateway bootstrapping information to remain valid.

11. The device of claim 10, wherein the RefreshInterval node comprises the properties:

12. The device of claim 10, wherein the at least one node comprises an DMGateway node that is a parent node to the RefreshInterval node.

13. The device of claim 1, wherein the at least one node comprises a ExpiryTime node that specifies the time at which the Gateway bootstrapping information in the device will lapse, unless renewed.

14. The device of claim 13, wherein the ExpiryTime node comprises the properties:

15. The device of claim 13, wherein the at least one node comprises an DMGateway node that is a parent node to the ExpiryTime node.

16. A device for communicating a Location Update Alert message to a Device Management (DM) Server via a DM Gateway, the device comprising:

a memory for storing code of a DM client and a plurality of DM Management Objects (MOs), each of the plurality of DM MOs including one or more nodes;

a processor for executing the code of the DM client stored in the memory;

a communications unit for receiving and sending messages for the DM client; and

the DM client for communicating a Location Update Alert message to the DM Server via the DM Gateway upon detecting a change in an address of the device, based on a LocationUpdate node of at least one of the plurality of DM MOs.

17. The device of claim 16, wherein the at least one of the plurality of DM MOs that includes the LocationUpdate node comprises a DM Account (DMAcc) MO.

18. The device of claim 16, wherein the at least one of the plurality of DM MOs that includes the LocationUpdate node or the LocationUpdate node, is referenced in a DMAcc MO.

19. The device of claim 16, wherein the at least one of the plurality of DM MOs that includes the LocationUpdate node does not comprise a DM Account (DMAcc) MO.

20. The device of claim 16, wherein the LocationUpdate node comprises the properties:

21. The device of claim 16, wherein the Location Update Alert message includes information on one or more of a hardware address of the device, an old address of the device, and a new address of the device.

22. The device of claim 16, wherein the Location Update Alert message uses a Generic Alert mechanism defined by a Open Mobile Alliance (OMA)-DM Protocol.

23. A method for operating a device including a Device Management (DM) Client to communicate a Location Update Alert message to a DM Server, the method comprising:

determining whether an address of the device has changed from other than one local address to another local address;

if it is determined that the address change from other than one local address to another local address, determining whether at least one DM Account (DMAcc) Management Object (MO) is located for which a LocationUpdate node has a value set to true;

if at least one DMAcc MO is located for which the LocationUpdate node has a value set to true, determining whether there is at least one DM Gateway in Proxy or Adaptation mode;

if it is determined that there is at there is not at least one DM Gateway in Proxy or Adaptation mode, directly communicating the Location Update Alert message to any DM Server associated with the at least one DMAcc MO for which the LocationUpdate node has a value set to true; and

if it is determined that there is at there is at least one DM Gateway in Proxy or Adaptation mode, communicating the Location Update Alert message to any DM Gateway that is in the Proxy or Adaptation mode and associated with the at least one DMAcc MO for which the LocationUpdate node has a value set to true.

24. The method of claim 23, wherein the determining of whether there is at least one DM Gateway in Proxy or Adaptation mode comprises searching for any DMAcc MOs that contain a Mode node that is set to a value of Proxy or Protocol Adaptation.

25. A method of transmitting a notification message from a Device Management (DM) Server, the method comprising:

generating the notification message; and

transmitting the notification message,

wherein the notification message includes a header and a body, the body of the notification message including at least one of a <

moi-code>

field and a <

reason-code>

field.

26. The method of claim 25, wherein each of the <

moi-code>

field and the <

reason-code>

field is 8 bits.

27. The method of claim 25, wherein the <

moi-code>

field specifies a MO identifier code for which there is a binding between an MO identifier and the MO identifier code in a MO, and the <

reason-code>

field specifies a reason code for which there is a binding between a reason string and the reason code in a MO.

28. The method of claim 25, wherein a bit set to true in a <

moi-present>

field included in the header of the notification message indicates that the <

moi-code>

field is present in the body of the notification message, and a bit set to true in a <

reason-present>

field included in the header of the notification message indicates that the <

reason-code>

field is present in body of the notification message.

29. A method for a Device Management (DM) Gateway to process messages from a DM server, the method comprising:

receiving a message from a DM server for a target device associated with the DM Gateway;

determining whether the DM Gateway is bootstrapped to the DM Server that sent the message;

if it is determined that the DM Gateway is not bootstrapped to the DM Server that sent the message, determining whether the DM Gateway should forward the message to the target device despite the DM Gateway not being bootstrapped to the DM Server that sent the message; and

if it is determined that the DM Gateway should forward the message to the target device despite the DM Gateway not being bootstrapped to the DM Server that sent the message, forwarding the message to the target device.

30. The method of claim 29, wherein the receiving of the message from a DM server for the target device associated with the DM Gateway comprises:

receiving the message from a DM server; and

determining whether the target device of the received message is associated with the DM Gateway by determining whether the target device has an entry in the LAN Device Inventory MO.

31. The method of claim 29, wherein the determining of whether the DM Gateway should forward the message to the target device despite the DM Gateway not being bootstrapped to the DM Server that sent the message comprises:

determining whether a LAN Device Inventory MO entry for the target device includes the DM Server that sent the message in a list of bootstrapped servers for the target device.

32. The method of claim 31, wherein the determining of whether the DM Gateway should forward the message to the target device despite the DM Gateway not being bootstrapped to the DM Server that sent the message further comprises:

if it is determined that the DM Server that sent the message is included in a list of bootstrapped servers for the target device, determining whether the DM Server that sent the message is included in a Blacklist of the DM Gateway; and

if it is determined that the DM Server that sent the message ID is not included in the Blacklist, forwarding the message to the target device.

33. The method of claim 32, wherein the determining of whether the DM Gateway should forward the message to the target device despite the DM Gateway not being bootstrapped to the DM Server that sent the message further comprises:

if it is determined that the DM Server that sent the message ID is included in the Blacklist, determining whether there is a management override against the blacklisting of the DM Server that sent the message, and if it is determined that there is a management override against the blacklisting of the DM Server that sent the message, forwarding the message to the target device.