US 9,607,330 B2Grant
Peer-assisted shopping
Issue Date:2017-03-28
•40 Claims
•6 Drawing Sheets
Abstract
According to an embodiment of the disclosure, a method for peer-assisted shopping, the method includes initiating, on a first endpoint corresponding to a first user, a display of media content. The method also includes initiating, on the first endpoint, an interactive feature configured to allow the first user to interact with the first endpoint in response to the display of media content. The method further includes initiating, on the first endpoint, an option for the first user to invoke a communication request with at least a second user corresponding to at least a second endpoint. Moreover, the method includes, upon selection of the option, initiating a connection request with the at least a second endpoint.
Metadata
Assignee
- Cinsay, Inc.
Inventors
- Robert K. Spitz
- Sergey Sundukovskiy
- Delfino Galindo, Jr.
- Todd Downing
- Christian Briggs
Application Information
Application Number:US 13/923,089
Filing Date:2013-06-20
Priority Date:2012-06-21
Art Unit:3625
Classifications
IPC:
G06Q30/06
Field of Search:
G06Q 30/06G06Q 30/0641
Patent Drawings (6 sheets)
Description
Cross-Reference to Related Application(s) and Claim of Priority
[0001] The present application claims priority to U.S. Provisional Patent Application Ser. No. 61/662,765, filed Jun. 21, 2012, entitled “PEER-ASSISTED SHOPPING.” The content of the above-identified patent documents is incorporated herein by reference.
Technical Field
[0002] The present disclosure is directed, in general, to software, and more specifically, to peer-assisted shopping.
Background
[0003] With the advent of shopping on the internet, shoppers have lost a fundamental feature—instant feedback from a companion that is shopping with them.
Summary
[0004] According to an embodiment of the present disclosure, systems and devices are disclosed for enabling peer-assisted shopping.
[0005] According to an embodiment of the disclosure, a method for peer-assisted shopping, the method includes initiating, on a first endpoint corresponding to a first user, a display of media content. The method also includes initiating, on the first endpoint, an interactive feature configured to allow the first user to interact with the first endpoint in response to the display of media content. The method further includes initiating, on the first endpoint, an option for the first user to invoke a communication request with at least a second user corresponding to at least a second endpoint. Moreover, the method includes, upon selection of the option, initiating a connection request with the at least a second endpoint.
[0006] Before undertaking the DETAILED DESCRIPTION below, it may be advantageous to set forth definitions of certain words and phrases used throughout this patent document: the terms “include” and “comprise,” as well as derivatives thereof, mean inclusion without limitation; the term “or,” is inclusive, meaning and/or; the phrases “associated with” and “associated therewith,” as well as derivatives thereof, may mean to include, be included within, interconnect with, contain, be contained within, connect to or with, couple to or with, be communicable with, cooperate with, interleave, juxtapose, be proximate to, be bound to or with, have, have a property of, or the like.
Brief Description of the Drawings
[0007] For a more complete understanding of the present disclosure and its advantages, reference is now made to the following description taken in conjunction with the accompanying drawings, in which like reference numerals represent like parts:
[0008] FIG. 1 is a simplified block diagram illustrative of a communication system that can be utilized to facilitate communication between endpoint(s) and endpoint(s) through a communication network, according to particular embodiments of the disclosure;
[0009] FIGS. 2A, 2B, 2C reference how a content container is enhanced for peer-assisted shopping, according to embodiments of the disclosure;
[0010] FIG. 3 shows an example interface 300 of initiating contact between endpoints in peer-assisted shopping, according to an embodiment of the disclosure
[0011] FIGS. 4 and 5 show processes for establishing communication between different endpoints, according to embodiments of the disclosure;
[0012] FIGS. 6 and 7 shows non-limiting examples of peer-assisted shopping communication interfaces, according to embodiments of the disclosure; and
[0013] FIG. 8 is an embodiment of a general purpose computer that may be used in connection with other embodiments of the disclosure to carry out any of the above-referenced functions and/or serve as a computing device for the endpoint(s) of FIG. 1 .
Detailed Description
[0014] The FIGURES, discussed below, and the various embodiments used to describe the principles of the present disclosure in this patent document are by way of illustration only and should not be construed in any way to limit the scope of the disclosure. Those skilled in the art will understand that the principles of the present disclosure may be implemented in any suitably arranged system.
[0015] FIG. 1 is a simplified block diagram illustrative of a communication system 100 that can be utilized to facilitate communication between endpoint(s) 110, endpoint(s) 120, and 130 through a communication network 140, according to particular embodiments of the disclosure. As used herein, “endpoint” may generally refer to any object, device, software, or any combination of the preceding that is generally operable to communicate with another endpoint. The endpoint(s) may represent a user, which in turn may refer to a user profile representing a person. The user profile may comprise, for example, an address for the user, a user name, a passcode, other user information, or any combination of the preceding. Additionally, the endpoint(s) may represent a device that comprises any hardware, software, firmware, or combination thereof operable to communicate through the communication network 140.
[0016] Examples of an endpoint(s) include, but are not necessarily limited to, a computer or computers (including servers, applications servers, enterprise servers, desktop computers, laptops, netbooks, tablet computers (e.g., WAD), a switch, mobile phones (e.g., including IPHONE and ANDROID-based phones), networked glasses (e.g., GOOGLE GLASS)), networked televisions, networked disc players, components in a cloud-computing network, or any other device or component of such device suitable for communicating information to and from the communication network 140. Endpoints may support Internet Protocol (IP) or other suitable communication protocols. Endpoints may additionally include a medium access control (MAC) and a physical layer (PHY) interface that conforms to IEEE 701.11. If the endpoint is a device, the device may have a device identifier such as the MAC address and may have a device profile that describes the device.
[0017] The communication network 140 and links 115, 125, and 135 to the communication network 140 may include, but are not limited to, a public or private data network; a telephony network, a local area network (LAN); a metropolitan area network (MAN); a wide area network (WAN); a wireline or wireless network (GSM, CDMA, LTE, WIMAX, or the like); a local, regional, or global communication network; portions of a cloud-computing network; a communication bus for components in a system; an optical network; a satellite network; an enterprise intranet; other suitable communication links; or any combination of the preceding. In particular embodiments, portions of the links 115, 125, 135 or communication network 140 may be on the Internet.
[0018] Although endpoint generally appears as being in a single location, the endpoint(s) may be geographically dispersed, for example, in cloud computing scenarios. As used in this document, “each” may refer to each member of a set or each member of a subset of a set.
[0019] When the endpoints(s) 110, 120, 130 communicate with one another, any of a variety of security schemes may be utilized. As an example, in particular embodiments, endpoint(s) 120 may represent a client and endpoint(s) 130 may represent a server in client-server architecture. The server and/or servers may host a website. And, the website may have a registration process whereby the user establishes a username and password to authenticate or log in to the website. The website may additionally utilize a web application for any particular application or feature that may need to be served up to the website for use by the user.
[0020] Additionally, in particular configurations, the communication between endpoints 110 and 120 may be facilitated through a communication path through endpoint 130.
[0021] Various embodiments described herein may avail benefits from and/or utilize Cinsay, Inc.'s (“Cinsay”) Smart Container™ Technology, which is briefly described below and is also described in U.S. application Ser. No. 13/598,443 filed Aug. 29, 2012 and claiming priority to several provisional applications. Cinsay, the Applicant, provides an innovative new method for merchants to reach their customers online. In the traditional online sales model, merchants need to create search or display ads which show up when online consumers visit search engine sites or various web properties. If the consumer sees an interesting ad related to a product or service, they need to leave their current activity and visit some other web destination to discover more information or make an online purchase. Consumers have specific online behavior patterns. If they are actively shopping, then the traditional multistep model is workable. The traditional advertising sales model requires that the consumer stop what they are doing and visit some other online destination. However, if they are on a social site interacting with friends, reading the news, playing games, or engaged in other online activities, then are much less likely to leave their current activity to visit some external internet destination.
[0022] The Cinsay Smart Container™ model brings the product information or store to the consumer. Cinsay utilizes an innovative new Smart Container™ code/technology that virally syndicates across the web, for, example using components described with reference to FIGS. 1 and 8 or using other components. It is ideal for those types of destinations that online consumers tend to frequent such as social networks and blogs. Regardless, if the Smart Container™ code is located on a web page, a blog article, a social network page or wall, or a mobile device, they can complete their transaction right there with no need to be diverted to some external destination.
[0023] Smart Container™ objects are intelligent internet objects that virally syndicate and propagate across the web and other connected network and mobile devices. They can be configured in a variety of ways to address the entire value chain of online marketing and shopping. This includes impressions, clicks, lead generation, and performing e-commerce transactions. A modern shopping experience works best when interactive media is used. One of the most appealing forms of media for sales and shopping is video. It allows a much more lifelike representation than text or static pictures. It also creates a much richer product browsing or shopping experience.
[0024] Cinsay's Smart Container™ code is normally configured with a video player window, a selection of products or services being offered, and a variety of related video clips. This collection of video clips allows the consumer to learn more about the products or services being offered. The consumer can select any of these offered items to get more details, all enclosed within the Smart Container™ technology.
[0025] These offered items (products or services) may be items being advertised or sold. Depending on the type, the Smart Container™ code may allow the consumer to request to be contacted, or even purchase the object, right there. The consumer need not leave their current activity or web page. The offered items could also include getting discounts or coupons. They may even be an opportunity to donate to a charity or political campaign. Of course, sometimes it does make sense to visit another internet designation, and if appropriate, the consumer can certainly be linked there as well.
[0026] Because the Smart Container™ code handles all the complexity, it can turn the simplest web site into an instant e-commerce store. This enables anyone to transact online without having to deal with the complexity of setting up an e-commerce site. For merchants with an e-commerce site, it readily enables a much richer shopping experience. For the creative hobbyist or local band, it lets them readily sell directly to interested consumers. To support and promote them, Cinsay offers supplemental items in their Smart Container™ code called On-Demand™ merchandise. Merchants can custom design a selection of apparel with their art and graphics to be sold along with their own creations. Cinsay's On-Demand™ fulfillment will dynamically produce & ship their custom apparel for them, eliminating the need to manage inventory, and provide their online customers with a richer line of products. Of course because their instant e-commerce store is based on Smart Container™ objects, it can also propagate out onto all forms of viral syndication methods as well.
[0027] The Cinsay Smart Container™ code is also auto customizing, according to particular configurations. If the device is a traditional PC or laptop, it will render using the optimal technology, which for this purpose which is usually flash. On mobile devices, such as IPhones, IPads, or Android phones, this means HTML5 or a native interactive app will likely get used. The items in the Smart Container™ code also know about each other, according to particular configurations. When a video is playing, the container can update the product and service objects being shown that correspond with the particular sequence in a video segment. It allows a mini QVC shopping channel to be created and syndicated across the internet. Beyond device type, there are other dimensions of customization. Smaller devices and some environments such as social site restrict window sizes, so the Smart Container™ code adapts. In addition, it may be appropriate to provide different content based on geo-location, so the Smart Container™ code can customize for these as well.
[0028] Cinsay Smart Container™ code virally syndicate across the internet following the more popular network paths. They can be hosted on traditional web pages, blogs, contained in emails, operate on mobile devices, or propagate social networks. Because the Smart Container™ code is flexible, they can also be setup in the form factor of a display ad unit and distributed via ad servers on display advertising networks. When the code exists on social networks like Facebook, they can ride the wave of user “likes.” For example, if a woman shopper likes some great shoes shown in a Smart Container™ object interface, the Smart Container™ object can propagate directly to their “wall.” Now all their friends see the Cinsay smart object, and can view or transact right there on their own wall. Of course, if any of their friends also “like” it, the Cinsay Smart Container™ object propagates and rides the wave further out into that branch of the social network yielding a potential exponential growth factor. Maybe the container does not involve products like shoes, but instead supports a politician running for office. Their supporters may be passionate about the message and “like” it, again making it available to their network Now, similarly minded political supporters can view those messages too, and if so moved donate to the cause.
[0029] Another example is sports. In this case, a sports fan may wish to watch that content on their HD large screen TV. More and more have interconnected devices such as a Roku device, and Cinsay Smart Container™ code may be sent to such an IP TV box as well.
[0030] When merchants launch and syndicate their Smart Container™ objects onto the internet, they what to know how their campaign is performing. Cinsay Smart Container™ object reports back status on events and transactions of interest such as impressions, video views, clicks, leads, and sales. All such events/transactions can be sent back as events occur, providing details on how they are doing. Because the containers are smart, they can be instructed to change behavior, offer different clips, update products, or to end when it is time to stop the marketing or sales campaign.
[0031] Another form of tracking relates to how the Cinsay Smart Container™ code is propagated. A merchant may wish to use affiliates to help syndicate them, and pay them a percentage based on the transactions resulting from their work. Cinsay Smart Container™ objects can be tagged with affiliate tracking identifiers allowing status reports and transactions from that container instance or its descendants to be properly filtered. Another tracking usage may be for a politician to assign affiliate codes to their supporters and be able to measure whose efforts result in the most new supporters.
[0032] Cinsay Smart Container™ objects are designed to be highly scalable according to particular configurations. Rather than burden a single website with massive traffic which would result from a traditional model of bringing all consumers to the store, Cinsay Smart Container™ code operates in a distributed manner. Cinsay Smart Container™ code execute where they are, on blog, social network or mobile device. They fetch their instructions when started, and then gather their product items and video streams from a worldwide distributed content delivery network. This results in highly scalable architecture allowing millions of concurrent consumers.
[0033] By bringing the store to the customer, Cinsay Smart Container™ code enables many new ways for merchants to connect with their consumers without disrupting the consumer's web activities. The end result is to connect the consumer directly with the merchant eliminating the middleman and promoting a much more natural shopping experience.
[0034] The functionality of the above description, once again, may avail from any of the components described in FIGS. 1 and 8 or other suitable components. The code, itself, may be written in any suitable format, including but not limited to Java, C++, C-sharp, HTML, HTML5, and the like.
[0035] FIGS. 2A, 2B, 2C reference how a content container is enhanced for peer-assisted shopping, according to embodiments of the disclosure. According to certain embodiments of the disclosure, the concept of shopping with friends or family is emulated. Specifically, the person with whom you are shopping with need not be physically present. However, one is able to communicate and solicit feedback from such a person as though they were shopping with them. As discussed below, a “peer” in particular embodiments may be a friend or family member. In other embodiments, a “peer” may be one who is not readily known to a person.
[0036] With reference to FIGS. 2A and 2B , a container 210 is shown. In this container 210, the viewable content is video (as indicated by the play button 220); however, in other configurations that will be described below, the container 210 may include images, live-video feeds, and other types of content. In FIG. 2B , the video has been initiated and a selectively displayable product carousel 230 with a plurality of products is shown. In particular configurations, these products correspond to the products or services being shown in the content within the underlying container (here, a video). Although shown on the top portion overlaying the video, the product carousel 230 may be on the sides or bottom of the container 210—overlaying the container 210 or not in other configurations. For example, the product carousel may expand from or be positioned outside of the container 210. Additionally, varying degrees of transparency may be used in the product carousel 230. Or, the product carousel 230 may not be transparent.
[0037] A user viewing the container 210 may interact with the displayable product carousel 214 and purchase items or transact without leaving the container 210. For example, with reference to a container on a Facebook™ wall of a friend, a user may purchase the product directly from the container and the wall. In other configurations, a user may leave the container 210 and be redirected to a website.
[0038] With reference to FIG. 2C , additional features of the container 210 are shown. For example, a selectively displayable toolbar 240 is shown at least partially overlaying a bottom of the container 210. Although shown on the bottom portion overlaying the video, the toolbar 240 may be on the sides or top of the container 210—overlaying the container 210 or not in other configurations. For example, the toolbar 240 may expand from or be positioned outside of the container 210. Additionally, varying degrees of transparency may be used in the toolbar 240. Or, the toolbar 240 may not be transparent.
[0039] A variety of typical options are provided in the toolbar, including play and audio options 241, share options 243, account login options 245, video quality options 247, and further information options 249. The play and audio options 241 will become apparent to one of ordinary skill in the art upon reading this disclosure. Also shown is a play bar 242, which will become apparent to one of ordinary skill in the art.
[0040] Upon clicking on the share options 242, a variety of other options may be provided. For example, a user may be given the opportunity to share the container via networks such as Facebook, Myspace, Twitter, Yahoo, LinkedIn, Google, or Wordpress. Furthermore, the user may be given the option to copy embed codes, and share via email. Additionally, a user may be able to propagate the container by clicking the “like” thumb or “+1”ing on Google Plus.
[0041] The account login options 245 may allow a user to sign-into a variety of networks including, for example, Cinsay, Facebook, or Google. The video quality options 247 allow modification of the video, and the further information options provides any of a variety of options one may one to provide about the container.
[0042] A peer-assisted shopping option 250 is also provided to allow communication with one or more other endpoint. For example, in particular embodiments, a user may be shopping at home on their computer, tablet, or television and upon seeing something they like, initiate a communication with a peer. Alternatively, in other embodiments, a user may be shopping in a store and see a particular item they like and initiate communication with a peer using and share what they are viewing, for example, use camera capture features on their mobile device (e.g., a phone, tablet, or Google Glass). This communication may be initiated by selecting the peer-assisted option 250. In particular embodiments, this may involve selecting with a mouse pointer, a finger, or a stylus. Alternatively, activations may occur with certain movement detected by sensors in the device or voice activation.
[0043] Again, although the underlying content for the container will be described as a video in particular configurations, the underlying content may be other items including, but not limited to, just-taken pictures and real-time video fees.
[0044] The method and/or manner of communicating between endpoints is virtually limitless. Non-limiting examples of communication channels are provided above with reference to FIG. 1 . Any of these communications and others may be utilized for initiating communication between end users. For example, upon clicking on the peer-assisted shopping option 250 in FIG. 2C , a list of contacts can be brought up. These contacts may be contacts on a device associated with an endpoint, contacts within a network, or other people as will be described below. In particular embodiments, only contacts that are currently connected to a network that is common to the first user (e.g., Facebook, Google+, Cinsay, or others) may be shown as options. In other configurations, a general list of contacts will be shown.
[0045] The following are non-limiting examples of initiating the communication between two end-users: short messaging service, online presence, a join-me link that displays in whatever interface they may currently be using, an email, a blast of messages to a group, or messages to specific friends. In particular embodiments, no account is needed; rather, the specific linkage between two end-devices is established through the connection parameters. As will be recognized by one of ordinary skill in the art reviewing this application, in certain embodiments, the communication may be direct (peer-to-peer) while in others in may indirect through servers which relay messages. In yet other configurations, the communications may be a hybrid of the two.
[0046] The following are non-limiting examples of methods of which end-users can communicate with one another: voice over IP (VOIP), video chat, text chatting, or phone call. Such communications are in addition to the content (e.g., digital content) that may be shared between the user. In particular embodiments, the manners of communication may be dependent on the capability of the particular device.
[0047] FIG. 3 shows an example interface 300 of initiating contact between endpoints in peer-assisted shopping, according to an embodiment of the disclosure. Upon clicking on the peer-assisted shopping option 250 in FIG. 2C , the interface 300 may be displayed. In particular configurations, the interface may be transparently displayed over a container.
[0048] In the interface 300, connection options 310 represent options for connecting to someone who is currently connected a network such as Cinsay, Facebook, or Video (e.g., Skype). If the user is not connected to such a network, the option is not shown. In such a connection option, a message may be propagated through the appropriate network asking the recipient to join the requestor in peer-assisted shopping. Upon responding “OK,” the receiving user may be taken to a container interface. Connection options 320 represent other manners of initiating contact with a person, for example, using short-messaging-service (SMS), or email. In these options, a link may be provided to the container interface.
[0049] When a container is invoked, the container determines the endpoint's environment and communication options. For example, the container may determine whether video chat is available, whether the bandwidth on the network is appropriate for certain communication techniques, whether VOIP chatting is an option, whether text chatting is an option, and whether mobile phone access is available (e.g., using a carrier such as AT&T, Verizon, Sprint, or T-mobile).
[0050] In particular embodiments, a user may have multiple devices. Accordingly, a connection attempt can be sent in parallel to multiple different devices.
[0051] FIGS. 4 and 5 show processes 400, 500 for establishing communication between different endpoints, according to embodiments of the disclosure. FIG. 4 shows a process 400 on a first requesting endpoint whereas FIG. 5 shows a process 500 on a second receiving endpoint.
[0052] With reference to FIG. 4 , the process 400 at the first endpoint begins at step 410 with a peer connection option being initiated. As referenced above, this may be a mouse click, a tap by a finger on a part of screen, or a stylus touching a screen. Additionally, it may be activated with a remote for a networked television, voice activation, or using a sensor such as proximity detector (e.g., a wave). Yet other activation techniques will become apparent to one of ordinary skill in the art after review of the disclosure.
[0053] At step 420, communication parameters of the first endpoint are determined. According to particular configurations, this may include determining the methods of communication available on the first endpoint (e.g., determining whether voice, chat, video are available), the nature of such channels (e.g., bandwidth—connected via WIFI, 3G, 4G, etc). According to particular configurations, this may also include a determination of which networks the first end point is currently connected to (e.g., Cinsay, Facebook, Google). In particular configurations, a user of a device may configure method of communication (e.g., only video chat if connected via WI-FI or turn video chat off).
[0054] At step 430, available communication parameters of other potential endpoints are determined. According to particular configurations, this may include determining which networks peers are currently connected to (e.g., Cinsay, Facebook, Google). This may also include determining what methods of communication one has in communicating with an end user. For example, as reference above, a particular person may have multiple devices. And, it is not clear which device or device the person is currently using—if at all. Thus, when considering peers, multiple different devices for single person may be considered.
[0055] In particular configurations, a user may also be prompted to enter communication parameters. For example, they may want to communicate with a friend and enter his or her telephone number for an SMS message.
[0056] At step 440, communications with at least a second endpoint is initiated awaiting receipt of a response. In particular configurations, messages may be sent in parallel to a second user (e.g., in-application message via Facebook/Cinsay and text message). If the user is at his or her desktop, they may prefer to communicate with a desktop computer as opposed to a mobile device.
[0057] At step 450, a determination is made as to whether other messages should go out to other endpoints. This is because particular configurations allow group settings where the peer-assisted shopping is amongst a group of friends. If yes, the process repeats at step 440. If no, the process 500 moves on.
[0058] At step 460, there is a negotiation process between the endpoints to determine how communication will occur. In this negotiation, the communication capability of each respective endpoint is considered. The negotiation process may be partially carried out on each respective endpoint. Alternatively, a server operates as an intermediary and deices. Or, one device may control the negotiation process communication setup.
[0059] Negotiation is used in particular embodiments because, for example, the second endpoint may only be able to communicate via messaging due a lack of a camera or a microphone. Accordingly, messaging may be determined as a suitable communication technique. In particular configurations, the negotiation process of step 460 may take into consideration other devices that are also communicating as well as the particular content feed within the container. In particular configurations, the first end point can communicate with multiple endpoints using disparate technologies. For example, communication between a first and second endpoint may be video chatting whereas communication between the first and third endpoints and the second and third endpoints is text chatting. Accordingly, the negotiation process may determine how to efficient handle such disparate technologies.
[0060] At step 470, the respective communication channels are established with each of the respective endpoints using suitable connection parameters.
[0061] According to particular embodiments, the process 400 of FIG. 4 may take only a couple of seconds—depending on the computing power and network latency. In certain configurations, the process 400 may take less than a second. In other configurations, the process 400 may take more than a couple of seconds.
[0062] With reference to FIG. 5 , the process 500 at a second endpoint begins at step 510 with a peer connection request being received at a second endpoint. As referenced above, in particular configurations, multiple parallel requests may be sent to a particular user who may have multiple devices. Several of these types of messages may be received on a particular endpoint. For example, a text message may be received as well as an in-app message (e.g., on Facebook or Cinsay). In particular configurations, the user upon seeing the message can choose to accept the invitation to connect. As a non-limiting examples, a user may click on a link or hit a button that confirms acceptance.
[0063] At step 520, a container for the communication is initialized. In particular configurations, the container may have features that correspond to a pre-installed application on a device. In other configurations, the container may correspond to application features that are propagated on the fly, for example, using embed codes.
[0064] At step 530, communication parameters of the second endpoint are determined. This may include initiating determination actions similar to those described above with reference to step 420 of FIG. 4 except with reference to the second endpoint. At step 540, a response is sent to the first endpoint.
[0065] At step 550, there is a negotiation process between the endpoints to determine how communication will occur. This is similar to the step 460 in FIGURE except from the perspective of the second endpoint.
[0066] At step 560, communication channels are established, which is similar to step 470 of FIG. 4 .
[0067] In particular embodiments, a second endpoint that received a request and established a link with the first endpoint may, in turn, undergo the process 400 of FIG. 4 using an “add-a-friend” feature. In such an embodiment, approval may or may not be required by the first endpoint. In repeating the process 400, the negotiation between endpoints may consider the link that has already been established between the first or second endpoint.
[0068] FIGS. 6 and 7 shows non-limiting examples of peer-assisted shopping communication interfaces 600 and 700, according to embodiments of the disclosure. Interface 600 may exist on any suitable device whereas interface 700 is shown as existing on a mobile device. In this particular embodiment, the underlying content is a video. Again, as referenced above, in other configurations, the underling content may be other items such a real-time video feed. In such an alternative configuration, a first device may capture video and send in real-time to a second device—either directly or through a server intermediary.
[0069] With reference to FIG. 6 , a container 610 is generally shown which may have features similar to those described above with reference to FIGS. 2A, 2B, and 2C .
[0070] A box 620 has been extended from one edge of the container 610 to show that the user is communication with three different people. The box 620 is shown partitioned into three portions 620A, 620B, and 620C—each portion corresponding to a particular user. Although this particular interface is shown, others may be utilized. For example, the box 620 may show up as an overlay over the content. Additionally, the interface may be hidden upon command with, for example, only voice being propogated. Additionally, portions or all of the box 620 may take on a chat room interface if messaging is utilized.
[0071] In particular configurations, a user may be allowed to interact with a portion of the box corresponding to a particular person. For example, a user may click on a portion 620A corresponding to a particular person to discover what is in that person's shopping chart.
[0072] As referenced above, disparate technologies may be utilized in certain configurations. Accordingly, for example, portions 620A and 620C may show a video chat interface whereas portion 620B may be messaging chatting. In particular embodiments, conversions technologies may be used to convert text-to-voice or voice-to-text in order to accommodate for scenarios requiring different communication techniques. The conversion process may occur anywhere in the communication chain—at either device or at a server.
[0073] A variety of tools 640 are also shown to facilitate the communication between the end users. In particular configuration, the tools 640 may replace some of the tools 240 shown in FIG. 2C . Although shown in the lower portion of the container 610 in this configuration, this toolset may be take on almost any configuration and can be selectively shown (and hidden) in any of a variety of manners. As a non-limiting example, the tools 640 may be invoked by hovering over a lower portion of the container or right clicking on the container.
[0074] A non-limiting example of tools include, a share shopping cart feature 641, a share particular location in video feature 643, a share current content feature 645, a sync feature 647 request to sync the playing of video and corresponding start location at a particular location so that two people may view the same thing at the same time, a commenting or tagging feature 649. Other features, designated “x” and “y” may additionally be incorporated.
[0075] The share shopping cart feature 641 allows one user to allow the peers to view the items in the shopping cart 625. The shopping cart 625, itself, may contain reverse links back to the location where the item was added. For example, it may contain a respective location in a video where the product was viewed and added to the cart.
[0076] The share particular location in a video feature 643 may enable one user to direct another user to a particular location in a video. For example, one user may like a particular product (e.g., shoes) in a video and choose to share that particular location with one of the peers.
[0077] The share current content feature 645 enables the sharing of the current content one is viewing through the container. For example, if the content is a video, the video may be shared. If content is real-time view of something, the real-time view may be recorded with both a camera and either pictures or video may be sent to the second user.
[0078] The sync feature 647 may allow a sync of views by different devices. For example, a first user may wish that a second user view the same thing they are viewing. Accordingly, initiating this feature allows the views to sync. In initiating this feature, a user may choose a start position of a particular video. The devices can communicate as necessary so that playback is in sync.
[0079] The comment or tagging feature 649 allows a user to comment on a time-based and/or coordinate-based portion of the content. For example, a first user may want to circle certain shoes at a certain time in the video and share with their peers. Any suitable annotation features may be utilized. The annotations may store the time and coordinates.
[0080] Also shown is a shopping cart 625, which a user may use to place items. The shopping cart 625 may be shared with the peers—allowing each respective peer to provide feedback.
[0081] With reference to FIG. 7 , a container 710 on a mobile device 790 is generally shown. This container 710 may contain features similar to those described above with reference to FIGS. 2A, 2B, and 2C . In particular embodiments, the container 710 may cover the entire screen with other interfaces selectively provided to cover a portion of the interface. For example, as shown, a box 720 containing communication features (e.g., video or text chat) may overlay a portion of the container.
[0082] With reference to various FIGURES herein, a concept of a shared shopping cart may additionally be utilized. The shared shopping cart provides access to a common shopping cart to a group of people. According to certain embodiments, the contents of the shared shopping cart may contain an identifier of who added the item along with a link-back to the location from where it came, which may be a video.
[0083] Shared shopping carts may be used in a variety of settings. For example, a shared shopping cart may be utilized for a group planning for a party with each added item showing the others in the group what they intend on buying. Additionally, for high school girls attending a prom, a shared shopping chart may be utilized so that each may see what the other intends on wearing to the prom. For items in the shared shopping cart, individuals may be able to comment on the items. Additionally, where a particular shared item has been annotated, the shared shopping cart may indicate that the item has a comment in the linked back object, which may be a video.
[0084] Despite the shopping carts being shared, in particular embodiments, individual checkouts may occur. When such a checkout has occurred, a notification in the shopping cart may be placed indicting that a particular item has been purchased. Alternatively, if all the items in the cart are shared purchase-wise, each person may have an individual check-out for their portion of the overall amount.
[0085] In particular embodiments, whether or not something is a shared in a cart can be define by permissions. For example, an individual cart may begin as an individual cart and quickly be turned into a shared shopping cart by changing permission.
[0086] With reference to various FIGURES herein, solicitation of feedback may be product or service specific and seek general feedback from non-friends and non-family members. For examples, embodiment may allow a user to solicit feedback on products or services from other individuals who had purchased or reviewed product or service in the past or opted in for peer-assisted shopping participation and active solicitation. In yet other configurations, users may solicit information from non-connected users from other networks that the particular user may utilize. In such configurations, the solicitation of information may also encourage the solicited individual to become a user of Cinsay's network. As a non-limiting example, one could have a Facebook or Google+ post that is automatically posted by Cinsay's technology, asking friends, groups, circles, or the general for input on a particular product. In particular configurations, an individual may simply engage in a response. In other configurations, an individual may be prompted to become a Cinsay network participant user or to simply associate their current network (e.g., Facebook or Google+) with a Cinsay account. In either configuration, the user may be given a variety of control configurations as to who is solicited. As non-limiting examples, the user may have the option to solicit by friends, groups or circles in Facebook or Google+ accounts, to solicit by geographic region (e.g., city, metropolitan area, region, or state), to solicit by those having certain technological capability (e.g., those that can video chat), to solicit those who purchased with a certain time frame (e.g., when such purchase statistics are available), to solicit those who purchased from the same company in which a purchase is contemplated, to solicit every known purchaser of the product, or any other criteria or combinations of the proceeding.
[0087] Active solicitation may take form of video conversation, chat, short messaging service (sms), email or any other form of electronic communication facilitated by the technology. In particular configurations, the receipt of such solicited message may be an opt-in or opt-out scenario. Similar configurations—similar to those provided above—may also be placed on the receipt of messages. For example, receive solicitations from friends, groups or circles in Facebook or Google+ accounts, receive solicitations by geographic region (e.g., city, metropolitan area, region, or state), receive solicitations by those having certain technological capability (e.g., only those that can video chat), receive solicitations by those who have are contemplating purchased from the same company the user purchased, any other criteria or combinations of the proceeding.
[0088] Upon product or service selection, a user may additionally be presented with a product or service reviews, ratings or feedback from other product or service users. Current users may choose to solicit additional feedback on a product or service of interest from other users in their network or peer-assisted shopping participants who have opted in for active solicitation and peer-assisted shopping process. Active solicitation is facilitated by the technology and may occur synchronously or asynchronously in real-time or delayed fashion.
[0089] Peer-assisted shopping or active solicitation participants may or may not receive compensation for the rendered assisted services. In cases where service compensation in rendered it may include such form of payments as credits, discounts, virtual currency and legal tender.
[0090] Unlike general comments on products, certain embodiments provide an actual real-time question/answer session about the product or service.
[0091] FIG. 8 is an embodiment of a general purpose computer 810 that may be used in connection with other embodiments of the disclosure to carry out any of the above-referenced functions and/or serve as a computing device for endpoint(s) 110 and endpoint(s) 120 of FIG. 1 . General purpose computer 810 may generally be adapted to execute any of the known OS2, UNIX, Mac-OS, Linux, Android and/or Windows Operating Systems or other operating systems. The general purpose computer 810 in this embodiment includes a processor 812, a random access memory (RAM) 814, a read only memory (ROM) 816, a mouse 818, a keyboard 820 and input/output devices such as a printer 824, disk drives 822, a display 826 and a communications link 828. In other embodiments, the general purpose computer 810 may include more, less, or other component parts. Embodiments of the present disclosure may include programs that may be stored in the RAM 814, the ROM 816 or the disk drives 822 and may be executed by the processor 812 in order to carry out functions described herein. The communications link 828 may be connected to a computer network or a variety of other communicative platforms including, but not limited to, a public or private data network; a local area network (LAN); a metropolitan area network (MAN); a wide area network (WAN); a wireline or wireless network; a local, regional, or global communication network; an optical network; a satellite network; an enterprise intranet; other suitable communication links; or any combination of the preceding. Disk drives 822 may include a variety of types of storage media such as, for example, floppy disk drives, hard disk drives, CD ROM drives, DVD ROM drives, magnetic tape drives or other suitable storage media. Although this embodiment employs a plurality of disk drives 822, a single disk drive 822 may be used without departing from the scope of the disclosure.
[0092] Although FIG. 8 provides one embodiment of a computer that may be utilized with other embodiments of the disclosure, such other embodiments may additionally utilize computers other than general purpose computers as well as general purpose computers without conventional operating systems. Additionally, embodiments of the disclosure may also employ multiple general purpose computers 810 or other computers networked together in a computer network. Most commonly, multiple general purpose computers 810 or other computers may be networked through the Internet and/or in a client server network. Embodiments of the disclosure may also be used with a combination of separate computer networks each linked together by a private or a public network.
[0093] Additionally, in particular embodiments, the general purpose computers 810 computers may be mobile devices that include features such as cameras, camcorders, GPS features, and antennas for wireless communications. Mobile devices such as these include those marketed as iPhone and Android phones.
[0094] Several embodiments of the disclosure may include logic contained within a medium. In the embodiment of FIG. 8 , the logic includes computer software executable on the general purpose computer 810. The medium may include the RAM 814, the ROM 816, the disk drives 822, or other mediums. In other embodiments, the logic may be contained within hardware configuration or a combination of software and hardware configurations.
[0095] The logic may also be embedded within any other suitable medium without departing from the scope of the disclosure.
[0096] It will be understood that well known processes have not been described in detail and have been omitted for brevity. Although specific steps, structures and materials may have been described, the present disclosure may not be limited to these specifics, and others may be substituted as it is well understood by those skilled in the art, and various steps may not necessarily be performed in the sequences shown.
[0097] While this disclosure has described certain embodiments and generally associated methods, alterations and permutations of these embodiments and methods will be apparent to those skilled in the art. Accordingly, the above description of example embodiments does not define or constrain this disclosure. Other changes, substitutions, and alterations are also possible without departing from the spirit and scope of this disclosure, as defined by the following claims.
Claims
What is claimed is:
1. A processor-implemented method for peer-assisted shopping, the method comprising:
executing a media container including a media player at a first endpoint compute device associated with a first user, the first endpoint compute device comprising one or more processors configured to execute the media player, the media player including an interface configured to display digital content including media content; and
using the media player to:
initiate, at the first endpoint compute device, a display of media content in the interface, the media content being associated with one or more products or services;
initiate, at the first endpoint compute device and in association with the media content, a display of one or more interactive features in the interface, at least one of the one or more interactive features configured to allow a transaction involving the one or more products or services without leaving the media container;
in response to receiving a selection of at least one of the one or more interactive features in the interface, initiate, at the first endpoint compute device, a display of one or more options in the interface to invoke a data connection request; and
in response to receiving a selection of at least one of the one or more options in the interface, initiate the data connection request to at least one second endpoint compute device associated with at least one second user, the data connection request configured to, upon confirmation of acceptance by the at least one second endpoint compute device, execute a media container on the second compute device, the media container executed on the second compute device including a media player and an interface configured to display digital content including media content and one or more interactive features.
2. The processor-implemented method of claim 1, wherein the one or more interactive features include a product carousel configured to display graphics or text corresponding to the one or more products or services in the interface.
3. The processor-implemented method of claim 1, wherein the media content comprises real-time content captured by the first endpoint compute device.
4. The processor-implemented method of claim 3, further comprising:
transmitting at least some of the real-time content captured by the first endpoint compute device to the at least one second endpoint compute device.
5. The processor-implemented method of claim 1, further comprising:
determining whether compute devices associated with users in a list are connected to each of multiple communication networks, the communication networks comprising at least two different networks through which the first endpoint compute device is able to initiate the connection request; and
displaying to the first user, in the interface and based on the determination, which communication network or networks each respective compute device of the compute devices associated with the users in the list is currently connected to.
6. The processor-implemented method of claim 1, further comprising:
determining one or more parameters of the first endpoint compute device;
receiving one or more parameters corresponding to the at least one second endpoint compute device; and
negotiating, based on the parameters of the first endpoint compute device and the at least one second endpoint compute device, a channel of communication among multiple possible channels of communication between the first endpoint compute device and each of the at least one second endpoint compute device.
7. The processor-implemented method of claim 1, wherein:
the at least one second endpoint compute device includes multiple second endpoint compute devices; and
the processor-implemented method further comprises establishing at least two disparate types of communication channels between the first endpoint compute device and the multiple second endpoint compute devices.
8. The processor-implemented method of claim 1, wherein the connection request includes at least two messages transmitted from the first endpoint compute device to at least two different second endpoint compute devices associated with a single second user, the at least two messages allowing the single second user to respond with any of the at least two different second endpoint compute devices.
9. An apparatus comprising a first endpoint compute device, the first endpoint compute device comprising:
at least one memory configured to store instructions implementing a media container including a media player; and
at least one processor configured to execute the instructions implementing the media container including the media player, the media player configured to, when implemented, provided an interface configured to display digital content including media content;
the instructions implementing the media container including the media player including instructions configured to cause the at least one processor to:
initiate, at the first endpoint compute device, a display of media content in the interface to a first user associated with the first endpoint compute device, the media content associated with one or more products or services;
initiate, at the first endpoint compute device and in association with the media content, a display of one or more interactive features in the interface, at least one of the one or more interactive features configured to facilitate a transaction for at least one of the one or more products or services within the media container;
in response to receipt of a selection of at least one of the one or more interactive features in the interface, initiate, at the first endpoint compute device, a display of one or more options in the interface to invoke a data connection request; and
in response to receipt of a selection of at least one of the one or more options in the interface, initiate the data connection request to at least one second endpoint compute device associated with at least one second user.
10. The apparatus of claim 9, wherein the one or more interactive features include a product carousel configured to display graphics or text corresponding to the one or more products or services in the interface.
11. The apparatus of claim 9, wherein the media content includes real-time content captured by the first endpoint compute device.
12. The apparatus of claim 11, wherein the instructions implementing the media container including the media player further include instructions configured to cause the at least one processor to initiate transmission of at least some of the real-time content captured by the first endpoint compute device to the at least one second endpoint compute device.
13. The apparatus of claim 9, wherein the instructions implementing the media container including the media player further include instructions configured to cause the at least one processor to:
determine whether compute devices associated with users in a list are connected to each of multiple communication networks, the communication networks comprising at least two different networks through which the first endpoint is able to initiate the connection request; and
display to the first user, in the interface and based on the determination, which communication network or networks each respective compute device of the compute devices associated with the users in the list is currently connected to.
14. The apparatus of claim 9, wherein the instructions implementing the media container including the media player further include instructions configured to cause the at least one processor to:
determine one or more parameters of the first endpoint compute device;
receive one or more parameters corresponding to the at least one second endpoint compute device; and
negotiate, based on the parameters of the first endpoint compute device and the at least one second endpoint compute device, a channel of communication among multiple possible channels of communication between the first endpoint compute device and each of the at least one second endpoint compute device.
15. The apparatus of claim 9, wherein the instructions implementing the media container including the media player further include instructions configured to cause the at least one processor to establish at least two disparate types of communication channels between the first endpoint compute device and different ones of multiple second endpoint compute devices.
16. The apparatus of claim 9, wherein:
the connection request includes at least two messages; and
the instructions implementing the media container including the media player further include instructions configured to cause the at least one processor to initiate transmission of the at least two messages to at least two different second endpoint compute devices associated with a single second user so that the single second user is able to respond with any of the at least two different second endpoint compute devices.
17. The processor-implemented method of claim 1, wherein the one or more interactive features include a tool in the interface configured to allow the media content to be shared with other users.
18. The processor-implemented method of claim 1, wherein the one or more interactive features include a tool in the interface configured to allow content at a particular location within the media content to be shared with other users.
19. The processor-implemented method of claim 1, wherein the one or more interactive features include a tool in the interface configured to allow a comment, tag, or annotation associated with at least one of the one or more products or services to be shared with other users.
20. The processor-implemented method of claim 1, wherein the one or more interactive features include a tool in the interface configured to allow the media content to be shared with other users and to substantially synchronize playback of the media content for the first user and the other users.
21. The processor-implemented method of claim 1, wherein the one or more interactive features include a tool in the interface configured to share an electronic shopping cart associated with the first user with other users.
22. The apparatus of claim 9, wherein the one or more interactive features include a tool in the interface configured to allow the media content to be shared with other users.
23. The apparatus of claim 9, wherein the one or more interactive features include a tool in the interface, the tool configured to allow a particular location within the media content to be shared with other users.
24. The apparatus of claim 9, wherein the one or more interactive features include a tool in the interface, the tool configured to allow a comment, tag, or annotation associated with at least one of the one or more products or services to be shared with other users.
25. The apparatus of claim 9, wherein the one or more interactive features include a tool in the interface, the tool configured to allow the media content to be shared with other users and to substantially synchronize playback of the media content for the first user and the other users.
26. The apparatus of claim 9, wherein the one or more interactive features include a tool in the interface, the tool configured to allow a shopping cart associated with the first user to be shared with other users.
27. A non-transitory computer readable medium embodying a computer program, the computer program comprising:
computer readable program code defining a media container including a media player having an interface configured to display digital content including media content, the code defining the media container, when executed by at least one processor, causes the at least one processor to:
initiate, at a first endpoint compute device associated with a first user, a display of media content in the interface, the media content associated with one or more products or services;
initiate, at the first endpoint compute device and in association with the media content, a display of one or more interactive features in the interface, at least one of the one or more interactive features configured to allow a transaction involving at least one of the one or more products or services in the media container;
in response to detecting a selection of at least one of the one or more interactive features in the interface, initiate, at the first endpoint compute device, a display of one or more options in the interface for invoking a data connection request; and
in response to detecting a selection of at least one of the one or more options in the interface, initiate the data connection request to at least one second endpoint compute device associated with at least one second user, the data connection request configured to initiate a media container on the second compute device.
28. The non-transitory computer readable medium of claim 27, wherein the one or more interactive features include a product carousel configured to display graphics or text corresponding to the one or more products or services in the interface.
29. The non-transitory computer readable medium of claim 27, wherein the media content includes real-time content captured by the first endpoint compute device.
30. The non-transitory computer readable medium of claim 29, wherein the computer readable program code defining the media container including the media player, when executed by the at least one processor, further causes the at least one processor to:
initiate transmission of at least some of the real-time content captured by the first endpoint compute device to the at least one second endpoint compute device.
31. The non-transitory computer readable medium of claim 27, wherein the computer readable program code defining the media container including the media player, when executed by the at least one processor, further causes the at least one processor to:
determine whether compute devices associated with users in a list are connected to each of multiple communication networks, the communication networks comprising at least two different networks through which the first endpoint compute device is able to initiate the data connection request; and
display to the first user, in the interface and based on the determination, which communication network or networks each respective compute device of the compute devices associated with the users in the list is currently connected to.
32. The non-transitory computer readable medium of claim 27, wherein the computer readable program code defining the media container including the media player, when executed by the at least one processor, further causes the at least one processor to:
determine one or more parameters of the first endpoint compute device;
receive one or more parameters corresponding to the at least one second endpoint compute device; and
negotiate, based on the parameters of the first endpoint compute device and the at least one second endpoint compute device, a channel of communication among multiple possible channels of communication between the first endpoint compute device and each of the at least one second endpoint compute device.
33. The non-transitory computer readable medium of claim 27, wherein:
the at least one second endpoint compute device includes multiple second endpoint compute devices; and
the computer readable program code defining the media container including the media player, when executed by the at least one processor, further causes the at least one processor to establish at least two disparate types of communication channels between the first endpoint compute device and the multiple second endpoint compute devices.
34. The non-transitory computer readable medium of claim 27, wherein:
the data connection request includes at least two messages; and
the computer readable program code defining the media container including the media player, when executed by the at least one processor, further causes the at least one processor to initiate transmission of the at least two messages from the first endpoint compute device to at least two different second endpoint compute devices associated with a single second user so that the single second user is able to respond with any of the at least two different second endpoint compute devices.
35. The non-transitory computer readable medium of claim 27, wherein the one or more interactive features include an option to share with other users the media content.
36. The non-transitory computer readable medium of claim 27, wherein the one or more interactive features include an option to share with other users a particular location within the media content.
37. The non-transitory computer readable medium of claim 27, wherein the one or more interactive features include an option to share with other users a comment, tag, or annotation associated with at least one of the one or more products or services.
38. The non-transitory computer readable medium of claim 27, wherein the one or more interactive features include an option to share with other users the media content and to substantially synchronize playback of the media content for the first user and the other users.
39. The non-transitory computer readable medium of claim 27, wherein the one or more interactive features include an option to share with other users a shopping cart associated with the first user.
40. The non-transitory computer readable medium of claim 27, wherein the media content includes at least one of: one or more images, video content, or a real-time video feed.
Patent Citations (329)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US5715400(A) | 1998-02-01 | Reimer et al. | Applicant |
| US5774664(A) | 1998-06-01 | Hidary et al. | Applicant |
| US5778181(A) | 1998-07-01 | Hidary et al. | Applicant |
| US5903816(A) | 1999-05-01 | Broadwin et al. | Applicant |
| US5929849(A) | 1999-07-01 | Kikinis | Applicant |
| US6006257(A) | 1999-12-01 | Slezak | Applicant |
| US6009410(A) | 1999-12-01 | LeMole et al. | Applicant |
| US6014638(A) | 2000-01-01 | Burge et al. | Applicant |
| US6018768(A) | 2000-01-01 | Ullman et al. | Applicant |
| US6154771(A) | 2000-11-01 | Rangan et al. | Applicant |
| US6169573(B1) | 2001-01-01 | Sampath-Kumar et al. | Applicant |
| US6188398(B1) | 2001-02-01 | Collins-Rector et al. | Applicant |
| US6233682(B1) | 2001-05-01 | Fritsch | Applicant |
| US6240555(B1) | 2001-05-01 | Shoff et al. | Applicant |
| US6263505(B1) | 2001-07-01 | Walker et al. | Applicant |
| US6275989(B1) | 2001-08-01 | Broadwin et al. | Applicant |
| US6282713(B1) | 2001-08-01 | Kitsukawa et al. | Applicant |
| US6321209(B1) | 2001-11-01 | Pasquali | Applicant |
| US6330595(B1) | 2001-12-01 | Ullman et al. | Applicant |
| US6357042(B2) | 2002-03-01 | Srinivasan et al. | Applicant |
| US6536041(B1) | 2003-03-01 | Knudson et al. | Applicant |
| US6553566(B1) | 2003-04-01 | Grant et al. | Applicant |
| US6564380(B1) | 2003-05-01 | Murphy | Applicant |
| US6573907(B1) | 2003-06-01 | Madrane | Applicant |
| US6628307(B1) | 2003-09-01 | Fair | Applicant |
| US6766528(B1) | 2004-07-01 | Kim et al. | Applicant |
| US6857010(B1) | 2005-02-01 | Cuijpers et al. | Applicant |
| US6910049(B2) | 2005-06-01 | Fenton et al. | Applicant |
| US6912726(B1) | 2005-06-01 | Chen et al. | Applicant |
| US6941575(B2) | 2005-09-01 | Allen | Applicant |
| US6976028(B2) | 2005-12-01 | Fenton et al. | Applicant |
| US6990498(B2) | 2006-01-01 | Fenton et al. | Applicant |
| US7000242(B1) | 2006-02-01 | Haber | Applicant |
| US7017173(B1) | 2006-03-01 | Armstrong et al. | Applicant |
| US7072683(B2) | 2006-07-01 | King et al. | Applicant |
| US7136853(B1) | 2006-11-01 | Kohda et al. | Applicant |
| US7158676(B1) | 2007-01-01 | Rainsford | Applicant |
| US7162263(B2) | 2007-01-01 | King et al. | Applicant |
| US7168051(B2) | 2007-01-01 | Robinson et al. | Applicant |
| US7188186(B1) | 2007-03-01 | Meyer et al. | Applicant |
| US7207057(B1) | 2007-04-01 | Rowe | Applicant |
| US7222163(B1) | 2007-05-01 | Girouard et al. | Applicant |
| US7231651(B2) | 2007-06-01 | Pong | Applicant |
| US7243139(B2) | 2007-07-01 | Ullman et al. | Applicant |
| US7254622(B2) | 2007-08-01 | Nomura et al. | Applicant |
| US7269837(B1) | 2007-09-01 | Redling et al. | Applicant |
| US7331057(B2) | 2008-02-01 | Eldering et al. | Applicant |
| US7353186(B2) | 2008-04-01 | Kobayashi | Applicant |
| US7409437(B2) | 2008-08-01 | Ullman et al. | Applicant |
| US7412406(B2) | 2008-08-01 | Rosenberg | Applicant |
| US7432768(B2) | 2008-10-01 | Han et al. | Applicant |
| US7444659(B2) | 2008-10-01 | Lemmons | Applicant |
| US7464344(B1) | 2008-12-01 | Carmichael et al. | Applicant |
| US7485397(B2) | 2009-02-01 | Eck et al. | Applicant |
| US7487112(B2) | 2009-02-01 | Barnes, Jr. | Applicant |
| US7509340(B2) | 2009-03-01 | Fenton et al. | Applicant |
| US7539738(B2) | 2009-05-01 | Stuckman et al. | Applicant |
| US7574381(B1) | 2009-08-01 | Lin-Hendel | Applicant |
| US7593965(B2) | 2009-09-01 | Gabriel | Applicant |
| US7613691(B2) | 2009-11-01 | Finch | Applicant |
| US7614013(B2) | 2009-11-01 | Dollar et al. | Applicant |
| US7624416(B1) | 2009-11-01 | Vandermolen et al. | Applicant |
| US7631327(B2) | 2009-12-01 | Dempski et al. | Applicant |
| US7661121(B2) | 2010-02-01 | Smith et al. | Applicant |
| US7664678(B1) | 2010-02-01 | Haber | Applicant |
| US7673017(B2) | 2010-03-01 | Kim et al. | Applicant |
| US7691666(B2) | 2010-04-01 | Levy et al. | Applicant |
| US7721307(B2) | 2010-05-01 | Hendricks et al. | Applicant |
| US7725362(B2) | 2010-05-01 | Weathers, Jr. | Applicant |
| US7739596(B2) | 2010-06-01 | Clarke-Martin et al. | Applicant |
| US7747037(B2) | 2010-06-01 | Hein, III | Applicant |
| US7750343(B2) | 2010-07-01 | Choi et al. | Applicant |
| US7756758(B2) | 2010-07-01 | Johnson et al. | Applicant |
| US7769827(B2) | 2010-08-01 | Girouard et al. | Applicant |
| US7769830(B2) | 2010-08-01 | Stuckman et al. | Applicant |
| US7773093(B2) | 2010-08-01 | Bates et al. | Applicant |
| US7774161(B2) | 2010-08-01 | Tischer | Applicant |
| US7774815(B1) | 2010-08-01 | Allen | Applicant |
| US7796941(B2) | 2010-09-01 | Poltorak | Applicant |
| US7800102(B2) | 2010-09-01 | Park et al. | Applicant |
| US7804506(B2) | 2010-09-01 | Bates et al. | Applicant |
| US7818763(B2) | 2010-10-01 | Sie et al. | Applicant |
| US7870592(B2) | 2011-01-01 | Hudson et al. | Applicant |
| US7885951(B1) | 2011-02-01 | Rothschild | Applicant |
| US7892216(B2) | 2011-02-01 | Fangrow, Jr. | Applicant |
| US7899719(B2) | 2011-03-01 | Lin-Hendel | Applicant |
| US7912753(B2) | 2011-03-01 | Struble | Applicant |
| US7923722(B2) | 2011-04-01 | Ryu et al. | Applicant |
| US7923772(B2) | 2011-04-01 | Mauder et al. | Applicant |
| US7925973(B2) | 2011-04-01 | Allaire et al. | Applicant |
| US7946492(B2) | 2011-05-01 | Rohs | Applicant |
| US7975020(B1) | 2011-07-01 | Green et al. | Applicant |
| US7975062(B2) | 2011-07-01 | Krikorian et al. | Applicant |
| US7979877(B2) | 2011-07-01 | Huber et al. | Applicant |
| US7982216(B2) | 2011-07-01 | Imai | Applicant |
| US7987098(B2) | 2011-07-01 | Schifone | Applicant |
| US7987483(B1) | 2011-07-01 | Des Jardins | Applicant |
| US8001116(B2) | 2011-08-01 | Cope | Applicant |
| US8001577(B2) | 2011-08-01 | Fries | Applicant |
| US8006265(B2) | 2011-08-01 | Redling et al. | Applicant |
| US8010408(B2) | 2011-08-01 | Rubinstein et al. | Applicant |
| US8032421(B1) | 2011-10-01 | Ho et al. | Applicant |
| US8055688(B2) | 2011-11-01 | Giblin | Applicant |
| US8091103(B2) | 2012-01-01 | Cope | Applicant |
| US8108257(B2) | 2012-01-01 | Sengamedu | Applicant |
| US8117281(B2) | 2012-02-01 | Robinson et al. | Applicant |
| US8122480(B2) | 2012-02-01 | Sholtis | Applicant |
| US8132486(B1) | 2012-03-01 | Calvert | Applicant |
| US8141112(B2) | 2012-03-01 | Cope et al. | Applicant |
| US8181212(B2) | 2012-05-01 | Sigal | Applicant |
| US8196162(B2) | 2012-06-01 | van de Klashorst | Applicant |
| US8234218(B2) | 2012-07-01 | Robinson et al. | Applicant |
| US8244830(B2) | 2012-08-01 | Robinson et al. | Applicant |
| US8312486(B1) | 2012-11-01 | Briggs et al. | Applicant |
| US8316450(B2) | 2012-11-01 | Robinson et al. | Applicant |
| US8341152(B1) | 2012-12-01 | Bates | Applicant |
| US8356077(B2) | 2013-01-01 | Robinson et al. | Applicant |
| US8423467(B1) | 2013-04-01 | Johansson et al. | Applicant |
| US8433611(B2) | 2013-04-01 | Lax et al. | Applicant |
| US8438646(B2) | 2013-05-01 | Sidi | Applicant |
| US8458053(B1) | 2013-06-01 | Buron et al. | Applicant |
| US8468562(B2) | 2013-06-01 | Miller et al. | Applicant |
| US8549555(B2) | 2013-10-01 | Briggs et al. | Applicant |
| US8615474(B2) | 2013-12-01 | Avedissian et al. | Applicant |
| US8635169(B2) | 2014-01-01 | Avedissian et al. | Applicant |
| US8639621(B1) | 2014-01-01 | Ellis et al. | Applicant |
| US8645214(B2) | 2014-02-01 | Hipolito et al. | Applicant |
| US8645217(B2) | 2014-02-01 | Siegel et al. | Applicant |
| US8645991(B2) | 2014-02-01 | McIntire et al. | Applicant |
| US8655146(B2) | 2014-02-01 | Bennett et al. | Applicant |
| US8682809(B2) | 2014-03-01 | Avedissian et al. | Applicant |
| US8707185(B2) | 2014-04-01 | Robinson et al. | Applicant |
| US8708223(B2) | 2014-04-01 | Gates et al. | Applicant |
| US8725826(B2) | 2014-05-01 | Robinson et al. | Applicant |
| US8752083(B2) | 2014-06-01 | Geer, III et al. | Applicant |
| US8769016(B2) | 2014-07-01 | Jakobson | Applicant |
| US8769053(B2) | 2014-07-01 | Spitz et al. | Applicant |
| US8769584(B2) | 2014-07-01 | Neumeier et al. | Applicant |
| US8782690(B2) | 2014-07-01 | Briggs et al. | Applicant |
| US8813132(B2) | 2014-08-01 | Andrews, II et al. | Applicant |
| US8818941(B2) | 2014-08-01 | Kiilerich et al. | Applicant |
| US8893173(B2) | 2014-11-01 | Briggs et al. | Applicant |
| US9451010(B2) | 2016-09-01 | Spitz et al. | Applicant |
| US2002/0059196(A1) | 2002-05-01 | I'Anson et al. | Applicant |
| US2002/0062481(A1) | 2002-05-01 | Slaney et al. | Applicant |
| US2002/0075332(A1) | 2002-06-01 | Geilfuss, Jr. et al. | Applicant |
| US2002/0083447(A1) | 2002-06-01 | Heron et al. | Applicant |
| US2002/0083469(A1) | 2002-06-01 | Jeannin et al. | Applicant |
| US2002/0126990(A1) | 2002-09-01 | Rasmussen et al. | Applicant |
| US2002/0199181(A1) | 2002-12-01 | Allen | Applicant |
| US2003/0023490(A1) | 2003-01-01 | Lenyon et al. | Applicant |
| US2003/0028873(A1) | 2003-02-01 | Lemmons | Applicant |
| US2003/0055723(A1) | 2003-03-01 | English | Applicant |
| US2003/0135563(A1) | 2003-07-01 | Bodin et al. | Applicant |
| US2003/0149983(A1) | 2003-08-01 | Markel | Applicant |
| US2003/0163832(A1) | 2003-08-01 | Tsuria et al. | Applicant |
| US2003/0228615(A1) | 2003-12-01 | Rossi et al. | Applicant |
| US2003/0231851(A1) | 2003-12-01 | Rantala et al. | Applicant |
| US2004/0021684(A1) | 2004-02-01 | Millner | Applicant |
| US2005/0022226(A1) | 2005-01-01 | Ackley et al. | Applicant |
| US2005/0033656(A1) | 2005-02-01 | Wang et al. | Applicant |
| US2005/0076372(A1) | 2005-04-01 | Moore et al. | Applicant |
| US2005/0091107(A1) | 2005-04-01 | Blum | Applicant |
| US2006/0009243(A1) | 2006-01-01 | Dahan et al. | Applicant |
| US2006/0089843(A1) | 2006-04-01 | Flather | Applicant |
| US2006/0122895(A1) | 2006-06-01 | Abraham | Examiner |
| US2006/0136305(A1) | 2006-06-01 | Fitzsimmons et al. | Applicant |
| US2006/0202191(A1) | 2006-09-01 | Gerlach et al. | Applicant |
| US2006/0242016(A1) | 2006-10-01 | Chenard | Applicant |
| US2006/0256133(A1) | 2006-11-01 | Rosenberg | Applicant |
| US2006/0265657(A1) | 2006-11-01 | Gilley | Applicant |
| US2006/0276266(A1) | 2006-12-01 | Sullivan | Applicant |
| US2007/0030080(A1) | 2007-02-01 | Han et al. | Applicant |
| US2007/0087489(A1) | 2007-04-01 | Park et al. | Applicant |
| US2007/0106646(A1) | 2007-05-01 | Stern et al. | Applicant |
| US2007/0150360(A1) | 2007-06-01 | Getz | Applicant |
| US2007/0157228(A1) | 2007-07-01 | Bayer et al. | Applicant |
| US2007/0180461(A1) | 2007-08-01 | Hilton | Applicant |
| US2007/0204308(A1) | 2007-08-01 | Nicholas et al. | Applicant |
| US2007/0239546(A1) | 2007-10-01 | Blum et al. | Applicant |
| US2007/0241327(A1) | 2007-10-01 | Kim et al. | Applicant |
| US2007/0250901(A1) | 2007-10-01 | McIntire et al. | Applicant |
| US2007/0266399(A1) | 2007-11-01 | Sidi | Applicant |
| US2007/0271149(A1) | 2007-11-01 | Siegel et al. | Applicant |
| US2007/0276721(A1) | 2007-11-01 | Jackson | Examiner |
| US2007/0288518(A1) | 2007-12-01 | Crigler et al. | Applicant |
| US2007/0300263(A1) | 2007-12-01 | Barton et al. | Applicant |
| US2007/0300280(A1) | 2007-12-01 | Turner et al. | Applicant |
| US2008/0005999(A1) | 2008-01-01 | Pervan | Applicant |
| US2008/0012010(A1) | 2008-01-01 | Myung-Seok et al. | Applicant |
| US2008/0066099(A1) | 2008-03-01 | Brodersen et al. | Applicant |
| US2008/0066107(A1) | 2008-03-01 | Moonka et al. | Applicant |
| US2008/0097843(A1) | 2008-04-01 | Menon et al. | Applicant |
| US2008/0098425(A1) | 2008-04-01 | Welch | Applicant |
| US2008/0109306(A1) | 2008-05-01 | Maigret et al. | Applicant |
| US2008/0109844(A1) | 2008-05-01 | Baldeschwieler et al. | Applicant |
| US2008/0126191(A1) | 2008-05-01 | Schiavi | Applicant |
| US2008/0126226(A1) | 2008-05-01 | Popkiewicz et al. | Applicant |
| US2008/0126949(A1) | 2008-05-01 | Sharma | Applicant |
| US2008/0148283(A1) | 2008-06-01 | Allen et al. | Applicant |
| US2008/0149921(A1) | 2008-06-01 | Choi et al. | Applicant |
| US2008/0162343(A1) | 2008-07-01 | Bedier | Applicant |
| US2008/0177627(A1) | 2008-07-01 | Cefail | Applicant |
| US2008/0177630(A1) | 2008-07-01 | Maghfourian et al. | Applicant |
| US2008/0235085(A1) | 2008-09-01 | Kovinsky et al. | Applicant |
| US2008/0250445(A1) | 2008-10-01 | Zigmond et al. | Applicant |
| US2008/0255934(A1) | 2008-10-01 | Leventhal et al. | Applicant |
| US2008/0276266(A1) | 2008-11-01 | Huchital et al. | Applicant |
| US2008/0281685(A1) | 2008-11-01 | Jaffe et al. | Applicant |
| US2008/0294694(A1) | 2008-11-01 | Maghfourian et al. | Applicant |
| US2008/0296568(A1) | 2008-12-01 | Ryu et al. | Applicant |
| US2008/0306999(A1) | 2008-12-01 | Finger et al. | Applicant |
| US2008/0307310(A1) | 2008-12-01 | Segal et al. | Applicant |
| US2008/0319852(A1) | 2008-12-01 | Gardner et al. | Applicant |
| US2008/0319856(A1) | 2008-12-01 | Zito et al. | Applicant |
| US2009/0013347(A1) | 2009-01-01 | Ahanger et al. | Applicant |
| US2009/0018904(A1) | 2009-01-01 | Shipman et al. | Applicant |
| US2009/0031382(A1) | 2009-01-01 | Cope | Applicant |
| US2009/0032809(A1) | 2009-02-01 | Kim et al. | Applicant |
| US2009/0043674(A1) | 2009-02-01 | Minsky et al. | Applicant |
| US2009/0077598(A1) | 2009-03-01 | Watson et al. | Applicant |
| US2009/0083815(A1) | 2009-03-01 | McMaster et al. | Applicant |
| US2009/0094339(A1) | 2009-04-01 | Allen et al. | Applicant |
| US2009/0119169(A1) | 2009-05-01 | Chandratillake et al. | Applicant |
| US2009/0132349(A1) | 2009-05-01 | Berkley et al. | Applicant |
| US2009/0157500(A1) | 2009-06-01 | Ames et al. | Applicant |
| US2009/0158322(A1) | 2009-06-01 | Cope et al. | Applicant |
| US2009/0199230(A1) | 2009-08-01 | Kumar et al. | Applicant |
| US2009/0210790(A1) | 2009-08-01 | Thomas | Applicant |
| US2009/0248546(A1) | 2009-10-01 | Norris et al. | Applicant |
| US2009/0259563(A1) | 2009-10-01 | Ruhnke et al. | Applicant |
| US2009/0265255(A1) | 2009-10-01 | Jackson et al. | Applicant |
| US2009/0276805(A1) | 2009-11-01 | Andrews, II et al. | Applicant |
| US2009/0320073(A1) | 2009-12-01 | Reisman | Applicant |
| US2010/0030578(A1) | 2010-02-01 | Siddique et al. | Applicant |
| US2010/0114983(A1) | 2010-05-01 | Robert et al. | Applicant |
| US2010/0131385(A1) | 2010-05-01 | Harrang et al. | Applicant |
| US2010/0145795(A1) | 2010-06-01 | Haber et al. | Applicant |
| US2010/0153831(A1) | 2010-06-01 | Beaton | Applicant |
| US2010/0223107(A1) | 2010-09-01 | Kim et al. | Applicant |
| US2010/0247061(A1) | 2010-09-01 | Bennett et al. | Applicant |
| US2010/0279766(A1) | 2010-11-01 | Pliska et al. | Applicant |
| US2010/0283827(A1) | 2010-11-01 | Bustamente | Applicant |
| US2010/0287580(A1) | 2010-11-01 | Harding et al. | Applicant |
| US2010/0299616(A1) | 2010-11-01 | Chen et al. | Applicant |
| US2010/0306402(A1) | 2010-12-01 | Russell et al. | Applicant |
| US2010/0306805(A1) | 2010-12-01 | Neumeier et al. | Applicant |
| US2010/0332329(A1) | 2010-12-01 | Roberts et al. | Applicant |
| US2011/0004517(A1) | 2011-01-01 | Soto et al. | Applicant |
| US2011/0052144(A1) | 2011-03-01 | Abbas et al. | Applicant |
| US2011/0071865(A1) | 2011-03-01 | Leeds et al. | Applicant |
| US2011/0133176(A1) | 2011-06-01 | Lee et al. | Applicant |
| US2011/0173300(A1) | 2011-07-01 | Levy et al. | Applicant |
| US2011/0191809(A1) | 2011-08-01 | Briggs et al. | Applicant |
| US2011/0231260(A1) | 2011-09-01 | Price | Applicant |
| US2011/0238755(A1) | 2011-09-01 | Khan et al. | Examiner |
| US2011/0251897(A1) | 2011-10-01 | Litvack et al. | Applicant |
| US2011/0307397(A1) | 2011-12-01 | Benmbarek | Applicant |
| US2011/0321096(A1) | 2011-12-01 | Landow et al. | Applicant |
| US2012/0030704(A1) | 2012-02-01 | Schiller et al. | Applicant |
| US2012/0036048(A1) | 2012-02-01 | Robb et al. | Applicant |
| US2012/0079021(A1) | 2012-03-01 | Roman et al. | Applicant |
| US2012/0158511(A1) | 2012-06-01 | Lucero et al. | Applicant |
| US2012/0185355(A1) | 2012-07-01 | Kilroy | Applicant |
| US2012/0201521(A1) | 2012-08-01 | Frojdh et al. | Applicant |
| US2012/0222064(A1) | 2012-08-01 | Geer, III et al. | Applicant |
| US2012/0227060(A1) | 2012-09-01 | Allen et al. | Applicant |
| US2012/0227074(A1) | 2012-09-01 | Hill et al. | Applicant |
| US2012/0284607(A1) | 2012-11-01 | Jones et al. | Applicant |
| US2012/0296738(A1) | 2012-11-01 | Leeder | Applicant |
| US2012/0296739(A1) | 2012-11-01 | Cassidy et al. | Applicant |
| US2012/0296782(A1) | 2012-11-01 | Tsai et al. | Applicant |
| US2012/0304065(A1) | 2012-11-01 | Cai | Applicant |
| US2013/0014137(A1) | 2013-01-01 | Bhatia et al. | Applicant |
| US2013/0014155(A1) | 2013-01-01 | Clarke et al. | Applicant |
| US2013/0054757(A1) | 2013-02-01 | Spitz et al. | Applicant |
| US2013/0110608(A1) | 2013-05-01 | Cassidy et al. | Applicant |
| US2013/0117131(A1) | 2013-05-01 | Robinson et al. | Applicant |
| US2013/0117409(A1) | 2013-05-01 | Yang et al. | Applicant |
| US2013/0144903(A1) | 2013-06-01 | Andrews, II et al. | Applicant |
| US2013/0151352(A1) | 2013-06-01 | Tsai et al. | Applicant |
| US2013/0152123(A1) | 2013-06-01 | Briggs et al. | Applicant |
| US2013/0162655(A1) | 2013-06-01 | Mueller | Applicant |
| US2013/0166382(A1) | 2013-06-01 | Cassidy et al. | Applicant |
| US2013/0183021(A1) | 2013-07-01 | Osman | Applicant |
| US2013/0211891(A1) | 2013-08-01 | Daniel et al. | Applicant |
| US2013/0212611(A1) | 2013-08-01 | Van Aacken et al. | Applicant |
| US2013/0215116(A1) | 2013-08-01 | Siddique et al. | Applicant |
| US2013/0218964(A1) | 2013-08-01 | Jakobson | Applicant |
| US2013/0228615(A1) | 2013-09-01 | Gates et al. | Applicant |
| US2013/0254018(A1) | 2013-09-01 | Rao | Applicant |
| US2013/0290550(A1) | 2013-10-01 | Bangalore et al. | Applicant |
| US2014/0019860(A1) | 2014-01-01 | Sathish et al. | Applicant |
| US2014/0052576(A1) | 2014-02-01 | Zelenka | Examiner |
| US2014/0095330(A1) | 2014-04-01 | Briggs et al. | Applicant |
| US2014/0181208(A1) | 2014-06-01 | Robinson et al. | Applicant |
| US2014/0208235(A1) | 2014-07-01 | Robinson et al. | Applicant |
| US2014/0250211(A1) | 2014-09-01 | Spitz et al. | Applicant |
| US2014/0254942(A1) | 2014-09-01 | Liu et al. | Applicant |
| US2014/0282700(A1) | 2014-09-01 | Briggs et al. | Applicant |
| US2014/0359671(A1) | 2014-12-01 | Andrews, II et al. | Applicant |
| US2015/0039468(A1) | 2015-02-01 | Spitz et al. | Applicant |
| US2015/0073919(A1) | 2015-03-01 | Spitz et al. | Applicant |
| US2015/0074710(A1) | 2015-03-01 | Spitz et al. | Applicant |
| US2015/0074711(A1) | 2015-03-01 | Spitz et al. | Applicant |
| US2015/0092111(A1) | 2015-04-01 | Spitz et al. | Applicant |
| US2015/0095455(A1) | 2015-04-01 | Spitz et al. | Applicant |
| CN102782608 | 2012-11-01 | Applicant | |
| JP2002-007587 | 2002-02-01 | Applicant | |
| JP2004-038694 | 2004-02-01 | Applicant | |
| JP2008-112381 | 2008-05-01 | Applicant | |
| JP2002-526831 | 2008-08-01 | Applicant | |
| KR100824197(B1) | 2008-04-01 | Applicant | |
| WO1/69364(A2) | 2001-09-01 | Applicant | |
| WO1/91869 | 2001-12-01 | Applicant | |
| WO2005/036875 | 2005-04-01 | Applicant | |
| WO2005/039131 | 2005-04-01 | Applicant | |
| WO2008/016634(A2) | 2008-02-01 | Applicant | |
| WO2009/012580(A1) | 2009-01-01 | Applicant | |
| WO2011/149491 | 2011-12-01 | Applicant | |
| WO2013/033239 | 2013-03-01 | Applicant | |
| WO2013/192557(A2) | 2013-12-01 | Applicant | |
| WO2015/013117 | 2015-01-01 | Applicant | |
| WO2015/038795 | 2015-03-01 | Applicant | |
| WO2015/038798 | 2015-03-01 | Applicant | |
| WO2015/038802 | 2015-03-01 | Applicant | |
| WO2015/048375 | 2015-04-01 | Applicant | |
| WO2015/048377 | 2015-04-01 | Applicant | |
| WO2015/054644 | 2015-04-01 | Applicant |
Non-Patent Literature (98)
- Office Action dated Apr. 10, 2014 in connection with U.S. Appl. No. 14/042,477.Applicant
- Office Action dated Apr. 11, 2014 in connection with U.S. Appl. No. 14/091,219.Applicant
- “Content distributors can shopping-enable video content”, www.web.archive.org, Apr. 27, 2007, 1 page.Applicant
- Dan Kaplan, “Delivery Agent lets you buy products in your favorite TV shows”, www.web.archive.org, May 4, 2007, 4 pages.Applicant
- “Shopisodes Enable You to Dress Like Your Favorite TV Character”, www.web.archive.org, Oct. 26, 2007, 1 page.Applicant
- Jesse Liebman, “Reality TV That's Social, Bravo!”, www.web.archive.org, Dec. 22, 2008, 6 pages.Applicant
- Kongwah Wan, et al., “Advertising Insertion in Sports Webcasts”, 2007 IEEE, p. 78-82.Applicant
- Miguel Helft, “Google Aims to Make YouTube Profitable With Ads”, The New York Times, Aug. 22, 2007, 3 pages.Applicant
- Chris Tomlinson, “Google tries to relive past glories by making YouTube pay for itself”, Birmingham Post, Sep. 4, 2007, 3 pages.Applicant
- John Skidgel, “Producing Flash CS3 Video, Techniques for Video Pros and Web Designers”, 2007, 9 pages.Applicant
- Jan Krikke, “Streaming Video Transforms the Media Industry”, IEEE, Jul./Aug. 2004, p. 6-12.Applicant
- Tao Mei, et al., “VideoSense—Towards Effective Online Video Advertising”, Sep. 23-28, 2007, p. 1075-1084.Applicant
- Dr. Harry van Vliet, “Where Television and Internet meet . . . New experiences for rich media”, Jan. 2002, 35 pages.Applicant
- “IAB Announces Advertising Creative Guidelines for Online Broadband Video Commercials”, Nov. 29, 2005, 4 pages.Applicant
- “Digital Video In-Stream Ad Format Guidelines and Best Practices”, Interactive Advertising Bureau, May 2008, 17 pages.Applicant
- “Broadband Ad Creative Guidelines”, Dec. 31, 2006, 3 pages.Applicant
- Rich Media Guidelines: Fall 2004, Dec. 31, 2006, 3 pages.Applicant
- “About Rich Media Guidelines Compliance: In-Page Units”, Jan. 7, 2007, 2 pages.Applicant
- “About Rich Media Guidelines Compliance: Over-the-Page Units”, Jan. 7, 2007, 2 pages.Applicant
- “Digital Video Ad Serving Template (VAST), Version 2.0”, iab., Nov. 2009, 18 pages. (Redlined).Applicant
- “Digital Video Ad Serving Template (VAST), Version 2.0”, iab., Nov. 2009, 16 pages.Applicant
- “DART Motif for In-Stream Helps Publishers Improve Efficiency, Push the Envelope with Video Ad Effects and Offer Advertisers Trusted, Reliable Reporting Metrics”, Nov. 6, 2006, 3 pages.Applicant
- “DoubleClick Debuts Video Ad-Serving Solution”, Nov. 6, 2006, 2 pages.Applicant
- Liz Gannes, “YouTube's New Inline Ads: Screenshots”, May 11, 2007, 7 pages.Applicant
- “Final Broadband Ad Creative Guidelines”, Interactive Advertising Bureau, Standards & Guidelines, 4 pages.Applicant
- Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration dated Jan. 10, 2014 in connection with International Patent Application No. PCT/US13/47124.Applicant
- Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration dated Jun. 24, 2011 in connection with International Patent Application No. PCT/US10/57567.Applicant
- “Akamai for Media & Entertainment”, Akamai Technologies, Inc., 2007, 38 pages.Applicant
- “ebd Web Video Player, Increase Online Video Ad Monetization”, www.ebdsoft.tv, 2010, 2 pages.Applicant
- Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration dated Nov. 14, 2012 in connection with International Patent Application No. PCT/US2012/52897.Applicant
- Office Action dated Jul. 21, 2014 in connection with U.S. Appl. No. 14/091,219.Applicant
- Office Action dated Jul. 9, 2014 in connection with U.S. Appl. No. 13/753,384.Applicant
- Office Action dated Aug. 27, 2014 in connection with U.S. Appl. No. 12/787,505.Applicant
- Office Action dated Aug. 27, 2014 in connection with U.S. Appl. No. 14/079,385.Applicant
- International Search Report dated Nov. 24, 2014 in connection with International Application No. PCT/US14/55233; 2 pages.Applicant
- Written Opinion of International Searching Authority dated Nov. 24, 2014 in connection with International Application No. PCT/US14/55233; 3 pages.Applicant
- International Search Report dated Dec. 15, 2014 in connection with International Application No. PCT/US14/57595; 2 pages.Applicant
- Written Opinion of International Searching Authority dated Dec. 15, 2014 in connection with International Application No. PCT/US14/57595; 3 pages.Applicant
- International Search Report dated Dec. 16, 2014 in connection with International Application No. PCT/US14/55226; 2 pages.Applicant
- Written Opinion of International Searching Authority dated Dec. 16, 2014 in connection with International Application No. PCT/US14/55226; 4 pages.Applicant
- International Search Report dated Dec. 16, 2014 in connection with International Application No. PCT/US14/55229; 2 pages.Applicant
- Written Opinion of International Searching Authority dated Dec. 16, 2014 in connection with International Application No. PCT/US14/55229; 4 pages.Applicant
- International Search Report dated Jan. 9, 2015 in connection with International Application No. PCT/US14/57597; 2 pages.Applicant
- Written Opinion of International Searching Authority dated Jan. 9, 2015 in connection with International Application No. PCT/US14/57597; 4 pages.Applicant
- Non-Final Office Action dated Dec. 18, 2014 in connection with U.S. Appl. No. 14/484,047; 8 pages.Applicant
- Non-Final Office Action dated Dec. 19, 2014 in connection with U.S. Appl. No. 14/484,065; 8 pages.Applicant
- Non-Final Office Action dated Dec. 26, 2014 in connection with U.S. Appl. No. 14/484,225; 8 pages.Applicant
- Non-Final Office Action dated Jan. 6, 2015 in connection with U.S. Appl. No. 14/512,204; 18 pages.Applicant
- Non-Final Office Action dated Jan. 9, 2015 in connection with U.S. Appl. No. 14/292,423; 14 pages.Applicant
- International Search Report dated Jan. 26, 2015 in connection with International Patent Application No. PCT/US2014/060150, 3 pages.Applicant
- Written Opinion of International Searching Authority dated Jan. 26, 2015 in connection with International Patent Application No. PCT/US2014/060150, 4 pages.Applicant
- Final Office Action dated Jul. 16, 2015 in connection with U.S. Appl. No. 14/787,505; 15 pages.Applicant
- Final Office Action dated Jul. 17, 2015 in connection with U.S. Appl. No. 14/484,065; 13 pages.Applicant
- Final Office Action dated Jul. 30, 2015 in connection with U.S. Appl. No. 14/512,204; 22 pages.Applicant
- International Search Report dated Jul. 30, 2015 in connection with International Patent Application No. PCT/US2015/019979; 5 pages.Applicant
- Written Opinion of the Internatoinal Searching Authority dated Jul. 30, 2015 in connection with International Patent Application No. PCT/US2015/019979; 5 pages.Applicant
- International Search Report dated Jun. 3, 2015 in connection with International Application No. PCT/US15/18140; 2 pages.Applicant
- Written Opinion of the International Searching Authority dated Jun. 3, 2015 in connection with International Application No. PCT/US15/18140; 7 pages.Applicant
- Non-Final Office Action dated May 4, 2012 in connection with U.S. Appl. No. 12/424,569; 7 pages.Applicant
- Final Office Action dated Oct. 25, 2012 in connection with U.S. Appl. No. 12/424,569; 10 pages.Applicant
- Non-Final Office Action dated Mar. 1, 2013 in connection with U.S. Appl. No. 12/787,505; 10 pages.Applicant
- Non-Final Office Action dated Mar. 15, 2013 in connection with U.S. Appl. No. 12/424,569; 9 pages.Applicant
- Final Office Action dated Jul. 18, 2013 in connection with U.S. Appl. No. 12/424,569; 9 pages.Applicant
- Non-Final Office Action dated Nov. 19, 2013 in connection with U.S. Appl. No. 12/424,569; 12 pages.Applicant
- Final Office Action dated Mar. 20, 2014 in connection with U.S. Appl. No. 12/424,569; 11 pages.Applicant
- Non-Final Office Action dated Dec. 2, 2014 in connection with U.S. Appl. No. 13/923,089; 16 pages.Applicant
- Non-Final Office Action dated Aug. 20, 2015 in connection with U.S. Appl. No. 13/923,089; 11 pages.Applicant
- Final Office Action dated May 18. 2015 in connection with U.S. Appl. No. 14/484,047; 10 pages.Applicant
- Final Office Action dated May 21, 2015 in connection with U.S. Appl. No. 14/484,255; 13 pages.Applicant
- Final Office Action dated Jul. 1, 2015 in connection with U.S. Appl. No. 14/079,385; 13 pages.Applicant
- Reid, et al.; “An Analysis of Anonymity in the Bitcoin System”; http://arxiv.org/pdf/1107.4524.pdf; May 7, 2012; 29 pages.Applicant
- Office Action for U.S. Appl. No. 12/363,713, mailed Oct. 3, 2011.Applicant
- Office Action for U.S. Appl. No. 12/363,713, mailed Jun. 13, 2012.Applicant
- Office Action for U.S. Appl. No. 14/079,385, mailed Mar. 3, 2015.Applicant
- Office Action for U.S. Appl. No. 12/434,569, mailed Oct. 2, 2014.Applicant
- Office Action for U.S. Appl. No. 13/753,384, mailed May 17, 2013.Applicant
- Office Action for U.S. Appl. No. 13/753,384, mailed Oct. 25, 2013.Applicant
- Office Action for U.S. Appl. No. 13/753,384, mailed Dec. 20, 2013.Applicant
- Office Action for Australian Application No. 2012302021, dated Oct. 22, 2015, 3 pages.Applicant
- Notice of Acceptance for Australian Application No. 2012302021, dated May 4, 2016, 2 pages.Applicant
- First Office Action for Chinese Application No. 201280053145.7, mailed Mar. 1, 2016, 3 pages.Applicant
- Second Office Action for Chinese Application No. 201280053145.7, mailed Aug. 16, 2016, 3 pages.Applicant
- Supplementary European Search Report for European Application No. 12828677.0, mailed Sep. 28, 2015, 7 pages.Applicant
- Office Action for European Application No. 12828677.0, mailed Sep. 14, 2016, 7 pages.Applicant
- Office Action for Japanese Application No. 2014-528557, mailed Jul. 26, 2016, 2 pages.Applicant
- Office Action for Mexican Application No. MX/a/2014/002490, dated Jun. 10, 2016, 8 pages.Applicant
- Office Action for Russian Application No. 2014112353, mailed Feb. 18, 2016, 2 pages.Applicant
- Office Action for Canadian Application No. 2,877,567, dated Feb. 29, 2016, 5 pages.Applicant
- Supplementary European Search Report for European Application No. 13806161.9, mailed Jan. 28, 2016, 5 pages.Applicant
- Office Action for Mexican Application No. MX/a/2014/015947, dated Mar. 2, 2016.Applicant
- Office Action for U.S. Appl. No. 14/512,204, mailed Dec. 4, 2015, 20 pages.Applicant
- Office Action for U.S. Appl. No. 14/512,204, mailed Aug. 12, 2016, 15 pages.Applicant
- Office Action for U.S. Appl. No. 14/497,686, mailed Feb. 24, 2015, 13 pages.Applicant
- Office Action for U.S. Appl. No. 14/498,800, mailed Mar. 27, 2015, 18 pages.Applicant
- Notification on Results of Estimation of Patentability of Invention dated Feb. 16, 2015 for Russian Patent Application No. 2012105917/08(009063); 7 pages.Applicant
- Lob, S. et al., “NEMO—The Network Environment for Multimedia Objects,” ACM, IITM '10 Proceedings of the First International Conference on Intelligent Interactive Technologies and Multimedia, ISBN 978-1-4503-0408-5, pp. 245-249 (2010) http://doi.acm.org/10.1145/1963564.1963607.Applicant
- MediaTomb, MediaTomb Scripting [online], Retrieved on Oct. 11, 2015, URL: http://mediatomb.cc/pages/scripting, 24 pages.Applicant
- Morin, J-H et al., “HyperNews: a commercial electronic newspaper,” pp. 147-163 (Nov. 8, 2004).Applicant