Difference between revisions of "Mpp Api"

From eLinux.org
Jump to: navigation, search
m (Draft Specifications)
m (Add category)
Line 63: Line 63:
The [[Media:ReferenceArchitecture.pdf| Reference Architecture]].
The [[Media:ReferenceArchitecture.pdf| Reference Architecture]].
[[Category:Mobile Phone Profile Working Group]]

Latest revision as of 23:20, 27 October 2011


The Mobile Phone Profile Working Group is developing an API for phone functionality. The goal is to allow applications consistent access to a wide range of standard functionality, to improve portability of applications across handsets. Having a standard API would make it easier to develop software that would run in more than one mobile phone environment. This would allow feature developers to spend more time on functionality development and less on porting from one phone to another.

The initial target for the API is a multimedia-centric phone, implemented either as a dual-processor or single-processor architecture. In the dual-processor model, a real-time operating system might run on the second processor, which would be dedicated to communications support.

This specification is a draft - it is NOT an approved CELF specification. Work on this specification is ongoing and the next draft may look significantly different.

The scope and details of the API are under review and discussion. The target for the next revision is the end of October 2005.

Formal Review

The Reference Architecture, Preface, Circuit-Switched, and Packet-Switched Communications chapters have now been submitted for Formal Review. For more information, see Mpp Api Formal Review.


Approved Specifications

No specifications have been approved by the Working Group for submission as CELF Specifications.

Draft Specifications

The following documents are working drafts in development by the Working Group. They have not been approved by the Working Group for submission to the Architecture Group and Board of Directors as CELF Specifications.

The Media:MppApiRefArch-2.2.4.pdf Reference Architecture] specification defines the layering of the system and its major components. UPDATED 2006.1.12 The Working Group's goal is a broad API covering most of the functionality needed by handset applications. At this time the Working Group is actively developing only the Telephony part of the API. The Telephony API is divided into a Preface, four Specifications, and a Programming Guide:

The Preface. UPDATED 2006.2.2

The Circuit-Switched section describes APIs for setting up and managing voice calls. UPDATED 2006.1.12

The Packet-Switched section describes APIs for data calls. UPDATED 2006.1.12

The Short Message Service section describes APIs for sending and receiving SMS messages. UPDATED 2005.12.27

The Equipment section describes APIs for managing the handset hardware.

The Programming Guide describes the basic concepts of the programming environment for applications using the MPP API and provides MSC scenarios for the major use cases for each section of the API specification.

This is the coverage for the first release of the API. Additional sections will be added in the future to broaden the scope of the API.


Comments on the specification should be sent to [1]. We welcome comments from all interested parties; you do not need to be a member to comment.

Remaining Issues

This specification will require substantial discussion and review by the Working Group. There is no pre-existing agreement on the scope of standardization and there are likely to be other candidate APIs in specific areas, such as telephony. This specification is a proposal to the WG; the WG has not reviewed or accepted it as a WG output.

Original Submissions

This section contains the original specifications submitted by NEC and Panasonic, which cover a much broader scope than the ones currently in development. The four sections the Working Group is currently advancing are based on about a third of the original Telephony API. The API also includes additional functional areas beyond Telephony. These Specifications are available here as reference materials and as source materials for CELF members who would like to initiate work in preparing additional sections for CELF development.

The Application Framework API.

The complete Telephony API.

The Equipment Service API.

The Multimedia API.

The Reference Architecture.