national chung cheng university 3gpp im call model

National Chung Cheng University

3GPP IM Call Model, Presence, and

P h t t lk C ll l Push-to-talk over Cellular

Chiang, Wei-Kuo (江為國)Assistant Professor Assistant Professor Department of CSIE National Chung Cheng University Office : EA 311 Office : EA 311 Phone : 05-2720411~33126 Email : [email protected] : http://www cs ccu edu tw/~wkchiang/

National Chung Cheng UniversityDept. Computer Science & Information Engineering

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


N t G ti N t kNext Generation Networkl i l i iInternet Telecom & Wireless Communication

GPRS

CSCF

3rd Parties App.

CSCF

WLAN

CSCFSIP

ServerInternetWireless App.

Server

MGCF

WLAN

IPT-SGW MGWMGW

PSTN

Telecom Service Integration for ITS IMS Services2

PSTN


O tliOutline

3GPP IMS Call ModelApplication TriggeringApplication Triggering

S-CSCF & AS Interactions

M bil PMobile PresencePresence Service

3GPP & OMA Presence

Push-to-talk over CellularPush to talk over CellularPoC Architecture and Operations

P C Hi h L l P d


PoC High Level Procedures


IMS S i A hit tIMS Service ArchitectureApplication ServersSh

MAPCSE OSA AS

AS ASCAP OSA APIs

MEGACOSi

OSA SCSIM-SSF SIP ASHSS MRFCSCIM

SIP+Cx MEGACOSIP+MRFP

Voice PacketsRTP

Incoming Leg Outgoing Leg

OLCMILCM

Incoming LegState Machine

Ougoing LegState Machine

Model

S i CSCF

Call Records

Registrar and Notifier


Serving CSCF


A li ti S TApplication Server TypesSIP AS

SIP-based Application ServersE lExamples

Presence Server (3GPP TS 23.141)PoC Server (3GPP TR 23 979)PoC Server (3GPP TR 23.979)

IM-SSFIP Multimedia Service Switching FunctionIP Multimedia - Service Switching FunctionHost the CAMEL network features (3GPP TS 23.278)

OSA SCSOSA SCSOpen Service Access Service Capability ServerUse the OSA API (3GPP TR 29.998)


Use the OSA API (3GPP TR 29.998)


A li ti T i iApplication Triggering

Application Server

Service Logic

Service Platform Trigger PointsService Platform Trigger Points

SIP I t fHSS

SIP Interface

sFC SIP iFC

S - CSCF

SS P T P

Filter Criteria SIPSIP



S i P i t T iService Point TriggerService Point Triggers (SPTs)

SPTs are those points in the SIP signalling on which Filter Criteria can be setwhich 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 fieldPresence or absence of some header fieldContent of some header field or Request-URIDirection of the request w.r.t. the served user

Mobile Originated (MO)Mobile Terminated (MT)

R i t d/ U i t d


Registered/ Unregistered users


Filt C it iFilter CriteriaFil C i i (FC)Filter Criteria (FC)

A FC triggers one or more SPTs in order to send the related request to one specific app server. q p ppThe set of Filter Criteria that is stored for a service profile of a specific user.

iFC (initial Filter Criteria) S CSCF receives from HSSiFC (initial Filter Criteria) - S-CSCF receives from HSSsFC (subsequent Filter Criteria) - S-CSCF receives from AS

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

FCs Contain the following informationAddress of Application ServerPriority of Filter CriteriaPriority of Filter CriteriaTrigger Point : composed by 1 to n SPTsDefault handlingO ti l S i I f ti ( IMSI)


Optional Service Information (e.g. IMSI)


S CSCF f iFCS-CSCF for iFCiFC 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 ti f REGISTER tS-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 ti f th t S-CSCF on reception of any other request 1)Set up filter criteria list by priority for that request2)Parse the received request in order to find out the SPTs3)Check with trigger points of unchecked highest priority FC) gg p g p y

If not match, S-CSCF proceed with step 4If match, S-CSCF shall

Add an indication to the requestForward the request to the AS The AS then performs the Forward the request to the AS. The AS then performs the service logic and may send the request back to the S-CSCFProceed 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


T i i f REGISTERTriggering for REGISTER

1. Inform about the user i t ti t

Download iFCregistration event

2. Trigger services

From: UserAT U A

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

HSS

2 Cx

1. SIP REGISTER

3 SIP 200 OK

To: User ACall-ID: X

S-CSCF ApplicationServer

5.SIP REGISTER

Call-ID: Z

6. SIP 200 OK

2. Cx

4 Filter Checking

Contact: S-CSCF

3. SIP 200 OKFrom: UserATo: User ACall-ID: X

6. SIP 200 OK4. Filter Checking

Match a trigger



T i i f INVITETriggering for INVITE

HSSSh Sh

AS 1 AS 2Cx

SIPInterface

Service Logic

Service Logic

SIP Interface

Outgoing Call legIncoming Call leg

ISC ISC

1

2 3 SIP message possiblywith modification by AS1

SPI

4.a

INVITE Match Initial Filter CriteriaS-CSCF

5a SIP message possiblywith modification by AS2

1

4 b

IFilter Criteria X -> AS1Filter Criteria Y -> AS2

6a


4.bSIP message forwarded by S-CSCF SIP message forwarded by S-CSCF


E l ti ( / )Explanation (1/2)This example applies both for call originating and terminating procedure. But we assume this is a call originating procedure. 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 Cxinterface. Also, the application server specific data may have been downloaded via the Sh interface to the have been downloaded via the Sh interface to the application server during registration.In this example, two application servers are assigned to p , pp gprovide additional services to a subscriber and they are showed as AS1 & AS2.



E l ti ( / )Explanation (2/2)b d1. 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 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 d th SIP t ibl ith i l t d difi ti b k t th 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


criteria is matched, then the S-CSCF forwards this request to next hop based on the route decision.


S CSCF F ti l M d lS-CSCF Functional ModelCombined I/OLSM

Incoming/Outgoing Leg State ModelStore session state infoActing as a SIP Proxy, Redirect Server or User Agent

dependant on the info received in the SIP+HSS

ApplicationServer

dependant on the info received in the SIP request, the filter conditions specified or the state of the session

ILCM and OLCM OLCMILCM

Cx

ILCM and OLCM Incoming/Outgoing Leg Control ModelStore transaction state info

R i t d N tifiRegistrar and

Incoming LegState Machine

Ougoing LegState Machine

Registrar and Notifierhandles registration & subscription to and notification of registration

Model

Serving CSCF

Notifier


events


AS F ti l M d lAS Functional ModelAS-ILCM

shall store transaction statemay optionally store sessionmay optionally store session state

depending on the specific i b i t d

Application Server

Application Logicservice being executed.

interfaces to the S-CSCF (ILCM) for an incoming leg.

AS-OLCMAS-ILCM

Sh/Si

AS-OLCMSimilar to AS-ILCM

li i iSIP+

Cx

HSS

Application Logiccan access the HSS via the Sh or Si interface to access

Cx

S-CSCF


subscriber related data


S CSCF & AS I t tiS-CSCF & AS InteractionsS CSCF acts as a SIP ProxyS-CSCF acts as a SIP ProxyApplication Server acts as

Terminating User Agent (Voice Mail) orTerminating User Agent (Voice Mail) or

Redirect Server Call Forwarding - UE redirect Application

Originating UA (Voice Mail Playback)

SIP Proxy

Server

From: XSIP leg

SIP leg

From: PTo: QCall ID: RFrom: X

SIP leg

SIP leg

From: XTo: YCall ID: ZFrom: X

SIP leg

SIP leg

From: XTo: YCall ID: ZCall Forwarding - S-CSCF redirect

3rd party call control APas a B2BUA (invite MRFC)

To: YCall-ID: Z

leg #1

leg #2

Call-ID: RTo: YCall-ID: Z

g#1

leg #1

Call-ID: ZTo: YCall-ID: Z

leg #1

leg #1

Call-ID: Z

( )Play AnnouncementsMultiparty Call

Without ASFrom: XTo: YCall-ID: Z

SIP leg #1

From: XTo: YCall-ID: Z

SIP leg #1S-CSCF


SIP leg #1

From: PTo: QCall-ID: R

SIP leg #2


SIP leg #1


SIP leg #1


SIP leg #1


SIP leg #1


Without AS


S CSCF & AS S-CSCF & AS Interactions (1/5)

S CSCF acts as a SIP ProxyS-CSCF acts as a SIP ProxyApplication Server acts as



Server

From: XSIP leg

To: YCall-ID: Z

g#1

S-CSCF


SIP leg #1







Originating UA (Voice Mail Playback) Server

SIP leg

From: XTo: YCall ID: Zleg

#1Call-ID: Z

S-CSCF


SIP leg #1







SIP leg

From: XTo: YCall ID: Z


SIP Proxy

Server

From: XSIP leg leg

#1Call-ID: ZCall Forwarding - S-CSCF redirect To: Y

Call-ID: Z

g#1


SIP leg #1S-CSCF


SIP leg #1








SIP Proxy

Server

From: XSIP leg

SIP leg

From: PTo: QCall ID: RCall Forwarding - S-CSCF redirect

3rd party call control APas a B2BUA (invite MRFC)

To: YCall-ID: Z

leg #1

leg #2

Call-ID: R

( )Play Announcements for VMMultiparty Call for Conference

S-CSCF


SIP leg #1

From: PTo: QCall-ID: R

SIP leg #2








SIP Proxy

Server

Call Forwarding - S-CSCF redirect3rd party call control AP

as a B2BUA (invite MRFC)( )Play AnnouncementsMultiparty Call

Without ASFrom: XTo: YCall-ID: Z

SIP leg #1


SIP leg #1S-CSCF


Without AS


C ll S i Call Screening

HSS App.Server

Originating Home Network

HSS

Terminating Home Network

App.ServerServer

3 5 6 8

Server

S-CSCFI-CSCF

2Vi it d/H

S-CSCFI-CSCF 74

9

P-CSCF

1

Visited/HomeNetwork P-CSCF

10

Visited/HomeNetwork

GGSNGGSNSGSNSGSN

Radio Access NetworkRadio Access Network

GGSNGGSNSGSNSGSN



Originating Terminating


C ll F di ( / )Call Forwarding (1/3)Network configuration

SIP AS CSEOSA AS

Application Servers

S-CSCF based redirect UE redirect call flow IM SSFOSA SCS

SIP AS CSEOSA ASOSA APIs CAP

S-CSCF

HSS Application Servers

ISC

HSS

I-CSCF S-CSCF

HSSI-CSCF

Home NetworkUE2HSS

Application Servers

Home NetworkUE3S-CSCF

UE3Home Network

UE1

Telecom Service Integration for ITS IMS Services23UE1

UE3


C ll F di ( / )Call Forwarding (2/3)UE redirect based call flows

Terminating UE3Home Network

Originating UE1Home Network

Terminating UE2 Home Network

HSS I-CSCF

2. INVITE3. Locate UE24. Response

6. INVITE

Service Platform

S-CSCF S-CSCF

5. INVITE

UE1. 1. INVITE

6. INVITE

9 302 M d T il

7. 302 Moved Temporarily

Application performs number translation

(based on CLI)

R di t M d8. ACK

10. 302 Moved Temporarily9. 302 Moved Temporarily

13. 302 Moved Temporarily

Redirect Mode

12. ACK 11. ACK

14. ACK

17. Bearer Establishment & Call Setup

15. INVITE16. INVITE


p


C ll F di ( / )Call Forwarding (3/3)S-CSCF based redirect call flows

I-CSCF HSS I-CSCF

Terminating UE3Home Network

Originating UE1Home Network

Service Platform

Terminating UE2 Home Network

S-CSCF S-CSCF S-CSCF HSS 1 INVITE2. INVITE3. Locate UE2

4. Response

6. INVITE

Platform

5. INVITE

UE1

7a 181 Call Is Being ForwardedApplication performs

number translation (b d CLI)

1. INVITE

10. Locate UE3

7c. 181 Call Is Being Forwarded

9. INVITE

7b. 181 Call Is Being Forwarded7a. 181 Call Is Being Forwarded

7d. 181 Call Is Being Forwarded

(based on CLI)

8 INVITEProxy Mode

No AS involvement

13b. 183 Session Progress

11. S-CSCF UE312a. INVITEUE3

12b. INVITE13a. 183 Session Progress)

g13c. 183 Session Progress

13g. 183 Session Progress13f. 183 Session Progress

13e. 183 Session Progress

13h 183 S i P

13d. 183 Session Progress

Telecom Service Integration for ITS IMS Services2514. Bearer Establishment & Call Setup

13h. 183 Session Progress


V i il R di ( / )Voicemail Recording (1/3)

HSS App.Server

Originating Home Network

HSS

Terminating Home Network

App.ServerServer

4 5 9

Server

87

S-CSCFI-CSCF

2Vi it d/H

S-CSCFI-CSCF 63

P-CSCF

1

Visited/HomeNetwork P-CSCF

Visited/HomeNetwork

GGSNGGSNSGSNSGSN


GGSNGGSNSGSNSGSN



Originating Terminating


V i il R di ( / )Voicemail Recording (2/3)The HSS responds back to I CSCF with an indication that 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.

S CSCTerminating Network

I-CSCF HSS S-CSCF1. INVITE

2. Cx-Loc Query3. Cx-Loc Query Resp.

5. INVITE

6. Cx-Put/Cx-Pull

4. S-CSCF Selection

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

8. Service Control


9. S-CSCF performs further actions


V i il R di ( / )Voicemail Recording (3/3)AS (acting as a terminating UA)

S-AS (VoicemailS ) S-

AS (VoicemailS )S

CSCFServer) S-CSCF

Server)

Voicemail ApplicationVoicemail Application

18. Voicemail Server Plays Annoncement

9 QOS Establishment / Resource Reservation

19. Caller Leaves Message

9. QOS Establishment / Resource Reservation



V i il R l i ( / )Voicemail Replaying (1/2)

HSS

Home Network

App.Server

Thi d Pa t Regist ation

3,5 4,6 10,118,9 12

Third Party Registration

S-CSCFI-CSCF 7

22

P-SCSFP-CSCF

11

Visited Network

GGSNGGSNSGSNSGSN


GGSNGGSNSGSNSGSN




V i il R l i ( / )Voicemail Replaying (2/2)AS (Voicemail

Server) S-CSCF

16. UPDATE

2. 401 Unauthorized 19. 200 OK

21. 180 Ringing

30 U t i i il

15. QoS Establishment / Resource Reservation

30. User retrieves voicemail messages



l i di iMultimedia Resource FunctionMRFC (Multimedia Resource Function Controller)MRFC (Multimedia Resource Function Controller)

Control media stream resources in the MRFPInterpret information from AS & S-CSCF, and pcontrol MRFP accordingly

MRFP (Multimedia Resource Function Processor)

AS

Bearer control on Gi interfaceMixing of media streamsMedia stream processing

ISC

S-CSCFMr

MRFC

Media stream processing

Application Server~S-CSCF~MRFCAnnouncement

MRFP

Mp

Gi

ConferencingTranscoding


Gi


A t ( / )Announcement (1/2)AS (acting as B2BUA)

3PCC with MRFC

Home Network for calling party

AS

S-CSCF MRFC



A t ( / )Announcement (2/2)

PRACKProvisional ack.

Allows preconditions and other advanced call setup features

UPDATEAllows modification of session without full “re-invite cycle”



Ad H C f ( / )Ad Hoc Conference (1/2)AS (acting as B2BUA)

3PCC with MRFCMRFCAS

Home Network for calling partyS-CSCFSessions exist between UE-1 and UE-2 MRFCAS S CSCF

1. INVITE (MPTY)[1]

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).

2. 100 (Trying)

4. Service Logic

3. INVITE (MPTY)[1]

5. INVITE (UE-2 SDP)[2]

8 200 OK (UE 2 SDP)[2]

100 Trying is sentafter each INVITE,but it isn't shown 6. INVITE (UE-2 SDP)[2]

7 200 OK (UE 2 SDP)[2]

13 200 OK (UE 2 SDP)[3]


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

11. Establish pathbetween UE-2and MRFP


12 200 OK (UE 2 SDP)[3]

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

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

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


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

and MRFP

17. ACK [3]

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


15. ACK [2]


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


Ad H C f ( / )Ad Hoc Conference (2/2)

MRFCAS

Home Network for calling party

S-CSCF


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

22. INVITE (UE-3 SDP)[5] 23. INVITE (UE-3 SDP)[5]

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

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

29. ACK [5]


28. ACK [4]

30. ACK [5]


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

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

38. ACK [6]

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

39. ACK [6]

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


40. ACK [1]

41. ACK [1]

38. ACK [6] [ ]



R f f IM C ll M d lReference for IM Call Model3GPP TS 23 218 V6 3 0 (2005 03)3GPP TS 23.218 V6.3.0 (2005-03)

IP Multimedia (IM) Session Handling;

IM C ll M d lIM Call Model;

Stage 2(Release 6)

The Intelligent Network :The Intelligent Network :Customizing Telecommunication Networks and Services

1998 by Uyless Black

Prentice-Hall PTR

N t G ti I t lli t N t kNext Generation Intelligent Networks2002 by Johan Zuidweg

A t h H


Artech House


SSummary

3GPP IM Call ModelNext Generation Intelligent Network will use SIP-based Application/Service Triggering



O tliOutline




3GPP & OMA Presence


P C Hi h L l P d




P S iPresence ServiceThe 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 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 servicesinformation to be made available to other users or services.The types of services that could be supported by the presence servicep

New communications services -"chat", instant messaging,

Information services - advanced push services


Enhanced existing services


P I f tiPresence InformationPresence Information

Usage information (Online/Offline/etc)Availability information (Busy/Away/On lunch/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 videoPreferred medium: text, e-mail, voice, video, …Preferences (caller and callee preferences)

PresencePresenceNotifications about a person’s availability and status sent directly to the recipient (not


stored)


P titPresentityP i

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

Presentitypresence info

user status p p p ypresentity. As the principal, I supply information to my presentity.

user status location info

set of access rules

User StatusAvailable

DiscreetAccess Rules

rules

Not available

Invisible

LocationCity

My presentity consists of information (describing my ability and willingness to

i t ) d Country

Mark’s Presentity

communicate) and access rules (describing how my presence information may be accessed).



A li ti f A R lApplication of Access Rules

Paggy …see you in the

…I think the car alarm is playing up…

Hello, weather is great here!

User StatusAvailable

Access

Mark

Paul

ybar at 7:30

Not available

Discreet

Invisible

LocationCity

Access Rules

Paul

Locationy

Country

Mark’s PresentityJude

…shame, Mark can’t tell me where Paul is

Watcher group…looks like Mark is not

d!


around!


P O ti M dPresence Operation ModesPeer-to-Peer

Watcher Presentity

Subscribe

Client-to-ServerPresence

Notify

PresenceServerSubscribe

Notify

Publish

+ Network Info

Watcher Presentity

Presence Network InfoNetwork Agent

HSS, HLR, VLR, IMS CSCFSGSN, GGSN

Register,Invite (call state)


SGS , GGSMSC, AAA Server


GPP PS A hit t3GPP PS Architecture

Presence suppliers Watcher applications

PwPresence External agent (Presence Pex

P U t

Watcher Presence Proxy

Pw

Presence External agent (Presence information provided by elements

outside the provider’s network)

PeuPresence User agent (Presence information provided by the user)

P N t k t (PPen

Presentity Presence Proxy

HSS

Pw

Px

Presence Network agent (Presence information provided by the

network)

PiPh Pc Pg Presence server

(HLR)Pw

Pk PlPr Pp

Interfaces Ph, Pi, Pc, Pg, Pk and Pl are based on existing Release 5procedures e.g. CAMEL, MAP, CAP, RADIUS, ISC, Cx, Sh.

MSC Server/VLR SGSN GMLC

(home network)GGSNS-CSCFHSS/HLR

3GPP AAA Server PDG

3GPP TS 23 141


The Pr, Pp interfaces are based on existing Release 6 procedures of the 3GPP-WLAN interworking architecture.

3GPP TS 23.141


PS F ti l E titiPS Functional EntitiesP S (PS)Presence Server (PS)

The Presence Server shall reside in the presentity's home network.p y

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 gsend requests to the HSS/HLRThe Presence Network Agent shall publish the Presence information to the Presence Server



P P iPresence Proxies

Watcher P-CSCF S-CSCFPw = Gm

Application Server

(Presence List)

ISC

applicationP CSCF S CSCF

Watcher Presence Proxy

List)

W h

Pw = ISC

I-CSCF

Pw =Mw Watcher application

Px = Cx

I CSCF

S-CSCF Presence S

HSSPw = ISC

Server




GPP P A hit t3GPP Presence Architecture

SIPPresencePresence

N t k A tPen

UE1 Home Network UE2 Home Network

ServerNetwork AgentPh (MAP) Pi ( ISC )

Subscriber Controlled Info(User Availability & Preference)

Network Controlled Info(Location Info/Connectivity State)

WatcherApplication

ApplicationServer

Pw ( ISC )HSS

S-CSCF 1

Pw ( ISC )

S-CSCF 2

Cx

I-CSCF 2

( )

SIPS CSCF 1

P-CSCF 1

S CSCF 2

P-CSCF 2

I CSCF 2

Watcher Presence


UE 1Watcher

SIPUE 2

Presentity

SIPProxy Proxy

Presence User Agent



IMS W t h R i t iIMS Watcher Registering

Presentity Presence ProxyWatcher Presence Proxy

Home Network of watcher

Presence

Home Network of presentity

UE P-CSCF

1.SubscribePres

S-CSCF HSSPresence

Server

4. Query

I-CSCF S-CSCF

2.SubscribePres 3.SubscribePres

5.Resp

6.SubscribePres 7.SubscribePres

10.MsgAck11.MsgAck12.MsgSck

8.MsgAck9.MsgAck

13.NotifyPresUp

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

14.NotifyPresUp15.NotifyPresUp16.MsgAck 17.MsgAck 18.MsgAck



U d ti PUpdating Presence

Home Network of Presentity

UE P-CSCF S-CSCF PresenceServer

1. PressUpdateMsg

2. PressUpdateMsg

3. PressUpdateMsg

6 MsgAck

4.MsgAck

5.MsgAck6. MsgAck



N tif i IMS W t hNotifying IMS Watcher

Home Network of WatcherHome Network of Presentity

Watcher Presence ProxyPresentity

Presence Proxy

S-CSCF

1 NotifyPresUp

Presence Server P-CSCFS-CSCF I-CSCF UE

Presence Server has updates

1. NotifyPresUp

3. NotifyPresUp

k

2. NotifyPresUpThe PS sends the NOTIFY straight to the originating watcher presence proxy, by passing the presentity presence proxypresence

information to send to watcher as a result of user or user

4. MsgAck

5. MsgAck

6. MsgAck

by-passing the presentity presence proxy.

user or user agent updates



S b ibi t W t h Li tSubscribing to Watcher Listsubscription to the Presence Server requesting notification of any newwatcher subscriptions

PresenceUser Agent

Presence Server

PresentityPresence

Proxy

Watcher Presence

Proxy User Agent1. SubscribePresence (Watcher List)

Server

3. SubscribePres

Proxy Proxy

2.MsgAcks

5.Watcher Request Notification

3. SubscribePres4. SubscribePres

6. MsgAck

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

8. Update SubscriptionAuthorisationPolicies9. NotifyPresUp

7. MsgAckg

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

10. NotifyPresUp



OMA PS A hit tOMA PS ArchitectureGLMS Management/Administration

ent

GM -3

GM -4

ETW

OR

KGLMS

Net

wor

k P

Cor

e)GLM

Cli

GM -5

GM -2

AC

CES

S N

E

Age

nt

ore

PresenceServer

e Pr

esen

ce N

d on

a S

IP/IP

senc

e U

ser A

SIP

/ IP

Co

Rem

ote

(bas

ed

PresenceNetworkAgent

PRS-1 PRS -2

PRS -3

Pres Presence

ExternalAgent PRS -4

Telecom Service Integration for ITS IMS Services52UE IP -1


P Presence serverThe Presence Server (PS) SHALL provide :

Receive and manage presence informationProvide Subscription Authorization PolicyProvide Subscription Authorization PolicyProvide a watcher, if required, configurable filtering function that is used to limit the i f ti th t i d li d t t hinformation that is delivered to a watcherAllow watchers to request and subscribe to the full set of presence info of a presentityGenerates partial notifications to a watcherVerifies the identity of the watcher that subscribes to presentity's presence infosubscribes to presentity s presence infoSupports SIP-based communications with the Presentity SIP/IP Core



P U A tPresence User AgentThe Presence User Agent (PUA) collects presence info associated with a presentity representing a principalA bl th i f i th t d d f t Assemble the presence info in the standard format Send the presence information to the PS M th S b i ti A th i ti P liManage the Subscription Authorisation PolicyIdentify itself uniquely among other PUAs of the same presentity when publishing presence informationpresentity when publishing presence informationHandle any necessary interworking required to support terminals that do not support the standard interfaceterminals that do not support the standard interface

The PUA may be located in the user’s terminal or within a network entity



P N t k A tPresence Network AgentThe 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

MSC Server/VLR

GGSN

(heartbeat) mechanism from the PUA to the PNA.

MSC/MSCe

Presence NetworkAgent3GPP

Presence NetworkAgent3GPP23GPP

HSS/HLR

3GPP2

HSS/HLR AAA/HA/ Position


HSS/HLRS-CSCF SGSN GMLC

HSS/HLRS-CSCF AAA/HA/

PDSNPositionServer


SIP/IP CSIP/IP CoreRoutes the SIP signaling between PUA and PSProvides discovery & address resolution servicesSupports SIP compressionPerforms authentication and authorization of the PUA based on user’s service profilepMaintains the registration state Provides charging informationProvides charging informationOMA SIP/IP Core = 3GPP Presence Proxies



GLMSGLMSGroup and List Management Server (GLMS )Provides list management operations to create, modify, retrieve and delete groups and listsProvides storage for groups and lists



PS G l A hit tPS General Architecture

PresenceServerServer

SIP/IP CoreWatcher

SIP/IP CorePresentityS-CSCF 1 S-CSCF 2I-CSCF 2

P-CSCF 1P-CSCF 2

PresentityWatcherUE 1Watcher

UE 2Presentity

Presence User Agent



P bli hi P I fPublishing Presence Info Home Network Home Network

Presentity

PUA

1. PUBLISH

PSSIP/IP CorePUA

1. PUBLISH

SIP/IP Core

2. PUBLISH

3 200 OK

2. PUBLISH

3 200 OK

4. 200 OK

3.200 OK

4. 200 OK

3.200 OK



S di S b ib R tSending a Subscribe Request

P re s e n t i t y S IP / IP C o reW a tc h e r S IP / IP C o re

H o m e N e tw o r k o f w a t c h e r

P r e s e n c e

H o m e N e tw o r k o f p r e s e n t i t y



P S




P r e s e n c e


P re s e n t i t y S IP / IP C o reP re s e n t i t y S IP / IP C o reW a tc h e r S IP / IP C o re


P S


P U AW a t c h e r

1 . S U B S C R I B E2 . S U B S C R I B E 3 . S U B S C R I B E

P U AW a t c h e r

1 . S U B S C R I B E2 . S U B S C R I B E 3 . S U B S C R I B E

4 . 2 0 0 O K

5 . 2 0 0 O K

4 . 2 0 0 O K

5 . 2 0 0 O K

7 . N O T I F Y7 . N O T I F Y

6 . 2 0 0 O K


6 . 2 0 0 O K

9 . 2 0 0 O K

8 . N O T I F Y

1 0 . 2 0 0 O K9 . 2 0 0 O K

8 . N O T I F Y

1 0 . 2 0 0 O K9 . 2 0 0 O K

8 . N O T I F Y

1 0 . 2 0 0 O K9 . 2 0 0 O K

8 . N O T I F Y

1 0 . 2 0 0 O K



R i i N tifi tiReceiving a Notification

P tit

Home Network ofPresentity Home Network of Watcher

P titP tit


P tit


P titP titP titP tit


Presentity SIP/IP Core

1 NOTIFY

Presence Server

Presence Server hasupdates to

WatcherSIP/IP Core

Presentity SIP/IP CorePresentity

SIP/IP Core

1 NOTIFY

PS


WatcherSIP/IP Core Watcher

Presentity SIP/IP Core

1 NOTIFY

Presence Server


WatcherSIP/IP Core

Presentity SIP/IP CorePresentity

SIP/IP CorePresentity

SIP/IP CorePresentity

SIP/IP Core

1 NOTIFY

PS


WatcherSIP/IP Core Watcher

1. NOTIFY

2. NOTIFY

has updates to send to the watcher

1. NOTIFY

2. NOTIFY


1. NOTIFY

2. NOTIFY


1. NOTIFY

2. NOTIFY


3. 200 OK

4 200OK

3. 200 OK

4 200OK

3. 200 OK

4 200OK

3. 200 OK

4 200OK4. 200 OK4. 200 OK4. 200 OK4. 200 OK



P ti l N tifi tiPartial NotificationsHome Network of PresentityHome Network of PresentityHome Network of PresentityHome Network of Presentity

Watcher

1. SUBSCRIBE

2. SUBSCRIBE

SIP/IP Core PUWatcher

1. SUBSCRIBE

2. SUBSCRIBE

SIP/IP Core PUAWatcher

1. SUBSCRIBE

2. SUBSCRIBE


1. SUBSCRIBE

2. SUBSCRIBE

SIP/IP Core PUAPSWatcher

1. SUBSCRIBE

2. SUBSCRIBE


1. SUBSCRIBE

2. SUBSCRIBE

SIP/IP Core PUAWatcher

1. SUBSCRIBE

2. SUBSCRIBE


1. SUBSCRIBE

2. SUBSCRIBE

SIP/IP Core PUAPS

3.200 OK

5. NOTIFY

4.200 OK

5. NOTIFY

3.200 OK

5. NOTIFY

4.200 OK

5. NOTIFY

6. NOTIFY

9. PUBLISH

7. 200 OK8. 200 OK

9. PUBLISH

6. NOTIFY

9. PUBLISH

7. 200 OK8. 200 OK

9. PUBLISH

6. NOTIFY

9. PUBLISH

7. 200 OK8. 200 OK

9. PUBLISH

6. NOTIFY

9. PUBLISH

7. 200 OK8. 200 OK

9. PUBLISH

full state presence document

11. NOTIFY

12. NOTIFY

13. 200 OK

10. 200 OK

11. NOTIFY

12. NOTIFY

13. 200 OK

10. 200 OK

11. NOTIFY

12. NOTIFY

13. 200 OK

10. 200 OK

11. NOTIFY

12. NOTIFY

13. 200 OK

10. 200 OK

a partial presence document formulated showing only the changed tuple.


14. 200 OK14. 200 OK14. 200 OK14. 200 OKg y g p


S b ib PSubscribe PresenceH N t k f t h H N t k f t i tH N t k f t h H N t k f t i tH N t k f t h H N t k f t i tH N t k f t h H N t k f t i t

P r e s e n ti t y S I P / I P C o r eW a tc h e r S I P / I P C o r e

H o m e N e t w o r k o f w a t c h e r

P U A

1 . S U B S C R I B E

P r e s e n c e S e r v e r

H o m e N e t w o r k o f p r e s e n t i t y






W a t c h e r



P U A




P r e s e n ti t y S I P / I P C o r eP r e s e n ti t y S I P / I P C o r eW a tc h e r S I P / I P C o r e





W a t c h e r

2 . S U B S C R I B E s

5 2 0 0 O K

3 . S U B S C R I B E s2 . S U B S C R I B E s


4 A ut h o r i z a t i o n

6 . 2 0 0 O K


5 2 0 0 O K

3 . S U B S C R I B E s2 . S U B S C R I B E s


4 A ut h o r i z a t i o n4 A ut h o r i z a t i o n4 A ut h o r i z a t i o n

6 . 2 0 0 O K


7 . 2 0 0 O K


7 . 2 0 0 O K

1 0 . 2 0 0 O K.

1 1 . 2 0 0 O K.

1 2 N O T I F Y

1 0 . 2 0 0 O K.

1 1 . 2 0 0 O K.

1 2 N O T I F Y1 2 . N O T I F Y

1 3 . N O T I F Y

1 4 . 2 0 0 O K

1 5 . 2 0 0 O K

P r e s e n c e S e r v e r h a s u p d a t e s t o s e n d t o t h e w a t c h e r

1 2 . N O T I F Y

1 3 . N O T I F Y

1 4 . 2 0 0 O K

1 5 . 2 0 0 O K

P r e s e n c e S e r v e r h a s u p d a t e s t o s e n d t o t h e w a t c h e r

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


w a t c h e r w a t c h e r y p g p y /


Bl kiBlocking

H om e N etw ork o f p resentityH om e N etw ork o f p resentityH om e N etw ork o f p resentityH om e N etw ork o f p resentity

S IP /IP C oreW atcher P resence

S erverS IP /IP C oreS IP /IP C ore

W atcher P SS IP /IP C ore

W atcher P resence S erver

S IP /IP C oreS IP /IP C oreW atcher P S

1 . S U B S C R IB E2. S U B S C R IB E

1. S U B S C R IB E2. S U B S C R IB E



3. 403 Forb idden or 603 D ec line4 . 403 Forb idden o r 603 D ec line

3 . 403 Forb idden or 603 D ec line4 . 403 Forb idden o r 603 D ec line





P lit Bl kiPolite BlockingHom e Network of presentityHom e Network of presentityHom e Network of presentityHom e Network of presentityHom e Network of presentityHom e Network of presentityHom e Network of presentityHom e Network of presentity

SIP/IP CoreW atcher

1. SUBSCR IBE

SIP/IP CoreSIP/IP CoreW atcher

1. SUBSCR IBE

SIP/IP CoreW atcher

1. SUBSCR IBE


1. SUBSCR IBE

PSSIP/IP Core

W atcher

1. SUBSCR IBE


1. SUBSCR IBE

SIP/IP CoreW atcher

1. SUBSCR IBE


1. SUBSCR IBE

PS

2. SUBSCR IBE2. SUBSCR IBE

3. 200 OK


3. 200 OK


3. 200 OK


3. 200 OK4. 200 OK

5. NOTIFY6. NOTIFY

5. NOTIFY6. NOTIFY

4. 200 OK

5. NOTIFY6. NOTIFY

5. NOTIFY6. NOTIFY

4. 200 OK

5. NOTIFY6. NOTIFY

5. NOTIFY6. NOTIFY

4. 200 OK

5. NOTIFY6. NOTIFY

5. NOTIFY6. NOTIFY After applying the subscription authorization

7. 200 OK8. 200 OK

7. 200 OK8. 200 OK

7. 200 OK8. 200 OK

7. 200 OK8. 200 OK

7. 200 OK8. 200 OK

7. 200 OK8. 200 OK

7. 200 OK8. 200 OK

7. 200 OK8. 200 OK

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



W t h I iti t d C liWatcher Initiated Canceling

H o m e N e tw o r k o f p r e s e n t i ty

P S

H o m e N e tw o r k o f p r e s e n t i ty

P SW a tc h e r



S IP / IP C o r e P SW a tc h e r



S IP / IP C o r e P S

“Expires” header field set to 03 . 2 0 0 O K 3 . 2 0 0 O K

Expires header field set to 0

5 . N O T I F Y

4 . 2 0 0 O K

6 N O T I F Y

5 . N O T I F Y

4 . 2 0 0 O K

6 N O T I F Y “S b i ti St t ” h d fi ld

7 . 2 0 0 O K

6 . N O T I F Y

8 . 2 0 0 O K7 . 2 0 0 O K

6 . N O T I F Y

8 . 2 0 0 O K

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



PS I iti t d C liPS Initiated Canceling

Home Network of presentityHome Network of presentity

Watcher SIP/IP Core PSWatcher SIP/IP Core PS

1. NOTIFY

2. NOTIFY

1. NOTIFY

2. NOTIFY“Subscription-State” header field set to “terminated”

3. 200 OK4. 200 OK

3. 200 OK4. 200 OK

terminated



S b ibi W t h I f Subscribing Watcher Info

W a t c h e r

H o m e N e t w o r k o fP r e s e n t i t y

S I P / IP C o r e P U A

1 S U B S C R IB E

W a t c h e r




1 S U B S C R IB E

W a t c h e r



1 S U B S C R IB E

W a t c h e r




1 S U B S C R IB E

W a t c h e r



1 S U B S C R IB E

W a t c h e r




1 S U B S C R IB E

W a t c h e r



1 S U B S C R IB E

W a t c h e r




1 S U B S C R IB E

P SW a t c h e r



1 S U B S C R IB E

W a t c h e r




1 S U B S C R IB E

W a t c h e r



1 S U B S C R IB E

W a t c h e r




1 S U B S C R IB E

W a t c h e r



1 S U B S C R IB E

W a t c h e r




1 S U B S C R IB E

W a t c h e r



1 S U B S C R IB E

W a t c h e r




1 S U B S C R IB E

P S1 . S U B S C R IB E

3 . N O T IF Y

4 . 2 0 0 O K

1 . S U B S C R IB E

2 . 2 0 0 O K

3 . N O T IF Y

4 . 2 0 0 O K


3 . N O T IF Y

4 . 2 0 0 O K


3 . N O T IF Y

4 . 2 0 0 O K


3 . N O T IF Y

4 . 2 0 0 O K


2 . 2 0 0 O K

3 . N O T IF Y

4 . 2 0 0 O K


3 . N O T IF Y

4 . 2 0 0 O K


3 . N O T IF Y

4 . 2 0 0 O K


3 . N O T IF Y

4 . 2 0 0 O K


2 . 2 0 0 O K

3 . N O T IF Y

4 . 2 0 0 O K


3 . N O T IF Y

4 . 2 0 0 O K


3 . N O T IF Y

4 . 2 0 0 O K


3 . N O T IF Y

4 . 2 0 0 O K


2 . 2 0 0 O K

3 . N O T IF Y

4 . 2 0 0 O K


3 . N O T IF Y

4 . 2 0 0 O K


3 . N O T IF Y

4 . 2 0 0 O K

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

8 . 2 0 2 A c c e p te d

7 . 2 0 2 A c c e p te d

8 . 2 0 2 A c c e p te d

9 . N O T IF Y

8 . 2 0 2 A c c e p te d

7 . 2 0 2 A c c e p te d

8 . 2 0 2 A c c e p te d

9 . N O T IF Y

8 . 2 0 2 A c c e p te d

7 . 2 0 2 A c c e p te d

8 . 2 0 2 A c c e p te d

9 . N O T IF Y

8 . 2 0 2 A c c e p te d

7 . 2 0 2 A c c e p te d

8 . 2 0 2 A c c e p te d

9 . N O T IF Y

SUBSCRIBESUBSCRIBE

NOTIFY with “Subscription-State" of "pending" value, which indicates that th b i ti h b i d b t

1 1 .2 0 0 O K

1 3 . N O T IF Y

1 4 . 2 0 0 O K

9 . N O T IF Y

1 0 . N O T IF Y

1 2 .2 0 0 O K1 1 .2 0 0 O K

1 3 . N O T IF Y

1 4 . 2 0 0 O K

9 . N O T IF Y

1 0 . N O T IF Y

1 2 .2 0 0 O K1 1 .2 0 0 O K

1 3 . N O T IF Y

1 4 . 2 0 0 O K

9 . N O T IF Y

1 0 . N O T IF Y

1 2 .2 0 0 O K1 1 .2 0 0 O K

1 3 . N O T IF Y

1 4 . 2 0 0 O K

9 . N O T IF Y

1 0 . N O T IF Y

1 2 .2 0 0 O K

the subscription has been received, but that policy info is insufficient to accept/ deny the Subscription at this time.

1 1 .S u b s c r ip t io n A u t h o r is a t io n1 5 .S u b s c r ip t io n A u t h o r is a t io n1 6 . N O T IF Y

1 7 . N O T IF Y

1 8 .2 0 0 O K1 9 2 0 0 O K


1 7 . N O T IF Y

1 8 .2 0 0 O K1 9 2 0 0 O K


1 7 . N O T IF Y

1 8 .2 0 0 O K1 9 2 0 0 O K


1 7 . N O T IF Y

1 8 .2 0 0 O K1 9 2 0 0 O K

authorizes the subscription

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


2 0 . N O T IF Y1 9 .2 0 0 O K

2 1 2 0 0 O K

2 0 . N O T IF Y1 9 .2 0 0 O K

2 1 2 0 0 O K

2 0 . N O T IF Y1 9 .2 0 0 O K

2 1 2 0 0 O K

2 0 . N O T IF Y1 9 .2 0 0 O K

2 1 2 0 0 O K

( g p g )


A ti P I fAggregating Presence InfoAggregating Published Presence information from multiple sources Home Network

PresentitHome Network of

Presentity

PUA1

1. PUBLISH

PSSIP/IP Core

PUA2 W atcher

4. 200 OK

2. PUBLISH

3. 200 OK

5. PUBLISH6. PUBLISH

8. 200 OK 7. 200 OK

10. NOTIFY9. NOTIFY

12 200 OK


11. 200 OK12. 200 OK


R f f PReferences for Presence (1/2)

3GPP TS 22.141 V6.2.1 (2004-07)Presence Service; Stage 1(Release 6)Stage 1(Release 6)

3GPP TS 23.141 V6.6.0 (2004-06)Presence Service;Architecture & functional description (Release 6)

Stage 2 - Presence using SIMPLEDraft Version 1 0 – 02 August 2004Draft Version 1.0 02 August 2004OMA-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



R f f PReferences for Presence (2/2)

CCL T h i l J l CCL Technical Journal 3GPP Mobile Presence: September 2003

OMA-Open Mobile Alliance/Wireless Village http://www.openmobilealliance.org/wirelessvillage/

Jabber Software Foundation,The Jabber Protocolhttp://www.jabber.org/protocol/ p // j g/p /

IETF IMPP (Instant Messaging and Presence Protocol)

IETF SIMPLE IETF SIMPLE (SIP for Instant Messaging and Presence Leveraging Extensions)


IETF XMPP (Extensible Messaging and Presence Protocol)


SSummary

3GPP/OMA Mobile Presence ServiceMaybe to be a Killer Service Platform

Integration of other VAS (PoC, LBS, MMS)



O tliOutline




3GPP & OMA Presence


P C Hi h L l P d




P h t t lk S iPush-to-talk Service

Push-to-talk Service



Wh t i P h t t lk ?What is Push-to-talk ?Mobile phone user can only push one button to talk with another person or a group.push to talk provides end-users with the ability to quickly find one another and engage in brief, burst oriented style communication burst-oriented style communication. Advances in market adoption and technology

l ti f i i l IP ill bl evolution of voice over wireless IP will enable improvements in Push-to-Talk (PTT).



I t d ti t P CIntroduction to PoCOriginally introduced in the US by Nextelthrough its partnership with Motorola and its use of the iDEN technology use of the iDEN technology Combining aspects of cellular mobile communications presence detection and communications, presence detection, and walkie-talkie style communications, E i Si M t l d N ki Ericsson, Siemens, Motorola and Nokia published the Push-to-talk over Cellular (PoC) release 1.0 at Aug. 2003.release 1.0 at Aug. 2003.OMA form the PoC (Push-to-talk over Cellular) working group at Nov 2003


working group at Nov. 2003.


P C M k t PoC Market P C it d f d d f i k PoC suited for demands for quick comm. among users.

PoC is provided in half-duplex mode transmission occurs in both directions, but not at the same time – each must wait to speak

the inability to interrupt lends to quick exchanges of info.

The PoC market will continue to evolve & ultimately represent service opportunities for the more traditional markets (dispatch and mobile workforce users) as well as markets (dispatch and mobile workforce users) as well as more mass market users such as the youth market.PoC will become important for government, public safety

l d th ffi i l personnel and other officials as a communications tool,

serving the need for efficient communications during i f di h


times of emergency, disaster, or threats.


P C T h l S tPoC Technology SupportAt the core of PoC is an IETP standardized protocol known as SIP used for IP Telecom and 3GPP IP Multimedia Subsystem infrastructure 3GPP IP Multimedia Subsystem infrastructure. Being that it uses IP as a transport/bearer, PoC is highly dependent on the roll out expansion is highly dependent on the roll-out, expansion and improvements of 2.5G and 3G technology and infrastructure.and infrastructure.The Open Mobile Alliance (OMA) is working to standardize Push-to-Talk over Cellular (PoC) standardize Push to Talk over Cellular (PoC) (below).



G l f OMA P C WGGoals of OMA PoC WGDevelop specifications to permit deployment of interoperable PoC services

l i f k hDevelop a common PoC service framework that could be deployed over a variety of networks

Th li ti f k ill b d l dThe application framework will be modeled over the capabilities of 3GPP IMS & 3GPP2 MMD

PoC SHALL utilize SIP/IP Core in 3GPP and 3GPP2Any non-IMS based SIP network is assumed to have the same functionality as IMS

Th i iti l f The initial focus develop an open standard to enable adoption of PoC service over mobile networks


oC se ce o e ob e et o s


P C St d di ti ( / )PoC Standardization (1/2)OMA is standardizing Push-to-Talk over Cellular (PoC) infrastructure & processes

evolution of PTT from proprietary approaches to a more open approach ultimately enable inter-carrier PoCultimately enable inter carrier PoC

OMA - offer infrastructure network elements:PoC Server:PoC Server:

Contains the PoC server-side logicproviding functions:

end-point for SIP signaling and voice bursts, handles participant lists distribution, reporting to the charging system, and


p g g g y ,media distribution.


P C St d di ti ( / )PoC Standardization (2/2)Group/List Manager Server (GLMS):

Responsible for management of contact lists, group lists, access lists, and permissions management, p g

IMS Core: Contains SIP proxies and SIP registers. The UE access the IMS Core for purposes of SIP signaling to the PoC the IMS Core for purposes of SIP signaling to the PoC Server. The IMS Core also handles HSS/AAA functions and triggering of personal & group instant talk sessions.

User Equipment (UE):Terminal equipment containing the PoC app. software

OMA standardize the processes:OMA - standardize the processes:roaming, identification, addressing, and modes of operation (session establishment and


panswering)


OMA P C A hit tOMA PoC ArchitectureGLMS Management/Administration

IeIt: Floor Control and media

GLMS

Im

RK

pabi

litie

s)

IplIgs

Itn: Floor Control and mediaIs: PoC Client to Proxies

Session Signaling (SIP)If: Proxy to PoC Server

PoC CES

S N

ETW

O

IMS

/MM

D c

a p

IkPresence Server

Ips

gIf: Proxy to PoC Server Session Signaling (SIP)

Ips: SIP/IP Core to PoC Server (SIP) PoC

clientIs

IfAC

C

ore

(bas

ed o

n Server

Ser

ver

Net

wor

k

( )In: Proxy to Proxy Session

Signaling (SIP)Im: Group Mgmt to PoC

ItS

IP /

IP C

o

PoC

S

Rem

ote

PoC

In

ItnClient (XCAP)XCAP–XML Configuration Access Protocol

Ik: Group Mgmt to PoC Server


InIk: Group Mgmt to PoC Server


OMA P C K E titiOMA PoC Key EntitiesPoC Specific Entities

PoC Client

PoC Server

Group and List Management Server (GLMS)

External Entities SIP/IP Core/

Presence Server



OMA P C Cli tOMA PoC ClientP C CliPoC Client

A software resides on the mobile terminal and is used to access PoC servicePerform Registration with SIP/IP coreParticipate in authentication with SIP/IP coreProvide access to different lists in GLMS, e.g., contact lists, group lists etc.Provide the capabilities for PoC sessioninitiation, participation and terminationSupport floor control procedures (e.g., make request and respond to commands)q p )Incorporate configuration data downloaded by the PoC Application Service InfrastructureProvide access to presence information


Provide access to presence information


OMA P C S ( / )OMA PoC Server (1/4)PoC Server

Provides PoC session handling

Provides SIP session handling, such as SIP sessionProvides SIP session handling, such as SIP session origination, termination, etc.

Provides the Media distribution

P id th fl t l f ti lit i l diProvides the floor control functionality including talker identification

Provides policy enforcement for participation in group sessions

Provides policy handling for incoming PoC session (e.g. access control, availability status, etc)

Provides the participants info (i.e. user nicknames)

Collects and provides media quality information

Collects and provides the charging information


Collects and provides the charging information


OMA P C S ( / )OMA PoC Server (2/4)PoC Server

The PoC server MAY perform a Controlling PoC Function or Participating PoC FunctionFunction or Participating PoC Function.

A PoC server MAY perform both a Controlling PoC function and a Participating PoC function at the same time.

The determination of the PoC Server roleIn case of 1 1 PoC Session & Ad hoc PoC group sessionIn case of 1-1 PoC Session & Ad-hoc PoC group session

the PoC server of the inviting user shall perform the Controlling PoC Function.

In case of Chat PoC group & pre-arranged group sessionthe PoC server owning/hosting the group identity shall perform the Controlling PoC


identity shall perform the Controlling PoC Function.


OMA P C S ( / )OMA PoC Server (3/4)1-1 PoC Session in a multiple network environment

Network A

Controlling POC

Function

POCClient A

1:1

ParticipatingPOC

Function A1:1

POCCli t B

ParticipatingPOC Client B1:1 POC

Function B1:1


Network B


OMA P C S ( / )OMA PoC Server (4/4)

Network ANetwork X

PoC Group session in a multiple network environment

ControllingPOC

Function

ParticipatingPOC

Function A

POCClient A

1:1 1:N

ParticipatingPOC

POCClient B

Network B

POCFunction B1:M 1:1



GLMS & PSGLMS & PSGroup and List Management Server (GLMS)

PoC users use the GLMS to manage groups and lists (e g contact and access lists) that arelists (e.g. contact and access lists) that are needed for the PoC service.

Provides list management operations to create, modify, retrieve and delete groups and lists

Provides storage for groups and lists

Presence Server (PS)Provides availability information in support of the PoC Servicethe PoC Service



SIP/IP CSIP/IP CoreP C SHALL ili SIP/IP C b d b PoC SHALL utilize SIP/IP Core based on capab. from IMS as specified in 3GPP & 3GPP2SIP/IP C i t f th P C S iSIP/IP Core in support of the PoC Service

Routes SIP signaling between PoC Client & PoC ServerProvides discovery and address resolution servicesSupports SIP compressionSupports SIP compressionPerforms authentication & authorization of PoC Client based on user’s service profile

i i h i i d hMaintains the registration state and the SIP session stateProvides charging information



P C Id tifi tiPoC IdentificationPoC address

Each user SHALL have one or more PoC Addresses, known as public user identityp yin format of SIP URI[RFC3261] or TEL URI[RFC2806bis]

At least one PoC Address SHALL be in the format of a SIP URI. SIP/IP Core will translate a TEL URI to a SIP URI for routing.SIP/IP Core will translate a TEL URI to a SIP URI for routing.

Examples of PoC Addresses sip:[email protected]:+16195551212tel:+16195551212

Private user identityassigned by network operator for authentication

@ lusername@realmGroup identities

A group is identified with a group identity.


Generated and stored in the GLMS


T lk B t A bit ti ( / )Talk Burst Arbitration (1/4)

The PoC Server SHALL arbitrate talk burstsSHOULD confirm the request to send a talk burst if no other PoC Client has the permissionSHALL reject the request to send a talk burst if another PoC Client has the permission and the PoC Server or the PoC Client does not support queuing.

talk burst queueSHALL place a request according to the prioritySHOULD support # queue positions per session pp q p p

at least equal to # participants up to the permitted maximum # participants

SHALL be at most one request queued for each PoC q q fClient

SHALL revoke the permission to talk if the length exceeds a configurable maximum talk burst duration




The PoC Client and the PoC Server SHALL support

T lk B t t (Cli t >S )Talk Burst request (Client->Server)

Talk Burst Confirm response (Server->Client)

Talk Burst Reject response (Server->Client)Talk Burst Reject response (Server >Client)

Talk Burst Completed indication (Client->Server)

No Talk Burst indication (Server->Client)

Receiving Talk Burst indication (Server->Client)

Stop Talk Burst indication (Server->Client)

Floor Control (RTCP - IETF RFC 1889)request, grant, deny, release, idle, taken, revoke (RTCP APP)


quality feedback (RTCP SR & RR), RTCP BYE



T lk b t t l 7 fl t lTalk burst control – 7 floor control messagesFloor Request – A UE requests that the Controlling PoC server shall allocate the media resource to his deviceFloor Grant – The Controlling PoC server notifies the UE that it has been granted the floorFloor Deny – The Controlling PoC server notifies a UE that it has been Floor Deny – The Controlling PoC server notifies a UE that it has been denied permission to use the media resourceFloor Release – A UE notifies the Controlling PoC server that it is releasing the media sourcereleasing the media sourceFloor Idle – The Controlling PoC server notifies the UEs that no one owns the media sourceFloor Taken – The Controlling PoC server notifies all UEs (except the granted UE) that the floor has been granted to another UEFloor Revoke – Allows the Controlling PoC server to revoke the media


gresource form a UE



If h P C S d h P C Cli If the PoC Server and the PoC Client support queuing of the Talk Burst Request

Talk Burst Request Queued responseTalk Burst Request Queued responseServer -> Client

Talk Burst Queue (client) Position requestClient -> Server

Talk Burst Queue Position responseServer > ClientServer -> Client

Talk Burst Queue (others) Identity requestClient -> Server

Talk Burst Queue Identity responseServer -> Client



P C S i S t U ( / ) PoC Session Set-Up (1/2) On-Demand Session

The On Demand session provides a mechanism to negotiate media parameters such as IP address,negotiate media parameters such as IP address, ports and codecs, which are used for sending the media and floor control packets between the PoC Client and the home PoC Server when thePoC Client and the home PoC Server when the user wants to actually establish a PoC session. This mechanism allows the PoC Client to invite, i P C ( ) th P C li t ivia PoC server(s), other PoC clients or receive

PoC sessions by using the full session establishment procedure each time the user

t t t bli h/ i /j i P C iwants to establish/receive/join a PoC session. Media parameters may be negotiated again in this mechanism.


PS Domain PS Domain PoC userPoC AS &PoC user(A) (B) (UE-B)IMS Core(UE-A)

1.Power On 1.Power On

2. PS Attach 2. PS Attach

3. Establish PDP context 3. Establish PDP context

4. Perform IMS Registration


5Initiate PoC

Session

6b INVITE

6a. Establish PDP context for media

6b. INVITE

7. INVITE

9a. Establish PDP context for media

8a. 200 OK

8b. Modify PDP context for media

9b. 200 OK

10.Floor Control

11.Transfer of Media


P C S i S t U ( / )PoC Session Set-Up (2/2)Pre-established Session

The pre-established session provides a mechanism to negotiate media parameters such asmechanism to negotiate media parameters such as IP address, ports and codecs, which are used for sending the media and floor control packets between the PoC Client and the home PoC Serverbetween the PoC Client and the home PoC Server before establishing the PoC session. This mechanism allows the PoC Client to invite other PoC clients or receive PoC sessions without negotiating again the media parameters. After the pre-established session has been set up (once the PoC user has registered), the PoC Client is able to activate media bearer whenever needed.


whenever needed.

PS Domain(A)

PS Domain PoC user(UE B)

PoC AS &PoC user(UE A) (A) (B) (UE-B)IMS Core(UE-A)

1.Power On 1.Power On

2. PS Attach 2. PS Attach

3 E t bli h PDP t t

5. Set up of Pre-established session

3. Establish PDP context 3. Establish PDP context



5. Set up of Pre established session5a. INVITE

5b. 200 OK

5. Set up of Pre-established session

7Initiate PoC

6. Establish PDP context for media6. Establish PDP context for media

8. Establish mediaSession (e.g. REFER)

10. ACCEPT

9. Floor control: Floor status

11. Floor Control establishment

12.Transfer of Media


Ad h P C A hit tAd-hoc PoC Architecture

PoC ServerControlling

PoC ServerParticipating



SIP/IP Core SIP/IP CoreS-CSCF 1 S-CSCF 2I-CSCF 2SIP/IP Core

P-CSCF 1P-CSCF 2

PoC Subscriber

PoC ClientInviting

UE 1Watcher

UE 2Presentity

Presence User Agent

PoC Subscriber



Ad h ( /8)Ad-hoc PoC Group Session (1/8)

In the Ad-hoc PoC group session setup one PoC subscriber selects

several other PoC subscribers to be invited

to an ad-hoc PoC group session.

1 1 PoC session set p 1-1 PoC session setup is similar case with ad-hoc PoC group session

except only one PoC subscriber is invited byexcept only one PoC subscriber is invited by the inviting PoC subscriber.

SetupSetupOn-demand session (Un-/Confirmed indication)

Pre-established session (Un-/Confirmed)



Ad h ( /8)Ad-hoc PoC Group Session (2/8)PoCClient A Home Network & Controlling Network

PoC client APoC client ASIP/IP Core A

PoC server A(participating& controlling)

PoCClient A Home Network & Controlling NetworkFrom PoC ClientOn-demand Session

2. INVITE2. INVITE

1. INVITE1. INVITE

Invitations to the invited PoC subscriber

Confirmed indication

3. RINGING3. RINGING First Ringing response4. RINGING4. RINGING

5. SUBSCRIBE (result)5. SUBSCRIBE (result)

d

Optional

8. OK8. OK7. OK7. OK First accepted invitation

9 Fl G d9 Fl G d

6. SUBSCRIBE (result)6. SUBSCRIBE (result)Sends SUBSCRIBE request in order to receive information about the result of the invitations.

If none of the invited PoC subscribers 9. Floor Granted9. Floor Granted

10. Media10. Media

Response for the invitation11. NOTIFY (result)11. NOTIFY (result)12. NOTIFY (result)12. NOTIFY (result)

When final response is received from an invited PoC subscriber, …

accepts the invitation, the PoC server A (participating & controlling) rejects the PoC session


from an invited PoC subscriber, …


Ad h ( /8)Ad-hoc PoC Group Session (3/8)PoCclient A Home Network

PoC client BPoC client BSIP/IP Core B

PoC server B(participating)

SIP/IP Core A


PoCClient B Home NetworkPoC client A Home Network & Controlling NetworkTo PoC Client

On-demand

1. INVITE1. INVITE

2. INVITE2. INVITE

Manual answer

6. RINGING6. RINGING

5. INVITE5. INVITE

4. INVITE4. INVITE

3. INVITE3. INVITE




10. RINGING10. RINGING12. OK12. OK

11. OK11. OK

14. OK14. OK

13. Ok13. Ok

15. OK15. OK16. Floor Status16. Floor Status 17. Floor Status17. Floor Status



Ad h ( /8)Ad-hoc PoC Group Session (4/8)PoC Client A Home Network & Controlling NetworkFrom PoC Client

On-demand Session PoC client APoC client ASIP/IP Core A


PoC Client A Home Network & Controlling Network

Unconfirmed indication

2. INVITE2. INVITE

1. INVITE1. INVITE


3. UNCONFIRMED OK3. UNCONFIRMED OK

invited PoC subscriber

First AUTO-ANSWER response4. UNCONFIRMED OK4. UNCONFIRMED OK

5. Floor Granted5. Floor Granted5. Floor Granted5. Floor Granted

6. Media6. Media

8. SUBSCRIBE (result)8. SUBSCRIBE (result)7. SUBSCRIBE (result)7. SUBSCRIBE (result)

f9 NOTIFY (result)9 NOTIFY (result)

OptionalSends SUBSCRIBE request in order to receive information

b t th lt f th i it ti Response for invitation9. NOTIFY (result)9. NOTIFY (result)10. NOTIFY (result)10. NOTIFY (result)about the result of the invitations.




Ad h ( /8)Ad-hoc PoC Group Session (5/8)PoCclient A Home Network



SIP/IP Core A



On-demand

1. INVITE1. INVITE

2. INVITE2. INVITE

Automatic answer

8. INVITE8. INVITE7. INVITE7. INVITE

3. INVITE3. INVITE

4. AUTO-ANSWER4. AUTO-ANSWER



12. OK12. OK

11. OK11. OK

10. OK10. OK9. OK9. OK

13. OK13. OK14. Floor Status14. Floor Status 15. Floor Status15. Floor Status



Ad h (6/8)Ad-hoc PoC Group Session (6/8)PoCClient A Home Network & Controlling Network



PoCClient A Home Network & Controlling NetworkFrom PoC ClientPre-established

3. ACCEPTED3. ACCEPTED

2. REFER2. REFER

1. REFER1. REFER


ÁÁ

Confirmed indication

First accepted invitation

4. ÁCCEPTED4. ÁCCEPTED

5. Floor Granted5. Floor Granted

6. Media6. Media

Response for invitation7. NOTIFY (result)7. NOTIFY (result)8. NOTIFY (result)8. NOTIFY (result)

Optional

If requested by the PoC client A8. NOTIFY (result)8. NOTIFY (result)




Ad h ( /8)Ad-hoc PoC Group Session (7/8)PoCClient A Home Network & Controlling Network



PoCClient A Home Network & Controlling NetworkFrom PoC ClientPre-established

3. ACCEPTED3. ACCEPTED

2. REFER2. REFER

1. REFER1. REFER


ÁÁ

Unconfirmed indication

First AUTO-ANSWER response

4. ÁCCEPTED4. ÁCCEPTED

5. Floor Granted5. Floor Granted

6. Media6. Media

Response for invitation7. NOTIFY (result)7. NOTIFY (result)8. NOTIFY (result)8. NOTIFY (result)8. NOTIFY (result)8. NOTIFY (result)


National Chung Cheng UniversityAd-hoc PoC Group Session(8/8)(8/8)

PoCclient A Home Network



SIP/IP Core A



Pre-established

1. INVITE1. INVITE

2. INVITE2. INVITE

AnswerConfirmed

OK

4. OK4. OK

3. INVITE3. INVITEOKUnconfirmed

Auto Answer5. OK5. OK

6. OK6. OK

7. Floor Status7. Floor Status 8. Floor Status8. Floor Status

Auto AnswerSince in this case the PoC client B is accepting the session automatically, or has authorised PoC Client A to issue a manual answer override PoC Client A to issue a manual answer override request,and PoC client B has pre-established session with PoC server B (participating), the PoC Server B (participating) sends OK response


PoC Server B (participating) sends OK response back towards the controlling network.


d hiPre-arranged PoC Architecture

PoC ServerControlling




PoC ServerParticipating p g

SIP/IP Core SIP/IP Core

S-CSCF 1 S-CSCF 2I-CSCF 2

p g

SIP/IP Core SIP/IP Core

P-CSCF 1P-CSCF 2

PoC Subscriber

PoC ClientInviting

UE 1Watcher

UE 2Presentity

Presence User Agent

PoC Subscriber

PoC Subscriber



P d P C G ( / )Pre-arranged PoC Group (1/5)

A pre-arranged PoC group a group having pre-defined group identity and member listmember list

a pre-arranged PoC group session is initiated by one of the members

established by using the group identity in the invitation message.

The PoC Server X performs the necessaryThe PoC Server X performs the necessary terminating service control

authorizes the PoC Client AIf the PoC address of the initiating user is authorized successfully, the PoC server X invites the other members to the PoC session


invites the other members to the PoC session


P d P C G ( / )Pre-arranged PoC Group (2/5)PoCClient A Home Network C t lli t k


PoC server A(participating)

SIP/IP Core X

PoC server X(controlling)

1. INVITE1. INVITE

PoCClient A Home Network Controlling networkOriginating partOn-demand

4. INVITE4. INVITE

3. INVITE 3. INVITE

2. INVITE2. INVITEConfirmed indication

5. INVITE 5. INVITE

First accepted invitation

Invitation to the group members

6. OK6. OK

8. OK8. OK

7. OK7. OK

10. OK10. OK

9. OK9. OK

Floor control



P d P C G ( / )Pre-arranged PoC Group (3/5)P CCli t B H N t kControlling Network



SIP/IP Core X


PoCClient B Home NetworkControlling NetworkTerminating partOn-demand

1. INVITE1. INVITE

3. INVITE3. INVITE

2. INVITE2. INVITE

Manual answer

7 Alerting7 Alerting6. Alerting6. Alerting

5. INVITE5. INVITE

4. INVITE4. INVITE

9. Alerting9. Alerting



10. Alerting10. Alerting12. OK12. OK

11. OK11. OK

14. OK14. OK

13. Ok13. Ok

15. OK15. OK

Floor control


Floor control


P d P C G ( / )Pre-arranged PoC Group (4/5)PoCClient A Home Network C t lli t k



SIP/IP Core X


1. INVITE1. INVITE

PoCClient A Home Network Controlling networkOriginating partOn-demand

4. INVITE4. INVITE

3. INVITE 3. INVITE

2. INVITE2. INVITEUnconfirmed

5. INVITE 5. INVITE

First auto-answer indication

Invitation to the group members

6. Unconfirmed OK6. Unconfirmed OK





Floor control



P d P C G ( / )Pre-arranged PoC Group (5/5)Controlling Network



SIP/IP Core X


PoCClient B Home NetworkControlling NetworkTerminating partOn-demand

1. INVITE1. INVITE

3. INVITE3. INVITE

2. INVITE2. INVITE

INVITEAuto answer

3. INVITE3. INVITE

5 . Auto-Answer5 . Auto-Answer

4. Auto-Answer4. Auto-Answer

6 . Auto-Answer6 . Auto-Answer

8. INVITE8. INVITE

7. INVITE7. INVITE

10. OK10. OK9. OK9. OK

12. OK12. OK

11. Ok11. Ok

13. OK13. OK



Ch t P C G S iChat PoC Group SessionPoC Client A Home Network C t lli t kJoin the Chat



SIP/IP Core X


1. INVITE1. INVITE

PoC Client A Home Network Controlling network

The PoC Server X performs the necessary terminating service control 4. INVITE4. INVITE

3. INVITE 3. INVITE

2. INVITE2. INVITE

(e.g. authorizes the PoC Client A) and if the PoC Address of the user initiating the PoC session is authorized successfully The user is

5. INVITE 5. INVITE

6. OK6. OK

7. OK7. OKauthorized successfully. The user is added to the Chat PoC Group session.

10. OK10. OK

9. OK9. OK

8. OK8. OK

11. Floor control



L i P C G S i Leaving PoC Group Session PoC Client A Home Network C t lli t k



SIP/IP Core X


PoC Client A Home Network Controlling network

2 BYE2 BYE

1. BYE1. BYE

Existing talk session

Leaving-session-request

Any group participant may leave the group session.

When the PoC group session 4. BYE4. BYE

3. BYE3. BYE

2. BYE2. BYE

5. BYE5. BYEWhen the PoC group session initiator leaves the group session, whether the group session is ended or not depends on the

5. BYE5. BYE

6. OK6. OK

8. OK8. OK

7. OK7. OK

group policy.10. OK10. OK

9. OK9. OK



R j i i P C G S iRe-joining PoC Group SessionPoCClient A Home Network C t lli t k



SIP/IP Core X


PoCClient A Home Network Controlling network

Rejoin-session-request

3. INVITE3. INVITE

2. INVITE2. INVITE

1. INVITE1. INVITE Existing talk session

When the user wishes to rejoin 4. INVITE4. INVITE

5. INVITE5. INVITE

6. OK6. OK

7 OK7 OK

jthe PoC group session, he issues INVITE request to the PoC server. The PoC server adds the user to the PoC group session if it is still

10. OK10. OK

9. OK9. OK

8. OK8. OK

7. OK7. OKthe PoC group session if it is still ongoing, otherwise it is rejected.

Floor control



G & Li t M tGroup & List Management

PoCClient A Home Network

PoC Client APoC Client A GLMS AGLMS A

1. LIST MANAGEMENT LIST Management request includea. Group identityb. Group objectives:

2. OK2. OK

p jdisplay name, group type, member list

c. Indication: Create, modify, retrieve or delete



P C M di FlPoC Media Flows

One to one Media Network A

PoCClient A

PoCServer A

(Participating)PoC

Client B

PoCServerX

(Controlling)

PoCServer B

(Participating)

Controlling POC

Function

POCClient A

ParticipatingPOC

Function A( p g) ( g) ( p g)

PoC Server

1. Media

2. MediaPOC

Client B

Participating

POC

3. Media4. Media

Network B

POCFunction B



P C M di FlPoC Media Flows

Network ANetwork Xbe used in PoC Sessions with Pre-arranged Groups

One-to-many Media

PoCPoC

Server A PoCPoC

Server XPoC

Server B PoC

ControllingPOC

Function

ParticipatingPOC

Function APOC

Client A

Network ANetwork Xbe used in PoC Sessions with Pre-arranged Groups, Ad Hoc groups or Chat groups

PoCClient A (Participating)

PoCClient B 1(Controlling) (Participating)

PoCClient B2

1. Media

2. Media

3. MediaParticipating

POC POC

Network B

4. Media

5. Media

6. Media

POCFunction B

POCClient B



R f f P CReferences for PoCPush to talk over Cellular (PoC) - Architecture

Draft Version 1.0 – 07 April 2004Open Mobile Alliance: OMA-AD PoC-V1 0-20040407-DOpen Mobile Alliance: OMA AD_PoC V1_0 20040407 D

Push-to-talk over Cellular (PoC) – ArchitecturePoC Release 2.0 –

Architecture V2.0.8 (2004-06)Comneon, Ericsson, Motorola, Nokia, Siemens

PoC User Plane - Transport ProtocolPoC User Plane Transport ProtocolPoC Release 2.0 –

Transport Protocols V2.0.6 (2004-06)i l ki iComneon, Ericsson, Motorola, Nokia, Siemens

3GPP TR 23.979 V1.0.0 (2004-06)3GPP enablers for OMA PoC Services;Stage 2(Release 6)


; g ( )


SSummary

Deploying Push-to-talk over CellularIncremental revenue, not to replace normal

ll l bil i ti icellular mobile communications service



Any Question? Any Question? y Qy Q

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

national chung cheng university 3gpp im call model

Documents