Open Mobile Terminal Platform

The Open Mobile Terminal Platform (OMTP) was a forum created by mobile network operators to discuss standards with manufacturers of mobile phones and other mobile devices. During its lifetime, the OMTP included manufacturers such as Huawei, LG Electronics, Motorola, Nokia, Samsung and Sony Ericsson.[1]

Open Mobile Terminal Platform
Industry Forum
IndustryWireless Services
Founded2004
Products"Industry recommendations", "BONDI initiative"
Websitehttp://www.omtp.org
http://bondi.omtp.org

Membership

OMTP was originally set up by leading mobile operators. At the time it transitioned into the Wholesale Applications Community at the end of June 2010, there were nine full members: AT&T, Deutsche Telekom AG, KT, Orange, Smart Communications, Telecom Italia, Telefónica, Telenor and Vodafone. OMTP also had the support of two sponsors, Ericsson and Nokia.

Activities

OMTP recommendations have hugely helped to standardise mobile operator terminal requirements, and its work has gone towards helping to defragment and deoptionalise operators' recommendations. OMTP's focus was on gathering and driving mobile terminal requirements, and publishing their findings in their Recommendations. OMTP was technology neutral, with its recommendations intended for deployment across the range of technology platforms, operating systems (OS) and middleware layers.

OMTP is perhaps best known for its work in the field of mobile security, but its work encompassed the full range of mobile device capabilities. OMTP published recommendations in 2007 and early 2008 on areas such as Positioning Enablers, Advanced Device Management, IMS and Mobile VoIP. Later, the Advanced Trusted Environment: OMTP TR1 and its supporting document, 'Security Threats on Embedded Consumer Devices'[2] were released, with the endorsement of the UK Home Secretary, Jacqui Smith.[3]

OMTP also published requirements document addressing support for advanced SIM cards. This document defines also advanced profiles for Smart Card Web Server, High Speed Protocol, Mobile TV and Contactless.[4]

OMTP has also made significant progress in getting support for the use of micro-USB as a standard connector for data and power.[5] A full list of their recommendations can be found at GSMA.com.[6]

BONDI

In 2008, OMTP launched a new initiative called BONDI (named after the Australian beach); the initiative defined new interfaces (JavaScript APIs) and a security framework (based on XACML policy description) to enable the access to mobile phone functionalities (Application Invocation, Application Settings, Camera, Communications Log, Gallery, Location, Messaging, Persistent Data, Personal Information, Phone Status, User Interaction) from browser and widget engine in a secure way. The BONDI initiative also had an open source Reference Implementation at https://web.archive.org/web/20130509121758/https://web.archive.org/web/20130509121758/http://bondi.omtp.org//. An Approved Release 1.0 of BONDI was issued in June 2009. An open source project for a comprehensive BONDI SDK was started at https://web.archive.org/web/20130528132818/http://bondisdk.org/.

Universal Charging System

In February 2009, OMTP expanded its Local Connectivity specification (based on micro-USB) to describe requirements for a common charger and common connector to enable sharing the same battery charger through different phones. The OMTP Common Charging and Local Data Connectivity[7] was adopted by GSM Association in the Universal Charging System (UCS) initiative. This has been further endorsed by the CTIA[8] and the ITU.[9] In June, 2009 the European Commission reached an agreement with several major mobile phone providers on requirements for a common External Power Supply (EPS) to be compatible with new data-enabled phones sold in the European Union. The EPS shares most of the key attributes of the UCS charger.[10][11]

Wholesale Applications Community

In June 2010, the OMTP transitioned itself into the new Wholesale Applications Community. All OMTP activities ceased at that time and were either taken over within the WAC organisation or other standards or industry associations.[12] In turn, in July 2012 WAC itself was closed, with the OMTP standards being transferred to GSMA, and other assets and personnel transferring to Apigee.[13]

gollark: Broken components? Isn't that talking about it being possible to enable extra cores?
gollark: Anyway, I don't know what this has to do with their current products.
gollark: Oh right, ye olden Phenom things.
gollark: I have no idea what you're talking about.
gollark: You mean the fact that their chiplet thing lets them use dies which aren't fully working?

See also

References
  1. "Pros seem to outdo cons in new phone charger standard". news.com. September 20, 2007. Retrieved November 26, 2007.
  2. OMTP Security Threats on Embedded Consumer Devices at gsma.com
  3. "Crime fighters welcome mobile security requirements". telecoms.com. May 22, 2008. Retrieved September 16, 2009.
  4. OMTP UICC v2.0 at gsma.com
  5. OMTP Local Data Connectivity at gsma.com
  6. "OMTP Documents.1.0 - OMTP ADM Anti-virus Client Requirements v1.0". Newsroom. Retrieved 3 January 2020.
  7. OMTP Common Charging and Local Data Connectivity
  8. CTIA–The Wireless Association Announces One Universal Charger Solution to Celebrate Earth Day Archived 2010-12-14 at the Wayback Machine
  9. pressinfo. "Press Release: Universal phone charger standard approved - One-size-fits-all solution will dramatically cut waste and GHG emissions". itu.int. Retrieved 21 May 2015.
  10. "Harmonisation of chargers for mobile telephones". ec.europa.eu. Archived from the original on 2009-10-23.
  11. "Annex II, Technical Annex to MoU regarding the Harmonisation of a Charging Capability for Mobile Phones" (PDF). 2010-01-12. Archived from the original (PDF) on 2010-11-28. Retrieved 2011-02-26.
  12. Keith Dyer. "OMTP announces final documents prior to transition into Wholesale Application Community". mobileeurope.co.uk. Retrieved 21 May 2015.
  13. Sarah Perez. "WAC Whacked: Telecom-Backed Alliance Merges Into GSMA, Assets Acquired By API Management Service Apigee". TechCrunch. AOL. Retrieved 21 May 2015.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.