1 / 19

Advanced IMS Multipoint Conference Management Using Web Services

Advanced IMS Multipoint Conference Management Using Web Services. IEEE Commun. Mag. pp. 51-57, July 2007 M. Gomez, Agora Systems T. P. de Miguel, Spanish National Research Network (RedIRIS). Short Report. Outline. Introduction IMS Conferencing Architecture. Introduction.

kendis
Download Presentation

Advanced IMS Multipoint Conference Management Using Web Services

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. Advanced IMS Multipoint Conference Management Using Web Services IEEE Commun. Mag. pp. 51-57, July 2007 M. Gomez, Agora SystemsT. P. de Miguel, Spanish National Research Network (RedIRIS) Short Report

  2. Outline • Introduction • IMS Conferencing Architecture

  3. Introduction • IMS conference control interfaces are still in an early stage of development. • OSA Parlay X Multimedia Conference Web Service • Only basic group communication service is allowed (push to talk) • Multipoint conference over IMS is limited

  4. Introduction (cont.) • IMS conference control interfaces need to be enhanced to provide • broader and finer-grained management environment • high flexibility • scalability • Interoperability

  5. IMS Conferencing Architecture • IMS platform provides • Session control • Media processing function • QoS • Security • OSA and Parlay X Web service provides • A set of services for group commun.

  6. IMS Conferencing Architecture (cont.) • CSCF/AS [ignored here] • Media Resource Function (MRF) • Provide media-related function for provision of advanced services. • Announcement playback, transcoding and media mixing • Include two logical functions • Media resource function processor (MRFP) • Media resource function controller (MRFC)

  7. IMS Conferencing Architecture (cont.) • MRFP • Handle RTP media streaming • Transcoding • Mixing • Filtering • MRFC • Control MRF • MRFC and MRFP are deployed separately • Media Gateway Control Protocol (H.248) is used.

  8. IMS Conferencing Architecture (cont.) • Service can be provided by • AS control MRFP directly • MRFC acts as SIP AS and receive request from S-CSCF directly • Combination of both MRFC and AS • IMS conferencing can be classified as • Tightly coupled from signaling point of view • Centralized in term of media distribution

  9. IMS Conferencing Architecture (cont.) • All participants • Hold a SIP session with MRFC/AS • Exchange RTP media streams with MRFP

  10. Native IMS Conference Control • IETF SIP conferencing framework (RFC 4353) • These procedures can be classified into • Basic call control signaling • Third party call control (SPCC) • Event notification

  11. Native IMS Conference Control (cont.) Basic call control signaling • User can create and join a conference by calling a predetermined conference factory address • Join a ongoing conference • Close the call for leave

  12. Native IMS Conference Control (cont.) Third party call control (3PCC) • A Third party entity can manage a call by 3PCC • User can use 3PCC • To request other parties to create or join a conference • To request MRFC/AS to invite third parties to a conference • To request MRFC/AS expel participants from a conference

  13. Native IMS Conference Control (cont.) Event notification • An entity can subscribe to event-triggered notification from remote nodes. • User can receive conference-related information from MRFC/AS.

  14. OSA Conference API • OSA defines a framework for service developers to access the function of 3G core network in a standard, flexible and scalable manner. • Each set of related network features is grouped in a service capability function (SCF). • A SCF is implemented by several service capability servers (SCSs).

  15. OSA Conference API • SCS can be implemented by • Independent network entity • OSA gateway map API into native IMS control functions • OSA gateway takes the IMS AS role • Native function • Combination of above 2 1 3

  16. Extending IMS Conference Framework • IMS conference control framework needs to be extended with conference policy control • Conference service definition and/or customization on conference reservation/creation • Conference policy management, including media, membership, control, and information access rule manipulation • State management of active conferences, allowing full control over all conferencing conditions and comprehensive access to conference state information • Query of past conference records

  17. Extending IMS Conference Framework (cont.) Implementation options • Call-control signaling • Embedding conference control information into media streams, • Low-level conference control protocols • Be negotiated as additional media types through call control signaling • High-level conference control protocols • Be advertised in the conference information data as an additional conference service

  18. Extending IMS Conference Framework (cont.) Note • Performance Issue • Definition of an independent high-level conference control protocols on top of IMS conference • Powerful • Flexible • Scalable

  19. Reference • J. Rosenberg, “A Framework for Conferencing with the Session Initiation Protocol (SIP),” IETF RFC 4353, Feb. 2006. • 3GPP, Tech. Spec. Group Core Network and Terminals, “Conferencing Using the IP Multimedia (IM) Core Network (CN) Subsystem, Stage 3, (Release 7),” TS 24.147 v7.4.0, Mar. 2007.

More Related