GB2423381A - Distributing electronic content - Google Patents

Abstract

A virtual package for electronic content is disclosed. The virtual package comprises a first level of encryption that includes license information, allowing the author of the content to limit its use and enjoyment to only those who have made proper payment. An additional level of encryption allows splash pages containing branding and purchase information to be associated with the content and displayed once the content is opened on an end user's machine. Additionally, a distribution system is disclosed in which electronic catalogues of content can be maintained for different roles in the distribution chain. This allows branding information to be added to the electronic content for each point of the chain, and allows revenues from a sale to be correctly allotted following a sale.

Description

Method of and System for Distributing Electronic Content This invention

relates to a method and system for distributing electronic content over a network, and in particular to distributing electronic content over the Internet.

Computers are an integral part of modern life, both for work and for recreation. Correspondingly, the use of digital media, such as software applications, games, and music or video data for example, has grown considerably over recent years.

The Internet provides an extremely powerful way of making such digital media, or electronic content, available to end users. Content can be uploaded to a web server, and its availability subsequently advertised by means of a webpage. By selecting an appropriate link on the webpage, an end user may then organise payment, and receive the electronic content as a download.

The AppleTM Itunes website is one such example. The website allows music data in MP3 format to be downloaded to a user's computer, following an appropriate selection from the website, and completion of a payment procedure.

The SonyTM Connect Website is another example for providing music files.

Software, video, and graphic data may also be obtained in this way from other dedicated websites.

From an end user's point of view, sites like the AppleTM ItunesTM, or SonyTM Connect websites provide a secure one-stop location on the Internet where digital media can be obtained, easily and cheaply in comparison to traditional retailers.

However, from the point of view of the author of the digital content, the arrangement is not so satisfactory. Presently, electronic content can only be effectively distributed through a limited number of recognised distributors. If a musician wishes to distribute or sell a digital music file, it is therefore necessary for him to register with an existing online retailer, and provide music in the appropriate format for that retailer to use. Different retailers, such as SonyTM and Apple require different electronic formats. The burden on the author of the content to provide the content in the different required formats is sometimes considerable.

Furthermore, the form of the electronic content that can be downloaded from such on-line retailers is usually just the file itself. Thus, the downloaded file could be used freely, and copied without the author's consent. Additionally, there is nothing to associate the file with the author, apart from perhaps the name of the file, and the author has no control over the presentation of the content and no means to state their copyright on the end user's computer once it has been sold.

It will be appreciated that the present scenario is therefore also unsatisfactory from a marketing point of view. In the world of physical goods for example, the sale of content happens through a distribution chain, whereby the owner of the finished goods can be assured that wherever the goods are ultimately sold, the original packaging and branding is part of the item. In this way, quality and brand loyalty can be maintained.

In the on-line environment, this is not possible. Platform dependency for example means that multiple selling and presentation methods together with different formats are needed for each piece of content depending on the distributor. Additionally, as only the content itself is ultimately delivered, branding or packaging information is lost. By analogy, the online environment is as if the retailer displays an item under a big branded sign, but following a sale, puts an unpackaged, unbranded copy into a plain brown bag, and writes the name and the price on the outside.

Furthermore, existing solutions for selling on-line digital content are idiosyncratic and varied. It depends on the retailer, and the end result is a distinct lack of distribution methods available to the author. Typically, content must be sublicensed to aggregators', with inflexible choices in pricing, payment methods and revenue returns; often recurring subscription fees must be paid for access.

We have therefore appreciated that there is a need for an improved method and system for distributing electronic content over a network.

Summary of the Invention

The invention is defined in the independent claims to which reference should now be made. Advantageous features are set forth in the appendent claims.

A virtual package for electronic content is provided. The virtual package comprises a first level of encryption that includes license information, allowing the author of the content to limit its use and enjoyment to only those who have made proper payment. An additional level of encryption allows splash pages containing branding and purchase information to be associated with the content and displayed once the content is opened on an end user's machine. A splash page' is generally understood to mean the initial page of a website which is presented before the main home page of the site is accessed. Splash pages are typically used to provide eyecatching promotional material to encourage the user to proceed further, or to indicate the software necessary to view the site. In this case, however, the splash page will be understood as a preliminary page from which the electronic content is then accessed. In more general terms, the splash page data may be thought of as author supplied data which is to be associated with the electronic content.

The splash page from which the electronic content is accessed is placed after the electronic content in the encrypted file, and is followed by a file header defining the encrypted file as a data format that is proprietary to the preferred system. This arrangement safeguards the integrity of the downloaded packaged file, as if the splash pages can be accessed to purchase the electronic content, all of the electronic content must have been received in the download. Thus, payment cannot be made for an incomplete product.

Additionally, because the branding and file integrity can be guaranteed by the above, a new type of online distribution system is provided which mimics the physical goods supply chain, and provides all the advantages of such a distribution process in which electronic catalogues of digital content can be maintained for different roles in the distribution chain. This enables branding and merchandising information to be added to the electronic content for each point of the chain, including dynamic pricing and market incentives, and allows revenues from a sale to be correctly allotted to each party in the distribution chain following a sale.

Brief Description of the Drawings

Preferred embodiments of the invention will now be described in more detail, by way of example, and with reference to the drawings in which: Figure 1 is a schematic block diagram of the preferred embodiment of the invention; Figure 2 is a schematic diagram illustrating the digital packaging process employed in the preferred embodiment; Figure 3 is a schematic diagram illustrating the launcher module in the preferred embodiment; Figure 4 is a simplified flow chart illustrating the process of creating a digitally packaged file, obtaining an access license for it, and opening it; Figure 5 is a corresponding architectural diagram showing the flow of information in a computer implementation; Figure 6 is an architectural diagram showing the flow of information in a mobile phone implementation; Figure 7 is a schematic diagram illustrating the architecture and control flow of the preferred system from the point of view of an author; Figure 8 is a schematic diagram illustrating the architecture and control flow of the preferred system from the point of view of a distributor; and Figure 9 is a schematic diagram illustrating the architecture and control flow of the preferred system from the point of view of a retailer;

Detailed Description of the Preferred Embodiments

Overview The preferred system provides virtual packaging for electronic content; the virtual packaging and the electronic content contained within, can be thought of as an electronic product. The virtual packaging for the electronic product allows branding information to be associated with the electronic content, as well as providing additional security for the electronic content within such that it cannot be viewed until it has been properly purchased. In the present implementation, each packaged file can hold unlimited packaged content and up to 1GB of branding and presentation data.

Additionally, the preferred system utilises the virtual packaging to provide a distribution method in which at least authors, distributors and retailers may maintain an on-line catalogue of electronic products, and have their branding information and pricing terms associated with the product wherever it is sold in the distribution chain.

The architecture comprising the preferred embodiment of the invention will now be described with reference to Figure 1. The preferred embodiment comprises a content management facility 2 having a number of dedicated servers, processes and data stores connected to the Internet.

A Web Server 4 provides a dedicated website allowing a user to browse and select from the various services that are provided. An FTP (File Transfer Protocol Standard) Server 6 is also provided to receive uploads of digital content from an author via a FTP connection. The upload of data may be requested and arranged via options presented on the website in a known fashion. Logically connected to the FTP Server, is Content Packager process 8, which is adapted to take the digital content provided by an author and encode it such as to form the electronic product mentioned above. This will be described in more detail later.

The content packager process 8 is in turn logically connected to Content storage device 10, in which details of the packaged electronic content that is available for sale or distribution can be stored. The storage device 10 and web server 4 communicate with each other so that the website can maintain an updated list of electronic products that are available for purchase. A central database 11 is also provided to store customer details and details of packaging runs that have been carried out for those customers.

License Server 12 accesses License database 14 to maintain a file of updated license and client information. In this way, depending on the terms of a license that has been agreed upon, access to the purchased content can be controlled and payment for those involved in a distribution chain can be organised. Payment gateway 16 provides the necessary processes and records to verify that payment for an electronic product has been received, and communicates with the license server 12 to enable access to content.

The system also comprises a launcher 20, which is arranged to be installed in an end user machine 22, such as a personal computer, personal digital assistant, or mobile phone. The launcher communicates with a local browser 24 or content player 26 to effect playback of any downloaded electronic content in a controlled manner.

Separate retailer sites 30 are also provided for by the invention. These sites can register through the website of web server 4 to act as retailers or distributors. In doing so, they may receive a copy of the electronic content that is on sale, may add their own branding, and include a copy of the content information in their own online catalogue. Preferably, the catalogue is maintained on the web server 4 as part of the preferred system. It can however be implemented locally on the machine of a retailer, distributor or author as desired.

The retailer may for example receive and sell a special copy of the electronic content, which includes their own branding information, as well as reflecting the retailer's price. In this case, it may be beneficial for the packaged content and the catalogue to be stored locally.

The operation of the content packager process 8 will be now described in more detail with reference to Figure 2. This figure shows how a piece of digital media or electronic content supplied by an author is provided with a virtual package both protecting the content, and allowing branding information to be associated with it. It will be appreciated that the virtual package may be thought of as analogous to traditional packaging such as a box or a wrapper, possibly within a retailer sealed shrink wrap.

A piece of electronic content is first submitted to the FTP server 6 by an author. The content may include music, video data, software, games, and indeed any electronic file that it is desired to make available for distribution. For example, electronic content representing music could be encoded in the MP3', the real audio', windows media', midi', way', and liquid audio' file format. Video data for example may be encoded in the well known MPEG file format. There are no limitations on the types of file format that can be dealt with in the preferred system. Additionally, the content may be an application itself not needing a viewer, such as a game or a business application.

At the same time as the content 40 is supplied, the author is requested to submit splash page data 42. The splash page data contains graphic and text data for example which will form the virtual wrapper for the electronic content when it is delivered to an end user machine. In the case of a music file, the splash page may for example show artwork associated with the music, photographs of the artist, a sheet of lyrics accompanying the music, as well as any other information or rights notices that the artist or author wishes to associate with the file. For this reason, it is preferred if the splash page data 42 is provided to the FTP server in HTML format, as this allows it to be easily run and displayed within a web browser of an end user machine. Alternatively, a template file may be provided to the author, or retailer for viewing, so that they may submit only the text or graphic data - this being input into the template by the preferred system.

In addition to the splash page data, the author of the electronic content can provide license information to regulate the conditions under which the electronic content can be enjoyed. The license information may specify that the electronic content can be enjoyed for a fixed period of time following payment of a fee. Alternatively, the license may specify that the electronic content can be enjoyed at no charge for a trial period, after which payment must be made to enjoy the electronic content further. The number of licensing conditions and the nature of those conditions are left up to the author of the electronic content to decide. A range of allowable licensing conditions may be presented to the author via the website or via a downloadable file. For example, a template file for the license data can be made available for downloading, which the author can edit to select the correct licensing terms before returning to the content management facility.

Software, such as FLEXnetTM from MacrovisionTM, allows licensing options to be selected and applied to electronic content, giving some protection against unauthorised copying. In this system, a unique license indicator is generated based on the licensing options selected by the author, and the electronic content to be protected. The license identifier and the content are then encrypted as a single file, and the decryption key is stored elsewhere. On making the appropriate payment, the end user receives the decryption key and can enjoy the encrypted content within the terms of the license. Preferably, such software is used to apply license conditions to electronic content as described above.

Once the electronic content 40, the splash page data 42 and the licensing data 44 have been input to the preferred system, the packaging process can begin. First of all, the content is converted into an encrypted form 46 using software such as FLEXnetTM from MacrovisionTM. The encrypted file 46 then contains an encrypted form of the content 40 and also an encrypted license identifier 48 which represents the licensing conditions specified by the author.

Meanwhile, the decryption key for uncoding the encrypted file is stored in the license database along with a reference to the license identifier.

The encrypted file 46 and the splash page data in HTML format 42 are then appended to each other, along with header information 50 to form an unpackaged product file 52. In this context, appending means making the binary representation of the HTML data for the splash page and the binary representation of the encrypted file 46 adjoin one another within a new file, that is to say they are continuous with each other. The header information 50 is used to provide descriptors for the file, and to delimit the data for the splash page information from that of the encrypted file 46 when the file is opened.

The product file 52 is then encrypted again with a different encryption technique, preferably the triple DES (digital encryption standard) technology.

The electronic content 40, the license identifier 48, and the splash page data 42, are then bound up in a single encrypted packaged product file 54. This is then ready for distribution to an end user.

At a later time, a distributor or retailer can request access to the encrypted packaged product file 54 and have their own branding, pricing and licensing information inserted into the product file as part of the distribution chain The header information 50, provided in the tail section of the product file, defines the file to be in a format which is proprietary to the preferred system. As a result, the launcher 20 is required to unencrypt and access the packaged product file 54 on the end user's machine.

The description of the packaging process given above is a generalised discussion. The particular implementation employing the FLEXnet technology of MacrovisionTM, will now be described in more detail below.

Assuming that the electronic content and splash page data have been received from the author, a field sequence is first composed that corresponds to the individual file's properties, including title, description, pricing information, and native format.

Next, the splash page data, including any help' pages are encoded and added to the field sequence. In detail, the content of each file needed for the splash pages is base64-encoded, and this is stored in the field sequence along with a relative filename, so as to maintain any directory hierarchy present in the original splash page data.

Thirdly, the field sequence is encrypted using the triple-DES algorithm with a fixed key, and encapsulated into a proprietary datablock format with a start-marker, end-marker, and header information containing a checksum and an indication that the field sequence has been encrypted.

Next, the new datablock (containing the field sequence) is extracted as a series of bytes. These are reversed in order, so that the datablock is effectively back to front' and these bytes are then appended to the end of the electronic content source file. The datablock in reverse- formation is known as the "file tail".

The source file with the tail is encoded with the FLEXnet' application.

Lastly, another copy of the "file tail" is appended to the end of the FLEXnet encrypted file. The resulting file can then be Triple DES encrypted and renamed with a new extension of.drml' to form a completely packaged electronic product. The file tail is applied twice because of a feature of the FLEXnetTM application which inhibits the reading of anything after the end of the encoded section, once a license has been obtained.

The launcher component will now be described in more detail. In Figure 3, launcher 20 is schematically illustrated as comprising four components, including control module 60, license manager 62, HTTP server 64 and plugin module 66.

Launcher control module 60, is implemented to recognise the downloaded packaged file 54, as a proprietary file type, and to coordinate the necessary operations to present the content to an end user. The License Manager 62 on the other hand, comprises a database of already acquired licenses relating to electronic content. In the preferred embodiment, two types of licenses' are provided. The first license, or preliminary license, is a file containing the decryption key enabling the launcher to access and display the splash pages for the content. From the above description, it will be appreciated that the preliminary license therefore contains a triple DES decryption key. Preferably, a separate preliminary license is generated for each piece of packaged content produced by content packager 8. This provides additional security against unauthorised third parties, as although the protection for a single piece of content may be broken by hacking, the knowledge gained of the encryption key will not enable other electronic content files to be accessed. This ensures the authenticity of the branding and pricing information associated with the packaged content.

Additionally, the preliminary license in the form of the decryption key, safeguards the integrity of the downloaded product. That is, the decryption key will not be operable with the packaged file 54, unless the whole of the packaged file has been received. For this reason, the splash page and file information are provided at the end of the packaged file. This means that if the splash page information has been received and opened with the intermediate license key, all of the electronic content on offer has also been received in the downloaded file.

As a result, it is impossible to make payment via the splash page for incomplete electronic content.

The second license, or access license, comprises the decryption key to access the electronic content itself, and is therefore only obtained when specific payment is made, or when the author of the content has allowed free access. It is this license that is implemented by software such as the FLEXnetTM technology, incorporated in the preferred system.

When a user selects the downloaded package content file 54 to open it, the launcher control module 60, checks with the license manager to determine whether a preliminary license exists in the local database of license manager 62.

If it does, then the decryption key for the packaged file 54 is extracted from the license file, and used to present the splash page information 42 to the user on the display device of the computer. In order to display the splash page, the launcher control module communicates with HTTP server 64, which passes the information to a local web browser 24. Preferably, when presenting the splash page information, the packaged file 54 is never actually completely unencrypted.

Instead, the representation in memory of the end user's computer or mobile terminal, remains in encrypted form, and only the information necessary to present the splash page information is decoded and presented to the browser.

If the license manager does not contain the appropriate for the packaged file 54, then the license manager contacts license server 12 to request the desired preliminary license from the license database 14. Preferably, this is done automatically, so that the end user is not aware of any delay.

If a preliminary license is not available from the license database, this may indicate that the electronic content is no longer to be made available, perhaps at the author's request, and that the relevant license information has been deleted.

The browser 24 on the end user's computer or mobile terminal can now display the splash page information to the user, including any branding information artwork, author information and so on. Additionally, the splash page is used to present licensing or purchase information, on the basis of which the user can decide whether or not to purchase an access license to view or use the electronic content.

The web page provided in the browser 24, may for example, have a "buy now" button provided allowing the user to purchase an access license. Assuming that a license is purchased, an access license containing the decryption key information, allowing the electronic content 40 to be extracted from the encrypted file 46, is downloaded to the license manager 62.

The content is then ready to view, and the launcher control module 60 determines the content file format, such as MP3, midi file, MPEG, an executable and so on, from the encrypted file, and either activates the necessary viewing application, or in the case of an executable file launches it. This may be the web browser 24, activated by means of the HTTP server 64 in conjunction with the control module 60, or alternatively, may be a media player 26, document viewer or some other application appropriate for use of the content, activated by means of plug-in module 66 adapted to communicate with the control module 60. The plug-in modules 66 needed to communicate with the media player application available on an end user's machine can be downloaded as required either automatically, or on request, from the web server 4.

The control module 60 then passes the unencrypted content 40 in real time to the relevant viewing application, allowing the user to view it. Preferably, in all this time, the content as a whole remains in encrypted form 46 within the encrypted packaged file 54. As a result, the end user is never allowed access to unencrypted electronic content, and the author can maintain control of his right to license the content appropriately. Thus, if the license period is only for a limited period of time, once that time has expired, the control module 60 can request that the user register again for a license.

The operation of the preferred system, in particular the licensing and payment control method, will now be described in more detail with reference to Figure 4. Figure 4 shows a high level flow chart illustrating various processes undertaken in order to generate a piece of packaged electronic content 54, and provide this to a user while exercising license and product control. First of all, in step SI 0, the author submits their finished digital content, such as a movie, a music track, a word document etc., on line to the FTP server 6 of the preferred system, together with a batch control file provided in steps S12. The batch control file contains processing information, branding graphics and text, and product metadata such as licensing and pricing information. The author may submit the batch file in step S12, for example, by accessing the website of the web server 4 and being taken through a series of links and web pages.

Alternatively, the batch control file may be provided to an author in advance on request from the web server 4 in a template form, so that this can be filled in and returned with the finished digital content.

Furthermore, via the website, an author can set up their own house style or template for their splash pages, into which the packaging process 8 can insert specific information content items. This may allow the packaging of a large number of closely related electronic content files to be performed automatically.

Once received, the content submission is checked and validated by the content packager 8 in step S14, and any errors are reported to the customer. In particular, a series of checks are made against the control file and the content to ensure that: a) the batch control file has a unique identifier, that can be matched to a submission directory for the user; b) each content item is referenced in the control file and vice versa; c) valid prices and license terms have been set; d) the author or customer ID is valid for the batch, matching that of a registered author or customer ID in the client database; e) the splash page referenced in the batch file exists for the author; if a template stored on the preferred system is being used, and the batch file contains only the raw graphics and text; f) appropriate insertion fields in the splash page for brand content and metadata information exist for the branding information that has been submitted. It will be appreciated that the last two checks relate to the situation

when an author submits only raw text and graphics for a splash page template stored by the preferred system. They are not therefore necessary when the author submits a completed splash page template containing the branding data in the first instance.

Once the batch is determined to be clear of errors, the content packager creates the splash page for each content item, and in step S16 provides a facility for the author to check and verify the splash page with the inserted data for each content file before the encrypted file is created. This is useful for large content files or batches.

If the author indicates that the splash pages are acceptable, then the content packager encrypts the splash pages and content, in encoding step S18, to form the packaged content 54. In doing so, the decryption key corresponding to the license specified by the author is generated and written via the license server 12 to the license database 14. The packaged content is then stored in content storage device 10, and the details of the packaging process and electronic product are written to central database 11. This is shown in Step S20.

The details in the central database include at least a unique identifier for the content, a unique identifier referencing the decryption key in the license database, as well as indicators for the author, and any distributors and retailers for example. It will be appreciated that the same unique identifier for the license that is stored with the decryption key in the database is also written into the encrypted file 46.

The license database also contains a customer database dedicated to maintaining customer information, such as name and address, credentials, account numbers, and so on. This information is used whenever a sale is made to organise payment to the parties involved in the sale.

The packaged product is then ready for distribution or sale, and the author is provided with a link to the appropriate location in the content storage device from which the packaged product can be downloaded. Once downloaded, the author can use and distribute the packaged product as they see fit. A copy of the packaged content may however preserved in the content storage device 10.

The electronic content could be made available over the Internet, or by email for example. This involves publishing a link to the location where a copy of the packaged electronic content is stored. The link may be provided on a web page or catalogue of an author, distributor or retailer for example, and may therefore point to a location on the author's or retailer's machine where the electronic content is stored. The preferred system provides the necessary services to support author, retailer and distribution catalogues as will be described in more detail later.

In conjunction with Figure 4, reference should now also be made to Figure 5, which shows the flow of information at an end user machine. When an end user clicks on the link to the electronic content, the packaged piece of content 54 is downloaded to their machine. In this case the end user is assumed to have viewed the link on the website of a retailer 30; and to have received the packaged content from the retailer acting for the author. Assuming that the end user has the launcher software 20 installed on their machine, the launcher checks to see whether the license manager 62 contains the appropriate preliminary license for the content. If not, then this is obtained in the manner described above with reference to Figure 3. Once the license manager has a copy of the appropriate preliminary license, the splash pages encoded with the content may then be automatically opened in step 824, and presented to the end user via their web browser 24. This allows a branded screen page to be launched, containing any product information pricing and promotional materials together with the owner's and retailer's branding.

The end user can then view the branding and author information and decide whether or not they are interested in purchasing the electronic content. If they are interested, functions are provided in the splash page in order to arrange payment and organise the necessary access license. This may take the form of a link, or preferably, a button marked "buy now". The information displayed may list the different prices and different licenses that are available, such as different license periods, or different types of usage.

When the buy now' button is clicked, in step S26, the browser of the end user downloads further web pages from web server 4 with instruction and choices of payment methods such as a credit card, premium rate telephone line, premium SMS connection, electronic wallet and so on. In known fashion, the end user can then select their preferred means of payment and complete the payment process via the appropriate third party payment facilities 18.

For example, the end user could input their credit card or other payment details into empty fields on the blank form and submit them to the third party payment facility 18. Payment facility 18 possesses the necessary functionality to process the payment details, such as contacting the credit card company with which the end user is registered, and organise the payment from the end user to the payment gateway 16 of the preferred system. The payment gateway stores details of any payment received and based on the information in the customer database, can organise distribution of the payment to the author, and any other party in the distribution chain. Instead of payment via a credit card, payment could also be achieved through a dedicated premium rate phone line for

example.

Simultaneously, an instruction is sent to license server 12 that purchase of the access license for the electronic content is being organised. The license server 12 then periodically polls the payment gateway 16 in step S30 to determine whether or not payment for the electronic content license has completed.

When the payment gateway 16 confirms that payment has successfully been made, the license server consults license database 14 using the license identifier of the electronic content in order to read the decryption key for the license specified by the end user. The decryption key is then transmitted in step S32 to the end users machine for local storage as a license file. Additionally, the license information is written into the customer database as a security measure against loss of the license file.

The launcher control module 60 in the launcher 20 detects that the license file has been received, and updates the splash page to show a "launch" option.

Selecting this option causes the launcher control module 60 to retrieve the decryption key from the license file in the license manager. The decryption key is then used to read the electronic content to the browser or to the relevant content player for viewing by the end user in step S34. During this time, the electronic content file remains encrypted in the packaged file 54.

As noted above, the first time the packaged file is selected by the end user, a preliminary license is requested from the license manager to allow opening of the splash pages. This arrangement is preferred as it enables the author of the content the flexibility to specify particular promotions in relation to the content. For example, an author may specify that the first 1000 people to download the content may be entitled to a free access license in order to generate interest, thereby encouraging as many people as possible view the splash pages.

The description of the system architecture above has assumed that the end user is accessing the preferred system using a desktop or portable personal computer or personal digital assistant. However, the preferred system may also be accessed via any internet enabled mobile device such as a mobile phone, personal digital assistant or set top box. In this case, the implementation of the architecture is slightly different.

Figure 6 shows the implementation of the launcher in a mobile phone system 70. Instead of providing the launcher in the mobile phone, the functionalities of the launcher are provided by a virtual launcher 20' provided on a server of the content management system 2. A mobile content manager module 72 is provided for implementation on the mobile phone itself to communicate with the virtual launcher 20'. This may be implemented in any suitable language such as C++ in known fashion. The license manager 62 is now also provided as part of the license server 12. This avoids the need to code the license manager in a specific proprietary format for the operating system of each mobile phone. In the computing environment, this problem does not arise as the database can be encoded in a generic format for installation on any server platform such as MicrosoftTM, MacintoshTM, Unix or other flavours of operating system. The mobile content manager may be implemented to display splash page information itself, or to communicate with a web browser of the mobile device to achieve this.

Figure 6 shows what happens when a mobile phone user connects to the web or WAP site of a retailer 30'. In the first instance, web browser 74 in the mobile phone accesses the retailer catalogue 31 allowing the end user to select an instance of packaged electronic content for downloading. If the content manager module 72 is not already installed on the mobile phone, this may also be downloaded from the retailer web or WAP site and installed on the mobile device as a local application.

The Mobile Content Manager 72, when first opened, is arranged to make an HTTP connection over the Internet to the virtual launcher 20' and start a user registration process. This provides a series of questions, which the user of the mobile device answers to uniquely identify the mobile device and his identity.

Once successfully registered, a registered user space 76 is created in the preferred system. Although, the storage space is logically separate to the mobile device, the system is arranged to transmit data from the storage space to the mobile device as explained below. The completion of the registration process can be completed by SMS message if desired.

After a piece of electronic content is selected from the retailer site, it can then be downloaded to the registered user space 76, associated with the virtual launcher 20', provided in the content management system 2. Storage space is provided for each mobile phone user, avoiding the need to store the content locally on the phone itself until payment has been completed.

The mobile content manager 72 then instructs the virtual launcher to deliver from the packaged content in the storage space, the relevant splash pages for display on the mobile device. The splash page data can be delivered to the mobile content manager or directly to the browser. In doing so, the virtual manager 20' communicates with the license server to obtain a copy of the decryption key necessary for accessing the splash pages.

The end user can then decide whether or not to purchase a viewing license for the packaged product. Using the mobile content manager 72 or the web browser 74, a payment option is selected and, payment details are given, then payment can be instructed in the same way as has been described above using payment facility 18 and payment gateway 16. On completion of payment, the license manager module in the license server is provided with an access license in the form of the appropriate decryption key.

The virtual launcher uses the decryption key to access the packaged file, and extracts the accessed electronic content. The type of the mobile device is checked and, if necessary, the packaged content is transformed via a standard format translator for the specific mobile device. This is then reencrypted and combined with the splash page information in a java applet and downloaded by the mobile content manager 72 for playback. In this way, a representation of the packaged file is transmitted to the phone which has a smaller memory footprint than the fully packaged content as would be used on a personal computer. Also, compatibility problems between the content and the systems of the mobile phone are avoided.

Of course, as the user has purchased an access license to the product, he may be provided with the option to download the content to his phone at a later date if he should wish to. Alternatively, he may request via the mobile phone, that a copy of the electronic content be transferred to his personal computer for later viewing.

It will be appreciated that the arrangement described above for mobile phones may be used with various different technologies where it is advantageous not to download the entire electronic product file in the first instance because of limited memory resources for example. Such technologies include, games consoles, set-top boxes, and music players.

Interaction and Distribution Roles In addition to the Content Packaging and Distribution Architecture described above, the preferred system also provides a number of on line services to support the commercial aspects of marketing and supplying content.

Specifically, the Web Server 4 provides an interactive web site through which users can register in order to perform one or more roles provided for by the marketing system. The following roles are envisaged: Visitor: this role describes a person who is just browsing the website out of interest, or who is seeking information; Author or content owner: this role describes an individual or organisation who supplies original electronic content to the website for packaging and sale; Distributor: this role describes an individual or organisation who maintains a catalogue of electronic content for distribution to retailers or other distributors; a distributor registers for access to an author's catalogue, or other distributor's catalogue of electronic content; Retailer: this role describes an individual or organisation who provides services, such as a website or catalogue, for selling electronic content to end users; the retailer registers to sell their own content or for access to an author's catalogue, or a distributor's catalogue of electronic content; Affiliate: this role describes an individual or organisation associated with a retailer to market content from the retailer's catalogue or website by referral means to earn a commission on any referred sales; End user: this role describes a person or organisation that downloads or otherwise receives a customer's content via a retailer or affiliate, and who typically pays for access to that content.

It will be appreciated that these roles mirror those in the world of physical goods. The set-up of the marketing services in the preferred system is arranged to allow the creation of a distribution chain for packaged electronic content, in which wherever the goods are ultimately sold, the original packaging and branding is part of the item. In this way, quality and brand loyalty can be maintained.

The interaction of each role with the services provided by the preferred system will now be described in more detail, building on the discussion that has gone before.

Referring now to Figure 7, in a typical scenario, the author having a machine 80, such as a personal computer, uses the preferred system 82 to produce a "virtual package" with a set presentation and branding.

The author stores raw electronic content and metadata including basic price and license terms, like a recommended retail price label on a physical item, in storage location 84 on their machine. Additionally, the author's branding templates and support files, such as splash page templates, are stored in storage location 86 on their machine. Data from these locations is then provided to the preferred system 82 via a secure local FTP client 88, and secure FTP server 90, and stored in raw content data storage 92 and branding database 94.

The Content packager 96 produces the packaged electronic content 54 in the manner described in the earlier section, based on the author's raw content and branding information stored in storage device and database 92 and 94. The packaged content is returned to the packaged content storage device 98, and subsequently the author can collect the packaged content via FTP server 90, and client 88. The packaged content can then be stored on the author's machine in packaged content storage device 100 for distribution by the author to individuals or organisations who may wish to purchase it.

In order to use the packaging service, the author is required to first register as a customer, by providing details such as name and address, and bank information. These may be submitted by local email client 102, or local web server 104, which communicate with a respective email server 106 and web server 108 of the preferred system. Having this information, a checking facility, provided by the web server, validates the information, using postal services information or a credit checking agency for example, and then stores the information for review by representatives of the content management system 2 who may then accept or refuse the application. If a successful application is made, the author's details are stored in the customer database part of the license database for future reference.

In addition to the raw content and branding data stored in storage device 92 and database 94, details of the packaging process are stored a central database 110 indicating uniquely the packaged product produced for the author.

As the author's details are kept in the customer database in the license server, any proceeds made to the payment gateway 16, which result from sale of the author's packaged content can be tracked, and payment made to the author's account.

Alternatively, or in addition to the direct sale method mentioned above, the author can choose to make the content available for sale through a distribution process provided by the preferred system. This relies on the production of a content catalogue for the author, and for any distributors or retailers.

In setting up an online catalogue, retailers may browse their lists of packaged content stored in database 98, using the links provided on web server 4. A special promotional version of the content may be produced by the author, or automatically by the preferred system, so that at least a portion of the electronic content can be played back without having to purchase a license. Alternatively, distributors or authors may be allowed to playback the raw electronic content in the storage device 92, and view the splash page information in database 94.

Preferably, this is done through a dedicated web application which presents the content to the distributors in a suitable catalogue format so that they may choose whether to list the content in their own catalogues or not, but such that the actual content is kept securely in the databases.

If a retailer, chooses to list the electronic content in his catalogue, for example, then retailer branding information can be combined with that of the author to produce a retailer branded version of the author's content, as is possible with putting stickers on physical goods. This may be produced from the raw data stored in databases 92 and 94, or alternatively by recoding the packaged author content to include the retailer specific information. More will be described in this regard later.

Like for the author, a retailer or distributor must first register with the content management system in order to be able to retail electronic content. As is known in the art, they are taken through a number of web forms in which they are requested to provide information such as names, address and financial details.

Having submitted the forms, a checking facility, provided by the web server, validates the information, using postal services information or a credit checking agency for example, and then stores it for review by representatives of the content management system 2 who may then accept or refuse the application.

Any successfully registered distributor or retailer information is stored in the customer database for future reference.

Referring now to Figure 8, the architecture and operation of the system from the point of view of a distributor will now be explained.

Once registered, the distributor can access the services of the preferred system through a local web browser 120 installed on their machine 122. The web browser communicates with the web server 108 to access author or distributor catalogues for which the distributor is registered, as well as handle any necessary registration or administration processes.

Via the web server 108, the distributor may browse the author's catalogue, and select electronic content to distribute. In selecting a piece of electronic content, the distributor may use a facility provided in the catalogue application to make an application and register himself as distributor for the content. The distributor enters an offer of a margin and stores it for review by the author or other distributor. If the application is acceptable, but not the margin, the author or other distributor can offer an alternative margin for consideration by the applicant distributor. This negotiation process may be done on-line through web forms, by email, or both.

Once a margin is agreed, the distributor is signed-up and the web server 4, stores a reference to the distributor in the central database 110 and customer database, and provides access for the content and splash page information to be displayed in the catalogue of the distributor. A link to the electronic content in the packaged author's content storage device 100 is also provided by the author and inserted into the central database 110 as part of the acceptance of the distributor for the content. In doing so, the distributor is not allowed an opportunity to download the raw data, merely to display it in a restricted form for promotional purposes. The price of the electronic content if purchased from the distributor is also indicated in his catalogue based on the margin specified by the distributor in the registration process.

It will be appreciated that the distributor's catalogue is preferably provided by means of a dedicated web application in the same way as the author catalogue.

The distributor may also use email client 124 to communicate with the email server of the preferred system. In this way instructions and reports may be passed between the distributor and the preferred system.

Additionally, distributors may register with other distributors and select content from a distributor catalogue in the same way, thereby becoming a registered sub-distributor with that distributor.

Referring now to Figure 9, the architecture and operation of the preferred system will now be described from the point of view of a retailer.

A retailer acts as a sales point where end users can purchase a copy of the electronic content. Additionally, a retailer may provide facilities to download the relevant launcher software to allow content to be used on an end user machine. Referring to the examples in the introduction to this application, it is envisaged that companies like SonyTM and AppleTM could register as retailers to sell electronic content like music or video files. In order to make this commercially attractive, the preferred system therefore allows the retailers to add their own branding and price margin to the product, with the approval of the author and/or distributor.

Figure 9 therefore shows a retailer's machine 130, having a database 132 for branding information and support files, such as templates. These can be transmitted to the preferred system by local FTP Client 134. FTP Server 90 receives the branding files and stores them in retailer branding database 136.

The author and distributor catalogues contain a link to the packaged content in the content storage devices 98 or 100. Thus, if the retailer selects the link from a catalogue he may download a copy of the content for viewing and inclusion in his catalogue or website for promotional purposes. The retailer may therefore receive a promotional copy of the electronic content with special access license conditions that allow the electronic content to be sampled or viewed for a limited period, if the author has provided this link to the central database 110.

Examples of a promotional content may include providing only the first minute of a music track, or say allowing the whole music track to be heard for say a period of one week.

Using functionality provided in the catalogue or in the packaged content itself, the retailer may then choose to take that packaged electronic content onto his catalogue. In doing so, a command is sent to the content packager 96 to retrieve the relevant packaged content file from the content storage devices 98 or 100, and repackage it to include the retailer's branding and price information obtained from database 136. At this stage, the author's branding information is preserved and the retailer's branding information added to the splash page at an appropriate location. The pricing information in the repackaged content and in the central database 110 now however reflects the margins of the distribution chain and retailer. These margins may be specified by the distributor or retailer when selecting content to put on their catalogue, or may be given once when they initially sign up.

The repackaged content may then be produced by unencypting the packaged file by retrieving the requisite key from the license server, and reencrypting it once the necessary updates to the splash page information have been written to the product.

The repackaged files are stored in the content storage device 98.

Subsequently, the retailer can collect the repackaged content via FTP server 90 and FTP client 134 to place on his website, and a new link to the repackaged product be put in the customer database, and passed to the retailer to advertise in his catalogue. Additionally, an entry is recorded in the central database listing the retailer endorsed content, and identifying the author, distributor chain and retailer for payment purposes.

Thus, if an end user selects the retailer endorsed content from the retailer's catalogue or website, and makes payment through the payment gateway, the license server can consult the central database to determine what pricing structure exists, and who requires payment. Any payments that are to be made, can be arranged by consulting the name, address and financial details stored in the customer database. The repackaged content could also be sent direct to the end user by e-mail or other means.

It will be appreciated that the author content or retailer endorsed electronic content could be made available for sale over the network in almost any way. The content could also be presented to end users by websites, banners e-mail marketing, all inviting them to download the content from the relevant site.

The only information any such invitations would need to contain is the URL link to the retailer endorsed content stored either locally or in the central database.

To encourage marketing, the preferred system therefore provides the ability to register as an affiliate of a retailer. An affiliate applies to a retailer to market the electronic content, in a similar way to the application process for retailers or distributors described above. If the retailer accepts the application, the affiliate is signed up as an authorised affiliate and details stored in the client database. Each sale made by the affiliate may then entitle him to benefits such as remuneration, or retailer specific bonuses.

Compared to the physical goods market, the movement of goods and money is different in the preferred system at least the following ways: i) The content does not need to move during distribution until it has been listed on a retailer's website. At that point, the retailer downloads the content from the author or distributor catalogue via the author's or distributor'scatalogue or uses a link to the author's catalogue to fulfil an order direct to the end- user.

ii) Distributors and retailers do not pay for any content. Instead the content management service collects the money from the end-consumer and distributes it back to the content owner and/or distributors and retailers as required.

Although, the relevant content and branding files have been described as transmitted to the preferred system by means of a web server, it will be appreciated that they could also be received by other delivery methods, such as by mailing of data cassettes, disk, or solid state memory devices. Additionally, although the downloading of electronic content and decryption keys has been described, it will be appreciated that distribution could occur by postal services, once a selection is made from a catalogue. This would be useful when large quantities of data are being handled.

Although in the preferred system, encryption is used to implement the product file as a secure proprietary format, it will be appreciated all that is required is that the packaged product file 54 be protected, and that a license key be necessary to gain access to the packaged product file. The license key could for example be a password, or other user identifier for example. The content could also be protected merely by placing it in a proprietary format and requiring a dedicated application or hardware to play it.

Preferred embodiments of the invention have been described by way of example. These are not intended to be limiting and modifications will be apparent to those skilled in the art within the scope of the invention as defined in the claims.

Claims (51)

1. Claims 1. A method of distributing electronic content for playback on the

   machine of an end user, comprising: receiving an instance of electronic content; receiving splash page data to be associated with the electronic content; combining the electronic content and the splash page in a product file, wherein the product file is arranged such that on opening, the splash page data is presented to the end user before the electronic content is accessed; protecting the product file, such that it cannot be opened without a first license key; the protected product file forming a packaged product file; and making the packaged product file and first license key available for transmission to a user; wherein the end user can request a copy of the packaged product file, and the first license key to open the packaged product file on their machine.
2. 2. The method of claim 1, wherein protecting the product file comprises encrypting the product file, and wherein the license key is a decryption key for the protected file.
3. 3. The method of claim I or 2, comprising combining the electronic content and the splash page data in the product file, such that the splash page data is arranged after the electronic content in the file.
4. 4. The method of claim 3, comprising including a tail section after the splash page data defining the product file as a proprietary data type.
5. 5. The method of any preceding claim, comprising providing a launcher for execution on the machine of the end user, the launcher being arranged to present the splash page data, and the electronic content to the end user.
6. 6. The method of claim 4, wherein the launcher is arranged to use the first license key to access the product file while preserving it in protected form, only that part of the file immediately needed for display of the splash page or electronic content being extracted for display.
7. 7. The method of claim 6, comprising: storing the first license key for the packaged product file on a storage device; and wherein the launcher is arranged, such that when the end user first selects the product file for display, the launcher requests the first license key from the storage device, such that the packaged product file can be accessed.
8. 8. The method of any preceding claim, comprising: receiving license data specifying license terms that restrict the use of the electronic content on the end user's machine; combining the electronic content with an electronic implementation of the license terms, such that playback of the electronic content on the machine of the end user is subject to the terms of the license; wherein the combined electronic content and electronic implementation of the license terms, are subsequently combined with the splash page data and encrypted.
9. 9. The method of claim 8, wherein the combining step comprises encrypting the electronic content and the electronic implementation of the license terms in an encrypted file, wherein the encrypted file is subsequently combined with the splash page data and encrypted.
10. 10. The method of claim 8 or 9, comprising: storing the license data in a storage device; and allocating the license data a unique identifier, and storing the unique identifier as a reference to the license data; combining the electronic content with the unique identifier.
11. 11. The method of any preceding claim, comprising: receiving retailer ID information from an individual or organisation who wishes to register as a retailer to retail a packaged product file; storing the retailer ID information; receiving retailer splash page data from the retailer; receiving from the retailer a selection of a packaged product file which they wish to sell; and combining the retailer splash page data with the splash page data already associated with the electronic content in the packaged product file to produce a retailer packaged product file.
12. 12. The method of claim 11 comprising: maintaining a catalogue for the retailer, showing the packaged product file, and pricing information for that packaged product file, and providing access to the catalogue to end users for purchase of the packaged product file.
13. 13. The method of claim 11 or 12, comprising; receiving distributor ID from an individual or organisation, including distributor pricing information, who wishes to register as a distributor of a packaged product file; storing the distributor ID information; maintaining a catalogue for the distributor, showing the packaged product file, and pricing information for that packaged product file; and providing access to the catalogue to other retailers or distributors.
14. 14. The method of any preceding claim, wherein the splash page data comprises branding information and/or price information.
15. 15. The method of any preceding claim, wherein the machine of the end user is a computer.
16. 16. The method of any of claims I to 14, wherein the machine of the end user is a mobile device.
17. 17. The method of claim 16, comprising: providing storage space for packaged product files on a server logically separate from the mobile device, and downloading only the splash page data to a display device of the mobile device.
18. 18. The method of claim 17, comprising: receiving purchase instructions from the user of the mobile device; and downloading the electronic content to the mobile device for playback.
19. 19. The method of claim 18, comprising: determining the type of the mobile device; and converting the electronic content to a compatible format, if it is incompatible with the type of the mobile device, the compatible format being re- encrypted before download.
20. 20. The method of claim 18, comprising converting the electronic content and splash page data into a java applet for download to the mobile device.
21. 21. The method of any preceding claim, wherein the electronic content is one of MP3, real audio', windows media', midi', way', and liquid audio', or MPEG file format.
22. 22. A method of distributing electronic content over a network, comprising: receiving electronic content from an author; encoding the electronic content in a protected file as an electronic product, the protected file requiring payment to be made before the electronic content can be accessed; receiving author payment information, such that on a sale of the electronic product, payment can be made to the author; providing the electronic product to the author for distribution and sale to an end user; receiving payment from an end user who has received the electronic product from an author, and who has decided to pay for the electronic content, and; allocating payment to the author on the basis of the author payment information.
23. 23. A method according to claim 22, comprising: storing the storage location of the electronic product in a database; maintaining a catalogue of electronic products available from the author, as an author catalogue, wherein if an electronic product is selected from the catalogue, the electronic product is retrieved from the storage location for downloading.
24. 24. A method according to claim 22 or 23, comprising receiving registration information from a retailer, the retailer information including retailer payment information, such that on a sale of an electronic product, payment can be made to the retailer; maintaining a catalogue of electronic products available from the retailer, as a retailer catalogue, wherein if an electronic product is selected from the catalogue, the electronic product is retrieved from the storage location for downloading by an end user.

    receiving an indication from a retailer that they wish to add the electronic product of an author to the retailer catalogue; and updating the retailer catalogue on the basis of the indication.
25. 25. The method of claim 24, wherein the indication from the retailer includes retail price information.
26. 26. A method according to claim 24 or 25, comprising receiving registration information from a distributor, the distributor information including distributor payment information, such that on a sale of an electronic product, payment can be made to the distributor; maintaining a catalogue of electronic products available from the distributor, as a distributor catalogue, wherein if an electronic product is selected from the catalogue by a retailer or other distributor, the electronic product can be sampled and added to the catalogue of the retailer or other distributor; receiving an indication from a distributor of an electronic product that they wish to add the electronic product of an author to the distributor catalogue; updating the distributor catalogue on the basis of the indication.
27. 27. A method of distributing electronic content over a computer network; comprising: maintaining a plurality of on-line catalogues listing electronic content that is for sale or distribution, each catalogue being associated with an author of electronic content, a distributor of electronic content, or a retailer of electronic content; maintaining a database specifying for an instance of electronic content a distribution chain from author to retailer; the database listing pricing and payment information for each of the author, distributor and retailer in the chain; allocating, upon sale by a retailer, and receipt of payment by an end user of the electronic content, the payment to the author, distributor or retailer as indicated by the pricing information.
28. 28. Apparatus for distributing electronic content for playback on the machine of an end user, comprising: input means arranged to: receive an instance of electronic content; and receive splash page data to be associated with the electronic content; data processing means arranged to: combine the electronic content and the splash page in a product file, wherein the product file is arranged such that on opening, the splash page data is presented to the end user before the electronic content is accessed; and protect the product file, such that it cannot be opened without a first license key; the protected product file forming a packaged product file; and a server for making the packaged product file and first license key available for transmission to a end user; wherein the end user can request a copy of the packaged product file, and the first license key to open the packaged product file on their machine.
29. 29. The apparatus of claim 1, wherein the data processing means is arranged to protect the product file by encrypting the product file, and wherein the license key is a decryption key for the protected file.
30. 30. The apparatus of claim 29 or 30, wherein the data processing means is arranged to combine the electronic content and the splash page data in the product file, such that the splash page data is arranged after the electronic content in the file.
31. 31. The apparatus of claim 30, wherein the data processing means is arranged to include a tail section after the splash page data defining the product file as a proprietary data type.
32. 32. The apparatus of any of claims 28 to 31, comprising a launcher for execution on the machine of the end user, the launcher being arranged to present the splash page data, and the electronic content to the end user.
33. 33. The apparatus of claim 32, wherein the launcher is arranged to use the first license key to access the product file while preserving it in protected form, only that part of the file immediately needed for display of the splash page or electronic content being extracted for display.
34. 34. The apparatus of claim 33, comprising: a storage device for storing the first license key for the packaged product file for download to an end user; and wherein the launcher is arranged, such that when the end user first selects the product file for display, the launcher requests the first license key from the storage device, such that the packaged product file can be accessed.
35. 35. The apparatus of any of claims 28 to 34, wherein the data processing means is arranged to: receive license data specifying license terms that restrict the use of the electronic content on the end user's machine; combine the electronic content with an electronic implementation of the license terms, such that playback of the electronic content on the machine of the end user is subject to the terms of the license; wherein the combined electronic content and electronic implementation of the license terms, are subsequently combined with the splash page data and encrypted.
36. 36. The apparatus of claim 35, wherein the data processing means is arranged to encrypt the electronic content and the electronic implementation of the license terms in an encrypted file, wherein the encrypted file is subsequently combined with the splash page data and encrypted.
37. 37. The apparatus of claim 35 or 36, comprising: a storage device for storing the license data; and wherein the data processing means is arranged to: allocate the license data a unique identifier; store the unique identifier as a reference to the license data; and combine the electronic content with the unique identifier.
38. 38. The apparatus of any of claims 28 to 37, comprising a storage device arranged to: receive retailer ID information from an individual or organisation who wishes to register as a retailer to retail a packaged product file; and store the retailer ID information; and wherein the data processing means is arranged to: receive retailer splash page data from the retailer; receive from the retailer a selection of a packaged product file which they wish to sell; and combine the retailer splash page data with the splash page data already associated with the electronic content in the packaged product file to produce a retailer packaged product file.
39. 39. The apparatus of claim 38, comprising: means for maintaining a catalogue for the retailer, the catalogue showing the packaged product file, and pricing information for that packaged product file, and, wherein end users can access the catalogue to purchase a the packaged product file.
40. 40. The apparatus of claim 38 or 39, comprising: a storage device arranged to: receive distributor ID from an individual or organisation, including distributor pricing information, who wishes to register as a distributor of a packaged product file; and storing the distributor ID information; and means for maintaining a catalogue for the distributor, the catalogue showing the packaged product file, and pricing information for that packaged product file; and wherein other retailers or distributors can access the catalogue.
41. 41. The apparatus of any of claims 28 to 40, wherein the splash page data comprises branding information and/or price information.
42. 42. The apparatus of any of claims 28 to 41, wherein the machine of the end user is a computer.
43. 43. The apparatus of any of claims 28 to 41, wherein the machine of the end user is a mobile device.
44. 44. The apparatus of claim 43, comprising: storage space for packaged product files on a server logically separate from the mobile device, and a launcher for downloading only the splash page data to a display device of the mobile device.
45. 45. The apparatus of claim 14, wherein the launcher is arranged to: receive purchase instructions from the user of the mobile device; and download the electronic content to the mobile device for playback.
46. 46. The apparatus of claim 45, wherein the launcher is arranged to: determine the type of the mobile device; and convert the electronic content to a compatible format, if it is incompatible with the type of the mobile device; re-encrypt the compatible format before download.
47. 47. The apparatus of claim 46, wherein the launcher is arranged to convert the electronic content and splash page data into a java applet for download to the mobile device.
48. 48. The apparatus of any of claims 28 to 47, wherein the electronic content is one of MP3, real audio', windows media', midi', way', and liquid audio', or MPEG file format.
49. 49. A computer program product having computer code stored therein, which when executed on a computer causes the computer to perform any of the steps of claim 1.
50. 50. A computer program product having computer code stored therein, which when executed on a computer causes the computer to perform any of the steps ofclaim2l.
51. 51. A system for distributing electronic content to a replay device, wherein the electronic content has associated splash page data, and the electronic content and the splash page data are so coded so as to form a single downloadable electronic product, and wherein the splash page data when displayed on the replay device, is arranged to provide text and graphics information relating to the electronic content, as well as providing options for purchase of the electronic content, the system comprising: a retailer site from which electronic products, containing electronic content and splash page data can be downloaded; a replay device comprising: a browser for connecting to a network to request an electronic product from the retailer site; and a content player for playing downloaded content; and a content distribution site having a dedicated storage device arranged to store an electronic product that has been downloaded from the retailer site according to a request made by the browser of the replay device, extract the splash page data, and transmit this to the replay device for display, wherein the electronic content can be obtained from the content distribution if the options for making payment are satisfied.