Technical Meeting
San Jose, USA, Friday January, 25th 2005
January 25th, 2005
1
Mobile Phone Profile WG
Technical Meeting Session
Scott E. Preece
WG Chair
January 25th, 2005
2
Agenda
•
•
•
•
Antitrust Warnings
Introduction – Where We Are
NEC/Panasonic API Update Presentation
Review of Work Items and Participants
– Reference Tiers and Profiles
– Reference Architectures
– MPP Requirements for Core Linux Components
– Middleware Scope and Requirements
– Open-Source Projects (Component Inventory)
– Related Organizations
– API Scope and Requirements
• NEC/Panasonic API Proposal
– Domain Roadmap
– Schedule
January 25th, 2005
3
WG Organization
• Chair: Scott Preece (Motorola)
• 58 Participants on mailing list from 25 member
companies
– 15 phone manufacturers
– 5 chip vendors
– 5 OS and middleware vendors
– 2 other interested parties
• Core Group: Motorola, NEC, Panasonic, Samsung
January 25th, 2005
4
MPPWG Priorities
• Standardization of architecture and APIs for
mobile phone software providing internet and
multimedia services
– Develop Linux OS for Consumer Electronics
that meets requirements for mobile phones
– Accelerate migration of PC domain internet
services to MP domain by use of Open Source
Software
– Establish platform to support common
multimedia services with mobile phones
January 25th, 2005
5
Deliverables / Work Items
• Reference Tiers and Profiles (Draft Available)
• Reference Architectures matched to tiers (First sketch)
• MPP Requirements for Core Linux Components (Not
started)
• Middleware Scope and Requirements (Not started)
• Open-Source Projects (Component Inventory)
– Project/Component list (Not started)
– Reference implementations (Not started)
• Related organizations (Some identified)
• API Scope and Requirements (Proposal in preparation)
• Roadmap for domain evolution (Not started)
• Schedule (Out of date)
January 25th, 2005
6
Working Plan
• Periodic teleconferences and face-to-face meetings to
negotiate details
• E-mail interaction to provide raw requirements and review
work products
• Focused small groups draft specific deliverables
• To-date:
– Core Group provided initial materials
– One face-to-face (November)
– Very limited success at eliciting e-mail interaction
January 25th, 2005
7
Mobile-Phone Profile Reference Model
Applications (Phone,Browser,JAVA,PIM…)
Mobile Middleware
Carrier Specification
Modules
(FOMA,Vodafone,
i-Mode for overseas…)
MP-Domain-Specific
General purpose
Middleware
Carrier Common Spec. Middleware
Modules
APIs
Specific Middleware
Functional-Domain-- (OCR recognition
Engine,
Specific OSS
Bar code recognition
elements.
Engine….)
Linux Kernel
Device Drivers
(Communication)
Device Drivers (UI,Multimedia)
Existing or WG-created OSS implementations
WG-created or adopted plug-in points for non-OSS elements
Licensed elements provided by vendor (not in WG scope)
January 25th, 2005
8
Reference Tiers Profiles
• Set of “functionality points” – phone categories
we will generate profiles for
• A Tier Profile Defines:
– Typical functionality
– Variability
– Hardware performance and characteristics
– Memory (RAM, ROM, Removable)
January 25th, 2005
9
Reference Tiers Proposal
• WG has identified and characterized four tiers:
– Smart Phone
– Media Phone
– Feature Phone
– Basic Phone
• Described in terms of “typical” capabilities (i.e.,
qualitative tiering)
• MPPWGReferenceTiers
January 25th, 2005
10
MPPWGReferenceTiers - CE Linux Forum Members
1 of 1
http://tree.celinuxforum.org/celfwiki/moin.cgi/MPPWGReferenceTiers?a...
MPPWGReferenceTiers
Aspect
Smart Phone
Media Terminal
Feature Phone
Focus
business focus
Personal/Entertainment Focus
Lifestyle Focus (voice plus social
Voice
networking support features)
Primary
Functionality
Full PDA functionality
(Calendaring, address
book)
Strong PIM support, personal
content management features
Minimal PIM functionality
(phonebook, datebook)
Phonebook and call
logs
Extensibility
Extensible
(downloadable features)
Limited extensibility (MIDlets or
BREW)
Limited extensibility
(MIDlets/BREW)
No extensibility
Multimedia
Optional
Vido capture support,
Media/content players, stereo
Limited multimedia support
(pictures, MP3, MIDI,Simple,
low-frame-rate animations)
None
DRM
Optional
Multiple DRM schemes
Hard DRM (limits on copying
any media of given types)
None
Camera
Optional
2-3 megapixel camera
VGA camera or no camera
No camera
Browser
XHTML Browser
XHTML Browser
WAP Browser (text-centric)
Embedded access to
specific URLs
Display
QVGA or larger color
display
QSIF or larger color display
QSIF or smaller color display
Small display
(64x96), non-color
Interaction
Touchscreen UI or
Specialized keypad for
QWERTY keyboard plus
media/game interaction
pointing device
Standard keypad plus
carrier-specific keys
Standard keypad
Connectivity
2.5G or 3G connectivity, possibly
3G connectivity, possibly
2G connectivity; USB or serial
WLAN; High-speed USB;
WLAN, Bluetooth, IrDA
cable
Bluetooth
2G connectivity;
proprietary
accessory cable
Memory
32M RAM, 64M ROM,
removable storage
64M RAM, 64M ROM, Hard Disk 16M RAM, 16M ROM, no
or large removable storage
removable storage
8M RAM, 8M
ROM or less
Processor
120MHz
200MHz
15MHz
30MHz
Plain-Old Mobile
1/25/2005 11:18 PM
Reference Architectures
• Reference Architecture is a commonly understood
structuring of systems
– Common components
– Common subsystems
– Relationships, dependencies, interactions
– Variabilities
January 25th, 2005
11
Reference Architecture
TV/Video Movies E-Books Games
Applications
Value-add
GUI
Browser
App. Mgr.
Phone
PDA/
PIM
BMS
Email
CELF
APIs
Carrier Specific
Barcode
OCR
Content
Handling F/W
Graphics API
Telephony
Services
Middleware
JVM
Modem
Services
OTA
Provisioning
Browser
Services
Multimedia
services
Database
DM
Location Services
Sync.
Services
IM
POP/IMAP
Bluetooth
SMS
WiFi
MMS
USB
Linux
SMIL
Serial
Drivers
H/W
January 25th, 2005
Alert
Management
Security
Services
Event Distribution
Connection Management
SIP
DRM
Power Policy
/Services
Codecs
Camera
API
Drivers
Stacks
Protocols
Personal
Services
Audio
SCA
Eth.
IrDA
Air Stack
WEP
Comms. Driver
DSP
SIM
Hot Plug
Frame Buffer
SD/MMC
PCMCIA
CF
Memory stick
12
MPP Requirements for Core Linux Components
•
•
•
•
Attributes commonly required for the domain
Options commonly required
Configuration options commonly required
Dependencies on other working groups
January 25th, 2005
13
Middleware Scope and Requirements
• Middleware important for the domain
• Boundaries of WG scope
January 25th, 2005
14
Open-Source Projects (Component Inventory)
• Open-source software projects that fill slots in the
reference architecture(s)
• Building the Component Inventory
• MPPWGComponentInventory
January 25th, 2005
15
MPPWGComponentInventory - CE Linux Forum Members
1 of 6
http://tree.celinuxforum.org/celfwiki/moin.cgi/MPPWGComponentInven...
MPPWGComponentInventory
This table lists many of the components of a mobile phone, with information about the APIs that provide
access to the component and available open-source implementations fo the APIs. Component names will be
tied to the Reference Architecture, once that is defined; the current names are temporary.
Only projects available with OSI-compatible licenses should be included.
The columns in the table are:
a descriptive name for the component
the name of a known API (typically a library)
the name of an open-source project implementing that API
the names of WG member companies familiar with the project
the names of WG member companies prepared to work on the component to
make it meet MPP WG needs
Note that there may be more than one API and/or project for a given component; if so, there should be a
separate line for each, with only the first line containing the component name.
1 Application Framework
Component
API
Project
Knowledgeable
Work Interest
Application Management
Application Download/Installation
OSGi
Coding Utility library
Glib
2 Feature Services
Component
API
Project
Knowledgeable
Work Interest
Location Service
Alert Management
Contact Management
Content Management
Media Player Services
3 Connectivity
Component
API
Bluetooth Stack
Project
BLUEZ
Knowledgeable
Work Interest
Motorola
Affix
IrDA Stack
irda-utils
Connection Management
DSN
DNSMASQ
Buffer Management
Accessory Support
1/25/2005 11:16 PM
MPPWGComponentInventory - CE Linux Forum Members
2 of 6
http://tree.celinuxforum.org/celfwiki/moin.cgi/MPPWGComponentInven...
Session Management
Connectivity Framework
Hotplug Control
hotplug
murasaki
4 Browser
Component
API
XML Parser
expat
Project
Knowledgeable
Work Interest
libxml2
HTTP
HTTP Client
jakarta
dillo
Browser Push
WAP
OMA
WTLS
Rendering (HTML, XML, xHTML, WML)
ECMAScript
WCSS
SSL
OpenSSL
WAP Binary XML support
libwbxml
libwbxml
5 Java
Component
API
Project
Knowledgeable
Work Interest
JVM
MIDP/CLDC
Various JSRs
Java Application manager
6 Device Management
Component
API
Project
Knowledgeable
Work Interest
Power-Up and Power-Down
Power Policy Management
OTA Patch Support
7 Security
Component
API
Project Knowledgeable
Work
Interest
Certificate Service
User Authentication Service
Crypto Service and Libraries
OpenSSL
GnuPG
1/25/2005 11:16 PM
MPPWGComponentInventory - CE Linux Forum Members
3 of 6
http://tree.celinuxforum.org/celfwiki/moin.cgi/MPPWGComponentInven...
Security Policy Manager and Framework
SELinux
Key Management
Secure Boot
Secure Communications Protocols
OpenS/WAN IPsec
Protected Filesystem
Motorola
Encrypted Filesystem
SFS
EncFS
Digital Rights Management (we will share our LUFS-based
implementation)
Motorola
8 Persistent State
Component
API
Project
Database Service
SQLite
SQLite
Knowledgeable
Work Interest
Motorola
Berkeley DB
Device State Management (configuration)
SIM Management
Removable Storage Management
Download Management
Filesystems
SquashFS
JFFS2
cramfs
Dosfstools
Flash Filesystem
9 Synchronization
Component
API
OBEX
Project
Knowledgeable
Work Interest
OpenOBEX
Synchronization Management
Synchronization Services (protocols)
SYNCML
10 Multimedia
Component
API
Project
Knowledgeable
Work Interest
Audio Management
Codecs
Multimedia Framework (for codec plug-ins)
Content Handling Framework
Video Transfer (window)
SMIL
MIDI
11 Messaging
Component
API
Project
Knowledgeable
Work Interest
1/25/2005 11:16 PM
MPPWGComponentInventory - CE Linux Forum Members
4 of 6
http://tree.celinuxforum.org/celfwiki/moin.cgi/MPPWGComponentInven...
SMS
EMS
MMS
E-Mail (POP3, IMAP)
Instant Messaging
12 Telephony
Component
API
Telephony API
GSM 7.07/9
Project
Knowledgeable
Work Interest
Call Processing
Call Control
Messaging
Network Registration
Voice Call Stack
Data Call Stack
GPRS
EDGE
Modem Control (AT Commands)
13 User Interaction
Component
API
Toolkit(s)
GTK+
Project
Knowledgeable
Work Interest
Motorola
Qt
Qt/Embedded
Skinning
Window Management
Localization
SVG (Scalabe Vector Graphics)
Framebuffer Abstraction
DirectFB
Motorola
OpenGL
OpenGL/ES
Motorola
Text renderer
Pango
Font Engine
freetype
Font Management
fontconfig
Layout Engine
Graphics Library
Gdk
gdk-directfb
libpng,libungif,libjpeg,libtiff
14 Test Support
Component
API
Logger
syslogd
Project
Knowledgeable
Work Interest
klogd
1/25/2005 11:16 PM
MPPWGComponentInventory - CE Linux Forum Members
5 of 6
http://tree.celinuxforum.org/celfwiki/moin.cgi/MPPWGComponentInven...
Test Command Interpreter
Test Framework
GNU check
CUnit
Profiler
gprof
Coverage mesurement
gcov
15 Device Drivers
Component
API
Project
Knowledgeable
Work Interest
USB (Client, Host, OTG)
Serial I/O
WiFi
Bluetooth
IrDA
Location Device(s)
Audio
Headset
Display(s)
Keypad(s)
Touchpad
Memory Card
SIM Card
Battery
Power Management
Real-Time Clock
Timers
Flash memory
Accessory Bus
Lights
Chipset Management
Physical Manipulation
16 Debugging Support
Component
API
Project
Kernel Crash Dumps
Debugger
Knowledgeable
Work Interest
LKCD
gdb(GNU Debugger)
17 Operating System
Component
API
Project
Linux (kernel, libraries, utilities)
Real-time support
Knowledgeable
Work Interest
Motorola
RTAI
Resource Manager
Event Distribution
1/25/2005 11:16 PM
MPPWGComponentInventory - CE Linux Forum Members
6 of 6
http://tree.celinuxforum.org/celfwiki/moin.cgi/MPPWGComponentInven...
Hotplug
Linux Hotplug
Dynamic Power Management
Motorola
Networking (TCP/IP, IPv6, etc.)
Motorola
USAGI(IPv6 stack)
OpenS/WAN(IPsec)
SIP
oSIP(SIP library)
Vovida(SIP liblary)
Performance, memory, power improvements
Motorola
1/25/2005 11:16 PM
API Scope and Requirements
• Core group proposed that an API for third-party
application builders should be a high priority
• Need WG agreement on scope of the API
January 25th, 2005
16
NEC/Panasonic API Proposal
• The core group thought it was important to have a
strawman API as a starting point
• Ideally this should be a “real” API, known to
provide functionality needed to support the full
scope of the domain tier
• NEC and Panasonic have jointly provided a
proposed API
• Proposal is meant as a starting point – assume the
WG would evolve it for consistency, organization,
and needs of additional technologies
January 25th, 2005
17
Proposed Platform
Profile(1/3)
:Module (Planning to Open)
X11R6 may be removed
• Profile Body
Tel App
Standby Screen,
main menu,
videophone app,
phone app,
phonebook,
NW service,
and
phone function
setup
System App
Air download
Generic LCD
display
Backside LCD
display
PIN authentication
and monitor mode
Other function
setup
Equipment alarm
MultiMedia
App
Multimedia app
Still image viewer
Video viewer
Camera app
Vector G viewer
Avatar
Ring tone
M-5 Telephony API M-2 AP Framework
[Services (ELIB)]
API
Resource management
library (API), SD file
Packet communication
Voice communication,
SMS communication
Equipment, key,
Authentication
Schedule, Data exchange
Record playback
Voice response
UI control
LMP management
Sound system
Service manager
Event transmitter, DRM
M-1 Common API
[Window Manager]
APC,WC,CLM,TMG
[Window System]
Fonts, Extended
Wiidget
[Inter-App communication]
MSB
[Other (AP Framework)]
PICT display library
Image library
[Text input(AP Framework)]
XIM server
:API (Planning to Open)
Data processing
App
OCR, barcode, SD-PIM,
data transfer, memory
transfer,
external I/F communication,
user data, IR, schedule,
voice memo, schedule alarm
and data folder
glibc
Java Engine
Java AP
SMS, mailer
Browser,
HTML mailer
Internet Java AP
AppEngine Engine
(AP Engine/CPE)
CPE,AWS
HTTP,SSL
IMD,FLASH
M-4 Multi Media API
Multi Media Multi Media Manager
[3G-324M] : H324, H245,H223
Elib
[Multi Media I/F]
Video control ELIB
Camera control ELB
Video phone ELIB
[3G-324M]
H324, H245,H223
GTK+
X11R6
Internet
App
File I/O, Mux/Demux,
Streaming
[Multi Media Plug-in]
File IO , Demuxer, Muxer ,
Video/Voice/Text control
[SCA]
Camera/Video control
[Video phone middleware]
Video phone/Video control
/Camera control ELIB
(AP Engine)
JAM
CLASS
KVM
Others
Accessory menu
Accessory
(text memo)
Accessory
(calc)
M-6 Data
Processing
API
M-3 Mobile
Middle
API
・Bar code(API)
・OCR(API)
[TAF(S-I/F)]
AT, CS, PS,
SMS, DCF,
TMF, EXT-IF
[Mobile Middleware]
MAW, OBEX,
OMF
Multi Media Driver API
VH(VideoHandler)
M-8 Driver API
DSP Lib, Tone Lib, Voice Path Lib, Melody Lib
Linux Kernel(K1-K7 Kernel API)
January 25th, 2005
Device Driver
18
2 Feature Services
4 Browser
5 Java
10 Multimedia
11 Messaging
12 Telephony
3 Connectivity
6 Device Management
7 Security
8 Persistent State
9 Synchronization
1 Application Framework
13 User Interaction
14 Test Support
16 Debugging Support
Application (Phone, browser, Java, PIM etc.)
APIs
Carrier specific module
(FOMA, Vodafone,
i-Mode for overseas)
キャリア共通
Carrier common
モジュール
module
Generic
middleware
汎用ミドルウェア
Functionally
機能特化
specialized OSS
OSS
ベンダー固有
Vendor
specific
ミドルウェア
middleware
Linux Kernel
Device Driver
(Communication)
Device
Driver (UI, Multimedia)
API and profile specified part (Open source would be desirable)
Carrier specific module
Vendor specific module
15 Device Drivers
January 25th, 2005
17 Operating System
19
Proposed Platform Profile (2/3)
•
APIs(1/2)
– Common
• equal to glibc (POSIX API , LGPL)
– Application Framework
• Contains following interfaces.
–
–
–
–
–
–
Window Manager
Window System ( X11R6, Xlib, Fonts etc. )
Inter-Application Communication
Basic Widget ( GTK+ : LGPL)
Character input
etc.
– Mobile Middle
• Contains OBEX and Interfaces of Supervisor task.
– Multimedia
• Contains following interfaces.
– Multimedia Manager
– Multimedia Extended library
– Multimedia Driver API( Video Handler interfaces )
January 25th, 2005
20
Proposed Platform Profile(3/3)
•
APIs(2/2)
– Data Processing
• Contains following interfaces.
– Bar-code reader
– OCR access reader
– Driver
• Contains following interfaces.
–
–
–
–
Audio Voice
Audio Tone
Audio Melody (MIDI)
DSP
– Telephony
• Contains following interfaces.
– Packet Communication, Voice Communication, SMS Communication, Device
Service, Certification and DRM, Schedule service, Data Exchange, Recording /
Playback etc.
• Contains some carrier specific functions.
It must be examined carefully.
January 25th, 2005
21
APIs Design Concept and their current status
•
•
•
•
•
Kernel-related-APIs
– They are generic and independent of any carrier specification.
Device driver-related-APIs
– They are independent of any carrier specification. and abstract its
hardware. However, only the verification on TI’s OMAP16xx Series has
been done at present. This I/F might be modified in case the functionality
of its device is enhanced (e.g. adoption of 3D hardware accelerator.)
Basic call (Out-going, in-coming, etc.)-related-APIs for mobile phones
– They can be available to mobile phone worldwide, since those APIs are
abstracted.(Verification will be required.)
APIs for supplementary services of mobile phones
– They are dependent on the specific carrier at present. Those shall be
updated for the mobile phones worldwide.
Multimedia APIs
– They can be independently implemented from any carrier spec, since they
have general-purpose-I/F called SCA(Stream Control API).
January 25th, 2005
22
Related Organizations
• Goal to build a list of other organizations working
in the domain and plan relationships with them
• MppRelatedOrganizations
January 25th, 2005
23
MppRelatedOrganizations - CE Linux Forum Members
1 of 1
http://tree.celinuxforum.org/celfwiki/moin.cgi/MppRelatedOrganization...
MppRelatedOrganizations
1 Related Organizations
This list includes organizations, consortia, standards groups, etc., working in the Mobile Phone domain.
Organization
Home
Relationship to MPP WG
OMA (Open Mobile Alliance)
http://www.openmobilealliance.org
Standards group driving data service standards for mobile
phones
MeT (Mobile electronic
Transaction)
http://www.mobiletransaction.org
Standards group for secure mobile transaction
MPF (Mobile Payment Forum
http://www.mobilepaymentforum.org
The work of Forum is focused on standardizing mobile
payments
MIPC(Mobile Imaging and
Printing Consortium)
http://www.mobileprinting.org
Industry group to provide for the camera-phone with
wireless/wired printing standard
NFC(Near Field Connection)
http://www.nfc-forum.org
A industry association advancing near field short-range
wireless interaction in CE devices
W3C(World Wide Web
Consortium)
http://www.w3.org
Its activity covers common mobile access protocols based on
Open Source/GPL compatible basis
1/25/2005 11:19 PM
Domain Roadmap
• Goal to build roadmap of expected future
requirements/scope of the domain
January 25th, 2005
24