Capability Discovery in RCS

Capability Discovery in Rich Communication System (RCS)..

1. Capability Discovery
Nikhil Shaw

2. Capability Discovery
Services Comment Tags
Instant Messaging 1-1 Chat / Group Chat
oma.sip.im

iari.rcs.im
File Transfer
Sharing of file via chat.JPG/JPEG for image.Pdf/
docx for document.

iari.rcs.fthttp
Image Share During call, sharing of image ish
Video Share Same like video call. Can share video during call.cs-voice
Geo-Location
Push
Share location in between calls. rcs.geopush
Shared Map Mark/ Pin places on shared map. gsma.sharedmap
Shared Sketch
Sharing a sketch window on either party in call
UI.Any sketch on either end will reflect on other
side.
gsma.sharedsketch

3. •Capability Discovery is a process which enables a user to understand the
subset of RCS services available to communicate with their contacts at
certain point of time.

•These capabilities are exchanged when the use of services come into play
& and the parties in that event needs to know each other capabilities, i.e,
what services are supported at either ends at that particular point of time.

•Why to check for services ?

It may happen that due to n/w fluctuation or no support for some services
etc , some services are not available, then we need to exchange the
capabilities in order to make either party updated for each other
capabilities.

4. Capability Discovery Mechanisms
•Presence:Uses PUBLISH,SUBSCRIBE and NOTIFY requests which queries
the RCS Application Server(AS) which stores the capabilities of users. Through
Publish, Users update their capabilities on AS. Subscribe and Notify are used to
get any other users capabilities. Bell operator is Canada support Presence.
•Options: Sip OPTIONS is an end to end message which is used to query the
capabilities (services which the other party is supporting) of the target user . Also
the capabilities supported by the requestor is also forwarded to the other party in
the options message. Vodafone is Europe support Options.

5. OPTIONS
User A,B is RCS Registered. User C is a RCS user but not registered now. User
D is not an RCS user.
UE A SIP IMS CORE UE (B/C/D)
SIP OPTIONS (UE B)
200 OK (Capabilities of B)
SIP OPTIONS (UE C)
480 TEMPORARILY UNAVAILABLE
SIP OPTIONS (UE D)
404 NOT FOUND
408 REQUEST TIMEOUT

6. PRESENCE
UE A SERVER
REGISTRATION
200 OK
SUBSCRIBE
200 OK
NOTIFY
200 OK
PUBLISH
200 OK

7. PRESENCE
SIP SUBSCRIBE(User B, Anonymous)
200 OK
NOTIFY (User B Capabilities)
200 OK
UE A RCS AS

8. THANK YOU