HK1202007B - Methods and systems for digital file distribution to theaters - Google Patents

Description

Method and system for distributing digital files to movie theaters

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Application No. 61/801,870, filed March 15, 2013, which is hereby incorporated by reference in its entirety.

Technical Field

The present invention relates generally to digital file distribution technology, and certain embodiments relate to methods for automatically distributing digital cinema files to theaters.

Background Art

Recent technological advances have enabled digital playback and broadcasting of feature films at high resolutions, increasing the adoption of digital systems for playback of digital cinema content. Digital Cinema Initiatives, LLC (DCI) was founded by film studios recognizing the benefits of adopting industry-wide standards for digital cinema. DCI has defined industry-wide standards and requirements for mastering, distribution, and cinema playback of digital cinema content.

Summary of the Invention

According to various embodiments of the disclosed method and system, a digital cinema file is distributed from a server to a cinema. In one embodiment, the server receives a request for component parts of a digital content package; the component parts of the digital content package are stored on the server; the component parts of the digital content package are assembled; and the assembled digital content package is encrypted.

In another embodiment, a server updates an original production playlist, updates a track file associated with the updated production playlist, and automatically distributes the updated production playlist and the updated track file to one or more theaters via a communication network. The theaters are configured to store the updated track file in a memory, which contains copies of all track files associated with the updated production playlist, and update the theaters' original production playlists to the updated production playlist.

In one embodiment, the updated production playlist and the updated trajectory file are distributed to theaters only if the theaters are geographically located in the region associated with the production playlist. In another embodiment, the server includes a theater information database that tracks the current production playlists associated with all theaters in the server-theater digital cinema distribution system.

In one embodiment, the cinema initiates a request to receive an updated track file from the server. The server authenticates the cinema, determines the cinema's current playlist and associated track file, and sends the updated track file and associated updated playlist to the cinema via a communication network. In another embodiment, the server determines the cinema's current playlist and associated track file by referring to a cinema information database stored in a memory unit communicatively connected to the server.

Other features and aspects of the disclosed methods and systems will become apparent from the following detailed description, taken in conjunction with the accompanying drawings, which illustrate, by way of example, features according to embodiments of the present invention. SUMMARY OF THE INVENTION This summary is not intended to limit the scope of the invention as claimed, which is defined solely by the claims appended hereto.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention, in accordance with one or more various embodiments, will now be described in detail with reference to the following drawings, which are for purposes of illustration only and merely depict typical or exemplary embodiments of the invention.

FIG. 1 shows a system for automatically distributing digital cinema files according to the present invention.

FIG. 2 illustrates a method for pushing digital cinema file updates from a server to a cinema.

FIG3 illustrates a method for pulling digital cinema file updates from a server to a cinema.

FIG4 illustrates an example computing module that may be used to implement various features of the methods and apparatus disclosed herein.

The drawings are not intended to be exhaustive and do not limit the invention to the precise form disclosed.

DETAILED DESCRIPTION

Given the large file sizes of high-resolution encoded digital cinema files, methods and systems for efficiently distributing digital cinema files in accordance with the DCI are desirable. Currently, digital films are delivered to cinemas via physical hard drives or satellite delivery. These delivery methods present two problems. First, incremental updates to films (e.g., regional changes to soundtracks, video and display formats such as 2D, 3D, Dolby sound, and ethnic customizations) are limited to manual deliverers localized to individual cinemas. Second, digital content packages (DCPs) can become bloated with a variety of options for trailers, languages, sound formats, image selections, and other technical changes, which result in a large number of permutations when distributing the DCPs. This requires pre-packaging, quality control, and shipping of multiple DCPs, which creates logistical problems and expenses for DCPs containing content that is not intended for use in a particular region.

Various embodiments of the present invention illustrate systems and methods for automatically distributing digital cinema updates to cinemas by separately delivering track file updates after the initial master file is delivered to all cinemas. In addition, embodiments illustrate methods and systems for on-demand assembly of digital content packages.

FIG1 illustrates a system for distributing digital cinema files according to the present invention. In distribution system 100, server 140 can distribute digital cinema trajectory files 134 stored in storage 130 to multiple cinemas 110 via communication network 120. In response to updates to server-side trajectory files 134, digital cinema files are automatically pushed from server 140 to cinemas 110 (step 150). In addition to or in lieu of pushing digital cinema files, in response to a request for cinema trajectory file updates from cinema 110 (step 114), cinema 110 pulls digital cinema files from server 140 (step 160).

The communication network 120 may include a cloud-based network, a satellite network, a cellular telephone network, an ad hoc network, an intranet, an extranet, a virtual private network (VPN), a local area network (LAN), a wireless LAN (WLAN), a wide area network (WAN), a portion of the Internet, a portion of the public switched telephone network (PSTN), or any combination thereof. The communication network 120 may employ a variety of communication mediums. The communication medium may be a wireless network system, such as a satellite network, a cellular network, a wireless personal area network, a wireless local area network, or other similar communication medium. The communication medium may alternatively be a wired system, such as a coaxial cable system, a fiber optic cable system, an Ethernet cable system, or other similar communication medium.

Server 140 may be operated by a digital cinema file distributor or a digital content creator (e.g., a movie studio). Server 140 may comprise a single computer unit or a distributed computing system that includes a combination of software and hardware to perform the cinema file distribution functions of distribution system 100. For example, server 140 may comprise a processing module 141, a transceiver module 142 for communicating over network 120, a memory module 143, a security module 144, storage 130, and a database 139. These modules and components may be separate or integrated. These modules may be located within server 140 or communicatively connected to server 140.

Referring now to storage 130, digital cinema files may be packaged according to the DCI standard on server 140. Storage 130 may include one or more digital cinema package (DCP) files 132. Each DCP 132 is a collection of all necessary files for a digital cinema production, such as a movie and its trailer.

In one embodiment, by storing all parts of the DCP 132 in the memory 130, the DCP 132 can be assembled as required by the server 140. In another embodiment, the DCP 132 parts can be stored in regional warehouses. The assembled DCP can be customized by the theater, region, or individual screen. According to this embodiment, the order of the specific component parts of the DCP 132 is implemented by the DCP system running on the server 140. This order can be implemented after the selected component parts of the DCP 132 are available on the server 140. The DCP can be assembled based on the selected component parts. The DCP system can confirm that the DCP 132 is compliant with the DCI and generate encryption keys for the DCP 132 in preparation for transmission.

The assembled DCP 132 can be pushed by the server 140 (step 160) or pulled by an authorized theater 110 (step 160). During the transmission of the DCP, software based on the transmission manager (not shown) can confirm that the DCP 132 contains the properly named files, keys, and all other information. The transmission manager also tracks the transmission of the DCP 132. For example, it can monitor that the DCP 132 arrives at its destination without checksum errors, report the progress of the DCP 132 during transmission, and report if the DCP 132 is created but not sent.

In yet another embodiment, the DCP system may be configured to provide updates on the status, configuration, or overall DCP 132 order status, requests for supplemental material, and generated keys.

A single DCP 132 can have multiple production playlists (CPLs) 133. For example, a DCP 132 can have three CPLs that share a common set of track files 134, but separate sets of audio track files dubbed for the film's three languages (e.g., Chinese, German, and Spanish). Each CPL 133 is a text list containing instructions for how the DCP's elements, namely the track files 134, should be played back. The CPLs 133 have a timecode index that specifies the order in which the associated track files should be played to present a digital cinema production, such as a film.

Track files 134 are digital cinema files that are distributed separately according to system 100. Each track file includes metadata or essence 135 in the file body, and associated file headers and file footers. Track files are also required to have time codes 137 to allow synchronization with associated track files.

Track files 134 include image metadata 135, sound metadata 135, subtitle (synchronized text and/or sub-pictures) metadata, or title metadata. Track files 134 include metadata including, for example, French subtitles for the first ten minutes of a film, commercial clips, a director's cut of a film, an alternate ending for a film, a film clip (e.g., the first five minutes, different ratio versions of scenes, credits, etc.), or a dubbing of a film clip. Each track file 134 has an associated time code 137 for synchronizing its playback with other related track files 134 (i.e., parts of the same theatrical production). The CPL 133 uses time code indexing to play associated track files (e.g., consecutive picture track files or synchronized image and sound track files) 134 in the correct order.

During the DCP 132 creation process, each trajectory file 134 is encrypted and assigned a unique encryption key 136. Each key 136 is stored in memory 130. During the delivery process (push 150 or pull 160), each encryption key associated with the trajectory file is delivered to allow decryption at the receiving end. The key delivery message can be used to package the encryption key in a file format (e.g., XML) that only allows specific trusted devices to access the key.

Referring now to the cinema end of the file distribution system, each cinema 110 can receive the same initial master file 105 for a film work from a content distributor, which includes a CPL 133 and associated track files 134. The master file 105 is associated with the initial release of the film work (e.g., the initial English theatrical version). Subsequent transmissions of updated CPLs supplement the initial transmission with updated track files customized for a specific region or cinema (e.g., subtitle or audio (dubbing) track files for foreign cinemas and image track files for adding additional scenes). In this way, during additional updates such as advertisements, additional scenes, alternative endings, etc., it is not necessary to retransmit the entire digital cinema file content (i.e., all track files) associated with the film work.

Cinema 110 has a storage 111 for storing all CPLs and their associated track files for each film title played at the cinema. Storage 111 may comprise a hard disk array, a hard drive, a server, or other means for storing and organizing digital cinema content. Associated track files 134 may be stored in the same folder or approximate location in storage 111. A theater management system (TMS) or screen management system (SMS) in accordance with the DCI standard may manage cinema 110 and its associated storage 111. For example, the TMS may have a cinema manager controller that manages the playback of all CPLs and associated track files in each auditorium. The TMS also manages the storage of all digital cinema content. The SMS may have a user interface for controlling the playback of CPLs and associated track files in individual auditoriums. The TMS or SMS is configured to update the cinema's CPLs and associated track files upon receiving new cinema CPLs and associated track files.

Server 140 may include a database 139 within memory 130 to manage the delivery of CPL and track file updates to cinemas 110 within file distribution system 100. Database 139 stores the following data for each cinema 110: the cinema's region or location, the cinema's language, the cinema's time zone, the cinema's current CPL, associated track files (and encryption keys) for currently playing or previously played film titles, a history of CPL and track file updates for the cinema, cinema status, and more. Additionally, database 139 includes a list of all existing CPLs and associated track files. Each time a CPL and track file update is pushed or pulled by cinema 110 from server 140, server 140 can reference the applicable database entry. Database 139 can be configured to automatically update the stored data associated with cinema 110 whenever server 140 sends an updated CPL and track file to cinema 110. In another embodiment, a cinema's database entry can be manually updated via user input (e.g., keyboard and mouse).

FIG2 illustrates an exemplary method 200 for pushing (step 150) digital cinema file updates from server 140 to cinema 110 according to the system of FIG1 . As a first step 200, a content distributor or server 140 operator updates server files (CPL and associated track files) corresponding to a film production (e.g., adding additional track files corresponding to commercials, alternate endings, director's cuts, new scenes, new language releases, new subtitles, or new scenes with altered product placement). The server updates may be stored in memory 130. The updates may include adding additional content with new track files, replacing existing content (i.e., replacing track files), or deleting content associated with an existing CPL (i.e., deleting track files). In some embodiments, the updates may include adding a new CPL and new associated track files (e.g., a new set of audio track files associated with a foreign language version of a film). In another embodiment, the updates may include replacing or modifying an existing CPL. Cinema 110 corresponding to the updated CPL and associated track files may be marked in database 139. For example, if the server file update includes adding a new CPL and associated trajectory file for a new foreign language version of a feature film, the applicable foreign cinemas may be marked for updating in database 139 .

In step 201, server 140 determines whether an updated CPL or updated trajectory file has been previously sent to one or more corresponding cinemas 110. If not, server 140 may concurrently send the updated CPL 205 and updated trajectory file 204 to cinemas 110 (steps 202-203), along with the trajectory file encryption key. The server may only send updated trajectory files that are not stored in the cinema's 110 memory 111. The updated trajectory files may be sent automatically or in response to user input at server 140. A packaging list required by the DCI standard is also sent. A checksum of the sent updated CPL 205 and updated trajectory file 204 is performed to detect errors during the file transfer. If the checksum detects an error during the transfer, the files may be retransmitted. After successful transmission, server 140 may update its database 139 to record the updated CPL and trajectory file associated with cinema 110.

At step 206, the updated track file 204 and the updated CPL 205 are received at the cinema 110. The cinema 110 may store the updated track file in the same folder or directory as all track files associated with the updated work playlist in the memory 111. The corresponding cinema CPL and associated track files are then updated. Updating the CPL may include overwriting the original CPL or rewriting the time code index in the original CPL to match the time code index in the updated CPL. Updating the track file may include deleting the original track file associated with the same time code as the updated track file. In other embodiments, updating the track file may include adding the updated track file 204 to the set of original track files of the cinema 110. In still further embodiments, updating the track file may include decrypting the track file using the transmitted associated encryption key.

FIG3 illustrates an exemplary method 300 for cinema 110 to pull (step 160) digital cinema file updates from a server, according to the system of FIG1 . As a first step 301, cinema 110 sends a request to the server to update its master file 105 associated with digital cinema content (step 301), namely, its CPL and associated track files. Cinema 110 may request specific track file updates (step 114). For example, cinema 110 may request track files and corresponding CPLs associated with a director's cut, an alternate ending, commercials, additional scenes, subtitles, or dubbing. In some embodiments, cinema 110 may request updates repeatedly or periodically. In step 302, server 140 authenticates the requesting cinema 110 before allowing the cinema to pull any digital cinema content from its storage 130. If cinema 110 cannot be authenticated, the request is canceled (step 303). The security module 144 of server 140 may perform authentication of cinema 110. Security module 144 may employ any number of authentication methods. For example, it can adopt password authentication, digital signature authentication, IPSEC authentication, Secure Sockets Layer (SSL) authentication, public key encryption authentication, etc.

If the cinema is authenticated (step 302), a parallel process to the one described above with respect to push method 200 can be performed. If an updated CPL or updated trajectory file has been previously sent to cinema 110 (step 304), the cinema's request is canceled (step 303). If not, server 140 can concurrently send updated CPL 308 and updated trajectory file 307 to cinema 110, along with the trajectory file encryption key (steps 305-306). A packaging list as required by the DCI standard is also sent. A checksum of the sent updated CPL 308 and updated trajectory file 307 is performed to detect errors during file transfer. If the checksum detects an error during transfer, the file can be retransmitted. After a successful transfer, server 140 can update its database 139 to record the updated CPL and trajectory file associated with cinema 110.

In step 309, the updated track file 307 and the updated CPL 308 are received at the cinema 110. The cinema 110 may store the updated track file in the memory 111 in the same folder or directory as all track files associated with the updated work playlist. The corresponding cinema CPL and the associated track file are then updated. Updating the CPL may include overwriting the original CPL or rewriting the time code index in the original CPL to match the time code index in the updated CPL. Updating the track file may include deleting the original track file associated with the time code that is the same as the time code of the updated track file. In other embodiments, updating the track file may include adding the updated track file 307 to the original track file set of the cinema 110. In further embodiments, updating the track file may further include decrypting the track file using the associated encryption key that was transmitted.

FIG4 illustrates an exemplary computing module that may be used to implement various features of the methods and apparatus disclosed herein.

As used herein, the term module can describe a given functional unit that can be executed according to one or more embodiments of the present application. As used herein, a module can be implemented in the form of any hardware, software, and combinations thereof. For example, one or more processors, controllers, ASICs, PLAs, PALs, CPLDs, FPGAs, logic devices, software routines, or other mechanisms can be implemented to form a module. In an embodiment, the different modules described herein can be implemented as discrete modules or some or all of the features and functions described are shared between one or more modules. In other words, it will be apparent to those skilled in the art who have read this specification that the various features and functions described herein can be implemented in any given application and can be implemented in various combinations and permutations in one or more separate or shared modules. Even if the elements of various features or functions can be described separately or claimed as separate modules, it will be understood by those skilled in the art that these features and functions can be shared in one or more common software and hardware elements, and that this description should not require or imply that separate hardware or software elements are used to implement these features or functions.

In one embodiment, the components or modules of the present application are implemented in whole or in part using software. These software elements can be implemented to operate in conjunction with a computing or processing module that can perform the functions described herein. FIG4 shows an example computing module. Various embodiments are described in terms of this exemplary computing module 400. After reading this specification, it will become apparent to those skilled in the relevant art how to implement the present application using other computing modules or architectures.

4 , computing module 400 may represent, for example, a computing or processing capability component found in a desktop, laptop, notebook, or tablet computer; a handheld computing device (tablet, PDA, smartphone, cell phone, palmtop, etc.); a mainframe, supercomputer, workstation, or server; or any other type of specialized or general-purpose computing device required or suitable for a given application or environment. Computing module 400 may also represent computing capability embedded within or otherwise available to a given device. For example, computing modules may be found in other electronic devices such as, for example, digital cameras, navigation systems, cell phones, portable computing devices, modems, routers, WAPs, terminals, and other electronic devices that may contain some form of processing capability.

The computing module 400 may include, for example, one or more processors, controllers, control modules, or other processing devices, such as a processor 404. The processor 404 may be implemented using a general-purpose or dedicated processing engine, such as, for example, a microprocessor, controller, or other control logic. In the example shown, the processor 404 is connected to a bus 602, although any communication medium may be used to facilitate interaction with other components of the computing module 400 or to communicate with the outside world.

The computing module 400 may also include one or more memory modules, referred to herein simply as main memory 408. For example, preferably random access memory (RAM) or other dynamic storage may be used to store information and instructions to be executed by the processor 404. The main memory 408 may also be used to store temporary variables or other intermediate information during the execution of instructions to be executed by the processor 404. The computing module 400 may also similarly include a read-only memory ("ROM") or other static storage device connected to the bus 402 for storing static information and instructions for the processor 404.

The computing module 400 may also include one or more information storage mechanisms 410 in various forms, which may include, for example, a media drive 412 and a storage unit interface 420. The media drive 412 may include a drive or other mechanism that supports fixed or removable storage media 414. For example, a hard disk drive, a floppy disk drive, a tape drive, an optical disk drive, a CD or DVD drive (R or RW), or other removable or fixed media drive may be provided. Thus, the storage media 414 may include, for example, a hard disk, a floppy disk, a magnetic tape, a cassette, an optical disk, a CD or DVD, or other removable or fixed media that is read, written, or accessed by the media drive 412. As these examples illustrate, the storage media 414 may include computer-usable storage media having computer software or data stored therein.

In alternative embodiments, information storage mechanism 410 may include other similar means for allowing computer programs or other instructions or data to be loaded into computing module 400. Such means may include, for example, a fixed or removable storage unit 422 and an interface 420. Examples of such storage units 422 and interfaces 420 may include a program cartridge and cartridge interface, removable memory (e.g., flash memory or other removable storage module) and memory slot, PCMCIA slot and card, and other fixed or removable storage units 422 and interfaces 420 that allow software and data to be transferred from storage unit 422 to computing module 600.

The computing module 400 may include a communication interface 424. The communication interface 424 may be used to allow software and data to be transferred between the computing module 400 and external devices. Examples of the communication interface 424 may include a modem or software modem, a network interface (such as Ethernet, a network interface card, WiMedia, IEEE802.XX or other interface), a communication port (such as, for example, a USB port, an IR port, an RS232 port, a Bluetooth interface or other port) or other communication interface. The software and data transmitted through the communication interface 424 may typically be carried on a signal, which may be an electronic signal, an electromagnetic signal (including an optical signal) or other signal that can be exchanged through a given communication interface 424. These signals may be provided to the communication interface 424 via a channel 428. The channel 428 may carry signals and may be implemented using a wired or wireless communication medium. Some examples of channels may include a telephone line, a cellular link, an RF link, an optical link, a network interface, a local area network or a wide area network and other wired or wireless communication channels.

In this document, the terms "computer program medium" and "computer-usable medium" generally refer to temporary or non-temporary media, such as, for example, memory 408, storage unit 420, medium 414, and channel 428. These and other different forms of computer program media or computer-usable media involve one or more sequences for carrying one or more instructions to a processing device for execution. These instructions embedded in the medium are generally referred to as "computer program code" or "computer program product" (which can be grouped in the form of a computer program or other grouping). When executed, these instructions may enable computing module 400 to perform the features or functions of the present application discussed herein.

Although various exemplary embodiments and implementations have been described above, it should be understood that the various features, aspects, and functions described in one or more individual embodiments are not limited to the specific embodiments in which they are described, but may be applied alone or in various combinations to one or more other embodiments of the present application, whether or not such embodiments are described, and whether or not such features are presented as part of such described embodiments. Thus, the breadth and scope of the present application should not be limited by any of the exemplary embodiments described above.

The terms and phrases used in this document, and variations thereof, unless otherwise specifically stated, should be interpreted as open ended and not restrictive. As an example, the term "including" should be interpreted as meaning "including, but not limited to" or a similar meaning; the term "example" is used to provide an illustrative example of the term in question, not an exhaustive or limiting list; the term "one" should be interpreted as meaning "at least one," "one or more," or a similar meaning; adjectives such as "conventional," "traditional," "normal," "standard," "known," and terms of similar meaning should not be interpreted as limiting the terms described to a given time period or other available term at a given time, but should be read as including conventional, traditional, normal, and standard technology that may be available or known at any time now or in the future. Similarly, the technology referred to in this document is understood or known by a person of ordinary skill in the art, and these technologies include those technologies that are understood or known by a person of ordinary skill in the art now or at any time in the future.

The presence of expanded words and phrases, such as "one or more," "at least," "but not limited to," or other similar phrases in some examples, should not be construed as intending or requiring a narrower case in the absence of such expanded phrases. The use of the term "module" does not imply that the components or functionality described or claimed as part of a module are all configured in a common package. In fact, any or all of the various components in a module, whether control logic or other components, may be combined into a single package or stored separately and may further be distributed among multiple groups or packages or across multiple locations.

In addition, the various embodiments listed herein are described in the form of exemplary block diagrams, flow charts, and other diagrams. It will be apparent to those skilled in the art reading this document that these illustrative embodiments and their various alternatives can be implemented without being limited to the examples shown. For example, the block diagrams and their accompanying descriptions should not be construed as requiring a specific structure or configuration.

Having described various embodiments of the present disclosure in the foregoing, it should be understood that they are disclosed by way of example only and not by way of limitation. Similarly, the various figures depict exemplary structures or configurations of the invention, which are provided to assist in understanding the features and functions encompassed by the invention. The disclosure is not limited to the disclosed exemplary architectures or configurations, but rather the desired features may be implemented using various alternative architectures and configurations. Indeed, one skilled in the art should understand how to implement alternative functional, logical or physical partitioning and configurations to achieve the desired features of the invention. Similarly, multiple different component module names may be applied to different parts, which names are different from those described herein. Furthermore, with reference to the flow charts, operational descriptions, and method claims, the order in which the steps are presented should not require that different embodiments perform the enumerated functions in the same order, unless the context indicates otherwise.

Although various exemplary embodiments and implementations of the present invention have been described above, it should be understood that the various features, aspects, and functions in one or more individual embodiments are not limited to the specific embodiments for which they are described, but may be applied alone or in various combinations to one or more other embodiments of the present disclosure, whether or not such embodiments have been described, and whether or not such features are presented as part of such embodiments. Thus, the breadth and scope of the present application should not be limited by any of the exemplary embodiments described above.

The terms and phrases used in this document and their variations, unless otherwise specifically stated, should be interpreted as open and not restrictive. As an example of the foregoing: the term "including" should be interpreted as meaning "including, but not limited to" or similar; the term "example" is used to provide an illustrative example of the use in the discussion, not an exhaustive or limiting list thereof; the term "one" should be understood as meaning "at least one", "one or more" or similar; adjectives such as "conventional", "traditional", "normal", "standard", "known" and terms of similar meaning should not be interpreted as limiting the terms described to a given time period or other available terms at a given time, but should be interpreted as including conventional, traditional, normal, standard technology that is available or known at any time now or in the future. Similarly, the technology mentioned in this document is understood or known by a person of ordinary skill in the art, and these technologies include those technologies that are understood or known by a person of ordinary skill in the art now or in the future.

The presence of expanded words and phrases, such as "one or more," "at least," "but not limited to," or other similar phrases in some examples, should not be construed as intending or requiring a narrower case in the absence of such expanded phrases. The use of the term "module" does not imply that the components or functionality described or claimed as part of a module are all configured in a common package. In fact, any or all of the various components in a module, whether control logic or other components, may be combined into a single package or stored separately and may further be distributed among multiple groups or packages or across multiple locations.

Furthermore, the various embodiments listed herein are described in the form of exemplary block diagrams, flow charts, and other diagrams. Those skilled in the art will appreciate that these illustrative embodiments and their various alternatives can be implemented without limitation to the examples shown. For example, the block diagrams and accompanying descriptions should not be construed as requiring a specific architecture or configuration.

Claims (16)

1. A method for distributing digital cinema file updates from a server to cinemas via a network, comprising: The server stores an original work playlist, which specifies the order in which a first plurality of track files can be played to present the film, wherein the first plurality of track files include image track files and audio track files corresponding to the video and audio content of a first version of the film; The server stores one or more new track files, which contain only a portion of the modified version of the video or audio content of the film; The server updates the original work playlist, the updated work playlist specifying the order in which a second plurality of track files can be played to present a modified version of the film, wherein the second plurality of track files include at least some of the first plurality of track files corresponding to the video and audio content of the first version of the film and the one or more new track files corresponding to the portion of the video or audio content of the modified version of the film. Through the network, requests from the cinema for one or more new track files and updated playlists are received; In response to receiving the request from the cinema: The cinema is certified; The server determines, by querying a database of recent playlists for the cinema corresponding to the presentation of the film, which version of the playlist corresponding to the presentation of the film was previously sent to the cinema; and The updated playlist and one or more new track files are sent from the server to the cinema via the network; and After sending the updated playlist and the one or more new track files, the records in the database are updated to record the association of the updated playlist and the second or more track files with the cinema. 2. The method of claim 1, wherein sending the updated playlist and the one or more new trajectory files is performed only when the server determines that the updated playlist is used in a region corresponding to the cinema. 3. The method of claim 1, wherein the server performs the determining step and the sending step for multiple cinemas. 4. The method of claim 1, wherein the content of the one or more new trajectory files is a scene of a modified version of the video. 5. The method of claim 1, wherein the content of the one or more new trajectory files is a foreign language audio version of the film. 6. A method for use in a cinema, comprising: A memory located in the cinema stores a playlist of original works, the playlist specifying the order in which first plurality of track files can be played to present the film, wherein the first plurality of track files include image track files and audio track files corresponding to the video and audio content of a first version of the film; The cinema sends a request to a server via a network for one or more new track files and an updated playlist of works, the updated playlist specifying the order in which the second or more track files can be played to present a modified version of the film, wherein the second or more track files include at least some of the first or more track files corresponding to the video and audio content of the first version of the film and the one or more new track files, wherein the one or more new track files include only a portion of the video or audio content of the modified version of the film; The cinema receives the updated playlist of works and one or more new track files; The one or more new trajectory files are stored in a memory located in the cinema; and Update the original playlist of works in the cinema with the updated playlist of works; The memory includes copies of the second plurality of trajectory files. 7. A system for use in a cinema, comprising: The server is configured as follows: Store an original work playlist, the original work playlist specifying the order in which first plurality of track files can be played to present the film, wherein the first plurality of track files include image track files and audio track files corresponding to the video and audio content of a first version of the film; Store one or more new track files, wherein the one or more new track files comprise only a portion of the modified version of the video or audio content of the film; The original playlist is updated, and the updated playlist specifies the order in which a second plurality of track files can be played to present a modified version of the film, wherein the second plurality of track files include at least some of the first plurality of track files corresponding to the video and audio content of the first version of the film and the one or more new track files corresponding to the portion of the video or audio content of the modified version of the film. Receive requests from the cinema via the network for one or more new track files and the updated playlist of works; In response to receiving the request from the cinema: The cinema is certified; By requesting records of the cinema's recent playlists from the database, it is determined which version of the playlist corresponding to the presentation of the film was previously sent to the cinema; and The updated playlist and one or more new trajectory files are sent to the cinema via a communication network; and After sending the updated playlist and the one or more new track files, the database records are updated to associate the updated playlist and the second or more track files with the cinema; and The database, which is communicatively connected to the server, includes records of the cinema's most recently played playlists corresponding to the presentation of the film. 8. The system of claim 7, wherein the server sends the updated playlist and the one or more new track files only when the playlist is used to correspond to the region of the cinema. 9. The system of claim 8, wherein the content of the one or more new trajectory files is a foreign language audio version of the film. 10. A system for a cinema, comprising: The server is configured as follows: Requests for updated track files and updated playlists are received from the cinema via the network. The updated playlists relate to the playback of modified versions of the film. The updated track files include only a portion of the video or audio content of the modified version of the film. In response to receiving a request from the cinema: The cinema is certified; Determine the current playlist and current trajectory file of the cinema, wherein the current playlist specifies the order in which the current trajectory file is played for the first version of the film; and The updated playlist and the updated track file are sent to the cinema over a communication network, wherein the updated playlist specifies the order in which modified versions of the film are played in the updated track file and the current track file; and After sending the updated playlist and the updated trajectory file, the records in the database communicating with the server are updated to record the updated playlist associating it with the cinema for playing the film; and A security module that communicates with the server. 11. The system of claim 10, further comprising a database communicatively connected to the server, wherein the database includes records of the current playlist of films in the cinema. 12. A system for a cinema, comprising: The cinema is configured as follows: Store an original work playlist, the original work playlist specifying the order in which first plurality of track files can be played to present the film, wherein the first plurality of track files include image track files and audio track files corresponding to the video and audio content of a first version of the film; The system sends a request to a server via a network for one or more new track files and an updated playlist of works, the updated playlist specifying the order in which the second or more track files can be played to present a modified version of the film, wherein the second or more track files include at least some of the first or more track files corresponding to the video and audio content of the first version of the film, as well as the one or more new track files, wherein the one or more new track files include only a portion of the video or audio content of the modified version of the film; Receive one or more new track files and the updated playlist of works; Update the original playlist with the updated playlist; and A memory, which is located in the cinema and configured to store one or more new trajectory files. 13. The system of claim 12, wherein storing the one or more new trajectory files includes deleting one of the first plurality of trajectory files, the first plurality of trajectory files including a timecode identical to that of one of the one or more new trajectory files. 14. The system of claim 13, wherein the content of the one or more new trajectory files includes an alternative ending to the video. 15. A method for creating a digital cinema package on a server, comprising: The server receives a request for a component portion of the digital cinema package; The server stores the component portions of the digital cinema package; The sequence is fulfilled by assembling the digital cinema package based on the component portions, the assembled digital cinema package including multiple track files and a playlist of works, the playlist of works specifying how the multiple track files are played to present the film; The digital cinema package is confirmed to comply with the Digital Cinema Initiatives (DCI) standard. Receive requests from cinemas for the confirmed digital cinema package via the network; In response to receiving the request, the confirmed digital cinema package is sent from the server to the cinema via the network; and After sending the confirmed digital cinema package, the records in the database communicating with the server are updated to record the playlist of the works and the multiple track files associated with the cinema. 16. The method of claim 15, further comprising generating an encryption key for the confirmed digital cinema package.