1 © nokia sip 2003 conference / 15-01-2003 / markus isomäki sip-based presence and messaging...

1 © NOKIA SIP 2003 Conference / 15-01-2003 / Markus Isomäki

SIP-based Presence and Messaging Services in Wireless Networks

Markus Isomäki

Nokia


Outline

• Current advances in wireless terminal capabilities

• Specific aspects of wireless terminals

• Roadmap of SIP services in wireless terminals

• Standardization status and estimates for presence, messaging and chat

• IETF SIMPLE, SIPPING and SIP• 3GPP Release 6


What Is Happening With Wireless Terminals During 2003

• Large colour displays• Graphics, pictures, video, more advanced UIs

• Digital cameras• Enable Messaging (currently MMS) & Presence with images • Personal/shared photo albums

• Video cameras• Near-real time streaming• Messaging with video clips (large size!)

• Enhanced data rates• GPRS available in most new models• WCDMA during 2003 with ~ 100 kbps


Wireless Terminals – Other Key Aspects

• Standardized/Open APIs• Java, Symbian

• Downloadable applications• Games etc.

• Specialization• Different models are good for different applications

• Multi-terminal ownership and use• This will set demands on protocols• Combined use with laptops & fixed PCs


Available Protocols and Services

• MMS• Camera phones with GPRS taking off

• Wireless Village• The first wave of Instant Messaging, Presence, Chat

• E-mail• WAP/Web browsers• Near real-time audio/video streaming, evolving toward RTSP• Many nice downloadable applications with “proprietary” protocols

• IM & Presence• Games But there are still limitations

• Updating software is a major headache still in the future - Unlike in the PC world, the first software version MUST work and interoperate

• Interoperable products require good and mature standards!


Special Aspects of Wireless Terminals

• Limited bandwith• Applications will work, but response times may

become frustratingly long if protocols are not done right

• Signaling Compression (SigComp) and RTP/UDP/IP header compression (RoHC)can deal with protocol overhead

• Protocols should be designed to send only changed data, not always the full state

• User interface• Displays are still relatively small, not many

concurrent windows• Relatively difficult to type – phonebook becomes an

essential aid• It is necessary to integrate all aspects of the

application into a single coherent UI – using browser for application data configuration not very handy


SIP in Wireless Terminals

• It will be one of the main protocols in IP-based terminals• Important to have open APIs for developers

• The first phase (2003-2005) will be mainly non-real-time services• Presence• Instant messaging• Multi-party Chat• Setting up sessions for near-real-time voice, video and games

• After that (2005->) strict real-time applications will follow• Voice• Video• Multimedia conferencing• Application sharing?


Standardization Status

• IETF• Main source of the protocol specifications• SIMPLE WG: Presence, Instant Messaging, Data Manipulation• SIPPING WG: Conferencing• SIP WG: Approving the SIP extensions

• 3GPP• Ahead of IETF in requirement setting• Makes protocol profiles of IETF RFCs for IMS architecture• Presence • IMS Messaging Evolution• IMS Group Management

• OMA• IMPS WG• Working on SIP/SIMPLE, but unclear what the scope of that

work will be vs. IETF and 3GPP• Interoperability between SIP/SIMPLE and Wireless Village


IETF SIMPLE/SIPPING – Main Ongoing Issues 1/2

• Presence Publication• SIP-based method selected• New requirements coming from multi-terminal use cases• For instance overriding the information published by another

terminal

• Presence Information Document format extensions• Media capabilities: express preference/support for voice, video,

IM etc.• Proposal to re-use SIP Callee Capabilities exists• Carrying multimedia content: images, logos

• Presence event filtering• Will be on SIMPLE WG charter• Filtering will be event package specific, generic solution too

complex• Rules on triggering and content

• Instant Messaging sessions• Proposals about the transport protocol have varied through the

last year, hopefully stable now


IETF SIMPLE/SIPPING – Main Ongoing Issues 2/2

• Presence list

• Messaging enhancements• Requirements draft just published• Still open whether all the features feasible with SIP• Storage & retrieval, conference invitations, group messaging,

etc.

• Conference Policy Control Protocol• Creating Conferences and setting up conference parameters• Invitation list, access lists, participant rights• This is essential already for the multi-party chat service

• Data manipulation• Requirements draft exist in SIMPLE WG• -> Next page


IETF SIMPLE – Data Manipulation

• Standardized protocol to configure application settings• This could be done with a Web/WAP browser, but it would be

clumsy in wireless terminals• Management of presence and messaging lists

• CREATE list, DELETE list, ADD entry, REMOVE entry• Management of presence authorization policies

• Logic which determines which lists/groups are able to see what information

• Can be a simple scripting language• Could be fixed without possibility to change

• Management of those lists (e.g. block, allow, private)• Similar to presence and messaging list management

• Must work in an environment where multiple clients manage the same data

• Atomicity of operations• Notification of changes, synchronization

• ACAP and SOAP with SIP notifications proposed as potential solutions


Example Presence Scenario

PrivateAliceBob

AllowJohnPeterLucyTom…

PUA A

PUA B

CompositorTuple 1ATuple 2Tuple 3Tuple 4

PresenceDocument

PUBLISHTuple 1BTuple 2

PUBLISHTuple 1ATuple 3Tuple 4

PUA A and PUA B publish the same information (Tuple 1). PUA A wins

based on explicit preference or based on compositor policy

Tuple 1A Tuple 2Tuple 3Tuple 4

Tuple 1A Tuple 3

Watchers in different groupsare given different parts and views of the overall presence information

Data Manipulation managesthis information


3GPP Release 6 - Related Work Items• Presence

• Requirements stable• Architecture and protocol selections mainly done, authorization

and list management not specified yet• Mapping of IETF solutions to IMS Stage-3 specifications ongoing,

protocol requirements submitted to the IETF• Official 3GPP Completion target 06/2003

• IMS Messaging Evolution• Immediate, deferred delivery and session based messaging• Requirements stable• Architecture and protocol selection work done:

• Immediate -> SIP MESSAGE • Deferred Delivery -> MMS • Session based -> SIP messaging sessions

• Official 3GPP Completion target 09/2003• IMS Group Management

• Requirements stable• Should be harmonized with IETF data manipulation and conference

control work• Official 3GPP Completion target 09/2003


3GPP IP Multimedia Subsystem Release 6

P-CSCF I-CSCF

S-CSCF

Gm

Mw Mw

Cx Diameter

GGSN

GoCOPS for

Policy Control

Visited Domain

Home Domain

Compression

APSE HSS

ISC

Sh

GPRS Core

WCDMAEDGEGPRS MGCF/BGCF

PSTN

PresenceMessaging

Conferencing


Conclusions

• Basic SIP specifications from the IETF and 3GPP Release 5 IMS are stable and ready to result in interoperable products

• Presence, Messaging, Chat and Session setup for non-real-time applications are the first uses of SIP in wireless terminals

• Many more standards (RFC, 3GPP TS) still needed to assure interoperability with all advanced features

• SIP PUBLISH• Instant messaging sessions• Data Manipulation protocol (especially important for wireless!)• Conference Policy Control Protocol

• Target is to get the standards complete during 2003 to allow mass-market deployment during 2004!

1 © nokia sip 2003 conference / 15-01-2003 / markus isomäki sip-based presence and messaging...

Documents