3GPP IM Call Model and Presence

National Chung Cheng UniversityDept. Computer Science & Information Engineering

3GPP IM Call Model and Presence

Chiang, Wei-Kuo (江為國)

Assistant Professor Department of CSIE National Chung Cheng University Office : EA 311 Phone : 05-2720411~33126 Email : [email protected]

URL : http://www.cs.ccu.edu.tw/~wkchiang/

National Chung Cheng University


Mobile Communication Networks IMS Call Model & Presence2

Next Generation Network

Internet Telecom & Wireless Communication

IP

MGCF

CSCF

T-SGW MGWMGW

WLAN

GPRS

CSCFSIP

Server

PSTN

InternetWireless App.Server

3rd Parties App.



Outline

3GPP IMS Call Model

Application Triggering

S-CSCF & AS Interactions

Mobile Presence

Presence Service

3GPP & OMA Presence

Push-to-talk over Cellular

PoC Architecture and Operations

PoC High Level Procedures



IMS Service Architecture

Model

Serving CSCF

Incoming Leg Outgoing Leg

SIP+

Call Records

OLCMILCM

Registrar and

Notifier

Cx

Application Servers

CAP OSA APIs

MEGACOSIP+

Sh

MAP

SiOSA SCSIM-SSF

CSE

SIP AS

OSA AS

HSS

MRFP

MRFC

Incoming LegState Machine

Ougoing LegState Machine

Voice PacketsRTP

SCIM

AS AS



Application Server Types

SIP AS

SIP-based Application Servers

Examples

Presence Server (3GPP TS 23.141)

PoC Server (3GPP TR 23.979)

IM-SSF

IP Multimedia - Service Switching Function

Host the CAMEL network features (3GPP TS 23.278)

OSA SCS

Open Service Access Service Capability Server

Use the OSA API (3GPP TR 29.998)




Application Server

Service Logic

Service Platform Trigger Points Service Platform Trigger Points

SIP Interface HSS

S - CSCF

S

P

T

P Filter Criteria

sFC SIP

SIP SIP

iFC



Service Point Trigger

Service Point Triggers (SPTs) SPTs are those points in the SIP signalling on

which Filter Criteria can be set.

The points may cause the S-CSCF to send/proxy the

SIP message to an SIP AS/OSA SCS/IM-SSF

SPTs are defined: SIP method (e.g. REGISTER, INVITE…)

Presence or absence of some header field

Content of some header field or Request-URI

Direction of the request w.r.t. the served user

Mobile Originated (MO)

Mobile Terminated (MT)

Registered/ Unregistered users



Filter Criteria

Filter Criteria (FC) A FC triggers one or more SPTs in order to send

the related request to one specific app server.

The set of Filter Criteria that is stored for a

service profile of a specific user.

iFC (initial Filter Criteria) - S-CSCF receives from HSS

sFC (subsequent Filter Criteria) - S-CSCF receives from AS

S-CSCF handles FCs in right sequence (by priority)

FCs Contain the following information

Address of Application Server

Priority of Filter Criteria

Trigger Point : composed by 1 to n SPTs

Default handling

Optional Service Information (e.g. IMSI)



S-CSCF for iFC

iFC are stored in the HSS as part of the user profile and are

downloaded to the S-CSCF upon user registration, or upon a

terminating initial request for an unregistered user.

S-CSCF on reception of a REGISTER request send a third-party REGISTER request to each AS that

matches the Filter Criteria for the REGISTER event

S-CSCF on reception of any other request 1)Set up filter criteria list by priority for that request

2)Parse the received request in order to find out the SPTs

3)Check with trigger points of unchecked highest priority FC

If not match, S-CSCF proceed with step 4

If match, S-CSCF shall

Add an indication to the request

Forward the request to the AS. The AS then performs the

service logic and may send the request back to the S-CSCF

Proceed with step 4 if the request received again from AS 4)Repeat steps 2 and 3 until the last filter criteria

5)Route the request



Triggering for REGISTER

Download iFC

Match a trigger

1. Inform about the user registration event

2. Trigger services

1. SIP REGISTER

3. SIP 200 OK

From: UserATo: User ACall-ID: X

From: UserATo: User ACall-ID: X

S-CSCF ApplicationServer

5.SIP REGISTER

From: S-CSCFTo: User ACall-ID: Z

6. SIP 200 OK

HSS

2. Cx

4. Filter Checking

Contact: S-CSCF



Outgoing Call legIncoming Call leg

HSS

SIPInterface

Service Logic

Service Logic

AS 1 AS 2

ISC ISC

Sh Sh

Cx

1

2

4.b

3 SIP message possiblywith modification by AS1

SIP Interface

SPI

4.a

INVITE Match Initial Filter Criteria

S-CSCF

Filter Criteria X -> AS1Filter Criteria Y -> AS2

5a SIP message possiblywith modification by AS2

6a

SIP message forwarded by S-CSCF SIP message forwarded by S-CSCF

Triggering for INVITE



Explanation (1/2)

This example applies both for call originating and

terminating procedure. But we assume this is a call

originating procedure.

User has registered with the network. Its filter criteria

and addresses of the assigned application servers have

been downloaded to its S-CSCF during registration via Cx

interface. Also, the application server specific data may

have been downloaded via the Sh interface to the

application server during registration.

In this example, two application servers are assigned to

provide additional services to a subscriber and they are

showed as AS1 & AS2.



Explanation (2/2)1. User initiates a SIP session by sending INVITE to its S-CSCF.

2. On receiving this request, the S-CSCF evaluates the SPTs and checks if

they match the initial filter criteria X for AS1. If they match, the S-CSCF

forwards this request to AS1.

3. The AS1 performs any needed service logic based on the Service Key and

sends the SIP request possibly with service related modification back to the

S-CSCF.

4.a On receiving the request from the AS, the S-CSCF evaluates the SPTs and

checks if they match the initial filter criteria Y for AS2. If they match the S-

CSCF forwards the request to the associated Application Server AS2.

4.b If the request doesn't match any further filter criteria, the S-CSCF forwards

this request to the next hop based on the route decision.

5.a The AS2 performs any needed service logic based on the Service Key and

sends the SIP request possibly with service related modification back to the

S-CSCF.

6.a The S-CSCF checks the request sent by AS2 and finds that no initial

criteria is matched, then the S-CSCF forwards this request to next hop

based on the route decision.



S-CSCF Functional Model

Combined I/OLSM Incoming/Outgoing Leg State Model

Store session state info

Acting as a SIP Proxy, Redirect

Server or User Agent

dependant on the info received in the

SIP request, the filter conditions

specified or the state of the session

ILCM and OLCM Incoming/Outgoing Leg Control Model

Store transaction state info

Registrar and Notifier handles registration & subscription

to and notification of registration

events

Model

Serving CSCF

SIP+

OLCMILCM

Registrar and

Notifier

Cx

HSS

Incoming LegState Machine

Ougoing LegState Machine

ApplicationServer



AS Functional Model

AS-ILCM shall store transaction state

may optionally store session

state

depending on the specific

service being executed.

interfaces to the S-CSCF

(ILCM) for an incoming leg.

AS-OLCM Similar to AS-ILCM

Application Logic can access the HSS via the Sh

or Si interface to access

subscriber related data

Application

Server

SIP+Cx

HSS

AS-OLCM

S-CSCF

AS-ILCM

Application Logic

Sh/Si



S-CSCF & AS Interactions S-CSCF acts as a SIP Proxy

Application Server acts as Terminating User Agent (Voice Mail) or

Redirect Server

Call Forwarding - UE redirect

Originating UA (Voice Mail Playback)

SIP Proxy

Call Forwarding - S-CSCF redirect

3rd party call control AP

as a B2BUA (invite MRFC)

Play Announcements

Multiparty Call

Without AS

From: XTo: YCall-ID: Z

SIP leg #1


SIP leg #1S-CSCF

Application

Server


SIP

leg

#1

SIP

leg

#2

From: PTo: QCall-ID: R


SIP leg #1


SIP leg #2


SIP

leg

#1


SIP leg #1

SIP

leg

#1



SIP leg #1


SIP

leg

#1


SIP leg #1

SIP

leg

#1



SIP leg #1



S-CSCF & AS Interactions (1/5)

S-CSCF acts as a SIP Proxy


Redirect Server


S-CSCF

Application

Server


SIP

leg

#1


SIP leg #1






Redirect Server



S-CSCF

Application

Server

SIP

leg

#1



SIP leg #1



SIP

leg

#1



SIP leg #1




Redirect Server



SIP Proxy


S-CSCF

Application

Server


SIP

leg

#1


SIP leg #1






Redirect Server



SIP Proxy




Play Announcements for VM

Multiparty Call for Conference

S-CSCF

Application

Server


SIP

leg

#1

SIP

leg

#2



SIP leg #1


SIP leg #2






Redirect Server



SIP Proxy




Play Announcements

Multiparty Call

Without AS


SIP leg #1


SIP leg #1S-CSCF

Application

Server



Call Screening

S-CSCF

P-CSCF

GGSN

SGSN

Radio Access Network

I-CSCF

HSS App.

Server

3

1

2

Originating Home Network

Visited/Home

Network

S-CSCFI-CSCF

HSS

5 6

7

8

Terminating Home Network

4

P-CSCF

GGSN

SGSN


10

9

App.

Server

Originating Terminating

Visited/Home

Network



Call Forwarding (1/3)

Network configuration

S-CSCF based redirect

UE redirect call flow

S-CSCF

HSS

Home NetworkUE3

UE1

S-CSCF

I-CSCF S-CSCF

HSSI-CSCF

Home NetworkUE2

UE3

Application Servers

Home NetworkUE1

HSS

Application Servers

IM SSF

ISC

OSA SCS

SIP AS CSEOSA AS

Application Servers

OSA APIs CAP




UE redirect based call flows

HSS I-CSCF

Terminating UE3Home Network

Originating UE1Home Network

2. INVITE3. Locate UE2

4. Response

6. INVITE

10. 302 Moved Temporarily

Service Platform

Terminating UE2 Home Network

S-CSCF S-CSCF

5. INVITE


UE1

17. Bearer Establishment & Call Setup



Application performs number translation

(based on CLI)

15. INVITE

16. INVITE

. 1. INVITE

Redirect Mode

12. ACK 11. ACK

14. ACK

8. ACK




S-CSCF based redirect call flows

No AS involvement

I-CSCF HSS I-CSCF

Terminating UE3Home Network

Originating UE1Home Network

2. INVITE3. Locate UE24. Response

13b. 183 Session Progress13c. 183 Session Progress

13g. 183 Session Progress

11. S-CSCF UE3

10. Locate UE3

6. INVITE

7c. 181 Call Is Being Forwarded

9. INVITE

12a. INVITE

Service Platform

Terminating UE2 Home Network

S-CSCF S-CSCF

5. INVITE

7b. 181 Call Is Being Forwarded

S-CSCF

13f. 183 Session Progress

13e. 183 Session Progress

UE3

UE1

14. Bearer Establishment & Call Setup

7a. 181 Call Is Being Forwarded

7d. 181 Call Is Being Forwarded

Application performs number translation

(based on CLI)

12b. INVITE

13a. 183 Session Progress)

13h. 183 Session Progress

8 INVITEProxy Mode

HSS 1. INVITE

13d. 183 Session Progress



Voicemail Recording (1/3)

S-CSCF

P-CSCF

GGSN

SGSN


I-CSCF

HSS App.

Server

1

2

Originating Home Network

Visited/Home

Network

S-CSCFI-CSCF

HSS

4 5

6

9

Terminating Home Network

3

P-CSCF

GGSN

SGSN


App.

Server

Originating Terminating

Visited/Home

Network

87



Voicemail Recording (2/3) The HSS responds back to I-CSCF with an indication that

I-CSCF should select S-CSCF for this MT call to the

unregistered Public User Identity of the user or

provide the I-CSCF with the previously allocated

S-CSCF name.

I-CSCF HSS S-CSCF

Terminating Network

1. INVITE2. Cx-Loc Query

3. Cx-Loc Query Resp.

5. INVITE

6. Cx-Put/Cx-Pull

7. Cx-Put/Cx-Pull-Resp.

8. Service Control

4. S-CSCF Selection

9. S-CSCF performs further actions



Voicemail Recording (3/3)

AS (acting as a terminating UA)

S-

CSCF

AS (VoicemailServer) S-

CSCF

AS (VoicemailServer)

Voicemail Application

9. QOS Establishment / Resource Reservation

18. Voicemail Server Plays Annoncement

19. Caller Leaves Message



Voicemail Replaying (1/2)

P-SCSF

S-CSCF

P-CSCF

GGSN

SGSN


GGSN

SGSN


I-CSCF

HSS

3,5 4,6

7

10,118,9 12

11

22

Home Network

Visited Network

App.

ServerThird Party Registration



Voicemail Replaying (2/2)

2. 401 Unauthorized

15. QoS Establishment / Resource Reservation

AS (VoicemailServer) S-

CSCF

16. UPDATE

19. 200 OK

21. 180 Ringing

30. User retrieves voicemail messages



AS

ISC

S-CSCFMr

MRFC

MRFP

Mp

Gi

Multimedia Resource Function

MRFC (Multimedia Resource Function Controller) Control media stream resources in the MRFP

Interpret information from AS & S-CSCF, and

control MRFP accordingly

MRFP (Multimedia Resource Function Processor) Bearer control on Gi interface

Mixing of media streams

Media stream processing

Application Server~S-CSCF~MRFC

Announcement

Conferencing

Transcoding



Announcement (1/2)

AS

S-CSCF MRFC

Home Network for calling party

AS (acting as B2BUA)

3PCC with MRFC



Announcement (2/2)

PRACK

Provisional ack.

Allows preconditions

and other advanced

call setup features

UPDATE

Allows modification

of session without

full “re-invite

cycle”



Ad Hoc Conference (1/2)

AS (acting as B2BUA)

3PCC with MRFCMRFCAS


S-CSCF

1. INVITE (MPTY)[1]

4. Service Logic

3. INVITE (MPTY)[1]

13. 200 OK (UE-2 SDP)[3]

9. INVITE (UE-2 SDP)[3]


8. 200 OK (UE-2 SDP)[2]

14. ACK (UE-2 SDP) [2]

100 Trying is sent

after each INVITE,but it isn't shown


20. 200 OK (UE-3 SDP)[4]

Sessions exist between UE-1 and UE-2,

and between UE-1 and UE-3 .

Request is to put all parties together for an Ad-hoc conference (multi-party call).

16. ACK (UE-2 SDP) [3]

11. Establish path

between UE-2and MRFP

2. 100 (Trying)

17. ACK [3]


12. 200 OK (UE-2 SDP)[3]


21. 200 OK (UE-3 SDP)[4]


7. 200 OK (UE-2 SDP)[2]

15. ACK [2]



Ad Hoc Conference (2/2)

MRFCAS


S-CSCF

24. Establish path

between UE-3and MRFP

37. Establish pathbetween UE-1and MRFP

40. ACK [1]

41. ACK [1]

35. 200 OK (UE-1 SDP) [1]

36. 200 OK (UE-1 SDP) [1]

38. ACK [6]

26. 200 OK (UE-3 SDP)[5]


27. ACK (UE-3 SDP) [4]

29. ACK [5]


34. 200 OK (UE-1 SDP)[6]

39. ACK [6]


25. 200 OK (UE-3 SDP)[5]

28. ACK [4]

30. ACK [5]


33. 200 OK (UE-1 SDP)[6]



Reference for IM Call Model

3GPP TS 23.218 V6.3.0 (2005-03) IP Multimedia (IM) Session Handling;

IM Call Model;

Stage 2(Release 6)

The Intelligent Network :

Customizing Telecommunication Networks and Services

1998 by Uyless Black

Prentice-Hall PTR

Next Generation Intelligent Networks 2002 by Johan Zuidweg

Artech House



Summary

3GPP IM Call Model

Next Generation Intelligent Network will use

SIP-based Application/Service Triggering



Outline

3GPP IMS Call Model


S-CSCF & AS Interactions

Mobile Presence

Presence Service

3GPP & OMA Presence

Push-to-talk over Cellular

PoC Architecture and Operations

PoC High Level Procedures



Presence Service

The presence service (PS) results in presence information

of a user and information on a user's devices, services and

services components being managed by the wireless

network.

Together, user, these devices, services and services

components are termed presentity (presence entity)

The presence service provides access to presence

information to be made available to other users or services.

The types of services that could be supported by the

presence service

New communications services -"chat", instant messaging,

Information services - advanced push services

Enhanced existing services



Presence Information

Presence Information Usage information (Online/Offline/etc)

Availability information (Busy/Away/On lunch/etc)

Location information (At work/At home/etc)

Location information (Positioning/etc)

Device information (PC/PDA/Mobile phone/etc)

Network information & capabilities (WLAN/GPRS)

Preferred medium: text, e-mail, voice, video, …

Preferences (caller and callee preferences)

Presence Notifications about a person’s availability and

status sent directly to the recipient (not

stored)



Presentity

User Status Available

Not a vailable

Discreet

Invisib le

Location City

Coun try

Mark’s Presentity

Access Rules

My name is Mark and I am supported by the presence service. I have a presentity which represents me, and I am the principal of my presentity. As the principal, I supply

information to my presentity.

My presentity consists of information (describing my ability and willingness to communicate) and access rules (describing how my presence information

may be accessed).

Presentity presence info

user status

location info

set of access

rules



Application of Access Rules

User Status Available

Not a vailable

Discreet

Invisib le

Location City

Coun try

Mark’s Presentity

Paggy

Access Rules

Mark

Paul

Jude

…see you in the

bar at 7:30

…I think the car

alarm is playing up…

…shame, Mark can’t

tell me where Paul is

Hello, weather is

great here!

Watcher group

…looks like

Mark is not

around!



Peer-to-Peer

Client-to-Server

+ Network Info

Presence Operation Modes

PresenceServer

Watcher Presentity

Subscribe

Notify

Watcher Presentity

Subscribe

Notify

Publish

Presence Network Agent

HSS, HLR, VLR,

IMS CSCF

SGSN, GGSN

MSC, AAA Server

Register,

Invite (call state)



3GPP PS Architecture

Interfaces Ph, Pi, Pc, Pg, Pk and Pl are based on existing Release 5

procedures e.g. CAMEL, MAP, CAP, RADIUS, ISC, Cx, Sh.

The Pr, Pp interfaces are based on existing Release 6 procedures of

the 3GPP-WLAN interworking architecture.

PeuPresence User agent

(Presence information

provided by the user)

Presence Network agent (Presence

information provided by the

network)

Pen

Pi

MSC Server

/VLRSGSN GMLC

Ph Pc Pg

Presence suppliers

Presence server

(home network)

Presentity

Presence Proxy

Watcher

Presence Proxy

Watcher

applications

HSS

(HLR)Pw

Pw

Pw

Px

GGSNS-CSCFHSS/HLR

Pk Pl

Presence External agent (Presence

information provided by elements

outside the provider’s network)

Pex

Pr

3GPP AAA

Server

Pp

PDG

3GPP TS 23.141



PS Functional Entities

Presence Server (PS) The Presence Server shall reside in the

presentity's home network.

Presence User Agent (PUA) The Presence User Agent shall send the Presence

information to the Presence Server.

Presence Network Agent (PNA) The Presence Network Agent shall receive

Presence information from network elements

The Presence Network Agent shall be able to

send requests to the HSS/HLR

The Presence Network Agent shall publish the

Presence information to the Presence Server



Presence Proxies

Watcher

application

Px = Cx

P-CSCF S-CSCF

I-CSCF

S-CSCFPresence

Server

Presentity Presence

Proxy

HSS

Pw = ISC

Pw =Mw

Watcher Presence Proxy

Pw = Gm

Application

Server

(Presence

List)

ISC

Watcher

application

Pw = ISC



3GPP Presence Architecture

SIPPresence

Server

HSS

S-CSCF 1

P-CSCF 1

UE 1Watcher


Ph (MAP)

SIP

Pw ( ISC )

Pen

S-CSCF 2

P-CSCF 2

UE 2Presentity

SIP

Cx

Pi ( ISC )

Subscriber Controlled Info

(User Availability & Preference)

Network Controlled Info

(Location Info/Connectivity State)

I-CSCF 2

WatcherApplication

ApplicationServer

Pw ( ISC )

Watcher

Presence

Proxy

Presentity

Presence

Proxy

Presence

User Agent

UE1 Home Network UE2 Home Network

SIP



IMS Watcher Registering

The PS sends the NOTIFY straight to the originating watcher presence proxy, by-passing the presentity presence proxy.

Presentity Presence ProxyWatcher Presence Proxy

Home Network of watcher

UE P-CSCF

1.SubscribePres

S-CSCF

10.MsgAck11.MsgAck

12.MsgSck

14.NotifyPresUp15.NotifyPresUp

HSSPresence

Server

4. Query

5.Resp

8.MsgAck9.MsgAck

16.MsgAck 17.MsgAck18.MsgAck

13.NotifyPresUp

Home Network of presentity

I-CSCF S-CSCF

2.SubscribePres 3.SubscribePres

6.SubscribePres

7.SubscribePres



Updating Presence

UE

1. PressUpdateMsg

6. MsgAck

2. PressUpdateMsg

4.MsgAck

5.MsgAck

P-CSCF

Home Network of Presentity

S-CSCF

3. PressUpdateMsg

PresenceServer



Notifying IMS Watcher

Presence Server

has updates

presence

information to

send to watcher

as a result of

user or user

agent updates

Watcher Presence ProxyPresentity

Presence Proxy

S-CSCF

1. NotifyPresUp

Presence

Server

Home Network of Watcher

P-CSCFS-CSCF I-CSCF UE

3. NotifyPresUp

4. MsgAck

2. NotifyPresUp

5. MsgAck

6. MsgAck


The PS sends the NOTIFY straight to the originating watcher presence proxy, by-passing the presentity presence proxy.



Subscribing to Watcher List

subscription to the Presence Server requesting notification of any newwatcher subscriptions

If the UpdateSubscriptionAuthorisationPoliciesindicates that the subscription is blockedthen steps 9 and 10 are not performed.

inform the watcher that PS has received the watcher’s request.

PresenceUser Agent

1. SubscribePresence (Watcher List)

5.Watcher Request Notification

Presence Server

8. Update SubscriptionAuthorisationPolicies

9. NotifyPresUp

7. MsgAck

3. SubscribePres

PresentityPresence

Proxy

Watcher Presence

Proxy

4. SubscribePres

6. MsgAck

10. NotifyPresUp

2.MsgAcks



OMA PS Architecture

AC

CE

SS

NE

TW

OR

K

Pre

se

nce

Use

r A

gen

t

GLMS

SIP

/ I

P C

ore

Presence

Server

Rem

ote

Pre

se

nce N

etw

ork

(ba

se

d o

n a

SIP

/IP

Co

re)

Presence

Network

Agent

Presence

External

Agent

GLMS Management/Administration

GL

M C

lie

nt

UE

PRS-1 PRS -2

PRS -3

PRS -4

IP -1

GM-5

GM -3

GM-2

GM -4



Presence server

The Presence Server (PS) SHALL provide : Receive and manage presence information

Provide Subscription Authorization Policy

Provide a watcher, if required, configurable

filtering function that is used to limit the

information that is delivered to a watcher

Allow watchers to request and subscribe to the

full set of presence info of a presentity

Generates partial notifications to a watcher

Verifies the identity of the watcher that

subscribes to presentity's presence info

Supports SIP-based communications with the

Presentity SIP/IP Core



Presence User Agent

The Presence User Agent (PUA) collects presence info

associated with a presentity representing a principal

Assemble the presence info in the standard format

Send the presence information to the PS

Manage the Subscription Authorisation Policy

Identify itself uniquely among other PUAs of the same

presentity when publishing presence information

Handle any necessary interworking required to support

terminals that do not support the standard interface

The PUA may be located in the user’s terminal or

within a network entity



Presence Network

Agent

3GPP

HSS/HLRS-CSCF

MSC Server/VLR

SGSN

GGSN

GMLC


The Presence Network Agent (PNA) SHALL collect the

presence information from the various network elements

and send it to the PS.

The PNA MAY also notify the PS when a PUA is

disconnected. This can be achieved by using keep-alives

(heartbeat) mechanism from the PUA to the PNA.

Presence NetworkAgent

3GPP2

HSS/HLRS-CSCF

MSC/MSCe

AAA/HA/

PDSN

Position

Server



SIP/IP Core

Routes the SIP signaling between PUA and PS

Provides discovery & address resolution

services

Supports SIP compression

Performs authentication and authorization of

the PUA based on user’s service profile

Maintains the registration state

Provides charging information

OMA SIP/IP Core = 3GPP Presence Proxies



GLMS

Group and List Management Server (GLMS )

Provides list management operations to create,

modify, retrieve and delete groups and lists

Provides storage for groups and lists



PS General Architecture

PresenceServer

SIP/IP CoreWatcher

PresentityWatcher

SIP/IP CorePresentity

S-CSCF 1

P-CSCF 1

S-CSCF 2

P-CSCF 2

I-CSCF 2

UE 1Watcher

UE 2Presentity

Presence

User Agent



Publishing Presence Info

PUA

1. PUBLISH

4. 200 OK

Home Network of

2. PUBLISH

PS

Serve

r

SIP/IP Core

3.200 OK

PUA

1. PUBLISH

4. 200 OK


2. PUBLISH

Serve

r

SIP/IP Core

3.200 OK



Sending a Subscribe Request

Presentity SIP/IP CoreWatcher SIP/IP Core


PUA

Presence

9. 200 OK

7. NOTIFY


8. NOTIFY

10. 200 OK



Watcher

1. SUBSCRIBE

PS

4. 200 OK

9. 200 OK

7. NOTIFY


5. 200 OK

6. 200 OK

8. NOTIFY

10. 200 OK

2. SUBSCRIBE 3. SUBSCRIBE



PUA

Presence

9. 200 OK

7. NOTIFY


8. NOTIFY

10. 200 OK

Presentity SIP/IP CorePresentity SIP/IP CoreWatcher SIP/IP Core


Watcher

1. SUBSCRIBE

PS

4. 200 OK

9. 200 OK

7. NOTIFY


5. 200 OK

6. 200 OK

8. NOTIFY

10. 200 OK

2. SUBSCRIBE 3. SUBSCRIBE



Receiving a Notification

Presentity

SIP/IP Core

Home Network ofPresentity

1. NOTIFY

Presence Server


2. NOTIFY

3. 200 OK

4. 200 OK

Presence Server

has updates to

send to the

watcher

Watcher

SIP/IP Core

Presentity

SIP/IP Core

Presentity

SIP/IP Core


1. NOTIFY

PS


2. NOTIFY

3. 200 OK

4. 200 OK

Presence Server

has updates to

send to the

watcher

Watcher

SIP/IP CoreWatcher

Presentity

SIP/IP Core


1. NOTIFY

Presence Server


2. NOTIFY

3. 200 OK

4. 200 OK

Presence Server

has updates to

send to the

watcher

Watcher

SIP/IP Core

Presentity

SIP/IP Core

Presentity

SIP/IP Core

Presentity

SIP/IP Core

Presentity

SIP/IP Core


1. NOTIFY

PS


2. NOTIFY

3. 200 OK

4. 200 OK

Presence Server

has updates to

send to the

watcher

Watcher

SIP/IP CoreWatcher



Partial Notifications

Watcher

1. SUBSCRIBE

2. SUBSCRIBE

SIP/IP Core

3.200 OK

PU

5. NOTIFY

6. NOTIFY

9. PUBLISH

11. NOTIFY

12. NOTIFY

7. 200 OK

8. 200 OK

13. 200 OK14. 200 OK

10. 200 OK

Watcher

1. SUBSCRIBE

2. SUBSCRIBE

SIP/IP CorePUA

9. PUBLISH


Watcher

1. SUBSCRIBE

4.200 OK

2. SUBSCRIBE

SIP/IP CorePU

5. NOTIFY

6. NOTIFY

9. PUBLISH

11. NOTIFY

12. NOTIFY

7. 200 OK

8. 200 OK

13. 200 OK14. 200 OK

10. 200 OK

Watcher

1. SUBSCRIBE

2. SUBSCRIBE

SIP/IP CorePUA

9. PUBLISH


PSWatcher

1. SUBSCRIBE

2. SUBSCRIBE

SIP/IP Core

3.200 OK

PU

5. NOTIFY

6. NOTIFY

9. PUBLISH

11. NOTIFY

12. NOTIFY

7. 200 OK

8. 200 OK

13. 200 OK14. 200 OK

10. 200 OK

Watcher

1. SUBSCRIBE

2. SUBSCRIBE

SIP/IP CorePUA

9. PUBLISH


Watcher

1. SUBSCRIBE

4.200 OK

2. SUBSCRIBE

SIP/IP CorePU

5. NOTIFY

6. NOTIFY

9. PUBLISH

11. NOTIFY

12. NOTIFY

7. 200 OK

8. 200 OK

13. 200 OK14. 200 OK

10. 200 OK

Watcher

1. SUBSCRIBE

2. SUBSCRIBE

SIP/IP CorePUA

9. PUBLISH


PS

a partial presence document formulated showing only the changed tuple.

full state presence document



Subscribe Presence

8. NOTIFY

9. NOTIFY

10. 200 OK.

11. 200 OK.

12. NOTIFY

13. NOTIFY

14. 200 OK

15. 200 OK



PUA

1. SUBSCRIBE

2. SUBSCRIBEs

Presence Server

5 200 OK


3. SUBSCRIBEs

7. 200 OK



1. SUBSCRIBE

2. SUBSCRIBEs

Presence Server


3. SUBSCRIBEs

Watcher

Presence Server has updates to send to the watcher

4 Authorization

6. 200 OK

8. NOTIFY

9. NOTIFY

10. 200 OK.

11. 200 OK.

12. NOTIFY

13. NOTIFY

14. 200 OK

15. 200 OK



PUA

1. SUBSCRIBE

2. SUBSCRIBEs

Presence Server

5 200 OK


3. SUBSCRIBEs

7. 200 OK

Presentity SIP/IP CorePresentity SIP/IP CoreWatcher SIP/IP Core


1. SUBSCRIBE

2. SUBSCRIBEs

Presence Server


3. SUBSCRIBEs

Watcher

Presence Server has updates to send to the watcher

4 Authorization4 Authorization4 Authorization

6. 200 OK

The PS sends the NOTIFY straight to the originating watcher SIP/IP core, by-passing the presentity SIP/IP core.



Blocking

SIP/IP Core


WatcherPresence

Server

1. SUBSCRIBE

2. SUBSCRIBE

3. 403 Forbidden or 603 Decline


SIP/IP CoreSIP/IP Core


Watcher PS

1. SUBSCRIBE

2. SUBSCRIBE



SIP/IP Core


WatcherPresence

Server

1. SUBSCRIBE

2. SUBSCRIBE





Watcher PS

1. SUBSCRIBE

2. SUBSCRIBE





Polite Blocking

SIP/IP Core


Watcher

1. SUBSCRIBE

2. SUBSCRIBE

4. 200 OK

5. NOTIFY

6. NOTIFY

7. 200 OK

8. 200 OK



Watcher

1. SUBSCRIBE

2. SUBSCRIBE

3. 200 OK

5. NOTIFY

6. NOTIFY

7. 200 OK

8. 200 OK

SIP/IP Core


Watcher

1. SUBSCRIBE

2. SUBSCRIBE

4. 200 OK

5. NOTIFY

6. NOTIFY

7. 200 OK

8. 200 OK



Watcher

1. SUBSCRIBE

2. SUBSCRIBE

3. 200 OK

5. NOTIFY

6. NOTIFY

7. 200 OK

8. 200 OK

PSSIP/IP Core


Watcher

1. SUBSCRIBE

2. SUBSCRIBE

4. 200 OK

5. NOTIFY

6. NOTIFY

7. 200 OK

8. 200 OK



Watcher

1. SUBSCRIBE

2. SUBSCRIBE

3. 200 OK

5. NOTIFY

6. NOTIFY

7. 200 OK

8. 200 OK

SIP/IP Core


Watcher

1. SUBSCRIBE

2. SUBSCRIBE

4. 200 OK

5. NOTIFY

6. NOTIFY

7. 200 OK

8. 200 OK



Watcher

1. SUBSCRIBE

2. SUBSCRIBE

3. 200 OK

5. NOTIFY

6. NOTIFY

7. 200 OK

8. 200 OK

PS

After applying the subscription authorization policies of the presentity, the PS determines to reject the subscription request



Watcher Initiated Canceling

7. 200 OK

Watcher

1. SUBSCRIBE

3. 200 OK

5. NOTIFY

4. 200 OK

6. NOTIFY

8. 200 OK

2. SUBSCRIBE


SIP/IP Core PS

7. 200 OK

Watcher

1. SUBSCRIBE

3. 200 OK

5. NOTIFY

4. 200 OK

6. NOTIFY

8. 200 OK

2. SUBSCRIBE


SIP/IP Core PS

“Expires” header field set to 0

“Subscription-State” header field set to “terminated”



PS Initiated Canceling

3. 200 OK

1. NOTIFY

2. NOTIFY

4. 200 OK

Watcher


SIP/IP Core PS

3. 200 OK

1. NOTIFY

2. NOTIFY

4. 200 OK

Watcher


SIP/IP Core PS

“Subscription-State” header field set to “terminated”



Subscribing Watcher Info

Watcher


SIP/IP CorePUA

1. SUBSCRIBE

3. NOTIFY

4. 200 OK

Watcher



SIP/IP CorePUA

1. SUBSCRIBE

2. 200 OK

3. NOTIFY

4. 200 OK

8. 202 Accepted

11.Subscription Authorisation

Watcher


SIP/IP CorePUA

1. SUBSCRIBE

3. NOTIFY

4. 200 OK

Watcher



SIP/IP CorePUA

1. SUBSCRIBE

3. NOTIFY

4. 200 OK

11.200 OK

13. NOTIFY

7. 202 Accepted

14. 200 OK

8. 202 Accepted


20. NOTIFY

16. NOTIFY

9. NOTIFY

10. NOTIFY

12.200 OK

17. NOTIFY

18.200 OK19.200 OK

21 200 OK

Watcher


SIP/IP CorePUA

1. SUBSCRIBE

3. NOTIFY

4. 200 OK

Watcher



SIP/IP CorePUA

1. SUBSCRIBE

2. 200 OK

3. NOTIFY

4. 200 OK

8. 202 Accepted


Watcher


SIP/IP CorePUA

1. SUBSCRIBE

3. NOTIFY

4. 200 OK

Watcher



SIP/IP CorePUA

1. SUBSCRIBE

3. NOTIFY

4. 200 OK

11.200 OK

13. NOTIFY

7. 202 Accepted

14. 200 OK

8. 202 Accepted


20. NOTIFY

16. NOTIFY

9. NOTIFY

10. NOTIFY

12.200 OK

17. NOTIFY

18.200 OK19.200 OK

21 200 OK

PSWatcher


SIP/IP CorePUA

1. SUBSCRIBE

3. NOTIFY

4. 200 OK

Watcher



SIP/IP CorePUA

1. SUBSCRIBE

2. 200 OK

3. NOTIFY

4. 200 OK

8. 202 Accepted


Watcher


SIP/IP CorePUA

1. SUBSCRIBE

3. NOTIFY

4. 200 OK

Watcher



SIP/IP CorePUA

1. SUBSCRIBE

3. NOTIFY

4. 200 OK

11.200 OK

13. NOTIFY

7. 202 Accepted

14. 200 OK

8. 202 Accepted


20. NOTIFY

16. NOTIFY

9. NOTIFY

10. NOTIFY

12.200 OK

17. NOTIFY

18.200 OK19.200 OK

21 200 OK

Watcher


SIP/IP CorePUA

1. SUBSCRIBE

3. NOTIFY

4. 200 OK

Watcher



SIP/IP CorePUA

1. SUBSCRIBE

2. 200 OK

3. NOTIFY

4. 200 OK

8. 202 Accepted


Watcher


SIP/IP CorePUA

1. SUBSCRIBE

3. NOTIFY

4. 200 OK

Watcher



SIP/IP CorePUA

1. SUBSCRIBE

3. NOTIFY

4. 200 OK

11.200 OK

13. NOTIFY

7. 202 Accepted

14. 200 OK

8. 202 Accepted


20. NOTIFY

16. NOTIFY

9. NOTIFY

10. NOTIFY

12.200 OK

17. NOTIFY

18.200 OK19.200 OK

21 200 OK

PS

SUBSCRIBE

SUBSCRIBE

After some time a Watcher attempts to subscribe to the PUA’s Presence info by sending a SUBSCRIBE message

NOTIFY with “Subscription-State" of "pending" value, which indicates that the subscription has been received, but that policy info is insufficient to accept/ deny the Subscription at this time.

authorizes the subscription

Notify the change in status of subscription (changes from pending to active)



Aggregating Presence Info

Aggregating Published Presence information from multiple sources

PUA1

1. PUBLISH

Home Network of Presentit

y

PS SIP/IP Core

4. 200 OK


2. PUBLISH

3. 200 OK

PUA2

5. PUBLISH

8. 200 OK

6. PUBLISH

7. 200 OK

Watcher

10. NOTIFY 9. NOTIFY

11. 200 OK 12. 200 OK



References for Presence (1/2)

3GPP TS 22.141 V6.2.1 (2004-07) Presence Service;

Stage 1(Release 6)

3GPP TS 23.141 V6.6.0 (2004-06) Presence Service;

Architecture & functional description (Release 6)

Stage 2 - Presence using SIMPLE Draft Version 1.0 – 02 August 2004

OMA-PAG-SIMPLE-AD-V1_1_0-20040802-D

Push-to-talk over Cellular (PoC) - Presence Service; PoC Release 2.0

Presence Service V2.0.9 (2004-06)

Comneon, Ericsson, Motorola, Nokia, Siemens



References for Presence (2/2)

CCL Technical Journal

3GPP Mobile Presence: September 2003

OMA-Open Mobile Alliance/Wireless Village

http://www.openmobilealliance.org/wirelessvillage/

Jabber Software Foundation,The Jabber Protocol

http://www.jabber.org/protocol/

IETF IMPP (Instant Messaging and Presence Protocol)

IETF SIMPLE (SIP for Instant Messaging and Presence

Leveraging Extensions)

IETF XMPP (Extensible Messaging and Presence Protocol)



Summary

3GPP/OMA Mobile Presence Service

Maybe to be a Killer Service Platform

Integration of other VAS (PoC, LBS, MMS)

Mobile All-IP Networking LaboratoryDepartment of Computer Science & Information Engineering

Any Question?


3GPP IM Call Model and Presence

Documents