`
`SONY EXHIBIT 1017- Page 3
`
`
`
`network interface
`
`movie archive
`
`home
`viewer
`
` user interface
`
`
` high-speed
`
`and display
`
`local database
`
`movie archive and movie distributor
`
`Figure 1: A Distributed Database Scenario for VOD
`
`Using this system model we seek to support infor-
`mation access and delivery services for interactive mul-
`timedia applications. To this end, we investigate ser-
`vice mechanisms for building such applications which
`require location, identification, and delivery of mu]-
`timedia data. More specifically, we examine services
`for retrieval of distributed multimedia data in a client-
`server architecture in which a server coordinates differ-
`
`ent client requests. We also present an experimental
`prototype we have developed in our laboratory which
`demonstrates a subset of the aforementioned concepts.
`The remainder of this paper is organized as follows.
`In Section 2, we develop our query architecture based
`on the concept of resource and metadata servers. Sec-
`tion 3 describes the application of these concepts in
`the context of a client—server VOD architecture.
`In
`
`Section 4, we describe the prototype testbed we have
`built in our lab. Finally, Section 5 concludes the pa-
`per.
`
`2 Services for Supporting Interactive
`Multimedia Applications
`
`A critical issue in the design of multimedia infor-
`mation systems is the data distribution architecture.
`Due to the enormous volumes of data involved, it is
`unwieldy to completely store and manage all informa-
`tion distribution from a single site. Furthermore, the
`interactive nature of the queries to the database re-
`quires the database manager to provide both database
`management and continuous media delivery function-
`ality.
`Services required to support interactive multime-
`dia applications include data distribution, metadata
`management, and resource management. These are
`
`described in the following subsections.
`
`2.1 Metadata Management
`
`To simplify the query mechanism, and increase in-
`teractivity, Inost database systems employ a “meta-
`data” mechanism. Metadata are “data about data.”
`
`In our context, this means that they contain concise
`information about the location and characteristics of
`
`the data to be retrieved (e.g., movie titles, where they
`are stored)
`By using such a scheme, the data deliv-
`ery process can be decoupled from the database man-
`agement functions.
`The advantage of this metadata approach is that
`it allows the user examine the contents of a database
`
`without necessitating the retrieval of the actual data
`objects. The user can quickly go over an information
`summary and select the information to be delivered.
`This concept is particularly appealing with respect to
`stored audio and video which can be costly to deliver
`and can consume significant portions of a data server’s
`I/O bandwidth.
`There are several requirements for the metadata
`management scheme necessary to support interactive
`multimedia applications. First, we require basic ser-
`vices to support object identification, location, nam-
`ing, and distribution
`Second, application-specific
`models are required to support application functional-
`ity (e.g., searches on movie scene content). In the for-
`mer, we can also consider the limitations of available
`I/O bandwidths for individual storage devices at data
`servers. For example, this limitation can be managed
`by a central site in the form of a resource state-table
`for sessions in progress (e.g., movies played out off a
`specific server). The attributes managed by the cen-
`tral site include:
`location, availability, current state
`
`12
`
`SONY |~'.XH H '1 101/— Page 4
`SONY EXHIBIT 1017- Page 4
Accessing this document will incur an additional charge of $.
After purchase, you can access this document again without charge.
Accept $ Charge
Still Working On It
This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.
Give it another minute or two to complete, and then try the refresh button.
A few More Minutes ... Still Working
It can take up to 5 minutes for us to download a document if the court servers are running slowly.
Thank you for your continued patience.
This document could not be displayed.
We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.
Your account does not support viewing this document.
You need a Paid Account to view this document. Click here to change your account type.
Your account does not support viewing this document.
Set your membership
status to view this document.
With a Docket Alarm membership, you'll
get a whole lot more, including:
- Up-to-date information for this case.
- Email alerts whenever there is an update.
- Full text search for other cases.
- Get email alerts whenever a new case matches your search.
One Moment Please
The filing “” is large (MB) and is being downloaded.
Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.
Your document is on its way!
If you do not receive the document in five minutes, contact support at support@docketalarm.com.
Sealed Document
We are unable to display this document, it may be under a court ordered seal.
If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.
Access Government Site
