Open Mobile Alliance
Abbreviation | OMA |
---|---|
Formation | June 2002 |
Merger of | IPSO Alliance;March 27, 2018 |
Type | NonprofitNGO |
Purpose | Internationaltechnical standards |
Headquarters | San Diego,California,United States |
Membership | Wireless vendors,information technologybusinesses, mobile operators, application & content providers |
Official language | English |
General Manager | Seth Newberry |
Staff | 143 |
Website | www |
OMA SpecWorks,previously theOpen Mobile Alliance(OMA), is astandards organizationwhich developsopen,internationaltechnical standardsfor themobile phoneindustry. It is anonprofitNon-governmental organization(NGO), not a formal government-sponsored standards organization as is theInternational Telecommunication Union(ITU): a forum for industrystakeholdersto agree on commonspecificationsfor products and services.
History
[edit]The OMA was created in June 2002 as an answer to the proliferation ofindustry forumseach dealing with a few application protocols: WAP Forum (focused on browsing and device provisioning protocols), theWireless Village(focused on instant messaging and presence),The SyncML Initiative(focused on data synchronization), the Location Interoperability Forum, the Mobile Games Interoperability Forum, and the Mobile Wireless Internet Forum. Each of these forums had its bylaws, its decision-taking procedures, its release schedules, and in some instances there was some overlap in the specifications, causing duplication of work.
Members include traditional wireless industry players such as equipment and mobile systems manufacturers (Ericsson,ZTE,Nokia,Qualcomm,Rohde & Schwarz) and mobile operators (AT&T,NTT Docomo,Orange,T-Mobile,Verizon), and also software vendors (Gemalto,Mavenirand others).[1]
In March, 2018, it merged with theIPSO Allianceto form OMA SpecWorks.[2]
Related standards bodies include: 3rd Generation Partnership Project (3GPP),3rd Generation Partnership Project 2(3GPP2),Internet Engineering Task Force(IETF) and theWorld Wide Web Consortium(W3C).
Its mission is to provideInteroperabilityof services across countries, operators and mobile terminals. The OMA only standardises applicative protocols; OMA specifications are intended to work with any cellular network technologies being used to provide networking and data transport. These networking technology are specified by outside parties. In particular, OMA specifications for a given function are the same with eitherGSM,UMTS,orCDMA2000networks. Adherence to the standards is entirely voluntary; the OMA does not have a mandative role.. OMA members that ownintellectual propertyrights (e.g.patents) on technologies that are essential to realizing a specification agree in advance to providelicensesto their technology on "fair,reasonable and non-discriminatory licensing"terms to other members. OMA is incorporated in California, United States.
Standard specifications
[edit]The OMA maintains many specifications, including:
- Browsing specifications, now namedBrowser and Content,formerly namedWAP browsing;in current version, these specifications rely essentially onXHTML Mobile Profile
- Multimedia Messaging Service(MMS) specifications
- OMA DRM specifications fordigital rights management
- OMA Instant Messaging and Presence Service(OMA IMPS) specification, which is a system for instant messaging on mobile phones; formerly namedWireless Village
- OMA SIMPLE IM instant messaging based onSession Initiation Protocol(SIP) SIMPLE
- OMA CAB Converged Address Book, a social address book service standard
- OMA CPM Converged IP Messaging, the underlying enabler forRich Communication Services
- OMA Lock and Wipe (LAWMO) specifications for those functions
- OMA Lightweight M2M (LwM2M)OMA LWM2Mspecifications for machine to machine functions
- OMA Client Provisioning(OMA CP) specification forprovisioning
- OMA Data Synchronization (OMA DS) specification fordata synchronizationusingSyncML
- OMA Device Management(OMA DM) specification formobile device managementusingSyncML
- OMA BCASTspecification for Mobile Broadcast Services
- OMARich Media Environment(RME) specification
- OMA OpenCMAPI Connection Management APIs[3]
- OMA PoC specification forPush to talkOver Cellular (PoC)
- OMA Presence SIMPLEspecification for presence based onSession Initiation Protocol(SIP) SIMPLE
- OMA Service Environment
- FUMOFirmware update
- Secure User Plane Location Protocol(SUPL),[4]an IP-based service forassisted GPSon handsets
- Mobile Location Protocol(MLP), an IP-based protocol for obtaining the position/location of mobile handset
- Wireless Application Protocol 1 (WAP1), 5-layer stack of protocols[5]
- OMA LOCSIP Location in SIP/IP Core[6]
- Software Component Management Object(SCOMO), allows a management authority to perform software management on a remote device
The OMA specifications inspired or formed the base for the following:
- NGSI-LDis an API and information model specified byETSIbased (with permission) on OMA specifications NGSI-09 and NGSI-10, extending them to provide bindings and to formally use property graphs, with node and relationship (edge) types that may play the role of labels in formerly-mentioned modelsandsupport semantic referencing by inheriting classes defined in sharedontologies.
See also
[edit]- Linux Phone Standards Forum(LiPS)
- LiMo Foundation
- Content Management Interface
- Open Handset Alliance
- Mobile Platform
- 3GPP
- European Telecommunications Standards Institute(ETSI)
- List of wireless router firmware projects
- Mobile Device Management
- List of Mobile Device Management Software
References
[edit]- ^"Current Members".Open Mobile Alliance.Retrieved2019-08-01.
- ^Jim Turley (March 28, 2018)."A Better Way to Define Industry Standards: OMA SpecWorks Creates IoT Standards, But Also Redefines the Game".RetrievedOctober 29,2021.
- ^SlidesArchived2016-03-04 at theWayback Machineslides
- ^"User Plane Location Protocol v3.0"(PDF).OMA.Retrieved7 October2017.
- ^dret.net GlossaryWAP1
- ^"LOCSIP V1.0 The Open Mobile Alliance".technical.openmobilealliance.org.Archived fromthe originalon 9 October 2016.Retrieved20 May2016.