SmartMediaNetworkweekstatus.pptVIP

Smart Media Network 1.0 week12 status Controller Team Server Team Device Team Server Team LDAP server based on OpenLDAP Can run on very minimal PC (Pentium I, 166Mhz, 64MB, 2GB) LDAP server modified to expire devices that do not re-register Open problem: how to do LDAP server discovery? LDAP Schema Devices and Controllers register themselves, re-register frequently Devices publish their capabilities and controls Capabilities include supported classes of functionality and stream types supported Controllers publish the fact that they exist (for receiving event notifications) Devices PLAYERS Can generate a stream Controlled by controllers using controls that the device publishes (some may have fixed semantics, some not) PRESENTERS Can accept a stream and render it in human-usable form (e.g. to a video monitor, to speakers) Can be controlled by a controller or by a player device Device Team Audio: XMMS plugin (Icecast backend) to do Shoutcast streaming MP3 Video: VideoLan MPEG-2 streams with Perl scripts to control interaction with SMN to spawn/kill clients, change controls Player/presenter architecture: when player receives a PLAY message it queries LDAP server then controls presenter with the controls it gets Devices, cont’d Uses C++ for XMMS plug-in Testing GUI written in Python Videolan wrappers and device publishers written in Perl OS used is Linux: Redhat 7.3 and 8.0 Java Media Frame (JMF) In Pervasive and Mobile computing Window Media Player / JMF Window Media Player (WMP) Stable, easy control Longer initial time Use Java.awt.Robot to simulate the control event Difficult to update to new version / license issue JMF Construct a player by our own Easy control Short initial time Platform independent WMP and JMF can based on the same server and controller System structure using JMF Controller design Streaming media between devices JMF Supports Real-Time Transport Protocol Capture and transmit real-time video Present media files remotely More available an