This document is subject to copyright protection. The GSM MoU Association (“Association”)
makes no representation, warranty or undertaking (express or implied) with respect to and
does not accept any responsibility for, and hereby disclaims liability for the accuracy or
completeness or timeliness of the information contained in this document.
Tag Archives: PDF
OMTP Documents.1.0 – OMTP Customisation Enabler v1.0
Customisation of the terminal is one of the key drivers in OMTP. The main responsibility of a Customisation enabler is maintaining a set of properties that are related to look and feel customisation.
The adoption of a common data structure to transfer all the customisation information between operators and manufacturers is one of the key requirements driving OMTP’s work in customisation
OMTP Documents.1.0 – OMTP Local Connectivity Wired Analogue Audio v1.0
This was the first delivery in OMTP’s drive to deliver a better customer experience in phone connectivity – fewer cables and less confusion – as well as a direct cost saving on hardware elements within mobile devices.
Many customers do not use the analogue audio output facilities (commonly the headphone socket) because of cost and compatibility issues with headsets. In addition the fragmentation in connectors creates unnecessary cost in the whole value chain. This document defines some recommended classes for a physical analogue audio connector to streamline the value chain and offer the user a wider choice of the most popular peripherals, including their own legacy equipment.
OMTP Documents.1.0 – OMTP Legacy Customer Support For Instant Messaging and Presence Service v1.0
Instant Messaging (IM) on mobiles has become a popular and expected service in the operator proposition; these recommendations offer guidelines that make new services compatible with older, SMS only handsets.
They address an identified gap in current Instant Messaging and Presence (IM&P) OMA IMPS implementations, in order to allow a user of a client supporting full IM&P to be able to distinguish and appropriately message users of SMS-only handsets. Reaching industry agreement on standard client requirements for IM will help create a climate of success for IM without restricting the freedom of innovation. It will also streamline the whole value chain and provide end users with a larger choice of terminals that support the basic requirement.
OMTP Documents.1.0 – OMTP IMS Functional Requirements v1.0
IMS is an internationally recognised standard for evolving GSM mobile networks, designed to ease integration with the Internet and help deliver services across multiple access types (3G, WLAN, WCDMA etc.)
It offers great opportunities for rich multimedia and voice application delivery, yet traditionally has been driven from the network side, with inadequate consideration of the handset interface. OMTP’s recommendations in this area seek to defragment and standardise that interface, address the practicalities of deployment and define the end-to-end experience that is required to enable IMS to deliver on its potential.
OMTP Documents.1.0 – OMTP Management of VoIP Settings v1.0
This document defines the minimum requirements for the management of VoIP settings on terminals offering voice calling using embedded VoIP technologies over all types of network bearer.
It contains use cases and functional requirements to ensure a consistently applied management of VoIP settings on terminals. This will allow operators to source and distribute terminals that support voice calling using VoIP, where the operator’s VoIP settings are securely protected and/or locked to the operator’s VoIP settings for the duration of a subsidised service contract.
OMTP Documents.1.0 – OMTP Local Data Connectivity v1.0
This is a continuation of OMTP’s work on standardising the physical connectors on mobile devices.
OMTP has already tackled the issues of fragmentation in audio connectors in a move designed to reduce vendor costs and improve the customer experience. This second document addresses the issue in data connectors by recommending a single, universal cross manufacturer USB (Universal Serial Bus) cable connector that enables mobile consumers to connect and charge their mobile devices.
OMTP Documents.1.5 – OMTP Recommended Practices for Connected Applications v1.5
Connected applications (such as push email) have already proven that they are a compelling mobile service and the market for Connected Applications has plenty of scope to grow.
To enable the next tranche of Connected Applications, user experience barriers and infrastructure limitations need to be addressed. The task will produce a set of Recommended Practices that outline the expected behaviour of a Connected Application as seen from a terminal and network operator perspective.
OMTP Documents.1.0 – OMTP Positioning Enablers v1.0
Navigation and mapping promise to be compelling consumer services on mobile devices. At the core of making that functionality work lies a complex and interlinked series of positioning enablers.
OMTP’s recommendations will define platform and interface requirements to enable location based services for GSM/WCDMA family mobile terminals. It will addresses different positioning techniques (wireless network based, satellite based and hybrid), standard interfaces (such as the ones defined in OMA SUPL) and APIs to be accessed from the application level in the mobile.
OMTP Documents.1.0 – OMTP Advanced Device Management v1.0
As the capabilities of the mobile device increase – particularly when it comes to downloading new applications – there’s a greater chance that customer error may adversely affect performance of the device.
These recommendations will look at ways the operator can offer technical customer support and fix handset software problems remotely, so the customer doesn’t need to return their device to a shop or service centre.
OMTP Documents.1.0 – OMTP ADM Anti-virus Client Requirements v1.0
This document defines how the anti-virus client can be remotely managed by a mobile network operator’s device management authority. The device itself needs to allow such an anti-virus client to be remotely managed and hence it needs to fulfil a basic set of requirements for this type of remote application management. As an anti-virus client will use a Terminal’s remote management features and does not need to implement a complete remote application management solution, this document concentrates on the features that an anti-virus client needs to support.
OMTP Documents.2.0 – OMTP Data Transfer v2.0
OMTP Documents.1.5 – OMTP OMA DRMv2 Enabled Terminals v1.5
Digital Rights Management (DRM) is an enabling technology for the controlled distribution and consumption of valued media content within the mobile industry. To prevent illegal sharing of mobile content, content providers are increasingly asking for content protection as a prerequisite for content provisioning.
The OMA (Open Mobile Alliance) has specified a widely implemented standard for the protection of premium content. This OMTP project looks at implementation pragmatically, lists operator guidelines and recommends practises to help ensure the interoperability of legal content sharing. The objective of this document is to provide a guide for Operators who intend to specify terminal requirements in support of OMA DRM v2 and to help terminal and OS manufacturers to understand key requirements in support of OMA DRM v2.
OMTP Documents.2.0 – OMTP UICC(U)SIM v2.0
This project sets a standard for the interface between the SIM card and the mobile device to reduce cost and ease implementation for Operators and OEMs.
Different devices have different levels of support for the variety of features provided by the UICC. Operators are therefore presented with a limited subset of capabilities due to the fragmentation of device support. This document is concerned with the defragmentation and consolidation of requirements for the device to support UICC functionalities.
OMTP Documents.2.0 – IMS Functional Requirements v2.0
This document defines the minimum set of requirements for IMS (IP Multimedia System) functionalities on mobile Terminals and identifies which of these functionalities shall be available for developing new IMS capable applications in the Terminal. 3GPP IMS Release 7 and related service enablers are the scope of this document.
OMTP Documents.1.1 – OMTP Common Charging and Local Data Connectivity v1.1
Defines a common charging specification for energy efficient mobile phone chargers, a common charging interface to enable reuse of chargers across mobile phones and other devices as well as a common local data connectivity specification to improve data interoperability and peripheral re-use.
OMTP Documents.1.1 – OMTP Security Threats on Embedded Consumer Devices v1.1
Hacking embedded systems is one of the most technically challenging but financially rewarding forms of hacking around. Consumer Devices such as mobile handsets are targeted for a variety of reasons, from targeting the IMEI number of a mobile phone to re-enable it after theft through to data extraction and cryptographic key manipulation.
Attacking the hardware foundations of mobile phones can undermine the whole platform above including the Application Security Framework. To design future secure systems it is important to know exactly what the threats are to be able to defend against them. OMTP’s companion document to the ‘Advanced Trusted Environment: OMTP TR1’, the ‘Security Threats on Embedded Consumer Devices’ formed part of the input to the threat and risk analysis performed during the creation of TR1.
This maintenance release expands on the detail provided in the initial release of this recommendation in May 2008 and accompanies the maintenance release of the Advanced Trusted Environment: OMTP TR1.
OMTP Documents.1.1 – OMTP Advanced Trusted Environment OMTP TR1 v1.1
Establishing trust in a Terminal that is delivered to the mass market is a difficult but critical task for future mobile services. The embedded security of handsets is under constant attack from hackers and this will steadily increase.
The ‘Advanced Trusted Environment: OMTP TR1’ extends the work of the ‘Basic Trusted Environment: OMTP TR0’ by looking at what is necessary to secure future services which have high security needs, for example Broadcast and M-Commerce applications. The requirements provide the foundation for all the security on the device providing the pillars of support to the Operating System running on the device and protecting other security features such as an Application Security Framework. The requirements also further enhance security measures against re-enablement of blocked mobile phones following theft, through increased security of stored data such as the IMEI.
This maintenance release includes alignment of TR1 requirements with standards that have evolved since the first release in May 2008. This includes standards from: ETSI, 3GPP, OMA and TCG’s Mobile Trusted Module.
OMTP Documents.1.0 – OMTP Mobile Terminal Testing 1.0
Today the mobile industry faces a fragmented and sometimes absent approach to test automation. This effectively limits the number of terminals, services and applications that can be launched. It increases the amount of manual testing that needs to be done before terminals, services and applications are in service, with the cost and resource implications. The situation is not likely to change as the number of terminals, variations and the pace of development is constantly increasing.
Having a common set of APIs implemented across different execution environments- that enable automated testing but with controlled and secure access – would greatly reduce manual testing efforts for both manufacturers and operators.
The OMTP Mobile Terminal Testing project has delivered a set of functional Terminal requirements, interfaces and recommendations that are essential for mobile Terminal (Applications and Services) end-to-end test automation using a wired link.
OMTP Documents.1.2 – OMTP Trusted Environment OMTP TR0 v1.2
OMTP’s Trusted Environment recommendations help provide protection and to mitigate risk to customers and network – allowing for example, for device ID protection and secure updates.
They define handset security recommendations to facilitate the development and deployment of secure services. By formalising the security needs of sensitive assets and enablers, the Trusted Environment task seeks to influence standardisation of hardware enablers, with the aim of facilitating the implementation of open platforms.
This document is the first release of an evolving area that will in time encompass further security measures like hardware security support for mobile payments.
This maintenance release reflects evolution in hardware security and provides the base of requirements for the Advanced Trusted Environment: OMTP TR1.
OMTP Documents.1.2 – OMTP VVM Specification 1.2
The document provides a technical Recommendation for an open and standardised Visual Voice Mail (VVM) interface protocol which VVM clients may use to interact with a voicemail server.
It is an update of the previous version 1.1 which may be found in the publications archive (click here)
OMTP Documents.1.0 – OMTP Local Bluetooth Connectivity v1.1
This document defines a minimum common suite of Bluetooth hardware and profile requirements for two classes of Bluetooth enabled mobile Terminal – Basic and Advanced.
The document’s main purpose is to improve customer user experience and expected functionality when using Bluetooth from a mobile Terminal.
The document references existing and approved industry Bluetooth standards as defined by the Bluetooth Special Interest Group (BT SIG) together with their revised qualification process for cross vendor interoperability testing.
The Total Cost of Ownership for Embedded Mobile Devices (0.78 MB)
This report examines the total cost of ownership of Embedded Mobile (EM) and machine-to-machine (M2M) devices with the aim of highlighting how near term technology design decisions may create legacy device management issues for the mobile industry. The study is broad ranging and provides insight for today’s decision makers in the EM ecosystem: the mobile network operators (MNOs), solution providers, manufacturers and end users, who will lead this new mobile market into the future.
TCO Report (801KB)
This report examines the total cost of ownership of Embedded Mobile (EM) and machine-to-machine (M2M) devices with the aim of highlighting how near term technology design decisions may create legacy device management issues for the mobile industry. The study is broad ranging and provides insight for today’s decision makers in the EM ecosystem: the mobile network operators (MNOs), solution providers, manufacturers and end users, who will lead this new mobile market into the future.
mHealth: A new vision for healthcare (0.39 MB)
The paper outlines the ever growing burden of unsustainably rising healthcare costs across the world; as healthcare expenditure is forecasted to reach some $6 trillion by 2011, it will outpace most countries’ GDP growth.
Mobile Technologies Promise for Healthcare (1.05 MB)
The CSMG-GSMA white paper examines the main drivers of mobile health services and assesses the size of the mHealth market opportunity in Europe.
The M2M World of Connected Services (0.72 MB)
This map of the “Internet of Things” from Beecham Research represents M2M service sectors, application groups, locations and devices.
Realising the Embedded Mobile Opportunity Together (0.25 MB)
The aim of the study was to assess the market opportunity and the main barriers to the development of the embedded mobile market.
Embedded Mobile – M2M Solutions and Beyond (0.71 MB)
This brief report summarises the key findings from a study conducted on behalf of members of the GSMA’s Board and Strategy Committee to explore the landscape, opportunities and challenges associated with new devices and services.
1.0 – Network Efficiency Task Force Fast Dormancy Best Practices
The introduction and mass adoption of smart-phones by customers has led to a change in the way devices interact with networks.
IN.08.4.1 – SMS Hubbing Handbook
This document has been developed as an handbook to help Operators and their chosen SMS hubbing/transit Service Provider (SMSIP) to implement SMS Hubbing Services.
Guidelines for end to end GRX Service Level Agreement between Mobile Operation and Carriers
This document is intended to provide Mobile Operators and GRX Providers with the minimum requirements to be included in the implementation of bilateral Service Level Agreements (“SLA”) related to the GRX Service agreed by between Mobile Operators and GRX.
AA.71.5.0 – Agreement for International SMS Hubbing Services
The SMSIP operates the SMS Hubbing Service (the Service) as defined in Annex 1 hereto (Definitions) which enables the international transit of SMS sent between telecommunications networks.
IR.90.2.0 – RCS Interworking Guidelines
This document illustrates the inter-operator aspects of RCS (Rich Communication Suite). Aim is to minimize any interoperability issues when deploying RCS service between operators by making sure guidelines for deployment options are documented.
IN.18.2.0 – Guidelines for Service Level Agreement Between Mobile Operators and Carriers for TDM Voice
It is recommended that Mobile Operators put in place a Service Level Agreement (SLA) with International Carriers to ensure the quality of TDM Voice. IN.01 provides a template SLA for ease of implementing such an agreement. This document provides guidelines on how to use the IN.01 template agreement and other items for consideration when setting up the SLA.
IN.12.2.0 – Number Resolution and ENUM White Paper
The purpose of this White Paper is to define the requirements for number resolution in a multi-service, multi-technology interconnect environment and describe how ENUM (E.164 Number Mapping) technology can be used to fulfil these requirements.
AA.83.1.1 – IP Packet eXchange (IPX) Service Schedule for MMS IW
The document consists of twelve sections and three annexes containing information about the IP Packet eXchange (IPX) Service Schedule for MMS IW
AA.82.1.1 – SMS Service Schedule to AA.80
For the purpose of this Agreement the following terms shall have the meanings set forth in their respective definitions, unless a different meaning is called for in the context of another provision in the Agreement:
AA.81.2.0 – Packet Voice Interconnection Service Schedule to AA.80
AA.80.4.0 – IP Packet eXchange Service Agreement
Any Service Provider acting as a gateway between the IPX Domain and the non-IPX Do-main (i.e. enabling other parties not directly connected to the IPX Domain.
AA.64.2.2 – MMS Schedule to AA.60
This Schedule applies to the traffic scenarios agreed on between the Parties in this Schedule
AA.63.2.2 – SMS Schedule to AA.60
This Schedule defines the commercial terms and conditions of relevant Scenarios for SMS Interworking Service.
IR.67.5.1 – DNS/ENUM Guidelines for Service Providers & GRX/IPX Providers
This document is intended to provide guidelines and technical information for those who need to set up and/or maintain DNS servers for inter Service Provider services. This document is not intended to provide a general education on DNS or ENUM. Thus, a reasonable level of technical competence in DNS, ENUM and DNS/ENUM server configuration is assumed through out this document.
The Impact of Taxation on the Development of the Mobile Broadband Sector
The purpose of this study is to assess the impact of taxation on the development of the mobile broadband sector in emerging countries.
The 2.6GHz Spectrum Band – An Opportunity for Global Mobile Broadband
Data traffic on mobile broadband networks is growing exponentially as both consumers and business users turn to smartphones, connected laptops, tablet computers and other devices to access the Internet, email, business applications and social networking services.
IR.87.1.0: SIP-I Interworking Test Cases
This document should be read by organisations interested in executing SIP-I Interworking Tests.
The Impact of Taxation on the Development of the Mobile Broadband Sector – Spanish Version
The Impact of Taxation on the Development of the Mobile Broadband Sector – Spanish Version (ESPANOL)
IR.90.1.0: RCS Interworking Guidelines
This document illustrates the inter-operator aspects of RCS (Rich Communication Suite). Aim is to minimize any interoperability issues when deploying RCS service between operators by making sure guidelines for deployment options are documented.
IN.12.2.1 – Number Resolution and ENUM White Paper
The purpose of this White Paper is to define the requirements for number resolution in a multi-service, multi-technology interconnect environment and describe how ENUM (E.164 Number Mapping) technology can be used to fulfil these requirements.
IN.08.4.2 – SMS Hubbing Handbook
This document has been developed as a handbook to help Operators and their chosen SMS hubbing/transit Service Provider (SMSIP) to implement SMS Hubbing Services. The document supports the AA.71 Agreement for International SMS Hubbing Services and its SLA.
IN.05.3.1 – Service Level Agreement for Signalling
This document intends to define the minimum requirements to be included in an International SCCP Signalling Service Level Agreement, understanding that this Service rendered by the Carrier has the aim to convey and terminate Mobile Operator’s International SCCP Signalling traffic.
IN.01.3.2 – Template for International Transit TDM Voice Service Level Agreement Between Mobile Operators and Carriers
This document is intended to provide mobile operators with the minimum requirements to include in a Service Level Agreement (SLA) for TDM Interconnection between a Mobile Operator and International Carrier for International Transit Voice where this is related to directly connected switch interconnect.
TS.16.1.1 – TAC Allocation Process for India
The Indian Telecommunications industry is one of the fastest growing in the world. India is the second largest telecom provider worldwide. The impressive growth seen to date, and future potential, has attracted a lot business interest from within India and internationally.
AA.61.3.1 – Voice Messaging Service Schedule to AA.60
This Service Schedule is intended for Video and/or Image share. Parties should delete text as required for the purpose of the agreement.
IR.79.1.3 – Image Share Interoperability Specification
This document describes the terminal interoperable Image (Live & Pre-stored) Share service. The terminal interoperable Image Share service allows users to share Images between them over PS connection with ongoing CS call, thus enhancing and enriching end-users voice communication.
IR.74.1.4 – Video Share Interoperability Specification
This document specifies the terminal interoperable Real-Time Live Video Share service. The intended audience of this document is terminal or software vendors who wish to implement an inter-operable Video Share service.
AA.71.6.0 – AA.71 Agreement for International SMS Hubbing Services
The SMSIP operates the SMS Hubbing Service (the Service) as defined in Annex 1 hereto (Definitions) which enables the international transit of SMS sent between telecommunications networks.
AA.68.1.1 – Social Presence Schedule to AA.60
In respect of Social Presence Information received by the MNO B Social Presence Server from the MNO A Social Presence Server for delivery by MNO B, the launch of the MNO B Social Presence Interworking Service
