OMA Device Management: Difference between revisions
Content deleted Content added
Digitallogik (talk | contribs) Cleaned up overview for grammatical issues. Improved links to make them more relevant for OMA DM. |
m →Overview: | Altered template type. Add: pages, issue, volume, journal, date, title, doi, authors 1-5. Changed bare reference to CS1/2. | Use this tool. Report bugs. | #UCB_Gadget |
||
| (33 intermediate revisions by 24 users not shown) | |||
| Line 1: | Line 1: | ||
'''OMA Device Management''' is a [[device management]] protocol specified by the [[Open Mobile Alliance]] (OMA) Device Management (DM) Working Group and the Data Synchronization (DS) Working Group. The current approved specification of OMA DM is version 1.2.1, the latest modifications to this version released in June 2008.<ref name="OMADM1.2.1">{{cite web | |
'''OMA Device Management''' is a [[device management]] protocol specified by the [[Open Mobile Alliance]] (OMA) Device Management (DM) Working Group and the Data Synchronization (DS) Working Group.<ref>[https://www.igi-global.com/chapter/oma-based-framework-updating-modulation/68957 An OMA DM Based Framework for Updating Modulation Module for Mobile Devices: Computer Science & IT Book Chapter | IGI Global]</ref> The current approved specification of OMA DM is version 1.2.1,<ref>[https://internet-access-guide.com/what-is-sprint-omadm/ What Is Sprint OMADM & Its Specifications? - Internet Access Guide]</ref> the latest modifications to this version released in June 2008.<ref name="OMADM1.2.1">{{cite web |title=OMA Device Management V1.2 |publisher=[[Open Mobile Alliance]] |url=http://technical.openmobilealliance.org/technical/release_program/dm_v1_2.aspx |url-status=dead |archive-url=https://web.archive.org/web/20130115013821/http://technical.openmobilealliance.org/technical/release_program/dm_v1_2.aspx |archive-date=2013-01-15 |date=2012 |access-date=2019-10-01}}</ref> The candidate release 2.0 was scheduled to be finalized in September 2013.<ref name="OMADM2.0">{{cite web |title=OMA Device Management V2.0 |publisher=[[Open Mobile Alliance]] |url=http://technical.openmobilealliance.org/technical/release_program/dm_v2_0.aspx |url-status=dead |archive-url=https://web.archive.org/web/20130116223833/http://technical.openmobilealliance.org/technical/release_program/dm_v2_0.aspx |archive-date=2013-01-16 |date=2012 |access-date=2019-10-01}}</ref> |
||
==Overview== |
==Overview== |
||
OMA DM specification is designed for management of [[mobile device]]s such as [[mobile phone]]s, [[Personal digital assistant|PDAs]] and [[Tablet computer|tablet]] computers. Device management is intended to support the following uses: |
OMA DM specification is designed for management of [[mobile device]]s such as [[mobile phone]]s, [[Personal digital assistant|PDAs]], and [[Tablet computer|tablet]] computers.<ref>{{cite journal | url=https://onlinelibrary.wiley.com/doi/abs/10.1002/nem.724 | doi=10.1002/nem.724 | title=OMA DM-based remote software fault management for mobile devices | date=2009 | last1=Kang | first1=Joon-Myung | last2=Ju | first2=Hong-Taek | last3=Choi | first3=Mi-Jung | last4=Hong | first4=James Won-Ki | last5=Kim | first5=Jun-Gu | journal=International Journal of Network Management | volume=19 | issue=6 | pages=491–511 }}</ref> Device management is intended to support the following uses: |
||
* [[Provisioning]] – Configuration of the device (including first time use), enabling and disabling features |
* [[Provisioning (telecommunications)|Provisioning]] – Configuration of the device (including first time use), enabling and disabling features |
||
* Device Configuration – Allow changes to settings and parameters of the device |
* Device Configuration – Allow changes to settings and parameters of the device |
||
* [[FOTA (technology)|Software Upgrades]] – Provide for new software and/or bug fixes to be loaded on the device, including applications and system software |
* [[FOTA (technology)|Software Upgrades]] – Provide for new software and/or bug fixes to be loaded on the device, including applications and system software |
||
* [[Fault management|Fault Management]] – Report errors from the device, query about status of device |
* [[Fault management|Fault Management]] – Report errors from the device, query about status of device |
||
All of the above functions are supported by the OMA DM specification, and a device may optionally implement all or a subset of these features. Since OMA DM specification is aimed at mobile devices, it is designed with sensitivity to the following: |
All of the above functions are supported by the OMA DM specification, and a device may optionally implement all or a subset of these features. Since OMA DM specification is aimed at mobile devices, it is designed with sensitivity to the following: |
||
* small |
* small footprint devices, where memory and storage space may be limited |
||
* constraint on bandwidth of communication, such as in wireless connectivity |
* constraint on bandwidth of communication, such as in wireless connectivity |
||
* tight security, as the devices are vulnerable to software attacks; authentication and challenges are made part of the specifications |
* tight security, as the devices are vulnerable to software attacks; authentication and challenges are made part of the specifications |
||
| Line 17: | Line 17: | ||
Technically, the OMA DM protocol uses [[XML]] for data exchange, more specifically the sub-set defined by [[SyncML]]. The device management takes place by communication between a server (which is managing the device) and the client (the device being managed). OMA DM is designed to support and utilize any number of data transports such as: |
Technically, the OMA DM protocol uses [[XML]] for data exchange, more specifically the sub-set defined by [[SyncML]]. The device management takes place by communication between a server (which is managing the device) and the client (the device being managed). OMA DM is designed to support and utilize any number of data transports such as: |
||
* physically over both wireline ([[USB]], [[RS-232]]) and wireless media ([[GSM]], [[CDMA]], [[Infrared Data Association|IrDA]] or [[Bluetooth]]) |
* physically over both wireline ([[USB]], [[RS-232]]) and wireless media ([[GSM]], [[CDMA]], [[Infrared Data Association|IrDA]], or [[Bluetooth]]) |
||
* transport layers implemented over any of [[Wireless Session Protocol|WSP]] ([[Wireless Application Protocol|WAP]]), [[HTTP]] or [[OBEX]] or similar transports |
* transport layers implemented over any of [[Wireless Session Protocol|WSP]] ([[Wireless Application Protocol|WAP]]), [[HTTP]], or [[OBEX]] or similar transports |
||
The communication protocol is a request-response protocol. Authentication and challenge of authentication are built-in to ensure the server and client are communicating only after proper validation. The server and client are both stateful, meaning a specific sequence of messages are to be exchanged only after authentication is completed to perform any task. |
The communication protocol is a request-response protocol. Authentication and challenge of authentication are built-in to ensure the server and client are communicating only after proper validation. The server and client are both stateful, meaning a specific sequence of messages are to be exchanged only after authentication is completed to perform any task. |
||
The communication is initiated by the OMA DM server, asynchronously, using any of the methods available such as a WAP Push or [[SMS]]. The initial message from server to client is said to be in the form of a notification, or alert message. |
The communication is initiated by the OMA DM server, asynchronously, using any of the methods available such as a [[Wap_push#WAP_Push|WAP Push]] or [[SMS]]. The initial message from server to client is said to be in the form of a notification, or alert message. |
||
Once the communication is established between the server and client, a sequence of messages might be exchanged to complete a given device management task. OMA DM does provide for alerts, which are messages that can occur out of sequence, and can be initiated by either server or client. Such alerts are used to handle errors, abnormal terminations etc. |
Once the communication is established between the server and client, a sequence of messages might be exchanged to complete a given device management task. OMA DM does provide for alerts, which are messages that can occur out of sequence, and can be initiated by either server or client. Such alerts are used to handle errors, abnormal terminations etc. |
||
| Line 30: | Line 30: | ||
Error recovery based on timeouts are not specified completely, hence, different implementations could possibly differ (protocol is not fully specified relating to these, and seem to leave them open intentionally). |
Error recovery based on timeouts are not specified completely, hence, different implementations could possibly differ (protocol is not fully specified relating to these, and seem to leave them open intentionally). |
||
The protocol specifies exchange of Packages during a session, each package consisting of several messages and each message in turn consisting of one or more commands. The server initiates the commands and the client is expected to execute the commands and return the result via a reply message. |
The protocol specifies exchange of Packages during a session, each package consisting of several messages, and each message in turn consisting of one or more commands. The server initiates the commands and the client is expected to execute the commands and return the result via a reply message. |
||
==See also== |
|||
==Implementations and application support== |
|||
* [[List of Mobile Device Management software]] |
|||
OMA DM is supported by several mobile devices, such as PDAs and mobile phones. |
|||
* [[Mobile Device Management]] |
|||
Supported mobile device platforms include: |
|||
*Nokia [[Series 40]] ([[Nokia OS]]-based) |
|||
*Nokia [[S60 (software platform)|S60]] ([[Symbian OS]]-based) |
|||
*Nokia [[Series 80]] (Symbian OS-based) |
|||
*[[UIQ]] (Symbian OS-based) |
|||
*[[Zyxel]] [[WiMAX]] Series |
|||
*[[Sony Ericsson]] (Xperia series) ([[Android (operating system)|Android]]-based) |
|||
*[[Windows_8.1]] and Windows RT 8.1 |
|||
*[[Microsoft]] [[Windows Mobile]]<ref name="Windows Mobile">{{cite web | url = http://msdn2.microsoft.com/en-us/library/bb737369.aspx | title = OMA Device Management | publisher = [[MSDN]] | accessdate = 2008-03-07}}</ref> |
|||
*[[BlackBerry_(company)|BlackBerry]] [[Blackberry_OS|OS]] (Some devices) |
|||
*[[BlackBerry_(company)|BlackBerry]] [[BlackBerry_10|10]] (Some devices, ie STL100-4 variant of the [[BlackBerry_Z10|Z10]] model) |
|||
Even though these implementations are based on OMA DM, the manufacturers continue to package it as a proprietary solution, supposedly due to security and the alleged need for tight control over the device management. |
|||
==References== |
==References== |
||
| Line 52: | Line 40: | ||
==External links== |
==External links== |
||
*[http:// |
* [http://jcp.org/en/jsr/detail?id=233 JSR 233: J2EE Mobile Device Management and Monitoring Specification] |
||
*[http:// |
* [http://www.openmobilealliance.org/Technical/DM.aspx OMA Device Management Working Group] |
||
*[http:// |
* [http://www.openmobilealliance.org/wp/Overviews/dm_overview.html Open Mobile Alliance - Device Management Overview] |
||
*[http://www.eclipse.org/koneki/simulators/omadm/ Open Source OMA-DM simulator - Eclipse Koneki project] |
* [http://www.eclipse.org/koneki/simulators/omadm/ Open Source OMA-DM simulator - Eclipse Koneki project] |
||
{{Open Mobile Alliance standards}} |
{{Open Mobile Alliance standards}} |
||
Latest revision as of 23:03, 25 June 2024
OMA Device Management is a device management protocol specified by the Open Mobile Alliance (OMA) Device Management (DM) Working Group and the Data Synchronization (DS) Working Group.[1] The current approved specification of OMA DM is version 1.2.1,[2] the latest modifications to this version released in June 2008.[3] The candidate release 2.0 was scheduled to be finalized in September 2013.[4]
Overview
[edit]OMA DM specification is designed for management of mobile devices such as mobile phones, PDAs, and tablet computers.[5] Device management is intended to support the following uses:
- Provisioning – Configuration of the device (including first time use), enabling and disabling features
- Device Configuration – Allow changes to settings and parameters of the device
- Software Upgrades – Provide for new software and/or bug fixes to be loaded on the device, including applications and system software
- Fault Management – Report errors from the device, query about status of device
All of the above functions are supported by the OMA DM specification, and a device may optionally implement all or a subset of these features. Since OMA DM specification is aimed at mobile devices, it is designed with sensitivity to the following:
- small footprint devices, where memory and storage space may be limited
- constraint on bandwidth of communication, such as in wireless connectivity
- tight security, as the devices are vulnerable to software attacks; authentication and challenges are made part of the specifications
Technical description
[edit]OMA DM was originally developed by The SyncML Initiative Ltd, an industry consortium formed by many mobile device manufacturers. The SyncML Initiative got consolidated into the OMA umbrella as the scope and use of the specification was expanded to include many more devices and support global operation.
Technically, the OMA DM protocol uses XML for data exchange, more specifically the sub-set defined by SyncML. The device management takes place by communication between a server (which is managing the device) and the client (the device being managed). OMA DM is designed to support and utilize any number of data transports such as:
- physically over both wireline (USB, RS-232) and wireless media (GSM, CDMA, IrDA, or Bluetooth)
- transport layers implemented over any of WSP (WAP), HTTP, or OBEX or similar transports
The communication protocol is a request-response protocol. Authentication and challenge of authentication are built-in to ensure the server and client are communicating only after proper validation. The server and client are both stateful, meaning a specific sequence of messages are to be exchanged only after authentication is completed to perform any task.
The communication is initiated by the OMA DM server, asynchronously, using any of the methods available such as a WAP Push or SMS. The initial message from server to client is said to be in the form of a notification, or alert message.
Once the communication is established between the server and client, a sequence of messages might be exchanged to complete a given device management task. OMA DM does provide for alerts, which are messages that can occur out of sequence, and can be initiated by either server or client. Such alerts are used to handle errors, abnormal terminations etc.
Several parameters relating to the communication such as the maximum message size can be negotiated between the server and client during the initiation of a session. In order to transfer large objects, the protocol does allow for sending them in smaller chunks.
Error recovery based on timeouts are not specified completely, hence, different implementations could possibly differ (protocol is not fully specified relating to these, and seem to leave them open intentionally).
The protocol specifies exchange of Packages during a session, each package consisting of several messages, and each message in turn consisting of one or more commands. The server initiates the commands and the client is expected to execute the commands and return the result via a reply message.
See also
[edit]References
[edit]- ^ An OMA DM Based Framework for Updating Modulation Module for Mobile Devices: Computer Science & IT Book Chapter | IGI Global
- ^ What Is Sprint OMADM & Its Specifications? - Internet Access Guide
- ^ "OMA Device Management V1.2". Open Mobile Alliance. 2012. Archived from the original on 2013-01-15. Retrieved 2019-10-01.
- ^ "OMA Device Management V2.0". Open Mobile Alliance. 2012. Archived from the original on 2013-01-16. Retrieved 2019-10-01.
- ^ Kang, Joon-Myung; Ju, Hong-Taek; Choi, Mi-Jung; Hong, James Won-Ki; Kim, Jun-Gu (2009). "OMA DM-based remote software fault management for mobile devices". International Journal of Network Management. 19 (6): 491–511. doi:10.1002/nem.724.