OMA Protocol Wizard-A concise tutorial to help you understand the OMA Protocol (i) & (b)

OMA Protocol Wizard
A concise tutorial to help you understand the OMA Protocol (i) & (b)

Unlike the TR069 protocol, because OMA is designed to support data synchronization between different devices across networks, OMA's data transfer 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, etc. The transmission tools are different between different networks, but because of the common use of the standard SYNCML packets, the data synchronization between different networks is realized, and then an intermediary interoperability tool is used to realize the data interaction between different networks and devices.

TR069 's original design
With the popularization of VoIP, IPTV and other IP terminal equipment (especially in the family), a large number of equipment configuration and maintenance becomes more and more difficult, greatly improving the cost of network product operators, the traditional SNMP-based network management system faced with a large number of terminal equipment appears to be inadequate, Limits the speed and scale of the broadband access market. TR069 defines a new set of network management architecture, including "Administrative Model", "interface", "Management parameters", to a large extent, reduce the cost of transportation of networking products.
OMA Protocol Wizard

I. Why the OMA protocol is required
With the rapid development of global mobile communications, in order to improve the quality of mobile communications services to meet people's needs, while addressing the data synchronization between different networks, and then realize interconnection, the urgent task is to establish a global and safe and reliable, A unified standard and specification for easy-to-operate end-to-end mobile communications. The Global Standardization organization OMA (Open Mobile Alliance) Open Mobility Alliance was established on June 12, 2002. It was created for this demand.

With regard to data synchronization, there are places where OMA has to address the interconnection of different networks, and you can never have a Chinese person talk directly to a foreigner on the other side of the ocean, and the only thing we do is to do as much as possible in the vocabulary, and then communicate through a translation process and a communication tool. OMA will never be a cell phone, but it's not just a word-control, it wants the world to use the same language.

Ii. establishment of the OMA organization
OMA was originally formed by a combination of two standardization organizations (WAP Forum) and open Mobility Architecture (open mobile ARCHITECTURE). Subsequently, the Regional Interoperability Forum (LIF), the Syncml,mms Interoperability Research Group (MMS-IOP) and the Wireless Association (WIRELESS VILLAGE), the organizations that are committed to advancing mobile business practices, have joined OMA in succession.

Iii. What the OMA organization does
Seek a system-neutral, open, standard that enables applications and businesses to synchronize data across a wide range of terminals worldwide.

Iv. what is the OMA DM protocol?
OMA DM (Device Manage) is a branch of OMA that is defined by the OMA organization as a set of management protocols specifically for mobile and wireless networks.

V. OMA DM Protocol What to do (OMA DM (Device Management))
1. Set initialization configuration information for the device
2. Install and update equipment information
3. Obtain relevant management information from the device
4. Handling event and alarm information generated by the device

Vi. how OMA DM manages equipment
Consists of two steps:
1.BOOTSTRAP, the boot process, literally means bringing equipment from an isolated island into a network that can be managed by OMA protocol
2.PROVISIONING and MANAGEMENT, device initialization and other management

Vii. What is the BOOTSTRAP (device boot process)
Enables a device to establish a connection to a remote Management Server

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

Nine, the main way of equipment to do bootstrap
1.CUSTOMIZED BOOTSTRAP (FACTORY PROVISIONING), the device is manufactured by the manufacturer to BOOTSTRAP the equipment, the 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 Equipment Management method
OMA DM configures and diagnoses devices by setting relevant parameters to the device, which are organized together by a tree structure called the device MANAGEMENT tree.

Xi. data transfer for OMA protocol
The OMA protocol uses the SYNCML message packet to pass data across different networks (also known as synchronization), 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 mainly uses two types of MIME media.
Unlike the TR069 protocol, because OMA is designed to support data synchronization between different devices across networks, OMA's data transfer 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, etc. The transmission tools are different between different networks, but because of the common use of the standard SYNCML packets, the data synchronization between different networks is realized, and then an intermediary interoperability tool is used to realize the data interaction between different networks of different devices.

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

12. What is SyncML
SyncML is synchronous MARKUP LANGUAGE (Synchronous Markup Language) written by IBM, LOTUS, MOTOROLA, NOKIA, PALM INC, PSION, Stafish Software and other merchants initiated the establishment of the SYNCML Forum initiated. The main objective is to solve two problems:
1. Synchronizing network data with any kind of mobile device
2. Synchronizing mobile devices with any kind of network data

The SYNML message consists of two parts: message header <SYNCHDR> message body <SYNCBODY>

The message header format is 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 > used for addressing, the server uses URIs, while clients use international mobile device identification code IMEI
< CRED;: Authentication information

Message formatting is as follows:
< Syncbody >
< status > </Status >
< RESULTS > ... </RESULTS >
< ALERT > ... </alert>
</syncbody >

< status;: Indicates the completion status of an operation
< RESULTS: If the command executes successfully, the data result is returned
< alert: Sender notifies recipient

13. The data interaction process of OMA DM
Consists of two stages:
1. Preparation phase (SETUP PHASE)
2. Management phase (Management phase)

14. Preparation phase (SETUP PHASE)
Primary transmission of authentication and equipment information

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

1.PACKAGE 0 (MANAGEMENT initiation ALERT from SERVER to CLIENT)
Similar to the TR069 notify, many wireless devices for security and other considerations do not continuously monitor the Management Server messages, so you can let the server notify the device to establish a connection to the server, or through the user interface on the device, the user operating device and the server to establish a connection, Some device problems can also cause the device to establish a connection 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 a management message to the device, and if only the <Final> command is included in Package 2, the next time the server may send the session Abort Alert (1223) command to force termination.

XV, Management phase (Management phase)
The management phase is a large number of interactive processes

Client Server

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

Package 3 (Client response sent to server)
Replies 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 only the <Final> command is included in Package 4, the next time the server may send a session Abort Alert (1223) command to force the termination of the session.

16. The current research hotspot of OMA protocol-one-touch (PPT)
One-touch (PTT) means that it is said to be. Its design is inspired by the trunking communication technology of walkie-talkie, which is essentially a VoIP technology based on 2.5G and 3G network. One-touch communication converts the voice signal into a packet over the network, and then converts the packet into a voice signal to complete a call, That is, the realization of voice communication in the form of digital exchange. Like a walkie-talkie, one-touch work is done in half-duplex, and only one person can speak at a time. 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. Problems faced by OMA
1, in contrast to the network standardization, the business area of the standardization of the degree of lag with the telecommunications network and technology is highly standardized in a sharp comparison, in the Business field of standardization began in a lot of small, decentralized, unstructured organizations, there are many of the company's own standards, although OMA tried to integrate scattered organizations, Unified standards to speed up progress, but since OMA started, many companies have launched their own solutions, coupled with the involvement of the company's complex and diverse, are expected to play a leading role, so standardization is very difficult, progress is not ideal. For example: With PC operating system Microsoft accounted for more than 90%, the formation of the fact that the standard is different, There are many different operating systems for mobile phones, including mobile and Palm OS, and there are still new operating systems in place. OMA's goal is that the business standard is independent of the operating system, but it is not yet available, and the presence of multiple operating systems makes business implementation and interoperability worse.
2, business differentiation, personalized and unified standards of conflict in the business standardization of the slow progress, business standards also face another contradiction is the difference between the different operators and standards of unity of the contradiction. Some big operators think they should take the lead in providing different business to other operators, Want to lead the development of business and mobile phones, it should not be necessary and no need for a high degree of unity, coupled with the current standards are not so perfect very unified, operators need to carry out business, so there is an operating enterprise or some operators to jointly develop their business and business portfolio standards, To phone manufacturers to customize the phenomenon of mobile phones. These questions can be seen from the development of the PTT standard currently being scrambled to see that OMA is divided into two camps: Motorola, Ericsson, Siemens and Sony Ericsson released their POC systems in 2003 Push-to-talk over Cellular ( POC) standard PoC1.0 and on the same day, Nokia also released POC technology, but the technology is not compatible with the technology of the four manufacturers mentioned above.

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>