It is well understood that a computing device can only display content that is of a format recognizable by the device's display software. It is the responsibility of the content provider to ensure that any content that it delivers over a network to a user's computing device is formatted appropriately for display on that particular user's device, or else the device will be unable to render the content correctly, if at all.
Taking into account the ever-increasing types of available content (e.g., web pages, feeds, videos, music, programs, etc.), in addition to the various types of computing devices that display content (e.g., PCs, mobile phones, handheld computing devices, etc.), this responsibility of providing multi-formatted content becomes a great burden to many content providers.
Accordingly, there is a need in the art for a system and method to provide displayable content to users in a less burdensome fashion.
The present invention reduces the content provider's burden of providing multi-formatted content by introducing a content distribution system that accepts content in its native format from a content provider, and makes any necessary transformations to the content's format so that the system can deliver displayable content to users.
In the configuration phase (100), the aggregation platform (120) provides a user interface (step 200) over a network (115) to a content provider (110) and an administrator (170) of the system. The content provider (110) inputs (step 210) into the UI (130) a location of content (132) to be provided to the aggregation platform (120) in the delivery phase (105). To ease the burden of the content provider (110), it need not alter the format of the source content to be delivered to the aggregation platform (120); the delivered content may remain in the source format native to the content provider (110). The platform (120) then stores (step 220) the content location (132) in the database (140) in association with the content provider's profile.
The content location may be expressed as a URL, for example. The source format may include, for example, podcast, RSS, NewsML, sportsML and/or a customized XML format.
In order to enable the aggregation platform (120) to recognize the content provider's source-formatted content (112) so that the platform (120) may process the content for delivery to users, the administrator (170) reviews the source format of the content and inputs (step 230) into the user interface (130) transformation instructions (134) describing how to transform the source format into a platform format native to the aggregation platform (120). The platform (120) then stores (step 240) the transformation instructions (134) in the database (140) in association with the content provider's profile.
Through the use of a such an interface (130), which may be provided as a web interface over the Internet, distribution partners and content partners associated with the content distribution system may establish feeds and programs/subscriptions very quickly and easily. A distribution partner can set up programs using any feeds available on the platform, including feeds that are provided by an unrelated third-party. This capability advantageously enables distribution partners who have an expertise in distribution and marketing, but not necessarily an expertise in or a capability of generating content, to offer a wider range of content in their subscriptions. Similarly, a content partner that generates content but does not want to market and sign up subscribers can obtain a revenue stream from their content by allowing distribution partners to distribute the content using the aggregation platform (120). As described above, the content provider (110) does not have to change the content from its native format. The platform (120) transforms the input and ensures proper compatibility with the end user's device.
In the delivery phase (105), the content provider (110) provides (step 400) the source-formatted content (112) to the platform (120). The transformation engine (150) receives the source-formatted content (112), and then retrieves (step 410) the transformation instructions (134) associated with this content from the database (140) so that it can transform (step 420) the source format of the content into the platform format in accordance with the retrieved instructions, and store the resulting platform-formatted content (155) in the database (140).
The delivery engine (160) subsequently retrieves (step 430) the platform-formatted content (155) from the database (140), transforms (step 440) the platform format of the platform-formatted content (155) into a delivery format recognizable by display software associated with a user (180), and delivers the delivery-formatted content (165) to the user (180) for display (step 450).
The following example illustrates a transformation of source-formatted content (112) into platform-formatted content (155) in accordance with an embodiment of the present invention. Suppose LISTING 1 represents source-formatted content (112) that is an XML-based RSS feed:
The transformation engine (150) may use the LISTING 2 XSL Transformation on the RSS feed of LISTING 1:
to generate the LISTING 3 platform-formatted content (155):
The input device (520) may include a keyboard, mouse, pen-operated touch screen or monitor, voice-recognition device, or any other device that provides input. The output device (530) may include a monitor, printer, disk drive, speakers, or any other device that provides output.
The storage (540) may include volatile and nonvolatile data storage, including one or more electrical, magnetic or optical memories such as a RAM, cache, hard drive, CD-ROM drive, tape drive or removable storage disk. The communication device (560) may include a modem, network interface card, or any other device capable of transmitting and receiving signals over a network. The components of the computing device may be connected in any manner, such as via electrical bus or wirelessly.
The software (550), which may be stored in the storage (540) and executed by the processor (510), may include, for example, the application programming that embodies the functionality of the present invention (e.g., as embodied in the configuration UI (130), transformation engine (150) and delivery engine (160)). The software (550) may include a combination of client applications and enterprise servers such as an application server and a database server.
Communications may occur over any type of network (115), which may implement any communications protocol, and which may be secured by any security protocol. Network links may include telephone lines, DSL, cable networks, T1 or T3 lines, wireless network connections, or any other arrangement that implements the transmission and reception of network signals.
The computing device may implement any operating system, such as Windows, Linux or UNIX. The software (550) may be written in any programming language, such as C, C++, Java, Visual Basic and/or SQL. In various embodiments, application software embodying the functionality of the present invention may be deployed on a standalone machine, in a client/server arrangement or through a Web browser as a Web-based application or Web service, for example.
Several embodiments of the invention are specifically illustrated and/or described herein. However, it will be appreciated that modifications and variations of the invention are covered by the above teachings and within the purview of the appended claims without departing from the spirit and intended scope of the invention.
For example, software functionality that implements the present invention, such as the configuration UI (130), transformation engine (150) and delivery engine (160), may comprise several discrete modules that together still provide the same functionality, data specified in the illustrated database (140) may be spread over several databases and/or systems, and the data and flow diagrams of
This application claims the benefit under 35 U.S.C. § 119(e) of U.S. Provisional Application No. 60/776,967, filed Feb. 24, 2006, which is hereby incorporated by reference in its entirety.
Number | Name | Date | Kind |
---|---|---|---|
5309257 | Bonino et al. | May 1994 | A |
5347600 | Barnsley et al. | Sep 1994 | A |
5548789 | Nakanura | Aug 1996 | A |
5613017 | Rao et al. | Mar 1997 | A |
5781901 | Kuzma | Jul 1998 | A |
5826023 | Hall et al. | Oct 1998 | A |
5860074 | Rowe et al. | Jan 1999 | A |
5883640 | Hsieh et al. | Mar 1999 | A |
5896502 | Shieh et al. | Apr 1999 | A |
5903723 | Beck et al. | May 1999 | A |
5917965 | Cahill et al. | Jun 1999 | A |
5956044 | Giorgianni et al. | Sep 1999 | A |
6016520 | Facq et al. | Jan 2000 | A |
6072598 | Tso | Jun 2000 | A |
6072902 | Myers | Jun 2000 | A |
6081883 | Popelka et al. | Jun 2000 | A |
6101320 | Schuetze et al. | Aug 2000 | A |
6125201 | Zador | Sep 2000 | A |
6141686 | Jackowski et al. | Oct 2000 | A |
6161140 | Moriya | Dec 2000 | A |
6167441 | Himmel | Dec 2000 | A |
6195696 | Baber et al. | Feb 2001 | B1 |
6198941 | Aho et al. | Mar 2001 | B1 |
6202097 | Foster et al. | Mar 2001 | B1 |
6256666 | Singhal | Jul 2001 | B1 |
6275869 | Sieffert et al. | Aug 2001 | B1 |
6278449 | Sugiarto et al. | Aug 2001 | B1 |
6289375 | Knight et al. | Sep 2001 | B1 |
6300947 | Kanevsky | Oct 2001 | B1 |
6311215 | Bakshi et al. | Oct 2001 | B1 |
6330068 | Matsuyama | Dec 2001 | B1 |
6330073 | Sciatto | Dec 2001 | B1 |
6334126 | Nagatomo et al. | Dec 2001 | B1 |
6341316 | Kloba et al. | Jan 2002 | B1 |
6351547 | Johnson et al. | Feb 2002 | B1 |
6351568 | Andrew | Feb 2002 | B1 |
6360252 | Rudy et al. | Mar 2002 | B1 |
6385772 | Courtney | May 2002 | B1 |
6389460 | Stewart et al. | May 2002 | B1 |
6411685 | O'Neal | Jun 2002 | B1 |
6421733 | Tso et al. | Jul 2002 | B1 |
6438576 | Huang et al. | Aug 2002 | B1 |
6441913 | Anabuki et al. | Aug 2002 | B1 |
6449658 | Lafe et al. | Sep 2002 | B1 |
6457044 | Iwazaki | Sep 2002 | B1 |
6473794 | Guheen et al. | Oct 2002 | B1 |
6480853 | Jain | Nov 2002 | B1 |
6490675 | Sugiura | Dec 2002 | B1 |
6493758 | McLain | Dec 2002 | B1 |
6505236 | Pollack | Jan 2003 | B1 |
6509910 | Agarwal et al. | Jan 2003 | B1 |
6592629 | Cullen et al. | Jul 2003 | B1 |
6598076 | Chang et al. | Jul 2003 | B1 |
6724721 | Cheriton | Apr 2004 | B1 |
6734994 | Omori | May 2004 | B2 |
6742043 | Moussa et al. | May 2004 | B1 |
6779042 | Kloba et al. | Aug 2004 | B1 |
6925595 | Whitledge et al. | Aug 2005 | B1 |
7054905 | Hanna et al. | May 2006 | B1 |
7310612 | McQueen et al. | Dec 2007 | B2 |
20010049648 | Naylor et al. | Dec 2001 | A1 |
20010054075 | Miyanaga | Dec 2001 | A1 |
20020016818 | Kirani et al. | Feb 2002 | A1 |
20020116531 | Chu | Aug 2002 | A1 |
20020120693 | Rudd et al. | Aug 2002 | A1 |
20020151283 | Pallakoff | Oct 2002 | A1 |
20020169823 | Coulombe et al. | Nov 2002 | A1 |
20030028563 | Stutz et al. | Feb 2003 | A1 |
20030093565 | Berger et al. | May 2003 | A1 |
20030115277 | Watanabe et al. | Jun 2003 | A1 |
20030126136 | Omoigui | Jul 2003 | A1 |
20030188039 | Liu et al. | Oct 2003 | A1 |
20040078304 | Gabbard et al. | Apr 2004 | A1 |
20040117731 | Blyashov | Jun 2004 | A1 |
20040162818 | Shaw | Aug 2004 | A1 |
20040258063 | Raith et al. | Dec 2004 | A1 |
20050193341 | Hayward et al. | Sep 2005 | A1 |
20060053227 | Ye et al. | Mar 2006 | A1 |
20060190616 | Mayerhofer et al. | Aug 2006 | A1 |
Number | Date | Country |
---|---|---|
19934787 | Feb 2001 | DE |
10050172 | Apr 2001 | DE |
0763643 | Mar 1997 | EP |
811939 | Dec 1997 | EP |
0950969 | Oct 1999 | EP |
0992922 | Apr 2000 | EP |
1109371 | Jun 2001 | EP |
1109372 | Jun 2001 | EP |
WO 9749252 | Dec 1997 | WO |
WO 9843177 | Oct 1998 | WO |
WO 9960793 | Nov 1999 | WO |
PCTGB0001962 | Nov 2000 | WO |
WO 0075859 | Dec 2000 | WO |
PCTSE0000807 | Jan 2001 | WO |
PCTKR0101323 | Feb 2002 | WO |
Number | Date | Country | |
---|---|---|---|
20080147674 A1 | Jun 2008 | US |
Number | Date | Country | |
---|---|---|---|
60776967 | Feb 2006 | US |