US20040244041A1 - System, method and article of manufacture for late synchronization during the execution of a multimedia event on a plurality of client computers - Google Patents

System, method and article of manufacture for late synchronization during the execution of a multimedia event on a plurality of client computers Download PDF

Info

Publication number
US20040244041A1
US20040244041A1 US10/880,272 US88027204A US2004244041A1 US 20040244041 A1 US20040244041 A1 US 20040244041A1 US 88027204 A US88027204 A US 88027204A US 2004244041 A1 US2004244041 A1 US 2004244041A1
Authority
US
United States
Prior art keywords
event
recited
storage device
memory storage
client
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US10/880,272
Inventor
Evgeniy Getsin
Michael Lewis
Todd Collart
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Sonic Solutions LLC
Original Assignee
Interactual Technologies Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Interactual Technologies Inc filed Critical Interactual Technologies Inc
Priority to US10/880,272 priority Critical patent/US20040244041A1/en
Publication of US20040244041A1 publication Critical patent/US20040244041A1/en
Assigned to SONIC SOLUTIONS, A CALIFORNIA CORPORATION reassignment SONIC SOLUTIONS, A CALIFORNIA CORPORATION ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: INTERACTUAL TECHNOLOGIES, INC., A CALIFORNIA CORPORATION
Abandoned legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/10Protecting distributed programs or content, e.g. vending or licensing of copyrighted material ; Digital rights management [DRM]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/60Network streaming of media packets
    • H04L65/75Media network packet handling
    • H04L65/764Media network packet handling at the destination 

Definitions

  • the present invention relates to network synchronization and more particularly to synchronizing the playback of a multimedia event on a plurality of client apparatuses.
  • Systems such as the Internet typically are point-to-point (or unicast) systems in which a message is converted into a series of addressed packets which are routed from a source node through a plurality of routers to a destination node.
  • the packet In most communication protocols the packet includes a header which contains the addresses of the source and the destination nodes as well as a sequence number which specifies the packet's order in the message.
  • IP Multicasting the network over which such packets are routed is referred to as the Multicast Backbone or MBONE.
  • routers have become available which can route the multicast addresses (class D addresses) provided for in communication protocols such as TCP/IP and UDP/IP.
  • a multicast address is essentially an address for a group of host computers who have indicated their desire to participate in that group.
  • a multicast packet can be routed from a source node through a plurality of multicast routers (or mrouters) to one or more devices receiving the multicast packets. From there the packet is distributed to all the host computers that are members of the multicast group.
  • a multimedia computer system can be defined as a computer system having a combination of video and audio outputs for presentation of audio-visual displays.
  • a modem multimedia computer system typically includes one or more storage devices such as an optical drive, a CD-ROM, a hard drive, a videodisc, or an audiodisc, and audio and video data are typically stored on one or more of these mass storage devices.
  • audio and video data for a multimedia display may also be stored in separate computer systems that are networked together. In this instance, the computer system presenting the multimedia display would receive a portion of the necessary data from the other computer system via the network cabling.
  • Bit-mapped images comprise a plurality of picture elements (pixels) and are created by assigning a color to each pixel inside the image boundary. Most bit-mapped color images require one byte per pixel for storage, so large bit-mapped images create correspondingly large files. For example, a full-screen, 256-color image in 640-by-480-pixel VGA mode requires 307,200 bytes of storage, if the data is not compressed.
  • Vector-based images are created by defining the end points, thickness, color, pattern and curvature of lines and solid objects comprised within the image.
  • a vector-based image includes a definition which consists of a numerical representation of the coordinates of the object, referenced to a corner of the image.
  • Bit-mapped images are the most prevalent type of image storage format, and the most common bit-mapped-image file formats are as follows.
  • a file format referred to as BMP is used for Windows bit-map files in 1-, 2-, 4-, 8-, and 24-bit color depths.
  • BMP files contain a bit-map header that defines the size of the image, the number of color planes, the type of compression used (if any), and the palette used.
  • the Windows DIB (device-independent bit-map) format is a variant of the BMP format that includes a color table defining the RGB (red green blue) values of the colors used.
  • Other types of bit-map formats include the TIF (tagged image format file), the PCX (Zsoft Personal Computer Paintbrush Bitmap) file format, the GIF (graphics interchange file) format, and the TGA (Texas Instruments Graphic Architecture) file format.
  • the standard Windows format for bit-mapped images is a 256-color device-independent bit map (DIB) with a BMP (the Windows bit-mapped file format) or sometimes a DIB extension.
  • the standard Windows format for vector-based images is referred to as WMF (Windows meta file).
  • Full-motion video implies that video images shown on the computer's screen simulate those of a television set with identical (30 frames-per-second) frame rates, and that these images are accompanied by high-quality stereo sound.
  • a large amount of storage is required for high-resolution color images, not to mention a full-motion video sequence.
  • a single frame of NTSC video at 640-by-400-pixel resolution with 16-bit color requires 512K of data per frame.
  • At 30 flames per second over 15 Megabytes of data storage are required for each second of full motion video.
  • various types of video compression algorithms are used to reduce the amount of necessary storage.
  • Video compression can be performed either in real-time, i.e., on the fly during video capture, or on the stored video file after the video data has been captured and stored on the media.
  • different video compression methods exist for still graphic images and for full-motion video.
  • Examples of video data compression for still graphic images are RLE (run-length encoding) and JPEG (Joint Photographic Experts Group) compression.
  • RLE is the standard compression method for Windows BMP and DIB files.
  • the RLE compression method operates by testing for duplicated pixels in a single line of the bit map and stores the number of consecutive duplicate pixels rather than the data for the pixel itself.
  • JPEG compression is a group of related standards that provide either lossless (no image quality degradation) or lossy (imperceptible to severe degradation) compression types.
  • Video compression algorithms for motion video generally use a concept referred to as interframe key frame. Successive frames are compared with the key frame, and only the differences between the digitized data from the key frame and from the successive frames are stored. Periodically, such as when new scenes are displayed, new key frames are digitized and stored, and subsequent comparisons begin from this new reference point. It is noted that interframe compression ratios are content-dependent, i.e., if the video clip being compressed includes many abrupt scene transitions from one image to another, the compression is less efficient. Examples of video compression which use an interframe compression technique are MPEG, DVI and Indeo, among others.
  • MPEG Motion Pictures Experts Group
  • ADPCM Adaptive Differential Pulse Code Modulation
  • a standard referred to as Digital Video Interactive (DVI) format developed by Intel Corporation is a compression and storage format for full-motion video and high-fidelity audio data.
  • the DVI standard uses interframe compression techniques similar to that of the MPEG standard and uses ADPCM compression for audio data.
  • the compression method used in DVI is referred to as RTV 2.0 (real time video), and this compression method is incorporated into Intel's AVK (audio/video kernel) software for its DVI product line.
  • IBM has adopted DVI as the standard for displaying video for its Ultimedia product line.
  • the DVI file format is based on the Intel i750 chipset and is supported through the Media Control Interface (MCI) for Windows.
  • MCI Media Control Interface
  • Microsoft and Intel jointly announced the creation of the DV MCI (digital video media control interface) command set for Windows 3.1 in 1992.
  • the Microsoft Audio Video Interleaved (AVI) format is a special compressed file structure format designed to enable video images and synchronized sound stored on CD-ROMs to be played on PCs with standard VGA displays and audio adapter cards.
  • the AVI compression method uses an interframe method, i.e., the differences between successive frames are stored in a manner similar to the compression methods used in DVI and MPEG.
  • the AVI format uses symmetrical software compression-decompression techniques, i.e., both compression and decompression are performed in real time.
  • AVI files can be created by recording video images and sound in AVI format from a VCR or television broadcast in real time, if enough free hard disk space is available.
  • a system, method and article of manufacture are provided for delayed synchronization of an event on a plurality of client apparatuses.
  • a plurality of client apparatuses are connected via a network and an event is stored in memory on the client apparatuses.
  • the event is then simultaneously played back on the client apparatuses utilizing the network.
  • a request may be received from one of the client apparatuses for that particular client to be included in the synchronized event.
  • information is transmitted to the requesting client apparatus utilizing the network. This information is adapted for identifying a location in the memory where the event is currently being played back on the remaining client apparatuses. This allows the simultaneous playback of the event on the requesting client apparatus.
  • the request may be received utilizing the network.
  • FIG. 1 is a schematic diagram of a hardware implementation of one embodiment of the present invention
  • FIG. 2 illustrates a flowchart delineating a method for synchronizing an event on a plurality of client apparatuses in accordance with one embodiment of the present invention
  • FIG. 3 illustrates a flowchart delineating a method for storing synchronization information for subsequent playback of an event in accordance with one embodiment of the present invention
  • FIG. 4 illustrates a flowchart setting forth a method for providing overlays during a synchronized event on a plurality of client apparatuses in accordance with one embodiment of the present invention
  • FIG. 5 illustrates a flow diagram for delayed synchronization of an event on a plurality of client apparatuses in accordance with one embodiment of the present invention
  • FIG. 6 illustrates a flow diagram for providing information on a synchronized event on a plurality of client apparatuses in accordance with one embodiment of the present invention
  • FIG. 7 illustrates a method for creating a synchronizer object in order to playback an event simultaneously on a plurality of client apparatuses in accordance with one embodiment of the present invention
  • FIG. 8 illustrates a flowchart for affording a scheduler object adapted to facilitate the playback of an event simultaneously on a plurality of networked client apparatuses in accordance with one embodiment of the present invention
  • FIG. 9 is a flowchart delineating a method for identifying a plurality of events which are played back simultaneously on a plurality of networked client apparatuses in accordance with one embodiment of the present invention
  • FIG. 10 shows a flowchart delineating a technique for interfacing a plurality of different types of playback devices of client apparatuses which are networked to simultaneously playback an event in accordance with one embodiment of the present invention
  • FIG. 11 illustrates the manner in which a layer factory is created in accordance with one embodiment of the present invention
  • FIG. 12 illustrates the manner in which user requests are processed in accordance with one embodiment of the present invention
  • FIGS. 13-16 illustrate various class/component diagrams in accordance with one embodiment of the present invention
  • FIG. 17 illustrates a logical sequence diagram in accordance with one embodiment of the present invention
  • FIG. 18 illustrates a logical sequence diagram that shows server side collaboration in accordance with one embodiment of the present invention.
  • FIG. 19 illustrates a logical sequence diagram showing client side collaboration in accordance with one embodiment of the present invention.
  • FIGS. 1-19 illustrate a system for synchronizing an event on a plurality of client apparatuses.
  • an event Prior to use, an event is stored in memory on at least one of the client apparatuses.
  • Such client apparatuses are adapted to be connected to a network along with a host computer(s).
  • information is transmitted from the host computer to the at least one client apparatus utilizing the network. This information allows for the simultaneous and synchronous playback of the event on each of the client apparatuses.
  • the client apparatuses may take the form of computers, televisions, stereos, home appliances, or any other types of devices.
  • the client apparatuses and the host computer each include a computer such as an IBM compatible computer, Apple Macintosh computer or UNIX based workstation.
  • FIG. 1 illustrates a typical hardware configuration of a workstation in accordance with a preferred embodiment having a central processing unit 110 , such as a microprocessor, and a number of other units interconnected via a system bus 112 .
  • the workstation shown in FIG. 1 includes a Random Access Memory (RAM) 114 , Read Only Memory (ROM) 116 , an I/O adapter 118 for connecting peripheral devices such as disk storage units 120 (i.e.
  • a user interface adapter 122 for connecting a keyboard 124 , a mouse 126 , a speaker 128 , a microphone 132 , and/or other user interface devices such as a touch screen (not shown) to the bus 112 , communication adapter 134 for connecting the workstation to a communication network (e.g., a data processing network) and a display adapter 136 for connecting the bus 112 to a display device 138 .
  • the workstation typically has resident thereon an operating system such as the Microsoft Windows NT or Windows/95 Operating System (OS), the IBM OS/2 operating system, the MAC OS, or UNIX operating system.
  • OS Microsoft Windows NT or Windows/95 Operating System
  • MAC OS MAC OS
  • UNIX operating system Those skilled in the art will appreciate that the present invention may also be implemented on platforms and operating systems other than those mentioned.
  • a preferred embodiment is written using JAVA, C, and the C++ language and utilizes object oriented programming methodology.
  • Object oriented programming has become increasingly used to develop complex applications.
  • OOP Object oriented programming
  • OOP is a process of developing computer software using objects, including the steps of analyzing the problem, designing the system, and constructing the program.
  • An object is a software package that contains both data and a collection of related structures and procedures. Since it contains both data and a collection of structures and procedures, it can be visualized as a self-sufficient component that does not require other additional structures, procedures or data to perform its specific task.
  • OOP therefore, views a computer program as a collection of largely autonomous components, called objects, each of which is responsible for a specific task. This concept of packaging data, structures, and procedures together in one component or module is called encapsulation.
  • OOP components are reusable software modules which present an interface that conforms to an object model and which are accessed at run-time through a component integration architecture.
  • a component integration architecture is a set of architecture mechanisms which allow software modules in different process spaces to utilize each others capabilities or functions. This is generally done by assuming a common component object model on which to build the architecture. It is worthwhile to differentiate between an object and a class of objects at this point.
  • An object is a single instance of the class of objects, which is often just called a class.
  • a class of objects can be viewed as a blueprint, from which many objects can be formed.
  • OOP allows the programmer to create an object that is a part of another object.
  • the object representing a piston engine is said to have a composition-relationship with the object representing a piston.
  • a piston engine comprises a piston, valves and many other components; the fact that a piston is an element of a piston engine can be logically and semantically represented in OOP by two objects.
  • OOP also allows creation of an object that “depends from” another object. If there are two objects, one representing a piston engine and the other representing a piston engine wherein the piston is made of ceramic, then the relationship between the two objects is not that of composition.
  • a ceramic piston engine does not make up a piston engine. Rather it is merely one kind of piston engine that has one more limitation than the piston engine; its piston is made of ceramic.
  • the object representing the ceramic piston engine is called a derived object, and it inherits all of the aspects of the object representing the piston engine and adds further limitation or detail to it.
  • the object representing the ceramic piston engine “depends from” the object representing the piston engine. The relationship between these objects is called inheritance.
  • the object or class representing the ceramic piston engine inherits all of the aspects of the objects representing the piston engine, it inherits the thermal characteristics of a standard piston defined in the piston engine class.
  • the ceramic piston engine object overrides these ceramic specific thermal characteristics, which are typically different from those associated with a metal piston. It skips over the original and uses new functions related to ceramic pistons.
  • Different kinds of piston engines have different characteristics, but may have the same underlying functions associated with it (e.g., how many pistons in the engine, ignition sequences, lubrication, etc.).
  • a programmer would call the same functions with the same names, but each type of piston engine may have different/overriding implementations of functions behind the same name. This ability to hide different implementations of a function behind the same name is called polymorphism and it greatly simplifies communication among objects.
  • composition-relationship With the concepts of composition-relationship, encapsulation, inheritance and polymorphism, an object can represent just about anything in the real world. In fact, one's logical perception of the reality is the only limit on determining the kinds of things that can become objects in object-oriented software. Some typical categories are as follows:
  • Objects can represent physical objects, such as automobiles in a traffic-flow simulation, electrical components in a circuit-design program, countries in an economics model, or aircraft in an air-traffic-control system.
  • Objects can represent elements of the computer-user environment such as windows, menus or graphics objects.
  • An object can represent an inventory, such as a personnel file or a table of the latitudes and longitudes of cities.
  • An object can represent user-defined data types such as time, angles, and complex numbers, or points on the plane.
  • OOP allows the software developer to design and implement a computer program that is a model of some aspects of reality, whether that reality is a physical entity, a process, a system, or a composition of matter. Since the object can represent anything, the software developer can create an object which can be used as a component in a larger software project in the future.
  • C++ is an OOP language that offers a fast, machine-executable code.
  • C++ is suitable for both commercial-application and systems-programming projects.
  • C++ appears to be the most popular choice among many OOP programmers, but there is a host of other OOP languages, such as Smalltalk, Common Lisp Object System (CLOS), and Eiffel. Additionally, OOP capabilities are being added to more traditional popular computer programming languages such as Pascal.
  • Encapsulation enforces data abstraction through the organization of data into small, independent objects that can communicate with each other. Encapsulation protects the data in an object from accidental damage, but allows other objects to interact with that data by calling the object's member functions and structures.
  • Subclassing and inheritance make it possible to extend and modify objects through deriving new kinds of objects from the standard classes available in the system. Thus, new capabilities are created without having to start from scratch.
  • Class hierarchies and containment hierarchies provide a flexible mechanism for modeling real-world objects and the relationships among them.
  • Class libraries are very flexible. As programs grow more complex, more programmers are forced to adopt basic solutions to basic problems over and over again. A relatively new extension of the class library concept is to have a framework of class libraries. This framework is more complex and consists of significant collections of collaborating classes that capture both the small scale patterns and major mechanisms that implement the common requirements and design in a specific application domain. They were first developed to free application programmers from the chores involved in displaying menus, windows, dialog boxes, and other standard user interface elements for personal computers.
  • Frameworks also represent a change in the way programmers think about the interaction between the code they write and code written by others.
  • the programmer called libraries provided by the operating system to perform certain tasks, but basically the program executed down the page from start to finish, and the programmer was solely responsible for the flow of control. This was appropriate for printing out paychecks, calculating a mathematical table, or solving other problems with a program that executed in just one way.
  • event loop programs require programmers to write a lot of code that should not need to be written separately for every application.
  • the concept of an application framework carries the event loop concept further. Instead of dealing with all the nuts and bolts of constructing basic menus, windows, and dialog boxes and then making these things all work together, programmers using application frameworks start with working application code and basic user interface elements in place. Subsequently, they build from there by replacing some of the generic capabilities of the framework with the specific capabilities of the intended application.
  • Application frameworks reduce the total amount of code that a programmer has to write from scratch.
  • the framework is really a generic application that displays windows, supports copy and paste, and so on, the programmer can also relinquish control to a greater degree than event loop programs permit.
  • the framework code takes care of almost all event handling and flow of control, and the programmer's code is called only when the framework needs it (e.g., to create or manipulate a proprietary data structure).
  • a programmer writing a framework program not only relinquishes control to the user (as is also true for event loop programs), but also relinquishes the detailed flow of control within the program to the framework. This approach allows the creation of more complex systems that work together in interesting ways, as opposed to isolated programs, having custom code, being created over and over again for similar problems.
  • a framework basically is a collection of cooperating classes that make up a reusable design solution for a given problem domain. It typically includes objects that provide default behavior (e.g., for menus and windows), and programmers use it by inheriting some of that default behavior and overriding other behavior so that the framework calls application code at the appropriate times.
  • default behavior e.g., for menus and windows
  • Behavior versus protocol Class libraries are essentially collections of behaviors that you can call when you want those individual behaviors in your program.
  • a framework provides not only behavior but also the protocol or set of rules that govern the ways in which behaviors can be combined, including rules for what a programmer is supposed to provide versus what the framework provides.
  • a preferred embodiment of the invention utilizes HyperText Markup Language (HTML) to implement documents on the Internet together with a general-purpose secure communication protocol for a transport medium between the client and the Newco. HTTP or other protocols could be readily substituted for HTML without undue experimentation.
  • HTML HyperText Markup Language
  • RRC 1866 Hypertext Markup Language—2.0
  • HTML Hypertext Transfer Protocol—HTTP/1.1: HTTP Working Group Internet Draft
  • HTML documents are SGML documents with generic semantics that are appropriate for representing information from a wide range of domains. HTML has been in use by the World-Wide Web global information initiative since 1990. HTML is an application of ISO Standard 8879; 1986 Information Processing Text and Office Systems; Standard Generalized Markup Language (SGML).
  • HTML has been the dominant technology used in development of Web-based solutions.
  • HTML has proven to be inadequate in the following areas:
  • UI User Interface
  • Custom “widgets” e.g., real-time stock tickers, animated icons, etc.
  • client-side performance is improved.
  • Java supports the notion of client-side validation, offloading appropriate processing onto the client for improved performance.
  • Dynamic, real-time Web pages can be created. Using the above-mentioned custom UI components, dynamic Web pages can also be created.
  • Sun's Java language has emerged as an industry-recognized language for “programming the Internet.”
  • Sun defines Java as: “a simple, object-oriented, distributed, interpreted, robust, secure, architecture-neutral, portable, high-performance, multithreaded, dynamic, buzzword-compliant, general-purpose programming language.
  • Java supports programming for the Internet in the form of platform-independent Java applets.”
  • Java applets are small, specialized applications that comply with Sun's Java Application Programming Interface (API) allowing developers to add “interactive content” to Web documents (e.g., simple animations, page adornments, basic games, etc.). Applets execute within a Java-compatible browser (e.g., Netscape Navigator) by copying code from the server to client.
  • Java's core feature set is based on C++.
  • Sun's Java literature states that Java is basically, “C++ with extensions from Objective C for more dynamic method resolution.”
  • ActiveX includes tools for developing animation, 3-D virtual reality, video and other multimedia content.
  • the tools use Internet standards, work on multiple platforms, and are being supported by over 100 companies.
  • the group's building blocks are called ActiveX Controls, small, fast components that enable developers to embed parts of software in hypertext markup language (HTML) pages.
  • ActiveX Controls work with a variety of programming languages including Microsoft Visual C++, Borland Delphi, Microsoft Visual Basic programming system and, in the future, Microsoft's development tool for Java, code named “Jakarta.”
  • ActiveX Technologies also includes ActiveX Server Framework, allowing developers to create server applications.
  • ActiveX could be substituted for JAVA without undue experimentation to practice the invention.
  • FIG. 2 illustrates a flowchart delineating a method for synchronizing an event on a plurality of client apparatuses.
  • an event is stored in memory on at least one of the client apparatuses.
  • the memory may take the form of an electromagnetic medium, or any type of optical storage device, i.e. CD-audio.
  • the memory includes a digital video disc (DVD) (audio or video).
  • DVD digital video disc
  • the information includes chapter information associated with the DVD.
  • the user may be required to purchase the memory, i.e. DVD, in order to participate in a synchronized event, thus increasing the sale of DVD's.
  • the event need not be necessarily stored in memory on all of the client apparatuses, but rather stored on one or some of the client apparatuses and streamed to the remaining client apparatuses at variant rates. This may be feasibly accomplished if the client apparatus(es) containing the stored event has a high-bandwidth connection with the remaining client apparatuses.
  • the client apparatus(es) containing the stored event may include a server that has a connection to a plurality of televisions via a cable network, i.e. WEBTV. Similar functionality may be achieved via a broadcast medium.
  • WEBTV i.e. WEBTV
  • the event includes a video and audio presentation such as movie, a concert, and/or a theatrical event. It should be noted, however, that the event may included any recording capable of being played back for entertainment, education, informative or other similar purposes.
  • the client apparatuses and a host computer are adapted to be connected to a network.
  • a network may include a wide, local or any other type of communication network.
  • a wide area network such as the Internet may be employed which operates using TCP/IP or IPX protocols.
  • information is transmitted from the host computer to the appropriate client apparatuses utilizing the network.
  • This information allows for the simultaneous and synchronous playback of the event on each of the client apparatuses.
  • the information may also include a start time when the playback of the event is to begin on each of the client apparatuses. Further, an ending time may be included when the playback of the event is to end on each of the client apparatuses. Still yet, “play” command information may be sent to the client apparatuses at the start time.
  • input may be received from the user, and used to alter the playback of the event.
  • the host server, or synchronization server can also control various streams of a variant rate and different hardware associated with those streams.
  • the present invention thus has the ability to synchronize video playback for one or multiple (thousands) users from one or multiple physical locations, and to synchronize with external video, audio and/or data streams.
  • Users of the present invention are at multiple physical locations and host servers may also be at different locations.
  • the present invention is thus a scalable system which is capable of servicing an unlimited number of users. Since the content is local to the user machine, no high network bandwidth is required.
  • FIG. 3 illustrates a flowchart delineating a method for storing synchronization information for subsequent playback of an event.
  • an event is stored in memory on at least one of the client apparatuses, as set forth earlier. These client apparatuses are adapted to be connected to a network along with a host computer during use.
  • information is stored on the host computer(s) for allowing the simultaneous playback of the event on each of the client apparatuses.
  • the information may include a history and data associated with the synchronous playback.
  • the history may include any overlaid material(as will be described hereinafter in greater detail), any specific commands affecting the playback of the information, or any other type of general information, i.e. start time, end time, etc.
  • the information may be downloaded utilizing the network at any time after the synchronous playback of the event. Such downloaded information may then be used for playback after the simultaneous playback of the event.
  • the present invention has the ability to allow users to download a history and data associated with a particular synchronization event and play it later.
  • FIG. 4 illustrates a flowchart setting forth a method for providing overlays during a synchronized event on a plurality of client apparatuses or any other source.
  • a plurality of client apparatuses are connected via a network.
  • an event may be simultaneously played back on the client apparatuses utilizing the network, as set forth earlier.
  • visual and/or audio material may also be overlaid on the event based on input received from at least one of the client apparatuses. See operation 404 . This may be accomplished by transmitting the overlay material from one of the client apparatuses to the host computer or any other server, and multicasting the same to the remaining client apparatuses.
  • the overlay material may include annotations on a display of the client apparatus.
  • the overlay material may include sketches which are inputted by way of a stylus-based input screen or a keyboard or the like, along with a voiceover inputted by way of a microphone or voice synthesizer. Such capability may also be quite valuable in an educational environment.
  • the overlay material may also be displayed on each of the client apparatuses utilizing the network. This allows each of the users to experience the overlay in real-time during the simultaneous playback of the event.
  • the user inputting the overlay material may select which users may experience the overlay material.
  • the client apparatus that provided the overlay material may also be identified to the users experiencing the overlay material.
  • FIG. 5 illustrates a flow diagram for delayed synchronization of an event on a plurality of client apparatuses.
  • a plurality of client apparatuses are connected via a network and an event is stored in memory on the client apparatuses.
  • the event is then simultaneously played back on the client apparatuses utilizing the network, as set forth earlier. Note operation 502 .
  • a request may be received from one of the client apparatuses for that particular to be included in the synchronized event, as set forth in operation 504 .
  • This request may be received after the synchronized event has already begun while it is still playing. Further, the request may be submitted via a site on a network, i.e. website.
  • information is transmitted in operation 506 to the requesting client apparatus utilizing the network.
  • This information is adapted for identifying a location in the memory where the event is currently being played back. This-allows the simultaneous playback of the event on the requesting client apparatus.
  • the end users are thus able to come in at a later time and to be synchronized with the event.
  • Targeted synchronization and various filters criteria can be applied to target different audiences. Also language and cultural differences can be taken into account.
  • the present invention may be adapted to address users on different hardware platforms (MAC, PC, set-top boxes). This may be accomplished by identifying the user using a cookie, a user profile which is identified by way of a log in, or a Burn Cut Area (BCA) of the disc.
  • MAC hardware platforms
  • the DVDs are packaging/boxed for distribution to either the Distributor or the Retailer. It should be noted that many companies take multiple forms, so the replicator and distributor may be one in the same. Also, some retailers are large/important enough to get shipments directly from replicator. The way in which the DVDs are packaging/shipped is very important because one must track the BCA numbers to actual shipping containers (box, etc.). Therefore tracking information must also be added to the BCA database.
  • the distributor also has mechanisms, i.e. scanners, input device, and monitoring devices, in place for tracking based on their distribution.
  • Deluxe may receive a “package” of 100,000 copies of “Lost in Space.”
  • the distributor ships 10,000 to Retailer A and 5,000 to Retailer B.
  • the distributor should be able to “input” retailer A and B's distribution information into the system. Ideally, this becomes a seamless/automated process.
  • DVDs may be further divided and distributed to local stores/outlets.
  • the retailer should be able to automatically “track” distribution of these DVDs through to their stores.
  • all three entitities are able to add tracking information to BCA database. Due to complexity and dependencies on existing business systems, the retail tracking concept will be rolled out in phases: replicator first most likely with key retail accounts. The distributors will be brought in. Retailers will then begin to embrace the ability to track based on local outlet/store.
  • ISAPI extensions will be used on the server. ISAPI extensions provide a mechanism to maintain a temporary or permanent connection with the users. These connections allow the Synchronization Server to process request and to send the appropriate DVD commands. The permanent connections are known as “Keep Alive” connections. ISAPI extension can also be used as an HTTP interface to a more traditional server, with all data returned as text.
  • Java 1.1 applets On the client side the approach is to use, but not limited to Java 1.1 applets, to initiate event start-up for the Synchronization server.
  • Java 1.1 applets The advantage of using Java 1.1 applets is to achieve platform independence for existing and future Java-enabled devices. JavaScript will be used to provide user interface navigation by “wrapping” the applet.
  • An ISAPI Internet Server Application Program Interface
  • CGI Common Gateway Interface
  • a disadvantage of a CGI application is that each time it is run, it runs as a separate process with its own address space, resulting in extra instructions that have to be performed, especially if many instances of it are running on behalf of users.
  • DLL Dynamic Link Library
  • HTTP Hypertext Transport Protocol
  • a special kind of ISAPI DLL is called an ISAPI filter, which can be designated to receive control for every HTTP request.
  • ISAPI server extension DLLs can be loaded and called by the HTTP server. Users can fill out forms and click a submit button to send data to a Web server and invoke an ISA, which can process the information to provide custom content or store it in a database. Web server extensions can use information in a database to build Web pages dynamically, and then send them to the client computers to be displayed. An application can add other custom functionality and provide data to the client using HTTP and HTML.
  • ISAPI filter is also a DLL that runs on an ISAPI-enabled HTTP server.
  • the filter registers for notification of events such as logging on or URL mapping. When the selected events occur, the filter is called, and one can monitor and change the data (on its way from the server to the client or vice versa).
  • ISAPI filters can be used to provide custom encryption or compression schemes, or additional authentication methods.
  • Such components include a Java/JavaScript Component, Synchronizer Component, LayerImpl Component, Business Layer Component, Configuration Manager Component, and DBConnect Component.
  • FIG. 6 illustrates a flow diagram for providing information on a synchronized event on a plurality of client apparatuses in accordance with one embodiment of the present invention.
  • a plurality of client apparatuses are connected via a network, as set forth earlier.
  • an application program is embedded on a site on the network in operation 602 .
  • Such application program may take the form of a JAVA applet, and the site may include a website on the Internet.
  • information is requested from a server on the network utilizing the application program. See operation 604 .
  • Such information relates to an event to be played back simultaneously on the client apparatuses and may include general information such as a start and stop time of the event, or more specific information about the event itself.
  • a script is received for displaying the information.
  • the script may take any form such as Perl, REXX (on IBM mainframes), and Tcl/Tk, and preferably includes a JAVAscript.
  • the JAVA applet may be further adapted to send a request to retrieve command information from the server for use with a playback device of one of the client apparatuses.
  • the commands may be adapted to playback the event on the playback device simultaneous with the playback of the event on the remaining client apparatuses. Further, the commands may include a start time when the playback of the event is to begin on each of the client apparatuses.
  • the JAVA applets and JAVAscript are used to communicate with the playback device of the client apparatuses.
  • the playback device includes a PCFriendly TM video player manufactured by Interactual®.
  • the Java applet is embedded within a web page and uses HTTP protocol to communicate to the synchronization server.
  • the applet could request event information from the server, and display it to the user via JavaScript.
  • the applet could also send a “BroadcastVideoEvent” request to retrieve DVD commands that can be passed to the video component, as set forth hereinabove.
  • FIG. 7 illustrates a method for creating a synchronizer object in order to playback an event simultaneously on a plurality of client apparatuses.
  • the synchronizer object is portion of the software that actually implements the synchronization procedure.
  • a request is received utilizing a network for viewing an event.
  • the request is queued in memory in operation 702 .
  • an object is created which is adapted to playback the event on a client apparatus simultaneous with the playback of the event on the remaining client apparatuses upon the receipt of an activation signal.
  • the activation signal may be provided using a clock of the client apparatus, or located at a different location, i.e. server.
  • the object identifies a start time when the playback of the event is to begin on each of the client apparatuses.
  • the object is sent to one of the client apparatuses utilizing the network for being stored therein.
  • the object may be adapted to playback the event which is stored in memory of the client apparatus. This may be accomplished by activating a digital video disc (DVD) player.
  • DVD digital video disc
  • the Synchronizer component when the Synchronizer component receives a “Broadcast VideoEvent” from the applet, it then places the request in the thread queue for processing. To process a request, the thread creates a “call back” object, if one does not exist for this event. The thread then adds the request to the “call back” object queue. This “call back” object will be invoked when it is time to play the DVD.
  • the Synchronizer component creates a Call Back COM object, LayerSink.
  • the Synchronizer component is also responsible for creating the LayerFactory interface which will be set forth hereinafter in greater detail.
  • FIG. 8 illustrates a flowchart for affording a scheduler object adapted to facilitate the playback of an event simultaneously on a plurality of networked client apparatuses.
  • the present method ensures that critical information is tracked during the synchronization of the event. Such critical information not only ensures proper synchronization, but also enables various peripheral features.
  • various values are determined including a current time, a start time when an event is to start, and a stop time when the event is to end. Thereafter, a length of the event is calculated based on the start time and the stop time in operation 802 .
  • the current time is determined by querying a clock of one of the client apparatuses.
  • a command is stored in memory in operation 804 .
  • the command may be adapted to automatically begin playing back the event at the start time.
  • the threshold period includes the time the users can be queued before the event.
  • chapter information may be stored in the memory if any portion of the length of the event takes place during the predetermined threshold period. This allows the command to automatically begin playing back the event at a predetermined chapter.
  • a loop is created at the start time during which a lapsed time of the event is tracked. This information may be used for various tracking purposes to decide when to issue commands to the user. In another embodiment, a second loop may be created upon the beginning of a chapter during which information on a next chapter is retrieved.
  • the “call back” object (LayerSink) is thus responsible for creating and communicating with the LayerImpl component.
  • the LayerImpl component acts as a scheduler, determining when to issue commands to the user.
  • LayerImpl will issue different DVD commands, based on the type of decoder the user has in their PC. LayerImpl will differentiate between the decoders by using the decoder information submitted from the client. The LayerImpl will pass the correct DVD command to the client, based on the decoder's capabilities. For example, if the decoder does not support the TimePlay event, then the server may send a ChapterPlay event and wait appropriately.
  • FIG. 9 is a flowchart delineating a method for identifying a plurality of events which are played back simultaneously on a plurality of networked client apparatuses. This features is important since a host server may be synchronizing more than one event at once, or during overlapping times. Such events must therefore be distinguished.
  • a plurality of events are stored in memory on a plurality of client apparatuses. Each of the events is assigned a unique identifier which is stored in the memory.
  • the client apparatuses are adapted to be coupled to a host computer via a network, as set forth hereinabove.
  • the identifier of the event which is stored in the memory of the client apparatuses is then retrieved utilizing the network. Such identifier is subsequently compared with an identifier of a scheduled event, as set forth in operation 906 . If the comparison renders a match, the playback of the event is begun on the appropriate client apparatuses. Note operation 908 .
  • CbusinessLayer thus differentiates events by the disk and location ids, uploaded by the client to guarantee backwards compatibility. As set forth earlier, late arrivals can always re-sync with the event.
  • FIG. 10 shows a flowchart delineating a technique for identifying playback devices of a plurality of client apparatuses which are networked to simultaneously playback an event.
  • the present technique is important since the playback devices of the various client apparatuses may differ in make and model. Thus, different commands are required therefor.
  • a type of the playback devices of the client apparatuses is first identified.
  • Such “type” may refer to a make, model, or any other distinguishing characteristic of the particular playback devices.
  • a command associated with the identified type of the playback device is then looked up in a look-up table. Note operation 1002 .
  • Such table may be located at the host server, or at any other location such as the client apparatuses.
  • This component is thus responsible for identifying what type of reference player is hosting the event.
  • the reference player can be the database, which contains the DVD commands or a real time player.
  • the “Synchronizer” table is queried for the host type. From that point forward, the scheduler would know from whom to receive data.
  • This component is responsible for communicating with the Synchronizer tables, and for providing access methods for the retrieved data. All interaction from the tables is on a read-only basis.
  • the LayerImpl component communicates with this component to retrieve DVD commands and event information.
  • MFC specific code may be avoided. Instead, STL may be used. ATL and/or MFC code may be encapsulated into separate classes and portioned from the rest of the code. Class implementations may use aggregation pattern to delegate business logic to the portable classes. Database connection classes may be separated and the communication protocol may be separated with respect to portability to Oracle and other platforms.
  • FIGS. 11 and 12 illustrate the order of events among the various components of the present invention.
  • FIG. 11 illustrates the manner in which a layer factory is created.
  • an event is first checked in a database server after which a business layer is created in a WEB server in a manner set forth hereinabove.
  • the foregoing components are then created.
  • FIG. 12 illustrates the manner in which user requests are processed.
  • communication is afforded with the video player on the client machine by means of JAVAscript and JAVA applets.
  • the WEB server communicates DVD commands to the video player via the JAVA applets, and also interfaces the database server via the various components thereof which were set forth hereinabove.
  • spirals may retrieve pre-recorded DVD commands from the database
  • alternate spirals may support a consumer as a host.
  • the architecture may also support plug-in components.
  • Alternate spirals may support the RealTimeConnector component, which accepts host user request and forwards them to the clients.
  • the instant architecture supports the DBConnector which accepts events from the database.
  • Clients may maintain connections throughout the event. This allows the host to send a various number of commands to the client of the event. Although the spiral disconnects users once a PLAY command has been issued, the Synchronizer class (which will be set forth later) adds each connection to a Thread Pool. This pool of connections can be left open during the life of the event.
  • Each request may be logged into the database to provide a reference for the future.
  • connections may be pooled to allow the synchronization server to direct consumer's machines to the certain locations throughout the entire event.
  • Synchronization events in alternate spirals may be defined as a combination of play from location event and the actual event. This way, one describes each event in the unambiguous way on the client side and synchronizes it with the server. For example, a situation may be considered where one fast forwards after a movie is played for 15 min and thereafter plays the scene in the movie. In such situation, one has to submit the information to the client player, indicating that it (player) has to start time play from 15 min into the movie and fast-forward to the certain location. A better way would be to analyze what is the next event after fast forwarding occurred and perform a combination for the play from location and next event. This design would require significant changes to the client infrastructure, including video object, remoteagent and provider and should be taken into consideration in any alternate client design.
  • FIGS. 13-16 illustrate various class/component diagrams.
  • FIGS. 13-16 illustrate a Synchronizer Class Diagram 1300 , Layerlmpl Class Diagram 1400 , Business Layer Class Diagram 1500 , and DBConnect Class Diagram 1600 , respectively.
  • FIG. 17 illustrates a logical sequence diagram 1700 .
  • the server receives a user request, it analyzes the authentication information of the request (date/time, disc id, user id, and BCA number) and the appropriate synchronization event stored in the database.
  • the database contains an event start threshold value measured in milliseconds. This threshold defines the amount of time prior to an event that a consumer is eligible to “connect” for the start of the event.
  • FIG. 18 illustrates a logical sequence diagram 1800 that shows server side collaboration.
  • server ISAPI extension receives a BroadcastVideoEvents request. It calls IA_BusinessServer via BeginProcess, to retrieve configuration information. Configuration information contains a playback connector. Playback connector identifies whether the server will have to communicate with a reference player or will it perform playback from the database.
  • ISAPI extension will call IA_BusinessServer CompareTime method and based on the results will send to the user a predefined web page indicating to retry later or return control to the web server, notifying it (web server) to keep the connection open. At this point connection is pooled and will be processed by the IA_BusinessServer at a time of the event.
  • FIG. 19 illustrates a logical sequence diagram 1900 showing client side collaboration in accordance with one embodiment of the present invention.
  • GetStartTimeDay Returns the time the event starts in days.
  • GetStartTimeYr Returns the time the event starts in year.
  • GetExpiredTime Returns lapse time of the event.
  • getServerTimeSec Returns the servers current in seconds.
  • getServerTimeMin Returns the servers current in minutes.
  • getServerTimeHr Returns the servers current in hours.
  • getServerTimeDay Returns the servers current in day.
  • getServerTimeMnth Returns the servers current in month.
  • getServerTimeYr Returns the servers current in year.
  • startProc Calls the ISAPIs “ServerInfo” method.
  • msgEvent Calls BroadCastEvent applet.
  • chkEvent Checks if an event is scheduled for the disk and location id.
  • get_nextDVDCommand Returns the next DVD command to play.
  • decoderArray Returns an array of decoder types.
  • get_hostType Returns the reference player host type.
  • This class provides a threading model that classes can use to derive.
  • start_address The routine at start_address must use the _cdecl calling convention and should have no return value. When the thread returns from that routine, it is terminated automatically.
  • start Starts the thread.
  • stop Stops the thread. Calls CloseHandle for the thread and event.
  • addrequest Adds the request to its vector.
  • getBLayerInfo Responsible for getting information about the event.
  • notifyCreateLayer responsible for creating a “businessLayerProp”.
  • layerSink represents a sink interface and stores a queue of requests. It creates a connection point object.
  • This call back object allows asynchronously processing.
  • connection point container creates a connection point (call back) by calling AtlAdvise, between the connection point container and the client sink object. This allows the client to receive events.
  • addRequest Adds the request to its vector.
  • createBusinessLayer Creates a business layer. Create the connection point.
  • updatetime This call back function translates the time and sends the command to
  • the “Synchronizers” createBusinessLayer method creates a class object from the “IBusinessLayer” interface. ⁇ The class object is part of the LayerImpl project>
  • the “Initialize” method then calls the “ChkValidEvent” method, which then creates a layerthread object.
  • This object acts as a scheduler, processing request from its queue.
  • startThread Processes requests from the queue
  • This object manages businesslayer objects.
  • Business layer objects communicate with the reference player and notify the user which DVD command to play.
  • This COM object is the servers Connectable Point object.
  • This server object supports connections to sink interfaces. These sink interfaces reside on the client side and are equivalent to the “call back” functions in Windows.
  • put_set_layer call the “CLayerFactoryImpl” add( ) method. Supplying the “businesslayer” object.

Abstract

A system, method and article of manufacture are provided for delayed synchronization of an event on a plurality of client apparatuses. First, a plurality of client apparatuses are connected via a network and an event is stored in memory on the client apparatuses. The event is then simultaneously played back on the client apparatuses utilizing the network. During the simultaneous playback, a request may be received from one of the client apparatuses for that particular client to be included in the synchronized event. In response to the request, information is transmitted to the requesting client apparatus utilizing the network. This information is adapted for identifying a location in the memory where the event is currently being played back on the remaining client apparatuses. This allows the simultaneous playback of the event on the requesting client apparatus.

Description

    RELATED APPLICATIONS
  • This application is a Continuation of U.S. patent application Ser. No. 09/488,613, filed Jan. 20, 2000, entitled A SYSTEM, METHOD, AND ARTICLE OF MANUFACTURE FOR LATE SYNCHRONIZATION DURING THE EXECUTION OF A MULTIMEDIA EVENT ON A PLURALITY OF CLIENT COMPUTERS, now pending, which is incorporated herein by reference.[0001]
  • FIELD OF THE INVENTION
  • The present invention relates to network synchronization and more particularly to synchronizing the playback of a multimedia event on a plurality of client apparatuses. [0002]
  • BACKGROUND OF THE INVENTION
  • Systems such as the Internet typically are point-to-point (or unicast) systems in which a message is converted into a series of addressed packets which are routed from a source node through a plurality of routers to a destination node. In most communication protocols the packet includes a header which contains the addresses of the source and the destination nodes as well as a sequence number which specifies the packet's order in the message. [0003]
  • In general, these systems do not have the capability of broadcasting a message from a source node to all the other nodes in the network because such a capability is rarely of much use and could easily overload the network. However, there are situations where it is desirable for one node to communicate with some subset of all the nodes. where it is desirable for one node to communicate with some subset of all the nodes. For example, multi-party conferencing capability analogous to that found in the public telephone system and broadcasting to a limited number of nodes are of considerable interest to users of packet-switched networks. To satisfy such demands, packets destined for several recipients have been encapsulated in a unicast packet and forwarded from a source to a point in a network where the packets have been replicated and forwarded on to all desired recipients. This technique is known as IP Multicasting and the network over which such packets are routed is referred to as the Multicast Backbone or MBONE. More recently, routers have become available which can route the multicast addresses (class D addresses) provided for in communication protocols such as TCP/IP and UDP/IP. A multicast address is essentially an address for a group of host computers who have indicated their desire to participate in that group. Thus, a multicast packet can be routed from a source node through a plurality of multicast routers (or mrouters) to one or more devices receiving the multicast packets. From there the packet is distributed to all the host computers that are members of the multicast group. [0004]
  • These techniques have been used to provide on the Internet audio and video conferencing as well as radio-like broadcasting to groups of interested parties. See, for example, K. Savetz et al. MBONE Multicasting Tomorrow's Internet (IDG Books WorldWide Inc., 1996). [0005]
  • Further details concerning technical aspects of multicasting may be found in the Internet documents Request for Comments (RFC) 1112 and 1458 which are reproduced at Appendices A and B of the Savetz book and in D. P. Brutaman et al., “MBONE provides Audio and Video Across the Internet,” IEEE Computer, Vol. 27, No. 4, pp. 30-36 (April 1994), all of which are incorporated herein by reference. [0006]
  • Multimedia computer systems have become increasingly popular over the last several years due to their versatility and their interactive presentation style. A multimedia computer system can be defined as a computer system having a combination of video and audio outputs for presentation of audio-visual displays. A modem multimedia computer system typically includes one or more storage devices such as an optical drive, a CD-ROM, a hard drive, a videodisc, or an audiodisc, and audio and video data are typically stored on one or more of these mass storage devices. In some file formats the audio and video are interleaved together in a single file, while in other formats the audio and video data are stored in different files, many times on different storage media. Audio and video data for a multimedia display may also be stored in separate computer systems that are networked together. In this instance, the computer system presenting the multimedia display would receive a portion of the necessary data from the other computer system via the network cabling. [0007]
  • Graphic images used in Windows multimedia applications can be created in either of two ways, these being bit-mapped images and vector-based images. Bit-mapped images comprise a plurality of picture elements (pixels) and are created by assigning a color to each pixel inside the image boundary. Most bit-mapped color images require one byte per pixel for storage, so large bit-mapped images create correspondingly large files. For example, a full-screen, 256-color image in 640-by-480-pixel VGA mode requires 307,200 bytes of storage, if the data is not compressed. Vector-based images are created by defining the end points, thickness, color, pattern and curvature of lines and solid objects comprised within the image. Thus, a vector-based image includes a definition which consists of a numerical representation of the coordinates of the object, referenced to a corner of the image. [0008]
  • Bit-mapped images are the most prevalent type of image storage format, and the most common bit-mapped-image file formats are as follows. A file format referred to as BMP is used for Windows bit-map files in 1-, 2-, 4-, 8-, and 24-bit color depths. BMP files contain a bit-map header that defines the size of the image, the number of color planes, the type of compression used (if any), and the palette used. The Windows DIB (device-independent bit-map) format is a variant of the BMP format that includes a color table defining the RGB (red green blue) values of the colors used. Other types of bit-map formats include the TIF (tagged image format file), the PCX (Zsoft Personal Computer Paintbrush Bitmap) file format, the GIF (graphics interchange file) format, and the TGA (Texas Instruments Graphic Architecture) file format. [0009]
  • The standard Windows format for bit-mapped images is a 256-color device-independent bit map (DIB) with a BMP (the Windows bit-mapped file format) or sometimes a DIB extension. The standard Windows format for vector-based images is referred to as WMF (Windows meta file). [0010]
  • Full-motion video implies that video images shown on the computer's screen simulate those of a television set with identical (30 frames-per-second) frame rates, and that these images are accompanied by high-quality stereo sound. A large amount of storage is required for high-resolution color images, not to mention a full-motion video sequence. For example, a single frame of NTSC video at 640-by-400-pixel resolution with 16-bit color requires 512K of data per frame. At 30 flames per second, over 15 Megabytes of data storage are required for each second of full motion video. Due to the large amount of storage required for full motion video, various types of video compression algorithms are used to reduce the amount of necessary storage. Video compression can be performed either in real-time, i.e., on the fly during video capture, or on the stored video file after the video data has been captured and stored on the media. In addition, different video compression methods exist for still graphic images and for full-motion video. [0011]
  • Examples of video data compression for still graphic images are RLE (run-length encoding) and JPEG (Joint Photographic Experts Group) compression. RLE is the standard compression method for Windows BMP and DIB files. The RLE compression method operates by testing for duplicated pixels in a single line of the bit map and stores the number of consecutive duplicate pixels rather than the data for the pixel itself. JPEG compression is a group of related standards that provide either lossless (no image quality degradation) or lossy (imperceptible to severe degradation) compression types. Although JPEG compression was designed for the compression of still images rather than video, several manufacturers supply JPEG compression adapter cards for motion video applications. [0012]
  • In contrast to compression algorithms for still images, most video compression algorithms are designed to compress full motion video. Video compression algorithms for motion video generally use a concept referred to as interframe key frame. Successive frames are compared with the key frame, and only the differences between the digitized data from the key frame and from the successive frames are stored. Periodically, such as when new scenes are displayed, new key frames are digitized and stored, and subsequent comparisons begin from this new reference point. It is noted that interframe compression ratios are content-dependent, i.e., if the video clip being compressed includes many abrupt scene transitions from one image to another, the compression is less efficient. Examples of video compression which use an interframe compression technique are MPEG, DVI and Indeo, among others. [0013]
  • MPEG (Moving Pictures Experts Group) compression is a set of methods for compression and decompression of full motion video images that uses the interframe compression technique described above. The MPEG standard requires that sound be recorded simultaneously with the video data, and the video and audio data are interleaved in a single file to attempt to maintain the video and audio synchronized during playback. The audio data is typically compressed as well, and the MPEG standard specifies an audio compression method referred to as ADPCM (Adaptive Differential Pulse Code Modulation) for audio data. [0014]
  • A standard referred to as Digital Video Interactive (DVI) format developed by Intel Corporation is a compression and storage format for full-motion video and high-fidelity audio data. The DVI standard uses interframe compression techniques similar to that of the MPEG standard and uses ADPCM compression for audio data. The compression method used in DVI is referred to as RTV 2.0 (real time video), and this compression method is incorporated into Intel's AVK (audio/video kernel) software for its DVI product line. IBM has adopted DVI as the standard for displaying video for its Ultimedia product line. The DVI file format is based on the Intel i750 chipset and is supported through the Media Control Interface (MCI) for Windows. Microsoft and Intel jointly announced the creation of the DV MCI (digital video media control interface) command set for Windows 3.1 in 1992. [0015]
  • The Microsoft Audio Video Interleaved (AVI) format is a special compressed file structure format designed to enable video images and synchronized sound stored on CD-ROMs to be played on PCs with standard VGA displays and audio adapter cards. The AVI compression method uses an interframe method, i.e., the differences between successive frames are stored in a manner similar to the compression methods used in DVI and MPEG. The AVI format uses symmetrical software compression-decompression techniques, i.e., both compression and decompression are performed in real time. Thus AVI files can be created by recording video images and sound in AVI format from a VCR or television broadcast in real time, if enough free hard disk space is available. [0016]
  • Despite these compression algorithms, it is very difficult to simultaneously multicast multimedia material due to bandwidth restraints. This problem is unavoidable with present technology since such large amounts of data must be transferred over networks such as the Internet from a single host server to numerous client computers. [0017]
  • SUMMARY OF THE INVENTION
  • A system, method and article of manufacture are provided for delayed synchronization of an event on a plurality of client apparatuses. First, a plurality of client apparatuses are connected via a network and an event is stored in memory on the client apparatuses. The event is then simultaneously played back on the client apparatuses utilizing the network. During the simultaneous playback, a request may be received from one of the client apparatuses for that particular client to be included in the synchronized event. In response to the request, information is transmitted to the requesting client apparatus utilizing the network. This information is adapted for identifying a location in the memory where the event is currently being played back on the remaining client apparatuses. This allows the simultaneous playback of the event on the requesting client apparatus. In one embodiment of the present invention, the request may be received utilizing the network. [0018]
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • The invention will be better understood when consideration is given to the following detailed description thereof. Such description makes reference to the annexed drawings wherein: [0019]
  • FIG. 1 is a schematic diagram of a hardware implementation of one embodiment of the present invention; [0020]
  • FIG. 2 illustrates a flowchart delineating a method for synchronizing an event on a plurality of client apparatuses in accordance with one embodiment of the present invention; [0021]
  • FIG. 3 illustrates a flowchart delineating a method for storing synchronization information for subsequent playback of an event in accordance with one embodiment of the present invention; [0022]
  • FIG. 4 illustrates a flowchart setting forth a method for providing overlays during a synchronized event on a plurality of client apparatuses in accordance with one embodiment of the present invention; [0023]
  • FIG. 5 illustrates a flow diagram for delayed synchronization of an event on a plurality of client apparatuses in accordance with one embodiment of the present invention; [0024]
  • FIG. 6 illustrates a flow diagram for providing information on a synchronized event on a plurality of client apparatuses in accordance with one embodiment of the present invention; [0025]
  • FIG. 7 illustrates a method for creating a synchronizer object in order to playback an event simultaneously on a plurality of client apparatuses in accordance with one embodiment of the present invention; [0026]
  • FIG. 8 illustrates a flowchart for affording a scheduler object adapted to facilitate the playback of an event simultaneously on a plurality of networked client apparatuses in accordance with one embodiment of the present invention; [0027]
  • FIG. 9 is a flowchart delineating a method for identifying a plurality of events which are played back simultaneously on a plurality of networked client apparatuses in accordance with one embodiment of the present invention; [0028]
  • FIG. 10 shows a flowchart delineating a technique for interfacing a plurality of different types of playback devices of client apparatuses which are networked to simultaneously playback an event in accordance with one embodiment of the present invention; [0029]
  • FIG. 11 illustrates the manner in which a layer factory is created in accordance with one embodiment of the present invention; [0030]
  • FIG. 12 illustrates the manner in which user requests are processed in accordance with one embodiment of the present invention; [0031]
  • FIGS. 13-16 illustrate various class/component diagrams in accordance with one embodiment of the present invention; [0032]
  • FIG. 17 illustrates a logical sequence diagram in accordance with one embodiment of the present invention; [0033]
  • FIG. 18 illustrates a logical sequence diagram that shows server side collaboration in accordance with one embodiment of the present invention; and [0034]
  • FIG. 19 illustrates a logical sequence diagram showing client side collaboration in accordance with one embodiment of the present invention. [0035]
  • DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
  • FIGS. 1-19 illustrate a system for synchronizing an event on a plurality of client apparatuses. Prior to use, an event is stored in memory on at least one of the client apparatuses. Such client apparatuses are adapted to be connected to a network along with a host computer(s). In operation, information is transmitted from the host computer to the at least one client apparatus utilizing the network. This information allows for the simultaneous and synchronous playback of the event on each of the client apparatuses. [0036]
  • In various embodiments, the client apparatuses may take the form of computers, televisions, stereos, home appliances, or any other types of devices. In one embodiment, the client apparatuses and the host computer each include a computer such as an IBM compatible computer, Apple Macintosh computer or UNIX based workstation. [0037]
  • A representative hardware environment is depicted in FIG. 1, which illustrates a typical hardware configuration of a workstation in accordance with a preferred embodiment having a [0038] central processing unit 110, such as a microprocessor, and a number of other units interconnected via a system bus 112. The workstation shown in FIG. 1 includes a Random Access Memory (RAM) 114, Read Only Memory (ROM) 116, an I/O adapter 118 for connecting peripheral devices such as disk storage units 120 (i.e. DVD playback device) to the bus 112, a user interface adapter 122 for connecting a keyboard 124, a mouse 126, a speaker 128, a microphone 132, and/or other user interface devices such as a touch screen (not shown) to the bus 112, communication adapter 134 for connecting the workstation to a communication network (e.g., a data processing network) and a display adapter 136 for connecting the bus 112 to a display device 138. The workstation typically has resident thereon an operating system such as the Microsoft Windows NT or Windows/95 Operating System (OS), the IBM OS/2 operating system, the MAC OS, or UNIX operating system. Those skilled in the art will appreciate that the present invention may also be implemented on platforms and operating systems other than those mentioned.
  • A preferred embodiment is written using JAVA, C, and the C++ language and utilizes object oriented programming methodology. Object oriented programming (OOP) has become increasingly used to develop complex applications. As OOP moves toward the mainstream of software design and development, various software solutions require adaptation to make use of the benefits of OOP. A need exists for these principles of OOP to be applied to a messaging interface of an electronic messaging system such that a set of OOP classes and objects for the messaging interface can be provided. [0039]
  • OOP is a process of developing computer software using objects, including the steps of analyzing the problem, designing the system, and constructing the program. An object is a software package that contains both data and a collection of related structures and procedures. Since it contains both data and a collection of structures and procedures, it can be visualized as a self-sufficient component that does not require other additional structures, procedures or data to perform its specific task. OOP, therefore, views a computer program as a collection of largely autonomous components, called objects, each of which is responsible for a specific task. This concept of packaging data, structures, and procedures together in one component or module is called encapsulation. [0040]
  • In general, OOP components are reusable software modules which present an interface that conforms to an object model and which are accessed at run-time through a component integration architecture. A component integration architecture is a set of architecture mechanisms which allow software modules in different process spaces to utilize each others capabilities or functions. This is generally done by assuming a common component object model on which to build the architecture. It is worthwhile to differentiate between an object and a class of objects at this point. An object is a single instance of the class of objects, which is often just called a class. A class of objects can be viewed as a blueprint, from which many objects can be formed. [0041]
  • OOP allows the programmer to create an object that is a part of another object. For example, the object representing a piston engine is said to have a composition-relationship with the object representing a piston. In reality, a piston engine comprises a piston, valves and many other components; the fact that a piston is an element of a piston engine can be logically and semantically represented in OOP by two objects. [0042]
  • OOP also allows creation of an object that “depends from” another object. If there are two objects, one representing a piston engine and the other representing a piston engine wherein the piston is made of ceramic, then the relationship between the two objects is not that of composition. A ceramic piston engine does not make up a piston engine. Rather it is merely one kind of piston engine that has one more limitation than the piston engine; its piston is made of ceramic. In this case, the object representing the ceramic piston engine is called a derived object, and it inherits all of the aspects of the object representing the piston engine and adds further limitation or detail to it. The object representing the ceramic piston engine “depends from” the object representing the piston engine. The relationship between these objects is called inheritance. [0043]
  • When the object or class representing the ceramic piston engine inherits all of the aspects of the objects representing the piston engine, it inherits the thermal characteristics of a standard piston defined in the piston engine class. However, the ceramic piston engine object overrides these ceramic specific thermal characteristics, which are typically different from those associated with a metal piston. It skips over the original and uses new functions related to ceramic pistons. Different kinds of piston engines have different characteristics, but may have the same underlying functions associated with it (e.g., how many pistons in the engine, ignition sequences, lubrication, etc.). To access each of these functions in any piston engine object, a programmer would call the same functions with the same names, but each type of piston engine may have different/overriding implementations of functions behind the same name. This ability to hide different implementations of a function behind the same name is called polymorphism and it greatly simplifies communication among objects. [0044]
  • With the concepts of composition-relationship, encapsulation, inheritance and polymorphism, an object can represent just about anything in the real world. In fact, one's logical perception of the reality is the only limit on determining the kinds of things that can become objects in object-oriented software. Some typical categories are as follows: [0045]
  • Objects can represent physical objects, such as automobiles in a traffic-flow simulation, electrical components in a circuit-design program, countries in an economics model, or aircraft in an air-traffic-control system. [0046]
  • Objects can represent elements of the computer-user environment such as windows, menus or graphics objects. [0047]
  • An object can represent an inventory, such as a personnel file or a table of the latitudes and longitudes of cities. [0048]
  • An object can represent user-defined data types such as time, angles, and complex numbers, or points on the plane. [0049]
  • With this enormous capability of an object to represent just about any logically separable matters, OOP allows the software developer to design and implement a computer program that is a model of some aspects of reality, whether that reality is a physical entity, a process, a system, or a composition of matter. Since the object can represent anything, the software developer can create an object which can be used as a component in a larger software project in the future. [0050]
  • If 90% of a new OOP software program consists of proven, existing components made from preexisting reusable objects, then only the remaining 10% of the new software project has to be written and tested from scratch. Since 90% already came from an inventory of extensively tested reusable objects, the potential domain from which an error could originate is 10% of the program. As a result, OOP enables software developers to build objects out of other, previously built objects. [0051]
  • This process closely resembles complex machinery being built out of assemblies and sub-assemblies. OOP technology, therefore, makes software engineering more like hardware engineering in that software is built from existing components, which are available to the developer as objects. All this adds up to an improved quality of the software as well as an increased speed of its development. [0052]
  • Programming languages are beginning to fully support the OOP principles, such as encapsulation, inheritance, polymorphism, and composition-relationship. With the advent of the C++ language, many commercial software developers have embraced OOP. C++ is an OOP language that offers a fast, machine-executable code. Furthermore, C++ is suitable for both commercial-application and systems-programming projects. For now, C++ appears to be the most popular choice among many OOP programmers, but there is a host of other OOP languages, such as Smalltalk, Common Lisp Object System (CLOS), and Eiffel. Additionally, OOP capabilities are being added to more traditional popular computer programming languages such as Pascal. [0053]
  • The benefits of object classes can be summarized, as follows: [0054]
  • Objects and their corresponding classes break down complex programming problems into many smaller, simpler problems. [0055]
  • Encapsulation enforces data abstraction through the organization of data into small, independent objects that can communicate with each other. Encapsulation protects the data in an object from accidental damage, but allows other objects to interact with that data by calling the object's member functions and structures. [0056]
  • Subclassing and inheritance make it possible to extend and modify objects through deriving new kinds of objects from the standard classes available in the system. Thus, new capabilities are created without having to start from scratch. [0057]
  • Polymorphism and multiple inheritance make it possible for different programmers to mix and match characteristics of many different classes and create specialized objects that can still work with related objects in predictable ways. [0058]
  • Class hierarchies and containment hierarchies provide a flexible mechanism for modeling real-world objects and the relationships among them. [0059]
  • Libraries of reusable classes are useful in many situations, but they also have some limitations. For example: [0060]
  • Complexity. In a complex system, the class hierarchies for related classes can become extremely confusing, with many dozens or even hundreds of classes. [0061]
  • Flow of control. A program written with the aid of class libraries is still responsible for the flow of control (i.e., it must control the interactions among all the objects created from a particular library). The programmer has to decide which functions to call at what times for which kinds of objects. [0062]
  • Duplication of effort. Although class libraries allow programmers to use and reuse many small pieces of code, each programmer puts those pieces together in a different way. Two different programmers can use the same set of class libraries to write two programs that do exactly the same thing but whose internal structure (i.e., design) may be quite different, depending on hundreds of small decisions each programmer makes along the way. Inevitably, similar pieces of code end up doing similar things in slightly different ways and do not work as well together as they should. [0063]
  • Class libraries are very flexible. As programs grow more complex, more programmers are forced to reinvent basic solutions to basic problems over and over again. A relatively new extension of the class library concept is to have a framework of class libraries. This framework is more complex and consists of significant collections of collaborating classes that capture both the small scale patterns and major mechanisms that implement the common requirements and design in a specific application domain. They were first developed to free application programmers from the chores involved in displaying menus, windows, dialog boxes, and other standard user interface elements for personal computers. [0064]
  • Frameworks also represent a change in the way programmers think about the interaction between the code they write and code written by others. In the early days of procedural programming, the programmer called libraries provided by the operating system to perform certain tasks, but basically the program executed down the page from start to finish, and the programmer was solely responsible for the flow of control. This was appropriate for printing out paychecks, calculating a mathematical table, or solving other problems with a program that executed in just one way. [0065]
  • The development of graphical user interfaces began to turn this procedural programming arrangement inside out. These interfaces allow the user, rather than program logic, to drive the program and decide when certain actions should be performed. Today, most personal computer software accomplishes this by means of an event loop which monitors the mouse, keyboard, and other sources of external events and calls the appropriate parts of the programmer's code according to actions that the user performs. The programmer no longer determines the order in which events occur. Instead, a program is divided into separate pieces that are called at unpredictable times and in an unpredictable order. By relinquishing control in this way to users, the developer creates a program that is much easier to use. Nevertheless, individual pieces of the program written by the developer still call libraries provided by the operating system to accomplish certain tasks, and the programmer must still determine the flow of control within each piece after it's called by the event loop. Application code still “sits on top of” the system. [0066]
  • Even event loop programs require programmers to write a lot of code that should not need to be written separately for every application. The concept of an application framework carries the event loop concept further. Instead of dealing with all the nuts and bolts of constructing basic menus, windows, and dialog boxes and then making these things all work together, programmers using application frameworks start with working application code and basic user interface elements in place. Subsequently, they build from there by replacing some of the generic capabilities of the framework with the specific capabilities of the intended application. [0067]
  • Application frameworks reduce the total amount of code that a programmer has to write from scratch. However, because the framework is really a generic application that displays windows, supports copy and paste, and so on, the programmer can also relinquish control to a greater degree than event loop programs permit. The framework code takes care of almost all event handling and flow of control, and the programmer's code is called only when the framework needs it (e.g., to create or manipulate a proprietary data structure). [0068]
  • A programmer writing a framework program not only relinquishes control to the user (as is also true for event loop programs), but also relinquishes the detailed flow of control within the program to the framework. This approach allows the creation of more complex systems that work together in interesting ways, as opposed to isolated programs, having custom code, being created over and over again for similar problems. [0069]
  • Thus, as is explained above, a framework basically is a collection of cooperating classes that make up a reusable design solution for a given problem domain. It typically includes objects that provide default behavior (e.g., for menus and windows), and programmers use it by inheriting some of that default behavior and overriding other behavior so that the framework calls application code at the appropriate times. [0070]
  • There are three main differences between frameworks and class libraries: [0071]
  • Behavior versus protocol. Class libraries are essentially collections of behaviors that you can call when you want those individual behaviors in your program. A framework, on the other hand, provides not only behavior but also the protocol or set of rules that govern the ways in which behaviors can be combined, including rules for what a programmer is supposed to provide versus what the framework provides. [0072]
  • Call versus override. With a class library, the code the programmer instantiates objects and calls their member functions. It's possible to instantiate and call objects in the same way with a framework (i.e., to treat the framework as a class library), but to take full advantage of a framework's reusable design, a programmer typically writes code that overrides and is called by the framework. The framework manages the flow of control among its objects. Writing a program involves dividing responsibilities among the various pieces of software that are called by the framework rather than specifying how the different pieces should work together. [0073]
  • Implementation versus design. With class libraries, programmers reuse only implementations, whereas with frameworks, they reuse design. A framework embodies the way a family of related programs or pieces of software work. It represents a generic design solution that can be adapted to a variety of specific problems in a given domain. For example, a single framework can embody the way a user interface works, even though two different user interfaces created with the same framework might solve quite different interface problems. [0074]
  • Thus, through the development of frameworks for solutions to various problems and programming tasks, significant reductions in the design and development effort for software can be achieved. A preferred embodiment of the invention utilizes HyperText Markup Language (HTML) to implement documents on the Internet together with a general-purpose secure communication protocol for a transport medium between the client and the Newco. HTTP or other protocols could be readily substituted for HTML without undue experimentation. Information on these products is available in T. Berners-Lee, D. Connoly, “RFC 1866: Hypertext Markup Language—2.0” (November 1995); and R. Fielding, H, Frystyk, T. Berners-Lee, J. Gettys and J. C. Mogul, “Hypertext Transfer Protocol—HTTP/1.1: HTTP Working Group Internet Draft” (May 2, 1996). HTML is a simple data format used to create hypertext documents that are portable from one platform to another. HTML documents are SGML documents with generic semantics that are appropriate for representing information from a wide range of domains. HTML has been in use by the World-Wide Web global information initiative since 1990. HTML is an application of ISO Standard 8879; 1986 Information Processing Text and Office Systems; Standard Generalized Markup Language (SGML). [0075]
  • To date, Web development tools have been limited in their ability to create dynamic Web applications which span from client to server and interoperate with existing computing resources. Until recently, HTML has been the dominant technology used in development of Web-based solutions. However, HTML has proven to be inadequate in the following areas: [0076]
  • Poor performance; [0077]
  • Restricted user interface capabilities; [0078]
  • Can only produce static Web pages; [0079]
  • Lack of interoperability with existing applications and data; and [0080]
  • Inability to scale. [0081]
  • Sun Microsystem's Java language solves many of the client-side problems by: [0082]
  • Improving performance on the client side; [0083]
  • Enabling the creation of dynamic, real-time Web applications; and [0084]
  • Providing the ability to create a wide variety of user interface components. [0085]
  • With Java, developers can create robust User Interface (UI) components. Custom “widgets” (e.g., real-time stock tickers, animated icons, etc.) can be created, and client-side performance is improved. Unlike HTML, Java supports the notion of client-side validation, offloading appropriate processing onto the client for improved performance. Dynamic, real-time Web pages can be created. Using the above-mentioned custom UI components, dynamic Web pages can also be created. [0086]
  • Sun's Java language has emerged as an industry-recognized language for “programming the Internet.” Sun defines Java as: “a simple, object-oriented, distributed, interpreted, robust, secure, architecture-neutral, portable, high-performance, multithreaded, dynamic, buzzword-compliant, general-purpose programming language. Java supports programming for the Internet in the form of platform-independent Java applets.” Java applets are small, specialized applications that comply with Sun's Java Application Programming Interface (API) allowing developers to add “interactive content” to Web documents (e.g., simple animations, page adornments, basic games, etc.). Applets execute within a Java-compatible browser (e.g., Netscape Navigator) by copying code from the server to client. From a language standpoint, Java's core feature set is based on C++. Sun's Java literature states that Java is basically, “C++ with extensions from Objective C for more dynamic method resolution.”[0087]
  • Another technology that provides similar function to JAVA is provided by Microsoft and ActiveX Technologies, to give developers and Web designers wherewithal to build dynamic content for the Internet and personal computers. ActiveX includes tools for developing animation, 3-D virtual reality, video and other multimedia content. The tools use Internet standards, work on multiple platforms, and are being supported by over 100 companies. The group's building blocks are called ActiveX Controls, small, fast components that enable developers to embed parts of software in hypertext markup language (HTML) pages. ActiveX Controls work with a variety of programming languages including Microsoft Visual C++, Borland Delphi, Microsoft Visual Basic programming system and, in the future, Microsoft's development tool for Java, code named “Jakarta.” ActiveX Technologies also includes ActiveX Server Framework, allowing developers to create server applications. One of ordinary skill in the art readily recognizes that ActiveX could be substituted for JAVA without undue experimentation to practice the invention. [0088]
  • Synchronization Overview
  • FIG. 2 illustrates a flowchart delineating a method for synchronizing an event on a plurality of client apparatuses. First, in [0089] operation 200, an event is stored in memory on at least one of the client apparatuses. In various embodiments, the memory may take the form of an electromagnetic medium, or any type of optical storage device, i.e. CD-audio. In a primary aspect of the present invention, the memory includes a digital video disc (DVD) (audio or video). Further, for reasons that will soon become apparent, the information includes chapter information associated with the DVD. In such embodiment where the memory is portable, the user may be required to purchase the memory, i.e. DVD, in order to participate in a synchronized event, thus increasing the sale of DVD's.
  • It should be noted that the event need not be necessarily stored in memory on all of the client apparatuses, but rather stored on one or some of the client apparatuses and streamed to the remaining client apparatuses at variant rates. This may be feasibly accomplished if the client apparatus(es) containing the stored event has a high-bandwidth connection with the remaining client apparatuses. For example, the client apparatus(es) containing the stored event may include a server that has a connection to a plurality of televisions via a cable network, i.e. WEBTV. Similar functionality may be achieved via a broadcast medium. The present invention is thus flexible by having an ability to host user events and corporative events. [0090]
  • In one embodiment, the event includes a video and audio presentation such as movie, a concert, and/or a theatrical event. It should be noted, however, that the event may included any recording capable of being played back for entertainment, education, informative or other similar purposes. [0091]
  • In use, the client apparatuses and a host computer are adapted to be connected to a network. Such network may include a wide, local or any other type of communication network. For example, a wide area network such as the Internet may be employed which operates using TCP/IP or IPX protocols. [0092]
  • In [0093] operation 202, information is transmitted from the host computer to the appropriate client apparatuses utilizing the network. This information allows for the simultaneous and synchronous playback of the event on each of the client apparatuses. In one embodiment, the information may also include a start time when the playback of the event is to begin on each of the client apparatuses. Further, an ending time may be included when the playback of the event is to end on each of the client apparatuses. Still yet, “play” command information may be sent to the client apparatuses at the start time. As an option, input may be received from the user, and used to alter the playback of the event. The host server, or synchronization server, can also control various streams of a variant rate and different hardware associated with those streams.
  • The present invention thus has the ability to synchronize video playback for one or multiple (thousands) users from one or multiple physical locations, and to synchronize with external video, audio and/or data streams. [0094]
  • Users of the present invention are at multiple physical locations and host servers may also be at different locations. The present invention is thus a scalable system which is capable of servicing an unlimited number of users. Since the content is local to the user machine, no high network bandwidth is required. [0095]
  • History Download Capabilities [0096]
  • FIG. 3 illustrates a flowchart delineating a method for storing synchronization information for subsequent playback of an event. Initially, in [0097] operation 300, an event is stored in memory on at least one of the client apparatuses, as set forth earlier. These client apparatuses are adapted to be connected to a network along with a host computer during use.
  • In [0098] operation 302, information is stored on the host computer(s) for allowing the simultaneous playback of the event on each of the client apparatuses. In one embodiment, the information may include a history and data associated with the synchronous playback. In particular, the history may include any overlaid material(as will be described hereinafter in greater detail), any specific commands affecting the playback of the information, or any other type of general information, i.e. start time, end time, etc.
  • In [0099] operation 304, the information may be downloaded utilizing the network at any time after the synchronous playback of the event. Such downloaded information may then be used for playback after the simultaneous playback of the event. As such, the present invention has the ability to allow users to download a history and data associated with a particular synchronization event and play it later.
  • Overlay Synchronization [0100]
  • FIG. 4 illustrates a flowchart setting forth a method for providing overlays during a synchronized event on a plurality of client apparatuses or any other source. First, in [0101] operation 400, a plurality of client apparatuses are connected via a network. In operation 402, an event may be simultaneously played back on the client apparatuses utilizing the network, as set forth earlier.
  • During the playback of the event, visual and/or audio material may also be overlaid on the event based on input received from at least one of the client apparatuses. See [0102] operation 404. This may be accomplished by transmitting the overlay material from one of the client apparatuses to the host computer or any other server, and multicasting the same to the remaining client apparatuses.
  • As an option, the overlay material may include annotations on a display of the client apparatus. For example, the overlay material may include sketches which are inputted by way of a stylus-based input screen or a keyboard or the like, along with a voiceover inputted by way of a microphone or voice synthesizer. Such capability may also be quite valuable in an educational environment. [0103]
  • In one embodiment, the overlay material may also be displayed on each of the client apparatuses utilizing the network. This allows each of the users to experience the overlay in real-time during the simultaneous playback of the event. As an option, the user inputting the overlay material may select which users may experience the overlay material. The client apparatus that provided the overlay material may also be identified to the users experiencing the overlay material. [0104]
  • It should be noted that various bi-directional communication may be enabled for allowing data to travel to and from the server. For instance, the playback of the event on the client apparatuses may be altered in any feasible way based on input from a user. [0105]
  • Late Synchronization [0106]
  • FIG. 5 illustrates a flow diagram for delayed synchronization of an event on a plurality of client apparatuses. First, in [0107] operation 500, a plurality of client apparatuses are connected via a network and an event is stored in memory on the client apparatuses. The event is then simultaneously played back on the client apparatuses utilizing the network, as set forth earlier. Note operation 502.
  • During the simultaneous playback, a request may be received from one of the client apparatuses for that particular to be included in the synchronized event, as set forth in [0108] operation 504. This request may be received after the synchronized event has already begun while it is still playing. Further, the request may be submitted via a site on a network, i.e. website.
  • In response to the request, information is transmitted in [0109] operation 506 to the requesting client apparatus utilizing the network. This information is adapted for identifying a location in the memory where the event is currently being played back. This-allows the simultaneous playback of the event on the requesting client apparatus.
  • The end users are thus able to come in at a later time and to be synchronized with the event. Targeted synchronization and various filters criteria can be applied to target different audiences. Also language and cultural differences can be taken into account. Still yet, the present invention may be adapted to address users on different hardware platforms (MAC, PC, set-top boxes). This may be accomplished by identifying the user using a cookie, a user profile which is identified by way of a log in, or a Burn Cut Area (BCA) of the disc. [0110]
  • An example setting forth details relating to identifying DVDs will now be set forth. First, a content owner (such as studio) requests use of the BCA on their DVDs. Based on request, the replicator (examples include WAMO, Panasonic, Nimbus, Technicolor, Pioneer, Crest) adds unique BCA number to every DVD. Adding BCA number to each DVD requires a special (YAG) laser. This may be the very last step in the manufacturing process. The BCA numbers for a specific DVD must then be entered into InterActual's BCA database. Information to track includes: DVD title, i.e. “Lost in Space”; BCA #/range, i.e. 12345687890; and Shipping Packaging/Tracking Container, i.e. Box 52221 to Hollywood Video. [0111]
  • After the BCA number is added to the DVDs, the DVDs are packaging/boxed for distribution to either the Distributor or the Retailer. It should be noted that many companies take multiple forms, so the replicator and distributor may be one in the same. Also, some retailers are large/important enough to get shipments directly from replicator. The way in which the DVDs are packaging/shipped is very important because one must track the BCA numbers to actual shipping containers (box, etc.). Therefore tracking information must also be added to the BCA database. [0112]
  • If packaged DVDs are then sent to distributor, the distributor also has mechanisms, i.e. scanners, input device, and monitoring devices, in place for tracking based on their distribution. For example, Deluxe may receive a “package” of 100,000 copies of “Lost in Space.” However, the distributor ships 10,000 to Retailer A and 5,000 to Retailer B. The distributor should be able to “input” retailer A and B's distribution information into the system. Ideally, this becomes a seamless/automated process. [0113]
  • Once the DVDs reach the retailer (either from the replicator or distributor), then DVDs may be further divided and distributed to local stores/outlets. In such a situation, the retailer should be able to automatically “track” distribution of these DVDs through to their stores. Over time, all three entitities (replicator, distributor, and retailer) are able to add tracking information to BCA database. Due to complexity and dependencies on existing business systems, the retail tracking concept will be rolled out in phases: replicator first most likely with key retail accounts. The distributors will be brought in. Retailers will then begin to embrace the ability to track based on local outlet/store. [0114]
  • By the foregoing design, easy deployment is thus afforded and minimal hardware is required to allow the synchronization of content without significant capital investments and with a very efficient control mechanism. The content delivery does not rely on high network bandwidth and is independent from the synchronization. [0115]
  • Internet Server Application Program Interface (ISAPI) extensions will be used on the server. ISAPI extensions provide a mechanism to maintain a temporary or permanent connection with the users. These connections allow the Synchronization Server to process request and to send the appropriate DVD commands. The permanent connections are known as “Keep Alive” connections. ISAPI extension can also be used as an HTTP interface to a more traditional server, with all data returned as text. [0116]
  • On the client side the approach is to use, but not limited to Java 1.1 applets, to initiate event start-up for the Synchronization server. The advantage of using Java 1.1 applets is to achieve platform independence for existing and future Java-enabled devices. JavaScript will be used to provide user interface navigation by “wrapping” the applet. [0117]
  • An ISAPI (Internet Server Application Program Interface) is a set of Windows program calls that let one write a Web server application that will run faster than a Common Gateway Interface (CGI) application. A disadvantage of a CGI application (or “executable file,” as it is sometimes called) is that each time it is run, it runs as a separate process with its own address space, resulting in extra instructions that have to be performed, especially if many instances of it are running on behalf of users. [0118]
  • Using ISAPI, you create a Dynamic Link Library (DLL) application file that can run as part of the Hypertext Transport Protocol (HTTP) application's process and address space. The DLL files are loaded into the computer when HTTP is started and remain there as long as they are needed; they don't have to be located and read into storage as frequently as a CGI application. [0119]
  • Existing CGI applications can be converted into ISAPI application DLLs without having to rewrite their logic. However, they do need to be written to be thread-safe so that a single instance of the DLL can serve multiple users. [0120]
  • A special kind of ISAPI DLL is called an ISAPI filter, which can be designated to receive control for every HTTP request. One can create an ISAPI filter for encryption or decryption, for logging, for request screening, or for other purposes. [0121]
  • One can write ISAPI server extension DLLs (ISAs) that can be loaded and called by the HTTP server. Users can fill out forms and click a submit button to send data to a Web server and invoke an ISA, which can process the information to provide custom content or store it in a database. Web server extensions can use information in a database to build Web pages dynamically, and then send them to the client computers to be displayed. An application can add other custom functionality and provide data to the client using HTTP and HTML. [0122]
  • One can write an ISAPI filter. The filter is also a DLL that runs on an ISAPI-enabled HTTP server. The filter registers for notification of events such as logging on or URL mapping. When the selected events occur, the filter is called, and one can monitor and change the data (on its way from the server to the client or vice versa). ISAPI filters can be used to provide custom encryption or compression schemes, or additional authentication methods. [0123]
  • Both server extensions and filters run in the process space of the Web server, providing an efficient way to extend the server's capabilities. [0124]
  • Overall Component Design
  • The various functional components of the software associated with the present invention will now be set forth. Such components include a Java/JavaScript Component, Synchronizer Component, LayerImpl Component, Business Layer Component, Configuration Manager Component, and DBConnect Component. [0125]
  • Java/JavaScript Component [0126]
  • FIG. 6 illustrates a flow diagram for providing information on a synchronized event on a plurality of client apparatuses in accordance with one embodiment of the present invention. First, in [0127] operation 600, a plurality of client apparatuses are connected via a network, as set forth earlier. Next, an application program is embedded on a site on the network in operation 602. Such application program may take the form of a JAVA applet, and the site may include a website on the Internet.
  • In use, information is requested from a server on the network utilizing the application program. See [0128] operation 604. Such information relates to an event to be played back simultaneously on the client apparatuses and may include general information such as a start and stop time of the event, or more specific information about the event itself.
  • In response to such request, a script is received for displaying the information. Note [0129] operation 606. The script may take any form such as Perl, REXX (on IBM mainframes), and Tcl/Tk, and preferably includes a JAVAscript.
  • In one embodiment of the present invention, the JAVA applet may be further adapted to send a request to retrieve command information from the server for use with a playback device of one of the client apparatuses. The commands may be adapted to playback the event on the playback device simultaneous with the playback of the event on the remaining client apparatuses. Further, the commands may include a start time when the playback of the event is to begin on each of the client apparatuses. [0130]
  • The JAVA applets and JAVAscript are used to communicate with the playback device of the client apparatuses. In one embodiment, the playback device includes a PCFriendly TM video player manufactured by Interactual®. [0131]
  • The Java applet is embedded within a web page and uses HTTP protocol to communicate to the synchronization server. The applet could request event information from the server, and display it to the user via JavaScript. The applet could also send a “BroadcastVideoEvent” request to retrieve DVD commands that can be passed to the video component, as set forth hereinabove. [0132]
  • Synchronizer Component [0133]
  • FIG. 7 illustrates a method for creating a synchronizer object in order to playback an event simultaneously on a plurality of client apparatuses. The synchronizer object is portion of the software that actually implements the synchronization procedure. First, in [0134] operation 700, a request is received utilizing a network for viewing an event. Next, the request is queued in memory in operation 702.
  • In response to the request, in [0135] operation 704, an object is created which is adapted to playback the event on a client apparatus simultaneous with the playback of the event on the remaining client apparatuses upon the receipt of an activation signal. As an option, the activation signal may be provided using a clock of the client apparatus, or located at a different location, i.e. server. To accomplish this, the object identifies a start time when the playback of the event is to begin on each of the client apparatuses.
  • In [0136] operation 706, the object is sent to one of the client apparatuses utilizing the network for being stored therein. In accordance with a primary aspect of the present invention, the object may be adapted to playback the event which is stored in memory of the client apparatus. This may be accomplished by activating a digital video disc (DVD) player.
  • In summary, when the Synchronizer component receives a “Broadcast VideoEvent” from the applet, it then places the request in the thread queue for processing. To process a request, the thread creates a “call back” object, if one does not exist for this event. The thread then adds the request to the “call back” object queue. This “call back” object will be invoked when it is time to play the DVD. The Synchronizer component creates a Call Back COM object, LayerSink. The Synchronizer component is also responsible for creating the LayerFactory interface which will be set forth hereinafter in greater detail. [0137]
  • LayerImpl Component [0138]
  • FIG. 8 illustrates a flowchart for affording a scheduler object adapted to facilitate the playback of an event simultaneously on a plurality of networked client apparatuses. The present method ensures that critical information is tracked during the synchronization of the event. Such critical information not only ensures proper synchronization, but also enables various peripheral features. [0139]
  • First, in [0140] operation 800, various values are determined including a current time, a start time when an event is to start, and a stop time when the event is to end. Thereafter, a length of the event is calculated based on the start time and the stop time in operation 802. As an option, the current time is determined by querying a clock of one of the client apparatuses.
  • If any portion of the length of the event takes place during a predetermined threshold period, a command is stored in memory in [0141] operation 804. The command may be adapted to automatically begin playing back the event at the start time. In one embodiment, the threshold period includes the time the users can be queued before the event. As an option, chapter information may be stored in the memory if any portion of the length of the event takes place during the predetermined threshold period. This allows the command to automatically begin playing back the event at a predetermined chapter.
  • In [0142] operation 806, a loop is created at the start time during which a lapsed time of the event is tracked. This information may be used for various tracking purposes to decide when to issue commands to the user. In another embodiment, a second loop may be created upon the beginning of a chapter during which information on a next chapter is retrieved.
  • The “call back” object (LayerSink) is thus responsible for creating and communicating with the LayerImpl component. The LayerImpl component acts as a scheduler, determining when to issue commands to the user. [0143]
  • LayerImpl will issue different DVD commands, based on the type of decoder the user has in their PC. LayerImpl will differentiate between the decoders by using the decoder information submitted from the client. The LayerImpl will pass the correct DVD command to the client, based on the decoder's capabilities. For example, if the decoder does not support the TimePlay event, then the server may send a ChapterPlay event and wait appropriately. [0144]
  • The following is an enumerated summary of the steps the component uses to determine when the users will receive the DVD commands: [0145]
  • 1. Retrieves the current time, and the time the event starts and ends. [0146]
  • 2. Calculates the length of the event. [0147]
  • 3. If the event is within a threshold period (i.e. the time users can be queued before the event), then store the first DVD command in memory. Also, store the Chapter information in memory. [0148]
  • 4. Create a loop that processes request until the event has completed. [0149]
  • 5. In the loop, calculate the lapsed time of the event. [0150]
  • 6. In the loop, retrieve the next chapter information. [0151]
  • 7. Create another loop that will loop until time for the next chapter to be played. [0152]
  • 8. When the next chapter is ready to play, send the command that was retrieved from the Chapter table. [0153]
  • Business Layer Component [0154]
  • FIG. 9 is a flowchart delineating a method for identifying a plurality of events which are played back simultaneously on a plurality of networked client apparatuses. This features is important since a host server may be synchronizing more than one event at once, or during overlapping times. Such events must therefore be distinguished. [0155]
  • First, in [0156] operation 900, a plurality of events are stored in memory on a plurality of client apparatuses. Each of the events is assigned a unique identifier which is stored in the memory.
  • In operation [0157] 902, the client apparatuses are adapted to be coupled to a host computer via a network, as set forth hereinabove. In operation 904, the identifier of the event which is stored in the memory of the client apparatuses is then retrieved utilizing the network. Such identifier is subsequently compared with an identifier of a scheduled event, as set forth in operation 906. If the comparison renders a match, the playback of the event is begun on the appropriate client apparatuses. Note operation 908.
  • CbusinessLayer thus differentiates events by the disk and location ids, uploaded by the client to guarantee backwards compatibility. As set forth earlier, late arrivals can always re-sync with the event. [0158]
  • Configuration Manager Component [0159]
  • FIG. 10 shows a flowchart delineating a technique for identifying playback devices of a plurality of client apparatuses which are networked to simultaneously playback an event. The present technique is important since the playback devices of the various client apparatuses may differ in make and model. Thus, different commands are required therefor. [0160]
  • In [0161] operation 1000, a type of the playback devices of the client apparatuses is first identified. Such “type” may refer to a make, model, or any other distinguishing characteristic of the particular playback devices. A command associated with the identified type of the playback device is then looked up in a look-up table. Note operation 1002. Such table may be located at the host server, or at any other location such as the client apparatuses.
  • Thereafter, in [0162] operation 1004, the command is sent to the corresponding client apparatus for beginning the playback of the event simultaneously with the playback of the event on each of the remaining client apparatuses.
  • This component is thus responsible for identifying what type of reference player is hosting the event. The reference player can be the database, which contains the DVD commands or a real time player. When the initial DVD is command is requested, the “Synchronizer” table is queried for the host type. From that point forward, the scheduler would know from whom to receive data. [0163]
  • DBConnect Component [0164]
  • This component is responsible for communicating with the Synchronizer tables, and for providing access methods for the retrieved data. All interaction from the tables is on a read-only basis. The LayerImpl component communicates with this component to retrieve DVD commands and event information. [0165]
  • Even though current implementation may be based on a Microsoft platform, hard dependencies on Microsoft or any other 3rd-party development tools may be avoided. To address such issues, the following considerations may be made throughout the code: [0166]
  • MFC specific code may be avoided. Instead, STL may be used. ATL and/or MFC code may be encapsulated into separate classes and portioned from the rest of the code. Class implementations may use aggregation pattern to delegate business logic to the portable classes. Database connection classes may be separated and the communication protocol may be separated with respect to portability to Oracle and other platforms. [0167]
  • FIGS. 11 and 12 illustrate the order of events among the various components of the present invention. In particular, FIG. 11 illustrates the manner in which a layer factory is created. As shown, an event is first checked in a database server after which a business layer is created in a WEB server in a manner set forth hereinabove. The foregoing components are then created. FIG. 12 illustrates the manner in which user requests are processed. As shown, communication is afforded with the video player on the client machine by means of JAVAscript and JAVA applets. The WEB server, in turn, communicates DVD commands to the video player via the JAVA applets, and also interfaces the database server via the various components thereof which were set forth hereinabove. [0168]
  • Alternate Embodiments [0169]
  • To support future enhancements, further components may be included with extendibility as the major objective. Various future enhancements of the product and how they will be addressed will now be set forth. [0170]
  • Hosted Real Time Players [0171]
  • While spirals may retrieve pre-recorded DVD commands from the database, alternate spirals may support a consumer as a host. The architecture may also support plug-in components. Alternate spirals may support the RealTimeConnector component, which accepts host user request and forwards them to the clients. The instant architecture supports the DBConnector which accepts events from the database. [0172]
  • Keep Alive Connections [0173]
  • Clients may maintain connections throughout the event. This allows the host to send a various number of commands to the client of the event. Although the spiral disconnects users once a PLAY command has been issued, the Synchronizer class (which will be set forth later) adds each connection to a Thread Pool. This pool of connections can be left open during the life of the event. [0174]
  • Logging Participants [0175]
  • Each request may be logged into the database to provide a reference for the future. [0176]
  • DVD Positioning [0177]
  • As an option, connections may be pooled to allow the synchronization server to direct consumer's machines to the certain locations throughout the entire event. [0178]
  • Synchronization events in alternate spirals may be defined as a combination of play from location event and the actual event. This way, one describes each event in the unambiguous way on the client side and synchronizes it with the server. For example, a situation may be considered where one fast forwards after a movie is played for 15 min and thereafter plays the scene in the movie. In such situation, one has to submit the information to the client player, indicating that it (player) has to start time play from 15 min into the movie and fast-forward to the certain location. A better way would be to analyze what is the next event after fast forwarding occurred and perform a combination for the play from location and next event. This design would require significant changes to the client infrastructure, including video object, remoteagent and provider and should be taken into consideration in any alternate client design. [0179]
  • Classes/Component Diagrams
  • FIGS. 13-16 illustrate various class/component diagrams. In particular, FIGS. 13-16 illustrate a Synchronizer Class Diagram [0180] 1300, Layerlmpl Class Diagram 1400, Business Layer Class Diagram 1500, and DBConnect Class Diagram 1600, respectively.
  • Sequence Diagrams [0181]
  • FIG. 17 illustrates a logical sequence diagram [0182] 1700. As shown, when the server receives a user request, it analyzes the authentication information of the request (date/time, disc id, user id, and BCA number) and the appropriate synchronization event stored in the database. The database contains an event start threshold value measured in milliseconds. This threshold defines the amount of time prior to an event that a consumer is eligible to “connect” for the start of the event.
  • If the date/time of the user request lies within the event start threshold, the user is put into wait queue and receive the appropriate data when the time elapses. Note [0183] steps 1,2,3,5,6,7 of the Logical Sequence diagram. Otherwise, a message is sent informing the user when the event will occur. Note step 4 of the Logical Sequence diagram.
  • Server side collaboration diagram [0184]
  • FIG. 18 illustrates a logical sequence diagram [0185] 1800 that shows server side collaboration. As shown, server ISAPI extension receives a BroadcastVideoEvents request. It calls IA_BusinessServer via BeginProcess, to retrieve configuration information. Configuration information contains a playback connector. Playback connector identifies whether the server will have to communicate with a reference player or will it perform playback from the database.
  • At [0186] step 6, ISAPI extension will call IA_BusinessServer CompareTime method and based on the results will send to the user a predefined web page indicating to retry later or return control to the web server, notifying it (web server) to keep the connection open. At this point connection is pooled and will be processed by the IA_BusinessServer at a time of the event.
  • Client Collaboration Diagram [0187]
  • FIG. 19 illustrates a logical sequence diagram [0188] 1900 showing client side collaboration in accordance with one embodiment of the present invention.
  • Classes/Interfaces Definition
  • Definitions of one embodiment of the various classes associated with the software which implements the present invention will now be set forth. [0189]
  • Class Applet[0190] 1
  • Purpose: [0191]
  • This is the class that implements the applet. The browser will use it to bootstrap our applet. [0192]
  • Responsibilities: [0193]
  • Request a BroadCastVideo event and to gather event status information. [0194]
  • Collaborations: [0195]
  • BroadCastEvent, CITIEncrypt [0196]
  • Base Class and Implemented Interfaces: [0197]
  • Javax.Applet [0198]
  • Public Interface: [0199]
  • getchapter Returns the current chapter the reference player is playing. [0200]
  • Return type: String [0201]
  • Parameters: void [0202]
  • Pre-conditions: None. [0203]
  • Post-conditions: None. [0204]
  • getTitleInfo Returns the current title the reference player is playing [0205]
  • Return type: String [0206]
  • Parameters: void [0207]
  • Pre-conditions: None. [0208]
  • Post-conditions: None. [0209]
  • getStartTime Returns the time the event is scheduled to start [0210]
  • <SS:MM:HH:DD:MM:YYYY>[0211]
  • Return type: String [0212]
  • Parameters: void [0213]
  • Pre-conditions: None. [0214]
  • Post-conditions: None. [0215]
  • getStartTimeSec Returns the time the event starts in seconds. [0216]
  • Return type: String [0217]
  • Parameters: void [0218]
  • Pre-conditions: None. [0219]
  • Post-conditions: None. [0220]
  • getStartTimeMinReturns the time the event starts in minutes. [0221]
  • Return type: String [0222]
  • Parameters: void [0223]
  • Pre-conditions: None. [0224]
  • Post-conditions: None. [0225]
  • getStartTimeHrReturns the time the event starts in Hours. [0226]
  • Return type: String [0227]
  • Parameters: void [0228]
  • Pre-conditions: None. [0229]
  • Post-conditions: None. [0230]
  • GetStartTimeDay Returns the time the event starts in days. [0231]
  • Return type: String [0232]
  • Parameters: void [0233]
  • Pre-conditions: None. [0234]
  • Post-conditions: None. [0235]
  • GetStartTimeMnth Returns the time the event starts in months. [0236]
  • Return type: String [0237]
  • Parameters: void [0238]
  • Pre-conditions: None. [0239]
  • Post-conditions: None. [0240]
  • GetStartTimeYr Returns the time the event starts in year. [0241]
  • Return type: String [0242]
  • Parameters: void [0243]
  • Pre-conditions: None. [0244]
  • Post-conditions: None. [0245]
  • GetLenOfEvent Returns the length of the event. [0246]
  • Return type: String [0247]
  • Parameters: void [0248]
  • Pre-conditions: None. [0249]
  • Post-conditions: None. [0250]
  • GetExpiredTime: Returns lapse time of the event. [0251]
  • Return type: String [0252]
  • Parameters: void [0253]
  • Pre-conditions: None. [0254]
  • Post-conditions: None. [0255]
  • getServerTime: Returns the servers current time <SS:MM:HH:DD:MM:YYYY>. [0256]
  • Return type: String [0257]
  • Parameters: void [0258]
  • Pre-conditions: None. [0259]
  • Post-conditions: None. [0260]
  • getServerTimeSec: Returns the servers current in seconds. [0261]
  • Return type: String [0262]
  • Parameters: void [0263]
  • Pre-conditions: None. [0264]
  • Post-conditions: None. [0265]
  • getServerTimeMin: Returns the servers current in minutes. [0266]
  • Return type: String [0267]
  • Parameters: void [0268]
  • Pre-conditions: None. [0269]
  • Post-conditions: None. [0270]
  • getServerTimeHr: Returns the servers current in hours. [0271]
  • Return type: String [0272]
  • Parameters: void [0273]
  • Pre-conditions: None. [0274]
  • Post-conditions: None. [0275]
  • getServerTimeDay: Returns the servers current in day. [0276]
  • Return type: String [0277]
  • Parameters: void [0278]
  • Pre-conditions: None. [0279]
  • Post-conditions: None. [0280]
  • getServerTimeMnth: Returns the servers current in month. [0281]
  • Return type: String [0282]
  • Parameters: void [0283]
  • Pre-conditions: None. [0284]
  • Post-conditions: None. [0285]
  • getServerTimeYr: Returns the servers current in year. [0286]
  • Return type: String [0287]
  • Parameters: void [0288]
  • Pre-conditions: None. [0289]
  • Post-conditions: None. [0290]
  • startProc: Calls the ISAPIs “ServerInfo” method. [0291]
  • Return type: void [0292]
  • Parameters: String disk id, String location id [0293]
  • Pre-conditions: None. [0294]
  • Post-conditions: None. [0295]
  • msgEvent: Calls BroadCastEvent applet. [0296]
  • Return type: void [0297]
  • Parameters: void [0298]
  • Pre-conditions: None. [0299]
  • Post-conditions: None. [0300]
  • Class BroadCastEvent [0301]
  • Purpose: [0302]
  • This is the class that invokes the Synchronizer. [0303]
  • Responsibilities: [0304]
  • Sets the JavaScript with the command returned from the server. [0305]
  • Collaborations: [0306]
  • CITIEncrypt [0307]
  • Base Class and Implemented Interfaces: [0308]
  • Java.Thread [0309]
  • Class CDBConnect [0310]
  • Purpose: [0311]
  • This is the class provides a public interface for components to request information from the DB tables. [0312]
  • Responsibilities: [0313]
  • Opens the database and Synchronizer, Chapter_Disk tables. [0314]
  • Queries the Synchronizer by the specified disk id and location id. [0315]
  • Queries the Chapter_Disk by disk id. [0316]
  • Provides the next chapter that is scheduled to play. [0317]
  • Queries the Decoder_Capabilities table to determine if the requested player is time or chapter play. [0318]
  • Collaborations: [0319]
  • DBSyncSet [0320]
  • DBReferenceSet [0321]
  • CDBChapterSet [0322]
  • CDecoderCapabilities [0323]
  • Base class and implemented interfaces: [0324]
  • Public Interface: [0325]
  • Get_NextChapter: Returns the next chapter to play. [0326]
  • Return type: String [0327]
  • Parameters: long time, long title, BSTR Chapter [0328]
  • Pre-conditions: None. [0329]
  • Post-conditions: None. [0330]
  • chkEvent: Checks if an event is scheduled for the disk and location id. [0331]
  • Return type: String [0332]
  • Parameters: long time, long title, BSTR Chapter [0333]
  • Pre-conditions: None. [0334]
  • Post-conditions: None. [0335]
  • get_initialDVDCommand: Returns the first DVD command to play. [0336]
  • Return type: String [0337]
  • Parameters: BSTR & [0338]
  • Pre-conditions: None. [0339]
  • Post-conditions: None. [0340]
  • get_nextDVDCommand: Returns the next DVD command to play. [0341]
  • Return type: String [0342]
  • Parameters: BSTR & [0343]
  • Pre-conditions: None. [0344]
  • Post-conditions: None. [0345]
  • decoderArray: Returns an array of decoder types. [0346]
  • Return type: String [0347]
  • Parameters: long**, long** [0348]
  • Pre-conditions: None. [0349]
  • Post-conditions: None. [0350]
  • Class CCConfigMgrImpl [0351]
  • Purpose: [0352]
  • This is the class provides a public interface for components to determine the type of reference player hosting the event. [0353]
  • Responsibilities: [0354]
  • Opens the database and Synchronizer, Chapter_Disk tables. [0355]
  • Queries the Synchronizer by the specified disk id and location id. [0356]
  • Stores the reference player type. [0357]
  • Collaborations: [0358]
  • CConfigMgrRecSet [0359]
  • Base Class and Implemented Interfaces: [0360]
  • Public Interface: [0361]
  • get_hostType: Returns the reference player host type. [0362]
  • Return type: String [0363]
  • Parameters: short [0364]
  • Pre-conditions: None. [0365]
  • Post-conditions: None. [0366]
  • Class threadFunctor [0367]
  • Purpose: [0368]
  • This class provides a threading model that classes can use to derive. [0369]
  • Responsibilities: [0370]
  • Calls the CreateEvent function, which opens a named or unnamed event objec. [0371]
  • Calls_beginthread, which creates a thread begins execution of a routine at [0372]
  • start_address. The routine at start_address must use the _cdecl calling convention and should have no return value. When the thread returns from that routine, it is terminated automatically. [0373]
  • Calls the WaitForSingleObject function, which checks the current state of the specified object. If the object's state is nonsignaled, the calling thread enters an efficient wait state. [0374]
  • Calls the ResetEvent function, which sets the state of the specified event object to nonsignaled. [0375]
  • The state of an event object remains nonsignaled until it is explicitly set to signaled by the SetEvent or PulseEvent function. [0376]
  • Collaborations: [0377]
  • CConfigMgrRecSet [0378]
  • Base Class and Implemented Interfaces: [0379]
  • Public Interface: [0380]
  • start: Starts the thread. [0381]
  • Return type: void [0382]
  • Parameters: void [0383]
  • Pre-conditions: None. [0384]
  • Post-conditions: None. [0385]
  • stop: Stops the thread. Calls CloseHandle for the thread and event. [0386]
  • Return type: void [0387]
  • Parameters: void [0388]
  • Pre-conditions: None. [0389]
  • Post-conditions: None. [0390]
  • Class Isapithread [0391]
  • Purpose: [0392]
  • This creates an ISAPI thread. [0393]
  • Responsibilities: [0394]
  • Adds a request to a vector. [0395]
  • Creates the sink object. [0396]
  • Stores the request into sink object. [0397]
  • Sends the time information to JavaScript. [0398]
  • Collaborations: [0399]
  • LayerSink [0400]
  • factorySink [0401]
  • Base Class and Implemented Interfaces: [0402]
  • threadFunctor [0403]
  • Public Interface: [0404]
  • addrequest: Adds the request to its vector. [0405]
  • Return type: void [0406]
  • Parameters: void [0407]
  • Pre-conditions: None. [0408]
  • Post-conditions: None. [0409]
  • getBLayerInfo: Responsible for getting information about the event. [0410]
  • Return type: void [0411]
  • Parameters: std:string&,std::string&, ChttpServerContext* [0412]
  • Pre-conditions: None. [0413]
  • Post-conditions: None. [0414]
  • Class factorySink [0415]
  • Purpose: [0416]
  • Manages the layerSink and businessLayerProp objects. [0417]
  • Responsibilities: [0418]
  • Stores a layerSink object. [0419]
  • Returns the “businesssLayerProp” <Business Layer Properties>[0420]
  • Creates the “businessLayerProp” <Business Layer structure>[0421]
  • Collaborations: [0422]
  • LayerSink [0423]
  • businessLayerProp [0424]
  • Base Class and Implemented Interfaces: [0425]
  • Public Interface: [0426]
  • construct: Stores a layerSink object. [0427]
  • Return type: void [0428]
  • Parameters: void [0429]
  • Pre-conditions: None. [0430]
  • Post-conditions: None. [0431]
  • notifyCreateLayer: Responsible for creating a “businessLayerProp”. [0432]
  • Return type: void [0433]
  • Parameters: BSTR, BSTR, DATE, DATE, LONG [0434]
  • Pre-conditions: None. [0435]
  • Post-conditions: None. [0436]
  • Class layerSink [0437]
  • Purpose: [0438]
  • layerSink represents a sink interface and stores a queue of requests. It creates a connection point object. [0439]
  • This call back object, allows asynchronously processing. [0440]
  • Responsibilities: [0441]
  • Acts as the client sink object. [0442]
  • Sends the results to the user [0443]
  • Creates the “BusinessLayer” and makes it a connection point object. [0444]
  • Closes the users connection. [0445]
  • Creates a Factory interface by calling “createFactory”. [0446]
  • Creates a connection point for the factory. [0447]
  • Stores the LayerSink in the FactorySink object. [0448]
  • Creates a connection point (call back) by calling AtlAdvise, between the connection point container and the client sink object. This allows the client to receive events. [0449]
  • Calls the connectable objects “getServerLayer”. This method fires an event to the clients sink object. [0450]
  • Create a business layer, [0451]
  • Store the request in its vector. [0452]
  • Release the Sink Object (client) [0453]
  • Calls AtlUnadvise to terminates the ability of the client to receive events. [0454]
  • Collaborations: [0455]
  • Base Class and Implemented Interfaces: [0456]
  • Public Interface: [0457]
  • construct: Creates a connection point. [0458]
  • Return type: void [0459]
  • Parameters: void [0460]
  • Pre-conditions: None. [0461]
  • Post-conditions: None. [0462]
  • addRequest: Adds the request to its vector. [0463]
  • Return type: void [0464]
  • Parameters: BSTR, BSTR, DATE, DATE, LONG [0465]
  • Pre-conditions: None. [0466]
  • Post-conditions: None. [0467]
  • createBusinessLayer: Creates a business layer. Create the connection point. [0468]
  • Return type: void [0469]
  • Parameters: businessLayerProp & [0470]
  • Pre-conditions: None. [0471]
  • Post-conditions: None. [0472]
  • updatetime: This call back function translates the time and sends the command to [0473]
  • the user. [0474]
  • Return type: void [0475]
  • Parameters: long,long [0476]
  • Pre-conditions: None. [0477]
  • Post-conditions: None. [0478]
  • Class CBusinessLayer [0479]
  • Purpose: [0480]
  • Creates a layerthread object. This object is responsible for providing access methods, which provide event information. [0481]
  • Responsibilities: [0482]
  • The “Synchronizers” createBusinessLayer method creates a class object from the “IBusinessLayer” interface. <The class object is part of the LayerImpl project>[0483]
  • The BusinesLayers class object <m_ilayer>calls its “Initialize” method. <Note: m_ilayer is the connection point object. It identifies the “Sink Interface”. [0484]
  • It then calls the “Initialize” method of the connection point. [0485]
  • The “Initialize” method then calls the “ChkValidEvent” method, which then creates a layerthread object. [0486]
  • Collaborations: [0487]
  • CBusinessLayer [0488]
  • layerthread [0489]
  • Base Class and Implemented Interfaces: [0490]
  • Public Interface: [0491]
  • Initialize: Calls the “ChkValidEvent” method which kicks of a layer thread. [0492]
  • Return type: void [0493]
  • Parameters: void [0494]
  • Pre-conditions: None. [0495]
  • Post-conditions: None. [0496]
  • Class layerthread [0497]
  • Purpose: [0498]
  • This object acts as a scheduler, processing request from its queue. [0499]
  • Responsibilities: [0500]
  • Send DVD commands to the user. [0501]
  • “Syncs” up late corners to the events. [0502]
  • Collaborations: [0503]
  • CBusinessLayer [0504]
  • CDBConnect [0505]
  • Base Class and Implemented Interfaces: [0506]
  • Public Interface: [0507]
  • startThread: Processes requests from the queue [0508]
  • Return type: void [0509]
  • Parameters: void [0510]
  • Pre-conditions: None. [0511]
  • Post-conditions: None. [0512]
  • Class CLayerFactory [0513]
  • Purpose: [0514]
  • This object manages businesslayer objects. Business layer objects communicate with the reference player and notify the user which DVD command to play. [0515]
  • Responsibilities: [0516]
  • Send DVD commands to the user. [0517]
  • “Syncs” up late corners to the events. [0518]
  • This object Implements the IID_LayerFactory interface. [0519]
  • This COM object is the servers Connectable Point object. [0520]
  • This server object supports connections to sink interfaces. These sink interfaces reside on the client side and are equivalent to the “call back” functions in Windows. [0521]
  • Collaborations: [0522]
  • CBusinessLayer [0523]
  • CDBConnect [0524]
  • Base Class and Implemented Interfaces: [0525]
  • Public Interface: [0526]
  • getServerLayer: “Fires” an event to create a business layer with the properties [0527]
  • retrieved from the pipe object. [0528]
  • Return type: void [0529]
  • Parameters: void [0530]
  • Pre-conditions: None. [0531]
  • Post-conditions: None. [0532]
  • put_set_layer: call the “CLayerFactoryImpl” add( ) method. Supplying the “businesslayer” object. [0533]
  • This will added to shared memory queue and written to a file. [0534]
  • Return type: void [0535]
  • Parameters: void [0536]
  • Pre-conditions: None. [0537]
  • Post-conditions: None. [0538]
  • FinalConstruct: Calls the “CLayerFactoryImpl” FinalConstruct COM class object. [0539]
  • Return type: void [0540]
  • Parameters: void [0541]
  • Pre-conditions: None. [0542]
  • Post-conditions: None. [0543]
  • Although only a few embodiments of the present invention have been described in detail herein, it should be understood that the present invention may be embodied in many other specific forms without departing from the spirit or scope of the invention. Therefore, the present examples and embodiments are to be considered as illustrative and not restrictive, and the invention is not to be limited to the details given herein, but may be modified within the scope of the appended claims. [0544]

Claims (48)

What is claimed is:
1. A method for delayed synchronization of an event on a plurality of client apparatuses, comprising the steps of:
connecting a plurality of client apparatuses via a network;
providing an event stored in a memory storage device on each of the plurality of client apparatuses;
transmitting information from a host apparatus to the plurality of client apparatuses to start a synchronized event, wherein the synchronized event includes playback of the event on each of the plurality of client apparatuses;
receiving a request from an additional client apparatus during the synchronized event; and
transmitting additional information from the host apparatus to the additional client apparatus to allow the additional client apparatus to join the synchronized event;
wherein only the host apparatus can transmit the additional information to allow the additional client apparatus to join the synchronized event.
2. A method as recited in claim 1, wherein said information includes a history of simultaneous playback.
3. A method of claim 1, wherein said client apparatus is a computer.
4. A method as recited in claim 1, wherein said request is received utilizing said network.
5. A method as recited in claim 1, wherein said synchronized event includes at least one of a movie, a concert, and a theatrical event.
6. A method as recited in claim 1, wherein said memory storage device includes a DVD.
7. A method as recited in claim 1, wherein said information includes chapter information associated with said memory storage device.
8. A method as recited in claim 1, wherein said information includes title information associated with said memory storage device.
9. A method as recited in claim 1, wherein said information includes start time information associated with said memory storage device.
10. A method as recited in claim 1, wherein said information includes stop time information associated with said memory storage device.
11. A method as recited in claim 1, wherein said information includes DVD command information associated with said memory storage device.
12. A method as recited in claim 1, wherein said information includes client apparatus capability information associated with said memory storage device.
13. A method as recited in claim 1, wherein said information includes user information associated with said memory storage device.
14. A method as recited in claim 1, wherein said network is a wide area network.
15. A method for synchronizing an event, comprising the steps of:
providing an event stored in a first memory storage device on a first client apparatus;
providing the event stored in a second memory storage device on a second client apparatus;
connecting the first client apparatus and the second client apparatus to a host apparatus utilizing a computer network; and
transmitting information from the host apparatus to the first client apparatus and the second client apparatus utilizing the network for allowing the simultaneous playback of the event on each of the first client apparatus and the second client apparatus;
wherein only the host apparatus can transmit the information to the first client apparatus and the second client apparatus for allowing the simultaneous playback of the event on each of the first client apparatus and the second client apparatus.
16. A method as recited in claim 15, wherein said information includes a history of the simultaneous playback.
17. A method of claim 15, wherein said client apparatus is a computer.
18. A method as recited in claim 15, wherein said event includes at least one of a movie, a concert, and a theatrical event.
19. A method as recited in claim 15, wherein said memory storage device includes a DVD.
20. A method as recited in claim 15, wherein said information includes chapter information associated with said memory storage device.
21. A method as recited in claim 15, wherein said information includes title information associated with said memory storage device.
22. A method as recited in claim 15, wherein said information includes start time information associated with said memory storage device
23. A method as recited in claim 15, wherein said information includes stop time information associated with said memory storage device
24. A method as recited in claim 15, wherein said information includes DVD command information associated with said memory storage device.
25. A method as recited in claim 15, wherein said information includes client apparatus capability information associated with said memory storage device.
26. A method as recited in claim 15, wherein said information includes user information associated with said memory storage device.
27. A method as recited in claim 9, wherein said network is a wide area network.
28. A method for delayed synchronization of an event on a plurality of client apparatuses, comprising the steps of:
connecting a plurality of client apparatuses via a network;
providing an event stored in a memory storage device on each of the plurality of client apparatuses;
transmitting information from a host apparatus to the plurality of client apparatuses to start a synchronized event, wherein the synchronized event includes playback of the event on each of the plurality of client apparatuses;
receiving a request from an additional client apparatus during the synchronized event; and
transmitting information from the host apparatus to the additional client apparatus to allow the additional client apparatus to join the synchronized event;
wherein the information to allow the additional client apparatus to join the synchronized event also includes a history of the synchronized event.
29. A method of claim 28, wherein said client apparatuses are computers.
30. A method as recited in claim 28, wherein said request is received utilizing said network.
31. A method as recited in claim 28, wherein said synchronized event includes at least one of a movie, a concert, and a theatrical event.
32. A method as recited in claim 28, wherein said memory storage device includes a DVD.
33. A method as recited in claim 28, wherein said information includes chapter information associated with said memory storage device.
34. A method as recited in claim 28, wherein said information includes title information associated with said memory storage device.
35. A method as recited in claim 28, wherein said information includes start time information associated with said memory storage device
36. A method as recited in claim 28, wherein said information includes stop time information associated with said memory storage device
37. A method as recited in claim 28, wherein said information includes DVD command information associated with said memory storage device.
38. A method as recited in claim 28, wherein said information includes client apparatus capability information associated with said memory storage device.
39. A method as recited in claim 28, wherein said information includes user information associated with said memory storage device.
40. A method as recited in claim 28, wherein said network is a wide area network.
41. A method for synchronizing an event, comprising the steps of:
connecting a first client apparatus to host apparatus utilizing a computer network, wherein the first client apparatus accesses an event stored in a first memory storage device;
connecting a second client apparatus to the host apparatus utilizing the computer network, wherein the second client apparatus accesses the event stored in a second memory storage device; and
transmitting information from the host apparatus to the first client apparatus and the second client apparatus utilizing the network for allowing the simultaneous playback of the event on each of the first client apparatus and the second client apparatus;
wherein only the host apparatus can transmit the information to the first client apparatus and the second client apparatus for allowing the simultaneous playback of the event on each of the first client apparatus and the second client apparatus.
42. A method as recited in claim 41, wherein said information includes a history of simultaneous playback.
43. A method of claim 41, wherein said client apparatus is a computer.
44. A method as recited in claim 41, wherein said request is received utilizing said network.
45. A method as recited in claim 41, wherein said synchronized event includes at least one of a movie, a concert, and a theatrical event.
46. A method as recited in claim 41, wherein said memory storage device includes a DVD.
47. A method as recited in claim 41, wherein said information includes chapter information associated with said memory storage device.
48. A method as recited in claim 41, wherein said network is a wide area network.
US10/880,272 2000-01-20 2004-06-28 System, method and article of manufacture for late synchronization during the execution of a multimedia event on a plurality of client computers Abandoned US20040244041A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US10/880,272 US20040244041A1 (en) 2000-01-20 2004-06-28 System, method and article of manufacture for late synchronization during the execution of a multimedia event on a plurality of client computers

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US09/488,613 US6769130B1 (en) 2000-01-20 2000-01-20 System, method and article of manufacture for late synchronization during the execution of a multimedia event on a plurality of client computers
US10/880,272 US20040244041A1 (en) 2000-01-20 2004-06-28 System, method and article of manufacture for late synchronization during the execution of a multimedia event on a plurality of client computers

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US09/488,613 Continuation US6769130B1 (en) 1999-04-21 2000-01-20 System, method and article of manufacture for late synchronization during the execution of a multimedia event on a plurality of client computers

Publications (1)

Publication Number Publication Date
US20040244041A1 true US20040244041A1 (en) 2004-12-02

Family

ID=32713728

Family Applications (2)

Application Number Title Priority Date Filing Date
US09/488,613 Expired - Lifetime US6769130B1 (en) 1999-04-21 2000-01-20 System, method and article of manufacture for late synchronization during the execution of a multimedia event on a plurality of client computers
US10/880,272 Abandoned US20040244041A1 (en) 2000-01-20 2004-06-28 System, method and article of manufacture for late synchronization during the execution of a multimedia event on a plurality of client computers

Family Applications Before (1)

Application Number Title Priority Date Filing Date
US09/488,613 Expired - Lifetime US6769130B1 (en) 1999-04-21 2000-01-20 System, method and article of manufacture for late synchronization during the execution of a multimedia event on a plurality of client computers

Country Status (1)

Country Link
US (2) US6769130B1 (en)

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050060754A1 (en) * 2003-09-17 2005-03-17 Wegener Communications, Inc. Apparatus and method for distributed control of media dissemination
US20070198111A1 (en) * 2006-02-03 2007-08-23 Sonic Solutions Adaptive intervals in navigating content and/or media
US20090034939A1 (en) * 2004-01-09 2009-02-05 Tomoyuki Okada Recording medium, reproduction device, program, reproduction method
US7689510B2 (en) 2000-09-07 2010-03-30 Sonic Solutions Methods and system for use in network management of content
US7711795B2 (en) 2000-01-20 2010-05-04 Sonic Solutions System, method and article of manufacture for remote control and navigation of local content
US20100151783A1 (en) * 2008-12-12 2010-06-17 At&T Intellectual Property I, L.P. Systems and Methods for Synchronized Playout of Music on Several Personal Digital Music Players
US7779097B2 (en) 2000-09-07 2010-08-17 Sonic Solutions Methods and systems for use in network management of content

Families Citing this family (41)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7346920B2 (en) * 2000-07-07 2008-03-18 Sonic Solutions, A California Corporation System, method and article of manufacture for a common cross platform framework for development of DVD-Video content integrated with ROM content
US8874244B2 (en) * 1999-05-19 2014-10-28 Digimarc Corporation Methods and systems employing digital content
US7840639B1 (en) 1999-09-21 2010-11-23 G&H Nevada-Tek Method and article of manufacture for an automatically executed application program associated with an electronic message
US9092535B1 (en) 1999-09-21 2015-07-28 Google Inc. E-mail embedded textual hyperlink object
US6360221B1 (en) 1999-09-21 2002-03-19 Neostar, Inc. Method and apparatus for the production, delivery, and receipt of enhanced e-mail
US7908635B2 (en) * 2000-03-02 2011-03-15 Tivo Inc. System and method for internet access to a personal television service
US8620520B2 (en) * 2000-05-09 2013-12-31 Robert Bosch Gmbh Method for controlling devices, and a device in a communications network in a motor vehicle
WO2001093141A1 (en) * 2000-06-01 2001-12-06 Fujitsu Limited System for managing right of using and recorded medium
FI20001570A (en) * 2000-06-30 2001-12-31 Nokia Corp Synchronized provision of services over a telecommunications network
US20030229893A1 (en) * 2001-04-26 2003-12-11 Vito Sgaraglino Multiple response means for interactive advertising and information systems
US7305691B2 (en) * 2001-05-07 2007-12-04 Actv, Inc. System and method for providing targeted programming outside of the home
US20020178060A1 (en) * 2001-05-25 2002-11-28 Sheehan Patrick M. System and method for providing and redeeming electronic paperless coupons
US20040100507A1 (en) * 2001-08-24 2004-05-27 Omri Hayner System and method for capturing browser sessions and user actions
US7574474B2 (en) * 2001-09-14 2009-08-11 Xerox Corporation System and method for sharing and controlling multiple audio and video streams
US7096203B2 (en) * 2001-12-14 2006-08-22 Duet General Partnership Method and apparatus for dynamic renewability of content
US20040010792A1 (en) * 2002-07-12 2004-01-15 Wallace Michael W. Method and system for providing flexible time-based control of application appearance and behavior
US20040081434A1 (en) * 2002-10-15 2004-04-29 Samsung Electronics Co., Ltd. Information storage medium containing subtitle data for multiple languages using text data and downloadable fonts and apparatus therefor
US7580867B2 (en) 2004-05-04 2009-08-25 Paul Nykamp Methods for interactively displaying product information and for collaborative product design
US20060053285A1 (en) * 2004-07-29 2006-03-09 Kimmel Gerald D Object access level
US7882530B2 (en) * 2004-11-23 2011-02-01 Palo Alto Research Center Incorporated Method, apparatus, and program products for socially synchronizing an experiential data stream
US7873983B2 (en) * 2004-11-23 2011-01-18 Palo Alto Research Center Incorporated Method and apparatus for controlling an experiential data stream in a social space
US7669219B2 (en) * 2005-04-15 2010-02-23 Microsoft Corporation Synchronized media experience
US8022989B2 (en) * 2005-08-17 2011-09-20 Palo Alto Research Center Incorporated Method and apparatus for controlling data delivery with user-maintained modes
AU2006325473A1 (en) * 2005-10-06 2007-06-21 Vergence Entertainment Llc, A California Limited Liability Company Substantially simultaneous alerts and use thereof in intermittent contests
CA2636819A1 (en) * 2006-01-13 2007-07-19 Diginiche Inc. System and method for collaborative information display and markup
US20080005353A1 (en) * 2006-06-28 2008-01-03 Microsoft Corporation Enabling a plurality of devices to control each other
US7966309B2 (en) 2007-01-17 2011-06-21 Google Inc. Providing relevance-ordered categories of information
US8966407B2 (en) 2007-01-17 2015-02-24 Google Inc. Expandable homepage modules
US8005822B2 (en) 2007-01-17 2011-08-23 Google Inc. Location in search queries
US8326858B2 (en) * 2007-01-17 2012-12-04 Google Inc. Synchronization of fixed and mobile data
US7966321B2 (en) * 2007-01-17 2011-06-21 Google Inc. Presentation of local results
US9098868B1 (en) 2007-03-20 2015-08-04 Qurio Holdings, Inc. Coordinating advertisements at multiple playback devices
US7984068B2 (en) 2007-05-25 2011-07-19 Google Inc. Providing profile information to partner content providers
WO2008157628A1 (en) * 2007-06-18 2008-12-24 Synergy Sports Technology, Llc System and method for distributed and parallel video editing, tagging, and indexing
US7805373B1 (en) * 2007-07-31 2010-09-28 Qurio Holdings, Inc. Synchronizing multiple playback device timing utilizing DRM encoding
US8060904B1 (en) 2008-02-25 2011-11-15 Qurio Holdings, Inc. Dynamic load based ad insertion
US20090249222A1 (en) * 2008-03-25 2009-10-01 Square Products Corporation System and method for simultaneous media presentation
US8825462B2 (en) 2008-09-17 2014-09-02 Accenture Global Services Limited Method and system for simulating a plurality of devices
US8893035B2 (en) * 2008-09-17 2014-11-18 Accenture Global Services Limited Method, system and graphical user interface for configuring a simulator to simulate a plurality of devices
CA2684678A1 (en) * 2009-11-03 2011-05-03 Research In Motion Limited System and method for dynamic post-processing on a mobile device
EP2684119A4 (en) 2011-03-08 2014-10-22 Tivo Inc Multi source and destination media discovery and management platform

Citations (99)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4672572A (en) * 1984-05-21 1987-06-09 Gould Inc. Protector system for computer access and use
US4709813A (en) * 1986-04-10 1987-12-01 Minnesota Mining And Manufacturing Company Anti-theft device for compact discs
US4710754A (en) * 1986-09-19 1987-12-01 Minnesota Mining And Manufacturing Company Magnetic marker having switching section for use in electronic article surveillance systems
US4739510A (en) * 1985-05-01 1988-04-19 General Instrument Corp. Direct broadcast satellite signal transmission system
US4785472A (en) * 1987-05-11 1988-11-15 The Trustees Of The Stevens Institute Of Technology Remote teaching system
US4888638A (en) * 1988-10-11 1989-12-19 A. C. Nielsen Company System for substituting television programs transmitted via telephone lines
US4967185A (en) * 1989-08-08 1990-10-30 Minnesota Mining And Manufacturing Company Multi-directionally responsive, dual-status, magnetic article surveillance marker having continuous keeper
US4993068A (en) * 1989-11-27 1991-02-12 Motorola, Inc. Unforgeable personal identification system
US5023907A (en) * 1988-09-30 1991-06-11 Apollo Computer, Inc. Network license server
US5109482A (en) * 1989-01-11 1992-04-28 David Bohrman Interactive video control system for displaying user-selectable clips
US5128752A (en) * 1986-03-10 1992-07-07 Kohorn H Von System and method for generating and redeeming tokens
US5274758A (en) * 1989-06-16 1993-12-28 International Business Machines Computer-based, audio/visual creation and presentation system and method
US5289439A (en) * 1992-05-27 1994-02-22 Vimak Corporation CD transport apparatus
US5305197A (en) * 1992-10-30 1994-04-19 Ie&E Industries, Inc. Coupon dispensing machine with feedback
US5305195A (en) * 1992-03-25 1994-04-19 Gerald Singer Interactive advertising system for on-line terminals
US5347508A (en) * 1992-04-22 1994-09-13 Minnesota Mining And Manufacturing Company Optical information storage disk for use with electronic article surveillance systems
US5353218A (en) * 1992-09-17 1994-10-04 Ad Response Micromarketing Corporation Focused coupon system
US5400402A (en) * 1993-06-07 1995-03-21 Garfinkle; Norton System for limiting use of down-loaded video-on-demand data
US5410343A (en) * 1991-09-27 1995-04-25 Bell Atlantic Network Services, Inc. Video-on-demand services using public switched telephone network
US5413383A (en) * 1993-09-08 1995-05-09 The Standard Register Company Multipurpose tuck label/form
US5420403A (en) * 1992-05-26 1995-05-30 Canada Post Corporation Mail encoding and processing system
US5457746A (en) * 1993-09-14 1995-10-10 Spyrus, Inc. System and method for access control for portable data storage media
US5483658A (en) * 1993-02-26 1996-01-09 Grube; Gary W. Detection of unauthorized use of software applications in processing devices
US5509074A (en) * 1994-01-27 1996-04-16 At&T Corp. Method of protecting electronically published materials using cryptographic protocols
US5530686A (en) * 1991-07-05 1996-06-25 U.S. Philips Corporation Record carrier having a track including audio information and additional non-audio information, and apparatus for reading and/or reproducing certain of the information included in such a track
US5550577A (en) * 1993-05-19 1996-08-27 Alcatel N.V. Video on demand network, including a central video server and distributed video servers with random access read/write memories
US5568275A (en) * 1992-04-10 1996-10-22 Avid Technology, Inc. Method for visually and audibly representing computer instructions for editing
US5619733A (en) * 1994-11-10 1997-04-08 International Business Machines Corporation Method and apparatus for synchronizing streaming and non-streaming multimedia devices by controlling the play speed of the non-streaming device in response to a synchronization signal
US5640453A (en) * 1994-08-11 1997-06-17 Stanford Telecommunications, Inc. Universal interactive set-top controller for downloading and playback of information and entertainment services
US5640560A (en) * 1995-08-02 1997-06-17 Microsoft Corporation CD-ROM content repurposing
US5642171A (en) * 1994-06-08 1997-06-24 Dell Usa, L.P. Method and apparatus for synchronizing audio and video data streams in a multimedia system
US5651064A (en) * 1995-03-08 1997-07-22 544483 Alberta Ltd. System for preventing piracy of recorded media
US5659792A (en) * 1993-01-15 1997-08-19 Canon Information Systems Research Australia Pty Ltd. Storyboard system for the simultaneous timing of multiple independent video animation clips
US5673195A (en) * 1995-06-12 1997-09-30 Schwartz; Vladimir Compact disc tracking system and method
US5677953A (en) * 1993-09-14 1997-10-14 Spyrus, Inc. System and method for access control for portable data storage media
US5694546A (en) * 1994-05-31 1997-12-02 Reisman; Richard R. System for automatic unattended electronic information transport between a server and a client by a vendor provided transport software with a manifest list
US5696898A (en) * 1995-06-06 1997-12-09 Lucent Technologies Inc. System and method for database access control
US5729687A (en) * 1993-12-20 1998-03-17 Intel Corporation System for sending differences between joining meeting information and public meeting information between participants in computer conference upon comparing annotations of joining and public meeting information
US5734898A (en) * 1994-06-24 1998-03-31 International Business Machines Corporation Client-server computer system and method for updating the client, server, and objects
US5734719A (en) * 1993-10-15 1998-03-31 International Business Systems, Incorporated Digital information accessing, delivery and production system
US5736977A (en) * 1995-04-26 1998-04-07 E-Systems, Inc. Video real estate information service
US5751672A (en) * 1995-07-26 1998-05-12 Sony Corporation Compact disc changer utilizing disc database
USRE35839E (en) * 1992-01-31 1998-07-07 Kabushiki Kaisha Sega Enterprises CD-ROM disk and security check method for the same
US5790753A (en) * 1996-01-22 1998-08-04 Digital Equipment Corporation System for downloading computer software programs
US5801685A (en) * 1996-04-08 1998-09-01 Tektronix, Inc. Automatic editing of recorded video elements sychronized with a script text read or displayed
US5802294A (en) * 1993-10-01 1998-09-01 Vicor, Inc. Teleconferencing system in which location video mosaic generator sends combined local participants images to second location video mosaic generator for displaying combined images
US5804810A (en) * 1996-06-26 1998-09-08 Par Government Systems Corporation Communicating with electronic tags
US5805442A (en) * 1996-05-30 1998-09-08 Control Technology Corporation Distributed interface architecture for programmable industrial control systems
US5809250A (en) * 1996-10-23 1998-09-15 Intel Corporation Methods for creating and sharing replayable modules representive of Web browsing session
US5808662A (en) * 1995-11-08 1998-09-15 Silicon Graphics, Inc. Synchronized, interactive playback of digital movies across a network
US5809471A (en) * 1996-03-07 1998-09-15 Ibm Corporation Retrieval of additional information not found in interactive TV or telephony signal by application using dynamically extracted vocabulary
US5812661A (en) * 1994-08-10 1998-09-22 Fujitsu Limited Software reproduction apparatus
US5819284A (en) * 1995-03-24 1998-10-06 At&T Corp. Personalized real time information display as a portion of a screen saver
US5822291A (en) * 1995-03-23 1998-10-13 Zoom Television, Inc. Mass storage element and drive unit therefor
US5822123A (en) * 1993-09-09 1998-10-13 Davis; Bruce Electronic television program guide schedule system and method with pop-up hints
US5825876A (en) * 1995-12-04 1998-10-20 Northern Telecom Time based availability to content of a storage medium
US5850218A (en) * 1997-02-19 1998-12-15 Time Warner Entertainment Company L.P. Inter-active program guide with default selection control
US5857021A (en) * 1995-11-07 1999-01-05 Fujitsu Ltd. Security system for protecting information stored in portable storage media
US5860068A (en) * 1997-12-04 1999-01-12 Petabyte Corporation Method and system for custom manufacture and delivery of a data product
US5869819A (en) * 1994-08-17 1999-02-09 Metrologic Instuments Inc. Internet-based system and method for tracking objects bearing URL-encoded bar code symbols
US5872747A (en) * 1997-01-16 1999-02-16 Jbs Enterprises, Inc. Apparatus and method for scheduled playing of compact disc audio tracks
US5875296A (en) * 1997-01-28 1999-02-23 International Business Machines Corporation Distributed file system web server user authentication with cookies
US5878233A (en) * 1995-08-07 1999-03-02 International Business Machines Corporation System, method, and computer program product for reviewing and creating advisories for data located on a content server
US5878020A (en) * 1996-03-25 1999-03-02 Kabushiki Kaisha Toshiba Information recording disk with management areas
US5883623A (en) * 1992-04-08 1999-03-16 Borland International, Inc. System and methods for building spreadsheet applications
US5882291A (en) * 1996-12-10 1999-03-16 Neocardia, Llc Device and method for controlling dose rate during intravascular radiotherapy
US5887143A (en) * 1995-10-26 1999-03-23 Hitachi, Ltd. Apparatus and method for synchronizing execution of programs in a distributed real-time computing system
US5889980A (en) * 1995-03-31 1999-03-30 International Business Machines Corporation Mode independent support of format conversion instructions for hexadecimal and binary floating point processing
US5892900A (en) * 1996-08-30 1999-04-06 Intertrust Technologies Corp. Systems and methods for secure transaction management and electronic rights protection
US5892908A (en) * 1996-09-10 1999-04-06 Marketscape Method of extracting network information
US5892825A (en) * 1996-05-15 1999-04-06 Hyperlock Technologies Inc Method of secure server control of local media via a trigger through a network for instant local access of encrypted data on local media
US5893910A (en) * 1996-01-04 1999-04-13 Softguard Enterprises Inc. Method and apparatus for establishing the legitimacy of use of a block of digitally represented information
US5895073A (en) * 1994-04-14 1999-04-20 Moore; Lewis J. Anti-counterfeiting system
US5896132A (en) * 1997-02-10 1999-04-20 International Business Machines Corporation Replacement of traditional scroll bar with a "more" bar
US5899980A (en) * 1997-08-11 1999-05-04 Trivnet Ltd. Retail method over a wide area network
US5907322A (en) * 1996-10-16 1999-05-25 Catch Tv Acquisition Corp. Television event marking system
US5907704A (en) * 1995-04-03 1999-05-25 Quark, Inc. Hierarchical encapsulation of instantiated objects in a multimedia authoring system including internet accessible objects
US5909551A (en) * 1995-08-25 1999-06-01 Hitachi, Ltd. Interactive recording/reproducing medium and reproducing system
US5913210A (en) * 1998-03-27 1999-06-15 Call; Charles G. Methods and apparatus for disseminating product information via the internet
US5915093A (en) * 1997-04-24 1999-06-22 Howard Berlin Computer network debit disk used for prepayment to transfer information from a central computer
US5920694A (en) * 1993-03-19 1999-07-06 Ncr Corporation Annotation of computer video displays
US5924013A (en) * 1997-09-03 1999-07-13 Guido; Mary M. Method and apparatus for transmitting motion picture cinematic information for viewing in movie theaters and ordering method therefor
US5922045A (en) * 1996-07-16 1999-07-13 At&T Corp. Method and apparatus for providing bookmarks when listening to previously recorded audio programs
US5930767A (en) * 1997-05-28 1999-07-27 Motorola, Inc. Transaction methods systems and devices
US5930238A (en) * 1997-07-10 1999-07-27 General Datacomm Asynchronous transfer mode (ATM) multicast tree delivery switching
US5931906A (en) * 1997-04-18 1999-08-03 Creative Communications Group System for creating a multimedia presentation by integrating local program materials with remotely accessible program materials
US5933497A (en) * 1990-12-14 1999-08-03 International Business Machines Corporation Apparatus and method for controlling access to software
US5940504A (en) * 1991-07-01 1999-08-17 Infologic Software, Inc. Licensing management system and method in which datagrams including an address of a licensee and indicative of use of a licensed product are sent from the licensee's site
US5943304A (en) * 1995-11-17 1999-08-24 Matsushita Electric Industrial Co., Ltd. Method of reproducing multimedia data and multimedia data server system
US5950173A (en) * 1996-10-25 1999-09-07 Ipf, Inc. System and method for delivering consumer product related information to consumers within retail environments using internet-based information servers and sales agents
US5956482A (en) * 1996-05-15 1999-09-21 At&T Corp Multimedia information service access
US5960398A (en) * 1996-07-31 1999-09-28 Wictor Company Of Japan, Ltd. Copyright information embedding apparatus
US5969898A (en) * 1997-10-01 1999-10-19 Storage Technology Corporation Method and system for reading data that is unreadable by a tape drive
US5978773A (en) * 1995-06-20 1999-11-02 Neomedia Technologies, Inc. System and method for using an ordinary article of commerce to access a remote computer
US5986690A (en) * 1992-12-09 1999-11-16 Discovery Communications, Inc. Electronic book selection and delivery system
US6108687A (en) * 1998-03-02 2000-08-22 Hewlett Packard Company System and method for providing a synchronized display to a plurality of computers over a global computer network
US6381404B1 (en) * 1999-01-28 2002-04-30 Oak Technology, Inc. Memory efficient method and apparatus for reading and caching of DVD data
US20020184627A1 (en) * 1997-02-28 2002-12-05 Alba Theresa A. Television control interface with electronic guide
US6609253B1 (en) * 1999-12-30 2003-08-19 Bellsouth Intellectual Property Corporation Method and system for providing interactive media VCR control

Family Cites Families (84)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4881061A (en) 1988-12-05 1989-11-14 Minnesota Mining And Manufacturing Company Article removal control system
US6076733A (en) 1993-11-24 2000-06-20 Metrologic Instruments, Inc. Web-based system and method for enabling a viewer to access and display HTML-encoded documents located on the world wide web (WWW) by reading URL-encoded bar code symbols printed on a web-based information resource guide
US6208805B1 (en) 1992-02-07 2001-03-27 Max Abecassis Inhibiting a control function from interfering with a playing of a video
DE4242992B4 (en) 1992-12-18 2004-01-29 Meto International Gmbh Arrangement for securing an article, in particular a recording disk such as a CD disk
US6246778B1 (en) 1994-04-14 2001-06-12 Lewis J. Moore Product distribution verification system using encoded marks indicative of product and destination
US6064979A (en) 1996-10-25 2000-05-16 Ipf, Inc. Method of and system for finding and serving consumer product related information over the internet using manufacturer identification numbers
US6006328A (en) 1995-07-14 1999-12-21 Christopher N. Drake Computer software authentication, protection, and security system
US6002394A (en) 1995-10-02 1999-12-14 Starsight Telecast, Inc. Systems and methods for linking television viewers with advertisers and broadcasters
EP1005025B1 (en) 1995-10-09 2002-01-02 Matsushita Electric Industrial Co., Ltd. Optical disk for use with an encryption or program license system
US6035329A (en) 1995-12-07 2000-03-07 Hyperlock Technologies, Inc. Method of securing the playback of a DVD-ROM via triggering data sent via a cable network
US5699047A (en) 1996-01-19 1997-12-16 Minnesota Mining And Manufacturing Co. Electronic article surveillance markers for direct application to optically recorded media
WO1997027553A1 (en) 1996-01-29 1997-07-31 Futuretense, Inc. Distributed electronic publishing system
SG77111A1 (en) 1996-02-28 2000-12-19 It Innovations Pte Ltd A system for manipulating and upgrading data objects with remote data sources automatically and seamlessly
US6018768A (en) 1996-03-08 2000-01-25 Actv, Inc. Enhanced video programming system and method for incorporating and displaying retrieved integrated internet information segments
US20020049832A1 (en) * 1996-03-08 2002-04-25 Craig Ullman Enhanced video programming system and method for incorporating and displaying retrieved integrated internet information segments
US6055314A (en) 1996-03-22 2000-04-25 Microsoft Corporation System and method for secure purchase and delivery of video content programs
US5991798A (en) 1996-05-17 1999-11-23 Hitachi, Ltd. Package medium system having URL hyper-linked to data in removable storage
US5805699A (en) 1996-05-20 1998-09-08 Fujitsu Limited Software copying system
EP0814419A2 (en) 1996-06-19 1997-12-29 Knowledge Information Research Institute Method of and device for executing a software and medium for distribution
US5991374A (en) 1996-08-08 1999-11-23 Hazenfield; Joey C. Programmable messaging system for controlling playback of messages on remote music on-hold- compatible telephone systems and other message output devices
US5774666A (en) 1996-10-18 1998-06-30 Silicon Graphics, Inc. System and method for displaying uniform network resource locators embedded in time-based medium
US6052717A (en) 1996-10-23 2000-04-18 Family Systems, Ltd. Interactive web book system
US6154844A (en) 1996-11-08 2000-11-28 Finjan Software, Ltd. System and method for attaching a downloadable security profile to a downloadable
US6101180A (en) 1996-11-12 2000-08-08 Starguide Digital Networks, Inc. High bandwidth broadcast system having localized multicast access to broadcast content
US5995965A (en) 1996-11-18 1999-11-30 Humetrix, Inc. System and method for remotely accessing user data records
US6134533A (en) 1996-11-25 2000-10-17 Shell; Allyn M. Multi-level marketing computer network server
US6543053B1 (en) * 1996-11-27 2003-04-01 University Of Hong Kong Interactive video-on-demand system
US6034925A (en) 1996-12-02 2000-03-07 Thomson Consumer Electronics, Inc. Accessing control method for identifying a recording medium in a jukebox
DE69720938T2 (en) 1996-12-20 2004-03-04 Texas Instruments Inc., Dallas Security system improvements
JPH10198965A (en) 1997-01-10 1998-07-31 Sony Corp Optical disk reproducing method, and device therefor
TW401573B (en) 1997-01-10 2000-08-11 Victor Company Of Japan Methods, apparatuse, and systems for producing and writing cipher keys, reproducing information with a cipher key, and for permitting reproduction of information with a cipher key, and optical disc recorded with a cipher key
US6073124A (en) 1997-01-29 2000-06-06 Shopnow.Com Inc. Method and system for securely incorporating electronic information into an online purchasing application
US6301661B1 (en) 1997-02-12 2001-10-09 Verizon Labortories Inc. Enhanced security for applications employing downloadable executable content
JP3497342B2 (en) 1997-02-27 2004-02-16 株式会社日立製作所 Client / server system, server, client processing method, and server processing method
US6061057A (en) 1997-03-10 2000-05-09 Quickbuy Inc. Network commercial system using visual link objects
US6209028B1 (en) 1997-03-21 2001-03-27 Walker Digital, Llc System and method for supplying supplemental audio information for broadcast television programs
US6182222B1 (en) 1997-03-25 2001-01-30 Electronic Data Systems Corporation Secure data storage system and method
US6449653B2 (en) 1997-03-25 2002-09-10 Microsoft Corporation Interleaved multiple multimedia stream for synchronized transmission over a computer network
US5987525A (en) 1997-04-15 1999-11-16 Cddb, Inc. Network delivery of interactive entertainment synchronized to playback of audio recordings
US6128649A (en) 1997-06-02 2000-10-03 Nortel Networks Limited Dynamic selection of media streams for display
US6219675B1 (en) 1997-06-05 2001-04-17 Microsoft Corporation Distribution of a centralized database
US6145006A (en) 1997-06-25 2000-11-07 Emc Corporation Method and apparatus for coordinating locking operations of heterogeneous host computers accessing a storage subsystem
US6175842B1 (en) 1997-07-03 2001-01-16 At&T Corp. System and method for providing dynamic three-dimensional multi-user virtual spaces in synchrony with hypertext browsing
JP3688099B2 (en) 1997-07-22 2005-08-24 富士通株式会社 Electronic information distribution method and recording medium
US6101534A (en) 1997-09-03 2000-08-08 Rothschild; Leigh M. Interactive, remote, computer interface system
US6138150A (en) 1997-09-03 2000-10-24 International Business Machines Corporation Method for remotely controlling computer resources via the internet with a web browser
US6134593A (en) 1997-09-30 2000-10-17 Cccomplete, Inc. Automated method for electronic software distribution
US6009410A (en) 1997-10-16 1999-12-28 At&T Corporation Method and system for presenting customized advertising to a user on the world wide web
US6195693B1 (en) 1997-11-18 2001-02-27 International Business Machines Corporation Method and system for network delivery of content associated with physical audio media
US6052785A (en) 1997-11-21 2000-04-18 International Business Machines Corporation Multiple remote data access security mechanism for multitiered internet computer networks
US5991399A (en) 1997-12-18 1999-11-23 Intel Corporation Method for securely distributing a conditional use private key to a trusted entity on a remote system
US6044403A (en) 1997-12-31 2000-03-28 At&T Corp Network server platform for internet, JAVA server and video application server
US6229523B1 (en) 1998-02-18 2001-05-08 Oak Technology, Inc. Digital versatile disc playback system with efficient modification of subpicture data
JP4014281B2 (en) * 1998-03-19 2007-11-28 富士通株式会社 Program reservation system in CATV
IL123819A (en) 1998-03-24 2001-09-13 Geo Interactive Media Group Lt Network media streaming
US6154738A (en) 1998-03-27 2000-11-28 Call; Charles Gainor Methods and apparatus for disseminating product information via the internet using universal product codes
US6233618B1 (en) 1998-03-31 2001-05-15 Content Advisor, Inc. Access control of networked data
US6243692B1 (en) 1998-05-22 2001-06-05 Preview Software Secure electronic software packaging using setup-external unlocking module
US6080207A (en) 1998-06-04 2000-06-27 Gateway 2000, Inc. System and method of creating and delivering software
US6698020B1 (en) 1998-06-15 2004-02-24 Webtv Networks, Inc. Techniques for intelligent video ad insertion
US6321252B1 (en) 1998-07-17 2001-11-20 International Business Machines Corporation System and method for data streaming and synchronization in multimedia groupware applications
US6141010A (en) 1998-07-17 2000-10-31 B. E. Technology, Llc Computer interface method and apparatus with targeted advertising
US6157953A (en) 1998-07-28 2000-12-05 Sun Microsystems, Inc. Authentication and access control in a management console program for managing services in a computer network
US6016166A (en) 1998-08-31 2000-01-18 Lucent Technologies Inc. Method and apparatus for adaptive synchronization of digital video and audio playback in a multimedia playback system
US6230174B1 (en) 1998-09-11 2001-05-08 Adobe Systems Incorporated Method of generating a markup language document containing image slices
US6510467B1 (en) 1998-09-16 2003-01-21 International Business Machines Corporation Method for transferring data files between a user and an internet server
US6331865B1 (en) 1998-10-16 2001-12-18 Softbook Press, Inc. Method and apparatus for electronically distributing and viewing digital contents
US6408128B1 (en) 1998-11-12 2002-06-18 Max Abecassis Replaying with supplementary information a segment of a video
US6374402B1 (en) 1998-11-16 2002-04-16 Into Networks, Inc. Method and apparatus for installation abstraction in a secure content delivery system
US6460086B1 (en) 1998-12-01 2002-10-01 Sun Microsystems, Inc. Method and apparatus for delivery of a bytecode embedded within a transport stream
US6453420B1 (en) 1999-04-21 2002-09-17 Research Investment Network, Inc. System, method and article of manufacture for authorizing the use of electronic content utilizing a laser-centric medium
US6529949B1 (en) 2000-02-07 2003-03-04 Interactual Technologies, Inc. System, method and article of manufacture for remote unlocking of local content located on a client device
US6239793B1 (en) 1999-05-20 2001-05-29 Rotor Communications Corporation Method and apparatus for synchronizing the broadcast content of interactive internet-based programs
WO2000071321A2 (en) 1999-05-21 2000-11-30 Microsoft Corporation Shared views for browsing content
US6415438B1 (en) 1999-10-05 2002-07-02 Webtv Networks, Inc. Trigger having a time attribute
US6341375B1 (en) 1999-07-14 2002-01-22 Lsi Logic Corporation Video on demand DVD system
US6591420B1 (en) 1999-08-25 2003-07-08 Warner Music Group, Inc. Remote control system for audio and video content
US6192340B1 (en) 1999-10-19 2001-02-20 Max Abecassis Integration of music from a personal library with real-time information
US6535909B1 (en) 1999-11-18 2003-03-18 Contigo Software, Inc. System and method for record and playback of collaborative Web browsing session
US6389467B1 (en) 2000-01-24 2002-05-14 Friskit, Inc. Streaming media search and continuous playback system of media resources located by multiple network addresses
US6505169B1 (en) 2000-01-26 2003-01-07 At&T Corp. Method for adaptive ad insertion in streaming multimedia content
US6691106B1 (en) 2000-05-23 2004-02-10 Intel Corporation Profile driven instant web portal
US6341292B1 (en) 2000-05-30 2002-01-22 Outlooksoft Corporation Spreadsheet-based network information exchange with two-part cache
US6691126B1 (en) 2000-06-14 2004-02-10 International Business Machines Corporation Method and apparatus for locating multi-region objects in an image or video database

Patent Citations (99)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4672572A (en) * 1984-05-21 1987-06-09 Gould Inc. Protector system for computer access and use
US4739510A (en) * 1985-05-01 1988-04-19 General Instrument Corp. Direct broadcast satellite signal transmission system
US5128752A (en) * 1986-03-10 1992-07-07 Kohorn H Von System and method for generating and redeeming tokens
US4709813A (en) * 1986-04-10 1987-12-01 Minnesota Mining And Manufacturing Company Anti-theft device for compact discs
US4710754A (en) * 1986-09-19 1987-12-01 Minnesota Mining And Manufacturing Company Magnetic marker having switching section for use in electronic article surveillance systems
US4785472A (en) * 1987-05-11 1988-11-15 The Trustees Of The Stevens Institute Of Technology Remote teaching system
US5023907A (en) * 1988-09-30 1991-06-11 Apollo Computer, Inc. Network license server
US4888638A (en) * 1988-10-11 1989-12-19 A. C. Nielsen Company System for substituting television programs transmitted via telephone lines
US5109482A (en) * 1989-01-11 1992-04-28 David Bohrman Interactive video control system for displaying user-selectable clips
US5274758A (en) * 1989-06-16 1993-12-28 International Business Machines Computer-based, audio/visual creation and presentation system and method
US4967185A (en) * 1989-08-08 1990-10-30 Minnesota Mining And Manufacturing Company Multi-directionally responsive, dual-status, magnetic article surveillance marker having continuous keeper
US4993068A (en) * 1989-11-27 1991-02-12 Motorola, Inc. Unforgeable personal identification system
US5933497A (en) * 1990-12-14 1999-08-03 International Business Machines Corporation Apparatus and method for controlling access to software
US5940504A (en) * 1991-07-01 1999-08-17 Infologic Software, Inc. Licensing management system and method in which datagrams including an address of a licensee and indicative of use of a licensed product are sent from the licensee's site
US5530686A (en) * 1991-07-05 1996-06-25 U.S. Philips Corporation Record carrier having a track including audio information and additional non-audio information, and apparatus for reading and/or reproducing certain of the information included in such a track
US5410343A (en) * 1991-09-27 1995-04-25 Bell Atlantic Network Services, Inc. Video-on-demand services using public switched telephone network
USRE35839E (en) * 1992-01-31 1998-07-07 Kabushiki Kaisha Sega Enterprises CD-ROM disk and security check method for the same
US5305195A (en) * 1992-03-25 1994-04-19 Gerald Singer Interactive advertising system for on-line terminals
US5883623A (en) * 1992-04-08 1999-03-16 Borland International, Inc. System and methods for building spreadsheet applications
US5568275A (en) * 1992-04-10 1996-10-22 Avid Technology, Inc. Method for visually and audibly representing computer instructions for editing
US5347508A (en) * 1992-04-22 1994-09-13 Minnesota Mining And Manufacturing Company Optical information storage disk for use with electronic article surveillance systems
US5420403A (en) * 1992-05-26 1995-05-30 Canada Post Corporation Mail encoding and processing system
US5289439A (en) * 1992-05-27 1994-02-22 Vimak Corporation CD transport apparatus
US5353218A (en) * 1992-09-17 1994-10-04 Ad Response Micromarketing Corporation Focused coupon system
US5305197A (en) * 1992-10-30 1994-04-19 Ie&E Industries, Inc. Coupon dispensing machine with feedback
US5986690A (en) * 1992-12-09 1999-11-16 Discovery Communications, Inc. Electronic book selection and delivery system
US5659792A (en) * 1993-01-15 1997-08-19 Canon Information Systems Research Australia Pty Ltd. Storyboard system for the simultaneous timing of multiple independent video animation clips
US5483658A (en) * 1993-02-26 1996-01-09 Grube; Gary W. Detection of unauthorized use of software applications in processing devices
US5920694A (en) * 1993-03-19 1999-07-06 Ncr Corporation Annotation of computer video displays
US5550577A (en) * 1993-05-19 1996-08-27 Alcatel N.V. Video on demand network, including a central video server and distributed video servers with random access read/write memories
US5400402A (en) * 1993-06-07 1995-03-21 Garfinkle; Norton System for limiting use of down-loaded video-on-demand data
US5413383A (en) * 1993-09-08 1995-05-09 The Standard Register Company Multipurpose tuck label/form
US5822123A (en) * 1993-09-09 1998-10-13 Davis; Bruce Electronic television program guide schedule system and method with pop-up hints
US5677953A (en) * 1993-09-14 1997-10-14 Spyrus, Inc. System and method for access control for portable data storage media
US5457746A (en) * 1993-09-14 1995-10-10 Spyrus, Inc. System and method for access control for portable data storage media
US5802294A (en) * 1993-10-01 1998-09-01 Vicor, Inc. Teleconferencing system in which location video mosaic generator sends combined local participants images to second location video mosaic generator for displaying combined images
US5734719A (en) * 1993-10-15 1998-03-31 International Business Systems, Incorporated Digital information accessing, delivery and production system
US5729687A (en) * 1993-12-20 1998-03-17 Intel Corporation System for sending differences between joining meeting information and public meeting information between participants in computer conference upon comparing annotations of joining and public meeting information
US5509074A (en) * 1994-01-27 1996-04-16 At&T Corp. Method of protecting electronically published materials using cryptographic protocols
US5895073A (en) * 1994-04-14 1999-04-20 Moore; Lewis J. Anti-counterfeiting system
US5694546A (en) * 1994-05-31 1997-12-02 Reisman; Richard R. System for automatic unattended electronic information transport between a server and a client by a vendor provided transport software with a manifest list
US5642171A (en) * 1994-06-08 1997-06-24 Dell Usa, L.P. Method and apparatus for synchronizing audio and video data streams in a multimedia system
US5734898A (en) * 1994-06-24 1998-03-31 International Business Machines Corporation Client-server computer system and method for updating the client, server, and objects
US5812661A (en) * 1994-08-10 1998-09-22 Fujitsu Limited Software reproduction apparatus
US5640453A (en) * 1994-08-11 1997-06-17 Stanford Telecommunications, Inc. Universal interactive set-top controller for downloading and playback of information and entertainment services
US5869819A (en) * 1994-08-17 1999-02-09 Metrologic Instuments Inc. Internet-based system and method for tracking objects bearing URL-encoded bar code symbols
US5619733A (en) * 1994-11-10 1997-04-08 International Business Machines Corporation Method and apparatus for synchronizing streaming and non-streaming multimedia devices by controlling the play speed of the non-streaming device in response to a synchronization signal
US5651064A (en) * 1995-03-08 1997-07-22 544483 Alberta Ltd. System for preventing piracy of recorded media
US5822291A (en) * 1995-03-23 1998-10-13 Zoom Television, Inc. Mass storage element and drive unit therefor
US5819284A (en) * 1995-03-24 1998-10-06 At&T Corp. Personalized real time information display as a portion of a screen saver
US5889980A (en) * 1995-03-31 1999-03-30 International Business Machines Corporation Mode independent support of format conversion instructions for hexadecimal and binary floating point processing
US5907704A (en) * 1995-04-03 1999-05-25 Quark, Inc. Hierarchical encapsulation of instantiated objects in a multimedia authoring system including internet accessible objects
US5736977A (en) * 1995-04-26 1998-04-07 E-Systems, Inc. Video real estate information service
US5696898A (en) * 1995-06-06 1997-12-09 Lucent Technologies Inc. System and method for database access control
US5673195A (en) * 1995-06-12 1997-09-30 Schwartz; Vladimir Compact disc tracking system and method
US5978773A (en) * 1995-06-20 1999-11-02 Neomedia Technologies, Inc. System and method for using an ordinary article of commerce to access a remote computer
US5751672A (en) * 1995-07-26 1998-05-12 Sony Corporation Compact disc changer utilizing disc database
US5640560A (en) * 1995-08-02 1997-06-17 Microsoft Corporation CD-ROM content repurposing
US5878233A (en) * 1995-08-07 1999-03-02 International Business Machines Corporation System, method, and computer program product for reviewing and creating advisories for data located on a content server
US5909551A (en) * 1995-08-25 1999-06-01 Hitachi, Ltd. Interactive recording/reproducing medium and reproducing system
US5887143A (en) * 1995-10-26 1999-03-23 Hitachi, Ltd. Apparatus and method for synchronizing execution of programs in a distributed real-time computing system
US5857021A (en) * 1995-11-07 1999-01-05 Fujitsu Ltd. Security system for protecting information stored in portable storage media
US5808662A (en) * 1995-11-08 1998-09-15 Silicon Graphics, Inc. Synchronized, interactive playback of digital movies across a network
US5943304A (en) * 1995-11-17 1999-08-24 Matsushita Electric Industrial Co., Ltd. Method of reproducing multimedia data and multimedia data server system
US5825876A (en) * 1995-12-04 1998-10-20 Northern Telecom Time based availability to content of a storage medium
US5893910A (en) * 1996-01-04 1999-04-13 Softguard Enterprises Inc. Method and apparatus for establishing the legitimacy of use of a block of digitally represented information
US5790753A (en) * 1996-01-22 1998-08-04 Digital Equipment Corporation System for downloading computer software programs
US5809471A (en) * 1996-03-07 1998-09-15 Ibm Corporation Retrieval of additional information not found in interactive TV or telephony signal by application using dynamically extracted vocabulary
US5878020A (en) * 1996-03-25 1999-03-02 Kabushiki Kaisha Toshiba Information recording disk with management areas
US5801685A (en) * 1996-04-08 1998-09-01 Tektronix, Inc. Automatic editing of recorded video elements sychronized with a script text read or displayed
US5892825A (en) * 1996-05-15 1999-04-06 Hyperlock Technologies Inc Method of secure server control of local media via a trigger through a network for instant local access of encrypted data on local media
US5956482A (en) * 1996-05-15 1999-09-21 At&T Corp Multimedia information service access
US5805442A (en) * 1996-05-30 1998-09-08 Control Technology Corporation Distributed interface architecture for programmable industrial control systems
US5804810A (en) * 1996-06-26 1998-09-08 Par Government Systems Corporation Communicating with electronic tags
US5922045A (en) * 1996-07-16 1999-07-13 At&T Corp. Method and apparatus for providing bookmarks when listening to previously recorded audio programs
US5960398A (en) * 1996-07-31 1999-09-28 Wictor Company Of Japan, Ltd. Copyright information embedding apparatus
US5892900A (en) * 1996-08-30 1999-04-06 Intertrust Technologies Corp. Systems and methods for secure transaction management and electronic rights protection
US5892908A (en) * 1996-09-10 1999-04-06 Marketscape Method of extracting network information
US5907322A (en) * 1996-10-16 1999-05-25 Catch Tv Acquisition Corp. Television event marking system
US5809250A (en) * 1996-10-23 1998-09-15 Intel Corporation Methods for creating and sharing replayable modules representive of Web browsing session
US5950173A (en) * 1996-10-25 1999-09-07 Ipf, Inc. System and method for delivering consumer product related information to consumers within retail environments using internet-based information servers and sales agents
US5882291A (en) * 1996-12-10 1999-03-16 Neocardia, Llc Device and method for controlling dose rate during intravascular radiotherapy
US5872747A (en) * 1997-01-16 1999-02-16 Jbs Enterprises, Inc. Apparatus and method for scheduled playing of compact disc audio tracks
US5875296A (en) * 1997-01-28 1999-02-23 International Business Machines Corporation Distributed file system web server user authentication with cookies
US5896132A (en) * 1997-02-10 1999-04-20 International Business Machines Corporation Replacement of traditional scroll bar with a "more" bar
US5850218A (en) * 1997-02-19 1998-12-15 Time Warner Entertainment Company L.P. Inter-active program guide with default selection control
US20020184627A1 (en) * 1997-02-28 2002-12-05 Alba Theresa A. Television control interface with electronic guide
US5931906A (en) * 1997-04-18 1999-08-03 Creative Communications Group System for creating a multimedia presentation by integrating local program materials with remotely accessible program materials
US5915093A (en) * 1997-04-24 1999-06-22 Howard Berlin Computer network debit disk used for prepayment to transfer information from a central computer
US5930767A (en) * 1997-05-28 1999-07-27 Motorola, Inc. Transaction methods systems and devices
US5930238A (en) * 1997-07-10 1999-07-27 General Datacomm Asynchronous transfer mode (ATM) multicast tree delivery switching
US5899980A (en) * 1997-08-11 1999-05-04 Trivnet Ltd. Retail method over a wide area network
US5924013A (en) * 1997-09-03 1999-07-13 Guido; Mary M. Method and apparatus for transmitting motion picture cinematic information for viewing in movie theaters and ordering method therefor
US5969898A (en) * 1997-10-01 1999-10-19 Storage Technology Corporation Method and system for reading data that is unreadable by a tape drive
US5860068A (en) * 1997-12-04 1999-01-12 Petabyte Corporation Method and system for custom manufacture and delivery of a data product
US6108687A (en) * 1998-03-02 2000-08-22 Hewlett Packard Company System and method for providing a synchronized display to a plurality of computers over a global computer network
US5913210A (en) * 1998-03-27 1999-06-15 Call; Charles G. Methods and apparatus for disseminating product information via the internet
US6381404B1 (en) * 1999-01-28 2002-04-30 Oak Technology, Inc. Memory efficient method and apparatus for reading and caching of DVD data
US6609253B1 (en) * 1999-12-30 2003-08-19 Bellsouth Intellectual Property Corporation Method and system for providing interactive media VCR control

Cited By (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7711795B2 (en) 2000-01-20 2010-05-04 Sonic Solutions System, method and article of manufacture for remote control and navigation of local content
US7689510B2 (en) 2000-09-07 2010-03-30 Sonic Solutions Methods and system for use in network management of content
US7779097B2 (en) 2000-09-07 2010-08-17 Sonic Solutions Methods and systems for use in network management of content
US20050060754A1 (en) * 2003-09-17 2005-03-17 Wegener Communications, Inc. Apparatus and method for distributed control of media dissemination
US20090034939A1 (en) * 2004-01-09 2009-02-05 Tomoyuki Okada Recording medium, reproduction device, program, reproduction method
US8391677B2 (en) 2004-01-09 2013-03-05 Panasonic Corporation Recording medium, reproduction device, program, reproduction method
US20070198111A1 (en) * 2006-02-03 2007-08-23 Sonic Solutions Adaptive intervals in navigating content and/or media
US8954852B2 (en) 2006-02-03 2015-02-10 Sonic Solutions, Llc. Adaptive intervals in navigating content and/or media
US9372604B2 (en) 2006-02-03 2016-06-21 Rovi Technologies Corporation Adaptive intervals in navigating content and/or media
US20100151783A1 (en) * 2008-12-12 2010-06-17 At&T Intellectual Property I, L.P. Systems and Methods for Synchronized Playout of Music on Several Personal Digital Music Players
US8515338B2 (en) * 2008-12-12 2013-08-20 At&T Intellectual Property I, L.P. Systems and methods for synchronized playout of music on several personal digital music players

Also Published As

Publication number Publication date
US6769130B1 (en) 2004-07-27

Similar Documents

Publication Publication Date Title
US6769130B1 (en) System, method and article of manufacture for late synchronization during the execution of a multimedia event on a plurality of client computers
US7188193B1 (en) System, method and article of manufacture for a synchronizer component in a multimedia synchronization framework
US7458091B1 (en) System, method and article of manufacture for a business layer component in a multimedia synchronization framework
US6941383B1 (en) System, method and article of manufacture for java/javascript component in a multimedia synchronization framework
US6529949B1 (en) System, method and article of manufacture for remote unlocking of local content located on a client device
US9571534B2 (en) Virtual meeting video sharing
US6848004B1 (en) System and method for adaptive delivery of rich media content to a user in a network based on real time bandwidth measurement &amp; prediction according to available user bandwidth
US8015491B2 (en) Systems and methods for a single development tool of unified online and offline content providing a similar viewing experience
US8265457B2 (en) Proxy editing and rendering for various delivery outlets
US20070201502A1 (en) Systems and methods for controlling the delivery behavior of downloaded content
CN103535026A (en) Image-based synchronization system and method
KR100340169B1 (en) System and Method for Web Cataloging Dynamic Multimedia Using Java
WO2023147758A1 (en) Method and apparatus for processing cloud game resource data, and computer device and storage medium
JPH11355658A (en) Presentation sequence generating method, program storage device, programmatic presentation generator, set top box and television set
JP2002502169A (en) Method and system for client-server interaction in conversational communication
Kumar et al. The HotMedia architecture: progressive and interactive rich media for the Internet
US20130182183A1 (en) Hardware-Based, Client-Side, Video Compositing System
KR20180041879A (en) Method for editing and apparatus thereof
Hayashi et al. Building Virtual Museum Exhibition System as a Medium
US20230276105A1 (en) Information processing apparatus, information processing apparatus, and program
US20230229443A1 (en) Synchronizing multiple instances of projects
WO2001054344A1 (en) System, method and article of manufacture for remote control and navigation of local content
Childers et al. Streaming media for web based training
WO2024005910A1 (en) Generating boundary points for media content
MOHLER Improving the delivery of instructional graphics on the Web with vector technology

Legal Events

Date Code Title Description
AS Assignment

Owner name: SONIC SOLUTIONS, A CALIFORNIA CORPORATION, CALIFOR

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:INTERACTUAL TECHNOLOGIES, INC., A CALIFORNIA CORPORATION;REEL/FRAME:017596/0401

Effective date: 20060327

STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION