1 / 24

Call Control Architecture in Integrated Media Server

Call Control Architecture in Integrated Media Server. S-38.3310 Tietoverkkotekniikan diplomityöseminaari Antti Turunen, 49971B Supervisor: Jörg Ott. Content . Objectives and scope Media Server and Terminology Call Control Architectures Java API for Integrated Networks (JAIN)

neorah
Download Presentation

Call Control Architecture in Integrated Media Server

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. Call Control Architecture in Integrated Media Server S-38.3310 Tietoverkkotekniikandiplomityöseminaari Antti Turunen, 49971B Supervisor: Jörg Ott 23.3.2010 Call Control Architecture in Media Server

  2. Content • Objectives and scope • Media Server and Terminology • Call Control Architectures • Java API for Integrated Networks (JAIN) • Call Control XML (CCXML) • Open Services Architecture (OSA) / Parlay • Evaluation • Results • Conclusions

  3. Objectives and scope • The aim is to investigate existing industry-adopted Call Control architectures for a Media Server use • The focus is on high level architectures and Call Control APIs with ability to offer media control and are independent of underlying network • The result should produce a high-level architecture proposal where Tecnotree Telco Server is integrated with Call Control API for a 3rd party service development

  4. Media Server • Media Server in telecommunications is a network entity providing multimedia processing capabilities for applications deployed to the network • Media Server implements network signaling interfaces (ISUP, SIP) and media interfaces (RTP, TDM) with support for audio and video codecs • Media Server exposes a media control protocol for applications use • Existing protocols: MSCML, MSML, VoiceXML

  5. Tecnotree Telco Server • Carrier-grade commercial Media Server product • Features • Transcoding services, advanced audio/video-conferecing with control functions, Automated Speech Recognition, Text-to-speech • Uses VoiceXML as media language • Provides ISUP / SIP network signaling interfaces • Supports multiple audio and video codecs • Multi-language component architecture

  6. Terminology:Application Server • Application Server is a network entity hosting and executing services in network • Application Server controls Media Server via control protocol (or language) • Application Server entities provide interfaces for service development

  7. Service Example:Video enrichment service

  8. Why Call Control APIs? • Traditionally services have been developed on top of user level signaling protocols • Protocol messages are mapped to functions in protocol stack implementation • APIs hide the complexity of the underlying network from the developer of the service • Application developers should be software engineers and not network engineers • Infrastructure for rapid development of services required by next generation networks • Developers use ”Call” objects modelling a real life call instead of encoded call initiation request

  9. Java Architecture for Integrated Networks (JAIN) • Originally JAIN aimed to integrate IP networks and Intelligent Network (IN) architecture • Current de facto Java architecture for providing telephony applications • JAIN protocol suite offers an API for several telephony protocols and concepts • JAIN SIP, JAIN SDP, JAIN ENUM, JAIN INAP • Strong developer community and object-oriented nature ease the service development

  10. JAIN • Java Call Control (JCC) API provides means for call control • Event / Listener design model for asynchronous events from network mapped to Call objects • JAIN Service Logic Execution Environment (SLEE) is a high-level application development environment for JAIN • Network signaling interfaces are modeled as Resource Adapters (RA) • Strong media integration with Media Server Control API (JSR 309)

  11. JAIN Architecture

  12. Call Control XML (CCXML) • Currently a working draft of World Wide Web Consortium (W3C) • XML-based scripting language for call control • Evolution of earlier XML-based telephony languages (CCML, TXML) • Tightly coupled with VoiceXML dialogs to produce Media Server integration

  13. CCXML • CCXML-scripts can be dynamically loaded by CCXML-browser in runtime analogously to HTML documents in WWW • Flexibility to provide personalized call control • Finite state machine design • Network events -> State Transitions -> Actions • A single CCXML script models state machine of the service • Inlined ECMAScript provides basic computational semantics to CCXML

  14. Open Services Architecture/Parlay API • Defined by Parlay group and 3rd Generation Partnership Project as open API for both network operators and enterprise telephony integration • Aims to be a language-neutral architecture • Provides three rationalizations: • CORBA • Web Services • Java

  15. OSA / Parlay • Multiple APIs to cover the whole area of telephony • APIs also for example mobility management, SMS services, geocoding and device management • Call Control APIs consist of 5 different parts – Service Capability Functions (SCF) • Tight Media Server integration with a separate API • One of service platform architectures in IMS • CORBA / IDL –based realization was analyzed

  16. OSA / Parlay

  17. Evaluation • Architecture / API evaluation aspects: • Capabilities • Level of Abstraction • Extensibility • Scalability • Security • Industry-adoptedness • Adaptability • Programmability

  18. Evaluation • Table of high-level evaluation results:

  19. Results • All architectures function more or less in the same level of abstraction • Object-oriented nature of programming gives more power of expression while XML provides dynamic loading of logic • Offered feature set nearly similar • Media Server integration differs: • CCXML coupled tightly with Voice XML dialogs • OSA Parlay offers a separate IDL API • JAIN can apply Java Media Control API (JSR 309)

  20. Results • All architectures have gained rather mild success – not a single leader • Different usage found for the architectures • JAIN suitable for Java-based platforms and environment • Parlay API in large distributed network operators systems with enterprise integration along with IMS • CCXML in conference servers and VoiceXML dialog integration

  21. Results • Implementation work estimates of architectures might grow to huge • The future realization of the Call Control architecture: • Proposed architecture for Tecnotree Telco Server encourages to apply a CCXML-based call control architecture adjacent to existing VoiceXML dialog engine for 3rd party development support – serves the need best

  22. Conclusions • Ongoing convergence of traditional PSTN networks and IP networks increase the need of Media Server as enabler of media processing • Advanced call control needed especially in conference servers and applications requiring third party call control (i.e. call centers) • A single prevailing de facto Call Control API does not exist – All existing solutions offer only compromizes • The myth of IMS: along with more intelligent handsets and the spectrum of services in the Internet, network operators’ role could be reduced only to transport service providers

  23. Questions?

More Related