A preliminary study on mobile device Management--oma DM Protocol Wizard

Along with the rapid development of 3G technology in China, the data business is bound to become an important means of communication between consumers and enterprise users, and these trends pose significant management challenges to mobile operators (while extending mobile data services to different mobile devices of different network types are also challenging). Mobile Device Management (Device Management) is a response to this management challenge and ensures that all mobile devices connected to the carrier network can provide high-quality mobile data services. Mobile device Management provides support for mobile devices such as 2G, 3G, WiMAX, and so on. OMA based on OTA (over-the-air) Device Management Framework provides a solution for mobile device management, the OMA-DM protocol is clearly independent of the hosting network, so this protocol can be used for a variety of networks, including mobile cellular network, Bluetooth, Ethernet, Wi-Fi, WiMAX, etc. It spans 2G, 3G, and WiMAX technology.

A preliminary study on mobile device Management--oma DM Protocol Wizard





Want to be your friend
Msn:itecies@hotmail.com
Skype ID:javen.china

Download: Mobile device Management and OMA DM protocol V5

Unlike the TR069 protocol, OMA is designed to support data synchronization between different networks of different devices, so OMA's data transmission is not only built on the Internet session layer using HTTP transmission, OMA also supports wireless network WAP using WSP and Bluetooth network using OBEs for data transmission, and so on. Different networks are only different transmission tools, but because of the common use of the standard SYNCML packets, the data synchronization between different networks, so that the use of an intermediary interoperability tool to achieve different networks and devices between the data interaction.

The original design of TR069
With VoIP, IPTV and more and more IP terminal equipment popularization (especially in the family), a large number of equipment configuration and maintenance becomes more and more difficult, greatly improve the cost of network product operators, the traditional SNMP based network management system in the face of a large number of terminal equipment is powerless, Limits the development speed and scale of the broadband access market. TR069 defines a new set of network management architectures, including "Administrative Model", "Interaction Interface", "Management parameters", which greatly reduces the cost of the transportation of networked products.
OMA Protocol Wizard

One, why the OMA protocol is required
With the rapid development of global mobile communication, in order to improve the quality of mobile communication service, meet the needs of people, and solve the problem of data synchronization between different networks, and then realize interconnection, the urgent task is to establish a universal and safe and reliable Unified standards and specifications for easy to operate End-to-end mobile communications. The Global Standardization organization OMA (Open Mobile Alliance) Open Mobility Alliance was founded on June 12, 2002. It is a demand-oriented approach.

About data synchronization, some places directly say OMA to solve the interconnection problem of different networks, you can never let a Chinese people and the foreigners on the other side of the direct dialogue, the only thing we can do is to do the words above, and then through a translation process and a communication tool to communicate. OMA will never become a mobile phone, but it is not just a word-control, it wants the world to use the same language.

Ii. establishment of the OMA organization
OMA was originally merged by the two standardization organizations of the WAP Forum (WAP FORUM) and open Mobile architecture (open mobility architecture). Subsequently, the Regional Interoperability Forum (LIF), the Syncml,mms Interoperability Research Group (MMS-IOP) and the Wireless Association (WIRELESS Village), which are committed to advancing the work of mobile business norms, have joined OMA.

Iii. What is the OMA organization doing?
Seeking a system-independent, open, and enabling applications and services to achieve data synchronization on various terminals worldwide.

Iv. what is the OMA DM agreement
OMA DM (Device Manage) is a branch of OMA that is defined by the OMA organization as a set of management protocols dedicated to mobile and wireless networks.

V. OMA DM Protocol What to do (OMA DM (Device Management))
1. Set initialization configuration information for the device
2. Installation and updating of equipment information
3. Obtain relevant management information from the equipment
4. Processing equipment generated events and alarm information

Vi. OMA DM How to manage equipment
Contains two steps:
1.BOOTSTRAP, the boot process, literally means bringing the device from an inaccessible island into a network that can be managed by the OMA protocol
2.PROVISIONING and MANAGEMENT, device initialization and other management

Vii. BOOTSTRAP (What is the boot process of the equipment)
To enable a device to connect to a remote Management Server

Eight, what bootstrap do
Set up some configuration information for the device to connect with the network and the Management Server

Nine, the main mode of equipment to do bootstrap
1.CUSTOMIZED BOOTSTRAP (FACTORY provisioning), the equipment before the factory by the manufacturer to do BOOTSTRAP, equipment at the factory has included the network and Management Server information
2.BOOTSTRAP from Smartcard (CLIENT provisioning), the device is BOOTSTRAP by inserting a memory card
3.SERVER initiated BOOTSTRAP, BOOTSTRAP via server remote notification device, provided the server already knows the device address (URL or phone number)

Ten, OMA DM's equipment management mode
OMA DM by configuring, diagnosing, and so on the device by setting the relevant parameters, these parameters are organized together through a tree structure called the Device Management tree (DEVICE MANAGEMENT)

Xi. data transmission of the OMA protocol
The OMA protocol uses SYNCML message packets to deliver data to interact (also known as synchronization) between different networks, similar to TR069 using SOAP packets and RPC functions, the data type of the message uses the data type defined by SYNCML, and the SYNCML message uses two types of MIME media primarily.
Unlike the TR069 protocol, OMA is designed to support data synchronization between different networks of different devices, so OMA's data transmission is not only built on the Internet session layer using HTTP transmission, OMA also supports wireless network WAP using WSP and Bluetooth network using OBEs for data transmission, and so on. Different networks are only different transmission tools, but because of the common use of the standard SYNCML packet, the data synchronization between different networks, so that the use of an intermediary interoperability tool to achieve different network data interaction between different devices.

Protocol stack:
----------------------------
SYNCML
----------------------------
http| wsp| Obex...
----------------------------
ssl| WTLS ...
----------------------------
Internet| wap| Bluetoos ...
----------------------------

12, what is SYNCML
SyncML is written by synchronous MARKUP LANGUAGE (Synchronous Markup Language), which is made by IBM, LOTUS, MOTOROLA, NOKIA, PALM INC, PSION, Stafish Software and other businesses launched the establishment of the SYNCML forum launched. The main objective is to address two issues:
1. Synchronizing network data with any kind of mobile device
2. Synchronizing mobile devices with any one of the network data

The SYNML message contains two parts: message headers <SYNCHDR> and message body <SYNCBODY>

The message headers are formatted as follows:
< SYNCHDR >
< VERDTD > 1. 2 </VERDTD >
< Verproto > SYNCML/1. 2 </Verproto >
< SESSIONID > 104050403 </SESSIONID >
< MSGID > 5 </MSGID >
< target > Target DATABASE URI </TAR get >
< source > Source DATABASE URI </source >
< cred > ... </cred >
</SYNCHDR >

< VERDTD >: SYNCML version statement
< SESSIONID >: Session ID
< MSGID >: Message ID
< SOURCE > and < TARGET > for addressing, server using URIs, while clients using International mobile device identifier IMEI
< cred: Authentication information

The message is in the following physical style:
< Syncbody >
< status > ... </status >
< RESULTS > ... </RESULTS >
< ALERT > ... </alert>
</syncbody >

< status: Indicates the completion status of an operation
< RESULTS: Returns data results if command execution succeeds
< alert: Sender notification receiver

13, OMA DM data interaction Process
Contains two phases:
1. Preparatory phase (SETUP PHASE)
2. Management phase (Management phase)

14. Preparation stage (SETUP PHASE)
Main transmission authentication and equipment information

CLIENT SERVER
| PACKAGE 0 |
|< ——————————————— > |
| PACKAGE 1 |
| ————————————————— >|
| PACKAGE 2 |
|< ————————————————— |
| |

1.PACKAGE 0 (MANAGEMENT initiation ALERT from SERVER to CLIENT)
Similar to TR069 's notify, many wireless devices, for security reasons, do not continuously listen to the Management Server messages, so you can let the server notify the device to establish a connection with the server, or through the user interface on the device, the user to operate the device and the server to establish a connection, Some device problems can also cause the device to connect to the server.
Before this, of course, the device has completed the bootstrap operation.

2.PACKAGE 1 (initialization from CLIENT to SERVER)
The device sends its device information and authentication information in package 1 to facilitate the server to identify the device and notify the server to start the management session

Package 2 (initialization from server to client)
The server initiates the session and sends management messages to the device, and if only the <Final> command is included in Package 2, the server may send the session Abort Alert (1223) command to force it to terminate it the next time.

XV, Management stage (Management phase)
Management phase for a large number of interactive processes

Client Server

| Package 3 |
| ————————————————— >|
| Package 4 |
|< ————————————————— |
| |

Package 3 (Client response sent to server)
Reply to the commands command execution results in package 2.

Package 4 (Further server management operations)
To end a conversation or to continue sending a command, if the <Final> command is included in Package 4, the server may next send session Abort Alert (1223) to force it to terminate.

16. The current research hotspot of OMA protocol--one-pass (PPT)
One-pass (PTT) means to say. Its design is inspired by the trunking communication technology of the walkie-talkie, which is essentially a VoIP technology based on 2.5G and 3G network. One-pass converts the speech signal into a packet through the network, and finally converts the packet into a voice signal to transmit it to complete a call, That is to achieve voice communication in the form of digital exchange. Like a walkie-talkie, one-pass works in half duplex mode, and only one person at a time can speak. As early as 2003, Nokia, Motorola, Siemens and Ericsson 4 have jointly developed a PTT open standard and submitted to OMA (Open Mobile Alliance).

17. The problems that OMA faces
1, compared to the network standardization, the apparent lag in the standardization of the business area contrasts with the high standardization of telecommunications networks and technology, where standardization in the business field begins in a number of small, decentralized, fragmented organizations, and many of them are standards of some companies themselves, although OMA attempts to integrate fragmented organizations Unified standards to speed up progress, but as OMA started, many companies have launched their own programs, coupled with the complexity and diversity of participating companies, are expected to play a leading role, so the standardization of the difficult, the progress is also very unsatisfactory. For example: With PC operating system Microsoft accounted for more than 90% of the fact that the standard is different, There are many kinds of operating systems for mobile phones, including mobile and Palm OS, and new operating systems are constantly appearing. OMA's goal is that business standards are independent of the operating system, but have not yet been able to do so, the existence of a variety of operating systems, making business implementation and interoperability worse.
2, business differentiation, personalized and unified standards of conflict in the business standardization of slow progress at the same time, business standards are also facing another contradiction is the difference between the business operators and standards of unity of the contradictions. Some big operators think they want to be the first to offer a different business from other operators, Want to lead the business and mobile phone development, that there should be no need for a high degree of unification, coupled with the current standards have not been very perfect and unified, operators need to carry out business, so there has been an operating enterprise or some operators to jointly develop their own business and business combination standards, Mobile phone manufacturers to order the phenomenon of mobile phones. These issues can be seen in the development of the PTT standard currently being fired, which is divided into two camps: Motorola, Ericsson, Siemens and Sony Ericsson released its POC system Push-to-talk over cellular in 2003 ( Standard PoC1.0 of POC) and on the same day, Nokia also released the POC technology, but the technology is not compatible with the technology of the four manufacturers.

Generic Alert Message
<Alert>
<CmdID>2</CmdID>
<Data>1226</Data> <!--Generic Alert-->
<Correlator>abc123</Correlator>
<Item>
<Source><LocURI>./SyncML/Sample</LocURI></Source>
<Meta>
<type xmlns= "Syncml:metinf" >
Reversed-domain-name:org.domain.samplealert
</Type>
<format xmlns= "Syncml:metinf" >xml</Format>
<mark xmlns= "Syncml:metinf" >critical</Mark> <!--Optional-->
</Meta>
<Data>
<!--Client Alert Data Goes here-->
</Data>
</Item>
</Alert>