1 / 13

OMA PoC over IMS

OMA PoC over IMS. Chapter 5.3 Multimedia Group Communication: Push-to-Talk over Cellular, Presence and List Management Concepts and Applications. Aldhino A. (20091204006) 2010.10.07. Overview: PoC Architecture in Service Provider. 4 major components:

valentine-gaines
Download Presentation

OMA PoC over IMS

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. OMA PoC over IMS Chapter 5.3 Multimedia Group Communication: Push-to-Talk over Cellular, Presence and List Management Concepts and Applications Aldhino A. (20091204006) 2010.10.07

  2. Overview: PoC Architecture in Service Provider 4 major components: • IMS as one of the gateways for user to use PoC • PoC Server provides major PoC communication functions • Presence Server deal with user availability list • XDMS handle PoC policy /setting (XML doc-based)

  3. Overview: OMA PoC Reference Points A reference point is defined whenever direct communication between two logical function is required. (POC-1, POC-2, etc.) Consist of: a set of operations to establish communication.

  4. Overview: 3GPP IMS Architecture • P-CSCF first entry point between user & IMS core network • S-CSCF single entry point between Apps. Servers & the IMS determines which and how services are provided to user behaves as a SIP registrar Other PoC component

  5. Map of OMA-IMS Reference Points From OMA PoC and 3GPP IMS architecture  map OMA PoC reference points into the corresponding IMS interfaces

  6. Map of OMA-IMS Ref. Points (2) • POC-1 implemented with “Gm” interface the handset must support features: - establish a security association with P-CSCF - implement signaling compression - IMS authentication based on AKA (Auth & Key Agreement)

  7. Map of OMA-IMS Ref. Points (3) • POC-2 IMS and PoC Server, implemented over “ISC” interface - 3rd party registration - setup of originating and terminating SIP sessions - delivery of SIP MESSAGE-based PoC operations

  8. Map of OMA-IMS Ref. Points (4) • POC-6 IMS and PoC XDMS, implemented with “ISC” interface - subscription to changes in XML docs. In this architecture, PoC XDMS is seen by the IMS as an application server.

  9. Map of OMA-IMS Ref. Points (5) • Ut interface defined for management of application data used to enable communication between XDMC and XDM service  to let the user manage groups. • IP-1 ref. point between IMS and IMS, implemented by “Mm” ref. points. interconnection function and pertain to diff. domains

  10. Map of OMA-IMS Ref. Points (6) • PRS-1 and PRS-2 implemented over “Gm” interface support Presence watcher & Presence source ops. • PRS-3, PRS-4, PRS-6, PRS-11 implemented over “ISC” interface support comm. between IMS – Presence Server, the RLS, the Presence XDMS, and RLS XDMS.

  11. PoC Server Roles • as a SIP Proxy • as a B2BUA (Back-to-Back User Agent)

  12. PoC Server as a SIP Proxy • When processing transaction based on the SIP MESSAGE method. • Application: delivery of PoC Group Adv. and Instant Personal Alert Messages. • When the participating PoC function does not need to stay in the media path. • PoC server will check the validity of incoming message. • Also, performs a routing decision to forward it to destination. • PoC server may reject an incoming request, before being forwarded. • After forwarding message, PoC server has no control over an incoming message.

  13. PoC Server as a B2BUA B2BUA : concatenation of a SIP User Agent Server (UAS) and a SIP User Agent Client (UAC). UAS  terminates incoming requests. UAC  initiates outgoing requests. When a user call another user, there are two SIP sessions: • The originating dialog between calling user & PoC server • The terminating dialog b.w. PoC server & remote end. To handle the sessions, PoC server maps incoming packets and SIP transactions between both parallel SIP/PoC sessions.  Thus, the PoC server behaves as a B2BUA, for both function: Controlling and Participating.

More Related