Integration of SIP protocol in Android Media Framework EUROCON - International Conference on Computer as a Tool (EUROCON), 2011 IEEE April 2011, PP1 - 4 Advisor : Lian-Jou Tsai Student : Kuo-Sheng Hung Date : 2013/03/27

最近研究方向 Android 在 SIP 協定上的相關應用

Outline Abstract INTRODUCTION ANDROID PLATAFORM Android Media Framework Streaming Protocols INTEGRATION OF SIP PROTOCOL IN OPENCORE FRAMEWORK CONCLUSION

Abstract Based on the current Android Media Framework, this paper presents a possible architecture for the integration of the SIP protocol. The integration of this architecture is to surpass the limitations of the current Android platform and promote an improved performance in the current SIP applications, which is reflected in a lower power consumption of the device.

INTRODUCTION(1/2) Currently, the Android platform uses the Real Time Streaming Protocol RTSP for streaming in real time. Its ability to manipulate a media (pause, play, stop, etc.), makes this protocol an excellent choice for watching a stream.

INTRODUCTION(2/2) The paper is organized into three sections: Describes the Android platform Presents a new architecture for the integration of SIP on OpenCore framework The conclusion of some of the most important aspects that are needed for integrating the proposed architecture is drawn.

ANDROID PLATAFORM The Android platform, currently belonging to the Open Handset Alliance, is a complete suite of open source softwar (operating system, middleware and base applications) designed to run on low power devices (Mobile Phones, PDAs, Tablet PCs). Besides the base set of software that makes the device functional, the Android platform offers an API (Android Software Development Kit) to support the development of third party applications.

Android Media Framework The Media Player Service is an Android system service. This service is divided into four components: Media Recorder Service, where the camera image is captured and manipulated (photo and video); Vorbis and MIDI libraries, where every type of MIDI media and Vorbis is handled, respectively; The OpenCore library, where all other media types, supported by the Android platform, are treated.

OpenCore OpenCore is a Framework for the development of media applications, providing features such as playback, streaming and recording (audio and video). Figure shows a high-level architecture of the OpenCore Framework. Its architecture is divided into five layers, which are composed of six components: Content Policy Manager, Multimedia Engines, Data Formats, Audio Codecs, Video Codecs and Android Interface.

Streaming Protocols(1/2) As previously described in the data format layer, the OpenCore Framework supports the protocols HTTP and RTSP for streaming media.

Streaming Protocols(2/2) As can be seen in Figure, the Data Format layer contains several nodes that are responsible for reading or recording media. The different types of nodes available in the Android OpenCORE are compiled in the form of libraries on the system and are loaded at runtime.

INTEGRATION OF SIP PROTOCOL IN OPENCORE FRAMEWORK(1/3) The OpenCore framework is platform independent, so it can not depend of external factors when using the SIP protocol on its sessions. The SIP protocol must be integrated directly on the structure of the OpenCore framework and not as part of the Android architecture. Hierarchically, the protocols RTSP and SIP are located in the data layer, which is responsible for handling the information to be decoded and reproduced.

INTEGRATION OF SIP PROTOCOL IN OPENCORE FRAMEWORK(2/3) As we can see in Figure, the new SIP Node is located in the data layer, and is a subcomponent of the Streaming Node. Simply put, when it is necessary for the OpenCore media Framework to start manipulating the media, the data layer is then responsible for the manipulation of data for playback.

INTEGRATION OF SIP PROTOCOL IN OPENCORE FRAMEWORK(3/3) With the integration of the proposed architecture, it is expected that applications using the SIP protocol for the establishment of multimedia sessions can take advantage of all the potential of the OpenCore media Framework. It is expected a reduction in energy consumption and an increase performance for the devices.

CONCLUSION The integration of SIP in the Android Media Framework as a protocol for establishing media sessions, brings new capabilities to the multimedia world of these new devices. Another advantage of integrating the SIP into Androids media service, is the reuse of libraries for the encoding and decoding of media for the OpenCore Framework.

REFERENCES [1] H. Schulzrinne, A. Rao, and R. Lanphier. Real Time Streaming Protocol (RTSP). RFC 2326 (Proposed Standard), April [2] J. Rosenberg, H. Schulzrinne, G. Camarillo, A. Johnston, J. Peterson, R. Sparks, M. Handley, and E. Schooler. SIP: Session Initiation Protocol. RFC 3261 (Proposed Standard), June Updated by RFCs 3265, 3853, 4320, 4916, 5393, 5621, 5626, [3] M. Handley and V. Jacobson. SDP: Session Description Protocol. RFC 2327 (Proposed Standard), April Obsoleted by RFC 4566, updated by RFC [4] N. P´assaro, A. Pinto, M. Ricardo, T. Mota, F. Pinto, T. Almeida, J. Gonc¸alves. ”Management of User Generated Multicast Sessions in IMS-Based Networks” Third International Conference on Next Generation Mobile Applications, Services and Technologies, September [5] J. Chen, ”An introduction to android”. Google I/O Sessions, May [6] P. Brady, ”Android anatomy and physiology”. Google I/O Sessions, May [7] D. Sparks, ”Mastering the android media framework”. Google I/O Sessions, May [8] PacketVideo Corporation, ”Opencore multimedia Framework capabilities”. OHA 2.07, rev 2, December 15, May [9] J. Tapia, J. Kosmach, D. Veselinovic, G. Sherwood and R. Neff, ”Introduction to the opencore audio components used in the android platform”. In AES 34th International Conference, Jeju Island, Korea, August 2008.