System, method, and computer program product for presenting multimedia objects, including movies and personalized collections of items

Description

DESCRIPTION
1. Technical Field
The present invention relates generally to data linking and presentation, and more particularly to linking and presenting movies with their underlying source information.
2. Related Art
The Information Age that currently exists has produced incredible amounts of data that are currently unavailable to the public. In many cases, the producers of such information would be more than willing to provide the information to the public for some reasonable fee, and the public would be willing to pay this fee. Typically, however, these information producers (also called information providers) are not able to take advantage of this significant business opportunity due to the problems inherent in providing the information to the public.
One problem relates to the medium in which the information is stored. Today, information is stored on paper, on film, on video, on compact disks, on magnetic tapes, on computer floppy disks, etc. Information related to a particular topic may be stored on any combination of these storage mediums. In order to provide information on that topic to an user, it would be necessary for an information provider to identify and locate all items containing information related to the topic, and then transport these items to the user. The value of these items to the user is questionable, since the user probably does not possess the equipment needed to access the information stored in all of the items. Accordingly, it is difficult to provide information to users because such information is stored in many different storage mediums.
A more significant problem results from the sheer volume of information relating to any particular topic. Such information is of little value to an user unless the user is able to efficiently and expeditiously make use of the information. For example, suppose that the user is reviewing a document written by an author and decides that it would be interesting to study other works the author has had a part in creating. The information provided to the user from the information provider will be of little value unless the user is able to efficiently, effectively, and expeditiously traverse the information and locate the data on the author of interest.
These above-described commercial opportunities associated with the dissemination of information, and the problems that prevent such commercial opportunities from being realized, shall now be described more concretely by considering a real-life example: the motion picture industry.
Viewing a movie via a theatrical presentation today involves travelling to the theater, waiting in line to buy a ticket, choosing a seat, and waiting for the movie to begin. The viewer's schedule must match that of the theater. Once the movie has started, the viewer must watch promotional previews of other films before watching the feature film. During the presentation, the viewer has no control over the sound volume or presentation flow. When the movie is over, the viewer travels back home. The picture quality and sound are excellent, and the viewer enjoys the best viewing experience possible today. However, these benefits are obtained only at the expense of convenience and viewing control. Thus, commercial opportunities exist in electronically transferring movies to viewer's homes.
The technology to electronically transfer movies to viewer's homes exists today. Viewing a movie over a conventional network or premium channel broadcast is simpler and more convenient, but the viewer has fewer movie choices and enjoys a more limited quality experience. Like a theatrical viewing, the viewer's schedule must match that of the broadcast and the viewer does not control the presentation flow. There is no travelling involved, and the cost is generally less than that of a theater experience. The video and audio quality are dependent on the viewer's television and sound system. Note that, with this viewing option (and also with the theatrical presentation option discussed above), the viewer is typically not provided with any supplemental information about the movie, such as information about the making of the movie, interviews with the director and cast members, information on the actors, information about special effects, etc.
Alternatively, a person can watch a movie by renting a video tape or laser disk. Watching a movie in this manner involves two trips to the rental shop, a search of their available titles, a wait in line, and a rental fee. The viewing experience is improved over that of a broadcast presentation, as the viewer has some presentation controls (pause, fast forward, rewind, etc.). A laser disk may also offer supplemental information about the film. Parallel audio tracks may be included containing, for example, director commentary. Separate chapters of video may also be provided. However, there is no ability to play video content from different chapters simultaneously. The cost is generally higher than that of a network broadcast. Cost comparisons to that of a premium channel are dependent on usage patterns (flat fee versus fee per rental).
A mid-90s `near video on demand` viewing experience represents something between that of broadcast movies and a VCR/laser disk. A viewer selects a movie from an expanded broadcast rotation (generally a much smaller collection than that available at a VCR rental outlet). The viewer must wait a few minutes until the next rotation of the movie broadcast. A purchase request via remote control or an 800 number is required to enable viewing. Once the presentation has begun, the viewer has a limited range of controls over the presentation flow. If the movie is paused, the viewer must wait until the next instance of the movie at that point is available in the rotation. This latency is dependent on the number of channels available and the collection size configured by the viewer's cable carrier, and is typically about five minutes. No travel is required, and the per use fee is typically added to the viewer's monthly cable bill. Supplemental information about the movie is typically not available.
A mid-90s `true video on demand` viewing experience is effectively like that of a VCR rental, without two trips to the rental outlet. A digital movie server and ITV infrastructure are used to enable the viewer to select a movie from a large collection of all digitized films available on the server. The available selection list is not restricted by a broadcast rotation, and each viewer has full and immediate control over their movie presentation. Like `near video on demand,` a purchase request via remote control or an 800 number is required to enable viewing. The per use fee is typically added to the viewer's monthly bill, and supplemental information is typically not available.
Thus, the current options for viewing a movie are limited because they are inconvenient (the viewer must travel to the theater or to the video store), and/or provide the viewer with little or no presentation flow. Also, these current viewing options are limited because they provide the viewer with little or no supplemental movie information. Thus, the motion picture industry is not taking advantage of the potential commercial opportunities associated with providing supplemental movie information to viewers. Even in those cases where supplemental information is provided, the viewer has little control over how such supplemental information is presented. Accordingly, the supplemental information is available only in a limited way to videophiles who are willing to pay extra for "special" or "director's cut" editions of the titles.
DISCLOSURE OF INVENTION
The present invention is directed to a system and method for providing on demand access to information related to a movie while the movie is being presented to a user, where the movie was generated from the movie related information. The invention operates by presenting the movie to the user, and then receiving from the user a query pertaining to the movie. The invention determines a frame of the movie that was being presented to the user when the user issued the query (the invention may extract this information from the query, or may extract this information from the movie itself). The invention identifies, as specified by the query, portions of the movie related information relating to the frame, and retrieves those portions of the movie related information. These retrieved portions of the movie related information are presented to the user.
The present invention is also directed to a system and method for enabling a user to create, modify, and utilize a personalized version of a movie. The system includes a foundation information database which stores movie related information used to generate the movie. This embodiment of the invention operates by enabling the user to modify a copy of an edit decision list associated with the movie. The edit decision list includes an entry for each scene, clip, and take in the movie. The modified edit decision list defines the personalized version of the movie. The personalized version of the movie is presented to the user in response to a request to do so from the user. Such presentation operates by retrieving an entry from the modified edit decision list, retrieving from the foundation information database one or more digitized frames specified by the retrieved entry, and presenting the digitized frames to the user.
In a similar manner, the present invention is directed to a system and method for enabling a user to create, modify, and utilize a personalized collection of items. This embodiment of the invention operates by enabling the user to modify a personalized collection table, where the personalized collection table defines the personalized collection and has an entry for each item in the personalized collection. The personalized collection of items is presented to the user in response to a request to do so from the user. Such presentation operates by retrieving an entry from the personalized collection table, retrieving from the foundation information database foundation information specified by the retrieved entry, and presenting the retrieved foundation information to the user. The items contained in the personalized collection include any combination of shots, takes, scenes, clips, audio segments, etc.
Further, the present invention is directed to a system and method for providing on demand access to merchandise information related to a movie, and for providing on demand connectivity to merchants, while the movie is being presented to a user. This embodiment of the invention operates by presenting the movie to the user, receiving from the user a merchandise related query pertaining to the movie, and determining a scene of the movie that was being presented to the user when the user issued the query. Portions of movie related information relating to merchandise appearing in the scene are identified and retrieved. These portions of movie related information are then presented to the user. The invention enables the user to interact with any merchant who provided any merchandise appearing in the scene in response to a request from the user to do so.

Further features and advantages of the present invention, as well as the structure and operation of various embodiments of the present invention, are described in detail below with reference to the accompanying drawings. In the drawings, like reference numbers indicate identical or functionally similar elements.
The foregoing and other objects, features and advantages of the invention will be apparent from the following more particular description of (a) preferred embodiment(s) of the invention, as illustrated in the accompanying drawing(s).
BRIEF DESCRIPTION OF FIGURES
The present invention will be described with reference to the accompanying drawings, wherein:
FIG. 1 is a block diagram of a preferred embodiment of the present invention;
FIG. 2 is a block diagram of a computer system representing a preferred implementation of many components of the present invention;
FIGS. 3 and 4 are data flow diagrams depicting the manner in which foundation and index information is generated according to a preferred embodiment of the present invention;
FIGS. 5 and 6 illustrate example index information contents;
FIG. 7 illustrates the pedigree of a frame;
FIG. 8 illustrates an example source table;
FIGS. 9A, 9B, 11, 15, 17A, 18, 19, and 21 are flowcharts depicting the operation of the present invention;
FIGS. 10A-10C, 12A, 12B, 13A, 13B, 14A, 14B, 17B, 20, 22A, and 22B are example index tables; and
FIG. 16 is a block diagram of a manager according to a preferred embodiment of the present invention.

BEST MODE FOR CARRYING OUT THE INVENTION
The present invention is directed to a system and method for organizing information, and for providing services to enable users to efficiently, effectively, and expeditiously access such information. In other words, the present invention provides services to enable users to access information in an intelligent, user-driven manner.
For illustrative purposes, the present invention is sometimes described herein in the context of information produced by the motion picture industry. That is, the present invention is described as a system and method for organizing movie and supplemental movie information, and for presenting such movie and supplemental movie information to users. It should be understood, however, that the present invention is not limited to this embodiment (call the "movie environment" for reference purposes). Instead, the present invention is applicable to any environment where information is produced, and where a commercial opportunity exists with the organization and presentation of such information. For example, the present invention is applicable to computer programming environment where information about the person who wrote a program, the company that sold the program, the place the program was written and tested, etc., could be linked to a running program.
The movie embodiment of the present invention is preferably realized through a combination of a `true video on demand` infrastructure, database technology, and other specialized digital servers. By tightly coupling databases to specialized digital servers for video, audio, still image, text, etc., a novel level of control of movie presentation is achieved. Additional information about a movie is stored and managed, to permit a viewer to more effectively explore and understand movies. The combination of greater control and additional information permits the viewer to experience a new level of richness and entertainment from movies.
Accordingly to the movie embodiment, text, still image, and audio information is directly related to specific movie scenes or frames. This level of association, coupled with a database, permits a greater level of direct access to movie information than previously possible. Searching and correlation of supplemental information (also called side information) permits the examination of different side information relationships, and permits the following sample actions not existing in conventional viewing technologies:
1. List the names of the actors, other credited roles, or scene technical detail for the current scene (e.g., director, producer, musical score, shot location, blue screen, matte, etc.).
2. List other movies, TV shows, or other scenes in the current movie with one or more properties equal to those found above.
3. List all scenes including a specific product tie-in (i.e., product brand name used in movie).
4. Save any of these lists for viewing selection.
5. View scene while listening to voice overs of director or actor with their comments about the scene.
6. View stills with pan and zoom controls, to examine fine detail.
7. View movie at desired censor level.
8. View script or staging information via picture in picture.
9. View outtakes for the current scene.
10. View signing (i.e., sign language) via picture in picture.
11. Search other stills for like colors, shapes, or textures.
12. Search the script for a word or phase.
13. Search other scripts for like words or phrases.
14. Layout a movie presentation box, with areas for displaying related information of interest.
15. View a movie through a presentation box, to concurrently view the movie and related information of interest.
In addition to these queries predominately based on script and editing linkages, queries can be made on non-text factors. Metrics extracted from the video, audio, or stills are also managed by the database, and are used to form non-text searches against these data. This scheme can be used to search for non-text aspects such as cut boundaries and movies having similar soundtracks.
The movie embodiment of the present invention also permits the examination of movie detail beyond that viewable through a TV or HDTV. Feature films are today captured principally on high grade film, affording fidelity far beyond that viewable on TV or HDTV. The present invention permits a viewer to pan and zoom, to examine finer detail in a movie or image still.
By using the movie embodiment of the present invention, film makers are afforded a new level of flexibility in optional viewing and associations from within their films. Alternate plot lines, cuts, or censor levels are much more easily constructed, because the film components are manipulated independently. Composition is directed through the database, easing the construction of alternate presentations and linkages.
STRUCTURE OF THE PRESENT INVENTION
The present invention shall now be discussed more generally with reference to FIG. 1, which illustrates a block diagram of a data processing environment 102 of the present invention. This environment 102 includes a plurality of user devices 106 representing, for example, set top boxes (STB) in combination with television monitors, or computers (such as personal computers). The user devices 106 each include a mechanism (such as a keyboard either integrated into the user devices 106 or contained in a remote control unit) for receiving control and information messages from human operators.
Each user device 106 also includes a well known transmit and receive component to transmit and receive control and information signals from other devices via a communication medium 124. Preferably, the communication medium 124 represents a data communication network, such as a local area network or a wide area network, in which case the environment 102 represents a distributed computing environment. However, the present invention is not limited to this connection scheme. For example, some of the devices shown in FIG. 1 may be positioned locally to each other, and/or some of the devices in FIG. 1 may be implemented using a single computer. In sum, any mechanism or scheme for connecting the devices shown in FIG. 1 is within the scope and spirit of the present invention.
The environment 102 also includes a foundation information interface component 108 that controls access to foundation information in a foundation information database 112. (As shown by line 110, the foundation information interface component 108 is preferably directly connected to the foundation information database 112.) The term "foundation information" is used herein to refer to information that has been produced by one or more parties (each party being a person or organization). According to the present invention, the foundation information represents digital information only. The present invention provides foundation information on demand to users via the user devices 106. With respect to the movie embodiment, the foundation information represents, for example, a movie and supplemental information pertaining to the movie (i.e., additional information generated during the pre-production, production, and post-production stages of the movie). The foundation information is described in greater detail below.
Preferably, the foundation interface component 108 represents a relational database management system (RDBMS). The foundation information database 112 preferably represents a file server. The foundation information database 112 may be distributed for performance reasons (i.e., to position foundation information closer to the user devices 106 so that communication performance is enhanced), in which case there would be multiple foundation information interface components 108 and multiple foundation information databases 112 (for simplicity purposes, only one foundation information interface component 108 and one foundation information database 112 are described).
An index interface component 118 controls access to index information in an index information database 122. (As shown by line 120, the index interface component 118 is preferably directly connected to the index information database 122.) This index information represents indices of the foundation information in the foundation information database 112. Accordingly, the organization of the foundation information is established by the index information. The present invention uses the index information to locate and reference particular foundation information. The index information is discussed further below.
Preferably, the index interface component 118 represents a relational database management system (RDBMS). The index information database 122 preferably represents a file server which has special searching capabilities or another relational database management system (RDBMS). The index information 122 may be distributed for performance reasons, in which case there would be multiple index interface components 118 and multiple index information databases 122 (for simplicity purposes, only one index interface component 118 and one index information database 122 are described).
The environment 102 further includes a presentation and control component 104. The functionality of the presentation and control component 104 may be distributed, in which case there would be multiple presentation and control components 104. For simplicity purposes, only one presentation and control component 104 is discussed. The presentation and control component 104 coordinates the actions of the user devices 106, the foundation information interface component 108, and the index interface component 118.
In particular, the presentation and control component 104 receives information requests from the user devices 106. The presentation and control component 104 processes these information requests by accessing the index information in the index information database 122 (via the index interface component 118) to identify and locate the particular foundation information indicated by the user requests. The presentation and control component 104 then retrieves this foundation information from the foundation information database 112 (via the foundation information interface component 108), and presents this foundation information to the users via the user devices 106. In an alternative embodiment, any or all of the functionality of the presentation and control component 104 is embedded in the index interface component 118 and/or the foundation information interface component 108, such that the user devices 106 (in some circumstances) communicate directly with the index interface component 118 and/or the foundation information interface component 108.
In an embodiment of the present invention, the user devices 106 are each used as the application driver in a client/server model, and makes server requests of the databases 112, 122 and digital servers through the index interface component 118 and the foundation information interface component 108 through an integrated interface. The functionality of this integrated interface is represented by the presentation and control component 104, although such functionality can alternatively be located or distributed among other modules. Through these interfaces, the digital video, audio, and still image objects stored on the digital server(s) appear to the application to be managed as data in the relational databases 108, 118.
The index information database 122 and the foundation information database 112 are preferably implemented as digital servers for at least two reasons:
1. To permit the use of specialized hardware and software to cost-effectively deliver the digital video, audio, and image stills.
2. To permit the distribution of these servers, thereby reducing the distance to the viewer and the associated latency and transmission costs.
As noted above, each user device 106 can be a full function PC, or a more limited function settop box. Depending on the hardware and software capacity of any particular user device 106, the client application executing thereon may be distributed over the user device 106 and an intermediate station emulating a full function end station. Independent of this distribution of function, the user device/intermediate station interacts with both the relational databases 112, 122 and the digital movie servers 108, 118 through the integrated interface (i.e., the presentation and control component 104).
The environment 102 also includes a cross merchant gateway 116 and a merchant transaction processor 114, which are described in U.S. patent application entitled "System and Method for Providing Merchant Information and Establishing Links to Merchants While Presenting a Movie", Attorney Docket No. ST9-94-046 (1252.1920000), referenced above.
The user devices 106, foundation information interface component 108, index interface component 118, presentation and control component 104, foundation information database 112, index information database 122, cross merchant gateway 116, and merchant transaction processor 114 are each preferably implemented using a computer system 202 as shown in FIG. 2. (Alternatively, each computer system 202 is used to implement a subset of these devices/components.) The computer system 202 includes a processor 204 (or multiple processors 204) communicating with other components via a communication bus 206.
Connected to the bus 206 is a primary memory 208 (such as random access memory, RAM) which stores control logic 210 (i.e., software) and data 212 (such as a portion of the foundation information and index information, for example). During run-time, the control logic 210 enables the processor 204 to perform the functions described herein. Thus, the control logic 210 represents a controller of the processor 204. In an alternate embodiment, the functionality of the present invention described herein is achieved using a hardware implemented state machine.
The computer system 202 also includes secondary memory 214, which may include a storage device 216, such as a removable disk drive (i.e., a floppy drive). A removable storage medium 218, such as a computer disk (i.e., a floppy disk) can be inserted in the storage device 216. The control logic 210 is stored in direct computer readable form (i.e., magnetically or optically) on a storage medium (i.e., magnetic storage medium) in the removable storage medium 218.
Also connected to the bus 206 is a network interface 222, which provides connectivity to the communication medium 124 shown in FIG. 1.
Source, Foundation, and Index Information
The present invention also includes a manager 1602 which is shown in block diagram form in FIG. 16. The manager 1602 includes one or more capture and digitizer components 304 (for simplicity purposes, only one is described), one or more index generation components 308 (for simplicity purposes, only one is described), a personalized presentation manager 1604, and a personalized collection manager 1606. The manager 1602 and its components 304, 308, 1604, 1606 are preferably implemented using one or more computer-based devices operating in accordance with instructions from computer software (as shown in FIG. 2). Alternatively, the functionality of at least portions of the manager 1602 (as described herein) is achieved using predominately hardware, such as a hardware implemented state machine.
The personalized presentation manager 1604 and the personalized collection manager 1606 are discussed below. The capture and digitizer component 304 and the index generation component 308 shall now be described.
The capture and digitizer component 304 and the index generation component 308 are used to generate the foundation information that is ultimately stored in the foundation information database 112, and the index information that is ultimately stored in the index information database 122. The detailed operation of the capture and digitizer component 304 and the index generation component 308 shall now be described with reference to a data flow diagram shown in FIG. 3.
The capture and digitizer component 304 receives source information 302. The source information 302 represents information that has been produced over time by one or more parties (each party being a person or organization), and that would be of value to some end users (i.e., those persons working at the user devices 106). This information may be stored in any number of storage mediums, such as paper, film, video, compact disk, magnetic tape, computer storage disks, etc.
An example of the contents of the source information 302 in the movie embodiment of the present invention is illustrated in FIG. 4. FIG. 4 also illustrates the process by which the source information 302 is generated in the movie embodiment.
As will be appreciated by persons skilled in the relevant art(s), a motion picture is generally produced in three phases: a pre-production phase 402, a production phase 406, and a post-production phase 410. Source information 302 is generated during each of these phases. Specifically, pre-production information 404 is generated during the pre-production phase 402, production information 408 is generated during the production phase 406, and post-production information 412 is generated during the post-production phase 410.
The pre-production information 404 includes, for example, diagrams of models, storyboards, contracts with actors and other persons and organizations associated with the movie, information on locations, versions of scripts, etc. The production information 408 includes, for example, takes, continuity sheets, department work orders, etc.
The post-production information 412 includes, for example, one or more edit decision lists 414. An edit decision list 414 specifies the scenes, takes, and/or clips that are in the theatrical version of the movie. There may be multiple versions of a movie (for example, the director's version, the unrated version, a signed version, etc.). Generally, an edit decision list 414 exists for each version.
The post-production information 412 also includes the video 416 and audio 418 associated with each version of the movie, and clock information 420 that is embedded in the video 416 and audio 418. Each frame in a movie has a time code. These time codes represent the clock information 420. The clock information 420 and time codes are discussed in greater detail below.
The edit decision list 414, video information 416, audio information 418, and clock information 420 represent primary information 492, whereas the pre-production information 404 and the production information 408 represent secondary information 490 (also called movie related information). Primary information 492 is what is normally presented and available to the public. Its creation is the purpose for performing a process such as that shown in FIG. 4. Secondary information 490 is generated for the purpose of generating the primary information 492, and/or is generated during the creation of the primary information 492, and/or is related to the primary information 492. In other words, the primary information 492 is generated from the secondary information 490. The secondary information 490 is not generally presented to or available to the public. However, often the public would be very interested in this secondary information 490, and would be willing to pay a fee to have access to it. The present invention is directed to providing the public with access to this secondary information 492 in an intelligent, user-friendly manner. Although the concepts of primary information 492 and secondary information 490 have been explained with reference to the movie embodiment, it should be understood that primary information 492 and secondary information 490 are generated in other contexts, and the present invention is equally applicable to these other contexts.
The pre-production information 404, production information 408, and post-production information 412 of the source information 302 can be stored in any number of storage mediums. For example, diagrams of models, storyboards, contracts with actors and other persons, location information, and department work orders are typically stored on paper. Scripts are also stored on paper, but may additionally be stored in electronic form on computer storage disks (i.e., floppy disks). An edit decision list 414 is stored on paper, and may additionally be stored in the electronic form used by automated offline editing tools. Takes are stored on film. Video 416 is stored on film and/or VCR tapes. Audio 418 is stored on tape, compact disks, computer storage disks, etc.
Referring again to FIG. 3, the capture and digitizer component 304 converts the source information 302 to foundation information 306. The foundation information 306 has the same information content as the source information 302, but is in digital form. Thus, the foundation information 306 is a digital, electronic representation of the source information 302.
Specifically, the capture and digitizer component 304 captures or otherwise extracts the source information 302 from the mediums on which they are stored, digitizes the captured/extracted source information 302, and stores such digitized information as the foundation information 306. Preferably, the operation of the capture and digitizer component 304 is automated to the greatest extent possible, but may require some human intervention and control depending on available technology.
The capture and digitizer component 304 includes, for example, scanners, optical character recognition (OCR) devices and processes, data compressors and decompressors, data extract and capture devices and processes, data converters, etc. The structure and operation of these devices and processes are well known to persons skilled in the relevant art(s) and, thus, shall not be described further.
In some cases, at least some portions of the source information 302 are already in digital, electronic form. Such portions of the source information 302 are directly stored as foundation information 306, as indicated by data flow line 312.
Eventually, it is possible that most or even all of the source information 302 will be available in digital, electronic form (once this occurs, the role of the capture and digitizer component 304 will be reduced or even eliminated). This is true for at least two reasons. First, the advance in computer technology is making it more and more attractive for parties to perform their work using a computer. As a result, that work is stored in digital, electronic form. Second, information generators who intend to utilize the present invention will have an incentive to store their work in digital, electronic form (the incentive being the ability to eliminate the capture and digitizer component 304).
The index generator component 308 analyzes the foundation information 306 and produces index information 310. The operation of the index generator component 308 is automated to the greatest extent possible, but may include user intervention and control (such as keying in index information). The index information 310 represents indices of the foundation information 306. Accordingly, the organization of the foundation information 306 is established by the index information 310. For example, suppose the foundation information 306 includes works by a group of authors, and articles written about those works and authors. In this example, the index information 310 may have a first table listing by author works available in the foundation information 306, a second table listing articles available in the foundation information 306 about each author, and a third table listing articles available in the foundation information 306 about each work.
With regard to the movie embodiment, and referring to FIG. 5, the index information 310 may include, for example, video indices 502, audio indices 504, text indices 506, parametric indices 508, and image content indices 510. Referring now to FIG. 6, the index information 310 in the movie embodiment includes general index table(s) 602 that pertain to all movies (such as actor biographies), and index table(s) 604, 606 specific to each movie. These tables 602, 604, 606 in FIG. 6 may each include indices as shown in FIG. 5. The index information 310 specific to the movie embodiment is discussed in greater detail below.
Video Frame Pedigree
Referring now to the movie embodiment of the present invention, FIG. 7 generally illustrates the making of a movie.
As is well known, during the production phase 406 a series of takes 710, 712, 714 are shot on film 720 (typically 35 mm film in full-frame super-35 format). Film 720 represents "negatives" and, thus, shall be called "negative film 720" for reference purposes. A take is the sequence of frames (such as frame 704) from the clap of a clapboard (when the director says "action") to when the director says "cut" or "cut and print." There are many types of takes, such as a master take, a close up (CU), an extreme close up (ECU), etc. Each take has one or more shots, such as shot 706 in take 712. A shot represents those frames in the take which are of value, and which may be used in the movie.
Each frame in the negative film 720 has an unique time code which can be tied to the start of the respective take (i.e., from the clap of the clapboard). Thus, the frames in the negative film 720 can be identified by reference to time codes.
The negative film 720 is developed and portions are printed (they are now positive) and are called "dailys." If the director ends a take by saying "cut and print," then that take is printed. Otherwise, it is not printed. FIG. 7 shows a portion of a daily 722. This daily 722 includes the shot 706 containing the frame 704. Each frame in the dailys 722 includes a unique time code. These time codes in the dailys 722 are the same as the time codes in the negative film 720 as they were copied in the printing process.
During the post-production phase 410, a theatrical presentation 724 of the movie is produced. The theatrical presentation 724 includes a sequence of scenes, such as scene 708. Each scene includes one or more shots, such as shot 706 in scene 708. The theatrical presentation 724 is typically generated by splicing together frames from the dailys, such as frame 704 from daily 722. This produces a work print of the whole movie. Using the workprint as a master, the negative film is cut and spliced to match. The cut negative is then printed to produce a timed (color corrected) positive. All the prints so far have been contact prints so the original time codes are preserved. The theatrical negative (not shown) is produced optically (to change aspect ratio, make room or sound tracks, etc.) and new time codes are assigned for the whole movie. Theatrical presentation 724 prints are made from that negative. Each frame in the theatrical presentation 724 includes an unique time code copied from the theatrical negative. These time codes are measured from the beginning of the theatrical presentation 724. Thus, the time codes in the theatrical presentation 724 differ from the time codes in the dailys 722 and the negative film 720. However, the process for converting from the time codes in the theatrical presentation 724 to the time codes in the dailys 722 and negative film 720, and vice versa, is well known.
Typically, versions of the movie other than the theatrical presentation 724 are produced. One such version is the VCR video version 702. Video runs at a different speed than film. Typically, video runs at 30 fps (frames per second) or 25 fps, while film runs at 24 fps. To compensate for this difference, additional frames are added to the shots in the VCR video version 702. For example, a shot 706' in the VCR video version 702 includes five frames, whereas the corresponding shot 706 in the theatrical presentation 724 includes four frames. Each frame in the VCR video version 702 includes an unique time code. These time codes are measured from the beginning of the VCR video version 702. Since the number of frames per shot differ in the VCR video version 702 and the theatrical presentation 724, the time codes between the VCR video version 702 and the theatrical presentation 724 also differ. However, the process for converting from the time codes in the VCR video version 702 to time codes in the theatrical presentation 724, and to the time codes in the dailys 722 and negative film 720, and vice versa, is well known.
Accordingly, it is possible to trace the lineage of any frame 704 through the negative film 720, the dailys 722, the theatrical presentation 724, the VCR video version 702, and any other version of the movie not shown in FIG. 7, by using the time code of the frame, and also by using the well known time code conversion processes mentioned above.
Source Table
FIG. 8 depicts a source table 802 according to a preferred embodiment of the present invention. A source table 802 exists for each version of a movie (i.e., the theatrical presentation, the VHS video version, the unrated version, the director's version, etc.), although the source tables 802 for different versions may be very similar to each other. In some cases, different versions may have the same source table 802.
The source table 802 is similar to an edit decision list, but the source table 802 contains information not found in a conventional edit decision list. Also, the present invention uses the source table 802 in ways that differ from the ways that an edit decision list is used. Further, according to the present invention, the source table 802 is organized and stored in electronic form. In fact, the source table 802 is part of the index information that is stored in the index information database 122.
The source table 802 specifies the scenes, takes, and/or clips that are in a version of a movie. The source table 802 contains sufficient information so that the lineage of each frame in the movie can be identified and located (an example of a frame's lineage or pedigree is shown in FIG. 7). The source table 802 represents a linkage mechanism so that foundation information 108 related to each frame can be identified, located, and retrieved from the foundation information database 112.
The source table 802 includes a row for each scene, clip, and take in the movie version. A clip is a sequence of frames taken without regard to scene, shot or take boundaries. However, it is taken from a single source with a uniform time base (such as theatrical presentation 724) so that the start time code and end time codes have unique meanings. A type code column 804 in the source table 802 identifies whether the row is a scene, clip, or take, and identifies the type of take (master, close up, extreme close up, etc.).
A first frame time code column 806 stores the time code of the first frame of the item corresponding to the row. Thus, if the row corresponds to a scene, then the first frame time code column 806 stores the time code of the first frame of the scene. The time code stored in the first frame time code column 806 is measured from the beginning of the movie version to which the source table 802 is associated. The present invention preferably uses SMPTE (Society of Motion Picture Television Experts) time codes, but other time codes could alternatively be used.
A last frame time code column 808 stores the time code of the last frame of the item corresponding to the row. Thus, if the row corresponds to a scene, then the last frame time code column 808 stores the time code of the last frame of the scene. The time code stored in the last frame time code column 808 is measured from the beginning of the movie version to which the source table 802 is associated.
A frame count column 810 stores a number that is equal to the number of frames in the item corresponding to the row. Thus, if the row corresponds to a scene, and the scene has 79 frames, then the frame count column 810 stores "79."
A source title column 816 stores information identifying the source of the item corresponding to the row. Referring to FIG. 7, suppose that the row corresponds to the take 712. The source of this take 712 is the daily 722 (actually, the ultimate source of take 712 is negative film 720, but preferably the present invention utilizes positives where possible, rather than negatives and the time codes match). Thus, information identifying the daily 722 is stored in the source title column 816. As discussed above in conjunction with FIG. 3, the images on the daily 722 were captured, digitized, and stored as foundation information 306 in the foundation information database 112. Preferably, what is stored in the source title column 816 is information sufficient to locate these digitized images of the daily 722 in the foundation information database 112 (such as a file name or address).
Note that the frames in a scene may originate from a number of sources. Thus, the source title column 816 is blank (or not applicable, N/A) for rows corresponding to scenes. Similarly, the source first frame time code column 812 and the source frame count column 814 (described below) are also blank.
A source first frame time code column 812 stores the time code of the first frame of the item identified by the source title column 816. Assume, again, that the row corresponds to the take 712 in FIG. 7. The source first frame time code column 812 stores the time code of the first frame of the take 712. The time code stored in the source first frame time code column 816 is measured from the beginning of the item identified by the source title column 816, i.e., from the beginning of the take 712.
A source frame count column 814 stores a number that is equal to the number of frames in the item identified by the source title column 816.
A "for which scene" column 818 contains information that identifies the scene in which the item corresponding to the row is used. For example, if the row corresponds to a take, then the "for which scene" column 818 contains information that identifies the scene in which the take is used. This column is blank for rows corresponding to clips.
User-Driven Operation of the Present Invention
The user-driven operation of the present invention shall now be described in conjunction with a flowchart depicted in FIG. 9A. This "user-driven" operation differs from the operation of the invention as shown in FIG. 3. Specifically, FIG. 3 illustrates the manner in which the present invention generates foundation information 306 and index information 310. The user-driven operation depicted in FIG. 9A refers to the manner in which the present invention access, retrieves, and presents foundation information 306 from the foundation information database 112 to users in response to information requests and/or queries from users.
For illustrative purposes, the user-driven operation of the present invention shall be described with reference to the movie embodiment. It should be understood, however, that the present invention is not limited to the movie embodiment. The following description is applicable when the present invention is used in other applications.
The flowchart in FIG. 9A begins with step 950, where control immediately passes to step 952.
In step 952, in response to an appropriate request from an user via an user device 106, the presentation and control component 104 transfers to the user device 106 a list of items which the user may view and/or interact with. Such items include, for example, various versions of movies, audio tracks related to movies, video games related to movies, text from books or magazines related to movies, etc. Such items also include personalized movie presentations and personalized movie collections, which are described below.
The presentation and control component 104 preferably performs step 952 by accessing the index information database 122 (via the index interface component 118) and/or the foundation information database 112 (via the foundation information interface component 108) for a listing of possible viewing choices. This list of viewing choices is transferred from the presentation and control component 104 to the user device 106 via the communication medium 124. The user device 106 displays this list of viewing choices in a well known manner.
In step 954, the presentation and control component 104 receives from the user (via the communication medium 124 and the user device 106) information identifying a particular item which the user wishes to view.
In step 956, the presentation and control component 104 accesses and retrieves the item identified by the user. In one embodiment, an Item Locator table (which may be implemented as a collection of tables) is stored in the index information database 122. The item Locator table has a row for each of the possible viewing choices. Each row stores at least (1) the name of the item (or other information to unambiguously identify the item), and (2) address information identifying the location in the foundation information database 112 where the item is stored.
The presentation and control component 104 performs step 956 by accessing the Item Locator table (via the index interface component 118) locating the row corresponding to the item identified by the user, extracting the address information from this row, and using this address information to access and retrieve the item from the foundation information database 112 (via the foundation information interface component 108). The item is transferred to the presentation and control component 104 via the communication medium 124. For example, if the item is a movie, then the digitized frames of the movie are transferred from the foundation information database 112 to the presentation and control component 104.
In step 958, the presentation and control component 104 begins to present the item to the user by transferring consecutive parts of the item to the user device 106. It is noted that the item is transferred to a location specified by the user (such as the user's home). Also, the item is preferably transferred to this location immediately after the user has selected the item. Thus, the present invention implements true video on demand.
For illustrative purposes, the following discussion assumes that the item is a movie. Thus, during step 958, the presentation and control component 104 sends the first digitized frame to the user device 106, where the frame is displayed.
In step, 960, the presentation and control component 104 determines whether it has received a query pertaining to the movie from the user (via the user device 106 and the communication medium 124). The manner in which the user sends a query is described below. If a query has been received, then the presentation and control component 104 processes the query in step 962, and then proceeds to step 964. The manner in which queries are processed are described below. Step 964 is also processed if no query was received.
In step 964, the presentation and control component 104 determines if there are any additional frames in the movie that have not yet been sent to the user. If additional frames exist, then control returns to step 958 where the next frame is sent to the user device 106. Otherwise, operation of the flowchart of FIG. 9A is complete, as indicated by step 966.
The above-described operation of the present invention can be modified in any number of ways to achieve better performance. For example, according to an alternate embodiment, the movie is sent directly to the user device 106 from the foundation information database 112, rather than being sent first to the presentation and control component 104. Also, in this alternate embodiment, the entire movie is sent to the user device 106 all at one time, rather than being sent frame by frame.
In another alternate embodiment, personalized movie presentations and personalized movie collections are retrieved from the foundation information database 112 and presented to the user according to index information contained in personalized edit decision lists. Personalized movie presentations and personalized movie collections are described further below.
Sending and Interpreting User Queries
The user can send a query to the presentation and control component 104 at any time while viewing and/or interacting with a movie (or some other item). Preferably, the user signals a query by pressing the "Pause" button provided by the user device 106 (this "Pause" button may be situated on the remote control unit, on the set top box, or on the computer keyboard, for example). By pressing the "Pause" button, the user indicates that he has a question regarding the movie, scene, cut, and/or frame that is currently being displayed. The question may be, for example, "Who is this person?," "What other movies has this director done?," "Why is the street in this street wet when it appears to be a clear day?," or "What other movies have script lines similar to what was just said?" The questions which users are allowed to ask are implementation dependent. Thus, the particular questions discussed herein are presented for illustrative purposes only, and are lot limiting.
Preferably, the user identifies his specific question by traversing an user menu hierarchy. User menus are well known. Thus, the specifics of the user menu hierarchy used to identify user questions shall not be discussed in detail.
It is noted, however, that the user menu may be driven and controlled by the presentation and control component 104 by exchanging control and data signals between the presentation and control component 104 and the user device 106. Alternatively, software control logic and/or hardware control logic can be incorporated into the user device 106 such that the user device 106 drives and controls the user menu.
Note that the question "Who is this person?" is somewhat ambiguous, in that it could mean "Who is the principle actor?," or "Who is the stunt double actor?," or "Who is the character?" In one embodiment of the invention, this ambiguity is solved by having a very detailed menu structure, so that the precise question is identified by the user. However, users may find this approach somewhat tedious.
Accordingly, to an alternate embodiment, the present invention makes assumptions as to what the users' precise questions are. For example, if the user asks "Who is this person?," the present invention may assume that the user is really asking "Who is the character in this scene?" The assumptions made by the present invention in this alternate embodiment are implementation dependent and are based on many factors, such as the context in which the question was asked, market information, surveys, empirical use, etc. For illustrative purposes, this alternate embodiment of the invention (where assumptions are made as to the user's precise question) is described below. The assumptions that are employed in the following description are used only by way of example, and may differ depending on the particular implementation.
Processing User Queries
FIG. 9B presents a flowchart depicting the manner in which the present invention processes an user query (i.e., the manner in which the present invention performs step 962 in FIG. 9A). The flowchart in FIG. 9B begins with step 902, where control immediately passes to step 904.
In step 904, the user device 106 determines the time code corresponding to the current frame (this time code is called the "current frame time code" for reference purposes). The user device 106 then transfers the current frame time code to the presentation and control component 104 via the communication medium 124. (The user device 106 may send the current frame time code such that the presentation and control component 104 receives it at the same time as receiving the user query, i.e., at step 960 in FIG. 9A.)
The "current frame" represents the frame that was being presented on the user device when the user issued the query (i.e., pressed the "Pause" button). As noted above, clock information 420 (i.e., time code information) is embedded in the video data 416 of the movie (see FIG. 4). Accordingly, in step 904, the user device 106 extracts the current frame time code corresponding to the current frame from the video data 416 of the movie being presented to the user.
The current frame time code is measured from the start of the movie (rather than being measured from a daily 722 or negative film 720, for example). Thus, time code conversions are performed in subsequent steps.
In step 906, the presentation and control component 104 accesses the index information database 122 (via the index interface component 118) and extracts from the source table 802 associated with the movie being presented (called the current movie for reference purposes) all rows where the current frame time code is greater than or equal to the first frame time code, and the current frame time code is less than or equal to the last frame time code.
In step 908, the presentation and control component 104 identifies the query type or category. This query type is indicated by information contained in the user query received in step 960 of FIG. 9A (it is assumed that the user selected a query type by traversing an user menu hierarchy, as discussed above). Each implementation of the present invention supports a set of query types. For illustrative purposes, a selected set of query types is discussed below. Other query types will be apparent to persons skilled in the relevant art(s).
In step 910, the presentation and control component 104 processes the user query according to the type of the query as identified in step 908. The manner in which the presentation and control component 134 processes a selected set of query types is discussed below. The processing of other query types will be apparent to persons skilled in the relevant art(s).
The flowchart of FIG. 9B is complete after step 910 is performed, as indicated by step 912.
Query Type: Who Is This?
This section discusses the "who is this?" query type. According to an embodiment of the present invention, the index information database 122 stores at least three index tables to support the processing of this query type: an Actor In Take table 1002, a Character In Scene Table 1012, and an Actor Play Character table 1018. These tables 1002, 1012, 1018 represent movie specific tables, and are shown in FIGS. 10A-10C.
The Actor In Take table 1002 includes at least one row for each actor appearing in each take. An actor column 1004 stores the name of the actor, a take title column 1006 stores the name of the take, a start time code column 1008 stores the time code of the first frame of the take in the current movie, and the end time code column 1010 stores the time code of the last frame of the take in the current movie. The time codes in the start time code column 1008 and the end time code column 1010 are measured from the start of the current movie. Information for the Actor In Take table 1002 is derived by the index generator component 308 by reference to production schedule information (that is part of the production information 408).
The Character In Scene table 1012 includes a row for each character who appears in each scene. A scene column 1014 stores the name of the scene, and a character column 1016 stores the name of a character who appears in the scene. Information for the Character In Scene table 1012 is derived by the index generator component 308 by reference to the script.
The Actor Plays Character table 1018 includes, for each character in the current movie, a row for each actor who plays the character. A character column 1020 stores the name of the character, an actor column 1022 stores the name of an actor who plays the character, and a code column 1024 identifies the manner in which the actor played the character (i.e., as the principle actor, as the stunt double, as the body double, etc.). Information for the Actor Plays Character table 1018 is derived by the index generator component 308 by reference to the credits of the movie and the production schedule.
FIG. 11 depicts a flowchart representing the manner in which the present invention processes a "who is it?" query according to one embodiment. This flowchart begins with step 1102, where control immediately passes to step 1106.
In step 1106, the presentation and control component 104 retrieves from the Actor In Take table 1002 rows that relate to the current frame. Step 1106 is performed by reference to the rows that were retrieved from the source table 802 in step 906. Step 1106 is performed by retrieving from the Actor In Take table 1002 all rows having a start time code (from column 1008) equal to the start time code (from column 806 in the source table 802) in the take row retrieved in step 906, and also having an end time code (from column 1010) equal to the end time code (from column 808 in the source table 802) in the take row retrieved in step 906. These rows from the Actor In Take table 1002 identify the actors who appear in the current frame.
Step 1104 tests to see that at least one actor 1004 was included in that take. (It might have been a long scenery shot for example.) If no actors are found in the take, then the scope is widened to include all the characters in the entire scene and processing continues at step 1120. Otherwise, processing continues with step 1108.
In step 1108, the presentation and control component 104 transfers to the user device 106 via the communication medium 124 the names of the actors stored in the actor column 1004 of these rows retrieved from the Actor In Take table 1002. The user device 106 presents these names to the user in a well known manner.
In step 1110, the presentation and control component 104 retrieves all rows from the Actor Plays Character table 1018 associated with all actors identified in step 1106 (i.e., actors corresponding to rows retrieved from the Actor In Take Table 1002). Step 1110 is performed by reference to the actor column 1022 in the Actor Plays Character table 1018.
In step 1112, the presentation and control component 104 transfers to the user device 106 via the communication medium 124 the names of the characters stored in the character column 1020 of these rows retrieved from the Actor Plays Character table 1018. The user device 106 presents these names to the user in a well known manner.
In step 1114, the presentation and control component 104 retrieves from the Actor Plays Character table 1018 all rows with code 1024 value of "principal" related to the characters identified in step 1110 (i.e., the characters corresponding to the rows retrieved from the Actor Plays Character table 1018). Step 1114 is performed by retrieving from the Actor Plays Character table 1018 all rows corresponding to these identified characters.
In step 1116, the presentation and control component 104 transfers to the user device 106 via the communication medium 124 the names of the actors (column 1022) and their roles (column 1024) from these rows retrieved from the Actor Plays Character table 1018. The user device 106 presents this information to the user in a well known manner.
If, in step 1104, it is determined that no actor may be in the current frame, then step 1120 is performed. In step 1120, the presentation and control component 104 retrieves all rows from the Character In Scene table 1012 associated with characters appearing in the current scene. The "current scene" is the scene in which the current frame is contained, and is identified by reference to information stored in the "for which scene" column 818 in the take row previously retrieved from the source table 802 (in step 906). Step 1120 is performed by retrieving from the Character In Scene table 1012 all rows corresponding to the current scene (by reference to the scene column 1014 in the Character In Scene table 1012).
In step 1122, the presentation and control component 104 transfers to the user device 106 via the communication medium 124 the names of the characters stored in the character column 1016 of these rows retrieved from the Character In Scene table 1012. The user device 106 presents these names to the user in a well known manner. After step 1122 is performed, then control moves to step 1114, described above (although, in this case, step 1114 is performed based on the results of step 1120).
The operation of the flowchart in FIG. 11 is complete after step 1116 is performed, as indicated by step 1118.
Query Type: What Other Films Has This Director Worked On?
This section discusses the "what other films has this director worked on?" query type. According to an embodiment of the present invention, the index information database 122 stores at least two index tables to support the processing of this query type: an One Movie Credit table 1202 (which is movie specific) and an All Movies Credit table 1208 (which applies to all movies). These tables 1202, 1208 are shown in FIGS. 12A and 12B.
The One Movie Credit table 1202 includes at least one row for each person involved in the creation of the movie (for example, a row for each person listed in the credits). Each row includes a person column 1204 storing the name of the person, and a job column 1206 indicating the person's position. If a person had many jobs, then there is one row in the One Movie Credit table 1202 for each job. Information for the One Movie Credit table 1202 is derived by the index generator component 308 by reference to the credits of the movie, and also by reference to contracts (pre-production information 404).
The All Movies Credit table 1208 includes one row for each job that each person had in each movie represented in the foundation information database 112. A movie title column 1212 stores a movie's name, a person column 1214 stores a person's name, a job column 1216 stores a job that the person had in the movie, and a table identifier row 1210 stores information that identifies where other index tables specific to the movie are stored in the index information database 122. Information for the All Movies Credit table 1208 is derived by the index generator component 308 by reference to the credits of the movie, and also by reference to contracts (pre-production information 404).
The present invention processes a "what other films has this director worked on?" query type as follows. First, the presentation and control component 104 accesses the One Movie Credit table 1202 for the current movie and retrieves the row where the job column 1206 is equal to "Director." Second, the presentation and control component 104 extracts the name of the director from the person column 1204 of this row. Third, the presentation and control component 104 accesses the All Movies Credit table 1208 and retrieves all rows where the person column 1214 is equal to the director's name. Fourth, the presentation and control component 104 extracts the movie title (from the movie title column 1212) and the job (from the job column 1216) from these rows and sends them to the user device 106 via the communication medium 124. The user device 106 displays this information in a well known manner.
Query Type: When Did This Happen?
This section discusses the "when did this happen?" query type. According to an embodiment of the present invention, the index information database 122 stores at least two index tables to support the processing of this query type: a Time In Story table 1302 and a Take Details table 1312, both of which are movie specific. These tables 1302, 1312 are shown in FIGS. 13A and 13B.
The Time In Story Table 1302 has a row for each scene in the current movie. A scene column 1304 stores the name of the scene, a time since story start column 1306 that stores a value representing the time (in terms of the story) that has elapsed since the current movie started, a time since last scene column 1308 that stores a value representing the time (in terms of the story) since the last scene ended, and an absolute date/time column 1310 that stores a value that represents the date and time (in terms of the story) of the events depicted in the current scene. Information for the Time In Story table 1302 is derived by the index generator component 308 by reference to time references in the script (for example, time indicators such as "that night," "later that day," "next morning," etc.).
The take details table 1312 has a row for each take. A take title column 1314 stores the title of the take, a take first frame time code column 1316 stores the time code of the take measured from the beginning of the current movie, a location name column 1318 stores the name of the location where the take was shot, a date shot (created) column 1320 and a time shot (created) column 1322 store a date and time when the take was shot, and a method column 1324 stores information identifying the manner in which the take was shot (i.e., steady-cam, digital morph, etc.). Information for the Take Details Table 1312 is derived by the index generator component 308 by reference to the production schedule.
The present invention processes a "when did this happen?" query type as follows. First, the presentation and control component 104 identifies the current scene by reference to the "for which scene" column 818 in the take row previously retrieved from the source table 802. Second, the presentation and control component 104 retrieves from the Time In Story Table 1302 the row where the scene column 1304 is equal to the name of the current scene. Third, the presentation and control component 104 extracts the time and date information from columns 1306, 1308, and 1310 of this row, and forwards this information to the user device 106 via the communication medium 124. The user device 106 displays this information in a well known manner.
The present invention alternatively processes a "when did this happen?" query type as follows. First, the presentation and control component 104 retrieves from the Take Details table 1312 the row where the value in the take first frame time code column 1316 is equal to the value in the first frame time code 806 of the take row previously retrieved from the source table 802. Second, the presentation and control component 104 extracts the date and time information from columns 1320 and 1322 of this row, and forwards this information to the user device 106 via the communication medium 124. The user device 106 displays this information in a well known manner.
Other queries can be answered by reference to the Take Details Table 1312. For example, a "Where was this take shot?" query can be answered by reference to the location name column 1318, and a "How was this take shot?" query can be answered by reference to the method column 1324.
Query Type: Why Queries
A "why" query is supported only if a corresponding answer is available. An example why question is: "Why is the street in this scene wet when it appears to be a clear day?" A typical answer is: "The director of photography uses water to create more interesting images on film by capturing the reflections of other parts of the scene in the street. The director calls for a wet-down just before the shop and a water truck drives through the scene and makes it wet."
The tables and methods for answering these "why" questions are shown in FIG. 14A, FIG. 14B and FIG. 15. Preferably, the present invention includes a Question/Answer table 1404 and Question Applies to Scene table 1424 to support "why" questions. These tables 1404, 1424 are movie specific, and are stored in the index information database 122. Information for the Question/Answer table 1404 and Question Applies to Scene table 1424 is derived by the index generator component 308 by reference to many sources, such as interviews with persons involved in the making of the movie, diaries kept during the making of the movie, books describing the making of the movie, etc. Preferably, a human operator uses this information to compose "why" questions and their answers, and to insert these questions and answers in the Question/Answer table 1404. Similarly, a human operator uses this information to determine appropriateness of each question to particular scenes or sequences of scenes and inserts this information into the Question Applies to Scene table 1424.
The Question/Answer table 1404 includes a row for each why question that is supported. A Question Number column 1406 uniquely identifies the question, a question column 1408 stores the why question, and an answer column 1410 stores an answer to the question.
The Question Applies to Scene table 1424 includes a row for each segment of a movie to which a question applies. A Question Number column 1426 identifies the question, a First Scene column 1428 identifies the first scene in a sequence of scenes for which this question is appropriate, and a Last Scene column 1430 identifies the last scene in a sequence of scenes for which this scene is appropriate. Since questions can apply to several scenes in a movie, many rows may have the same Question Number 1426. Many questions will apply to any given scene so First Scene 1428 and Last Scene 1430 values may also be repeated.
The present invention processes a why question as is shown in FIG. 15. The procedure gets control at 1510 and proceeds immediately to the first processing step 1520. First the presentation and control component 104 accesses the row of source table 802 where the type code 804 is "scene" and the current time code of the movie is between the First Frame Time Code 806 and the Last Frame Time Code 808 to retrieve the correct for which scene 818 value. Second, step 1522, the Question Applies to Scene table is accessed to retrieve a list of question numbers 1426 where the previously retrieved for which scene 818 value is between the First Scene 1428 and Last Scene 1430. There is a possibility of duplicate question number 1426 values in the list and these should be removed. Third, step 1512, the questions 1408 from the Question/Answer table 1404 along with the questions numbers 1406 are forwarded to the user device 106 through the communication medium 124 and are subsequently displayed in a well known manner. Upon receipt of a response from the user device 106, the question 1408 and answer 1410 corresponding to the question number 1406 selected by the user are retrieved 1514. Finally, step 1516, the question 1408 and answer 1410 are forwarded to the user device 106 via the communication medium 124. The user device 106 displays this information in a well known manner. Processing then proceeds directly through termination 1518.
Show Option
According to an embodiment of the invention, the user can request that the script be displayed as the movie is presented. The present invention processes this user request as follows. First, the time code for the current frame is determined. Second, the row corresponding to the current scene is retrieved from the source table 802. This is done by identifying a scene row in the source table 802 where the current frame time code is greater than or equal to the value of the first frame time code column 806, and less than or equal to the value of the last frame time code column 808. Based on the information contained in this scene row, it is possible to synchronize the display of the movie with the display of the script (the script is retrieved from the foundation information database 112).
The operation of the show option shall now be discussed in greater detail. The identified row (described above) is the first of a sequential set of scene rows which describe the rest of the movie. Each has values for frame count 810 and for which scene 818. The Script text is accessed using the for which scene 818 values obtained from the source table 802 as index keys. The frame count 810 from each row tells exactly how long that scene will be on the screen. The scrolling rate of the script text is adjusted so that the script rolls by in the same amount of time that the scene takes in the movie. Each new segment of the script is accessed to have it ready when it has to start appearing on the screen. Since the scrolling window has many lines of the script on it, the slug line for the following scene will appear before the video for the current scene has completed. Well known techniques for anticipatory buffering enable smooth scrolling and synchronization.
Manager
As noted above, the present invention includes a manager 1602 which is shown in block diagram form in FIG. 16. The manager 1602 includes one or more capture and digitizer components 304 (for simplicity purposes, only one is described), one or more index generation components 308 (for simplicity purposes, only one is described), a personalized presentation manager 1604, and a personalized collection manager 1606. The capture and digitizer component 304 and the index generation component 308 were described above. The personalized presentation manager 1604 and the personalized collection manager 1606 shall now be discussed.
Personalized Presentation Manager
The personalized presentation manager 1604 enables a user to create a personalized version of a movie. The user, in his personal movie version, may include shots not in the theatrical presentation or the VCR video version, and/or may exclude shots, takes, clips, and/or scenes that are in the theatrical presentation and/or the VCR video version. The user may change the sequence of shots, takes, clips, and/or scenes, and/or may change the length of shots, takes, clips, and/or scenes. Other modification options available to users will be apparent to persons skilled in the relevant art based on the discussion contained herein.
The user interacts with the personalized presentation manager 1604 to create a personalized movie version. In one embodiment, the personalized presentation manager 1604 forms part of the presentation and control component 104, such that interaction with the user is achieved through the transfer of control and data messages between the presentation and control component 104 and the user device 106. In an alternate embodiment, the personalized presentation manager 1604 is part of the presentation and control component 104, but becomes resident (at least in part) at the user device 106 pursuant to a user request to create or edit a personalized movie version. This alternate embodiment is advantageous in that it reduces traffic on the communication medium 124. Other ways for implementing the personalized presentation manager 1604 will be apparent to persons skilled in the relevant art(s).
FIG. 17A presents a flowchart depicting the operation of the personalized presentation manager 1604 when working with an user to create or modify a personalized movie version. This flowchart begins with step 1702, where control immediately passes to step 1704.
In step 1704, the personalized presentation manager 1604 creates a copy of the edit decision list corresponding to the movie which the user wishes to personalize. This copy is called the personalized edit decision list for reference purposes. An example of a personalized edit decision list 1702 is shown in FIG. 1702.
According to a preferred embodiment of the present invention, a personalized movie version is made up of a sequence of clips. Accordingly, the personalized edit decision list 1702 includes a row for each clip. The columns in the personalized edit decision list 1702 have the same function as those of the same name in the source table 802 (FIG. 8). Thus, once editing of the personalized edit decision list 1702 has been completed, and the personalized movie is being viewed, it is possible to process user queries in the same manner as discussed above.
It may be necessary to perform a translation from the movie's edit decision list, which includes scene and take entries, to the personalized edit decision list 1702, which contains just clip entries. The mechanics of this translation will be apparent to persons skilled in the relevant art(s).
In step 1706, the personalized presentation manager 1604 enables the user to modify the personalized edit decision list 1702. In this capacity, the personalized presentation manager 1604 acts as an editor, such that the user can edit the rows in the personalized edit decision list 1702. However, the personalized presentation manager 1604 functions as more than an editor, since it allows a user to view any shot, take, scene, clip, etc., contained in any version of the movie, or in the underlying dailys 722 or even the underlying negative film 720. These shots, takes, scenes, clips, etc., are located by using the associated time codes as a reference to the source table 802 for the movie. Based on information contained in the source table 802, it is possible to identify the storage location in the foundation information database 112 of any shot, take, scene, clip, etc., as discussed above. Accordingly, the user can view his proposed change to the personalized edit decision list 1702 before actually making the change.
The operation of the flowchart in FIG. 17A is complete after step 1706 is performed, as indicated by step 1708.
FIG. 18 presents a flowchart representing the manner in which the presentation and control component 104 presents a personalized movie to a user. This flowchart begins with step 1802, where control immediately passes to step 1804.
In step 1804, the presentation and control component 104 selects and retrieves the first entry (row) from the personalized edit decision list 1702 for the personalized movie the user wants to view.
In step 1806, the presentation and control component 104 uses the information contained in this row to retrieve from the foundation information database 112 the digitized frames corresponding to the clip represented by this row (that was retrieved in step 1804). In particular, the presentation and control component 104 uses information from the source title column 1712, the source first frame time code column 1708, and the source frame count column 1710 from this row (retrieved from the personalized edit table in step 1804) to obtain these digitized frames.
In step 1808, the presentation and control component 104 presents these digitized frames to the user. In particular, the presentation and control component 104 transfers these digitized frames to the user device 106 via the communication medium 124, and the user device 106 displays the frames in a well known manner. Note that, while these frames are being presented to the user, the user can issue a query, as described above. Any such query issued by the user is processed in the same manner as described above.
In step 1810, the presentation and control component 104 determines whether there are any more entries in the personalized edit decision list 1702 left to process. If there are more entries to process, then in step 1814 the next entry is selected, and control returns to step 1806. Otherwise, operation of the flowchart in FIG. 18 is complete as indicated by step 1812.
Personalized Collection Manager
The personalized collection manager 1606 enables a user to create a personalized collection of items for later presentation. These items may be scenes and/or clips from a movie or from multiple movies, tracks from a soundtrack or multiple soundtracks, favorite "coming attraction" clips, etc., or any combination of these. Thus, the personalized collection manager 1606 enables a user to create collections or groupings of items of interest.
The user interacts with the personalized collection manager 1606 to create a personalized collection. In one embodiment, the personalized collection manager 1606 forms part of the presentation and control component 104, such that interaction with the user is achieved through the transfer of control and data messages between the presentation and control component 104 and the user device 106. In an alternate embodiment, the personalized collection manager 1606 is part of the presentation and control component 104, but becomes resident (at least in part) at the user device 106 pursuant to a user request to create or edit a personalized collection. This alternate embodiment is advantageous in that it reduces traffic on the communication medium 124. Other ways for implementing the personalized collection manager 1606 will be apparent to persons skilled in the relevant art(s).
FIG. 19 presents a flowchart depicting the operation of the personalized collection manager 1606 when working with an user to create or modify a personalized collection. This flowchart begins with step 1902, where control immediately passes to step 1904.
In step 1904, the personalized collection manager 1606 creates a new personalized collection table, or opens an existing personalized collection table for editing (which action is taken depends on the user's request). FIG. 20 illustrates an example personalized collection table 2002, which has an entry (row) for each item in the collection. The source first frame time code column 2004, source last frame time code column 2006, and source title column 2008 are similar to the identically named columns in the source table 802 (FIG. 8). These columns 2004, 2006, 2008 contain information necessary to locate the underlying foundation information in the foundation information database 112. The personalized collection table 2002 shown in FIG. 20 is somewhat specialized for takes, cuts, scenes, and/or clips from a movie. Minor modifications to the personalized collection table 2002 may be necessary to accommodate other items, such as audio tracks (for example, for audio tracks, the source first frame time code column 2004 and source last frame time code column 2006 are modified to store time codes or other indicia to identify the beginning and end of an audio track). The nature and implementation of such modifications will be apparent to persons skilled in the relevant art(s).
In step 1906, the personalized collection manager 1606 enables the user to modify the personalized collection table 2002. In this capacity, the personalized collection manager 606 acts as an editor, such that the user can edit the rows in the personalized collection table 2002. However, the personalized collection manager 606 functions as more than an editor, since it allows a user to preview any shot, take, scene, clip, audio segment, etc., contained in any version of the movie, the underlying dailys 722, the underlying negative film 720, or other foundation information stored in the foundation information database 112. These shots, takes, scenes, clips, audio segments, etc., are located by using the associated time codes or other identifying indicia as a reference to the source table 802 for the movie, or to other index tables stored in the index information database 122. Based on this index information, it is possible to identify the storage location in the foundation information database 112 of any shot, take, scene, clip, audio segment, etc., as discussed above. Accordingly, the user can view his proposed change to the personalized collection table 2002 before actually making the change.
The operation of the flowchart in FIG. 19 is complete after step 1906 is performed, as indicated by step 1908.
The presentation and control component 104 presents a personalized collection by traversing each entry in the corresponding personalized collection table 2002 in a manner similar to that discussed above in conjunction with FIG. 18. While viewing a personalized collection, an user can issue a query as discussed above. The present invention processes such a query in the manner discussed above.
While various embodiments of the present invention have been described above, it should be understood that they have been presented by way of example only, and not limitation. Thus, the breadth and scope of the present invention should not be limited by any of the above-described exemplary embodiments, but should be defined only in accordance with the following claims and their equivalents.
While the invention has been particularly shown and described with reference to (a) preferred embodiment(s) thereof, it will be understood by those skilled in the art that (various changes) (the foregoing and other changes) in form and details may be made therein without departing from the spirit and scope of the invention.

Claims

1. A method of enabling a user to operate with a personalized version of a movie, comprising the steps of:
(1) enabling said user to modify an edit decision list associated with said movie, said edit decision list having entries for at least some of at least one of scenes, clips, and takes in said movie, said modified edit decision list storing at least information sufficient to locate movie related information pertinent to generation of said movie; and
(2) presenting to said user said personalized version of said movie in response to a request from said user;
wherein step (1) comprises the steps of:
receiving from said user information identifying a particular portion of said movie;
retrieving information corresponding to said particular portion of said movie; and
enabling said user to add any part of said retrieved information corresponding to said particular portion of said movie to said personalized version of said movie.
2. The method of claim 1, wherein step (2) comprises the steps of:
(a) retrieving an entry from said modified edit decision list;
(b) retrieving one or more digitized frames specified by said retrieved entry; and
(c) presenting said digitized frames to said user.
3. The method of claim 1, further comprising the step of:
(3) receiving from said user a query pertaining to said personalized version of said movie.
4. The method of claim 3, wherein said query is one of the following query types:
(a) a "who is this?" query;
(b) a "what other films has this director worked on?" query;
(c) a "when did this happen?" query; and
(d) a "why?" query.
5. The method of claim 4, wherein processing of a "who is this?" query involves accessing one or more of an Actor in Take table, a Character In Scene table, and an Actor Play Character table, and wherein processing of a "what other films has this director worked on?" query involves accessing one or more of an One Movie Credit table and an All Movies Credit table, and wherein processing of a "when did this happen?" query involves accessing one or more of a Time In Story table and a Take Details table.
6. A system of enabling a user to operate with a personalized version of a movie, comprising:
edit decision list modifying means for enabling said user to modify an edit decision list associated with said movie, said edit decision list having entries for at least some of at least one of scenes, clips, and takes in said movie, said modified edit decision list storing at least information sufficient to locate movie related information pertinent to generation of said movie; and
presenting means for presenting to said user said personalized version of said movie in response to a request from said user;
wherein said edit decision list modifying means comprises:
means for receiving from said user information identifying a particular portion of said movie;
means for retrieving information corresponding to said particular portion of said movie; and
means for enabling said user to add any part of said retrieved information corresponding to said particular portion of said movie to said personalized version of said movie.
7. The system of claim 6, wherein said presenting means comprises:
means for retrieving an entry from said modified edit decision list;
means for retrieving one or more digitized frames specified by said retrieved entry; and
means for presenting said digitized frames to said user.
8. The system of claim 6, further comprising:
means for receiving from said user a query pertaining to said personalized version of said movie.
9. The system of claim 8, wherein said query is one of the following query types:
(a) a "who is this?" query;
(b) a "what other films has this director worked on?" query;
(c) a "when did this happen?" query; and
(d) a "why?" query.
10. The system of claim 9, wherein processing of a "who is this?" query involves accessing one or more of an Actor in Take table, a Character In Scene table, and an Actor Play Character table, and wherein processing of a "what other films has this director worked on?" query involves accessing one or more of an One Movie Credit table and an All Movies Credit table, and wherein processing of a "when did this happen?" query involves accessing one or more of a Time In Story table and a Take Details table.
11. A computer program product having control logic stored therein, said control logic, when executed by a computer, enabling the computer to enable a user to operate with a personalized version of a movie, said control logic comprising:
edit decision list modifying means for enabling the computer to enable said user to modify an edit decision list associated with said movie, said edit decision list having entries for at least some of at least one of scenes, clips, and takes in said movie, said modified edit decision list storing at least information sufficient to locate movie related information pertinent to generation of said movie; and
presenting means for enabling the computer to present to said user said personalized version of said movie in response to a request from said user;
wherein said edit decision list modifying means comprises:
means for enabling the computer to receive from said user information identifying a particular portion of said movie;
means for enabling the computer to retrieve information corresponding to said particular portion of said movie; and
means for enabling the computer to enable said user to add any part of said retrieved information corresponding to said particular portion of said movie to said personalized version of said movie.
12. The computer program product of claim 6, wherein said presenting means comprises:
means for enabling the computer to retrieve an entry from said modified edit decision list;
means for enabling the computer to retrieve one or more digitized frames specified by said retrieved entry; and
means for enabling the computer to present said digitized frames to said user.
13. The computer program product of claim 6, wherein said control logic further comprises:
means for enabling the computer to receive from said user a query pertaining to said personalized version of said movie.
14. The computer program product of claim 8, wherein said query is one of the following query types:
(a) a "who is this?" query;
(b) a "what other films has this director worked on?" query;
(c) a "when did this happen?" query; and
(d) a "why?" query.
15. The computer program product of claim 9, wherein processing of a "who is this?" query involves accessing one or more of an Actor in Take table, a Character In Scene table, and an Actor Play Character table, and wherein processing of a "what other films has this director worked on?" query involves accessing one or more of an One Movie Credit table and an All Movies Credit table, and wherein processing of a "when did this happen?" query involves accessing one or more of a Time In Story table and a Take Details table.
16. A method for enabling a user to operate with a personalized collection comprising one or more shots, takes, scenes, clips, video segments, audio segments, and multimedia segments, said method comprising the steps of:
enabling said user to modify a personalized collection table having entries for items in said personalized collection; and
presenting to said user at least a part of said personalized collection in response to a request from said user, comprising the steps of:
retrieving an entry from said personalized collection table;
retrieving information specified by said retrieved entry; and
presenting said retrieved information to said user.
17. A system for enabling a user to operate with a personalized collection comprising one or more shots, takes, scenes, clips, video segments, audio segments, and multimedia segments, comprising:
modifying means for enabling said user to modify a personalized collection table having entries for items in said personalized collection; and
presenting means for presenting to said user at least a part of said personalized collection in response to a request from said user, comprising:
means for retrieving an entry from said personalized collection table;
means for retrieving information specified by said retrieved entry; and
means for presenting said retrieved information to said user.
18. A computer program product having control logic stored therein, said control logic when executed by a computer causing the computer to enable a user to operate with a personalized collection comprising one or more shots, takes, scenes, clips, video segments, audio segments, and multimedia segments, said control logic comprising:
modifying means for causing the computer to enable said user to modify a personalized collection table having entries for items in said personalized collection; and
presenting means for causing the computer to present to said user at least a part of said personalized collection in response to a request from said user, comprising:
means for causing the computer to retrieve an entry from said personalized collection table;
means for causing the computer to retrieve information specified by said retrieved entry; and
means for causing the computer to present said retrieved information to said user.
19. A system for presenting movies, comprising:
a communication medium;
one or more foundation information databases coupled to said communication medium;
one or more index information databases coupled to said communication medium; and
one or more presentation and control components coupled to said communication medium.
20. The system of claim 19, further comprising:
one or more cross merchant gateways coupled to said communication medium; and
one or more merchant transaction processors coupled to said communication medium.
21. A method of presenting movie related objects, comprising the steps of:
retrieving a next portion of a selected movie related object by reference to a foundation information database;
presenting said next portion of said selected movie related object;
receiving a query pertaining to said selected movie related object; and
processing said received query by reference to said foundation information database.
22. The method of claim 21, wherein said received query is one of the following query types:
(a) a "who is this?" query;
(b) a "what other films has this director worked on?" query;
(c) a "when did this happen?" query; and
(d) a "why?" query.
23. The method of claim 21, wherein said selected movie related object is one of a version of a movie, a movie audio track, a video game related to a movie, text related to a movie, or a personalized collection.
24. A system of presenting movie related objects, comprising:
means for retrieving a next portion of a selected movie related object by reference to a foundation information database;
means for presenting said next portion of said selected movie related object;
means for receiving a query pertaining to said selected movie related object; and
means for processing said received query by reference to said foundation information database.
25. The system of claim 24, wherein said received query is one of the following query types:
(a) a "who is this?" query;
(b) a "what other films has this director worked on?" query;
(c) a "when did this happen?" query; and
(d) a "why?" query.
26. The system of claim 24, wherein said selected movie related object is one of a version of a movie, a movie audio track, a video game related to a movie, text related to a movie, or a personalized collection.
27. A computer program product having control logic stored therein, said control logic when executed by a computer causing the computer to present movie related objects, said control logic comprising:
means for enabling the computer to retrieve a next portion of a selected movie related object by reference to a foundation information database;
means for enabling the computer to present said next portion of said selected movie related object;
means for enabling the computer to receive a query pertaining to said selected movie related object; and
means for enabling the computer to process said received query by reference to said foundation information database.
28. The computer program product of claim 27, wherein said received query is one of the following query types:
(a) a "who is this?" query;
(b) a "what other films has this director worked on?" query;
(c) a "when did this happen?" query; and
(d) a "why?" query.
29. The computer program product of claim 27, wherein said selected movie related object is one of a version of a movie, a movie audio track, a video game related to a movie, text related to a movie, or a personalized collection.

CROSS-REFERENCE TO OTHER APPLICATIONS

The present application is a continuation of Ser. No. 08/840,276 filed Apr. 14, 1997, which is now U.S. Pat. No. 5,781,730, which is a continuation of Ser. No. 08/407,305 filed Mar. 20, 1995, abandoned, herein incorporated by reference in their entireties. The following applications of common assignee contain some common disclosure, and are believed to have an effective filing date identical with that of the present application. "System and Method for Linking and Presenting Movies With Their Underlying Source Information," incorporated herein by reference. "System and Method for Providing Merchant Information and Establishing Links to Merchants While Presenting a Movie," incorporated herein by reference.

US Referenced Citations (19)

Number	Name	Date
4305131	Best	Dec 1981
4931950	Isle et al.	Jun 1990
5053956	Donald et al.	Oct 1991
5111409	Gasper et al.	May 1992
5231566	Blutinger et al.	Jul 1993
5307456	MacKay	Apr 1994
5309355	Lockwood	May 1994
5319455	Hoarty et al.	Jun 1994
5345549	Appel et al.	Sep 1994
5353391	Cohen et al.	Oct 1994
5367621	Cohen et al.	Nov 1994
5388993	McKiel et al.	Feb 1995
5404316	Klingler et al.	Apr 1995
5414808	Williams	May 1995
5440678	Eisen et al.	Aug 1995
5451998	Hamrick	Sep 1995
5485611	Astle	Jan 1996
5515490	Buchanan et al.	May 1996
5539450	Handelman	Jul 1996

Non-Patent Literature Citations (7)

Entry
Cowart, Robert, "Master Windows.RTM. 3.1," Sybex, 1992, p. 31.
Ozer, "Digital Video: Shot by Shot," PC Magazine, vol. 14, No. 7, Apr. 11, 1995, pp. 104-110.
Sahai, "Video Thrills for Digital De Milles: Adobe Premiere 4.0," Windows Magazine, vol. 6 No. 1, Jan. 1, 1995, p. 140 (abstract only).
Simone, "Video-Editing Software: Digital Master," PC Magazine, vol. 14, No. 7, Apr. 11, 1995, pp. 144-145.
Woolsey, Kristina H., "Multimedia Scouting," IEEE Computer Graphics & Applications, Jul. 1991, pp. 26-38.
The Seybold Report on Desktop Publishing, vol. 7, No. 3, Nov. 2, 1992.
Boisseau, Charles, "The Bard of CD-ROM: Artist Bringing Unique Computerized Novel to Market," Houston Chronicle, Oct. 5, 1992.

Continuations (2)

	Number	Date	Country
Parent	840276	Apr 1997
Parent	407305	Mar 1995

System, method, and computer program product for presenting multimedia objects, including movies and personalized collections of items

Information

Patent Number

Date Filed

Date Issued

Inventors

Original Assignees

Examiners

Agents

CPC

US Classifications

Field of Search

US