Field of the Disclosure
The present disclosure relates to providing product information and, more particularly, to providing product information during multimedia programs.
Description of the Related Art
Commercially available products may be displayed or mentioned in multimedia programs. While viewing or listening to multimedia programs, consumers may become aware of a product of interest to them.
In one aspect, a disclosed method for providing product information over a multimedia content distribution network (MCDN) includes receiving multimedia content from the MCDN, including receiving product metadata coordinated in time with the multimedia content. Responsive to receiving a user notification at or proximate to a time when a placed product occurs in the multimedia content, the method may further include determining coordinated product metadata for the placed product based on the time, and using the coordinated product metadata to obtain product information for the placed product.
In some embodiments, the method may further include outputting product information for the placed product to the user. The product information may include information from a vendor of the placed product. The method may further include outputting to the user a list of placed products occurring in the multimedia content when the user notification is received, and receiving a command from the user indicating selection of one of the placed products on the list.
In some instances, the method may still further include receiving a request from the user to purchase the placed product. The method may also include validating the identity of the user. Validating the identity of the user may include determining the global-positioning system (GPS) location of a wireless telephony device registered to the user. In some cases, validating the identity of the user may include determining the network identity of a multimedia handling device (MHD) registered to the user, while the MHD may be used for said receiving and said outputting of the multimedia content.
In another aspect, a disclosed system for accessing product information over an MCDN includes a processor, and storage accessible to the processor, including processor executable instructions. The instructions may be executable to decode multimedia content received from the MCDN, wherein product metadata coordinated in time with the multimedia content is also received from the MCDN, and respond to receiving a user alert indicating product interest at a time when a placed product occurs in the multimedia content by determining the placed product from the coordinated product metadata. The instructions may further be executable to associate the user alert with the placed product.
In one embodiment, the system further includes instructions executable to respond to said instructions to associate by obtaining product information for the placed product. The instructions may further be executable to output the product information to a display and respond to receiving a command from the user to purchase the placed product by initiating a purchase of the placed product. The instructions may still further be executable to apply a charge for the price of the placed product and cause the placed product to be delivered to the user. An MHD registered to the user under a service contract may be used to execute said instructions to decode multimedia content, while said instructions executable to apply a charge may include program instructions executable to charge a user account according to the service contract.
In some embodiments, the instructions are further executable to validate an identity of the user. The instructions executable to validate may include instructions executable to determine the GPS location of a wireless telephony device registered to the user. The instructions executable to validate may include instructions executable to determine a network identity of the MHD registered to the user.
In yet a further aspect, computer-readable memory media, including processor executable instructions for distributing product information over an MCDN, may include instructions executable to send multimedia content and product metadata coordinated in time with the multimedia content to a client an MHD, and respond to receiving a request for product information, at a time when a placed product occurs in the multimedia content by using the coordinated product metadata to obtain product information for the placed product. The instructions may further be executable to send the product information to the client MHD.
In some embodiments, the instructions are executable to respond to receiving a request to purchase the placed product by causing the placed product to be ordered on behalf of the user. The instructions may further be executable to validate an identity of the user, including obtaining user information from an account for MCDN services. A price of the placed product may be charged to the account for MCDN services. The instructions may still further be executable to charge the user for a price of the placed product and send a receipt for the purchase to the user.
In the following description, details are set forth by way of example to facilitate discussion of the disclosed subject matter. It should be apparent to a person of ordinary skill in the field, however, that the disclosed embodiments are exemplary and not exhaustive of all possible embodiments. Throughout this disclosure, a hyphenated form of a reference numeral refers to a specific instance of an element and the un-hyphenated form of the reference numeral refers to the element generically or collectively. Thus, for example, widget 12-1 refers to an instance of a widget class, which may be referred to collectively as widgets 12 and any one of which may be referred to generically as a widget 12.
Turning now to the drawings,
The elements of MCDN 100 illustrated in
As depicted in
Access network 130 demarcates clients 120 and service provider 121, and provides connection path(s) between clients 120 and service provider 121. In some embodiments, access network 130 is an Internet protocol (IP) compliant network. In some embodiments, access network 130 is, at least in part, a coaxial cable network. It is noted that in some embodiments of MCDN 100, access network 130 is owned and/or operated by service provider 121. In other embodiments, a third party may own and/or operate at least a portion of access network 130.
In IP-compliant embodiments of access network 130, access network 130 may include a physical layer of unshielded twist pair cables, fiber optic cables, or a combination thereof MCDN 100 may include digital subscriber line (DSL) compliant twisted pair connections between clients 120 and a node (not depicted) in access network 130 while fiber, cable or another broadband medium connects service provider resources to the node. In other embodiments, the broadband cable may extend all the way to clients 120.
As depicted in
In
Thus, the content provided by service provider 121 encompasses multimedia content that is scheduled in advance for viewing by clients 120 via access network 130. Such multimedia content, also referred to herein as “scheduled programming,” may be selected using an electronic programming guide (EPG). Some scheduled programs may be “regularly” scheduled programs, which recur at regular intervals or at the same periodic date and time (i.e., daily, weekly, monthly, etc.).
As will be discussed in detail below, commercially available products may be placed or included in multimedia content provided for consumption by a user of client 120. As used herein, “consumption” refers to viewing, listening, recording, copying, obtaining, selecting, or any other actions associated with receipt of multimedia content by the user. Product information for placed products may be provided to the user in response to receiving a notification of product interest by the user. Furthermore, product metadata coordinated in time with the multimedia content may be used to provide product information for the placed products. Such product information may include specifications, price, availability, warranty, and other related information for the products.
Acquired content is provided to content delivery server 160 via backbone network 170 and switching network 140. Content may be delivered from content delivery server 160 to clients 120 via switching network 140 and access network 130. Content may be compressed, encrypted, modulated, demodulated, and otherwise encoded or processed at content acquisition resources 180, content delivery server 160, or both. Although
Although service provider 121 is depicted in
Applications provided by application server 150 may be downloaded and hosted on other network resources including, for example, content delivery server 160, switching network 140, and/or on clients 120. Application server 150 is configured with a processor and storage media (not shown in
Further depicted in
Turning now to
In
Clients 120 as depicted in
Clients 120 are further shown with their respective remote control 128, which is configured to control the operation of MHD 125 by means of a user interface (not shown in FIG. 2) displayed on display 126. Remote control 128 of client 120 is operable to communicate requests or commands wirelessly to MHD 125 using infrared (IR) or radio frequency (RF) signals. MHDs 125 may also receive requests or commands via buttons (not depicted) located on side panels of MHDs 125.
MHD 125 is enabled and configured to process incoming multimedia signals to produce audio and visual signals suitable for delivery to display 126 and any optional external speakers (not depicted). Incoming multimedia signals received by MHD 125 may be compressed and/or encrypted, digital or analog, packetized for delivery over packet switched embodiments of access network 130 or modulated for delivery over cable-based access networks. In some embodiments, MHD 125 may be implemented as a stand-alone set top box suitable for use in a co-axial or IP-based MCDN.
Referring now to
In the embodiment depicted in
In embodiments suitable for use in IP based content delivery networks, MHD 125, as depicted in
Video and audio streams 332 and 334, as output from transport unit 330, may include audio or video information that is compressed, encrypted, or both. A decoder unit 340 is shown as receiving video and audio streams 332 and 334 and generating native format video and audio streams 342 and 344. Decoder 340 may employ any of various widely distributed video decoding algorithms including any of the Motion Pictures Expert Group (MPEG) standards, Windows Media Video (WMV) standards including WMV 9, which has been standardized as Video Codec-1 (VC-1) by the Society of Motion Picture and Television Engineers. Similarly decoder 340 may employ any of various audio decoding algorithms including Dolby® Digital, Digital Theatre System (DTS) Coherent Acoustics, and Windows Media Audio (WMA).
The native format video and audio streams 342 and 344 as shown in
Storage 310 encompasses persistent and volatile media, fixed and removable media, and magnetic and semiconductor media. Storage 310 is operable to store instructions, data, or both. Storage 310 as shown includes sets or sequences of instructions, namely, an operating system 312, a remote control (RC) application program identified as RC module 314, and a product metadata application 318. Operating system 312 may be a UNIX or UNIX-like operating system, a Windows® family operating system, or another suitable operating system. In some embodiments, storage 310 is configured to store and execute instructions provided as services to client 120 by application server 150, as mentioned previously.
Referring now to
Multimedia content may be received from the MCDN, along with product metadata coordinated in time with the multimedia content (operation 402). The multimedia content may be a video or television program, and the product metadata may be indexed to each frame of the received program. The product metadata may provide an indication of which products occur in the multimedia content, and may be used to obtain additional product information such as specifications, price, availability, warranty, and other related information for the products. The multimedia content may then be output to a display device (operation 404). In some embodiments of operation 404, a video program received via access network 130 is displayed on display 126.
Input from a user receiving the multimedia content may be received at or proximate to a time when the placed product occurs in the multimedia content (operation 406). In some embodiments, the user may use remote control 128 to provide a notification of interest in a placed product. The placed product may be determined from the coordinated product metadata (operation 408). The product metadata may be determined by coordinating the point in time that the user input, such as a user alert, was received in operation 406. In some embodiments, a query to database server 190 is performed to query product metadata. Product information may be obtained and output to the user (operation 410). In some cases product information is displayed to the user on display 126. Outputting product information to the user may further include outputting a list of placed products occurring in the multimedia content at the time a user notification was received. In response to viewing the list, the user may select one or more products from the list for which product information may be provided. The coordinated product metadata may be used to obtain product information, which may include price, availability, specifications, warranty, and other information pertaining to the desired product. In some cases, product information is obtained from a vendor of the placed product in operation 410.
A request may then be received from the user to purchase the placed product (operation 412). A decision may be made whether or not the user is a valid user, or has been validated (operation 414). In one embodiment, validation of the user is performed by determining a GPS location of a wireless telephony device registered to the user. In some cases, user validation is performed by determining the network identity of an MHD registered to the user, such as the MHD used for receiving, decoding, and outputting the multimedia content. If the result of operation 414 is NO, then the user request for purchase may be denied (operation 416). If the result of operation 414 is YES, then the user may be charged for the selected product and method 400 may cause the product to be ordered for the user (operation 418). In one embodiment, the user may be charged for the product on an account for MCDN services, which may be governed by a service contract with the user. In other embodiments, the user may provide applicable payment via other methods such as credit card, direct billing, or the like.
Referring now to
Multimedia content may be sent via the MCDN to a client MHD, along with product metadata coordinated in time with the multimedia content (operation 502). A request for product information may be received at a time when a placed product occurs in the multimedia content (operation 504). The product metadata may be used to obtain product information for the placed product and the product information may be sent to the client MHD (operation 506). In some cases, the point in time of the request may be used to coordinate the product metadata. A request to purchase the placed product may be received and a client account for MCDN services may be charged (operation 508). In some embodiments, an option to separately pay for the desired placed product may be provided. Method 500 may then cause the placed product to be delivered to the user (operation 510). In one embodiment, shipping of a physical product is initiated in operation 510. In some cases, the product may include digital multimedia content, which may be sent to the user using MCDN 100. A receipt for the purchase may be sent to the user (operation 512). The receipt may be a printed hardcopy or may be sent in electronic form.
To the maximum extent allowed by law, the scope of the present disclosure is to be determined by the broadest permissible interpretation of the following claims and their equivalents, and shall not be restricted or limited to the specific embodiments described in the foregoing detailed description.
Number | Name | Date | Kind |
---|---|---|---|
5065345 | Knowles et al. | Nov 1991 | A |
5109482 | Bohrman | Apr 1992 | A |
5204947 | Bernstein et al. | Apr 1993 | A |
5438355 | Palmer | Aug 1995 | A |
5539871 | Gibson | Jul 1996 | A |
5561708 | Remillard | Oct 1996 | A |
5596705 | Reimer et al. | Jan 1997 | A |
5708845 | Wistendahl et al. | Jan 1998 | A |
5790677 | Fox | Aug 1998 | A |
5872589 | Morales | Feb 1999 | A |
5903816 | Broadwin et al. | May 1999 | A |
5929850 | Broadwin et al. | Jul 1999 | A |
5961603 | Kunkel et al. | Oct 1999 | A |
5973685 | Schaffa et al. | Oct 1999 | A |
6005561 | Hawkins et al. | Dec 1999 | A |
6016141 | Knudson et al. | Jan 2000 | A |
6215417 | Krass et al. | Apr 2001 | B1 |
6253193 | Ginter et al. | Jun 2001 | B1 |
6275989 | Broadwin et al. | Aug 2001 | B1 |
6445306 | Trovato et al. | Sep 2002 | B1 |
6490580 | Dey et al. | Dec 2002 | B1 |
6496981 | Wistendahl et al. | Dec 2002 | B1 |
6505348 | Knowles et al. | Jan 2003 | B1 |
6587835 | Treyz et al. | Jul 2003 | B1 |
6615408 | Kaiser et al. | Sep 2003 | B1 |
6637029 | Maissel et al. | Oct 2003 | B1 |
6718551 | Swix et al. | Apr 2004 | B1 |
6788800 | Carr et al. | Sep 2004 | B1 |
7142198 | Lee | Nov 2006 | B2 |
7343617 | Katcher et al. | Mar 2008 | B1 |
7367042 | Dakss et al. | Apr 2008 | B1 |
7450163 | Rothschild | Nov 2008 | B2 |
7454380 | Garahi et al. | Nov 2008 | B2 |
7456872 | Rothschild | Nov 2008 | B2 |
7503059 | Rothschild | Mar 2009 | B1 |
7692580 | Rothschild | Apr 2010 | B2 |
7896242 | Rothschild | Mar 2011 | B2 |
7917285 | Rothschild | Mar 2011 | B2 |
8739236 | Weaver | May 2014 | B1 |
20020069415 | Humbard et al. | Jun 2002 | A1 |
20020083451 | Gill et al. | Jun 2002 | A1 |
20020162118 | Levy et al. | Oct 2002 | A1 |
20030014754 | Chang | Jan 2003 | A1 |
20030101100 | Sako et al. | May 2003 | A1 |
20040109087 | Robinson et al. | Jun 2004 | A1 |
20040177008 | Yang | Sep 2004 | A1 |
20040215526 | Luo et al. | Oct 2004 | A1 |
20050086682 | Burges et al. | Apr 2005 | A1 |
20050114149 | Rodriguez et al. | May 2005 | A1 |
20050132420 | Howard et al. | Jun 2005 | A1 |
20050137958 | Huber | Jun 2005 | A1 |
20050160469 | Chiu et al. | Jul 2005 | A1 |
20050251732 | Lamkin et al. | Nov 2005 | A1 |
20050289050 | Narayanan et al. | Dec 2005 | A1 |
20060004778 | Lamkin et al. | Jan 2006 | A1 |
20060100951 | Mylet et al. | May 2006 | A1 |
20060114337 | Rothschild | Jun 2006 | A1 |
20060114338 | Rothschild | Jun 2006 | A1 |
20060114514 | Rothschild | Jun 2006 | A1 |
20060259930 | Rothschild | Nov 2006 | A1 |
20060277316 | Wang et al. | Dec 2006 | A1 |
20070022465 | Rothschild | Jan 2007 | A1 |
20070045405 | Rothschild | Mar 2007 | A1 |
20070052585 | Rothschild | Mar 2007 | A1 |
20070078732 | Crolley et al. | Apr 2007 | A1 |
20070143775 | Savoor et al. | Jun 2007 | A1 |
20070150375 | Yang | Jun 2007 | A1 |
20070244750 | Grannan et al. | Oct 2007 | A1 |
20070252689 | Rothschild | Nov 2007 | A1 |
20070265006 | Washok et al. | Nov 2007 | A1 |
20080004978 | Rothschild | Jan 2008 | A1 |
20080040767 | McCarthy | Feb 2008 | A1 |
20080109841 | Heather | May 2008 | A1 |
20080126809 | Rothschild | May 2008 | A1 |
20080148317 | Opaluch | Jun 2008 | A1 |
20080178245 | Moons | Jul 2008 | A1 |
20080263602 | Murray et al. | Oct 2008 | A1 |
20080271088 | Robinson et al. | Oct 2008 | A1 |
20080281684 | Stefanik et al. | Nov 2008 | A1 |
20090037949 | Birch | Feb 2009 | A1 |
20090094104 | Anuar | Apr 2009 | A1 |
20090150257 | Abrams et al. | Jun 2009 | A1 |
20090192903 | Weiss et al. | Jul 2009 | A1 |
Number | Date | Country | |
---|---|---|---|
20100153226 A1 | Jun 2010 | US |