US20140082153A1 - Digital content hub - Google Patents

Abstract

There are provided methods and systems to retrieve search result information and digital content. The system receives input information identifying a plurality of data sources from which to retrieve digital content. Next the system retrieves search result information, over the network, from the plurality of data sources based on the input information. Next the system retrieves the digital content, over the network, from at least one of the data sources based on the search result information. Finally, the system communicates digital content to a client machine.

Description

PRIORITY
• This application is a Continuation of and claims the benefit of priority to U.S. patent Application Ser. No. 13/552,935, filed Jul. 19, 2012, which is a continuation of application Ser. No. 11/779,022, filed Jul. 17, 2007, both of which are hereby incorporated by reference in their entirety.
FIELD
• Embodiments relate generally to the technical field of data communications and, in one example embodiment, to methods and systems to retrieve search result information and digital content.
BACKGROUND
• Searching for information and digital content on a network presents many challenges. One challenge is the time required to find and retrieve the desired information and digital content. For example, a user may consume considerable time operating a personal computer to visit web sites and media stores to locate specific types of digital content. Further, requesting delivery of digital content that is published to a feed may also require time to locate the feed and time to filter undesirable information and digital content that is published to the feed. Other challenges include organizing, storing, and budgeting payments for digital content.
BRIEF DESCRIPTION OF DRAWINGS
• The present invention is illustrated by way of example and not limitation in the figures of the accompanying drawings, in which like references indicate similar elements and in which:
• FIG. 1 is a network diagram depicting a system, according to one example embodiment, having a client-server architecture;
• FIG. 2 is a block diagram illustrating modules and an engine, according to an embodiment, at a digital content hub;
• FIG. 3 is a block diagram illustrating modules, according to an embodiment, at a control node;
• FIG. 4 is a block diagram illustrating modules, according to an embodiment, at a portable control node;
• FIG. 5 is a block diagram illustrating a data flow, according to an embodiment;
• FIG. 6 is a block diagram illustrating a database, according to an embodiment, coupled to the digital content hub;
• FIG. 7 is a block diagram illustrating input information, according to an embodiment;
• FIG. 8 is a block diagram illustrating search information, according to an embodiment;
• FIG. 9 is a block diagram illustrating filter information, according to an embodiment;
• FIG. 10 is a block diagram illustrating output information, according to an embodiment;
• FIG. 11 is a block diagram illustrating target information, according to an embodiment;
• FIG. 12 is a block diagram illustrating a database, according to an embodiment, coupled to the control node;
• FIG. 13 is a block diagram illustrating a database, according to an embodiment, coupled to the portable control node;
• FIG. 14 is a flow chart illustrating a method, according to an embodiment, to retrieve search result information and digital content;
• FIG. 15 is a flow chart illustrating a method, according to an embodiment, to retrieve search result information;
• FIG. 16 is a flow chart illustrating a method, according to an embodiment, to retrieve digital content;
• FIG. 17 is a flow chart illustrating a method, according to an embodiment, to identify digital content to retrieve;
• FIG. 18 is a flow chart illustrating a method, according to an embodiment, to communicate digital content to the portable control node;
• FIG. 19 is a flow chart illustrating a method, according to an embodiment, to receive input information from the portable control node and communicate the input information to the control node;
• FIGS. 20-28 are diagrams illustrating user interfaces, according to an embodiment;
• FIG. 29 is a block diagram of a machine, according to an example embodiment, including instructions to perform any one or more of the methodologies described herein.
DETAILED DESCRIPTION
• In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of an embodiment of the present invention. It will be evident, however, to one skilled in the art that the present invention may be practiced without these specific details.
• FIG. 1 is a network diagram depicting asystem10, according to one example embodiment to retrieve and communicate output information including digital content. Thesystem10 is shown to include a server machine12 (e.g., digital content hub),data sinks14, anddata sources18. Broadly, the server machine12 (e.g., digital content hub) receives input information over a network16 (e.g., Internet) from thedata sinks14 and periodically retrieves output information including digital content, over thenetwork16, frommultiple data sources18 based on the input information before communicating the retrieved output information, over thenetwork16, to thedata sinks14. Theserver machine12 may receive the input information from a user that operates thedata sinks14 and may store the input information on adatabase23 for continual and periodic retrieval of the digital content and other output information. In addition, theserver machine12 may also be authorized by the data sinks14 to make a payment, over thenetwork16, to apayment system20 as required for the retrieval of the output information including the digital content. Accordingly, the retrieved output information is targeted to the tastes and preferences of the user. This may serve to automate and streamline the tasks required to continually identify, filter, and retrieve digital content and other output information, that are of interest to the user.
• Thedata sinks14 may include a client machine22 (e.g., control node) andportable data sinks24. Thedata sinks14 may be used to request, store, manage, and play digital content. Theportable data sinks24 include portable client machines32 (e.g., IPOD or other content storage and reproduction devices). Theclient machine22 may operate as a control node that may receive input information from a user and communicate the input information to the digital content hub that, in turn, uses the input information to retrieve the digital content and other output information. Theclient machine22 is shown to be coupled to adatabase26 for storing the input and output information and amonitor28 andspeaker30. Theportable data sinks24 are shown to include twoportable client machines32. Theportable client machines32 are respectively coupled to amonitor28,speakers30 and adatabase34. Theportable client machines32 may be embodied as an IPOD made by APPLE INC. (Apple Computers) of Cupertino, Calif., the BLACKBERRY ™ wireless platform made by RESEARCH IN MOTION LIMITED (RIM) of Waterloo, Ontario or any other portable media playing device for playing, managing, and retrieving digital content.
• Thedata sources18 includeserver machines36 respectively coupled todatabases38. In various embodiments theserver machines36 may host search engines such as the GOOGLE™ search engine by GOOGLE, INC. of Mountain View, Calif., media stores such as the ITUNES media store by APPLE INC. previously mentioned, network based marketplaces such as that operated by EBAY, INC. of San Jose, Calif., multimedia distribution platforms such as YOUTUBE also by GOOGLE, INC. of or any other network accessible platforms for retrieving output information.
• Further, while thesystem10 shown inFIG. 1 employs a client-server architecture, embodiments are of course not limited to such an architecture, and could equally well find application in a distributed, or peer-to-peer, architecture system. Theserver machine12 and theclient machine22 may also host software modules and engines, as later described, that could also be implemented as standalone software programs, which do not necessarily have networking capabilities.
• FIG. 2 is a block diagram illustrating modules at server machine12 (e.g., digital content hub), according to an embodiment. The digital content hub includes aconfiguration module50, aprocessing module52, arecommendation engine54 andmedia modules56. Theconfiguration module50 receives input information from the user (e.g., control node) or from the portable client machine32 (e.g., portable control node) via theclient machine22 and utilizes the input information to generate metadata information. Further, theconfiguration module50 uses the metadata information to retrieve search result information, including search result information entries, from thedata sources18. Theprocessing module52 may utilize the identified search result information entries (e.g., links to retrieve digital content) to retrieve digital content from thedata sources18. Themedia modules56 may be used by theconfiguration module50 to access thedata sources18 to retrieve the search result information. Themedia modules56 may also be accessed by theprocessing module52 to access thedata sources18 to retrieve the digital content. Themedia modules56 may be embodied as a digital media player such as the ITUNES digital media player, a browser such as the INTERNET EXPLORER offered by MICROSOFT CORPORATION of Redmond, Wash., an RSS reader such as the GOOGLE RSS READER or any other module used to access output information over thenetwork16.
• FIG. 3 is a block diagram illustrating modules at a client machine22 (e.g., control node), according to an embodiment. Theclient machine22 may include acommunication module58, adistribution module60, andmedia modules56. Thecommunication module58 may be used to receive input information from the user and communicate the input information to the server machine12 (e.g., digital content hub). In addition, thecommunication module58 may be used to receive input information from the portable client machine32 (e.g., iPod) and communicate the input information to the server machine12 (e.g., digital content hub). Thecommunication module58 may further receive digital content and other output information from theserver machine12 and store such information to memory or to thedatabase26.
• Thedistribution module60 communicates digital content to the portable client machine32.In one embodiment thedistribution module60 may communicate the digital content to theportable client machine32 via amedia module56. In another embodiment thedistribution module60 may communicate the digital content to theportable client machine32 via an Application Processing Interface (API). Thedistribution module60 may communicate the digital content responsive to determining aportable client machine32 is connected to theclient machine22. In another embodiment, thedistribution module60 may communicate the digital content responsive to a user requesting communication of the digital content.
• FIG. 4 is a block diagram illustrating modules at a portable client machine32 (e.g., IPOD). Theportable client machine32 includes aportable media module66. Theportable media module66 may receive input information from a user and communicate the input information to the client machine22 (e.g., control node) that, in turn, communicates the input information to the server machine12 (e.g., digital content hub). In addition, theportable media module66 may generate recommendations for the acquisition of digital content that are communicated, as input information, to theclient machine22. Further, theportable media module66 may receive digital content from the client machine22 (e.g., control node) and be controlled by the user to manage and play the digital content.
• FIG. 5 is a block diagram illustrating adataflow100 for thesystem10, according to an embodiment. Illustrated on the left panel are data processing operations performed by a server machine12 (e.g., digital content hub). Illustrated in the middle panel are data processing operations performed by a server machine36 (e.g., data sources18). Illustrated in the right panel are data processing operations performed by a client machine22 (e.g., data sink14). Thedataflow100 moves from left to right and starts at the server machine12 (e.g., digital content hub).
• Broadly, the server machine12 (e.g., digital content hub) usesinput information102, that has been received from the client machine22 (e.g., control node) or the portable client machine24 (e.g., iPod) via theclient machine22, to generatemetadata information104 that, in turn, is used to retrieve output information (e.g., digital content) that is communicated to theclient machine22.
• Theinput information102 may be contained in aninput information folder108 and includesglobal filter information110. The input information may describe artists that author the digital content, creations of digital content or categories describing digital content. The global filter information112 may be used to filter retrieval of the digital content from the data sources. For example, the global filter information may be used to identify digital content that requires a purchase for an amount that exceeds a predetermined purchasing limitation before retrieving the digital content from thedata source18. Further, the global filter information may be used to filter retrieval of digital content that requires storage that exceeds a predetermined storage limitation before retrieving the digital content from thedata source18.
• Themetadata information104 includes searchresult retrieval metadata118,target metadata120, and digitalcontent retrieval metadata124. The searchresult retrieval metadata118 is used to retrieve search results information145 from the data sources18. The searchresult retrieval metadata118 includeslocal command metadata126 that may be used to generate commands. Examples of such commands include queries to retrieve the search result information145 that includes searchresult information entries121. The commands may be communicated directly through an Application Processing Interface to one of the server machines36 (e.g., search engine). In another embodiment, the commands may be communicated via a media module56 (e.g., ITUNES) that executes on theserver machine12. For example, the commands may be communicated to an ITUNES media player to advance the ITUNES media player through a series of user interfaces and request search result information (e.g., links to digital content). The ITUNES media player may, in turn, communicate the request for digital content to an ITUNES media store.
• Thetarget metadata120 includes parsemetadata128 andprofile information130. The parsemetadata128 may be used by the server machine12 (e.g., digital content hub) to parse the search result information145 to identify target information entries123 (e.g., links to digital content, subscriptions to digital content, requested information, links to streaming digital content). Theprofile information130 may include a history of input information and may be used by the server machine12 (e.g., digital content hub) to further identify target information entries123 from the search result information145. For example, theprofile information130 may be based oninput information102 that is collected from the user over a predetermined and extended period of time. Theprofile information130 may be used to generate a recommendation for each of the searchresult information entries121.
• The digitalcontent retrieval metadata124 includesremote command metadata132,purchase metadata134, andstorage metadata136. Theremote command metadata132 may be used to generate remote commands that are communicated in association with digital content to theclient machine22. The commands may be used at theclient machine22 to communicate the digital content to a portable client machine32 (e.g., portable music player). For example, theremote command metadata132 may include commands and/or other information that may be used at theclient machine22 to communicate digital content to the portable music player. Thepurchase metadata134 may be used by the server machine12 (e.g., digital content hub) to determine whether selecting a link to purchase digital content exceeds a purchase limitation such as a predetermined price. Thestorage metadata136 may be used by theserver machine12 to determine whether retrieval of digital content exceeds a storage limitation such as a predetermined storage limitation.
• Theoutput information folder106 includestarget information147, as previously described anddigital content140. Thedigital content140 may include digital information in the form of movies, albums, songs, digital samples, multimedia presentations, videos, images, etc.
• The dataflow is now described. Atoperation142, theinput information102 that has been previously received from theclient machine22, or theportable client machine32 via theclient machine22, may be used by the server machine12 (e.g., digital content hub) to generate themetadata information104. Atoperation144, themetadata information104 is used by the server machine12 (e.g., digital content hub) to retrieve the search result information145. For example, queries may be communicated to thedata sources18 that, in turn, respond by communicating the search result information145. Atoperation146, thetarget metadata120 is used by the server machine12 (e.g., digital content hub) to identify searchresult information entries121 as target information entries123. In addition, theprofile information130 may be used to generate a recommendation for each of the searchresult information entries121. Finally, the searchresult information entries121 associated with recommendations that exceed a predetermined limit may be identified as target information entries123, as explained further below.
• Atoperation148, the digitalcontent retrieval metadata124 and thetarget information147 may be used to retrieve digital content from the server machine(s)36 (e.g., data sources18). In some instances, thepurchase metadata134 and thestorage metadata136 may prohibit retrieval of digital content, as previously described. Atoperation149 thetarget information147 and thedigital content140, with associated remote commands, may be communicated to theclient machine22.
• FIG. 6 is the block diagram illustrating adatabase23 according to an embodiment, coupled to the server machine12 (e.g., digital content hub). Thedatabase23 may be used to store theinput information102, themetadata information104, and theoutput information106.
• FIG. 7 is a block diagram illustratinginput information102, according to an embodiment. Theinput information102 includesinput information folders108 andglobal filter information110. The server machine12 (e.g., digital content hub) schedules the retrieval of search result information145 and associateddigital content140 based on aninput information folder108 granularity. Theinput information folders108 may be used to store theinput information102 for an artist, a creation, or a category. For example, theinput information folder108 may containartist information152,creation information154, orcategory information156. Theartist information152 may be used to identify output information106 (e.g., digital content) associated (e.g., authored, produced, directed, edited, etc.) with an artist (e.g., Shawn Mullins, Frank Sinatra, Bob Dylan). Thecreation information154 may be used to retrieveoutput information106 associated with a creation (e.g., “Frozen Man,” “Pirates of the Caribbean,” “I Did It My Way,” etc.). Thecategory information156 may be used to retrieveoutput information106 associated with a category (e.g., Jazz, Jazz Artists, Best Movies of the Year, etc.) of digital content. Theartist information152,creation information154, andcategory information156 respectively includesearch information158 and filterinformation160. Thesearch information158 may be used to retrieve the search result information145 and identify thetarget information147 includingdigital content140 from the search result information145. The filter information160 (e.g., predetermined criteria) may be used to determine whether the identifieddigital content140 is prohibited from retrieval from the data sources18.
• The global filter information110 (e.g., predetermined criteria) may be used to apply global filters across theinput information folders108. Theglobal filter information110 includesrecommendation information162,global purchase information164, andglobal storage information214. Therecommendation information162 may be used to generate recommendations from search result information145, as previously described. Theglobal purchase information164 may be used to determine whether the digital content should be purchased based on a global filter. For example, the global filter may include a purchase limitation that prevents a one time purchase exceeding $50 notwithstanding the artist, creation or category. Another example of a global filter may include a storage rule that applies to multiple artists or a combination of artists and categories. The global storage information may be used to determine whether the digital content is retrieved based on a global filter that operates as described, but in a context of storage limitations.
• FIG. 8 is a block diagram illustratingsearch information158, according to an embodiment. Thesearch information158 includes afolder title200, targetidentification information202,search frequency information204, data sourceinformation206,release information208, andalert information210. Thefolder title200 may be input by the user to name a corresponding input andoutput information folder108,106. Thetarget identification information202 may be used to identify different types of thedigital content140 or other information (e.g., targets) that are of interest to the user. Thesearch frequency information204 may be used to identify the frequency of initiating retrieval of search result information145 and associateddigital content140. The data sourceinformation206 may be used to identify thedata sources18 from which to retrieve the search result information145 and thedigital content140. Therelease information208 may be used to identify whether all releases of a type ofdigital content140 are retrieved or a new release (e.g., not previously released) of digital content is retrieved. For example, theinput checkbox624 may receive a request to receive all releases of a type ofdigital content140 and theinput checkbox626 may receive a request to receive a new release ofdigital content140. Thealert information210 may be used to communicate an alert to a device over thenetwork16 responsive to predetermined criteria, such as retrieval of digital content.
• FIG. 9 is a block diagram illustratingfilter information160, according to an embodiment. Thefilter information160 includespurchase information212 andstorage information214 and is used as previously described but for a single input information folder108 (e.g., a single artist, creation, or category).
• FIG. 10 is a block diagram illustratingoutput information106, according to an embodiment. Theoutput information106 may include multipleoutput information folders250. Theoutput information folder250 includes a title252,target information147 and one or more digital content information254 entries. The title252 may be provided by the user and appears on user interfaces that display theoutput information folder250. Thetarget information147 may include search result information145 and digital content information245. The digital content information254 may includedigital content140, as previously described, and remote command information258. The remote command information258 may be communicated with thedigital content140 to theclient machine22 that, in turn, uses the remote command information258 to communicate thedigital content140 to a portable client machine32 (e.g., iPod).
• FIG. 11 is a block diagram illustratingtarget information147, according to embodiment. Thetarget information147 includes digitalcontent link information268, digital content subscribeinformation270, requestedinformation272 and digital contentstreaming link information274. The digitalcontent link information268 may include user interface elements (e.g., link) that may be selected to retrieve thedigital content140. In some instances, selection of the link may require a purchase to retrieve the digital content. In other instances, selection of the link may enable retrieval of thedigital content140 with a delayed purchase (e.g., at play time). The digital content subscribeinformation270 may include user interface elements (e.g., link) that may be selected to subscribe to a feed (e.g., RSS feed) that communicates (e.g., publishes) search result information145digital content140. In some instances, selection of the link may require a purchase to receive publications of the digital content. In other instances, selection of the link may enable receipt of publications of the digital content with a delayed purchase (e.g., at play time). The requestedinformation272 includes information identified by the user for retrieval form adata source18. For example, the requestedinformation272 may include ticket availability information for concerts of an artist that performs. The digital contentstreaming link information274 may include user interface elements that may be selected to initiate streaming of thedigital content140.
• FIG. 12 is a block diagram illustrating adatabase26, according to an embodiment, coupled to the client machine22 (e.g., control node). Thedatabase26 may storeoutput information folders250, as previously described.
• FIG. 13 is a block diagram illustrating adatabase34, according to an embodiment, coupled to a portable client machine32 (e.g., a portable music player). Thedatabase34 may storedigital content140, as previously described.
• FIG. 14 is flowchart illustrating amethod300, according to an embodiment, to retrieve search result information145 anddigital content140. Illustrated on the left panel is aportable client machine32 and illustrated in the right panel is aserver machine36. Illustrated in the middle left panel is aclient machine22 and illustrated in the middle right panel is aserver machine12. Themethod300 commences at operation302, at theclient machine22, with thecommunication module58 receivinginput information102. Thecommunication module58 receives theinput information102 and communicates theinput information102 to theserver machine12.
• Atoperation304, at theserver machine12, theconfiguration module50 receives theinput information102. For example, theinput information102 may identify an artist, Shawn Mullins, and request retrieval of music videos authored by Shawn Mullins for communication to theclient machine22 and to theportable client machine32. For example, theinput information102 may include a folder title200 (e.g., Shawn Mulllins), target identification information202 (e.g., music videos, ticket availability), search frequency information204 (e.g., once a day), data source information206 (e.g., iTunes Store, etc.), release information208 (e.g., new releases), alert information210 (e.g., communicate an email if found), purchase information212 (e.g., authorization to pay but not to exceed a predetermined limit) and storage information214 (e.g., authorization to retrieve but not to exceed a predetermined limit).
• At operation306, theconfiguration module50 generatesmetadata information104 based on the receivedinput information102. Atoperation308, theconfiguration module50 utilizes thesearch retrieval metadata118 to communicate commands (e.g., queries) to thedata sources18 to retrieve the search result information145.
• Atoperation308, theprocessing module52 may use thetarget metadata120 to process the search result information145. For example, theprocessing module52 may use thetarget metadata120 to identify target information entries123 in the search result information145 that may be selected to retrieve a music video by Shawn Mullins. Atoperation310, theserver machine36 may receive commands including queries from theserver machine12 that may be processed to identify the search result information145 and communicate the search result information145 back to theserver machine12.
• Atoperation312, theprocessing module52 utilizes the digitalcontent retrieval metadata124 and the search result information145 to identify thetarget information147. Next, therecommendation engine54 uses theprofile information130 and the search result information145 to identifytarget information147. Finally, theprocessing module52 utilizes thetarget information147 to communicate commands including queries to the data sources to retrieve thedigital content140 from theserver machine36.
• Atoperation314, theserver machine36 may receive commands including queries from theserver machine12 that may be processed to identify thedigital content140 and communicate thedigital content140 back to theserver machine12.
• Atoperation316, at theserver machine12, theprocessing module52 may communicate the digital content information254 and thetarget information147 to theclient machine22. For example, the digital content information254 may includedigital content140 in the form of a Shawn Mullins music video and remote command information133 to communicate thedigital content140 to a portable music player. Further, for example, thetarget information147 may include the digitalcontent link information268 used to retrieve the Shawn Mullins music video and ticket availability information for Shawn Mullins concerts.
• At operation318, at theclient machine22, thecommunication module58 receives the digital content information254 and thetarget information147 and stores the digital content information254 and thetarget information147 in theoutput information folder125 associated with Shawn Mullins.
• Atoperation320, at theclient machine22, thedistribution module60 uses themedia module identifier262 to launch the appropriate media module56 (e.g., iTunes) to communicate the associateddigital content140 to theportable client machine32.
• At operation324, at theportable client machine32, theportable media module66 receives thedigital content140 and stores the digital content on thedatabase34.
• In another embodiment, theinput information102 may be received from theportable client machine32 and communicated to theserver machine12 via theclient machine22. For example, at operation301, the user may enterinput information102 at theportable client machine32 which, in turn, communicates theinput information102 to theclient machine22. Atoperation303, at theclient machine22, thecommunication module58 may receive theinput information102 and communicate theinput information102 to the server machine12 (e.g., digital content hub).
• It will further be appreciated that the above describedmethod300 to retrieve search result information145 anddigital content140 may be initiated responsive to receipt ofinput information102 or responsive to theconfiguration module50 determining a search has been scheduled based onsearch frequency information204 associated with an input information folder is requiring initiation.
• FIG. 15 is a flowchart illustrating amethod308, according to an embodiment, to retrieve search result information145. Illustrated on the left panel are operations performed by the server machine12 (e.g., digital content hub) and illustrated on the right panel are operations performed by the server machines36 (e.g., data sources18). With respect to the left panel, operations on the left are performed by theprocessing module52 operations on the right are performed by themedia module56. Themethod308 commences atoperation350 with theprocessing module52 launchingmedia modules56 based ondata source information206 in theinput information folder108 associated with Shawn Mullins. At operation352, theconfiguration module50 communicates a query for search result information145. For example, theconfiguration module50 may use thelocal command metadata126 to generate the appropriate commands including queries to be communicated to themedia module56. Accordingly, one embodiment may include a sequence of commands to provide a user name and password to themedia module56 and navigate through a series of user interfaces displayed by themedia module56 before communicating a query to themedia module56 for the desireddigital content140. Atoperation354, themedia module56 receives the commands including a query and communicates the commands to theappropriate server machine36. Atoperation356, at thedata source18, the query is received and at operation358 thedata source18 communicates the search result information145 to theserver machine12.
• At operation360, at the server machine12 (e.g., digital content hub), themedia module56 receives the search result information145 and atoperation354, theconfiguration module50 scrapes the search result information145 from themedia module56 user interface.
• Atoperation366, theprocessing module52, at theserver machine12, subscribes to a feed for search result information145. For example, theprocessing module52 may subscribe to a feed that advertises Shawn Mullins music videos that are available for purchase on release of the music video. Atoperation368, at the server machine12 (e.g., digital content hub), themedia module56 receives and communicates the subscription to thedata source18. Atoperation370, the data source18 (e.g., iTunes Store) receives the subscription and at operation372, thedata source18 communicates the search result information145 (e.g., advertisement to purchase Shawn Mullins music video) to the server machine12 (e.g., digital content hub) responsive to the subscription. Further, at operation372, thedata source18 continues to communicate or publish search result information145 to themedia module56, at the server machine12 (e.g., digital content hub), as it becomes available.
• At operation374, at theserver machine12, the media module56 (e.g., iTunes) receives the search result information145 and at operation378, theconfiguration module50 scrapes the search result information145 from themedia module56 user interface.
• At operation380, theprocessing module52, at the server machine12 (e.g., digital content hub), processes the search result information145 to identify thetarget information147. For example, theprocessing module52 may use the parsemetadata128 that was generated based on the search information associated with a particular input information folder106 (e.g., Shawn Mullins) and the search result information145 to identify searchresult information entries121 as target information entries123. The target information entries123 may be in the form of digitalcontent link information268 or digital content subscribeinformation270 or requestedinformation272 or digital contentstreaming link information274.
• At operation382, therecommendation engine54 parses the search result information145 to identifyadditional target information147. For example, therecommendation engine54 may use theprofile information130 to parse the searchresult information entries121 and associate a recommendation with each of the searchresult information entries121. Therecommendation engine54 may use a star scheme with the highest recommendation being four stars. In addition, the recommendation engine may determine that a searchresult information entry121 that is associated with a recommendation that exceeds a predetermined threshold is identified a target information entry123. For example, a searchresult information entry121 that is associated with a recommendation of three stars may exceed a predetermined threshold of two stars thereby triggering identification as a target information entry123.
• It will be appreciated that the above describedmethod308 to retrieve search result information145 may include launchingmultiple media modules56 to retrieve the search result information145. It will further be appreciated that theconfiguration module50 is not required to utilize amedia module56 to retrieve the search result information145 but may communicate directly with the data sources via an application processing interface.
• FIG. 16 is a flowchart illustrating amethod312, according to an embodiment, to retrievedigital content140. Illustrated on the left panel are operations performed by the server machine12 (e.g., digital content hub), and illustrated on the right panel are operations performed by thedata source18. At the left panel and illustrated on the left are operations performed by theprocessing module52 and illustrated on the right are operations performed by themedia module56. The method400 commences atoperation402 at the server machine12 (e.g., digital content hub) with theprocessing module52 identifyingdigital content140 to retrieve. For example, theprocessing module52 may use thepurchase metadata134 and thestorage metadata136 to determine whether to retrievedigital content140 identified by digitalcontent link information268. Atoperation404, theprocessing module52 launches theappropriate media modules56 to retrieve thedigital content140. Atoperation406, at the server machine12 (e.g., digital content hub), theprocessing module52 communicates commands including a query for adigital content140 via themedia module56. Atoperation408, themedia module56 receives and communicates the query to theappropriate data source18.
• Atoperation410, at thedata source18, the query is received and atoperation412, thedata source18 communicates thedigital content140 to the server machine12 (e.g., digital content hub).
• Atoperation414, at the server machine12 (e.g., digital content hub), themedia module56 receives thedigital content140. At operation416, theprocessing module52 stores the receiveddigital content140 in the appropriateoutput information folder250. For example, a Shawn Mullins music video would be stored in the Shawn Mullins folder. Atoperation417, theprocessing module52 generates remote command information133 responsive to receipt of thedigital content140. For example, theprocessing module52 may generate the digital content identifier260 for the Shawn Mullins music video, themedia module identifier262 to identify theiTunes media module56 andremote commands264 to command theiTunes media module56.
• At operation418, theprocessing module52, subscribes to a feed fordigital content140. For example, subscription to the feed may result in receiving thedigital content140 as it is released. Atoperation420, themedia module56 communicates the subscription to theappropriate data source18.
• Atoperation422, at thedata source18, the subscription is received and atoperation424, thedata source18 communicates or publishes thedigital content140 to the server machine12 (e.g., digital content hub) as it becomes available. Atoperation426, at the server machine12 (e.g., digital content hub), themedia module56 receives thedigital content140. Atoperation428, theprocessing module52 stores the publisheddigital content140 in the appropriateoutput information folder250. Atoperation430, theprocessing module52 may generate remote command information258 for the receiveddigital content140 and store the remote command information258 in the appropriateoutput information folder250.
• It will be appreciated thatmultiple media modules56 may be launched to retrieve thedigital content140. It will further be appreciated that theconfiguration module50 need not utilize amedia module56 to retrieve thedigital content140 but may communicate directly with thedata sources18 via an application processing interface.
• Further, while the above described embodiment of themethod312 describes a subscription for thedigital content140 that may be communicated to the data source (e.g., iTunes Store) via the media module56 (e.g., iTunes) it will be appreciated that the subscription may include a criterion to retrieve thedigital content140. For example, the criterion to retrieve the digital content may include search information158 (e.g., release information208) and/or filter information160 (e.g., purchaseinformation212 and/or storage information214), and/or an authorization to push thedigital content140 based on a recommendation of the data source18 (e.g., iTunes Store).
• FIG. 17 is a flowchart illustrating amethod402, according to an embodiment, to identify digital content to retrieve. Atdecision operation450, at the server machine12 (e.g., digital content hub) theprocessing module52 determines whether the next target information entry123 is a digitalcontent link information268. If the target information entry123 is digitalcontent link information268, then a branch is made todecision operation454. Otherwise, processing continues atdecision operation452.
• Atdecision operation452, theprocessing module52 determines if the target information entry123 is a link to subscribe to digital content140 (e.g., digital content subscribe information270). If the target information entry123 is digital content subscribeinformation270, then a branch is made todecision operation454. Otherwise, processing continues atdecision operation464.
• Atdecision operation454, theprocessing module52 determines if a purchase is required to request thedigital content140 or to subscribe for thedigital content140. If a purchase is required, then a branch is made to decision operation456. Otherwise, if no purchase is required or purchase may be delayed until after the request or subscription, processing continues atdecision operation458.
• At decision operation456, theprocessing module52 determines if a purchase limitation is exceeded based on a predetermined price limitation. If the purchase limitation is exceeded, then a branch is made tooperation460. Otherwise, processing continues atdecision operation458.
• Atdecision operation458, theprocessing module52 determines if a predetermined storage limitation is exceeded based on a storage requirement of thedigital content140. If the storage limitation is exceeded, then a branch is made todecision operation464. Otherwise, a branch is made tooperation460.
• Atoperation460, theprocessing module52 registers thedigital content140 for retrieval. Atoperation462, theprocessing module52 communicates an alert that includes notification information to a predetermined network address based onalert information210. For example, theprocessing module52 may communicate an email to an email address that includes that notifies the recipient of receipt of thedigital content140.
• Atdecision operation464, theprocessing module52 determines if there are more target information entries123. If there are more target information entries123, a branch is made tooperation466 where theprocessing module52 advances to the next target information entry123. Otherwise, processing ends.
• FIG. 18 is a flowchart illustrating amethod320, according to an embodiment, to communicate digital content140 a portable client machine32 (e.g., iPod). Themethod320 commences at the client machine22 (e.g., control node) with thedistribution module60 using themedia module identifier262 to launch theappropriate media module56. For example, themethod500 may commence responsive to receiving thedigital content140 from the server machine12 (e.g., digital content hub) or responsive to a periodic scheduling. Atoperation504, thedistribution module60 may utilize theremote commands264 and the digital content identifier260 to command themedia module56 to communicate thedigital content140 that is identified to the portable client machine32 (e.g., iPod). Atoperation506, themedia module56 communicates thedigital content140 to the portable client machine32 (e.g., iPod) and the method ends.
• FIG. 19 is a flowchart illustrating amethod506, according to an embodiment, to receiveinput information102 from a portable client machine32 (e.g., iPod) and communicate theinput information102 to the server machine12 (e.g., digital content hub). At operation508, themethod506 commences with thecommunication module58 launching theappropriate media module56. For example, thecommunication module58 may launch themedia module56 responsive to detecting a connection of theportable client machine32 to theclient machine22. Other embodiments may require the user to requestinput information102 from theportable client machine32. At operation510, thecommunication module58 scrapes theinput information102 from the display generated by themedia module56. At operation512, thecommunication module58 communicates theinput information102 to the server machine12 (e.g., hub node) and the method ends.
• FIG. 20 is a diagram illustrating auser interface550, according to an embodiment, to receiveinput information102. Theuser interface550 includes an interface control in the form of aninput box551 to receive afolder title200 and other interface controls to receivetarget identification information202. Thefolder title200 may be used to identify a pair of information folders including theinput information folder108 and theoutput information folder106.
• The interface controls to receive thetarget identification information202 include a pull downmenu552, aninput box554, and input checkboxes562-598. The pull downmenu552 may be used to receive a selection of an artist, creation, or category. Theinput box554 may be used to receive the name of an artist, the name of a creation, or the name of a category.
• The input checkboxes562-598 may be used to receive requests for different types (e.g., media types) of digital content140 (e.g., music videos, digital sample, albums, streaming, image) and information (e.g., ticket availability). The input checkboxes562-568 may be used to receive requests for a music video. Theinput checkbox562 may be used to receive a request to retrieve information about music videos for the named artist. Similarly, theinput checkbox564 may be used to receive a request to retrievedigital content140 and theinput checkbox566 may be used to receive an authorization to purchase (e.g., if necessary for retrieval). Finally, theinput checkbox568 may be used to receive a request to communicate an alert responsive retrieval of a music video.
• The input checkboxes570-574 may be used to receive the same requests for a digital sample. The input checkboxes576-582 may be used to receive the same requests for an album. Theinput checkboxes584 may be used to receive the request for information fordigital content140 that is streamed (e.g., links to initiate streaming). Finally, theinput checkbox596 may be used to receive a request for information about ticket availability.
• It will be appreciated that theuser interface500 is merely an example and thattarget identification information202 may be received for other types of digital content140 (e.g., multimedia presentations, slide shows, television episodes, movies, flash video files, etc.).
• FIG. 21 is a diagram illustrating auser interface600, according to an embodiment, to receivedata source information206,search frequency information204 andrelease information208. Theuser interface600 may be presented to the user responsive to receiving a request to retrieve search result information145 (e.g., inputcheckboxes562,570,576,584,588,596) via theuser interface550. The data sourceinformation206 may be received through input checkboxes604-6145 that respectively identify requests to retrieve search result information145 anddigital content140 from the identified data sources18. Associated with thecheckbox612 is acheckbox613 to request communication of thedigital content140 to the portable client machine(s)32 (e.g., iPod). Thesearch frequency information204 may be received via input checkbox616-620. Thesearch frequency information204 may be used to schedule searches at a predetermined period. Therelease information208 may be received from theinput checkbox624 and626. Theinput checkbox624 may be used to receive a request to retrieve all releases of the digital content. Theinput checkbox626 may be used to receive a request to retrieve the latest released digital content.
• FIG. 22 is a diagram illustrating auser interface650, according to an embodiment, to receivestorage information214. Theuser interface650 may be presented to the user responsive to receiving a request to retrievedigital content140 of a specified type (e.g., inputcheckboxes564,572,578,590) via theuser interface550. Theinput box654 may be used to receive a storage maximum limitation. Theinput box656 may be used to receive a storage maximum per day limitation. Theinput box658 may be used to receive a storage rule limitation. The respective storage limitations may be used by the server machine12 (e.g., digital content hub) to block retrieval ofdigital content140 based on the storage requirements of thedigital content140.
• FIG. 23 is a diagram illustrating auser interface670, according to an embodiment, to receivepurchase information212. Theuser interface670 may be presented to the user responsive to receiving a request to purchasedigital content140 of a specified type (e.g., inputcheckboxes566,580,592) via theuser interface550. Theinput box674 may be used to receive a one time purchase not to exceed limitation. Theinput box674 may be used to receive a one time purchase not to exceed limitation. Theinput box676 may be used to receive a one month subscription not to exceed limitation. Theinput box678 may be used to receive a year subscription not to exceed limitation. Theinput box680 may be used to receive a total purchases purchase not to exceed limitation. Theinput box682 may be used to receive a purchase rule limitation. The respective purchase limitations may be used by the server machine12 (e.g., digital content hub) to block retrieval ofdigital content140 based on the purchase requirements of thedigital content140.
• FIG. 24 is the diagram illustrating auser interface700, according to an embodiment, to receivealert information210. Theuser interface700 may be presented to the user responsive to receiving a request to communicate an alert (e.g., inputcheckboxes568,574,582,594,598) via theuser interface550. Thealert information210 may be received with pull downmenus712,716, and720 respectively receiving an operation status (e.g., enabled/disabled) for the respective communication channels (e.g., email, instant messaging, cell phone). It will be appreciated that thealert information210 may be received for any communication channel capable of communicating a message (e.g., voice mail, VOIP, etc.). Thealert information210 may further be received frominput boxes714,718, and722 respectively receiving network addresses for the respective communication channels.
• FIG. 25 is a diagram illustrating auser interface750, according to an embodiment, to receiverecommendation information162,global purchase information164 andglobal storage information166. Therecommendation information162 may be received frominput checkbox752 andinput boxes754,756. Theinput checkbox752 may receive an operation status (e.g., enabled/disabled). Receiving an enabled operation status triggers therecommendation engine54 to parse the search result information145 and make recommendations, as previously described. Theinput boxes754,756 may receive a predetermined criterion that is used to determine whetherdigital content140 is retrieved based on a recommendation. For example, theinput box754 is illustrated as receiving a predetermined criterion of three. Accordingly, in one embodiment, a searchresult information entry121 associated with a recommendation of three stars or greater triggers retrieval of the correspondingdigital content140. Similarly, theinput box756 receives a predetermined criterion to determine whether a recommendation to retrieve digital that requires a purchase may be retrieved based on the recommendation. Accordingly, in one embodiment, a searchresult information entry121 associated with a recommendation of four stars or greater triggers payment and retrieval of the correspondingdigital content140.
• Theglobal purchase information164 may be received via input boxes758-764 that respectively receive predetermined criteria or purchasing limitations, as previously described but, in the present instance, as applied to all purchases and not to purchases of a type ofdigital content140. Theglobal purchase information164 further includes input boxes766-772 for receiving payment method information that may be used to purchase thedigital content140 via a payment system (e.g., PayPal, etc).
• FIG. 26 is a diagram illustrating auser interface800, according to an embodiment, to display folder information. The folder information may include information contained in theinput information folder108,output information folder106, andreceipt information810. Illustrated from right to left are tabs802-808. Thetab802 may be selected to view the information contained in theinput information folder108 and information contained in theoutput information folder106 associated with an artist (e.g., “Shawn Mullins”). Similarly, thetab804 may be selected to view the folder information for a creation (e.g., television series “24”) and thetab806 may be selected to view the folder information for the category (e.g., “Best Pictures of the Year”). Finally, thetab808 may be selected to view folder information includingreceipt information810 for purchase of thedigital content140.
• FIG. 27 is a diagram illustrating auser interface850, according to an embodiment, to present information contained in anoutput information folder106. Theoutput information folder106 includes text blocks852,856,858,860,862,864, and868 for describingtarget information147 for the artist, Shawn Mulllins anddigital content140 that has been retrieved from thedata sources18 for the same artist. The text blocks may include a recommendation (e.g. ****). The text blocks852,856,858,860 describe digitalcontent link information268, according to an embodiment. Thetext block862 describes digital contentstreaming link information274, according to an embodiment. Thetext block862 includes auser interface element866 that may be selected to initiate streaming.
• Thetext block868 includes information that has been identified via requested information272 (e.g., ticket availability information), according to an embodiment. Auser interface element869 may be selected for further information about ticket availability.
• Theuser interface850 further includes text blocks870,872, and874 describingdigital content140 that was retrieved, according to an embodiment.
• FIG. 28 is a diagram illustrating auser interface900, according to an embodiment, to presentreceipt information810. Thereceipt information810 includes afolder title column902, associated with a set of payments fordigital content140, and method ofpayment information906. Appearing under thefolder title column902 are thefolder titles200, as previously described. Illustrated are three payments fordigital content140 to respective data sources18 (e.g., awarstore.com, iTunes.com) aggregated intosingle transaction904. For example, the server machine12 (digital content hub) may communicate with the payment system20 (e.g., PayPal) and the server machines36 (e.g., data sources18) to conclude a single charge on the users financial instrument (e.g., VISA, ATM, EFT, etc.) that balances a first payment to a server machine36 (e.g., awarestore.com) and a second payment to a different server machine36 (e.g., iTunes.com). Accordingly, the digital content hub provides the advantage of simplifying payment fordigital content140 by automatically aggregating multiple payments to financiallyindependent data sources18 and a single charge to a financial instrument into a single transaction.
• It will be appreciated that other embodiments may receive the above describedinput information102 utilizing an interface other than a user interface. For example, theinput information102 may be received via an audio interface, a machine interface, a kinetic interface (e.g., Wii), a graphical user interface or any other type of interface that may receive theinput information102.
• FIG. 29 shows a diagrammatic representation of machine in the example form of acomputer system1000 within which a set of instructions, for causing the machine to perform any one or more of the methodologies discussed herein, may be executed. In alternative embodiments, the machine operates as a standalone device or may be connected (e.g., networked) to other machines. In a networked deployment, the machine may operate in the capacity of a server or a client machine in server-client network environment, or as a peer machine in a peer-to-peer (or distributed) network environment. The machine may be a server computer, a client computer, a personal computer (PC), a tablet PC, a set-top box (STB), a Personal Digital Assistant (PDA), a cellular telephone, a web appliance, a network router, switch or bridge, or any machine capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that machine. Further, while only a single machine is illustrated, the term “machine” shall also be taken to include any collection of machines that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein.
• Theexample computer system1000 includes a processor1002 (e.g., a central processing unit (CPU) a graphics processing unit (GPU) or both), amain memory1004 and astatic memory1006, which communicate with each other via abus1008. Thecomputer system1000 may further include a video display unit1010 (e.g., a liquid crystal display (LCD) or a cathode ray tube (CRT)). Thecomputer system1000 also includes an alphanumeric input device1012 (e.g., a keyboard), a cursor control device1014 (e.g., a mouse), adisk drive unit1016, a signal generation device1018 (e.g., a speaker) and anetwork interface device1020.
• Thedisk drive unit1016 includes a machine-readable medium1022 on which is stored one or more sets of instructions (e.g., software1024) embodying any one or more of the methodologies or functions described herein. Thesoftware1024 may also reside, completely or at least partially, within themain memory1004 and/or within theprocessor1002 during execution thereof by thecomputer system1000, themain memory1004 and theprocessor1002 also constituting machine-readable media.
• Thesoftware1024 may further be transmitted or received over anetwork1026 via thenetwork interface device1020.
• While the machine-readable medium1022 is shown in an example embodiment to be a single medium, the term “machine-readable medium” should be taken to include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) that store the one or more sets of instructions. The term “machine-readable medium” shall also be taken to include any medium that is capable of storing, encoding or carrying a set of instructions for execution by the machine and that cause the machine to perform any one or more of the methodologies of the present disclosure. The term “machine-readable medium” shall accordingly be taken to include, but not be limited to, solid-state memories, optical and magnetic media, and carrier wave signals.
Modules, Components and Logic
• Certain embodiments are described herein as including logic or a number of modules, components or mechanisms. A module, logic, component or mechanism (herein after collectively referred to as a “module”) may be a tangible unit capable of performing certain operations and is configured or arranged in a certain manner. In example embodiments, one or more computer systems (e.g., a standalone, client or server computer system) or one or more components of a computer system (e.g., a processor or a group of processors) may be configured by software (e.g., an application or application portion) as a “module” that operates to perform certain operations as described herein.
• In various embodiments, a “module” may be implemented mechanically or electronically. For example, a module may comprise dedicated circuitry or logic that is permanently configured (e.g., within a special-purpose processor) to perform certain operations. A module may also comprise programmable logic or circuitry (e.g., as encompassed within a general-purpose processor or other programmable processor) that is temporarily configured by software to perform certain operations. It will be appreciated that the decision to implement a module mechanically, in the dedicated and permanently configured circuitry, or in temporarily configured circuitry (e.g., configured by software) may be driven by cost and time considerations.
• Accordingly, the term “module” should be understood to encompass a tangible entity, be that an entity that is physically constructed, permanently configured (e.g., hardwired) or temporarily configured (e.g., programmed) to operate in a certain manner and/or to perform certain operations described herein. Considering embodiments in which modules or components are temporarily configured (e.g., programmed), each of the modules or components need not be configured or instantiated at any one instance in time. For example, where the modules or components comprise a general-purpose processor configured using software, the general-purpose processor may be configured as respective different modules at different times. Software may accordingly configure the processor to constitute a particular module at one instance of time and to constitute a different module at a different instance of time.
• Modules can provide information to, and receive information from, other modules. Accordingly, the described modules may be regarded as being communicatively coupled. Where multiple of such modules exist contemporaneously, communications may be achieved through signal transmission (e.g., over appropriate circuits and buses) that connect the modules. In embodiments in which multiple modules are configured or instantiated at different times, communications between such modules may be achieved, for example, through the storage and retrieval of information in memory structures to which the multiple modules have access. For example, a one module may perform an operation, and store the output of that operation in a memory device to which it is communicatively coupled. A further module may then, at a later time, access the memory device to retrieve and process the stored output. Modules may also initiate communications with input or output devices, and can operate on a resource (e.g., a collection of information).
• Thus, methods and systems to retrieve search result information and digital content have been described. Although the present disclosure has been described with reference to specific example embodiments, it will be evident that various modifications and changes may be made to these embodiments without departing from the broader spirit and scope of the disclosure. Accordingly, the specification and drawings are to be regarded in an illustrative rather than a restrictive sense.
• The Abstract of the Disclosure is provided to comply with 37 C.F.R. § 1.72(b), requiring an abstract that will allow the reader to quickly ascertain the nature of the technical disclosure. It is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. In addition, in the foregoing Detailed Description, it can be seen that various features are grouped together in a single embodiment for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed embodiments require more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter lies in less than all features of a single disclosed embodiment. Thus the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separate embodiment.

Claims (20)

What is claimed is:

1. A method comprising:

receiving input information identifying a plurality of data sources from which to retrieve digital content;

retrieving search result information, over a network, from the plurality of data sources based on the input information;

retrieving the digital content, over the network, from at least one of the data sources based on the search result information; and

communicating the digital contentto a client machine.

2. The method ofclaim 1, further including communicating the digital content from the client machine to a portable client machine.

3. The method ofclaim 1, wherein the receiving of the input information includes at least one of receiving artist information, receiving creation information, or receiving category information.

4. The method ofclaim 3, wherein the receiving of the artist information includes at least one of receiving a request for a type of artist, receiving a request for an artist, receiving a request for ticket information, or receiving a request for digital sample information, wherein the receiving of the creation information includes at least one of receiving a request for digital content that is released or receiving a request for a multimedia presentation.

5. The method ofclaim 1, wherein the retrieving of the search result information includes at least one of communicating a query to at least one data source to receive the search result information or communicating a subscription to at least one data source to receive the search result information.

6. The method ofclaim 1, wherein the retrieving of the search result information is performed periodically based on a predetermined period.

7. The method ofclaim 1, wherein the retrieving of the search result information includes filtering the search result information based on a media type, wherein the media type includes at least one of a music video, a digital sample, or a streaming video.

8. The method ofclaim 1, including determining whether payment is required after the digital content is retrieved from the data source.

9. The method ofclaim 1, wherein the retrieving the digital content includes at least one of communicating a query to at least one data source to receive the digital content or communicating a subscription to at least one data source to receive the digital content.

10. The method of theclaim 1, wherein the retrieving of the digital content includes communicating a subscription to at least one data source and receiving the digital content that is pushed from the data source based on a recommendation of the data source.

11. The method ofclaim 1, wherein the retrieving of the digital content includes identifying whether payment is required to retrieve the digital content from the data source.

12. The method ofclaim 1, wherein the retrieving of the digital content includes purchasing the digital content.

13. The method ofclaim 1, wherein the retrieving of the digital content includes determining whether a predetermined criterion is exceeded.

14. The method ofclaim 13, wherein the predetermined criterion includes at least one of a storage limitation or a purchase limitation.

15. The method ofclaim 1, including communicating, on a predetermined communication channel, an alert that the digital content has been retrieved.

16. A system comprising:

a configuration module to receive input information to identify a plurality of data sources from which to retrieve digital content and to retrieve search result information, over a network, from the plurality of data sources based on the input information; and

a processing module to retrieve the digital content, over the network, from at least one of the data sources based on the search result information and to communicate the digital content to a client machine.

17. The system ofclaim 16, further including a distribution module, at the client machine, to communicate the digital content to a portable client machine.

18. The system ofclaim 16, wherein the input information includes at least one of artist information, creation information, and category information.

19. The system ofclaim 18, wherein the artist information includes at least one of a request for a type of artist, a request for an artist, a request for ticket information, and a request for digital sample information, wherein the creation information is includes at least one of a request for digital content that is released and a request for a multimedia presentation.

20. The system ofclaim 16, wherein the configuration module is to communicate a query to at least one data source to receive the search result information and wherein the configuration module communicates a subscription to at least one data source to receive the search result information.

Images