1. CHAPTER 5: MULTIMEDIA DATABASE MANAGEMENT SYSTEM ARCHITECTURE TOPIC : 5.1 DISTRIBUTED MULTIMEDIA DATABASE MANAGEMENT SYSTEM ARCHITECTURE GROUP MEMBERS: MAHIRAH BINTI YUSUFAI080228 ZULAIKA AK ZAINAL ABIDINAI080286 MASLINDA BINTI SAIDCI080044 CHANGGAN NARSINAI080303

2. ARCHITECTURAL CONSIDERATIONS  C-S System  Peer-to-Peer System  MPEG-21-Based Architecture

3. C-S System  In this system, client applications request multimedia data from the server, which are then processed locally.  This architecture minimizes the degree of parallel processing that can occur because of the synchronous nature of the request function.  It is a common experience that pure C-S systems do not scale well with respect to the number of users, the heterogeneity of the terminals employed, and the size of the data requested

4.  Client-server-based multimedia system

5. Client-server-based multimedia system with different profiles

6. Peer-to-Peer System  To allow greater flexibility, multimedia systems evolve from pure C-S system to peer-to-peer (P2P) systems with the notion of a "user," which is defined in MPEG-21 as an entity to consume and to produce digital multimedia items.  To allow greater flexibility, multimedia systems evolve from pure C-S system to peer-to-peer (P2P) systems with the notion of a "user," which is defined in MPEG-21 as an entity to consume and to produce digital multimedia items.  A P2P architecture is shown as in Exhibit 5.3, where portable devices with various capabilities send and transfer multimedia content from one device to another.  A P2P architecture is shown as in Exhibit 5.3, where portable devices with various capabilities send and transfer multimedia content from one device to another.  Exhibit 5.3 shows a PDA user, a mobile phone user, and PC users consuming content from the multimedia storage server but also communicating with each other, including making phone calls, sending e- mail, images, music, and videos to the other, although the terminal capability is quite different from PDAs to mobile phones or PCs.

7. Such a system must provide peer-to-peer services which may have the following functions: 1. To hold the content from the creation to the delivery. 2. To check the capability of the other peer party and see whether it can process the multimedia data before delivering. 3. To create metadata (e.g., in the form of a MPEG-21 Digital Item [DI]) to describe content received from the users Peer-to-peer-based multimedia system

8.  They concern mainly the realization of generic information communication between peers.  A set of open peer-to-peer protocols that allow any connected device on the network to communicate and collaborate in a peer- to-peer manner has to be defined.  All the negotiation messages will sit on top of the generic peer- to-peer communication protocols that are uplayers of physical network protocols.

9.  In a peer-to-peer multimedia environment, mobile agents are an important paradigm.  Mobile agents is a process that can transport its state from 1 environment to another.  The great advantage of a mobile agent is that it is simultaneously a client and a server.

10.  Natural applications in distributed MMDBMSs are multiuser applications, such as video conferencing, network management, and distributed search.  Therefore, several works recently attempted to integrate mobile agent technology into distributed MMDBMSs.

11.  mobile agent system was developed on top of the multimedia extension of Oracle 9i that allows the execution of personal multimedia-searching algorithms in the core of the Oracle database.  The system uses the JServer functionality of Oracle 9i, including its CORBA services, which are provided by a VisiBroker CORBA ORB.

12. MPEG-21-Based Architecture

13. Peer-to-peer-based multimedia system relying on MPEG-21.

14.  The Multimedia Database holds a collection of MPEG-21 Dis.  DID contain: DI identification(s) for describing the item,DI identification(s) for describing the item, DI adaptation(s) for describing its quality of service characteristics andDI adaptation(s) for describing its quality of service characteristics and Rights Expression Language (REL) descriptor(s) for describing its usage rights.Rights Expression Language (REL) descriptor(s) for describing its usage rights.  The Web server is the front end for all users to the framework providers. It serves several needs, including the following: SearchingSearching Uploading and downloading DIsUploading and downloading DIs PurchasingPurchasing ControllingControlling

15.  The MPEG-21 terminals where users consume and create DIs for the use in the distributed system.where users consume and create DIs for the use in the distributed system. could be a Web browser application, a media player, or potentially a media recorder.could be a Web browser application, a media player, or potentially a media recorder. contains software to upload or download content, buy or sell licenses, activate the on-demand media streamer, or tune into a broadcast session.contains software to upload or download content, buy or sell licenses, activate the on-demand media streamer, or tune into a broadcast session.  A media streamer streams content to a user for immediate consumption.streams content to a user for immediate consumption. can stream on a one-to-one connection, as in on-demand (pull) applications, or it can broadcast (push).can stream on a one-to-one connection, as in on-demand (pull) applications, or it can broadcast (push). In both cases, resources will usually be protected, and only licensed users can play it.In both cases, resources will usually be protected, and only licensed users can play it.

16.  In a peer-to-peer manner, the terminal may create DIs, too. For instance, the user creates the resource with available media recorder and then generates descriptions for the resource.  These descriptions include the identification in the form of the DI Identification, information for adaptation engines in the form of DI adaptation, and the rights associated to the resource in the form of a REL description.  The resource and the descriptions are bundled in the DID and are uploaded to the Web server for further use in the system; for example, to be stored in the database or delivered directly to another user.