Report: Future of Mobile Content Services TOC

Contents
Synopsis
Subject Area
Report Content
Who Should Read this Report?
Introduction
Online Projects
Yahoo! Search BOSS
Google AppEngine
ebay developer
Amazon Web Services (AWS)
Salesforce.com AppExchange
Telecoms Projects
Orange Partner Programme
Historic Announcements
API Features
Commercial Aspects
-No Commercialisation Path
-Onerous Usage Restrictions
Verizon Open Developer Initiative (ODI)
Comparison with access Orange API
Example Market Segments
Business Rationale
Business Model Options
Device Technical Standards
Activation and Billing Processes
-Device Activation
-Billing
Vodafone betavine
Example API Features
Commercial Aspects
BT Web21C
Example API Features
Commercial Aspects
Other Projects
Europe
Asia
Analysis: Mobile Services
Historic Model: Mobile Content Service Development
Need for a New Model
Slow, labour-intensive, costly process
Limits Creativity
Limited API functionality
Comparison: Online vs. Telecoms Projects
Senior Management Commitment
Strong Commercial Focus
-Project Controlled by Business People
-Offers Clear Path to Revenue
-Support Infrastructure
Competitive Offer
Evolution of API Models
Integrated APIs
-Model 1 API: Device-focused
-Model 2 API: Network-focused
-Model 3 API: Device and Network - Integrated
Cross-network Considerations
-Cross-network Considerations
-Converged Services
Example API: Description
API Features
Notification Manager API
Individual Messaging API
Group Messaging API
Inbound Messaging API
Voice Calling API
Conference Calling API
Voice Messaging API
Location API
Contact Manager API
Mapping API
Browser API
Data Exchange API
Application Trigger API
Media Capture API
Inter-service Messaging API
Device Query API
Customer Data API
Authentication API
Billing and Payment
-Pricing
-Billing Strategy
Payment Service Provider Function
-User Charging
-Merchant Charging
-Brand Considerations

Future of Mobile Content Services

Table of Contents