computer science

OMA Device Management

OMA Device Management is a computer science topic covered in the lgStudy science library. This page brings together a partial reference excerpt, illustrations, worked examples, real-world applications and a short study plan, so you can understand OMA Device Management rather than just read about it. In short: 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.

Key takeaways

OMA Device Management belongs to computer science; place it in that map before memorising details.
Learn the definition first, then one example that makes the definition concrete.
Connect OMA Device Management to a quantity you can measure, compute or draw — that is where exam questions come from.
Reproduce the core statement of OMA Device Management from memory before moving on to harder problems.

Reference excerpt

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. The candidate release 2.0 was scheduled to be finalized in September 2013.

Overview OMA DM specification is designed for management of mobile devices such as mobile phones, PDAs, and tablet computers. 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 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 List of Mobile Device Management software Mobile Device Management

References

External links JSR 233: J2EE Mobile Device Management and Monitoring Specification OMA Device Management Working Group Open Mobile Alliance - Device Management Overview Open Source OMA-DM simulator - Eclipse Koneki project

Worked examples

Example 1 — a first encounter with OMA Device Management

Start with the simplest possible case. Write down what OMA Device Management claims or describes in one sentence, then invent the smallest concrete situation in which that sentence is true. In computer science, the smallest case is usually a single object, a single equation or a single measurement. Check that every symbol or term in your sentence has a meaning in that case.

Example 2 — changing one variable

Take the situation from Example 1 and change exactly one quantity: double it, halve it, or set it to zero. Predict what should happen to OMA Device Management before you calculate. Comparing your prediction with the result is the fastest way to find out whether you understand the idea or only the words.

Example 3 — an exam-style question

Typical questions about OMA Device Management ask you to (a) state it precisely, (b) apply it to given data, and (c) explain a limitation. Practise writing all three answers in under five minutes; the third part is what separates a full-mark answer from an average one.

Applications of OMA Device Management

In research: OMA Device Management appears in computer science research whenever the underlying quantities have to be modelled precisely. Papers usually cite it as a starting assumption and then explore where it breaks down.
In technology and industry: Engineering practice reuses OMA Device Management in design rules, simulations and safety margins. Knowing the idea lets you read a specification sheet and understand why the numbers look the way they do.
In the classroom: OMA Device Management is common in secondary-school and first-year university syllabi. It links to neighbouring topics Computer hardware standards, Networking standards, Open Mobile Alliance standards, so understanding it makes those chapters shorter.
In everyday life: Look for OMA Device Management outside the textbook — in sport, cooking, traffic, electronics or the sky above you. An example you found yourself is remembered far longer than one you were given.

Affiliate

Preply — study more efficiently by working with a personal tutor. 50% off.

How to study OMA Device Management in 20 minutes

Read the reference excerpt below once, without taking notes.
Close the page and write down what OMA Device Management means in your own words.
Compare your version with the excerpt and mark what you missed.
Work through the three examples above with pen and paper.
Explain OMA Device Management out loud to somebody else — or to Teacher Smith in the lgStudy chat.

Frequently asked questions

What is OMA Device Management in simple terms?

Why does OMA Device Management matter?

Because it connects several computer science ideas at once: it gives you a definition you can apply, a quantity you can calculate, and a way to check whether a result is plausible.

How should I study OMA Device Management?

Read the excerpt, restate it from memory, then work through the examples and applications listed on this page. The five-step study plan above takes about twenty minutes.

What does this page cover?

It gives you a compact reference excerpt plus original lgStudy explanations, examples, applications and study material on OMA Device Management.