METHOD FOR ADDRESSING A MANAGEMENT OBJECT NODE IN A DEVICE MANAGEMENT TREE OF A MOBILE DEVICE

DESCRIPTION

FIELD

[0001] The present invention relates to the field of managing mobile devices using Open Mobile Alliance Device Management (OMA DM) protocol. More particularly, the present invention relates to addressing a management object node in a device management tree of a mobile device.

BACKGROUND

[0002] A Device Management (DM) group is part of an Open Mobile Alliance (OMA) and specifies an interoperable way to manage one or more mobile devices. The DM is used to manage one or more of software, firmware upgrade and connectivity parameters for Wireless Application Protocol (WAPyGeneral Packet Radio Service (GPRS) of the mobile devices. An OMA DM protocol basically operates on a device management tree which is a collection of management objects in a hierarchical tree structure. Each mobile device that supports the OMA DM protocol contains the device management tree. The management objects are logical collections of related Management Object (MO) nodes that enable the targeting of management operations using commands of the OMA DM protocol. The MO nodes can be uniquely identified with a Uniform Resource Identifier (URI). Each MO represents a particular functionality of a mobile device, for example information pertaining to WAP/GPRS connection, software or firmware. In an existing scenario, the DM server needs to address an MO node using an absolute path of the MO node. Often, it is desired to address the MO node without using the absolute path.

[0003] Some of the MOs are standardized within the OMA DM group so as to be interoperable with most of the mobile devices. Examples of the standardized MOs include, DM Account (DMAcc), Device Detail (DevDetail) and Device Information (Devlnfo). In order to operate on a particular mobile device, a DM Server requires a Device Description Framework (DDF), defined by a manufacturer, to represent the device management tree of the mobile device. However, the DDF can vary from one mobile device model to another as per the manufacturer.

[0004] The DM Server uses the DDF to issue commands on the device management tree. In the OMA DM protocol, a Device Management Tree and Description (DMTND) provides certain rules for identifying the MO node. These rules are to be strictly followed for addressing any MO node.

[0005] In such a case, the DM Server has to compile the commands separately for each mobile device model based on the associated DDF, which gives rise to complexity. Hence, there is a need to address the MO node without the knowledge of the DDF for the particular mobile device.

[0006] In light of the foregoing discussion, there is a need for an address mechanism to address a management object node in a device management tree of a mobile device.

SUMMARY
[0007] Embodiments of the present invention provide a method and device management server for addressing a management object node in a device management tree of a mobile device.

[0008] An example of a method for addressing a Management Object (MO) node in a device management tree of a mobile device includes generating an address path for the MO node using a Management Object Identifier (MOl). The method also inctudes addressing the MO node based on the address path.

[0009] An example of a Device Management (DM) server includes a processor for operating at least one application. The processor includes a generating module for generating an address path for a Management Object (MO) node. The processor also includes an addressing module for addressing the MO node based on the address path.

BRIEF DESCRIPTION OF THE DRAWINGS

[0010] FIG. 1 is a block diagram illustrating a device management server for addressing a management object node in a device management tree of a mobile device, in accordance with which various embodiments can be implemented;

[0011] FIG. 2 illustrates a method for addressing a management object node in a device management tree of a mobile device, in accordance with one embodiment;

[0012] FIG. 3 illustrates a method for addressing a management object node in a device management tree of a mobile device, in accordance with another embodiment;

[0013] F'C. 4A is an exemplary illustration of a server request to a management object node by a device management server, in accordance with one embodiment;

[0014] FIG. 4B is an exemplary illustration of a response from a mobile device to a device management server, in accordance with one embodiment; and

[0015] FIG. 4C is an exemplary illustration of a server request to a management object node by a device management server, in accordance with another embodiment.

DETAILED DESCRIPTION

[0006] It should be observed that method steps and system components have been represented by conventional symbols in the figures, showing only specific details that are relevant for an understanding of the present invention. Further, details that may be readily apparent to person ordinarily skilled in the art may not have been disclosed.

[0017] Embodiments of the present invention provide a method and device management server for addressing a management object node in a device management tree of a mobile device.

[0018] FIG. 1 is a block diagram illustrating a Device Management (DM) server 105 for addressing a management object node in a device management tree of a mobile device no, in accordance with which various embodiments can be implemented. It is a client server network where the mobile device 110 acts as a DM client to the DM server 105,

[0019] The DM server 105 includes a bus 115 or other communication mechanism for communicating information. The DM server 105 includes a processor 120 coupled with the bus 110 for operating at least one application. The DM server 105 also includes a memory 125, for example a random access memory (RAM) or other dynamic storage device, coupled to the bus 115 for storing information which can be used by the processor 120. The memory 125 can also be used for storing any temporary information required by the processor 120, for example an address path. The DM server 105 further includes a read only memory (ROM) 130 or other static storage device coupled to the bus 115 for storing static information for the processor 120. A storage unit 135, for example, a magnetic disk or optical disk, is provided and coupled to the bus 115 for storing information.

[0020] The processor 120 can include or be connected to one or more processing units, for example, a generating module 140 and an addressing module 145. The generating module 140 is used for generating an address path for the Management Object (MO) node. The addressing module 145 addresses the MO node based on the address path.

[0021] The bus 115 is coupled to a display 150, for example a cathode ray tube (CRT), a liquid crystal display (LCD) or a light emitting diode (LED) display, for displaying information to a user. An input device 155, including alphanumeric and other keys, is coupled to the bus 115 for communicating an input to the processor 120. Another type of user input device is a cursor control 160, for example a mouse, a trackball, or cursor direction keys for communicating an input to the processor 120 and for controlling cursor movement on the display 150. The input device 155 can be included in the display 150, for example a touch screen.

[0022] Various embodiments are related to the use of the DM server 105 for implementing the techniques described herein. In one embodiment, the techniques are performed by the processor 120 using information included in the memory 125. The information can be read into the memory 125 from another machine-readable medium, for example, the storage unit 135.

[0023] The term "machine-readable medium" as used herein refers to any medium that participates in providing data that causes a machine to operate in a specific fashion. In an embodiment implemented using the DM server 105, various machine-readable medium are involved, for example, in providing information to the processor 120. The machine-readable medium can be a storage media. Storage media includes both nonvolatile media and volatile media. Non-volatile media includes, for example, optical or magnetic disks, for example, the storage unit 135. Volatile media includes dynamic memory, for example, the memory 125. All such media must be tangible to enable the information carried by the media to be detected by a physical mechanism that reads the information into a machine.

[24] Common forms of machine-readable medium include, for example, a floppy disk, a flexible disk, hard disk, magnetic tape, or any other magnetic medium, a CD- ROM, any other optical medium, punchcards, papertape, any other physical medium with patterns of holes, a RAM, a PROM, and EPROM, a FLASH-EPROM, any other memory chip or cartridge.

[0025] In another embodiment, the machine-readable medium can be a transmission media including coaxial cables, copper wire and fiber optics, including the wires that include the bus 115. Transmission media can also take the form of acoustic or light waves, for example, those generated during radio-wave and infra-red data communications.

[0026] The DM server 105 also includes a communication interface 165 coupled to the bus 115. The communication interface 165 provides a two-way data communication coupling to a network 170. For example, the communication interface 165 can be a local area network card to provide a data communication connection to a compatible local area network. Wireless links can also be implemented. In any such implementation, the communication interface 165 sends and receives electrical signals that cany digital data streams representing various types of information. The communication interface 165 can be a universal serial bus port. The DM server 105 is in electronic communication with one or more mobile devices, for example the mobile device 110, through the communication interface 165 and the network 170. Examples of the network 170 include, but are not limited to, local area networks, wide area networks, wired networks, metropolitan area networks, internet, bluetooth, zigbee technology and wireless networks.

[0027] In some embodiments, the mobile device 110 functions similar to the DM server 105. The mobile device 110 further includes elements present in the DM server 105. In such an implementation, the mobile device 110 generates an absolute path which is sent to the DM server 105.

[0028] FIG. 2 illustrates a method for addressing a management object node in a device management tree of a mobile device, in accordance with one embodiment.

[0029] The method starts at step 205.

[0030] At step 210, an address path for a Management Object (MO) node is generated using a Management Object Identifier (MOI). A Device Management (DM) server generates the address path for each command that needs to be sent to the mobile device. For the DM server to issue one or more commands to the mobile device, the DM server includes the address path in a server request. An addressing mechanism identifier in the address path identifies an addressing mechanism used. For example, if the addressing mechanism identifier is ''urn" or any other combination of characters, the MOI can be identified as the addressing mechanism. The addressing mechanism identifier um is a shortened form of Uniform Resource Name. The MOI is an identifier associated with a Management Object (MO). The MOI identifies the MO node of the device management tree to be managed. The MO node reflects a set of configuration parameters for the mobile device. Actions that can be taken against the MO node include, but are not limited to, reading and setting parameter keys and values. Another type of MO node can be a run time environment for software applications on the mobile device. The actions that can be taken against this type of MO node includes, but are not limited to, installing, upgrading, or uninstalling software elements.

[0031] The address path includes, but is not limited to, the addressing mechanism identifier, the MOI and the MO node. If RDMOI is to be used, the address path includes, but is not limited to, the addressing mechanism identifier, the RDMOI and the MO node.

[0032] At step 215, the MO node is addressed based on the address path. The address path generated is included in the server request and is sent by the DM server to the mobile device. The MO node to which the command needs to be issued can therefore be addressed based on the address path generated.

[0033] The commands can further be issued by the DM server based on the addressing.

[0034] The method stops at step 220.

[0035] In some embodiments, the DM server receives an absolute path from the mobile device in response to the addressing. The absolute path is a detailed path in the device management tree including each section traversed to reach the MO node. The absolute path usually starts with a root of the device management tree.

[0036] FIG. 3 illustrates a method for addressing a management object node in a device management tree of a mobile device, in accordance with another embodiment.

[0037] The method starts at step 305.

|0038] At step 310, an address path for a Management Object (MO) node is generated using a Management Object Identifier (MOI). A Device Management (DM) server generates the address path for each command that needs to be sent to the mobile device. For the DM server to issue one or more commands to the mobile device, the DM server includes the address path in a server request. An addressing mechanism identifier in the address path identifies an addressing mechanism used. For example, if the addressing mechanism identifier is "urn" or any other combination of characters, the MOI can be identified as the addressing mechanism. The addressing mechanism identifier urn is a shortened form of Uniform Resource Name. The MOI is an identifier associated with a Management Object (MO). The MOI identifies the MO node of the device management tree to be managed. The MO node reflects a set of configuration parameters for the mobile device. Actions that can be taken against the MO node include, but are not limited to, reading and setting parameter keys and values. Another type of MO node can be a run time environment for software applications on the mobile device. The actions that can be taken against this type of MO node includes, but are not limited to, installing, upgrading, or uninstalling software elements.

[0039] In some embodiments, the MOI is defined by Open Mobile Naming Authority (OMNA) which is an Open Mobile Alliance (OMA) group.

[0040] In other embodiments, the MOI is defined by Reverse Domain Management Object Identifier (RDMOI) which is a Device Management Tree and Description (DMTND) method.

[0041] The address path includes, but is not limited to, the addressing mechanism identifier, the MOI and the MO node. If RDMOI is to be used, the address path includes, but is not limited to, the addressing mechanism identifier, the RDMOI and the MO node.

[0042] At step 315, the MO node is addressed based on the address path. The address path generated is included in the server request and is sent by the DM server to the mobile device. The MO node to which the command needs to be issued can therefore be addressed based on the address path generated.

[0043] At step 320, the commands can further be issued by the DM server based on the addressing.

[0044] A DM client residing on the mobile device receives the server request from the DM server and further processes the server request. The DM client identifies the MO node based on the addressing mechanism identifier, maps it to a system implementation, and performs an operation requested in the server request.

[45] At step 325, an absolute path is received from the mobile device in response to the addressing. The DM client in the mobile device generates the absolute path and sends the absolute path to the DM server, after performing the operation specified in the server request.

[0046] In some embodiments, the DM server receives error messages if the mobile device does not support the MO node as identified in the server request.

[0047] The method stops at step 330.

[0048] FIG. 4A is an exemplary illustration of a server request to a MO node by a DM server, in accordance with one embodiment. The server request by the DM server can be sent in Extensible Markup Language (XML) format or any other suitable format. The DM server is requesting a mobile device to add certain data, for example Wireless Application Protocol (WAP) settings for the MO node CNN. Hence an address path 405 is generated by the DM server and is included in the server request. For example, the address path 405 can resemble the following path:

urn:oma:oma-wap settings: 1.0/CNN

[0049] In the above address path 405,"urn:" is an addressing mechanism identifier used to identify if MOI is the addressing mechanism. The addressing mechanism identifier can also be any combination of characters. The portion after the addressing mechanism identifier which is "oma:oma-wap_settings:L0", identifies the MOL The MOI is followed by a separator "/" and the MO node CNN. The MO node in the exemplary illustration identifies the WAP settings to access the WAP website for the MO node, for example Cable News Network (CNN).

[0050] A response to the server request sent from the mobile device is explained in conjunction with FIG. 4B.

[005l] FIG. 4B is an exemplary illustration of a response from the mobile device to the DM server, in accordance with one embodiment. The response by the mobile device can be sent in XML format or any other suitable format. The response includes an absolute path 410. On receiving the server request from the DM server, the mobile device can directly operate on the MO node and respond with the absolute path 410, since the addressing mechanism is based on the MOI. For example, the absolute path 410 is of the following path:

./settings/wapsettings/CNN

[0052] In the above absolute path 410, "./" is a root of the device management tree followed by a path traversed to obtain WAP settings of the MO node CNN.

[0053] In some embodiments, the absolute path 410 can be stored for further usage.

[0054] In case of RDMOI, the addressing uses the RDMOI to represent the address path which is explained in conjunction with FIG. 4C.

[0055] FIG. 4C is an exemplary illustration of a server request to a MO node by a DM server, in accordance with another embodiment. The DM server requests a mobile device to send certain data, for example WAP settings of the MO node, CNN. Hence an address path 415 is generated by the DM server and is included in the server request. For example, the address path 415 can resemble the following path:

urn:com.companyx/1.2/wapsettings/CNN

[0056] In the above address path 415,"urn:" is an addressing mechanism identifier used to identify if MOI is the addressing mechanism. The addressing mechanism identifier can also be any combination of characters. The portion after the addressing mechanism identifier which is "com.companyx/1.2/wap_settings", identifies the RDMOI. The RDMOI is followed by a separator "/" and CNN which is the MO node being addressed.

[0057] In some embodiments, if the RDMOI is not supported by the mobile device an error is reported to the DM server.

[0058] The address path using the MOI makes the addressing of the MO node simple and less cumbersome. The addressing further enables easy identification of the MO node thereby saving computational time at both the DM server and the mobile device.

[0059J The foregoing description sets forth numerous specific details to convey a thorough understanding of embodiments of the present invention. However, it will be apparent to one skilled in the art that embodiments of the present invention may be practiced without these specific details. Some well-known features are not described in detail in order to avoid obscuring the present invention. Other variations and embodiments are possible in light of above teachings, and it is thus intended that the scope of the present invention not be limited by this Detailed Description, but only by the Claims.

CLAIMS I/We claim:

1. A method for addressing a Management Object (MO) node in a device management tree of a mobile device, the method comprising:

generating an address path for the MO node using a Management Object Identifier (MOI); and

addressing the MO node based on the address path.

2. The method of claim 1 further comprising:
issuing one or more commands from a Device Management (DM) server to the mobile device based on the addressing.

3. The method of claim 1 further comprising:
receiving an absolute path from the mobile device in response to the addressing.

4. The method of claim I, wherein the MOI is defined by Open Mobile Naming Authority (OMNA).

5. The method of claim 1, wherein the MOI is defined by Reverse Domain Management Object Identifier (RDMOI).

6. The method of claim 1, wherein the address path comprises one or more of an addressing mechanism identifier, the MOI and the MO node.

7. The method of claim 1, wherein the address path comprises one or more of an addressing mechanism identifier, a Reverse Domain Management Object Identifier (RDMOI) and the MO node.

8. A Device Management (DM) server comprising:

a processor for operating at least one application, the processor comprising:

a generating module for generating an address path for a Management Object (MO) node; and

an addressing module for addressing the MO node based on the address path.

9. A system for performing a method, the method as described herein and in accompanying figures.

10. A method for addressing a management object node by a Device Management (DM) server, the DM server as described herein and in accompanying figures.