WO2002007405A2

WO2002007405A2 - Content distribution

Info

Publication number: WO2002007405A2
Application number: PCT/US2001/022249
Authority: WO
Inventors: Les Hill; Sanjeev Datta
Original assignee: Blue Ripple, Inc.
Priority date: 2000-07-17
Filing date: 2001-07-16
Publication date: 2002-01-24
Also published as: AU2001276920A1; WO2002007405A3

Abstract

Content can be distributed from one or more content producers to one or more content subscribers by receiving content from at least one of the producers, and associating at least one content profile with the received content. A subscriber profile is associated with each of the subscribers. Based on at least one content profile and at least one subscriber profile, a subset of the received content is identified and provided to at least one of the subscribers. The identified subset is then communicated to the at least one of the subscribers.

Description

CONTENT DISTRIBUTION Priority Information

This application claims priority to U.S. Serial No. 09/617,897 filed on July 17, 2000.

Technical Field

This invention relates to digital content distribution, and more particularly to methods and systems for distributing content over computer networks from content providers to content subscribers.

Background Information

Content is provided from a single source, referred to as a content provider or content producer, to one or more receivers, referred to as content subscribers. A newspaper is an example of a content provider, in that the newspaper provides the same content (the text and graphics in the newspaper) to each of its various subscribers. This is a typical content distribution model, even on the Internet, where a content provider typically makes one or more documents available on a web page for others to download. A document available on a web page, for example, can be accessed and downloaded by computers worldwide. Even content that is provided only to paid or otherwise registered subscribers is typically provided so that the same content is provided to all subscribers who present valid subscription authentication information, although some web sites offer web content that is at least somewhat customized to a reader's preferences.

A newspaper is also an example of a content subscriber, in that newspapers subscribe to content providers for news (for example, Associated Press), cartoon syndications, and so on. The newspaper includes this received content in the newspaper, which is then offered (as a whole newspaper) to newspaper subscribers. This is also a typical content distribution model, even over the Internet, as web site publishers purchase, are given, or otherwise obtain content from others to include on a web site. Also, typically, a subscriber, like a newspaper, subscribes to all of the content offered by each content provider, because it is administratively difficult for a content provider to customize its content for each subscriber. Also, typically, each content provider communicates with its subscribers directly, with the result that the protocols and procedures to be used to communicate content from a content provider to a content subscriber are different for each provider/subscriber combination. Both the provider and the subscriber therefore often incur a significant initial overhead cost associated with negotiating and implementing such protocols and procedures. Over the Internet, the process of providing multiple content files to users is typically accomplished by a manual process. For example, several links, each a link to a single document, can be provided on a web page. A subscriber then manually selects and downloads each file. Alternatively, a collection of content files can be provided in a single directory or group of directories, and access to that directory is provided using file transfer protocol (ftp) or other file- sharing technologies, which allow for the transfer of all files in a single directory or group of directories. A collection of content files can be combined into a single archive file, such as ZIP or TAR format file, and the archive file transferred to the subscriber's computer. When downloaded to a receiver's computer, the collection of content files is extracted from the archive file, either manually or automatically using a script or program. Software developers have developed variations of this archive file extraction mechanism to try to simplify installation of personal computer software programs, which carf iiicmde multiple files that require placement in specific directories.

Summary of the Invention

The invention relates to a content hub that is an intermediary between content producers and content subscribers. The hub makes it possible for content producers to provide variations and subsets of their content to different subscribers. As an intermediary, the hub facilitates the transfer of content from multiple content producers to multiple subscribers. The hub provides a mechanism for the efficient transfer of multiple files.

In general, in one aspect, the invention features a method of customized distribution of content from one or more content producers to one or more content subscribers. The method includes receiving content from at least one of the producers, and associating at least one content profile with the received content. The method includes associating a subscriber profile with each of the subscribers. The method includes identifying based on at least one content profile and at least one subscriber profile a subset of the received content that is to be provided to at least one of the subscribers. The method includes communicating the identified subset to the at least one of the subscribers based on this determination. Embodiments of this aspect of the invention include the following features.

In one embodiment, the content profile includes a metadata description of the content. In one embodiment, the subscriber profile may include a metadata description of asset selection criteria of assets to be provided to a subscriber and may include a metadata description of the subscriber. In another embodiment, the subscriber profile includes a list of packages to be provided to the subscriber. In another embodiment, the subscriber profile includes customer categorization information.

In one embodiment, content is received via a network connection. In one such embodiment, the network connection is an Internet network connection. In one embodiment, content is received via a network connection from an agent running on a computer of the producer. In one embodiment, the agent is an applet. In one embodiment, before receiving the producer's content via the network connection, the method includes initiating the network connection to a computer designated by the producer, and requesting the producer's content via the network connection. In another embodiment, before receiving the producer's content via the network connection, the method includes receiving a network connection request from the producer's computer, and opening a network connection in response to the network connection request. In one embodiment, the method also includes the step of transmitting to the producer notice of successful communication of the subset to the subscriber.

In one embodiment, content is communicated to a subscriber via a network connection. In one such embodiment, the network connection is an Internet network connection. In one embodiment, content is communicated via a network connection to an agent running on a computer of the subscriber. In one embodiment, the agent is an applet. In one embodiment, before communicating content via the network connection, the method includes initiating the network connection to a computer designated by the subscriber. In another embodiment, before communicating the subscriber's content via the network connection, the method includes receiving a network connection request from the subscriber's computer, and opening a network connection in response to the network connection request. In one embodiment, the method also includes the step of transmitting to the subscriber notice of successful communication of the subset.

In another embodiment, the method also includes modifying the content profile in response to a request from the producer. In another embodiment, the method also includes modifying the subscriber profile in response to a request from the subscriber. In another embodiment, the method also includes modifying the subscriber profile in response to a request from a producer. In another embodiment, the method includes incorporating the subset in the one or more web pages of the subscriber. In another embodiment, the method includes copying the identified subset of the producer's content and modifying the copy of the identified subset based on the subscriber profile. In another embodiment, the method also includes communicating the modified copies of the subset to the subscriber. In another embodiment, the subset includes all of the received content. In another embodiment, the method also includes the step of associating at least one package, each of the at least one packages having a^ι package profile, with the received content based on the at least one content profile, and associating a subscriber profile with each of the subscribers.

In general, in another aspect, the invention features a hub for customized distribution of content from one or more producers to one or more subscribers. The hub includes a receiver for receiving content from at least one of the producers, a content profile association subsystem for associating at least one content profile with the received content, and a subscriber profile association subsystem for associating a subscriber profile with each of the subscribers. The hub also includes a selection subsystem for identifying based on at least one content profile and at least one subscriber profile a subset of the received content that is to be provided to at least one of the subscribers, and a transmitter for communicating" the identified subset to the at least one of the subscribers. Embodiments of this aspect of the invention include the following features.

In one embodiment, the content profile is a metadata description of the content. In another embodiment, the subscriber profile can include a metadata description of asset selection criteria of assets to be provided to a subscriber and a metadata description of the subscriber. In another embodiment, the subscriber profile is a list of packages to be provided to the subscriber. In another embodiment, the subscriber profile includes customer categorization information for the subscriber.

In one embodiment, the receiver receives content via a network connection. In another embodiment, the receiver receives content via an Internet network connection. In another embodiment, the receiver receives content via a network connection from an agent running on a computer of the producer. In another embodiment, the receiver receives content via a network connection from an agent running on a computer of the producer, wherein said agent is an applet. In another embodiment, the hub also includes a network interface for initiating the network connection to a computer designated by the producer and for requesting the producer's content via the network connection. In another embodiment, the receiver receives a network connection request from the producer's computer and opens a network connection in response to the network connection request. In another embodiment, the transmitter transmits to the producer notice of successful communication of the subset to the subscriber.

In one embodiment, the transmitter communicates content via a network connection. In another embodiment, the transmitter communicates via an Internet network connection. In another embodiment, the transmitter communicates via a network connection to an agent running on a computer of the producer. In another embodiment the agent is an applet. In another embodiment, the hub also includes a network interface for initiating the network connection to a computer designated by the subscriber. In another embodiment, the network interface receives a network connection request from the subscriber's computer and opens a network connection in response to the network connection request. In another embodiment, the transmitter transmits to the subscriber notice of successful communication of the subset to the subscriber.

In another embodiment, the content profile association subsystem modifies the content profile in response to a request from the producer. In another embodiment, the subscriber profile association subsystem modifies the subscriber profile in response to a request from the subscriber. In another embodiment, the subscriber profile association subsystem modifies the subscriber profile in response to a request from a producer. In another embodiment, the subset is incorporated in the one or more web pages of the subscriber. In another embodiment, the hub also includes a customization subsystem for copying the identified subset of the producer's content and modifying the copy of the identified subset based on the subscriber profile. In another embodiment, the transmitter transmits the modified copies of the subset to the subscriber. In another embodiment, the subset includes all of the received content.

In another embodiment, the hub also includes at least one package, each of the at least one package having a package profile, associated with the received content based on the at least one content profile, and wherein the subscriber profile association subsystem associates a subscriber profile with each of the subscribers, the subscriber profile specifying packages to be provided to one or more of the subscribers based on the subscriber profile and at least one package profile.

The foregoing and other objects, aspects, features, and advantages of the invention will become more apparent from the following description and from the claims.

Brief Description of the Drawings

In the drawings, like reference characters generally refer to the same parts throughout the different views. Also, the drawings are not necessarily to scale, emphasis instead generally being placed upon illustrating the principles of the invention.

FIG. 1 is a schematic of a content distribution system including an embodiment of a hub according to the invention.

FIG. 2 is a schematic of an embodiment of a profile according to the invention.

FIG. 3 depicts the relationship of content assets, rules, packages, and subscribers in an embodiment of the invention. FIG. 4 is an example embodiment in which a tool company is a content producer and a retailer is a content subscriber.

FIG. 5 is a block diagram of the web pages presented to a content producer in an embodiment of the invention.

FIG. 6 is a block diagram of the web pages presented to a subscriber in an embodiment of the invention.

FIG. 7 is a block diagram of an embodiment of a method for customized distribution of content according to the invention.

Description

Referring to FIG. 1, a content hub 10 receives one or more content assets C1-C13 (also referred to as content and referred to as assets) from one or more content producers Pl-PN. The hub 10 transmits a subset of the content assets C1-C13, which may include all of the content assets C1-C13 or a portion of the content assets C1-C13, to one or more content subscribers Sl- SM. The hub 10, as an intermediary, enables the efficient transfer (via the hub) of content assets from the one or more producers Pl-PN to the one or more subscribers Sl-SM. The number of content assets C1-C13, producers Pl-PN and subscribers Sl-SM shown in the figure is exemplary, and is not intended to be limiting. Likewise, the hub 10 is shown as a single block in FIG. 1, although the hub 10 may be implemented with one or more components, such as one or more server computers. Each content producer typically has associated with it at least one content asset, and typically there are a plurality of content producers and a plurality of content subscribers.

Content producers Pl-PN and content subscribers Sl-SM typically each have at least one computer, such as a desktop personal computer (PC) or workstation, that is connected or periodically connects to a computer network, such as the Internet. Such computers typically use such operating systems as MICROSOFT WINDOWS NT or GNU/LINUX, but that is not a requirement. The computers communicate with the hub over the Internet both using standard Internet communication protocols and may use other protocols, depending on the networks and the specific implementation. Use of the Internet as a communications medium allows the hub 10 to receive content assets from content producers to communicate those content assets, possibly after some modification, to content subscribers throughout the world.

Generally, the term content assets includes all types of digital content. Content assets may include content in various standard and proprietary formats. As some examples, content assets may include, without limitation, text, marked text, or formatted text in such formats as HTML, XML, MICROSOFT WORD, and the like; graphics files in such formats as JPEG, GIF, TIFF, BMP, and the like; and audio and video files in such formats as MP3, MPEG, REAL AUDIO, REAL VIDEO, and the like. Content producers may also store content assets in databases, such as those sold by ORACLE CORPORATION of Redwood Shores, CA or by MICROSOFT CORPORATION of Redmond, WA. In such a case, the actual data itself, the database files, or some combination may constitute, content assets. For simplicity of discussion, content assets will be considered to be in a standard data file format, such as the file formats above, and will also be referred to as files.

Content producers Pl-PN generally have content assets of their own, or content assets developed by others, or both, to distribute to subscribers. Content producers may be publishers, such as newspaper, magazine, or web site publishers that have text and graphic content to distribute to printers or to web site publishers that wish to repurpose or otherwise use the content assets on their web site. As additional examples, content producers may be multimedia studios that have multimedia content to distribute, software distributors that have executable software programs to distribute, musicians or record companies that have music files to distribute, writers and publishers who have text documents to distribute, and so on. Also, as another example, a content producer may be a business that has product .or product support information to distribute. A content producer may have regular or irregular content updates to distribute to subscribers, or the content producer may distribute a single distribution to provide to subscribers that is not changed, modified, or added to over time.

Content subscribers Sl-SM generally would like to receive content assets from one or more content producers Pl-PN. Content subscribers can be any person or entity that desires to receive content, and may make use of the received content assets in various ways. For example, a subscriber may be a publisher of a newspaper, magazine, or web site that wishes to include the received content in its own publications or web pages. As another example, a subscriber may be a product reseller who intends to distribute the received content with a product. A subscriber may be both a subscriber and a content producer, and may redistribute the received content, on a web site, in printed documents, in a broadcast or public display, or even using the hub. As another example, a subscriber may view, read, play, or otherwise use the content for the subscriber's own use. For example, a subscriber might be a fan of text and graphical works provider by an author, or a fan of audio and video works published by a musical group, or both, that wishes to receive one or more content producers' works for her own enjoyment. A subscriber may desire to receive content changes or updates regularly or irregularly if one or more content producers Pl-PN update or add to their content offerings.

Referring to FIG. 2, in one embodiment, the hub 10 uses a profile 20 to identify content assets, packages of content assets, and subscribers. Generally, a profile includes information describing one or more of the system components. The profile 20 includes metadata, which is a term used in the computer industry to mean data that describes other data. The hub 10 typically uses a plurality of profiles 20, one for each of the content assets, packages, and subscribers.

In one embodiment, the metadata in the profile 20 is in the form of a list of name/value pairs. The name 21 can be any string that exists in the namespace, not including reserved system names, and not allowing duplicates. A value 22 has a type (e.g. string, number, enumeration, date). The value 22 can be any value that is allowed by the type. Each type may have a default value, and also may have one or more special values, for example for indicating that it is empty (i.e. no value has been set). ^<-^••- ^•

Generally, the metadata that is included in the profile is specific to the content asset, package, or subscriber that the profile is associated with, and is specific to the type of content assets provided by the producer and received by the subscriber. For example, if the producer is an investment broker offering information about investments, the profile will include metadata to specify the type of content asset (e.g. text, web page, audio file), and the subject of the content asset (e.g. Vespucci Corporation common stock), and the type of investment (e.g. Common Stock). Examples of other profile metadata include when the content should first be available to subscribers, when the content expires, and descriptions of the possible uses for the content.

Referring to FIG. 3, in an example embodiment, content assets C34, C35, C36 stored in the hub 10 each have an associated content profile 44, 45, 46. Each content profile includes metadata describing the respective content assets C34, C35, C36. The content assets C34, C35, C36 may be selected by one or more named rules 30-33. The named rules specify aggregations of some subset (which may include all) of the content assets on the hub 10. The content assets are selected by named rules based on the rule logic 40 associated with each named rule. The rule logic specifies content profile 44, 45, 46 values. Generally, there are many named rules 30-33 used the hub, and some content assets may be selected by more than one rule 30-33. The figure shows that content assets C34, C35, and C36 are selected by the named rule 30.

A content package 38 can use one or more named rules 30-33 to select content assets C34-C36. A content package 38 is an aggregation of some subset (which may be all) of the content assets chosen by one or more named rules 30-33. The package 38 shown in the figure includes the one named rule 30 shown in detail, and two other named rules 31, 32. A subscriber subscribes to one or more packages, such as package 38. A subscriber 29 has an associated subscriber profile 49, and the subscriber profile includes metadata describing the subscriber 29. The subscriber profile 49 includes information about which packages 38 the subscriber 29 wishes to receive. The subscriber profile 49 may also include the content transfer method and content format preferred by the subscriber. The subscriber profile 49 may also include other information about the subscriber, which will help the producer offer targeted packages to the subscriber. The subscriber profile 49 may include information kept by the hub about the subscriber, and may include information about the subscriber kept by one or more producers. If a subscriber selects the package 38, the content assets C34, C35, C36 selected by the named rules 30, 31, 32 are communicated to the subscriber 29 as appropriate.

Before transfer to the hub, content assets may be stored at the producer in various formats, such as files in the formats described above, as data in a database, or as documents in a content management system, such as those offered by Vignette Corporation of Austin, TX or Open Market Inc. of Burlington, MA. A producer may provide such content assets to the hub 10 in many ways. The producer may provide the assets via a web server or an ftp server, or make them available in another manner over a data communications network, for example via email. The producer may provide the hub 10 with a web URL, ftp address and authentication information, dial-up access information, or similar information that will allow the hub 10 to access the producer's assets.

The hub 10 may access the assets at predetermined time or periodic time interval, or a producer (or a system operator) may manually direct the hub to connect to the producer's computer to receive the assets. In one embodiment, the hub 10 includes a web crawler that can copy an entire web site (or portions of a web site) offered by the producer over the Internet.

In one embodiment, the producer's server communicates the assets to the hub 10 over a computer network. The producer may associate a content profile with one or more assets at the time that the assets are communicated, or may associate a content profile with one or more assets ahead of time, for example by indicating that assets received from a particular file system location are to be associated with a particular content profile. The producer also may transmit an asset to the hub for storage on the hub, and then at a later time associate a content profile with the asset.

In one embodiment, the producer provides instructions to the hub 10 by way of accessing Internet web pages on the hub. The producer provides access information, or other information about the content assets to allow the assets to be received by the hub 10. In one embodiment, the producer specifies files to be received by the hub, aridTprovides content profile metadata to describe the files. In one embodiment, the files are communicated to the hub using file transfer capabilities incorporated into the producer's web browser. In other embodiments, other file communication techniques are used.

In another embodiment, the producer provides information to the hub 10 by describing the assets and their locations on the producer's computer. The hub 10 then provides the producer with an agent, meaning an executable computer program that executes on the producer's computer. The agent identifies the assets according to the information that the producer provided to the hub, and the agent obtains the assets and communicates them to the hub 10. In one embodiment, the agent is customized to the particular computing environment of the producer.

In one embodiment, an agent running on the producer's computer identifies updates or additional assets, for example as files are placed in predetermined directories, or as a database is provided with new information. The agent associates content profile information with the assets, for example, by associating files in the predetermined directories with particular content profile metadata. The agent communicates the assets and the content profile metadata to the hub. In one embodiment, the agent periodically checks for updates, and communicates them to the hub. The use of the agent as just described allows for the automatic transfer of assets from producer to hub 10 (and then on to the subscriber) as new content is generated and without manual intervention by the producer.

Assets may be provided to a subscriber in various formats, and may be communicated from the hub to the subscriber in various ways. In one embodiment, the hub 10 communicates the assets to the subscriber over a computer network. The hub 10 can "push" the content assets to the subscriber using email, ftp or other such protocols. The hub 10 can make the assets available for "pull" by the subscriber, for example by making them available for download from the hub's web server. The hub 10 can store a number of assets in a single archive format, which can be uncompressed by the subscriber.

In one embodiment, the subscriber provides instructions to the hub 10 by way of accessing Internet web pages on the hub 10. The subscriber provides access information, or other information about the desired content assets to allow the assets to be received by the subscriber. In one embodiment, the subscriber specifies files to be received from the hub 10, and provides content profile metadata to describe the files. In another embodiment, the subscriber specifies one or more packages to be received by. the. subscriber. In one embodiment, the files are communicated to the subscriber using the file transfer capabilities of the subscriber's web browser as it is connected to the hub 10.

In another embodiment, the subscriber provides information to the hub 10 describing the desired assets and the desired locations on the subscriber's computer. The hub 10 then provides the subscriber with an agent that can be executed on the subscriber's computer. The agent identifies the assets according to the information that the subscriber provided to the hub 10, and the agent obtains the assets from the hub 10 by communicating with the hub 10. In one embodiment, the agent is customized to the particular computing environment of the subscriber.

In one embodiment, an agent running on the subscriber's computer communicates with the hub 10 and determines that updates or additional assets associated with an offer are available for communication to the subscriber. The agent receives the assets from the hub 10, and places the assets in predetermined directories on the subscriber's computer. In one embodiment, the agent periodically checks for updates, and receives them from the hub 10. The use of the agent as just described allows for the automatic transfer of assets from hub 10 to subscriber without manual intervention by the subscriber.

The content provided by the producer can be customized by the hub for a subscriber. In one embodiment, this is accomplished by the use of style sheets. A style sheet is a file of instructions used to apply character, paragraph, and page layout formats in word processing and text publishing applications. When style sheets are used in web publishing, they contain code to apply semantics such as page layout specifications to a web page. In one embodiment, content is provided to a subscriber such that the look of the content as it is provided to the subscriber is varied, depending on the style sheet chosen by the subscriber. For example, the subscriber can choose whether to receive a report formatted as one-column or two-columns. This may be helpful if the subscriber is using content from multiple producers, and would like the content to be formatted consistently.

Additional operations and transformations can be performed on the content assets by the hub before the content assets are provided to a subscriber. In one embodiment, the hub converts the format of content assets from one format to another ^"based on a subscriber's preferences. For example, in one such embodiment, HTML files are' converted to Wireless Markup Language ("WML") file format before transmission to a subscriber. WML is a lightweight variation of HTML used for wireless devices.

In another embodiment, tracking information, which can be a unique web link or other identifying data, is inserted into the document by the hub to allow the hub or another server to track the usage of the document. For example, if a link with a unique identifier is placed in an HTML file, each time the file is accessed, the link will be accessed, and the server specified in the link will be notified of the access.

In another embodiment, uniform resource locators ("URLs") in the links of HTML files are modified to change the server and/or file locations specified. This can be useful for customization for a particular subscriber. Changes to the URLs can also be used to allow a server selected by the hub to serve some of the web pages identified in those links.

In another embodiment, text content is indexed. The index of the text can be included with the package, and the text index can also be used to select files to be included in a package. In another embodiment, the content is translated and localized for a particular language or geographic region.

Preferably, the hub 10 is used in connection with multiple producers and multiple subscribers. A producer can malce a package available to multiple subscribers. Each subscriber then receives the content assets associated with the package. As described above, the content assets can be customized so that the actual files provided to the subscriber are customized for that subscriber.

Likewise, a subscriber can subscribe to content offers from multiple producers. In this way, a subscriber can receive content assets from multiple sources in a consistent manner. This is useful if the subscriber integrating content assets from multiple subscribers into the subscriber's own documents. The aggregation of content assets in this way allows a subscriber to easily receive packages from multiple producers.

Referring to FIG. 4, in an illustrative example, a tool manufacturer is a content producer that uses a computer 120 having a web browser 10Q to connect to an embodiment of a content hub 110 over a computer network such as the Internet. While the specific example of the tool manufacturer is used here to help describe the invention; it should be clear that the type and amount of content described in this example is intended to be illustrative and is not intended to be limiting.

The tool manufacturer identifies content, in the form of files, data, and so on, to provide to the hub 110. The tool manufacturer uses the web browser as the interface to upload the files to the hub 110. The tool manufacturer also identifies packages of content. The tool manufacturer determines which subscribers should be offered which packages.

When a subscriber, such as a retailer having a computer 121, connects to the hub 110, the subscriber is offered the various packages designated to be offered to that subscriber by the tool manufacturer and other content producers. If the subscriber subscribes to a package, the subscriber receives the content associated with that package. If there are updates or changes to a package, those updates or changed files are identified to the subscriber, and the subscriber can receive those files as. they are made available.

Either of the producer or the subscriber, or both, can have an agent 101, 105 running on their respective computers to connect to the hub 11.0,. and automatically distribute the content from the producer to hub, and from the hub to the subscriber. Once the subscription and agent configuration process is complete, the content can flow automatically from producer to subscriber using the agents 101, 105.

In this example, the tool manufacturer has documents that describe the tool manufacturer's various products. The tool manufacturer's content assets include written descriptions and photographic depictions of the products (i.e. tools) offered by the tool manufacturer. Of course, a tool manufacturer typically would also have other documents, such as user manuals, factory repair manuals, and so on that it would wish to distribute, but for simplicity, this example addresses the sales information for a few products. Examples of the various products produced by the tool manufacturer include a twenty-five piece drill set, a forty- five piece drill and screwdriver set, a cordless circular saw, and a cordless drill. The tool manufacturer uses the hub 110 to share the documents describing its tools with its distributors and retailers. The tool manufacturer thus provides the distributors and retailers with product information that can be shared with sales staff and customers distributor's or retailer's intranet, for example, or in a printed product description book. The tool manufacturer can use the hub to provide the same information (in the same or a different format) to an on-line retailer for easy inclusion on the on-line retailer's web site.

In this example, in addition to product information, the tool manufacturer also creates promotional documents that describe holiday (in this example, Father's Day) gift ideas that are priced at under $100. These promotional documents are intended to help readers looking for a Father's Day present to select one of the tool manufacturer's products. Distribution of such promotional documents allows on- and off-line retailers to promote the tool manufacturer's products. In this example, content assets may be provided in various formats, and some documents may be provided in multiple formats to allow for web use, Internet use, and use as a printed document, as the subscriber prefers.

Examples of content assets produced by the tool manufacturer are shown in TABLE 1. A short description of each of the assets is also included for reference.^' As described above, the tool manufacturer can create content profiles for each of these content assets. In this example, the content profiles include system attributes and user-defined attributes, which are defined by the producer. The system attributes include FILE NAME, which is the name of the file, CREATION DATE, which is the date the asset was created, CREATOR, which is the name of the file creator, TYPE, which is the format of the file, and SIZE, which is the file size, in kilobytes. The tool manufacturer also includes user-defined attributes in the content profiles. These user-defined attributes include NAME, which is a full name for the asset, an ALIAS which is an alternative NAME, a TARGET AUDIENCE, which indicates who the target audience of the asset is, a PRICE POINT indicating the price of the product described in the asset (e.g. 30 meaning $30-and-under, 100 meaning $100 and under, and so on). DESCRIPTION fields allow for additional description of the content. TARGET USE indicates how the asset is intended to be used (e.g. web, print). ASSOCIATED IMAGE includes a list of other files or assets (e.g. graphics or audio files) needed for use of the asset. START DATE indicates when the asset should first be available for' distribution. ' EXPIRATION DATE indicates when the content asset will no longer be available for distribution. REFRESH RATE indicates how frequently the asset will change or should be updated. UTYPE provides additional information about the type of intended use, for example, web, camera-ready, etc.

TABLE 2 lists content profiles for some of the example content assets of TABLE 1. For example, for the file 20PCDRILL.pdf, the system attributes indicate that the FILENAME is 20PCDRILL.pdf, the CREATION DATE is October 15, 1999, the CREATOR is Sam Smith, the file is an ADOBE ACROBAT PDF file, and the SIZE is 15 kilobytes. The user-attributes indicate that the NAME is "20 Piece Drill Set," and the ALIAS is "Drill Accessories." The TARGET AUDIENCE is a "Retail Customer," and the PRICE POINT is under $30. Product DESCRIPTIONS include "Small Household Projects," "Gift Assortments," and "Power Tools." The TARGET USE is print. The ASSOCIATED IMAGEs include a graphics file "20PCBIT.gif." The START DATE for when the file was available for distribution is November 30, 1999, and the EXPIRATION DATE is August 31, 2000. The REFRESH RATE is monthly, and UTYPE is "Camera-Ready," indicating that this document is ready for printing.

For the file 45PCDRIVER.pdf, the system attributes indicate that the CREATION DATE is October 15, 1999, the CREATOR is Sam Smith, the file is an ADOBE ACROBAT PDF file, and the SIZE is 18 kilobytes. The user-attributes indicate that the NAME is "45 Piece Driver Set," and the ALIAS is "Drill Accessories." The TARGET AUDIENCE is a "Retail Customer," and the PRICE POINT is under $30. Product DESCRIPTIONS include "Small Household Projects," "Gift Assortments," and "Power Tools." The TARGET USE is print. The ASSOCIATED IMAGEs include a graphics file "20PCBIT.gif." The START DATE for when the file was available for distribution is November 30, 1999, and the EXPIRATION DATE is August 31, 2000. The REFRESH RATE is monthly, and UTYPE is "Camera-Ready," indicating that this document is ready for printing.

For the file CSCIRCSAW.htm, the system attributes indicate that the CREATION DATE is October 15, 1999, the CREATOR is Sam Smith, the file is an HTML file, and the SIZE is 10 kilobytes. The user-attributes indicate that the NAME is "14.4v Cordless Circular Saw," and the ALIAS is "Circular Saw." The TARGET AUDIENCE is a "Retail Customer," and the PRICE POINT is under $100. Product DESCRIPTIONS include "Small Household Projects," "Gift Assortments," "Power Tools," and "Cordless Tools." The TARGET USE is website. The ASSOCIATED IMAGEs include a graphics file "circsaw.gif." The START DATE for when the file was available for distribution is November 30, 1999, and the EXPIRATION DATE is August 31, 2000. The REFRESH RATE is monthly, and UTYPE is "webpage," indicating that this document is ready to be included on a web site.-

The file CSCIRCSAW.pdf provides essentially the same information as CSCIRCSAW.HTM, but is presented in a printable and display format, rather than in HTML. The system attributes indicate that FILE CSCIRCSAW.pdf has a CREATION DATE of October 15, 1999, and the CREATOR is Sam Smith, the file is a PDF file, and the SIZE is 15 kilobytes. The user-attributes indicate that the NAME is "14.4v Cordless Circular Saw," and the ALIAS is "Circular Saw." The TARGET AUDIENCE is a "Retail Customer," and the PRICE POINT is under $100. Product DESCRIPTIONS include "Small Household Projects," "Gift Assortments," "Power Tools," and "Cordless Tools." The TARGET USE is print. The ASSOCIATED IMAGEs include a graphics file "circsaw.gif." The START DATE for when the file was available for distribution is November 30, 1999, arid the EXPIRATION DATE is August 31, 2000. The REFRESH RATE is monthly, and UTYPE is "Camera-Ready," indicating that this document is ready to be included on a web site.

For the file CSDRILL.htm, the system attributes indicate that the CREATION DATE is October 15, 1999, the CREATOR is Sam Smith, the file is an HTML file, and the SIZE is 10 kilobytes. The user-attributes indicate that the NAME is " 14.4v Cordless Drill," and the ALIAS is "Drills." The TARGET AUDIENCE is a "Retail Customer," and the PRICE POINT is under $100. Product DESCRIPTIONS include "Small Household Projects," "Gift Assortments," "Power Tools," and "Cordless Tools." The TARGET USE is website. The ASSOCIATED IMAGEs include a graphics file "drill.gif." The START DATE for when the file was available for distribution is November 30, 1999, and the EXPIRATION DATE is August 31, 2000. The REFRESH RATE is monthly, and UTYPE is "webpage," indicating that this document is ready to be included on a web site.

The file CSDRILL.pdf provides essentially the same information as CSDRILL.HTM, but is presented in a printable and display format, rather than in HTML. The system attributes indicate that FILE CSCIRCSAW.pdf has a CREATION DATE of October 15, 1999, and the CREATOR is Sam Smith, the file is a PDF file, and the SIZE is 15 kilobytes. The user-attributes indicate that the NAME is "14.4v Cordless Drill, and the ALIAS is "Drills." The TARGET AUDIENCE is a "Retail Customer," and the PRICE POINT is under $100. Product DESCRIPTIONS include "Small Household Projects," "Gift Assortments," "Power Tools," and "Cordless Tools." The TARGET USE is print. The ASSOCIATED IMAGEs include a graphics file "drill.gif." The START DATE for when the file was available for distribution is November 30, 1999, and the EXPIRATION DATE is August 31, 2000. The REFRESH RATE is monthly, and UTYPE is "Camera-Ready," indicating that this document is ready to be included on a web site.

For the file FATHERSDAY.fls, the system attributes indicate that the CREATION DATE is October 15, 1999, the CREATOR is Brad Hicks, the file is a FLASH multimedia file (a format defined by MACROMEDIA), and the SIZE is 1500 kilobytes. The user-attributes indicate that the NAME is "Father's Day Flash," and the ALIAS is "Gift Box Animation." The TARGET AUDIENCE is a "Retail Customer," DESCRIPTIONS include "Father's day," "Animation," and "Web Site Enhancements." The TARGET USE is website. The START DATE for when the file was available for distribution is June 1, 2000, and the EXPIRATION DATE is June 30, 2000. The UTYPE is "multimedia," indicating that this content asset is a multimedia presentation. Because this asset does not describe a product, the data "PRICE POINT" is not included. Therefore, a rule that specified "PRICE POINT > $100" would not select this asset.

Other assets have profiles with similarly appropriate information associated with them.

Referring to TABLE 3, the tool manufacturer can create packages of the content files, and each of these packages has an associated profile. The system attributes of a package profile include the PACKAGE NAME, which is a package identifier, the CREATE DATE, which is when the package was created, the CREATOR of the package, the SIZE of the package including all assets, and the assets included in the package, which may be determined by referring to one or more named rules. Named rules may specify file names or other references to specific assets (e.g. NAME— "FILENAME.HTML"), or named rules can include the names of rules, that is logical statements that result in the selection of specified files (e.g. DESCRIPTION = "drill" and PRICE POINT <= 100). System attributes also include a START DATE for the package availability, and EXPIRATION DATE when the package will no longer be available, and the package REFRESH RATE, which is how often the package will be updated. The DESCRIPTION provides additional descriptors of package content. The STYLE SHEET attribute includes the options for style sheets, which can be used to provide formatting alternatives.

A producer can define additional attributes, and in this example, the tool manufacturer defines a CUSTOMER SEGMENT, which is who the intended recipient of the package is, a TARGET MARKET, that is who the content is directed to the package TYPE, indicating the type of package, a PACKAGE GROUP, for indicating the group the package is in. The PURPOSE indicates the intended purpose of the content.

For the sample package called "GIFTS_UNDER_$100", system attributes indicate that the CREATE DATE is January 15, 2000. The CREATOR is Susan Gilmont, and the SIZE is 1500 kilobytes (1.5 megabytes). The START DATE for the package availability is June 1, 2000, the EXPIRATION DATE is May 31, 01. The REFRESH RATE is quarterly. The DESCRIPTION of the package is "Mid Priced Gifts for All Occasions," and the STYLE SHEET lists one option "OPTION 1."

The ASSOCIATED ASSETS include the "Cordless Combo Kit," the "14.4v Cordless Circular Saw," and the "14.4v Cordless Drill." The assets could be selected manually by file name. Alternatively, they could be selected by using a rule. For example, the rule of ((PRICE POINT <= $100) and (DESCRIPTION = "Gift Assortments") and (TARGET AUDIENCE) == "Retail) and ((TARGET USE = "website") or (TARGET USE = "print"))) will select the assets associated with gifts under $100. A choice of (PRICE POINT <= $30) would select a smaller subset of those assets.

For the user-defined attributes, the CUSTOMER SEGMENT is "Regional Distributors," the TARGET MARKET is "Retail." The TYPE of package is "Mid-Priced Gifts," the PACKAGE GROUP is the "cordless group," and the PURPOSE is "Sales." The user defined attributes provide additional ways for rules to select a subset of assets.

For the sample package called "Father's Day Flash", system attributes indicate that the CREATE DATE is January 15, 2000. The CREATOR is Brad Hicks, and the SIZE is 1500 kilobytes (1.5 megabytes). The START DATE for the package availability is June 1, 2000, the EXPIRATION DATE is June 30, 2000. The REFRESH RATE is "N/A," meaning that there are no updates scheduled. The DESCRIPTION of the package is "Simple Multimedia," and there is no STYLE SHEET. The ASSOCIATED ASSETS include only "Father's Day Flash." The assets can be associated with the package by manual selection, or they can be selected by using a rule. For example, the rule of ((UTYPE==Multimedia) and (NAME == Father's Day)) will select the assets associated with Father's Day multimedia presentations.

For the user-defined attributes, the CUSTOMER SEGMENT is "Regional Distributors," the TARGET MARKET is "Retail," The TYPE of package is "Multimedia," and the PACKAGE GROUP is the "cordless group," and the PURPOSE is "Site Enhancement."

Referring to TABLE 4, an example subscriber profile is associated with a subscriber. In other embodiments, utilizing somewhat different profile attributes, the same subscriber profile is associated with one or more employees of a corporate subscriber, so that a subscriber can have one or more employees each communicate with the hub using a different SYSTEM NAME. In such a case, the subscriber-specific information would be the same for each SYSTEM NAME. In yet other embodiments, groups of subscribers could share subscriber profiles. This example demonstrates the simple case, where each subscriber has one SYSTEM NAME.

In this example, the subscriber profile includes system attributes, such as the SYSTEM NAME, which is a system identifier for the subscriber, a START DATE, which is the date that the subscriber can access the system, and the STATUS of the subscriber's account. An AGENT CONFIG FILE attribute identifies a file containing configuration information for this subscriber. This file may be shared among one or more agents of a subscriber. The NAME of the subscriber is also included, the EMAIL (electronic mail) address of the subscriber, a USER IDENTIFIER for the user to authenticate to the hub, as well as a PASSWORD, which is an access code to authenticate the subscriber. The PASSWORD may be stored in an encrypted form, for example, as the result of a one-way function performed on the subscriber's password. The CORP URL includes the Internet address for the subscriber's company, and an Internet DELIVERY ADDRESS lists an Internet address for content delivery. The NOTIFICATION indicates how the subscriber is notified of content updates and offers of packages. The subscriber's ORGANIZATION affiliation is also included.

In addition to the subscriber-specific information, a content producer can include attribute information in a subscriber's profile. Generally, this is information that relates to the producer-subscriber relationship. The example of TABLE 4 shows only producer attributes for one producer, "Tool Maker, Inc.," however, if a subscriber subscribes to the content for multiple producers, it is likely that there will be producer-provided attributes from each of the producers. In the example of TABLE 4, producer-defined attributes include the PRODUCER identifier, a CUSTOMER SEGMENT, which indicates what type of subscriber this is, the TARGET MARKET of this subscriber, an indicator of whether this subscriber is an ACTIVE customer, the ROLE of this subscriber, the STYLE SHEET TYPE preference of the subscriber, and the PRODUCT LINES that the subscriber is interested in. This information can be used to direct packages and other information to the subscriber.

In the example of TABLE 4, the SYSTEM name for the subscriber shown is 134258. The START DATE is November 21, 2000, and the subscriber's status is ACTIVE. The AGENT CONFIG FILE is 134258.cfg, and the NAME of the subscriber is Sam Smith, and his EMAIL ADDRESS is "ssmith@acmetool.com." The subscriber's USER ID is "Sammy," and his PASSWORD is encrypted, which is shown as "XXXXXXXX" in TABLE 4. The CORP URL is www.iacksonhardware.com and the DELIVERY ADDRESS is 125.255.16.10. The NOTIFICATION value is "EMAIL ONLY." The subscriber's ORGANIZATION is ACME Tool Co.

The PRODUCER in this example is "Tool Maker, Inc." The CUSTOMER SEGMENT associated with this subscriber is "Regional Distributors." The TARGET MARKET is "retail," the subscriber is ACTIVE, and the ROLE of the subscriber is SALES. The STYLE SHEET TYPE selected by this subscriber is OPTION 1. The PRODUCT LINES carried by this subscriber are the "Cordless Group," "Hand Tools," "Low-price Power Tools," "Lawn & Garden Equipment," "Holiday Promotions," and "Seasonal Promotions." The CONTENT STYLE used by this subscriber includes "Web," "Flyer," and "Radio Promotions."

For each subscriber, the hub also has a list of the packages subscribed to by the subscriber, and the hub tracks the content that has been delivered to a subscriber and the content that is awaiting delivery to each subscriber.

Referring to FIG. 5, in one embodiment, a content producer can access and manage the operation of the hub 10 using a web-based user interface. The interface includes a series of web pages that allow the user to manage the distribution of the content assets to subscribers.

In one embodiment, when a content producer first connects to the hub 10, the main page 200 is presented. The main page 200 provides the content producer with subscriber activity updates, including reports of subscribers that have accepted the content producer's package offers, and reports of content asset receipt. The riiaiή page 200 also allows access to message communication such as electronic mail and bulletin boards. The main page 200 also provides a list of the package offers currently pending. Also, system announcements are available to the content producer on the main page 200. The main page 200 also allows access to configuration settings 202. These settings include such settings as automatic expansion of archive files, configuration of web crawler and other content upload options, and so on. The main page 200 also has links to the asset management page 205, the rules management page 210, the package management page 215, and the subscriber management page 220.

The asset management page 205 displays a list of the content producer's assets that are stored on, or accessible to, the hub 10. Associated with each asset listing is a link to profile editing pages 207 for editing the content profile associated with that asset. There is also a link to upload pages 206, which is used to manually upload assets to the hub 10, or to configure the automatic transfer of assets to the hub. There are upload pages 206 for selecting files, activating the web crawler, specifying the extraction of content from a database or from a content management system. The upload pages 206 allow for configuration .of an agent to automatically upload assets from a content producer's computer. The upload pages 206 allow for the automatic, or semi-automatic initialization of profile information for uploaded assets, by setting default parameter values for uploaded assets, and^'interface tools for creating profile information.

The rules management page 210 displays a list of the content producer's named rules. Associated with each rule listing is a link to rule editing pages 211 for editing the rule logic. There is also a link to asset selection pages 212 for manual selection of assets to be included in a rule, or to review and modify the results of rule-based selection of assets.

As described above, packages are collections of assets identified by one or more rules that are made available to some subset (which possibly includes all) subscribers. The package management page 215 presents a list of each of the content producer's packages. The package management page allows for the editing of the text and graphic description of a package that will be presented to potential and actual subscribers. A link associated with each package offer listing provides access to pages 216 that allow editing of the profiles associated with each package. There is also a link to pages 217 for selecting rules to select the assets to be included in a package, which includes a link to rules management pages 210 (not shown). There is also a link to pages 220 for identifying subscribers who will receive a package, and for identifying and modifying information about subscribers subscribed to the package, which may include editing the producer-supplied information in the subscriber profiles for those subscribers.

Referring to FIG. 6, in one embodiment, when a subscriber first connects to the hub 10 over the web, the subscriber is presented with the subscriber main page 240. The main page 240 displays a list of the subscriber's current subscriptions, and a list of unsubscribed packages currently available for subscription. The subscriber main page 240 includes reports of producer's activities, including updates, and subscriptions that will be available shortly. The main page 240 also allows access to message communication such as receipt and transmission of electronic mail and bulletin board messages. Also, system announcements are available to the subscriber on the main page 240. The main page 240 also allows access to configuration settings, including display preferences. The main page 240 also has links to the new package subscription pages 244, the current packages management page 246, and the download management page 248. If a subscriber selects a new package from a list on the main page 240, a new package page 244 provides information about the package. This is the package information that was provided by the content producer as described above. The new package page may provide a preview of the content assets. Also, information such as cost and licensing restrictions may be provided on the new package page 244. The subscriber can select a link to subscribe to the package. The subscriber can select a method for downloading the package, for example, whether download will be manual or automatic, and where on the subscriber's computer the downloaded assets should be stored. If there are configuration options, such as style sheet choices or other content preferences available for the package, those preferences can be selected or modified on the new package page 244.

The subscriber can select an existing package page 246 from the main page 240, which will display detailed information about the current package, the assets associated with the package that have been provided to the subscriber, and any changes or updates that are available. If there are configuration options, such as style sheets or content preferences available for the package, those preferences can be modified on the existing package page 246. The subscriber can suspend or halt the subscription from the existing package page 246.

The subscriber can manage the download of assets on a download management page 248. The subscriber can select a transfer protocol (i.e. http, ftp, a proprietary protocol, etc.), and select manual or automatic transfer of content assets. The subscriber can indicate the locations for the received content assets, and indicate the type of computer and other information that will allow the hub 10 to provide an agent to the subscriber that will perform automatic transfer of the content assets.

Thus the web interface enables interaction with many producers and subscribers, and allows for easy transfer of assets from producer to subscriber.

Referring to FIG. 7, an embodiment of a method of customized distribution of content from one or more content producers to one or more content subscribers begins with the step of receiving content from at least one producer (STEP 300). In one embodiment, content is received via a computer network connection. In one such embodiment, the network connection is established over the Internet. In one embodiment, content is received via a network connection from an agent running on a computer of the producer, and in one such embodiment, the agent is an applet.

Either the producer or the hub can initiate the network connection. In one embodiment, before receiving a producer's content via the networlc connection, the method includes initiating the network connection to a computer designated by the producer, and requesting the producer's content via the network connection. In another embodiment, before receiving the producer's content via the network connection, the method includes receiving a network connection request from the producer's computer, and establishing a network connection in response to the network connection request.

The method also includes associating at least one content profile with the received content (STEP 301). In one embodiment, the content profile includes a metadata description of the content. In one embodiment, the metadata description allows for the use of rules to organize the content into packages, as described above.

The method includes associating a subscriber profile with one or more of the subscribers (STEP 302). In one embodiment, the subscriber profile may include a metadata description of asset selection criteria of assets to be provided to a subscriber and the subscriber profile may include a metadata description of the subscriber. In another embodiment, the subscriber profile includes a list of packages to be provided to the subscriber. In another embodiment, the subscriber profile includes subscriber categorization information. An example of such categorization information is a customer service level denoting a level of service to be provided to the subscriber. The subscriber profile thus specifies content to be provided to one or more of the subscribers.

The method includes identifying, based on at least one content profile and at least one subscriber profile, a subset of the received content that is to be provided to at least one of the subscribers (STEP 303).

The method includes communicating the identified subset to the at least one of the subscribers based on the identified subset (STEP 304). In one embodiment, content is communicated to a subscriber via a network connection. In one such embodiment, the network connection is established over the Internet. In one embodiment, content is communicated via a network connection to an agent running on a computer of the subscriber. In one embodiment, the agent is an applet.

The network connection can be initiated by the hub or by the subscriber. In one embodiment, before communicating content via the network connection, the method includes initiating the network connection to a computer designated by the subscriber. In another embodiment, before communicating the subscriber's content via the network connection, the method includes receiving a network connection request from the subscriber's computer, and establishing a network connection in response to the network connection request. In another embodiment, the method also includes modifying the content profile in response to a request from the producer. In another embodiment, the method also includes modifying the subscriber profile in response to a request from the subscriber. .In another embodiment, the method also includes modifying the subscriber profile in response to a request from a producer. In another embodiment, the method includes incorporating the subset in the one or more web pages of the subscriber. In another embodiment, the method includes copying the identified subset of the producer's content and modifying the copy of the identified subset based on the subscriber profile. In another embodiment, the method also includes communicating the modified copies of the subset to the subscriber. In another embodiment, the subset includes all of the received content.

In another embodiment, the method also includes the step of associating at least one package, each of the at least one packages having a package profile, with the received content based on the at least one content profile, and associating a subscriber profile with each of the subscribers.

In one embodiment, the method also includes the step of transmitting to the producer notice of successful communication of the subset to the subscriber. In one embodiment, the method also includes transmitting to the subscriber notice of successful communication of the subset.

In one embodiment, the method just described is performed on a hub, which is implemented as one or more server computers including network interface hardware and having one or more processors and software programming that performs the tasks described above. The hub includes a receiver for receiving content from at least one of the producers. In one embodiment, the receiver is implemented in a combination of hardware and software for network communication. The hub includes a content profile association subsystem for associating at least one content profile with the received content, and a subscriber profile association subsystem for associating a subscriber profile with each of the subscribers. In one embodiment, these subsystems are implemented as software modules that run on the server computer or computers. The hub also includes a selection subsystem for identifying based on at least one content profile and at least one subscriber profile a subset of the received content that is to be provided to at least one of the subscribers. In one embodiment, the selection subsystem is implemented as a software module running on the server computers. The hub also includes a transmitter for communicating the identified subset to the at least one of the subscribers. In one embodiment, this is implemented with a combination of software and hardware for network communication. Variations, modifications, and other implementations of what is described herein will occur to those of ordinary skill in the art without departing from the spirit and the scope of the invention as claimed. Accordingly, the invention is to be defined not by the preceding illustrative description but instead by the spirit and scope of the following claims.

What is claimed is:

Claims

1. A method of customized distribution of content from one or more content producers to one or more content subscribers, comprising the steps of:

(a) receiving content from at least one of the producers;

(b) associating at least one content profile with the received content;

(c) associating a subscriber profile with each of the subscribers;

(d) identifying based on at least one content profile and at least one subscriber profile a subset of the received content that is to be provided to at least one of the subscribers;

(e) communicating the identified subset to the at least one of the subscribers based on the determination in step (d).

2. The method of claim 1 wherein step (b) comprises associating a content profile with the received content, the content profile comprising a metadata description of the content.

3. The method of claim 1 wherein step (c) comprises associating a subscriber profile with a subscriber, the subscriber profile comprising at least one of a metadata description of asset selection criteria of assets to be provided to a subscriber and a metadata description of the subscriber.

4. The method of claim 1 wherein step (c) comprises associating a subscriber profile with a subscriber, the subscriber profile comprising a list of packages to be provided to the subscriber.

5. The method of claim 1 wherein step (c) comprises associating a subscriber profile with a subscriber, the subscriber profile comprising customer categorization information.

6. The method of claim 1 wherein step (a) comprises receiving content via a network connection.

7. The method of claim 6 wherein step (a) comprises receiving content via an Internet network connection.

8. The method of claim 6 wherein step (a) comprises receiving content via a network connection from an agent running on a computer of the producer.

9. The method of claim 8 wherein step (a) comprises receiving content via a network connection from an agent running on a computer of the producer, wherein said agent is an applet.

10. The method of claim 7 further comprising, before the step of receiving the producer's content via the network connection, the steps of: (i) initiating the network connection to a computer designated by the producer; and (ii) requesting the producer's content via the network connection.

11. The method of claim 7 further comprising, before the step of receiving the producer' s content via the network connection, the steps of:

(i) receiving a network connection request from the producer's computer;

(ii) opening a network connection in response to the network connection request.

12. The method of claim 1 further comprising the step of transmitting to the producer notice of successful communication of the subset to the subscriber.

13. The method of claim 1 wherein step (e) comprises communicating the subset via a network connection.

14. The method of claim 13 wherein step (e) comprises communicating the subset via an Internet network connection.

15. The method of claim 13 wherein step (e) comprises communicating the subset via a network connection to an agent running on a computer of the subscriber.

16. The method of claim 15 wherein step (e) comprises communicating the subset via a network connection to an agent running on a computer of the subscriber, wherein said agent is an applet.

17. The method of claim 13 further comprising, before the step of communicating the subset, the step of: initiating the network connection to a computer designated by the subscriber.

18. The method of claim 13 further comprising, before the step of communicating the subset, the steps of:

(i) receiving a network connection request from the subscriber's computer;

19. The method of claim 1 further comprising the step of transmitting to the subscriber notice of successful communication of the subset to the subscriber.

20. The method of claim 1 further comprising the step of modifying the content profile in response to a request from the producer.

21. The method of claim 1 further comprising the step of modifying the subscriber profile in response to a request from the subscriber.

22. The method of claim 1 further comprising the step of modifying the subscriber profile in response to a request from a producer.

23. The method of claim 1 further comprising the step of:

(f) incorporating the subset in the one or more web pages of the subscriber.

24. The method of claim 1, further comprising, after step (d) and before step (e), the steps of: (i) copying the identified subset of the producer's content; and

(ii) modifying the copy of the identified subset based on the subscriber profile.

25. The method of claim 24 wherein step (e) comprises communicating the modified copies of the subset to the subscriber.

26. The method of claim 1, wherein step (d) comprises identifying the subset of the received content to be provided to the subscriber, the subset comprising all of the received content.

27. The method of claim 1, further comprising, after step (b), the step of associating at least one package, each of the at least one packages having a package profile, with the received content based on the at least one content profile; and wherein step (c) comprises associating a subscriber profile with each of the subscribers, the subscriber profile specifying packages to be provided to one or more of the subscribers based on the subscriber profile and at least one package profile.

28. A hub for customized distribution of content from one or more producers to one or more subscribers, comprising:

(a) a receiver for receiving content from at least one of the producers;

(b) a content profile association subsystem for associating at least one content profile with the received content;

(c) a subscriber profile association subsystem for associating a subscriber profile with each of the subscribers;

(d) a selection subsystem for identifying based on at least one content profile and at least one subscriber profile a subset of the received content that is to be provided to at least one of the subscribers;

(e) a transmitter for communicating the identified subset to the at least one of the subscribers.

29. The hub of claim 28 wherein the content profile association subsystem associates a content profile with the received content, the content profile comprising a metadata description of the content.

30. The hub of claim 28 wherein the subscriber profile association subsystem associates a subscriber profile with a subscriber, the subscriber profile comprising at least one of metadata description of asset selection criteria of assets to be provided to a subscriber and a metadata description of the subscriber.

31. The hub of claim 28 wherein the subscriber profile association subsystem associates a subscriber profile with a subscriber, the subscriber profile comprising a list of packages to be provided to the subscriber.

32. The hub of claim 28 wherein the subscriber profile association subsystem associates a subscriber profile with a subscriber, the subscriber profile comprising customer categorization information.

33. The hub of claim 28 wherein the receiver receives content via a network comiection.

34. The hub of claim 33 wherein the receiver receives content via an Internet network connection.

35. The hub of claim 34 wherein the receiver receives content via a network comiection from an agent running on a computer of the producer.

36. The hub of claim 35 wherein the receiver receives content via a network connection from an agent running on a computer of the producer, wherein said agent is an applet.

37. The hub of claim 34 further comprising a network interface for initiating the network connection to a computer designated by the producer and for requesting the producer's content via the network connection.

38. The hub of claim 34 wherein the receiver receives a network connection request from the producer's computer and opens a network connection in response to the network connection request.

39. The hub of claim 28 wherein the transmitter transmits to the producer notice of successful communication of the subset to the subscriber.

40. The hub of claim 28 wherein the transmitter communicates the identified subset via a network connection.

41. The hub of claim 40 wherein the transmitter communicates the identified subset via an Internet network connection.

42. The hub of claim 41 wherein the transmitter communicates the identified subset via a network connection to an agent running on a computer of the subscriber.

43. The hub of claim 42 wherein the transmitter communicates the identified subset via a network connection to an agent running on a computer of the subscriber, wherein said agent is an applet.

44. The hub of claim 40 further comprising a network interface for initiating the network connection to a computer designated by the subscriber and for communicating the subset via the network connection.

45. The hub of claim 40 further comprising a network interface for receiving a network connection request from the subscriber's computer and opening a network connection in response to the network connection request.

46. The hub of claim 40 wherein the transmitter transmits to the subscriber notice of successful communication of the subset to the subscriber.

47. The hub of claim 28 wherein the content profile association subsystem modifies the content profile in response to a request from the producer.

48. The hub of claim 28 wherein the subscriber profile association subsystem modifies the subscriber profile in response to a request from the subscriber.

49. The hub of claim 28 wherein the subscriber profile association subsystem modifies the subscriber profile in response to a request from the producer.

50. The hub of claim 28 wherein the subset is incorporated in the one or more web pages of the subscriber.

51. The hub of claim 28, further comprising a customization subsystem for copying the identified subset of the producer's content and modifying the copy of the identified subset based on the subscriber profile.

52. The hub of claim 51 wherein the transmitter transmits the modified copies of the subset to the subscriber.

53. The hub of claim 28, wherein the subset comprises all of the received content.

54. The hub of claim 28, further comprising atleast one package, each of the at least one package having a package profile, associated with the received content based on the at least one content profile; and wherein the subscriber profile association subsystem associates a subscriber profile with each of the subscribers, the subscriber profile specifying packages to be provided to one or more of the subscribers based on the subscriber profile and at least one package profile.