Converged IP Messaging
Integrating multiple communications platforms, multiple
devices and existing standards for global interoperability
Mark Cataldo
Chair, OMA Technical Plenary
www.openmobilealliance.org
Future of Mobile Messaging, Budapest, 31
Agenda
OMA and its messaging activities
Drivers for change
”
“
The Open Mobile Alliance
VISION
No matter what device I have,
No matter what
service
I want,
No matter what
carrier
or
network
I’m using,
I can
communicate, access
and
exchange
information
Created June 2002
• by leading mobile operators, device and network suppliers,
information technology companies, content and service
providers -- now near 400 member companies
International organisation
• developing open, market driven interoperable specifications
for global adoption of data services
Robust Interoperability Testing Program
OMA deliverables and value
OMA develops specifications, promoting application level interoperability
Broadcast Services, Digital Rights Management, Mobile Location
Services, Games Services, Device Management, Advertising,
Messaging…
Reaching beyond mobile market
Applicable to IP based networks both fixed and mobile
Consumer Electronics devices
Traditional PC and telephone environments
OMA avoids duplication, divergence and fragmentation
OMA has an extensive network of liaison relationships
OMA’s work in messaging standards
OMA, like industry trends, has historically
focused on “the task at hand”
– creating application silos
Multimedia Messaging
Instant Messaging (IMPS)
Streaming and Gaming
Network Subsystem
Base Station Subsystem
...
...
Charging Media C ontrol QoS . . . Charging Media C ontrol QoS . . . Charging Media C ontrol QoS . . .MMS
MMS
Streaming
Streaming
Gaming
Gaming
PoC
PoC
Presence
Presence
...
IM
IM
PSTN
WLAN
2.5G/3G
IP Multimedia Subsystem
• Session Control • Media Control • QoS • Charging • . . . ....
...
Multi -service IP Network
For IMS-based enablers, OMA has improved
matters
Interoperability across different network types
Working with 3GPP
ensure OMA enablers and IMS are compatible
Reusing other enablers such as Presence and
XDM (for contact list and group management)
OMA’s work in messaging standards
OMA has
new approach to messaging standardisation
single set of protocols for communication services
support for existing and many different user experiences
accessible from any device, over any IP network
multiple devices per user
Interworks with existing messaging services and handsets
common message repository
reuse of other enablers
e.g. Presence and XDM
reuse of existing specifications
e.g. PoC and SIMPLE IM, as needed
Converged
Agenda
OMA and its messaging activities
Drivers for change
More than PTT and Mobile IM
Converging industry requirements include
Email, MMS, SMS
OMA existing work in XDM, SIMPLE Presence and
Push-to-Talk
Messaging services currently in silos
Fixed mobile convergence
Messaging Presence
New Platform
SMSC
SMSB
MMS
SMS/MMS Platforms
Interworking
with SMS/MMS
•
Presence
•
Conversation
model
•
Multi-party
conversations
•
No limits to
formats – e.g.
pictures, audio etc.
•
Multiple Devices
Dave
Anders
New phone Legacy SMS phoneSMS inbox
Dave
Dave
Dave
Dave
MMS inbox
Dave
Conversation with Anders
Dave: Hi Anders
Anders: Hi – wassup??
Dave: Hi – will you be going to
the Nokia meeting?
Anders: Yes – I was planning
to attend between 2 and 4pm.
Dave: Great – can we meet
afterwards to discuss DVBH?
BTW. Check out this new
Nokia WiFi phone
Anders: Yep – that would be
great – Saw the Nokia. It has
integrated VoIP. I would also
like to discuss WiFi strategy.
Dave: OK – no problem. See
you later.
Technology convergence
No need to maintain existing messaging silo applications
in IP multimedia networks
e.g. text only or voice only services
Lack of interoperability between application platforms
own O&M procedures
own handset client and configuration data
new training for engineers and customer care
OMA moving to common, more generic platforms
Enable converged messaging technology, and still
support different user paradigms: push, session or pull
Enable interworking between existing messaging
services and a new converged messaging services
Convergence
Service examples
Technology convergence
Agenda
OMA and its messaging activities
Drivers for change
Future Converged Messaging vision
Integration and Interoperability
New services and network capabilities opportunities
multiple access methods and services
OMA track record of integrating fixed and mobile
technologies to enable global interoperability
Planning smooth migration
of SMS/MMS user experience to new IMS-based messaging
architecture
This will require:
New Vision: Converged IP Messaging
Converged IP Messaging (CPM) enables creation of services
allowing
Communication without knowing the technology supporting a given
messaging experience or session
Parallel conversations across multiple devices and media types
Personalised services through predetermined preferences
E.g. which messages are sent to which device(s),
Storage of any type of message and media in common network repository
Seamless communication between legacy voice, video and messaging
services (such as MMS, SMS), and CPM services,
Use of presence support to enhance communications experiences,
Evolving CPM Ecosystem
CPM Service
Provider
CPM Subscriber
CPM User
CPM -enabled
value-added
application
Non -CPM
enabled user
CPM User
Non -CPM User
In remote domain
CPM Enabler
Remote
CPM Enabler
1
1
2
2
3
3
3
Service
Provider Resources
5
4
6
4
5
6
Service provider offering CPM -enabled
services to its subscribers
Remote CPM User - using CPM -enabled
communication services between different
CPM -enabled domains
CPM User - using CPM enabled
communication services in his home domain
Remote Non-CPM User - using communication
services with CPM Users utilizing CPM Enabler ‘s
Non-CPM User - using communication services
with CPM Users utilizing CPM Enabler ‘s
interworking functions
Value -added application - using CPM enabled
communication services over open interface
CPM Service
Provider
CPM Subscriber
CPM User
CPM -enabled
value-added
application
Non -CPM
enabled user
CPM User
Non -CPM User
In remote domain
CPM Enabler
Remote
CPM Enabler
1
1
2
2
3
3
3
Service
Provider Resources
5
4
6
4
5
6
Service provider offering CPM -enabled
services to its subscribers
Remote CPM User - using CPM -enabled
communication services between different
CPM -enabled domains
CPM User - using CPM enabled
communication services in his home domain
Remote Non-CPM User - using communication
services with CPM Users utilizing CPM Enabler ‘s
Non-CPM User - using communication services
with CPM Users utilizing CPM Enabler ‘s
interworking functions
CPM Use Cases
Converged user paradigms in one conversation thread
Check presence
Start voice discussion
Add unidirectional streamed video
Add picture
Change over to text
Multimedia group communication
Multiple device environment
Multiple CPM addresses
Seamless interworking between a CPM user and a non-CPM
communication service user
VAS application messaging
Network-based storage (Common Repository)
Converged address book
Absence service
Presence List Checked
Voice Call Started
